Information provision device, information provision program, apparatus registration system, and apparatus registration method

Abstract

To facilitate the execution of communication settings of devices.SOLUTION: A provisioning server 10 acquires identification information of a device with which destination information indicating the location of a destination to which data is to be sent from the device is associated, receives a query for the destination information from the device, and notifies the device requesting the query of the destination information associated with the identification information of the device requesting the query.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information providing device, an information providing program, a device registration system, and a device registration method. [Background technology]

[0002] BACKGROUND ART Conventionally, there is known a technique using a cloud environment for collecting data from various devices such as gateway devices, sensor devices, and control devices installed in a plant or the like. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6421220 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with conventional technologies, it is difficult to easily configure communication settings for devices when building a data collection system using a cloud environment because individual settings are required for each communication connection layer, such as the cloud environment, gateway devices, and sensor devices, which places a heavy burden on engineering.

[0005] The present invention has been made in view of the above, and has an object to easily execute communication settings for a device. [Means for solving the problem]

[0006] The present invention provides an information providing device comprising: an acquisition unit that acquires identification information of a device to which destination information indicating the location of the destination to which data is to be sent from the device is associated; a reception unit that receives an inquiry about the destination information from the device; and a notification unit that notifies the device that is the source of the inquiry of the destination information that is associated with the identification information of the device that is the source of the inquiry.

[0007] The present invention also provides an information provision program that causes a computer to execute the following processes: acquire identification information of a device to which destination information indicating the location of the destination to which data is to be sent from the device is associated; accept an inquiry about the destination information from the device; and notify the device that requested the inquiry of the destination information that is associated with the identification information of the device that requested the inquiry.

[0008] The present invention also provides a device registration system including an information management device that performs specified processing on data received from a device, and an information providing device, wherein the information management device has a sending unit that sends to the information providing device identification information of the device to be collected, destination information indicating the destination of the data, and identification information of the device that is associated with the destination information, and the information providing device has an acquiring unit that acquires the identification information from the information management device, a receiving unit that accepts an inquiry about the destination information from the device, and a notification unit that notifies the device that requested the inquiry of the destination information that is associated with the identification information of the device that requested the inquiry.

[0009] The present invention also provides a device registration method executed by a device registration system including an information management device that executes specified processing on data received from a device and an information providing device, the device registration method executing the following processes: the information management device transmits to the information providing device identification information of the device to be collected, destination information indicating the destination of the data, and identification information of the device that is associated with the destination information; and the information providing device acquires the identification information from the information management device, accepts an inquiry about the destination information from the device, and notifies the device that requested the inquiry of the destination information that is associated with the identification information of the device that requested the inquiry. [Effects of the Invention]

[0010] According to the present invention, there is an advantage that communication settings for a device can be easily performed. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an example of the configuration of a device registration system according to an embodiment. [Figure 2] FIG. 1 is a diagram illustrating a device registration system of a reference technology. [Figure 3] FIG. 2 is a block diagram showing an example of the configuration of each device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a device information storage unit of a provisioning server according to the embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a device information storage unit of the application server according to the embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of a plant information storage unit of an application server according to the embodiment. [Figure 7] FIG. 10 is a sequence diagram illustrating an example of the flow of a device registration process according to the embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a hardware configuration. DETAILED DESCRIPTION OF THE INVENTION

[0012] An information providing device, an information providing program, a device registration system, and a device registration method according to an embodiment of the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited to the embodiment described below.

[0013] [Embodiment] The configuration of the device registration system 100 according to the embodiment, the configuration of each device, and the processing flow will be described below, and finally, the effects of the embodiment will be described.

[0014] 1. Configuration of device registration system 100 The configuration of a device registration system 100 according to an embodiment will be described in detail using Fig. 1. Fig. 1 is a diagram showing an example of the configuration of the device registration system 100 according to an embodiment. Below, an example of the overall configuration of the device registration system 100, the processing of the device registration system 100, and problems with the device registration system 100P of the reference technology will be described in order, and finally, the effects of the device registration system 100 will be described. Note that in the embodiment, factory production remote monitoring using plant equipment, which is a device installed in a plant, will be described as an example, but the device and field of use are not limited thereto, and the present invention can also be applied to environmental measurement remote monitoring such as power monitoring, wind power generation, water and sewage monitoring, and river monitoring.

[0015] (1-1. Example of the overall configuration of the device registration system 100) The device registration system 100 includes a provisioning server 10, which is an information providing device, an application server 20, which is an information management device, a receiving server 30, which is an information collecting device, and plant devices 40 (gateway devices 40A, sensor devices 40B, and control devices 40C). Here, the provisioning server 10, the application server 20, and the receiving server 30 are constructed in a cloud environment. The plant devices 40 are installed in a plant.

[0016] 1 may include a plurality of provisioning servers 10, a plurality of application servers 20, or a plurality of receiving servers 30. In addition, the application server 20 may be integrated with the receiving server 30.

[0017] (1-2. Overall processing of the device registration system 100) The following describes the overall processing of the device registration system 100. Note that the following steps S1 to S7 may be executed in a different order. Also, some of the following steps S1 to S7 may be omitted.

[0018] (1-2-1. Device information setting process) Engineer E, who is an administrator of the device registration system 100, sets device information in the application server 20 (step S1). For example, engineer E sets up gateway devices 40A, sensor devices 40B, control devices 40C, etc. on a network map that logically configures a network. At this time, the device information registered in the application server 20 includes identification information of the plant devices 40, such as hardware identification numbers, location information of the plant devices 40, such as global Internet Protocol (IP) addresses and cellular line telephone numbers, and application information related to applications that use the plant information collected by the plant devices 40. Furthermore, destination information related to the receiving server 30 to which each device sends data is also registered in the application server 20.

