Management device, management system, and management method

Abstract

To set a communication path suitable for a request.SOLUTION: A management device: identifies a first communication path requirement template corresponding to first communication path requirements of a first application module and a second communication path requirement template corresponding to second communication path requirements of a second application module; determines a usable communication module included in the first communication path requirement template as a first communication module and a usable communication module included in the second communication path requirement template as a second communication module; determines the first communication module arrangement destination as a first arrangement destination and the second communication module arrangement destination as a second arrangement destination; arranges the first application module and the first communication module in the first arrangement destination; and arranges the second application module and the second communication module in the second arrangement destination and sets a communication path.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] The present invention relates to a management device, a management system, and a management method for managing modules.

Background Art

[0002] Fifth-generation mobile communication (5G) has enabled low-latency, wide-bandwidth, and highly reliable wireless communication. Under such circumstances, by introducing a low-latency, wide-bandwidth, and highly reliable wireless network characteristic of 5G, it becomes possible to integrate and abolish various existing networks in a private network, and it is expected that the costs of network construction and operation can be reduced. Particularly in a system where multiple networks coexist, such as a system including OT (Operation Technology), the effect is remarkable. 5G is being considered for application in various fields. One example of its application destination is the on-site network in manufacturing and logistics.

[0003] In the manufacturing and logistics sites, it is desired to introduce new DX (Digital Transformation) solutions such as real-time work instructions utilizing high-definition video analysis, equipment control enabling humans and robots to cooperate, and remote operation with a sense of presence, in order to address labor shortages, improve productivity, and improve quality.

[0004] On the other hand, by introducing local 5G or public 5G and a general-purpose edge processing server (also called MEC: Multi-access Edge Computing) to integrate and aggregate the on-site network into a wireless network, it is being considered to realize highly reliable and flexible service provision, including feedback control in a cyber-physical system.

[0005] As a result, it can be expected that applications related to business can be flexibly and quickly changed due to factors such as supply and demand fluctuations in the supply chain, process changes due to personnel adjustments within the company, and fine-tuning of operations caused by changes in the on-site environment. Here, the application referred to is a program for achieving a certain purpose by combining a plurality of modules that provide some kind of data input / output service. Changing the configuration of the application means arbitrarily changing the combination and deployment positions of these multiple modules. The change in the application configuration is triggered by the above-mentioned factors and is implemented according to instructions from the cloud. The network connecting these modules is required to provide highly reliable connectivity that follows the configuration change.

[0006] Patent Document 1 below discloses a network requirement generation system that generates network requirements applied to services. This network requirement generation system is composed of a computer having an arithmetic device that executes predetermined arithmetic processing to realize each of the following functional units, and a storage device accessible by the arithmetic device, and includes a service requirement acquisition unit that acquires service requirements input by a user, a service requirement analysis unit that analyzes the input service requirements to generate network requirements, and a network requirement control unit that creates network setting contents for a control device that constructs a network from the generated network requirements.

[0007] The following Patent Document 2 discloses a network gateway for routing data flows through a plurality of network connections. This network gateway includes a plurality of network interfaces including a first network interface for transmitting data through a plurality of network connections, and at least one processor configured to transmit sequential bursts of packets through the first network interface, generate a bandwidth of the first network interface based on a timestamp recorded when a packet within the sequential burst of packets is received at a receiving node and the size of the packet, and route the data flow of sequential packets through a plurality of network connections based on the generated bandwidth of the first network interface.

Prior Art Documents

Patent Documents

[0008]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0009] Problems in wirelessly networking a field network that meets the strict application requirements demanded by an application in OT will be described by taking a factory network as an example. In the current factory network, a plurality of networks such as a control network, an information network, and an OA (Office Automation) network coexist according to the requirements of operations. Also, for each application, requirements such as communication delay and communication operation rate for control devices are diverse.

[0010] By wirelessly networking the factory network, while the system becomes more flexible, the dependence on system engineers increases. If system engineers manually configure or construct the system and network to meet these requirements, they cannot keep up with supply and demand fluctuations and changes in the on-site environment, and furthermore, the business cannot scale either.

[0011] Also, in the network requirement generation system disclosed in Patent Document 1, only the setting of network devices is generated, and the provision of highly reliable communication connectivity as required by the application is not disclosed. Further, in the network gateway disclosed in Patent Document 2, a dynamic and flexible introduction method to the system is not disclosed.

[0012] An object of the present invention is to realize the setting of a communication path suitable for requirements.

Means for Solving the Problems

[0013] A management device which is an aspect of the invention disclosed in the present application is a management device capable of communicating with a computer cluster, and has a processor that executes a program and a storage device that stores the program. The storage device stores an application module group, a communication module group, a communication path requirement which is a condition required for a communication path between an application module in the application module group and another application module which is a communication partner of the application module, a communication path requirement target that designates the other application module, a communication path requirement definition that defines the type and conditions of communication in the communication path requirement, a usable communication module definition that defines a communication module usable for the communication path requirement definition, a usable setting definition that defines a communication setting usable for the communication path requirement definition, and a communication path requirement template group constituted by these. The processor specifies a first communication path requirement template corresponding to a first communication path requirement of a first application module from the communication path requirement template group, and specifies a second communication path requirement template corresponding to a second communication path requirement of a second application module designated as a communication partner of the first application module in the communication path requirement target from the communication path requirement template group (specification process); determines the usable communication module included in the first communication path requirement template as a first communication module usable by the first application module, and determines the usable communication module included in the second communication path requirement template as a second communication module usable by the second application module (communication module determination process); determines the placement destination of the first communication module as a first placement destination of the first application module in the computer cluster, and determines the placement destination of the second communication module as a second placement destination of the second application module in the computer cluster (communication module placement destination determination process); and places the first application module and the first communication module at the first placement destination, and places the second application module and the second communication module at the second placement destination (placement process).A communication path setting process for communicably connecting between the first application module and the second application module via the first communication module and the second communication module is executed.

Advantages of the Invention

[0014] According to a typical embodiment of the present invention, it is possible to realize setting of a communication path suitable for requirements. Problems, configurations, and effects other than those described above will be clarified by the description of the following embodiments.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11A

Figure 11B

Figure 11C

Figure 11D

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17A

Figure 17B

Figure 18

Figure 19

DETAILED DESCRIPTION OF THE INVENTION

[0016] <Edge Operation Management System> FIG. 1 is a block diagram showing a system configuration example of an edge operation management system. The edge operation management system 1 includes a cloud 101 and a factory system 5. The cloud 101 and the factory system 5 are communicably connected via a public network 100. Also, the cloud 101 and the factory system 5 are communicably connected to a public 5G network 40 via the public network 100.

[0017] The public 5G network 40 includes a base station 41, an edge processing server 24E2, and a mobile network management server 44. The base station 41, the edge processing server 24E2, and the mobile network management server 44 are communicably connected via a mobile core network 43. The mobile network management server 44 is communicably connected to the public network 100. The mobile network management server 44 manages communications between the public 5G network 40 and an IoT gateway 13 outside the public 5G network 40, a local 5G network 20, a factory LAN (Local Area Network) 32, and the cloud 101. Also, the base station 41 is communicably connected to the mobile core network 43 via an MBH (Mobile Backhaul) 42.

[0018] The cloud 101 includes an orchestration server 102 and a cloud processing server 24C1. The orchestration server 102 is a management device that controls the cloud processing server 24C1, the edge processing server 24E2, the edge processing server 24E3, and the edge processing server 24E4 to integrally set up a virtualized environment or automate the operation of the virtualized environment.

[0019] The factory system 5 includes an edge processing server 24E3, a factory LAN 32, an existing factory network 34, a factory LAN management server 35, a local 5G network 20, a wireless LAN access point 31, and a terminal 15. The edge processing server 24E3, a firewall 33, the existing factory network 34, the factory LAN management server 35, the local 5G network 20, and the wireless LAN access point 31 are communicably connected via the factory LAN 32. The factory LAN management server 35 manages communications between the factory LAN 32 and an IoT gateway 13 outside the factory LAN 32, the local 5G network 20, a cloud 101, and a public 5G network 40.

