Equipment management system and equipment management method
By adopting multi-database structure and controller management access rights in the device management system, the problem of gateway devices controlling device information access rights is solved, the balance between information security and user convenience is achieved, and the risk of information leakage is reduced.
Patent Information
- Application Number
- CN201880062716.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-09-28
- Filing Date
- 2018-09-26
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2038-09-26
AI Technical Summary
When existing equipment management systems allow gateway devices to access device information, it is difficult to balance user convenience and the risk of proprietary information leakage, and cannot effectively control the gateway devices' access rights to sensitive information.
Adopt a multi-database structure, wherein the first database stores information that allows the gateway to access, the second database stores information of sensitive equipment that prohibits the gateway from access, and allows or prohibits the gateway from accessing different databases through the controller to control the risk of information leakage, and provide User convenience.
By separating information storage and access rights, the risk of leakage of sensitive equipment information is reduced, while improving user convenience and ensuring information security.
Smart Images

Figure CN111164639B_ABST
Abstract
Description
Technical Field
[0001] The invention relates to an equipment management system and an equipment management method. Background Art
[0002] A device management system is known that manages various information about a plurality of devices. Examples of the various information include basic information and maintenance information of the devices. For example, the basic information includes: installation date, expected service life, and rated power consumption. The maintenance information includes the maintenance history of the devices (e.g., Patent Document 1).
[0003] Reference List
[0004] Patent Literature
[0005] Patent Document 1: Japanese Patent Application Publication No. 2005-182399 Summary of the invention
[0006] The device management system according to the first disclosure includes: a gateway device having an interface configured to receive an operation command for operating a device; a first database configured to store first information that is allowed to be accessed from the gateway device; a second database configured to store second information that is prohibited from being accessed from the gateway device; and a controller configured to allow access to the first database from the gateway device and prohibit access to the second database from the gateway device. The second information includes device information collected from a control device that controls the device.
[0007] The device management method according to the first disclosure includes: step A, receiving an operation command for operating a device by a gateway device; step B, storing first information that is allowed to be accessed from the gateway device in a first database; step C, storing second information that is prohibited from being accessed from the gateway device in a second database; step D, allowing access to the first database from the gateway device; and step E, prohibiting access to the second database from the gateway device. The second information includes device information collected from a control device for controlling the device. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 is a diagram showing a device management system 100 according to an embodiment.
[0009] Figure 2 is a diagram showing a device management apparatus 200 according to an embodiment.
[0010] Figure 3 is a diagram showing an example of information stored in the first DB 211 according to the embodiment.
[0011] Figure 4 is a diagram showing an example of information stored in the second DB 212 according to the embodiment.
[0012] Figure 5 is a diagram showing an example of information stored in the third DB 213 according to the embodiment.
[0013] Figure 6 is a diagram illustrating a device management method according to an embodiment. DETAILED DESCRIPTION
[0014] Recently, a gateway device equipped with a user interface such as a voice input interface has attracted attention. From the perspective of improving user convenience, it is preferred to allow the gateway device to access the information managed by the device management system without restriction. On the other hand, from the perspective of suppressing the leakage of proprietary information, it is not advisable to allow the gateway device to access the information managed by the device management system without restriction.
[0015] The present disclosure provides a device management system and a device management method, which support access to properly operate a gateway device.
[0016] Embodiments will be described below with reference to the accompanying drawings. In the following description of the accompanying drawings, the same or similar parts are represented by the same or similar symbols.
[0017] However, it should be noted that the drawings are schematic and their dimensional ratios etc. are different from the actual situation. Therefore, the specific dimensions etc. should be determined according to the following description. Of course, the drawings include parts with different dimensional relationships or ratios with each other.
[0018] [Example]
[0019] (Equipment Management System)
[0020] The following will describe a device management system according to an embodiment. Figure 1 As shown in FIG. 1 , the equipment management system 100 includes an equipment management device 200, a facility 300, a contractor terminal 400, and an external server 500. Figure 1 , facilities 300A to 300C are shown as examples of the facilities 300. The equipment management apparatus 200, the facilities 300, the contractor terminal 400, and the external server 500 are connected to the network 120. The network 120 only needs to provide a line between the equipment management apparatus 200 and the facilities 300, a line between the equipment management apparatus 200 and the contractor terminal 400, and a line between the facilities 300 and the external server 500. For example, the network 120 is the Internet. The network 120 can provide a dedicated line such as a virtual private network (VPN).
[0021] The equipment management apparatus 200 manages equipment installed at the facility 300. The details of the equipment management apparatus 200 will be described later (see Figure 2 ).
[0022] The facility 300 has a device 310, an energy management system (EMS) 320, and a gateway device 330. The device 310 is connected to the power grid 110. The device 310 may be a power generation device. The power generation device may be a device that generates power using natural energy such as sunlight, wind energy, or geothermal energy. The power generation device may be a fuel cell device. The device 310 may be a battery device. The device 310 may be a load device that consumes electricity. The load device may be an air conditioning device or a lighting device. The facility 300 may have two or more types of devices 310.
[0023] The EMS 320 is a device (EMS: Energy Management System) that manages power information indicating power in the facility 300. The power in the facility 300 is power flowing within the facility 300, power purchased by the facility 300, or power sold by the facility 300.
[0024] The gateway device 330 has an interface that receives an operation command for operating the device 310. The interface may include a sound input interface. The interface may include a sound output interface. The interface may include a button input interface. The interface may include a touchpad input interface. The interface may include a gesture input interface. A gesture is, for example, an action such as waving a hand toward a camera possessed by the interface. The interface may include an image output interface. The gateway device 330 has an artificial intelligence (AI) function, which has a function of analyzing an operation command and performing various actions based on the analysis results of the operation command. Various actions may include an action of obtaining information from a server connected via the network 120, and may also include an action of outputting information obtained from a server connected via the network 120. The server may be the device management device 200 or an external server 500. Various actions may include an action of sending a control command based on an operation command, and may also include an action of receiving a response command to the control command. The gateway device 330 may send a control command to the device 310 via the EMS 320, or may send a control command to the device 310 without the intervention of the EMS 320. The gateway device 330 may be referred to as a smart speaker or AI.
[0025] Here, the gateway device 330 may send the information collected by the gateway device 330 to the external server 500. The information collected by the gateway device 330 may be the analysis result of the operation command, or may be the information acquired from the equipment management device 200.
[0026] The contractor terminal 400 may be a terminal belonging to a contractor that performs maintenance on the device 310. Examples of maintenance include inspection, checking the deterioration state of the device; maintenance, performing simple services during the inspection; repair, fixing device problems to restore the function and performance of the device to the original installation state; and replacement, replacing an existing device with a new one.
[0027] Here, the device management system 100 may have a power management server. For example, the power management server sends to the facility 300: a power flow control message requesting control of the power flow from the power grid 110 to the facility 300, a reverse power flow control message requesting control of the reverse power flow from the facility 300 to the power grid 110, a power supply control message requesting control of the device 310 (distributed power source) provided in the facility 300, and the like.
[0028] The external server 500 may be a server that provides a search engine to search for desired information based on the analysis result of the operation command. The external server 500 may be a server operated by an entity that provides the gateway device 330. The external server 500 may manage the information collected by the gateway device 330 as big data, and utilize the managed big data as information to improve user convenience.
[0029] (Device Management Device)
[0030] The following will describe a device management apparatus according to an embodiment. Figure 2 As shown, the equipment management apparatus 200 includes a manager 210 , a communicator 220 , and a controller 230 .
[0031] The manager 210 includes a storage medium (media) such as a nonvolatile memory or / and an HDD, and manages information on a plurality of facilities 300. The manager 210 has a first database (DB) 211, a second database (DB) 212, and a third database (DB) 213.
[0032] The first DB 211 is an example of a first database storing first information, and the first information allows the gateway device 330 to access. The first information includes guidance information about the operation method of the device. For example, the guidance information includes at least one of the following: device name, installation information, inspection information, and usage information, such as Figure 3 shown.
[0033] The device name is the name of the device 310. The device name may be information that uniquely identifies the device 310 (eg, a product model, a manufacturer code), or may be information indicating the type of the device 310 (eg, a solar cell device, an air conditioning device, etc.).
[0034] The installation information is information required when the device 310 is installed in the facility 300. For example, the installation information is information indicating the installation process of the device 310, such as "connect the cable xx to the terminal oo" or "turn on the power". For example, the installation information can be used by the installation contractor of the device 310.
[0035] The inspection information is information required when inspecting the device 310. For example, the inspection information is information indicating the inspection process of the device 310, such as "Is the cable xx connected to the terminal oo?" or "Is the power light on?" For example, the inspection information can be used by an inspection contractor of the device 310. The inspection of the device 310 can be an inspection performed after the device 310 is installed, or can be an inspection performed as maintenance of the device 310.
[0036] The usage information is information required when the device 310 is used. For example, the usage information is information indicating the use process of the device 310, such as "power on" or "press button oo". The usage information may be information indicating the function of the device 310 or information indicating troubleshooting of the device 310. The usage information may be information used by the user of the device 310.
[0037] In an embodiment, the first DB 211 may store index information that associates guide information, device information, and user information with each other, such as Figure 3 The index information contains any combination of characters and numbers and does not need to be meaningful.
[0038] The second DB 212 is an example of a second database storing second information, the second information prohibiting access by the gateway device 330. The second information includes device information about the device 310. The device information is information collected by the EMS 320 that controls the device 310. For example, the device information includes at least one of the following: device name, sensing data, error code, statistical data, reference data, and operation history, such as Figure 4 shown.
[0039] The device name is the name of the device 310. The device name may be information that uniquely identifies the device 310 (eg, a product model, a manufacturer code), or may be information indicating the type of the device 310 (eg, a solar cell device, an air conditioning device, etc.).
[0040] The sensed data is data including numerical data representing the operating state of the device 310. The sensed data is measured by a sensor provided at the facility 300. Alternatively, the sensed data may be measured by a sensor provided at the device 310 or by a sensor provided at the EMS 320. The sensed data is sent from the EMS 320 to the device management apparatus 200. For example, the sensed data may be output power data of the device 310, power consumption data of the device 310, temperature data of the device 310, ambient temperature data of the device 310, ambient humidity data of the device 310, and the like.
[0041] The error code is a code that identifies an error of the device 310. The error may be detected by the device 310 or by the EMS 320. The error code is sent from the EMS 320 to the device management apparatus 200. For example, the error code may be a code indicating that the temperature of the device 310 is abnormal, a code indicating that a component provided in the device 310 is abnormal, a code indicating that the output power of the device 310 is abnormal, or a code indicating that the power consumption of the device 310 is abnormal.
[0042] Statistical data is data obtained after statistical processing of numerical data. Statistical data can be generated by the device management apparatus 200. Alternatively, statistical data can be generated by the device 310, or can be generated by the EMS 320. For example, statistical data can be numerical data grouped or sorted for a specific purpose. For example, statistical data can be data indicating the output power transition (distribution) of the device 310 within a predetermined time (e.g., 1 day, 1 week, or 1 month), or can be data indicating the power consumption transition of the device 310 within a predetermined time.
[0043] The reference data is data including a threshold value to be compared with the numerical data. The reference data is a value set by the manufacturer of the device 310 or the like. The threshold value is a value used to determine an error of the device 310.
[0044] The operation history is the history of the operation of the device 310. The operation history may be the transition of the operation mode within a predetermined time (e.g., 1 day, 1 week, or 1 month), the number of executions of a predetermined operation mode, or the number of times the device 310 stops operating. For example, if the device 310 is a fuel cell device, the operation history may be the number of normal stops of the fuel cell device, or the number of emergency stops of the fuel cell device. If the device 310 is a battery device, the operation history may be the number of times the battery device is charged, the charging time of the battery device, the number of times the battery device is discharged, the discharge time of the battery device, or the number of charge / discharge cycles of the battery device.
[0045] In an embodiment, the second DB 212 may store index information that associates guide information, device information, and user information with each other, such as Figure 4 The index information contains any combination of characters and numbers and does not need to be meaningful.
[0046] The third DB 213 stores user information about users. The user can be a legal person or a natural person (individual). For example, the user information includes at least one of the following: the user's name or title, the user's address, and the user's contact information (email address and telephone number), such as Figure 5 As shown. User information is information to be protected. In addition, user information may include at least one of contractor information and maintenance information, such as Figure 5 shown.
[0047] The contractor information is information about the contractor that conducts transactions with the user. The contractor may be a contractor that performs maintenance. The contractor may be the manufacturer of the device 310. The contractor may be a company such as a power generation company, a power transmission and distribution company, a retail company, or a resource integrator.
[0048] Maintenance information is information about maintenance of the device 310. The maintenance information may be a maintenance history or a maintenance plan. The maintenance information may be accumulated through maintenance information sent from the contractor terminal 400 or accumulated through maintenance information input by an operator. The maintenance information may include a maintenance execution date, a planned maintenance date, and maintenance content. As described above, maintenance includes, for example: inspection, checking the deterioration state of the device; maintenance, performing simple services during the inspection; repair, fixing equipment problems to restore the function and performance of the device to the original installation state; and replacement, replacing an existing device with a new device.
[0049] In an embodiment, the third DB 213 may store index information that associates guide information, device information, and user information with each other, such as Figure 5 The index information contains any combination of characters and numbers and does not need to be meaningful.
[0050] The communicator 220 includes a communication module and communicates with the facility 300 and the contractor terminal 400 via the network 120. For example, the communicator 220 receives equipment information such as sensing data and error codes from the EMS 320. The communicator 220 receives maintenance information from the contractor terminal 400. The communicator 220 receives analysis results of operation commands from the gateway device 330.
[0051] The controller 230 includes, for example, a memory and a CPU, and controls various configurations provided in the equipment managing apparatus 200. In the embodiment, the controller 230 performs control as shown below.
[0052] The controller 230 collects device information from the EMS 320 that controls the device 310. The controller 230 may actively collect the device information transmitted from the EMS 320, or may collect the device information transmitted from the EMS 320 in response to a request to the EMS 320. As described above, the device information is stored in the second DB 212.
[0053] The controller 230 allows the EMS 320 to access the second DB 212. On the other hand, the controller 230 prohibits the EMS 320 from accessing the third DB 213. In other words, the controller 230 is configured to prohibit the EMS 320 from accessing the third DB 213 even if the EMS 320 is allowed to access the second DB 212.
[0054] Similarly, the controller 230 may allow the contractor terminal 400 to access the second DB 212. On the other hand, the controller 230 may prohibit the contractor terminal 400 from accessing the third DB 213. In other words, the controller 230 may be configured to prohibit the contractor terminal 400 from accessing the third DB 213 even if the contractor terminal 400 is allowed to access the second DB 212.
[0055] The controller 230 may provide device information to a third party. In this case, the controller 230 deletes at least the index information. According to such a configuration, the risk that user information may be leaked to a third party may be reduced. The third party is not particularly limited, and may be a company such as a power generation company, a transmission and distribution company, a retail company, or a resource aggregator.
[0056] In the present embodiment, the controller 230 allows the gateway device 330 to access the first DB 211. On the other hand, the controller 230 prohibits the gateway device 330 from accessing the second DB 212. In other words, the controller 230 is configured to prohibit the gateway device 330 from accessing the second DB 212, even if the gateway device 330 is allowed to access the first DB 211. Here, the controller 230 may allow the gateway device 330 to access the third DB 213, or may prohibit the gateway device 330 from accessing the third DB 213. If a user who is allowed to access the third DB 213 inputs an operation command to the gateway device 330, the controller 230 may allow the gateway device 330 to access the third DB 213.
[0057] Here, the user who inputs the operation command to the gateway device 330 can be considered as the user of the device 310. Therefore, the user who inputs the operation command to the gateway device 330 can be considered to have the authority to access the second information (device information) stored in the second DB 212. For example, the user has the right to access the second information via the EMS 320.
[0058] However, even if the access is based on an operation command obtained from a user having access to the second information, the controller 230 prohibits the gateway device 330 from accessing the second DB 212. In other words, the controller 230 prohibits the gateway device 330 from accessing the second DB 212, while allowing the EMS 320 to access the second DB 212.
[0059] (Device management method)
[0060] A device management method according to an embodiment will be described below.
[0061] like Figure 6 As shown, in step S10, user information is registered in the third DB 213. This registration is performed based on a contract or the like between the organizer of the equipment management apparatus 200 and the user of the equipment 310. The registration is performed by the operator of the equipment management apparatus 200.
[0062] In step S11, the guidance information is registered in the first DB 211. The registration may be performed before starting to install the device 310 in the facility 300. The registration may be performed when a sales contract for the device 310 is signed. The registration may be performed by information acquired from a server operated by the manufacturer of the device 310, or by an operator of the device management apparatus 200.
[0063] In step S12, the EMS 320 accesses the second DB 212 and transmits the sensing data to the second DB 212. If an error occurs in the device 320, the EMS 320 may transmit an error code to the second DB 212.
[0064] In step S13, the device management apparatus 200 updates the device information stored in the first DB 211 based on the sensing data. The device management apparatus 200 may update the device information stored in the first DB 211 based on the error code. The device management apparatus 200 automatically generates index information that can associate the device information with the user information. The index information is stored in the second DB 212 and the third DB 213.
[0065] In step S14, the gateway device 330 receives an operation command. In this case, the operation command is an instruction to request guidance information. The operation command may be issued by voice.
[0066] In step S15 , the gateway device 330 sends an access request to the first DB 211 to the equipment managing device 200 based on the analysis result of the operation command.
[0067] In step S16, in response to the access request, the equipment management device 200 sends guidance information to the gateway device 330. The gateway device 330 outputs the guidance information. The guidance information may be output by sound.
[0068] In step S17, the gateway device 330 receives an operation command. In this case, the operation command is an instruction to request device information. The operation command may be issued by voice.
[0069] In step S18 , the gateway device 330 transmits an access request to the second DB 212 to the equipment managing device 200 based on the analysis result of the operation command.
[0070] In step S19, in response to the access request, the equipment management device 200 transmits access rejection to the gateway device 330. The gateway device 330 may output the fact that access to the second DB 212 is prohibited. Such information may be output by sound.
[0071] In this case, the information output from the gateway device 330 may be information such as “the gateway device 330 is prohibited from accessing the second DB 212” or information such as “please access the second DB 212 from the user terminal”. Alternatively, the gateway device 330 may send a request for delivery of device information to the EMS 320, and the EMS 320 may send the device information managed by the EMS 320 or the device information acquired from the device management device 200 to the user terminal without passing through the gateway device 330. In the case where the request for delivery of the device information is sent, the output of the fact that the access to the second DB 212 is prohibited may be omitted.
[0072] In step S20 , the gateway device 330 receives an operation command. In this case, the operation command is an instruction to request an operation of the device 310 .
[0073] In step S21 , the gateway device 330 transmits a control command based on the operation command to the EMS 320 .
[0074] (Function and Effect)
[0075] In an embodiment, the device management apparatus 200 is configured to prohibit the gateway apparatus 330 from accessing the second DB 212. According to this configuration, since the gateway apparatus 330 that may send various information to the external server 500 is prohibited from accessing the second DB 212, the risk that the second information belonging to the specialized knowledge of the entity running the device management apparatus 200 may be leaked to another entity can be reduced.
[0076] In the embodiment, the equipment managing apparatus 200 is configured to allow the gateway apparatus 330 to access the first DB 211. According to this configuration, since part of the information stored in the equipment managing apparatus 200 is provided, user convenience can be improved.
[0077] [Other embodiments]
[0078] The present invention has been described by the above embodiments. However, the drawings and discussions constituting a part of the present disclosure should not be interpreted as limiting the present invention. According to the present disclosure, various alternative embodiments, examples and operating techniques will be obvious to those skilled in the art.
[0079] In the embodiment, the first DB 211, the second DB 212, and the third DB 213 are physically different databases. However, the embodiment is not limited thereto. The first DB 211, the second DB 212, and the third DB 213 may be formed of one database and virtually isolated from each other by setting access rights.
[0080] In the embodiment, the first DB 211, the second DB 212, and the third DB 213 are provided in the device management apparatus 200. However, the embodiment is not limited thereto. At least any one of the first DB 211, the second DB 212, and the third DB 213 may be provided in a server connected to the device management apparatus 200 via the network 120.
[0081] Although not specifically mentioned in the embodiment, the functions of the device management apparatus 200 may be provided by a cloud service.
[0082] In the embodiment, the controller for prohibiting the gateway device 330 from accessing the second DB 212 is set in the equipment management device 200. However, the embodiment is not limited thereto. The controller for prohibiting the gateway device 330 from accessing the second information may be set in the gateway device 330. In other words, the gateway device 330 may autonomously prohibit itself from accessing the second DB 212.
[0083] In an embodiment, the control device that controls the device 310 is the EMS 320. However, the embodiment is not limited thereto. The control device may be the device 310 itself. The control device may be a remote controller that sends a control command to the device 310.
[0084] Although not specifically mentioned in the embodiment, the device management apparatus 200 (controller 230) may set access rights to information elements included in the device information for each entity that accesses the device information. For example, the device management apparatus 200 may allow the EMS 320 to access the sensing data, but prohibit the contractor terminal 400 from accessing the sensing data. Alternatively, the device management apparatus 200 may allow the contractor terminal 400 to access the operation history, but prohibit the EMS 320 from accessing the statistical data.
[0085] In the embodiment, the entity accessing the device information is the EMS 320 and the contractor terminal 400. However, the embodiment is not limited thereto. The entity may be a user terminal belonging to a user of the device 310. In this case, the device management apparatus 200 may allow the user terminal to access the operation history, but prohibit the user terminal from accessing the sensing data.
[0086] Although not specifically mentioned in the embodiments, the device information may include basic information such as installation date, expected service life, and rated power consumption.
Claims
1. A device management system, comprising: A smart speaker having an interface configured to receive an operation command for operating the device from a user of the device by voice, and a sound output interface configured to output information by voice based on the operation command, and to send various information to an external server; a first database configured to store first information accessible from the smart speaker; a second database configured to store second information that is prohibited from being accessed from the smart speaker; as well as a controller configured to allow access to the first database from the smart speaker and to disable access to the second database from the smart speaker; in The first information includes instruction information related to the operation method of the device, The second information includes device information collected from a control device that controls the device, The controller is configured to, for the smart speaker, disable access to the second database from the smart speaker, The smart speaker outputs the first information obtained from the first database through sound, In response to access to the second database being prohibited, the smart speaker outputs information recommending the use of another device other than the smart speaker to access the second database to the user who has executed the operation command to request the second information. 2 . The equipment management system according to claim 1 , wherein the first database and the second database are physically different databases from each other. 3 . The equipment management system according to claim 1 , wherein the first database and the second database store index information associating the first information and the second information with each other.
4. An equipment management system according to claim 1 or 2, wherein the equipment information includes at least one of the following: sensing data, including numerical data indicating the operating status of the equipment; an error code, identifying an error of the equipment; statistical data, obtained by performing statistical processing on the numerical data; reference data, including a threshold value for comparison with the numerical data; and the operating history of the equipment.
5. The equipment management system according to claim 1 or 2, wherein the smart speaker is configured to send a control command based on the operation command to the control device.
6. The device management system according to claim 1 or 2, wherein the smart speaker has a function of sending information collected by the smart speaker to an external server.
7. A device management method, comprising the following steps: (A) receiving an operation command for operating a device by a smart speaker, the smart speaker having an interface configured to receive the operation command from a user of the device by voice, and a sound output interface configured to output information by voice based on the operation command, and sending various information to an external server; (B) storing first information accessible from the smart speaker in a first database; (C) storing in a second database second information that is prohibited from being accessed from the smart speaker; (D) allowing access to the first database from the smart speaker; as well as (E) disabling access to the second database from the smart speaker; wherein The first information includes instruction information related to the operation method of the device, The second information includes device information collected from a control device for controlling the device, Step (E) includes: for the smart speaker, prohibiting access to the second database from the smart speaker, Step (D) includes: outputting the first information obtained from the first database by sound, Step (E) includes: in response to access to the second database being prohibited, outputting to the user who has executed an operation command to request the second information information information recommending the use of another device different from the smart speaker to access the second database.