[0019] (1-2-2. Device information registration process) The application server 20 transmits the device information and destination information to the provisioning server 10 (step S2). At this time, the identification information of the plant device 40, the location information of the plant device 40, etc. are registered in the provisioning server 10 as the device information.

[0020] (1-2-3. Connection destination inquiry processing) The plant device 40 transmits an inquiry about the communication destination (information destination) of the plant device 40 to the provisioning server 10 (step S3). At this time, the plant device 40 transmits identification information of the plant device 40 to the provisioning server 10 along with the inquiry about the communication destination. The plant device 40 also connects based on location information of the provisioning server 10 that was incorporated into parameters in the storage area of the plant device 40 at the time of shipment from the factory, and requests destination information, which is location information of the receiving server 30, which is the communication destination, from the provisioning server 10. For example, when the plant device 40 is powered on, it connects to the provisioning server 10 based on a global IP address or a URL (Uniform Resource Locator) stored in the storage area, and requests destination information of the receiving server 30.

[0021] (1-2-4. Connection destination response processing) The provisioning server 10 transmits a response regarding the communication connection destination of the plant device 40 to the plant device 40 (step S4). At this time, the provisioning server 10 permits the connection of the plant device 40 using the device information as a whitelist, and transmits destination information, which is location information of the receiving server 30, such as a global IP address or a URL, to the permitted plant device 40. That is, the provisioning server 10 determines whether the device information contains the identification information acquired from the plant device 40 in step S3 above. Here, the provisioning server 10 permits the connection if the identification information is included in the device information, and does not permit the connection if the identification information is not included in the device information.

[0022] (1-2-5. Device information deletion process) The provisioning server 10 deletes the device information of the plant device 40 (step S5). At this time, the provisioning server 10 deletes the device information of the plant device 40 to which the destination information was sent. In addition, the provisioning server 10 deletes device information for which a predetermined period has elapsed since the device information was acquired in step S2 above.

[0023] (1-2-6. Plant information collection processing) The plant device 40 transmits the plant information to the receiving server 30, which is the communication connection destination (information transmission destination) (step S6). At this time, the plant device 40 changes the connection destination from the provisioning server 10 to the receiving server 30, and periodically transmits plant information such as measurement data and control data acquired from the plant to the receiving server 30.

[0024] (1-2-7. Plant information registration process) The receiving server 30 transmits the received plant information to the application server 20 (step S7). Then, the plant information received by the application server 20 is operated by an application on the application server 20.

[0025] (1-3. Device Registration System 100P) The following describes an overview of the device registration process of the reference technology and then describes the problems with the reference technology using Fig. 2. Fig. 2 is a diagram illustrating the device registration system of the reference technology.

[0026] (1-3-1. Overview of device registration process in reference technology) As shown in Fig. 2, the device registration system 100P has an application server 20, a receiving server 30, and plant devices 40 (gateway devices 40A, sensor devices 40B, and control devices 40C). Here, the application server 20 and the receiving server 30 are constructed in a cloud environment. The plant devices 40 are installed in a plant. Device registration process 1 and device registration process 2 related to the device registration system 100P will be described below.

[0027] (1-3-1-1. Device registration process 1) In device registration process 1, on-site engineering is required to set up communication-related settings for each connection layer, such as settings for the cloud environment, settings for gateway device 40A, which is a communication device, and settings for sensor device 40B and control device 40C connected to gateway device 40A. Furthermore, in device registration process 1, system consistency checks are required between the layers for the settings for each layer. That is, in device registration process 1, communication settings are made for communication from gateway device 40A to the upper side. Furthermore, in device registration process 1, settings are made for devices connected to gateway device 40A on the upper side. In this case, in device registration process 1, settings are made using a preferred connection to gateway device 40A, sensor device 40B, etc., or a local wireless connection.

[0028] (1-3-1-2. Device registration process 2) In the device registration process 2, if the settings are not to be configured by engineering, a method of configuring the settings at the time of shipping at a factory can also be implemented. In this case, in the device registration process 2, the QR code (registered trademark) or the like attached to the sensor device 40B or the gateway device 40A can be used to simplify input of the settings for the gateway device 40A and the cloud environment.

[0029] (1-3-2. Issues with the device registration process in the reference technology) Below, we will explain the problems with the device registration process of the reference technology: Problem 1 when engineering is performed on site (device registration process 1), and Problem 2 when completing settings at the time of shipment (device registration process 2).

[0030] (1-3-2-1.Problem 1) When performing on-site engineering using the device registration system 100P, the following problems arise. First, individual settings are required for each communication connection layer, which requires knowledge of on-site communication settings and on-site engineering communications and cloud environments, limiting the number of engineers available. Second, device settings are required for each layer. As the number of connected devices increases, the cloud environment, gateway device 40A, sensor device 40B, and other aspects require enormous on-site engineering man-hours. Third, the information set for each layer must be checked for consistency as a whole, which requires significant man-hours. Furthermore, it is necessary to ensure that the settings for the connection source and destination are consistent. Fourth, as the number of devices increases, management becomes more complex, input errors increase, and rework is required. Fifth, because individual settings are required, even when multiple similar settings are required, individual settings are required.