[0020] The local 5G network 20 includes an edge processing server 24E4, a mobile core device 23, a base station 21, and an MBH 22. The edge processing server 24E4, the mobile core device 23, and the base station 21 are communicably connected via the MBH 22. The mobile core device 23 is a general term for devices that accommodate mobile communications such as LTE (Long Term Evolution) and 5G, and is also referred to as an EPC (Evolved Packet Core) or 5GC (5G Core). The mobile core device 23 manages communications between the local 5G network 20 and an IoT gateway 13 outside the local 5G network 20, the factory LAN 32, a cloud 101, and a public 5G network 40.

[0021] The terminal 15 is a computer that includes a camera 10, a control device 11, a bus 12, and an IoT gateway 13. The camera 10, the control device 11, and the IoT gateway 13 are communicably connected via the bus 12. Also, the terminal 15 is communicably connected to the base station 21, the wireless LAN access point 31, and a base station 41 via the IoT gateway 13.

[0022] The camera 10 images workers and working machines such as conveyors within the factory system 5. The control device 11 is connected to the working machine to be controlled, and provides control data such as the rotation speed of a roller to the working machine to control the operation of the working machine.

[0023] One terminal 15 is provided for the factory system 5. When there are multiple production lines in the factory system 5, the terminal 15 is provided for each production line.

[0024] In addition, when the edge processing servers 24E2, 24E3, and 24E4 are not distinguished, they are simply denoted as the edge processing server 24E. Also, when the cloud processing server 24C1, the edge processing servers 24E2, 24E3, and 24E4 are not distinguished, they are simply denoted as the processing server 24. The processing server 24 is a computer.

[0025] <Hardware configuration example of computers (orchestration server 102, processing server 24, IoT gateway 13)> FIG. 2 is a block diagram showing a hardware configuration example of a computer. The computer 200 includes a processor 201, a storage device 202, an input device 203, an output device 204, and a communication interface (communication IF) 205. The processor 201, the storage device 202, the input device 203, the output device 204, and the communication IF 205 are connected by a bus 206. The processor 201 controls the computer 200. The storage device 202 serves as a working area for the processor 201. Also, the storage device 202 is a non-temporary or temporary recording medium that stores various programs and data. Examples of the storage device 202 include a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), and a flash memory. The input device 203 inputs data. Examples of the input device 203 include a keyboard, a mouse, a touch panel, a numeric keypad, a scanner, a microphone, and a sensor. The output device 204 outputs data. Examples of the output device 204 include a display, a printer, and a speaker. The communication IF 205 connects to a network and transmits and receives data. Hereinafter, embodiments according to the present invention will be described.

[0026] <Functional Configuration Example of Orchestration Server 102> FIG. 3 is a block diagram showing a functional configuration example of an orchestration server 102. The orchestration server 102 includes a metric information collection unit 300, an application requirement acquisition unit 301, a module placement determination unit 302, a communication path requirement interpretation unit 303, a module deployment control unit 304, an E2E network quality control unit 305, a resource management table 500, an application requirement table 600, an application management table 700, a communication module repository 800, and a communication path requirement template table 900.

[0027] The metric information collection unit 300, the application requirement acquisition unit 301, the module placement determination unit 302, the communication path requirement interpretation unit 303, the module deployment control unit 304, and the E2E network quality control unit 305 are specifically realized, for example, by causing a processor 201 to execute a program stored in a storage device 202 shown in FIG. 2.

[0028] The metric information collection unit 300, the application requirement acquisition unit 301, the module placement determination unit 302, the communication path requirement interpretation unit 303, the module deployment control unit 304, and the E2E network quality control unit 305 are stored in the storage device 202.

[0029] The metric information collection unit 300 collects metric information from the processing server 24 and the IoT gateway 13. The metric information is information regarding the distance of a path (route) to a communication partner, and specifically, for example, delay ([ms]), jitter ([ms]), bandwidth ([Mbps]), and PER (Packet Error Rate). The metric information collection unit 300 may collect and update the metric information at regular time intervals.

[0030] The application requirement acquisition unit 301 receives the input of application requirements by receiving from an external computer or by the operation of an operator. The application requirements are the conditions required for the application. The application is a group of software modules including an application module and a communication module. The application is held in the cloud 101. When the application module and the communication module are not distinguished, they are simply referred to as modules.

[0031] The application module is a software module that processes data. For example, there are a learning module that executes machine learning, a data collection module that collects data, a video analysis module that analyzes video, a camera control module that controls a camera, and a control device control module that controls a control device.

[0032] The communication module is a module that transmits and receives data. For example, there are a broadband communication module that performs packet replication transfer in multiple paths, a high-reliability communication module that performs aggregation of multiple paths, a jitter reduction communication module that absorbs packet jitter, and a WAF communication module that functions as a WAF (Web Application Firewall).

[0033] The application requirements are defined for each module and include conditions such as where each module is located, what communication path requirements are, and with whom to communicate. The communication path requirements are the conditions required for the communication path and include communication types such as control communication and media communication and their constraint conditions. The communication path is the communication route between a module and its communication partner.

[0034] The module placement determination unit 302 determines the placement destination of the module. The placement destinations include, for example, ANY (anywhere is fine), a closed area, and a field area. The closed area is within the device where the module is placed, and the field area indicates that the device where the module is placed can communicate with multiple networks.

[0035] The communication path requirement interpretation unit 303 interprets the communication path requirements. Specifically, for example, the communication path requirement interpretation unit 303 specifies a communication path requirement template corresponding to the communication path requirements of the module placement destination from the communication path requirement template table 900, and determines a communication module corresponding to the specified communication path requirement template.

[0036] The module deployment control unit 304 controls to deploy the module to the module placement destination determined by the module placement determination unit 302. Specifically, for example, the module deployment control unit 304 transmits the module to the module placement destination determined by the module placement determination unit 302.

[0037] The E2E network quality control unit 305 controls the quality of the network existing between the module placed at the placement destination and its communication partner, that is, END-TO-END. Specifically, for example, the E2E network quality control unit 305 executes QoS (Quality of Service) setting and communication path setting. QoS is an existing technology that adjusts the order and amount of data passing through to enable stable use of services on the network.

[0038] <Application> FIG. 4 is an explanatory diagram showing an example of an application. The application 400 includes a camera control module 401, a control device control module 402, a data collection module 403, a video analysis module 404, a primary learning module 405, and a secondary learning module 406.

[0039] The camera control module 401 instructs the camera 10 to capture images and receives the video data captured by the camera 10. During the learning of the primary learning model, the camera control module 401 transmits the video data to the data collection module 403, and during prediction using the primary learning model, it transmits the video data to the video analysis module.

[0040] The control device control module 402 acquires the control data set for the control target from the control device. During the learning of the primary learning model, the control device control module 402 transmits the control data to the data collection module 403, and during prediction using the primary learning model, it transmits the control data to the video analysis module 404.

[0041] In addition, the control device control module 402 transfers the real-time feedback control data from the video analysis module 404 to the control device. The control device 11 controls the control target based on the real-time feedback control data. Specifically, for example, when the real-time feedback control data indicates that the video data and control data obtained by video analysis are normal operations, the control device 11 continues to control the control target as it is. On the other hand, when the real-time feedback control data indicates that the video data and control data obtained by video analysis are abnormal operations that deviate, the control data is corrected. For example, when the conveyor's transport speed exceeds the upper limit speed, the control device 11 executes control to reduce the rotation speed of the roller.

[0042] The data collection module 403 associates the video data and the control data with time and transfers them to the primary learning module as learning data.