[0031] (1-3-2-2.Problem 2) In the device registration system 100P, if on-site engineering is not performed or if the settings are completed at the time of shipment, the following problems arise: If on-site engineering is not performed, the device cannot be shipped until the cloud environment URL and the settings of the gateway device 40A have been determined to be used by the customer, and problems such as a long delivery time and a complicated production process occur.

[0032] (1-4. Effects of the Device Registration System 100) In the following, an overview of the device registration system 100 according to the embodiment will be described, and then the effects of the device registration system 100 will be described.

[0033] (1-4-1. Overview of the device registration system 100) In the device registration system 100, the provisioning server 10 acquires device information that associates the identification information of the plant device 40 with destination information indicating the location of the receiving server 30 to which the plant device 40 sends data, accepts an inquiry for destination information from the plant device 40, and notifies the plant device 40 that is the source of the inquiry of the destination information that is associated with the identification information of the plant device 40 that is the source of the inquiry based on the device information.

[0034] The provisioning server 10 also acquires device information from each of a plurality of application servers 20 that hold device information on plant devices from which plant information such as sensor values is to be collected. The provisioning server 10 also accepts inquiries based on location information that specifies the destination of the inquiry, which was set at the shipping stage before the plant devices 40 were installed in the plant. The provisioning server 10 also determines whether identification information of the plant devices 40 that are the source of the inquiry is registered in the device information, and if it is registered, notifies the plant devices 40 of destination information. If it is not registered, the provisioning server 10 outputs a warning that the plant devices 40 are not registered. The provisioning server 10 also stores the acquired device information and deletes, from the stored device information, device information of the plant devices 40 for which destination information has been notified or device information for which a predetermined time has passed since acquisition.

[0035] As described above, the device registration system 100 simplifies engineering work related to device settings on-site and can centrally manage overall consistency. Furthermore, the device registration system 100 can connect shipped devices to a specific cloud simply by turning them on, without the need for on-site configuration.

[0036] (1-4-2. Effects of the device registration system 100) The device registration system 100 has the following advantages. First, settings made in a cloud application are reflected in lower-level systems, so setting information is centrally managed and consistency is not lost. Second, on-site setting work is not required, which allows for a significant reduction in engineering work. Third, because engineering work such as writing setting information to hardware on-site is not required, on-site installation is possible without requiring the engineer E to have advanced knowledge of communication settings, etc. Fourth, because application management is performed, settings can be copied, which reduces the input burden on the engineer E. Fifth, because the setting data in the provisioning server 10 is deleted after use, device information is centrally managed only by the application server 20. As described above, the device registration system 100 can easily perform communication settings for devices.

[0037] 2. Configuration of each device in the device registration system 100 The functional configuration of each device included in the device registration system 100 shown in Fig. 1 will be described using Fig. 3. Fig. 3 is a block diagram showing an example configuration of each device according to an embodiment. Below, an example configuration of the entire device registration system 100 according to the embodiment will be described, and then example configurations of the provisioning server 10, the application server 20, the receiving server 30, and the plant device 40 according to the embodiment will be described in detail.

[0038] (2-1. Example of the overall configuration of the device registration system 100) 3, the device registration system 100 includes a provisioning server 10, an application server 20, a receiving server 30, and a plant device 40. The provisioning server 10, the application server 20, and the receiving server 30 are communicably connected via a predetermined communication network in a cloud environment. The plant device 40 also has a communication function that enables communication via a communication network N such as a mobile phone network.

[0039] The provisioning server 10, the application server 20, and the receiving server 30 are not limited to server devices constructed in a cloud environment, but may be physical servers, virtual machines, containers, or the like.

[0040] (2-2. Example of the configuration of the provisioning server 10) First, a configuration example of a provisioning server 10, which is an information providing device, will be described with reference to Fig. 3. The provisioning server 10 has a communication unit 11, a storage unit 12, and a control unit 13. The provisioning server 10 may also have an input unit (e.g., a keyboard, a mouse, etc.) that accepts various operations from an engineer E who is an administrator of the device registration system 100, and a display unit (e.g., a liquid crystal display, etc.) that displays various information.

[0041] (2-2-1. Communications Department 11) The communication unit 11 controls data communication with other devices. For example, the communication unit 11 performs data communication with each communication device via a router or the like. The communication unit 11 can also perform data communication with an operator's terminal (not shown).

[0042] (2-2-2. Storage section 12) The storage unit 12 stores various types of information that the control unit 13 refers to when it operates and various types of information that the control unit 13 acquires when it operates. The storage unit 12 includes a device information storage unit 12a. Here, the storage unit 12 can be realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. Note that, in the example of Fig. 3, the storage unit 12 is installed inside the provisioning server 10, but it may be installed outside the provisioning server 10, or multiple storage units may be installed.

[0043] (2-2-2-1.Device information storage unit 12a) The device information storage unit 12a stores device information and destination information transmitted from the application server 20. An example of information stored in the device information storage unit 12a will now be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the device information storage unit 12a of the provisioning server 10 according to the embodiment. In the example of Fig. 4, the device information storage unit 12a has items such as "device ID," "device destination information," and "server destination information."

[0044] "Device ID" indicates identification information for identifying the plant device 40, such as the identification number of the plant device 40. "Device destination information" indicates location information for identifying the location of the plant device 40 in a communication connection, such as the global IP address or cellular line telephone number of the plant device 40. "Server connection destination information" indicates location information for identifying the location of the receiving server 30 in a communication connection, such as the global IP address or URL of the receiving server 30.