[0043] The one-shot learning module 405 performs machine learning using the learning data from the data collection module and the correct answer data for each preset time, and generates a learning model. The correct answer data is, for example, an identification label that identifies whether the work at that time is normal work or deviated work. The one-shot learning module 405 transmits the generated one-shot learning model to the two-shot learning module 406 and the video analysis module 404.

[0044] The video analysis module 404 performs video analysis using the one-shot learning model. The video analysis module 404 inputs the video data from the camera control module 401 and the control data from the control device control module 402 into the one-shot learning model, calculates a prediction result indicating whether the work at that time is normal work or deviated work, and transmits it as real-time feedback control data to the control device control module 402.

[0045] The two-shot learning module 406 acquires the one-shot learning model from the one-shot learning module 405 and generates a two-shot learning module. Specifically, for example, the two-shot learning module 406 extracts only the feature quantities common to the factory system group including the factory system 5 and other factory systems, reconstructs the one-shot learning model, and generates it as a two-shot learning model as know-how.

[0046] Next, the table group in the orchestration server 102 will be specifically described.

[0047] FIG. 5 is an explanatory diagram showing an example of the resource management table 500. The resource management table 500 is a table that manages the computer resources available to the terminal 15. The resource management table 500 has, as fields, a management identifier 501, an IoT device 502, a possessed interface 503, available computer resources 504, a location 505, and metric information 506.

[0048] The management identifier 501 is an identifier for managing the computer resources available to the IoT device 502, and corresponds one-to-one with the IoT device 502. The IoT device 502 defines the IoT devices within the terminal 15. In the example of the terminal 15, the IoT device 502 is the IoT gateway 13.

[0049] The owned interface 503 is a communication interface owned by the IoT device 502. In the example of the terminal 15, the IoT gateway 13 has an interface connectable to the base station 21 of the local 5G network 20, the wireless LAN base station 31, and the public 5G network 40.

[0050] The available computer resources 504 are computer resources that can communicate with the IoT device 502 and are available to the application, such as the cloud processing server 24C1, the edge processing server 24E2, the edge processing server 24E3, and the edge processing server 24E4.

[0051] The location 505 indicates the location of the computer resources where the available computer resources 504 exist. Note that since the resource management table 500 defines entries in units of the management identifier 501 indicating the IoT gateway, although not shown in the figure, the location 50 of the IoT device 502 5 is also held.

[0052] Metric information 506 is information regarding the communication between the IoT device 502 and the available computing resources 504, and has, as sub-fields, a local 5G connection 507, a Wi-Fi connection 508, and a public 5G connection 509. Metric information 506 is recorded for each of the local 5G connection 507, the Wi-Fi connection 508, and the public 5G connection 509. As described above, the metric information 506 is collected by the metric information collection unit 300.

[0053] Figure 6 is an explanatory diagram showing an example of the application requirement table 600. The application requirement table 600 is a table that defines application requirements. The application requirement table 600 has, as fields, an application identifier 601, an application module 602, a placement location 603, a communication path requirement target 604, a communication path requirement 605, and a communication path direction 606.

[0054] The application identifier 601 is identification information that uniquely identifies the application 400. In this example, "App-A" is the application identifier 601 of the application 400.

[0055] The application module 602 is a software module that constitutes the application specified by the application identifier 601. In the example of the application 400, the application module 602 includes a camera control module 401, a control device control module 402, a data collection module 403, a video analysis module 404, a primary learning module 405, and a secondary learning module 406.

[0056] The placement location 603 defines the locations where the application module 602 can be placed. The communication path requirement target 604 is the target that communicates with the application module 602 according to the communication path requirement 605, that is, the destination module when the application module 602 is the source and module. The communication path requirement 605 is the condition required for the communication path between the application modules 602, and includes communication types such as control communication and media communication and their constraint conditions.

[0057] The communication path direction 606 defines the direction of the communication path, either forward or reverse, for an entry where the communication path requirement 605 exists. The forward direction indicates the transmission direction from the application module 602 to the communication path requirement target 604, and the reverse direction indicates the data transmission direction from the communication path requirement target 604 to the application module 602.

[0058] FIG. 7 is an explanatory diagram showing an example of an application management table 700. The application management table 700 is a table that manages the state after the application is placed. The application management table 700 has, as fields, a management identifier 501, an application identifier 601, a classification 701, a module 702, a module address 703, and a placement location address 704.

[0059] Classification 701 is a classification that divides the applications specified by the application identifier 601 by type. In the example of the application 400, as the classification 701, it has an application module and a communication module. The camera control module 401, the control device control module 402, the data collection module 403, the video analysis module 404, the primary learning module 405, and the secondary learning module 406 are classified as the application module. The broadband communication module and the high-reliability communication module are classified as the communication module.

[0060] Module 702 details each of the application module 602 and the communication module classified by the classification 701.

[0061] The module address 703 is the IP address within the destination of the module 702. The module address 703 is assigned at the destination of the module 702. The placement location address 704 is the address of the destination of the module 702. In the example of FIG. 7, "C1.cloud.jp" is the address of the cloud processing server 24C1. "E3.fab.local" is the address of the edge processing server 24E3. "E4.mobile.local" is the address of the edge processing server 24E4. "IGW1111" is the address of the terminal 15.

[0062] FIG. 8 is an explanatory diagram showing an example of the communication module repository 800. The communication module repository 800 defines information related to the communication module. The communication module repository 800 has, as fields, a communication module name 801, an explanation 802, a provision form 803, a communication form 804, a configuration 805, and a storage destination 806.

[0063] The communication module name 801 is the name of the communication module classified by the classification 701. The description indicates the meaning of the communication module. The provision form 803 indicates the form in which the communication module is provided. The communication form 804 indicates the form in which the communication module communicates. The configuration 805 indicates the method by which the communication module communicates. The storage destination 806 indicates the address where the communication module is stored.

[0064] Figure 9 is an explanatory diagram showing an example of the communication path requirement template table 900. The communication path requirement template table 900 is a table that defines a template (hereinafter referred to as the communication path requirement template) corresponding to the communication path requirement 605. The communication path requirement template table 900 has, as fields, a communication path requirement definition 901, an available communication module 902, and an available setting 903. A combination of the communication path requirement definition 901, the available communication module 902, and the available setting 903 in the same row defines one communication path requirement template.

[0065] The communication path requirement definition 901 defines the communication path requirement 605. Specifically, for example, the communication path requirement definition 901 has, as sub-fields, a classification 911 and a condition 912. The classification 911 is a classification that divides communication paths by type and includes, for example, control communication, media communication, and secure communication. Control communication is a classification 911 of a communication path for communicating control data. Media communication is a classification 911 of a communication path for communicating video data. Secure communication is a classification 911 of a communication path for securely communicating data. The condition 912 is a restriction when performing communication classified by the classification 911.

[0066] The available communication module 902 is a communication module that can be used according to the communication path requirement definition 901. The available setting 903 is a communication setting that can be used with the available communication module 902 according to the communication path requirement definition 901. In the available setting 903, restrictions more detailed than the condition 912 are defined.

[0067] <Functional Configuration Example of Processing Server 24 and IoT Gateway 13> FIG. 10 is a block diagram showing a functional configuration example of processing server 24 and IoT gateway 13. Processing server 24 and IoT gateway 13 include a metric measurement unit 1001, a module execution unit 1002, an inter-module routing control unit 1003, and a communication path management table 1100.

[0068] Specifically, the metric measurement unit 1001, the module execution unit 1002, and the inter-module routing control unit 1003 are realized by causing a processor 201 to execute a program stored in a storage device 202 shown in FIG. 2, for example. The communication path management table 1100 is stored in the storage device 202.

[0069] The metric measurement unit 1001 measures metric information and transmits the measured metric information to the orchestration server 102.

[0070] The module execution unit 1002 executes the modules arranged from the orchestration server 102.