[0045] 4 shows an example in which the plant device 40 identified by the device ID "Device A" has device destination information of "AAA.AA.AAA.A" and server destination information of "aaa.aa.aaa.a", and the plant device 40 identified by the device ID "Device C" has device destination information of "CCC.CC.CCC.C" and server destination information of "ccc.cc.ccc.c". The device information stored in the device information storage unit 12a is deleted as appropriate by a deletion unit 13d of the control unit 13, which will be described later.

[0046] (2-2-3. Control unit 13) The control unit 13 is responsible for overall control of the provisioning server 10. The control unit 13 has an acquisition unit 13a, a reception unit 13b, a notification unit 13c, and a deletion unit 13d. Here, the control unit 13 can be realized by, for example, an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0047] (2-2-3-1. Acquisition part 13a) The acquiring unit 13a acquires identification information of a device associated with destination information indicating the location of a destination to which data is to be transmitted from the device. For example, the acquiring unit 13a acquires equipment information in which the identification information of each of a plurality of devices is associated with destination information indicating the destination to which plant information of each of the plurality of devices is to be transmitted. The acquiring unit 13a also acquires identification information about a device that has issued a query and destination information associated with the identification information, which are transmitted from the application server 20. At this time, the acquiring unit 13a can also inquire of the application server 20 and acquire the identification information about the device that has issued the query and destination information associated with the identification information. The acquiring unit 13a also acquires, from each of the plurality of application servers 20, identification information about a device that acquires plant information that each application server 20 is to collect. Here, the device refers to, for example, a plant device 40 that includes a communication device and a sensor installed in the plant and transmits plant information (e.g., sensor values) acquired from the plant to a destination indicated by the notified destination information. In addition, equipment information is information that includes, for example, identification information of the plant equipment 40 such as a hardware identification number, destination information which is location information of the plant equipment 40 such as a global IP address or a cellular line telephone number, and transmission information which is location information of the receiving server 30 to which the plant equipment 40 sends data.

[0048] To explain a specific example, the acquisition unit 13a acquires the hardware identification number "Device A," the global IP address "AAA.AA.AAA.A" of the gateway device 40A, and the global IP address "aaa.aa.aaa.a" of the receiving server 30 as the device information of the gateway device 40A transmitted from the application server 20. The acquisition unit 13a stores the acquired device information in the device information storage unit 12a.

[0049] (2-2-3-2. Reception section 13b) The reception unit 13b receives, from a device, an inquiry about destination information indicating the location of a destination to which the device transmits data. For example, the reception unit 13b receives an inquiry about destination information from a device such as the plant equipment 40 that has been powered on and started up for the first time. Here, the first start-up refers to the start-up when the device is powered on for the first time after shipping, or the start-up when the device is powered on for the first time after initialization. Furthermore, the reception unit 13b receives an inquiry from a device that has set itself (the provisioning server 10) as the destination of the inquiry request at the time of shipping the device that is the source of the inquiry.

[0050] To explain a specific example, the reception unit 13b receives an inquiry about the destination information of the receiving server 30 based on the global IP address "XXX.XX.XXX.X" of the provisioning server 10, which was set at the shipping stage before the plant equipment 40, which has been powered on and started up for the first time, is installed in the plant.

[0051] (2-2-3-3. Notification section 13c) The notification unit 13c notifies the device that has requested the query of destination information associated with the identification information of the device that has requested the query. For example, the notification unit 13c notifies the device, such as the plant equipment 40, of the destination information when it is started up for the first time. At this time, the notification unit 13c determines whether the identification information of the device that has requested the query is registered in the identification information acquired from the application server 20, and if registered, notifies the device of the destination information. If not registered, the notification unit 13c outputs to the device a message that the device is not registered.

[0052] To explain a specific example, when notifying unit 13c receives an inquiry from gateway device 40A (identification number "Device A"), notifying unit 13c refers to device information storage unit 12a and, since identification number "Device A" is registered, transmits to gateway device 40A the global IP address "aaa.aa.aaa.a" of receiving server 30. On the other hand, when notifying unit 13c receives an inquiry from sensor device 40B (identification number "Device B"), notifying unit 13c refers to device information storage unit 12a and, since identification number "Device B" is not registered, transmits to sensor device 40B a warning that it is not registered.

[0053] (2-2-3-4. Deleted section 13d) The deletion unit 13d deletes, from the identification information stored in the device information storage unit 12a, the identification information of a device for which destination information has been notified, or the identification information for which a predetermined time has elapsed since it was acquired from the application server 20 by the acquisition unit 13a.

[0054] To explain a specific example, when deletion unit 13d receives an inquiry from gateway device 40A and transmits the global IP address “aaa.aa.aaa.a” of receiving server 30 to gateway device 40A, deletion unit 13d deletes from device information storage unit 12a the identification number “Device A” of gateway device 40A, the global IP address “AAA.AA.AAA.A” of gateway device 40A, and the global IP address “aaa.aa.aaa.a” of receiving server 30. Furthermore, when 10 days have passed since deletion unit 13d acquired the device information of sensor device 40B from application server 20, deletion unit 13d deletes from device information storage unit 12a the identification number “Device B” of sensor device 40B, the global IP address “BBB.BB.BBB.B” of sensor device 40B, and the global IP address “bbb.bb.bbb.b” of receiving server 30.

[0055] (2-3. Example of application server 20 configuration) An example of the configuration of the application server 20, which is an information management device, will be described with reference to Fig. 3. The application server 20 has a communication unit 21, a storage unit 22, and a control unit 23. The application server 20 may also have an input unit (e.g., a keyboard, a mouse, etc.) that accepts various operations from an engineer E who is the administrator of the device registration system 100, and a display unit (e.g., a liquid crystal display, etc.) that displays various information.

[0056] (2-3-1. Communications Department 21) The communication unit 21 controls data communication with other devices. For example, the communication unit 21 performs data communication with each communication device via a router, etc. The communication unit 21 can also perform data communication with an operator's terminal (not shown).

[0057] (2-3-2. Storage section 22) The storage unit 22 stores various types of information referenced by the control unit 23 when it operates and various types of information acquired when the control unit 23 operates. The storage unit 22 has an equipment information storage unit 22a and a plant information storage unit 22b. Here, the storage unit 22 can be realized by, for example, a semiconductor memory element such as RAM or flash memory, or a storage device such as a hard disk or optical disk. Note that, in the example of FIG. 3, the storage unit 22 is installed inside the application server 20, but it may be installed outside the application server 20, or multiple storage units may be installed.

[0058] (2-3-2-1.Device information storage section 22a) The device information storage unit 22a stores device information set by Engineer E, who is the administrator of the device registration system 100. An example of information stored in the device information storage unit 22a will now be described with reference to FIG. 5. FIG. 5 is a diagram showing an example of the device information storage unit 22a of the application server 20 according to the embodiment. In the example of FIG. 5, the device information storage unit 22a has items such as "Device ID," "Device Source Information," "Server Destination Information," and "Application Information."

[0059] "Device ID" indicates identification information for identifying the plant device 40, such as the identification number of the plant device 40. "Device source information" indicates location information for identifying the location of the plant device 40 in a communication connection, such as the global IP address or cellular line telephone number of the plant device 40. "Server destination information" indicates location information for identifying the location of the receiving server 30 in a communication connection, such as the global IP address or URL of the receiving server 30. "Application information" is information for identifying the application that processes the plant information collected from the plant device 40.

[0060] That is, Figure 5 shows an example in which, for plant equipment 40 identified by equipment ID "equipment A," the equipment source information is "AAA.AA.AAA.A," the server destination information is "aaa.aa.aaa.a," and the application information is "Application A," while for plant equipment 40 identified by equipment ID "equipment B," the equipment source information is "BBB.BB.BBB.B," the server destination information is "bbb.bb.bbb.b," and the application information is "Application B," and for plant equipment 40 identified by equipment ID "equipment C," the equipment source information is "CCC.CC.CCC.C," the server destination information is "ccc.cc.ccc.c," and the application information is "Application C."

[0061] (2-3-2-2. Plant information storage unit 22b) The plant information storage unit 22b stores device identification information and plant information collected by the plant equipment 40 and received via the receiving server 30. An example of information stored in the plant information storage unit 22b will now be described with reference to FIG. 6. FIG. 6 is a diagram illustrating an example of the plant information storage unit 22b of the application server 20 according to the embodiment. In the example of FIG. 6, the plant information storage unit 22b has items such as "equipment ID" and "sensor value."

[0062] The "device ID" indicates identification information for identifying the plant device 40, for example, the identification number of the plant device 40. The "sensor value" represents plant information, such as measurement data, control data, etc., collected by the plant device 40 in the plant.

[0063] That is, Figure 6 shows an example in which the sensor value for plant equipment 40 identified by equipment ID "equipment A" is "XXXXX", the sensor value for plant equipment 40 identified by equipment ID "equipment B" is "YYYYY", and the sensor value for plant equipment 40 identified by equipment ID "equipment C" is "ZZZZZ".

[0064] (2-3-3. Control unit 23) The control unit 23 is responsible for overall control of the application server 20. The control unit 23 has a receiving unit 23a and a transmitting unit 23b. Here, the control unit 23 can be realized by, for example, an electronic circuit such as a CPU or an MPU, or an integrated circuit such as an ASIC or an FPGA.

[0065] (2-3-3-1. Receiving unit 23a) The receiving unit 23a receives device identification information. For example, the receiving unit 23a receives identification information of the plant device 40 transmitted from the terminal device of engineer E. The receiving unit 23a also receives device information of the plant device 40 via a network map that is operated by engineer E to logically configure the network. At this time, the receiving unit 23a receives, as device information, identification information of the plant device 40 such as a hardware identification number, location information of the plant device 40 such as a global IP address and a cellular line telephone number, application information related to applications used by the plant device 40, and the like. Note that the destination information is set by the application server 20 based on the settings of engineer E.

[0066] To explain a specific example, the receiving unit 23a receives the hardware identification number "Device A," the global IP address "AAA.AA.AAA.A" of the gateway device 40A, the global IP address "aaa.aa.aaa.a" of the receiving server 30, and the application information "Application A" as the device information of the gateway device 40A set by the operation of the engineer E. The receiving unit 23a stores the received device information in the device information storage unit 22a.

[0067] The receiving unit 23a also receives data collected by the devices. For example, the receiving unit 23a receives plant information transmitted by the receiving server 30. To explain a specific example, the receiving unit 23a receives, as plant information, a sensor value "XXXXX" collected by the gateway device 40A, a sensor value "YYYYY" collected by the sensor device 40B, and a sensor value "ZZZZZ" collected by the control device 40C. The receiving unit 23a stores the received plant information in the plant information storage unit 22b.