[0071] The inter-module routing control unit 1003 executes routing control with other modules.

[0072] <Communication Path Management Table> The communication path management table is illustrated with reference to FIGS. 11A to 11D.

[0073] FIG. 11A is an explanatory diagram showing an example of a communication path management table 1100A held by the edge processing server 24E3 in the factory LAN 32. FIG. 11B is an explanatory diagram showing an example of a communication path management table 1100B held by the edge processing server 24E4 in the local 5G network 20. FIG. 11C is an explanatory diagram showing an example of a communication path management table 1100C held by the IoT gateway 13. FIG. 11D is an explanatory diagram showing an example of a communication path management table 1100D held by the cloud processing server 24C1. When not distinguishing the communication path management tables 1100A to 1100D and the communication path management table 1100E described later in FIG. 17A, they are simply denoted as the communication path management table 1100.

[0074] The communication path management table 1100 has, as fields, a management identifier 501, a source address 1101, a destination address 1102, and a gateway 1103. The source address 1101 is an address indicating the source of the packet. The destination address 1102 is an address indicating the destination of the packet. The gateway 1103 is the gateway that is the destination of the packet specified by the source address 1101 and the destination address 1102.

[0075] For example, taking the communication path management table 1100A as an example, in the entry of the first row, it indicates that packets with the primary learning module 405 (10.0.3.10) as the source are sent according to the "Default" routing table (not shown) for any destination (ANY). Also, in the entry of the second row, packets with the data collection module 403 (10.0.3.20) as the source are sent to the broadband communication module (10.0.3.254) which is the gateway 1103 when the camera control module 401 (10.0.5.10) is the destination, and are sent according to the "Default" routing table (not shown) for destinations other than the camera control module 401 (10.0.5.10) (ANY).

[0076] <Module Deployment Operation Sequence> FIG. 12 is a sequence diagram showing an example of the deployment operation of the module.

[0077] [Step S1200] The orchestration server 102 acquires application requirements for each application by the application requirement acquisition unit 301 and stores them in the application requirement table 600.

[0078] [Step S1201] The orchestration server 102 determines the deployment destination of the application module 602 by referring to the resource management table 500 and the application requirement table 600 by the module placement determination unit 302. Specifically, for example, the module placement determination unit 302 specifies the placement position 603 for each application module 602 by referring to the application requirement table 600. For example, for the data collection module 403, the video analysis module 404, and the primary learning module 405, it is the "closed area", for the camera control module 401 and the control device control module 402, it is the "field area", and for the secondary learning module 406, it is "ANY".

[0079] The module placement determination unit 302 specifies the position 505 corresponding to the specified placement position 603 by referring to the resource management table 500. For example, if the specified placement position 603 is "ANY", the module placement determination unit 302 determines the deployment destination of the application module 602 to the available computer resource 504 where the position 505 exists in either the "public area" or the "closed area". In this example, it is assumed that the module placement determination unit 302 determines the deployment destination of the secondary learning module 406 with the placement position 603 being "ANY" to the cloud processing server 24C1 where the position 505 is the "public area".

[0080] Also, for example, if the specified placement position 603 is a "closed area", the position 505 is a "closed area", and the available computer resources 504 that satisfy the communication path requirement 605 of the specified placement position 603 are determined as the placement destination.

[0081] For example, in the case of the data collection module 403 and the primary learning module 405 where the position 505 is a "closed area", since the communication path requirement 605 is not defined, the module placement determination unit 302 may use any available computer resources 504 as the placement destination if the position 505 is a "closed area". In this case, the module placement determination unit 302 may determine the same available computer resources 504 as those of the other application module 602 as the placement destination, or may determine different available computer resources 504 from those of the other application module 602 as the placement destination. In this example, it is assumed that the module placement determination unit 302 determines the placement destinations of the data collection module 403 and the primary learning module 405 to be the edge processing server 24E3 where the position 505 is a "closed area".

[0082] Also, for example, in the case of the video analysis module 404 where the position 505 is a "closed area", the communication path requirement 605 is "control communication" and "delay < 20 [ms]". In this case, the module placement determination unit 302 determines the available computer resources 504 where the position 505 is a "closed area" and the delay (time) satisfies the "delay < 20 [ms]" of the communication path requirement 605 as the placement destination. The available computer resources 504 where the position 505 is a "closed area" are the edge processing servers 24E2, 24E3, and 24E4.

[0083] Among these, the available computer resources 504 whose delay (time) satisfies the "delay < 20 [ms]" of the communication path requirement 605 are the edge processing server 24E4 via local 5G 507. Therefore, the module placement determination unit 302 determines the placement destination of the video analysis module 404 where the position 505 is a "closed area" to be the edge processing server 24E4 via local 5G 507.

[0084] Further, for example, if the specified placement position 603 is the "field area", the module placement determination unit 302 determines the placement destination of the application module 602 (camera control module 401, control device control module 402) to the IoT gateway 13 of the terminal 15.

[0085] The module placement determination unit 302 registers the determined placement destination address in the placement position address 704 of the entry whose module 702 in the application management table 700 is the application module 602 whose placement destination has been determined.

[0086] In this way, the placement destination of the secondary learning module 406 is determined to be the cloud processing server 24C1, the placement destinations of the data collection module 403 and the primary learning module 405 are determined to be the edge processing server 24E3, the placement destination of the video analysis module 404 is determined to be the edge processing server 24E4 via the local 5G 507, and the placement destinations of the camera control module 401 and the control device control module 402 are determined to be the IoT gateway 13 of the terminal 15.

[0087] [Step S1202] The orchestration server 102 specifies, by the communication path requirement interpretation unit 303, a communication path requirement template corresponding to the communication path requirement 605 of the application module 602 whose placement destination has been determined by the module placement determination unit 302 from the communication path requirement template table 900 in FIG. 9.

[0088] Specifically, for example, in the application requirement table 600 in FIG. 6, for the primary learning module 405 and the secondary learning module 406, since the communication path requirement 605 is "-", the communication path requirement 605 is not defined. Therefore, the communication path requirement interpretation unit 303 does not specify a communication path requirement template corresponding to the communication path requirement 605 for the primary learning module 405 and the secondary learning module 406.

[0089] On the other hand, in the application requirement table 600 of FIG. 6, the communication path requirement 605 from the camera control module 401 to the data collection module 403 is defined as "media communication" and "4K video × 3". Therefore, the communication path requirement interpretation unit 303 specifies a communication path requirement template corresponding to "media communication" and "4K video × 3" (an entry where the classification 911 is "media communication" and the condition 912 is "4K video × 3" (N ≧ 3)) from the communication path requirement template table 900 of FIG. 9.

[0090] Also, in the application requirement table 600 of FIG. 6, the communication path requirement 605 from the video analysis module 404 to the control device control module 402 is defined as "control communication" and "delay < 20 [ms]". Therefore, the communication path requirement interpretation unit 303 specifies a communication path requirement template corresponding to "control communication" and "delay < 20 [ms]" (an entry where the classification 911 is "control communication" and the condition 912 is "delay < 20 [ms]" (X ≧ 20)) from the communication path requirement template table 900 of FIG. 9.

[0091] Also, in the application requirement table 600 of FIG. 6, the communication path requirement 605 from the video analysis module 404 to the camera control module 401 is defined as "media communication" and "4K video × 1". Therefore, the communication path requirement interpretation unit 303 specifies a communication path requirement template corresponding to "media communication" and "4K video × 1" (an entry where the classification 911 is "media communication" and the condition 912 is "4K video × N" (N ≧ 1)) from the communication path requirement template table 900 of FIG. 9.

[0092] In this way, communication path requirement templates are specified for each communication path requirement target 604 of the application module 602.

[0093] [Step S1203] The orchestration server 102 determines the available communication modules 902 and the available settings 903 from the communication path requirement template identified in step S1202 by the module placement determination unit 302.

[0094] Specifically, for example, for the data collection module 403, the primary learning module 405, and the secondary learning module 406, since the communication path requirement 605 is not defined, the communication path requirement template is not identified. Therefore, the module placement determination unit 302 does not determine the available communication modules 902 and the available settings 903 for the data collection module 403, the primary learning module 405, and the secondary learning module 406.

[0095] Also, in FIG. 9, the communication path requirement template of the video analysis module 404 as the application module 602 is an entry where the classification 911 is "control communication" and the condition 912 is "delay < 20 [ms]" (X ≥ 20). Therefore, the module placement determination unit 302 determines the available communication module 902 for the video analysis module 404 as the application module 602 to be the high-reliability communication module in the communication path requirement template (the entry where the classification 911 is "control communication" and the condition 912 is "delay < 20 [ms]" (X ≥ 20)).

[0096] Then, the module placement determination unit 302 identifies the metric information 506 of the edge processing server 24E4 via local 5G 507, which is the placement destination of the video analysis module 404, from the resource management table 500. And the module placement determination unit 302 determines the available setting 903 of the high-reliability communication module used by the video analysis module 404 to be the identified metric information (delay: 10 [ms], fluctuation: 10 [ms], bandwidth 80 [Mbps], PER: 10 -4 (= 0.01 [%])).

[0097] In this way, when the control device control module 402 and the video analysis module 404 communicate, the available communication module 902 is determined to be the high-reliability communication module, and the available setting 903 is determined to be the metric information (delay: 10 [ms], fluctuation: 10 [ms], bandwidth 80 [Mbps], PER: 10 -4 (=0.01 [%])).

[0098] Also, in FIG. 9, for the communication path requirement target 604 which is the data collection module 403 of the camera control module 401, the communication path requirement template is an entry where the classification 911 is "media communication" and the condition 912 is "4K video × N" (N ≥ 3). Therefore, for the camera control module 401 where the communication path requirement target 604 is the data collection module 403, the module placement determination unit 302 determines the available communication module 902 as the wideband communication module in the communication path requirement template (the entry where the classification 911 is "media communication" and the condition 912 is "4K video × N" (N ≥ 3)).

[0099] And when the placement destination of the application module 602 is the IoT device 502 (i.e., the IoT gateway 13), the module placement determination unit 302 specifies the metric information 506 of the placement destination of the application module 602, which is the communication path requirement target 604, from the resource management table 500.

[0100] In this case, the communication path requirement target 604 of the camera control module 401 is the data collection module 403, and the available communication module 902 is determined to be the wideband communication module. Therefore, the module placement determination unit 302 specifies the metric information 506 of the edge processing server 24E3, which is the placement destination of the data collection module 403, from the resource management table 500.

[0101] Specifically, for example, when the edge processing server 24E3 communicates with the camera control module 401 via the local 5G 507, the metric information (delay: 30 [ms], jitter: 10 [ms], bandwidth 60 [Mbps], PER: 10 -4 (=0.01 [%])) is specified from the resource management table 500. Also, when the edge processing server 24E3 communicates with the camera control module 401 via the wireless LAN 508, the module placement determination unit 302 specifies the metric information (delay: 30 [ms], jitter: 20 [ms], bandwidth 100 [Mbps], PER: 10 -2 (=1 [%])) from the resource management table 500.

[0102] Then, the module placement determination unit 302 determines the available setting 903 for the data collection module 403 determined to be the broadband communication module based on the specified metric information. Specifically, for example, the available setting 903 of the broadband communication module of the data collection module 403 is the metric information (delay: 30 [ms], jitter: 10 [ms], bandwidth 60 [Mbps], PER: 10 -4 (=0.01 [%])) when the edge processing server 24E3 communicates with the camera control module 401 via the local 5G 507, and is the metric information (delay: 30 [ms], jitter: 20 [ms], bandwidth 100 [Mbps], PER: 10 -2 (=1 [%])) when the edge processing server 24E3 communicates with the camera control module 401 via the wireless LAN 508.

[0103] In this way, the available communication module 902 when the data collection module 403 and the camera control module 401 communicate is determined to be the broadband communication module.

[0104] Also, the available setting 903 is determined by metric information according to the communication method (via local 5G 507 or via wireless LAN 508) between the edge processing server 24E3 where the data collection module 403 is located and the camera control module 401.

[0105] In this way, the available communication module 902 and the available setting 903 are determined for each specified communication path requirement template.

[0106] [Step S1204] The orchestration server 102 determines the placement destination of the available communication module 902 with reference to the placement location address 704 of the application module 602 shown in FIG. 7 by the module placement determination unit 302.

[0107] Specifically, for example, for the highly reliable communication module determined as the available communication module 902 when the control device control module 402 and the video analysis module 404 communicate, the module placement determination unit 302 determines the placement destination of the highly reliable communication module, which is the available communication module 902, for each of the control device control module 402 and the video analysis module 404.

[0108] More specifically, for example, the module placement determination unit 302 determines the placement destination of the available communication module 902 of the control device control module 402 to be "IGW1111", which is the same address as the placement location address 704 of the control device control module 402, and registers it in the placement location address 704.

[0109] Similarly, the module placement determination unit 302 determines the placement destination of the highly reliable communication module, which is the available communication module 902 of the video analysis module 404, to be "E4.mobile.local", which is the same address as the placement location address 704 of the video analysis module 404, and registers it in the placement location address 704.

[0110] In addition, for the broadband communication module determined as the available communication module 902 when the data collection module 403 and the camera control module 401 communicate with each other, the module placement determination unit 302 determines the placement destination of the broadband communication module, which is the available communication module 902, for each of the data collection module 403 and the camera control module 401.

[0111] More specifically, for example, the module placement determination unit 302 determines the placement destination of the broadband communication module, which is the available communication module 902 of the data collection module 403, to be "E3.fab.local", which is the same address as the placement location address 704 of the data collection module 403, and registers it in the placement location address 704.

[0112] Similarly, the module placement determination unit 302 determines the placement destination of the broadband communication module, which is the available communication module 902 of the camera control module 401, to be "IGW1111", which is the same address as the placement location address 704 of the camera control module 401, and registers it in the placement location address 704.

[0113] In this way, the placement location address 704 of the available communication module 902 is determined.

[0114] [Step S1205] The orchestration server 102 executes a confirmation of satisfaction of the communication path requirement 605 by the module placement determination unit 302. Specifically, for example, the module placement determination unit 302 determines whether the metric information 506 determined in the available setting 903 satisfies the communication path requirement 605. If there is metric information 506 that does not satisfy the requirement, it notifies the source of the application requirement in step S1200 that the communication path requirement 605 is not satisfied, and deletes the entry of the application requirement registered in the application requirement table 600 and the value of the placement location address 704 in the application management table 700.

[0115] [Step S1206] When the communication path requirement 605 is satisfied in step S1205, the orchestration server 102 executes module deployment by the module deployment control unit 304. Specifically, for example, the module deployment control unit 304 transmits the module 702 to the arrangement position address 704 according to the application management table 700 shown in FIG. 7.

[0116] As a result, the secondary learning module 406 is arranged in the cloud processing server 24C1. The primary learning module 405 and the data collection module 403 are arranged in the edge processing server 24E3. Also, the broadband communication module, which is the available communication module 902 of the data collection module 403, is also arranged in the edge processing server 24E3.

[0117] The video analysis module 404 is arranged in the edge processing server 24E4. Also, the highly reliable communication module, which is the available communication module 902 of the video analysis module 404, is also arranged in the edge processing server 24E4.

[0118] The camera control module 401 and the control device control module 402 are arranged in the IoT gateway 13. Also, the broadband communication module, which is the available communication module 902 of the camera control module 401, is also arranged in the IoT gateway 13. Also, the highly reliable communication module, which is the available communication module 902 of the control device control module 402, is also arranged in the IoT gateway 13.