[0068] (2-3-3-2. Transmitting unit 23b) The transmitter 23d transmits, to the information providing device, destination information indicating the destination of the data, as well as identification information of the device associated with the destination information. For example, the transmitter 23d transmits, to the provisioning server 10, device information in which the identification information of the plant device 40 is associated with the destination information of the receiving server 30.

[0069] To explain a specific example, the transmitter 23b transmits to the provisioning server 10 the device information of the gateway device 40A set by the operation of engineer E, including the hardware identification number "Device A," the global IP address of the gateway device 40A "AAA.AA.AAA.A," and the global IP address of the receiving server 30 "aaa.aa.aaa.a."

[0070] The transmitter 23b also issues an instruction to initialize the device by causing the device to delete destination information stored in the device. For example, the transmitter 23b issues an initialization instruction to the plant device 40 that has been started up for the first time and that stores the global IP address of the provisioning server 10 as destination information, causing the plant device 40 to delete the global IP address stored therein.

[0071] (2-4. Example of configuration of receiving server 30) An example of the configuration of the receiving server 30, which is an information collection device, will be described with reference to Fig. 3. The receiving server 30 has a communication unit 31 and a control unit 32. The receiving server 30 may also have an input unit (e.g., a keyboard, a mouse, etc.) that accepts various operations from an engineer E who is the administrator of the device registration system 100, and a display unit (e.g., a liquid crystal display, etc.) that displays various information.

[0072] (2-4-1. Communications Department 31) The communication unit 31 controls data communication with other devices. For example, the communication unit 31 performs data communication with each communication device via a router or the like. The communication unit 31 can also perform data communication with an operator's terminal (not shown).

[0073] (2-4-2. Control unit 32) The control unit 32 is responsible for overall control of the receiving server 30. The control unit 32 has a receiving unit 32a and a transmitting unit 32b. Here, the control unit 32 can be realized by, for example, an electronic circuit such as a CPU or MPU, or an integrated circuit such as an ASIC or FPGA.

[0074] (2-4-2-1. Receiving unit 31a) The receiving unit 31a receives data and identification information collected by the devices. For example, the receiving unit 31a receives plant information collected by the plant device 40. To explain a specific example, the receiving unit 31a receives, as plant information, a sensor value "XXXXX" collected by the gateway device 40A, a sensor value "YYYYY" collected by the sensor device 40B, and a sensor value "ZZZZZ" collected by the control device 40C. The receiving unit 31a may store the received plant information in a storage unit (not shown).

[0075] (2-4-2-2. Transmitting unit 31b) The transmitter 31b transmits data collected by the devices. For example, the receiver 31a transmits plant information and identification information collected by the plant device 40 to the application server 20. To explain a specific example, the transmitter 31b transmits, as plant information, the sensor value "XXXXX" collected by the gateway device 40A, the sensor value "YYYYY" collected by the sensor device 40B, and the sensor value "ZZZZZ" collected by the control device 40C to the application server 20.

[0076] (2-5. Configuration example of plant device 40) An example configuration of the plant device 40 will be described with reference to Fig. 3. For example, the plant device 40 includes a gateway device 40A that is a communication device, a sensor device 40B that is a measurement device, and a control device 40C that controls the plant devices. The plant devices 40 (40A, 40B, 40C) have collection units 41 (41A, 41B, 41C) and transmission / reception units 42 (42A, 42B, 42C).

[0077] (2-5-1. Collection Department 41) The collection unit 41 collects data. For example, the collection unit 41 collects plant information, which is data on a plant.

[0078] (2-5-2. Transmitter / receiver 42) The transmitter / receiver 42 transmits data. For example, the transmitter / receiver 42 transmits the plant information collected by the collector 41 to the receiving server 30. The transmitter / receiver 42 also transmits a query for destination information indicating the location of the destination to which the device will transmit data. For example, when the power is turned on and the device is started up for the first time, the transmitter / receiver 42 refers to the global IP address of the provisioning server 10 that identifies the destination of the query set at the time of shipment, and transmits a query for the global IP address of the receiving server 30 to the identified provisioning server 10.

[0079] The transmitter / receiver 42 also receives data. For example, the transmitter / receiver 42 receives the global IP address of the receiving server 30 from the provisioning server 10. The transmitter / receiver 42 also receives a warning from the provisioning server 10 that the plant device 40 is not registered.

[0080] 3. Processing Flow of Device Registration System 100 The processing flow of the device registration system 100 according to the first embodiment will be described with reference to Fig. 7. Fig. 7 is a sequence diagram showing an example of the flow of the device registration processing according to the embodiment. Note that the processing of steps S101 to S111 below may be executed in a different order. Also, some of the processing of steps S101 to S111 below may be omitted.

[0081] (3-1. Device information setting process) Engineer E, who is the administrator of the device registration system 100, sets device information in the application server 20 (step S101). For example, engineer E sets identification information of the plant device 40, location information of the plant device 40, application information, etc. At this time, the application server 20 sets destination information based on the settings of engineer E.

[0082] (3-2. Device information registration process) The application server 20 transmits the device information and destination information to the provisioning server 10 (step S102). Then, the provisioning server 10 stores the transmitted device information in the storage unit 12 (step S103). For example, the provisioning server 10 stores identification information of the plant device 40, location information of the plant device 40, etc.

[0083] (3-3. Connection destination inquiry processing) Based on the location information of the provisioning server 10 that was installed at the time of shipment, the plant device 40 sends an inquiry about the receiving server 30 to which the plant device 40 is connected to the provisioning server 10 (step S104). At this time, the plant device 40 sends the identification information of the plant device 40 to the provisioning server 10 together with the inquiry about the communication connection destination.