[0119] [Step S1207] The orchestration server 102 executes QoS settings for the factory LAN management server 35 and the mobile core device 23 by the E2E network quality control unit 305. Specifically, for example, the E2E network quality control unit 305 refers to the communication module repository 800 and executes QoS settings so as to have a provisioning form 803, a communication form 804, and a configuration 805 according to the communication module. For example, since communication between the data collection module 403 and the camera control module 401 is performed by a broadband communication module, the E2E network quality control unit 305 sets the QoS for each broadband communication module of the data collection module 403 and the camera control module 401 with the provisioning form 803 as a container, the communication form 804 as a gateway, and the configuration 805 as point-to-point. Regarding the content of the QoS settings, the orchestration server 102 refers to the communication path requirement template table 900 in FIG. 9 and follows the communication path QoS settings described in the available settings 903 for each communication module.

[0120] [Step S1208] The orchestration server 102 executes communication path settings for the IoT gateway 13 and the processing server 24 in which the modules are arranged by the E2E network quality control unit 305. Specifically, for example, the E2E network quality control unit 305 sets the source address 1101, the destination address 1102, and the gateway 1103 of the packet passing through the IoT gateway 13 and the processing server 24 in which the modules are arranged.

[0121] For example, for the edge processing server 24E3, the E2E network quality control unit 305 sets so that a packet having "10.0.3.10", which is the module address 703 of the primary learning module 405, as the source address 1101 is sent according to the "Default" routing table (not shown) for any destination address 1102 (ANY).

[0122] In addition, when a packet with the module address 703 of the data collection module 403, "10.0.3.20", as the source address 1101 and the module address 703 of the camera control module 401, "10.0.5.10", as the destination address 1102, the E2E network quality control unit 305 sends it to the broadband communication module (10.0.3.254) which is the gateway 1103, and for a destination address 1102 (ANY) other than the camera control module 401 (10.0.5.10), it is set to be sent according to the routing table (not shown) of the "Default" gateway 1103.

[0123] In this way, a logical system is constructed by the deployment of modules.

[0124] [Step S1209A] The IoT gateway 13 starts the execution of the modules deployed from the orchestration server 102. Specifically, for example, the IoT gateway 13 starts the execution of the camera control module 401, its broadband communication module, the control device control module 402, and its highly reliable communication module.

[0125] [Step S1209B] The edge processing server 24E4 starts the execution of the modules deployed from the orchestration server 102. Specifically, for example, the edge processing server 24E4 starts the execution of the video analysis module 404 and its highly reliable communication module.

[0126] [Step S1209C] The edge processing server 24E3 starts the execution of the modules deployed from the orchestration server 102. Specifically, for example, the edge processing server 24E3 starts the execution of the data collection module 403, its highly reliable communication module, and the primary learning module 405.

[0127] [Step S1209D] The cloud processing server 24C1 starts the execution of the modules arranged from the orchestration server 102. Specifically, for example, the cloud processing server 24C1 starts the execution of the secondary learning module 406.

[0128] As a result, the logical system constructed by the deployment of the modules starts to operate.

[0129] <Logical System after Deployment> FIG. 13 is a block diagram showing a configuration example of the logical system after the deployment of the modules. FIG. 13 shows the logical system constructed according to the sequence of FIG. 12. In FIG. 13, the bidirectional arrows between the modules indicate that both modules can communicate with each other.

[0130] Also, the communication between the data collection module 403 and the camera control module 401 is realized by the broadband communication 1301T between the broadband communication module 1301B connected to the data collection module 403 and the broadband communication module 1301A connected to the camera control module 401. Also, the communication between the video analysis module 404 and the control device control module 402 is realized by the high-reliability communication 1302T between the high-reliability communication module 1302B connected to the video analysis module 404 and the high-reliability communication module 1302A connected to the control device control module 402.

[0131] <Example of the Display Screen of the Orchestration Server 102> FIG. 14 is an explanatory diagram showing an example of the display screen of the orchestration server 102. The display screen 1400 in FIG. 14 displays the stored contents of the application management table 700 shown in FIG. 7 as the deployment processing result.

[0132] <Sequence of the Undeployment Operation of the Application> FIG. 15 is a sequence diagram showing an example of the undeployment operation of a module. The undeployment operation of the module in FIG. 15 shows the operation after the deployment operation of the module in FIG. 12.

[0133] [Step S1500] The orchestration server 102 acquires an application deletion request from the application requirement acquisition unit 301.

[0134] [Step S1501] The orchestration server 102 transmits a deletion instruction for communication path setting to the IoT gateway 13 and the processing server 24 for which communication path setting (step S1208) has been performed by the E2E network quality control unit 305.

[0135] [Step S1502] The orchestration server 102 transmits a deletion instruction for QoS setting to the factory LAN management server 35 and the mobile core device 23 for which QoS setting (step S1207) has been performed by the E2E network quality control unit 305. When the factory LAN management server 35 deletes the QoS setting, the communication between the edge processing server 24E3 via the factory LAN 32 and the IoT gateway 13 is interrupted. When the mobile core device 23 deletes the QoS setting, the communication between the edge processing server 24E4 via the local 5G network 20 and the IoT gateway 13 is interrupted.

[0136] [Step S1503] The orchestration server 102 transmits a deletion instruction for the module to the IoT gateway 13 and the processing server 24 where the module is placed by the E2E network quality control unit 305.

[0137] [Step S1504A] When the IoT gateway 13 receives the deletion instruction in step S1501, it deletes the entry of the management identifier 501 "IGW1111" to be deleted in the communication path management table 1100C. When the IoT gateway 13 receives the deletion instruction in step S1503, it deletes the arranged camera control module 401, its broadband communication module 1301A, the control device control module 402, and its high-reliability communication module 1302A.

[0138] [Step S1504B] When the edge processing server 24E4 receives the deletion instruction in step S1501, it deletes the entry of the management identifier 501 "IGW1111" to be deleted in the communication path management table 1100B. When the edge processing server 24E4 receives the deletion instruction in step S1503, it deletes the arranged video analysis module 404 and its high-reliability communication module 1302B.

[0139] [Step S1504C] When the edge processing server 24E3 receives the deletion instruction in step S1501, it deletes the entry of the management identifier 501 "IGW1111" to be deleted in the communication path management table 1100A. When the edge processing server 24E3 receives the deletion instruction in step S1503, it deletes the arranged data collection module 403, its high-reliability communication module, and the primary learning module 405.

[0140] [Step S1504D] When the cloud processing server 24C1 receives the deletion instruction in step S1501, it deletes the entry of the management identifier "IGW1111" to be deleted in the communication path management table 1100D. When the cloud processing server 24C1 receives the deletion instruction in step S1503, it deletes the arranged secondary learning module 406.

[0141] In this way, the module is undeployed from the processing server 24.

[0142] <Module Redeployment Operation Sequence> FIG. 16 is a sequence diagram showing an example of a module redeployment operation. The redeployment is executed, for example, when there is a change in the metric information 506. In FIG. 16, when the edge processing server 24E4 fails to satisfy the communication path requirement 605 of the video analysis module 404, which is the application module 602 disposed in the edge processing server 24E4, an example will be described in which the video analysis module 404 and its high-reliability communication module 1302B are relocated to the edge processing server 24E2.

[0143] [Step S1600] The orchestration server 102 detects, via the metric information collection unit 300, an application module 602 that fails to satisfy the communication path requirement 605 due to a change in the metric information 506. Specifically, for example, the metric information collection unit 300 repeatedly collects the metric information 506 for each available computer resource 504, and detects whether the communication path requirement 605 of the application module 602 disposed in the available computer resource 504 is no longer satisfied.

[0144] In this example, it is assumed that the metric information collection unit 300 has detected that the edge processing server 24E3 has failed to satisfy the communication path requirement 605 (4K video × 3) of the data collection module 403 disposed in the edge processing server 24E3.