[0084] (3-4. Connection destination response processing) The provisioning server 10 searches for a connection destination for the plant device 40 based on the device information (step S105). Next, if the device information acquired from the application server 20 based on the identification information acquired in step S105 is registered and the provisioning server 10 has permitted the plant device 40, it transmits destination information of the receiving server 30, which is the data transmission destination, to the plant device 40 (step S106). On the other hand, if the device information acquired from the application server 20 based on the identification information acquired in step S105 is not registered and the provisioning server 10 has not permitted the plant device 40, it transmits a warning to the plant device 40 that it has not been permitted.

[0085] (3-5. Device information deletion process) The provisioning server 10 deletes the device information of the plant device 40 (step S107). For example, the provisioning server 10 deletes the device information of the plant device 40 to which the destination information has been transmitted. Furthermore, the provisioning server 10 deletes device information for which a predetermined period has elapsed since the device information was acquired.

[0086] (3-6. Plant information collection and processing) The plant device 40 collects plant information (step S108), and transmits the plant information and identification information to the receiving server 30, which is the communication connection destination (step S109).

[0087] (3-7. Plant information registration process) The receiving server 30 transmits the received plant information and identification information to the application server 20 (step S110). Then, the application server 20 stores the transmitted plant information in the storage unit 22 (step S111) and ends the process.

[0088] 4. Effects of the embodiment Finally, the effects of the embodiment will be described below: Effects 1 to 9 corresponding to the processing according to the embodiment will be described below.

[0089] (4-1. Effect 1) First, in the process according to the embodiment described above, the provisioning server 10 acquires identification information of a device associated with destination information indicating the location of a destination to which data is to be sent from the device, accepts an inquiry about destination information from the device, and notifies the device that has requested the inquiry of the destination information associated with the identification information of the device. Therefore, in this process, communication settings for the device can be easily performed.

[0090] (4-2. Effect 2) Second, in the process according to the embodiment described above, the provisioning server 10 receives an inquiry about destination information from a device that has been powered on and booted up for the first time, and notifies the device of the destination information when booted up for the first time. Therefore, in this process, the data destination of the device is automatically set, thereby easily executing communication settings for the device.

[0091] (4-3. Effect 3) Third, in the process according to the embodiment described above, the provisioning server 10 acquires identification information relating to the device that is the request source of the inquiry and destination information associated with the identification information, which are transmitted from the application server 20. Therefore, in this process, the data destination is automatically set for each device corresponding to the application, thereby easily executing communication settings for the device.

[0092] (4-4. Effect 4) Fourth, in the process according to the embodiment described above, the provisioning server 10 queries the application server 20 and acquires identification information related to the device that has requested the query and destination information associated with the identification information. Therefore, in this process, the data destination is automatically inquired for each device corresponding to the application, thereby easily setting up communication for the device.

[0093] (4-5. Effect 5) Fifth, in the process according to the embodiment described above, the provisioning server 10 receives an inquiry from a device that has been set as the destination of the inquiry at the time of shipping the device that is the source of the inquiry. Therefore, in this process, it is not necessary to perform individual settings for the same device, and communication settings for the device can be easily performed.

[0094] (4-6. Effect 6) Sixth, in the process according to the embodiment described above, the provisioning server 10 determines whether the identification information of the device that has made the inquiry is registered in the identification information acquired from the application server 20, and if it is registered, notifies the device of the destination information, and if it is not registered, outputs to the device a message that it is unregistered. Therefore, this process reduces the risk of information leakage due to incorrect settings and makes it easy to set up communication settings for the device.

[0095] (4-7. Effect 7) Seventh, in the process according to the embodiment described above, the provisioning server 10 stores the acquired identification information and deletes, from the stored identification information, the identification information of the device for which the destination information has been notified or the identification information for which a predetermined time has passed since acquisition. Therefore, in this process, even if the settings are changed, the device information can be centrally managed, and the communication settings of the device can be easily executed.

[0096] (4-8. Effect 8) Eighth, in the process according to the above-described embodiment, the device is a plant device that transmits the plant information acquired from the plant to the destination indicated by the notified destination information. Therefore, in this process, communication settings of the plant device can be easily performed.

[0097] (4-9. Effect 9) Ninth, in the process according to the above-described embodiment, the application server 20 issues a command to initialize the device by causing the device to delete the destination information stored in the device. Therefore, in this process, communication settings can be easily performed even when device reconfiguration is required.

[0098] 〔system〕 The information including the processing procedures, control procedures, specific names, various data and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified.

[0099] Furthermore, the components of each device shown in the figure are functional concepts and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown. In other words, all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0100] Furthermore, all or any part of the processing functions performed by each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware using wired logic.

[0101] [Hardware] Next, an example of the hardware configuration of the provisioning server 10, which is an information processing device, will be described. Note that other devices such as the application server 20 and the receiving server 30 may also have a similar hardware configuration. FIG. 8 is a diagram illustrating an example of the hardware configuration. As shown in FIG. 8, the provisioning server 10 includes a communication device 10a, an HDD (Hard Disk Drive) 10b, a memory 10c, and a processor 10d. The components shown in FIG. 8 are interconnected by a bus or the like.

[0102] The communication device 10a is a network interface card or the like, and communicates with other servers. The HDD 10b stores programs and DBs that operate the functions shown in FIG.

[0103] The processor 10d reads out a program that executes the same processes as the respective processing units shown in Fig. 3 from the HDD 10b or the like and loads it into the memory 10c, thereby operating a process that executes the respective functions described in Fig. 3 or the like. For example, this process executes the same functions as the respective processing units of the provisioning server 10. Specifically, the processor 10d reads out a program that has the same functions as the acquisition unit 13a, the reception unit 13b, the notification unit 13c, the deletion unit 13d, or the like from the HDD 10b or the like. Then, the processor 10d executes a process that executes the same processes as the acquisition unit 13a, the reception unit 13b, the notification unit 13c, the deletion unit 13d, or the like.

[0104] In this way, the provisioning server 10 operates as a device that executes various processing methods by reading and executing programs. The provisioning server 10 can also realize functions similar to those of the above-described embodiment by reading the programs from a recording medium using a media reader and executing the read programs. Note that the programs in these other embodiments are not limited to those executed by the provisioning server 10. For example, the present invention can also be applied in the same way to cases where other computers or servers execute programs, or where these execute programs in cooperation with each other.

[0105] This program can be distributed via a network such as the Internet. In addition, this program can be recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, a magneto-optical disk (MO), or a digital versatile disk (DVD), and can be executed by being read from the recording medium by a computer. [Explanation of symbols]

[0106] 10 Provisioning Server 11 Communications Department 12 Storage section 12a Device information storage section 13 Control Unit 13a Acquisition part 13b Reception 13c Notification Department 13d Deleted section 20 Application Server 21 Communications Department 22 Memory section 22a Device information storage section 22b Plant information storage unit 23 Control Unit 23a Receiving section 23b Transmitter 30 Receiving Server 31 Communications Department 32 Control Unit 32a Receiver 32b Transmitter 40 40A 40B 40C Plant equipment 41 41A 41B 41C Collection Section 42 42A 42B 42C Transmitter / Receiver 100 Device Registration System

Claims

1. an acquisition unit that acquires identification information of the device associated with destination information indicating the location of a destination to which data is to be sent from the device; a reception unit that receives an inquiry about the destination information from the device; a notification unit that notifies the device that is the request source of the inquiry of the destination information associated with identification information of the device that is the request source of the inquiry; a storage unit that stores the identification information acquired by the acquisition unit; a deletion unit that deletes, from the identification information stored in the storage unit, the identification information of the device to which the destination information has been notified, or the identification information for which a predetermined time has elapsed since it was acquired by the acquisition unit; An information providing device comprising:

2. The reception unit: receiving an inquiry about the destination information from the device that has been powered on and started up for the first time; The notification unit notifying the device of the destination information when the device is started for the first time; The information providing device according to claim 1 .

3. The acquisition unit acquiring the identification information relating to the device that is the source of the inquiry and the destination information associated with the identification information, the identification information being transmitted from the information management device; The information providing device according to claim 1 .

4. The acquisition unit: making an inquiry to an information management device, and acquiring the identification information relating to the device that has made the inquiry and the destination information associated with the identification information; The information providing device according to claim 1 .

5. The reception unit: receiving the inquiry from the device that has been set as a request destination of the inquiry at the time of shipping of the device that is the request source of the inquiry; The information providing device according to any one of claims 1 to 4.

6. The notification unit: determining whether or not identification information of the device that is the source of the inquiry is registered in the identification information acquired from the information management device; If the destination information is registered, the destination information is notified to the device, and if the destination information is not registered, a message indicating that the destination information is not registered is output to the device. The information providing device according to claim 3 .

7. The device comprises: a plant device that transmits plant information acquired from the plant to a destination indicated by the notified destination information; The information providing device according to claim 1 .

8. A computer comprising: acquiring identification information of the device associated with destination information indicating the location of a destination to which data is to be sent from the device; receiving an inquiry about the destination information from the device; notifying the device that is the request source of the inquiry of the destination information associated with identification information of the device that is the request source of the inquiry; storing the acquired identification information; Among the identification information to be stored, the identification information of the device that notified the destination information or the identification information for which a predetermined time has elapsed since acquisition is deleted. An information providing program that executes processing.

9. A device registration system including an information management device that performs specified processing on data received from a device, and an information providing device, The information management device a transmitting unit that transmits, to the information providing device, destination information indicating a destination of the data, together with identification information of the device associated with the destination information; The information providing device an acquisition unit that acquires the identification information together with the destination information from the information management device; a reception unit that receives an inquiry about the destination information from the device; a notification unit that notifies the device that is the request source of the inquiry of the destination information associated with identification information of the device that is the request source of the inquiry; a storage unit that stores the identification information acquired by the acquisition unit; a deletion unit that deletes, from the identification information stored in the storage unit, the identification information of the device to which the destination information has been notified, or the identification information for which a predetermined time has elapsed since it was acquired by the acquisition unit; A device registration system comprising:

10. The information management device comprises: notifying the device of an instruction to initialize the device by causing the device to delete the destination information stored in the device; The device registration system according to claim 9 .

11. A device registration method executed by a device registration system including an information management device that performs specified processing on data received from a device and an information providing device, The information management device a process of transmitting, to the information providing device, destination information indicating a destination of the data, together with identification information of the device associated with the destination information; The information providing device acquiring the identification information from the information management device; receiving an inquiry about the destination information from the device; notifying the device that is the request source of the inquiry of the destination information associated with identification information of the device that is the request source of the inquiry; storing the acquired identification information; a process of deleting, from the identification information to be stored, the identification information of the device that notified the destination information or the identification information for which a predetermined time has elapsed since acquisition; A device registration method that performs the above.

Images