[0145] [Step S1601] When the orchestration server 102 detects an application module 602 that fails to satisfy the communication path requirement 605 in step S1600, the orchestration server 102, similar to step S1201, refers to the resource management table 500 and the application requirement table 600 by the module placement determination unit 302 to determine the relocation destination of the application module 602. In this example, it is assumed that the relocation destination of the data collection module 403 has been determined to be the edge processing server 24E2.

[0146] [Steps S1602 to S1605] Steps S1602 to S1605 are the same process as Steps S1202 to S1205. In this example, it is assumed that, through Steps S1602 to S1605, the relocation destination of the broadband communication module 1301B of the data collection module 403 has been determined to be the edge processing server 24E2. Note that since the primary learning module 405 communicates with the data collection module 403 at the edge processing server 24E3, the orchestration server 102 may relocate the data collection module 403, the broadband communication module 1301B, and itself to the edge processing server 24E2.

[0147] [Steps S1606] Similar to Step S1501, the orchestration server 102 sends a deletion instruction for communication path setting to the edge processing server 24E3, which is the original placement destination of the data collection module 403, the broadband communication module 1301B, and the primary learning module 405.

[0148] [Steps S1607] Similar to Step S1503, the orchestration server 102 sends a deletion instruction for the data collection module 403, the broadband communication module 1301B, and the primary learning module 405 to the edge processing server 24E3, which is the original placement destination of the data collection module 403, the broadband communication module 1301B, and the primary learning module 405.

[0149] [Steps S1608] Upon receiving the deletion instruction in Step S1606, the edge processing server 24E3 deletes the entry of the management identifier 501 "IGW1111" in the communication path management table 1100A that is the target of the deletion instruction. Upon receiving the deletion instruction in Step S1607, the edge processing server 24E3 deletes the data collection module 403, the broadband communication module 1301B, and the primary learning module 405.

[0150] [Steps S1607] The orchestration server 102 executes module deployment to the IoT gateway 13, the edge processing server 24E2, the edge processing server 24E4, and the cloud processing server 24C1 according to the processing results of steps S1601 to S1605 by the module deployment control unit 304.

[0151] In this way, a logical system is constructed by redeployment of the modules.

[0152] [Step S1610A] The IoT gateway 13 starts the execution of the modules arranged from the orchestration server 102. Specifically, for example, the IoT gateway 13 starts the execution of the camera control module 401, its broadband communication module 1301A, the control device control module 402, and its high-reliability communication module 1302A.

[0153] [Step S1610B] The edge processing server 24E4 starts the execution of the modules arranged from the orchestration server 102. Specifically, for example, the edge processing server 24E2 starts the execution of the video analysis module 404 and its high-reliability communication module 1302B.

[0154] [Step S1610D] The cloud processing server 24C1 starts the execution of the modules arranged from the orchestration server 102. Specifically, for example, the cloud processing server 24C1 starts the execution of the secondary learning module 406.

[0155] [Step S1610E] The edge processing server 24E2 starts the execution of the modules arranged from the orchestration server 102 in step S1609. Specifically, for example, the edge processing server 24E3 starts the execution of the data collection module 403, its broadband communication module 1301B, and the primary learning module 405.

[0156] Thereby, the logical system constructed by the redeployment of the modules starts operating.

[0157] <Communication path management table 1100 after redeployment> Using FIGS. 17A to 17B, the communication path management table 1100 after redeployment is illustrated.

[0158] FIG. 17A is an explanatory diagram showing an example of the communication path management table 1100E held by the edge processing server 24E2 in the public 5G network 40. FIG. 17B is an explanatory diagram showing an example of the communication path management table 1100C held by the IoT gateway 13.

[0159] As shown in FIG. 17A, after redeployment, instead of the communication path management table 1100A of the edge processing server 24E3, the communication path management table 1100E of the edge processing server 24E2 is set.

[0160] In the communication path management table 1100E of the edge processing server 24E2 shown in FIG. 17A, in the entry of the first row, it indicates that packets originating from the primary learning module 405 (10.0.2.10) are sent to the "Default" gateway 1103 for any destination (ANY). Also, in the entry of the second row, packets originating from the data collection module 403 (10.0.3.20) are sent to the broadband communication module (10.0.3.254), which is the gateway 1103, when the camera control module 401 (10.0.5.10) is the destination, and are sent to the "Default" gateway 1103 for destinations other than the camera control module 401 (10.0.5.10) (ANY).

[0161] As shown in FIG. 17B, in the communication path management table 1100C of the IoT gateway 13, compared with FIG. 11, the address of the primary learning module 405 at the shaded part of the destination address 1103C has been changed from "10.0.3.20" to "10.0.2.20".

[0162] Note that for the communication path management table 1100B held by the edge processing server 24E4 and the communication path management table 1100D held by the cloud processing server 24C1, there is no change from FIGS. 11B and 11D even after redeployment.

[0163] <Logical system after redeployment> FIG. 18 is a block diagram showing a configuration example of a logical system after redeployment of the modules. The difference from FIG. 13 is that the data collection module 403, the broadband communication module 1301B, and the primary learning module 405 have been relocated from the edge processing server 24E3 of the factory LAN 32 to the edge processing server 24E2 of the public 5G network 40.

[0164] <Example of the display screen of the orchestration server 102 after redeployment> FIG. 19 is an explanatory diagram showing an example of a display screen of the orchestration server 102 after redeployment. Compared with FIG. 14, the module address 703 and the placement position address 704 of the broadband communication module 1301B and the primary learning module 405 are rewritten to the address of the edge processing server 24E2 at the redeployment destination. The module address 703 and the placement position address 704 of the application management table 700 are updated as shown in FIG. 19.

[0165] In the above-described redeployment, the data collection module 403, the broadband communication module 1301B, and the primary learning module 405 were described as being relocated from the edge processing server 24E3 of the factory LAN 32 to the edge processing server 24E2 of the public 5G network 40. However, the broadband communication module 1301A, the camera control module 401, the control device control module 402, and the highly reliable communication module 1302A may be relocated to another IoT gateway 13.

[0166] Thus, according to this embodiment, for example, a highly reliable connectivity (communication path) can be realized so that the on-site network at a site such as manufacturing or logistics satisfies the application requirements required by the application.

[0167] Note that the present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the configurations described. Also, a part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Also, the configuration of another embodiment may be added to the configuration of one embodiment. Also, for a part of the configuration of each embodiment, addition, deletion, or replacement with another configuration may be performed.

[0168] In addition, each of the above-described configurations, functions, processing units, processing means, etc. may be realized in hardware by designing part or all of them, for example, by means of an integrated circuit, or may be realized in software by a processor interpreting and executing a program for realizing each function.

[0169] Information such as programs, tables, files, etc. for realizing each function can be stored in a storage device such as a memory, a hard disk, an SSD (Solid State Drive), or a recording medium such as an IC (Integrated Circuit) card, an SD card, or a DVD (Digital Versatile Disc).

[0170] Also, the control lines and information lines show those considered necessary for explanation, and do not necessarily show all the control lines and information lines required for implementation. In practice, it may be considered that almost all configurations are interconnected.

Explanation of Reference Numerals

[0171] 1 Edge operation management system 10 Camera control module 11 Control device 13 Gateway 15 Terminal 23 Mobile core device 24C1 Cloud processing server 24E Edge processing server 102 Orchestration server 300 Metric information collection unit 301 Application requirement acquisition unit 302 Module placement determination unit 303 Communication path requirement interpretation unit 304 Module deployment control unit 305 Network quality control unit 400 Application 401 Camera control module 402 Control device control module 403 Data Collection Module 404 Video Analysis Module 405 Primary Learning Module 406 Secondary Learning Module 500 Resource Management Table 600 Application Requirement Table 700 Application Management Table 800 Communication Module Repository 900 Communication Path Requirement Template Table 901 Communication Path Requirement Definition 902 Available Communication Modules 903 Available Settings 1001 Metric Measurement Unit 1002 Module Execution Unit 1003 Inter - module Routing Control Unit 1100 Communication Path Management Table

Claims

1. A management device capable of communicating with a computer cluster, comprising a processor that executes a program and a storage device that stores the program, wherein the storage device stores a group of application modules, a group of communication modules, communication path requirements that are conditions required for a communication path between an application module in the group of application modules and another application module that is a communication partner of the application module, a communication path requirement target that designates the other application module, and a communication path requirement template group composed of a communication path requirement definition that defines the type and conditions of communication in the communication path requirements, an available communication module that defines a communication module that can be used for the communication path requirement definition, and an available setting that defines a communication setting that can be used for the communication path requirement definition, wherein the processor performs a specifying process of specifying, from the communication path requirement template group, a first communication path requirement template corresponding to a first communication path requirement of a first application module, and specifying, from the communication path requirement template group, a second communication path requirement template corresponding to a second communication path requirement of a second application module designated as a communication partner of the first application module in the communication path requirement target, performs a communication module determination process of determining the available communication module included in the first communication path requirement template as a first communication module that can be used by the first application module, and determining the available communication module included in the second communication path requirement template as a second communication module that can be used by the second application module, Determine the placement destination of the first communication module to the first placement destination of the first application module in the computer cluster, and determine the placement destination of the second communication module to the second placement destination of the second application module in the computer cluster, which is a communication module placement destination determination process; Place the first application module and the first communication module at the first placement destination, and place the second application module and the second communication module at the second placement destination, which is a placement process; Set a communication path that enables communication between the first application module and the second application module via the first communication module and the second communication module, which is a communication path setting process; A management device characterized by executing the above.

2. The management device according to claim 1, wherein The storage device stores area information where each computer in the computer cluster is located, and the deployable area of each application module in the application module group, and stores them. The processor Based on the area information and the deployable area, determine the first placement destination from the computer cluster, and determine the second placement destination from the computer cluster, which is an application module placement destination determination process; A management device characterized by executing the above.

3. The management device according to claim 1, wherein The storage device stores a communication module repository that defines information on network quality according to the type of the communication module. The processor Refer to the communication module repository, and perform a quality setting process of setting the network quality according to the type of each communication module of the first communication module and the second communication module; A management device characterized by executing the above.

4. The management device according to claim 1, wherein the processor, performs a deletion process of transmitting a deletion instruction for the communication path to the first destination and the second destination, transmitting a stop or deletion instruction for the first application module and the first communication module to the first destination, and transmitting a stop or deletion instruction for the second application module and the second communication module to the second destination; and is characterized by executing the above.

5. The management device according to claim 2, wherein the storage device, stores metric information generated in communication between the computers, and the processor, performs a first detection process of detecting that the first application module no longer satisfies the first communication path requirement based on the metric information; for the first application module that no longer satisfies the first communication path requirement by the first detection process, based on the area information and the available area, performs an application module placement destination re-determination process of determining a third destination different from the first destination from the computer group; performs a communication module placement destination re-determination process of determining the placement destination of the first communication module to the third destination; performs a re-placement process of placing the first application module and the first communication module at the third destination; performs a communication path re-setting process of communicably connecting between the first application module placed at the third destination and the second application module via the first communication module and the second communication module placed at the third destination; and is characterized by executing the above.

6. The management device according to claim 2, wherein the storage device, Store the metric information generated in the communication between the computers, The processor, Based on the metric information, a second detection process for detecting that the second application module has failed to meet the second communication path requirement, For the second application module that has failed to meet the second communication path requirement by the second detection process, based on the area information and the available area, an application module placement destination re-determination process for determining a fourth placement destination different from the second placement destination from the computer group, A communication module placement destination re-determination process for determining the placement destination of the second communication module to the fourth placement destination, A re-placement process for placing the second application module and the second communication module at the fourth placement destination, A communication path re-setting process for communicably connecting between the first application module and the second application module placed at the fourth placement destination via the first communication module and the second communication module re-placed at the fourth placement destination, A management device characterized by executing the above.

7. The management device according to claim 5, The processor, Based on the metric information, execute a second detection process for detecting that the second application module has failed to meet the second communication path requirement, In the application module placement destination re-determination process, the processor determines, from the computer group, a fourth placement destination different from the second placement destination for the second application module that has failed to meet the second communication path requirement by the second detection process, based on the area information and the available area, In the communication module placement destination re-determination process, the processor determines the placement destination of the second communication module to the fourth placement destination, In the reconfiguration process, the processor places the second application module and the second communication module at the fourth destination, In the communication path reconfiguration process, the processor sets a communication path that enables communication between the first application module relocated to the third destination and the second application module relocated to the fourth destination via the first communication module relocated to the third destination and the second communication module relocated to the fourth destination. A management device characterized by the above.

8. A management system having a computer group and a management device capable of communicating with the computer group, The management device is An application module group, A communication module group, A communication path requirement, which is a condition required for a communication path between an application module in the application module group and another application module that is a communication partner of the application module, A communication path requirement target that designates the other application module, A communication path requirement template group composed of a communication path requirement definition that defines the type and conditions of communication in the communication path requirement, a usable communication module that defines a communication module usable for the communication path requirement definition, and a usable setting that defines a communication setting usable for the communication path requirement definition, and stores them. The management device is A specifying process of specifying a first communication path requirement template corresponding to the first communication path requirement of the first application module from the communication path requirement template group, and specifying a second communication path requirement template corresponding to the second communication path requirement of the second application module designated as the communication partner of the first application module in the communication path requirement target from the communication path requirement template group. Determine the available communication module included in the first communication path requirement template as the first communication module that can be used by the first application module, and determine the available communication module included in the second communication path requirement template as the second communication module that can be used by the second application module, which is a communication module determination process; Determine the placement destination of the first communication module as the first placement destination of the first application module within the computer cluster, and determine the placement destination of the second communication module as the second placement destination of the second application module within the computer cluster, which is a communication module placement destination determination process; Place the first application module and the first communication module at the first placement destination, and place the second application module and the second communication module at the second placement destination, which is a placement process; Set a communication path that enables communication between the first application module and the second application module via the first communication module and the second communication module, which is a communication path setting process; A management system characterized by executing the above.

9. A management method by a management device capable of communicating with a computer cluster, The management device includes a processor that executes a program and a storage device that stores the program. The storage device An application module group, A communication module group, Communication path requirements, which are the conditions required for the communication path between an application module in the application module group and another application module that is the communication partner of the application module, A communication path requirement target that designates the other application module, Store a communication path requirement template group composed of a communication path requirement definition that defines the type and conditions of communication in the communication path requirement, a usable communication module that defines a communication module usable for the communication path requirement definition, and a usable setting that defines a communication setting usable for the communication path requirement definition. The processor A specifying process of specifying a first communication path requirement template corresponding to the first communication path requirement of the first application module from the communication path requirement template group, and specifying a second communication path requirement template corresponding to the second communication path requirement of the second application module designated as the communication partner of the first application module for the communication path requirement target from the communication path requirement template group. A communication module determination process of determining the usable communication module included in the first communication path requirement template as a first communication module usable by the first application module, and determining the usable communication module included in the second communication path requirement template as a second communication module usable by the second application module. A communication module placement destination determination process of determining the placement destination of the first communication module as the first placement destination of the first application module in the computer group, and determining the placement destination of the second communication module as the second placement destination of the second application module in the computer group. A placement process of placing the first application module and the first communication module at the first placement destination, and placing the second application module and the second communication module at the second placement destination. A communication path setting process of setting a communication path that enables communication between the first application module and the second application module via the first communication module and the second communication module. A management method characterized by executing the above.

Images