Service-based middleware integration system

Abstract

The present invention provides a service-based middleware integration system, including: multiple service middlewares, multiple service middlewares are distributed in multiple layers of devices in an end-edge cloud system, each service middleware includes more than one service, and each service includes more than one microservice; a soft bus, the soft bus is connected to the services or microservices in the multiple service middlewares, and the soft bus is used for data interaction between the services or microservices in the multiple service middlewares; a management platform, the management platform is connected to the multiple service middlewares, and the management platform responds to application requirements and combines the services or microservices in the multiple service middlewares, so that some or all of the services or microservices in the multiple service middlewares run and interact according to the corresponding combination mode. The present invention integrates heterogeneous industrial control system data in a low-coupling manner through a dynamic reorganization mode of service combination of multiple middlewares, provides data support for upper-level applications, and improves the flexibility of industrial control business.

Description

Technical Field

[0001] The present invention relates to the field of industrial control technology, and in particular to a service-based middleware integration system. Background Art

[0002] The automatic control system is a business-centered automation, which mainly realizes the operation of automated equipment in the real physical world; while the information system processes software, data, and information in the virtual world. The two are completely different systems. In order to realize the automatic control of industrial systems, it is necessary to use middleware to allocate the software and hardware resources of industrial control systems and information systems, and to schedule and control industrial tasks. However, existing middleware is usually deployed in a centralized manner, which leads to serious coupling of multiple middleware and makes it difficult to ensure the flexibility of industrial control services. Summary of the invention

[0003] The service-based middleware integration system provided by the present invention integrates heterogeneous industrial control system data in a low-coupling manner by dynamically reorganizing multiple middleware in a service combination mode, provides data support for upper-level applications, and improves the flexibility of industrial control business.

[0004] The present invention provides a service-based middleware integration system, comprising:

[0005] Multiple service middlewares, wherein the multiple service middlewares are distributed in multiple devices in the end-edge-cloud system, each service middleware includes more than one service, and each service includes more than one microservice;

[0006] A soft bus, the soft bus being communicatively connected with the services or microservices in the multiple service middlewares, and the soft bus being used for data interaction between the services or microservices in the multiple service middlewares;

[0007] A management platform is communicatively connected with the multiple service middlewares, and the management platform combines the services or microservices in the multiple service middlewares in response to application requirements, so that some or all of the services or microservices in the multiple service middlewares run and interact according to corresponding combinations.

[0008] Optionally, the multiple service middlewares include: one or more of: field protocol support middleware, device access middleware, device management middleware, data security middleware, data stream processing middleware, data exchange middleware, data transfer middleware, industrial software data integration middleware and industrial control system integration middleware.

[0009] Optionally, the end-edge-cloud system includes: the end-edge-cloud system heterogeneous industrial control system includes: an enterprise cloud platform, an edge server, an industrial gateway, and a field-side heterogeneous industrial control system.

[0010] Optionally, the data security middleware, data transfer middleware, industrial software data integration middleware, device management middleware and the data stream processing middleware are run on an enterprise cloud platform in the heterogeneous industrial control system of the end-edge-cloud system;

[0011] The data exchange middleware, industrial control system integration middleware, industrial control integration middleware and device access middleware are run on the edge server in the heterogeneous industrial control system end-edge-cloud system;

[0012] The field protocol supports the middleware protocol supports the industrial gateway running in the end-edge cloud system;

[0013] The device access middleware runs on an industrial gateway or edge server in the end-edge cloud system. Optionally, the management platform is used to perform static parameter configuration on the services or microservices in the multiple service middlewares, and to interactively combine the multiple service middlewares according to dynamic application requirements.

[0014] Optionally, the management platform includes a service composition module, and the service composition module includes:

[0015] A service registration unit, wherein the service registration unit is used to create and maintain a registry for the services or microservices in the multiple service middlewares, and the registry is used to store attribute information of the multiple middlewares.

[0016] Optionally, the service combination module further includes:

[0017] A service configuration unit, wherein the service configuration unit is used to configure parameters of services or microservices in the multiple service middlewares.

[0018] Optionally, the service combination module further includes:

[0019] A service integration unit is used to set the interaction mode between the added service middleware, service or microservice and the existing service middleware, service or microservice according to a preset decision logic.

[0020] Optionally, the service combination module further includes:

[0021] A service composition optimization unit is used to optimize the combination of services or microservices in a variety of service middlewares based on a reference point non-dominated sorting genetic algorithm.

[0022] Optionally, the service combination module further includes:

[0023] A service calling module, which is used to create calling modes and calling methods for services or microservices in some or all of the service middlewares in a variety of service middlewares according to corresponding combinations, publish the calling modes and calling methods to a registry, and bind the calling addresses and calling methods of some or all of the services or microservices.

[0024] In the technical solution provided by the present invention, multiple service middlewares are distributed in the edge-cloud system, and the services or microservices in the multiple service middlewares interact independently through the soft bus, thereby decoupling the multiple service middlewares, services and microservices, so that each service middleware, service and microservice can run independently. This deployment method uses multiple middlewares to dynamically reorganize the service combination mode, so that the data of heterogeneous industrial control systems are integrated in a low-coupling manner, providing data support for upper-level applications and improving the flexibility of industrial control services. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A schematic diagram of the logical relationship between various service middleware and the soft bus in a service-based middleware integration system according to an embodiment of the present invention;

[0026] Figure 2 A schematic diagram of the deployment and operation locations of multiple service middlewares after being dynamically combined and configured by a management platform in a service-based middleware integration system according to another embodiment of the present invention;

[0027] Figure 3 A schematic diagram of a service-based middleware integration system in another embodiment of the present invention in which multiple service middlewares are dynamically combined and configured through a management platform and run in a service or microservice mode;

[0028] Figure 4 A schematic diagram of the logical relationship between a management platform, industrial applications and multiple service middleware in a service-based middleware integration system according to another embodiment of the present invention;

[0029] Figure 5 This is a diagram of the operation relationship of each unit in a management platform of a service-based middleware integration system when receiving a service request in another embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0031] The embodiment of the present invention provides a service-based middleware integration system, such as Figure 1-3 As shown, including:

[0032] Multiple service middlewares, wherein the multiple service middlewares are distributed in multiple devices in the end-edge-cloud system, each service middleware includes more than one service, and each service includes more than one microservice;

[0033] In some embodiments, Figure 1 As shown, multiple service middlewares are used to provide different services. There can be more than one service middleware for each service. Each middleware is composed of a group of services that can run independently. Each service can include more than one microservice. Microservice refers to a more fine-grained functional unit that can run independently.

[0034] A soft bus, the soft bus being communicatively connected with the services or microservices in the multiple service middlewares, and the soft bus being used for data interaction between the services or microservices in the multiple service middlewares;

[0035] In some embodiments, the soft bus is used to define the interactive data interface between multiple service middlewares and determine the function of the protocol used for data interaction between multiple service middlewares. The protocol determined by the soft bus may include different communication interaction modes such as request / response and publish / subscribe. The soft bus can provide real-time and reliable interactive semantic support and is a data transmission channel for various services in multiple service middlewares. Thus, the soft bus can support each service middleware to interact with various heterogeneous data resources located in different hardware platforms, operating systems, network protocols, data management systems and network environments in a unified, transparent and efficient manner. The soft bus shields the heterogeneity of communication modes and can provide data for upper-level applications. Therefore, the data interaction of services or microservices in multiple service middlewares through the soft bus is conducive to the flexible expansion of multiple service middlewares, services and microservices.

[0036] A management platform is communicatively connected with the multiple service middlewares, and the management platform combines the services or microservices in the multiple service middlewares in response to application requirements, so that some or all of the services or microservices in the multiple service middlewares run and interact according to corresponding combinations.

[0037] In some embodiments, Figure 2-3As shown in the figure, since various service middlewares are distributed in multiple devices in the edge-cloud system and run independently, it is necessary to manage the various service middlewares through the management platform so that the various service middlewares can interact with each other and meet industrial needs. Different industrial systems require different sets of middleware services to be put into operation during operation. Therefore, the management platform needs to implement personalized combinations of services or microservices in various service middlewares according to specific industrial application scenarios and business needs, flexibly configure middleware functions, and become an actual runtime system.

[0038] In the technical solution provided by the embodiment of the present invention, a variety of service middleware is distributed in the end-edge cloud system, and the services or microservices in the multiple service middleware interact independently through the soft bus, thereby decoupling the multiple service middleware, services and microservices, so that each service middleware, service and microservice can run independently. This deployment method utilizes multiple middleware in a service combination dynamic reorganization mode to integrate heterogeneous industrial control system data in a low-coupling manner, provide data support for upper-level applications, and improve the flexibility of industrial control business. As an optional implementation method, the multiple service middleware includes: one or more of field protocol support middleware, device access middleware, device management middleware, data security middleware, data stream processing middleware, data exchange middleware, data transfer middleware, industrial software data integration middleware and industrial control system integration middleware.

[0039] As an optional implementation, the end-edge-cloud system heterogeneous industrial control system includes: an enterprise cloud platform, an edge server, an industrial gateway, and a field-side heterogeneous industrial control system.

[0040] As an optional implementation, the data security middleware, data transfer middleware, industrial software data integration middleware, device management middleware and the data stream processing middleware are run on the enterprise cloud platform of the end-edge cloud system;

[0041] The data exchange middleware and the industrial control system integration middleware run on the edge server in the end-edge cloud system;

[0042] The field protocol supports the middleware running on the industrial gateway in the end-edge cloud system;

[0043] The device access middleware runs on the industrial gateway or edge server in the end-edge cloud system.

[0044] In some embodiments, multiple service middlewares are deployed on devices at different levels of the end-edge-cloud system to implement different functions. For example, they can be deployed in the following manner:

[0045] Industrial field protocol support middleware, deployed in the embedded operating system of the edge gateway, is used to support industrial control communication protocols such as OPCUA, Profibus, Modbus, EtherCAT, and interact with the soft bus through the MQTT interface;

[0046] Device access middleware, deployed in the docker container of the edge gateway or edge server, is used to support the access of multiple types of devices such as PLC, CNC machine tools, industrial robots, sensors, etc., and interact with the soft bus through the REST API interface;

[0047] Industrial control system integration middleware is deployed in the docker container of the edge gateway or edge server. It can be deployed in a cross-platform manner to provide docking services for core components of industrial control systems such as DCS and SCADA, and interact with the soft bus through API, RPC, database or table interface. Industrial control system integration middleware is mainly used to realize industrial timing, streaming, relational and other multi-data collection and access, reducing data integration access costs. In order to adapt to various industrial control systems, by atomically encapsulating each data processing process, the data processing process can be freely combined to meet various data integration processing requirements, providing a basis for industrial control system adapter encapsulation.

[0048] The data exchange middleware is deployed in the docker container of the edge server. It can be deployed in a cross-platform manner to support data types such as Json, XML, AutomationML, and RDF to interact with the soft bus through REST API or MQ publishing and subscription. After data protocol conversion and access of multiple types of devices and heterogeneous industrial control systems, the data exchange middleware processes the data based on a unified data model. The data exchange middleware receives multi-source heterogeneous data in a unified parsing format and first enters the general conversion memory pool. After the data is converted, it is written into MQ and the data source is marked. Then a new Job is created to execute the target data format unified data model conversion and output.

[0049] Data stream processing middleware is deployed on the enterprise cloud platform. It can be deployed in a cross-platform manner to provide post-access extraction, conversion, and loading of batch data, streaming data, and real-time data, and interact with the soft bus through the MQTT interface.

[0050] Data transfer middleware is deployed on the enterprise cloud platform. It can be deployed in a cross-platform manner to provide multi-source heterogeneous data transfer and query services, and interact with the soft bus through the data set interface;

[0051] Industrial software data integration middleware, deployed on the enterprise cloud platform, is used to provide integrated ERP, MES, PHM and other information system data services, and interacts with the soft bus through data sets or MQTT interfaces;

[0052] Device management middleware, deployed on the enterprise cloud platform, is used to support services such as device discovery, addition, deletion, query, and configuration, and interacts with the soft bus through API or RPC interface;

[0053] Data security middleware is deployed on the enterprise cloud platform to provide data security services such as data integrity verification and data storage, and interacts with the soft bus through an API interface.

[0054] Taking the combination of field protocol support middleware and device access middleware as an example, the middleware combination is exemplified. By combining field protocol support middleware and device access middleware, the field protocol support middleware provides a variety of heterogeneous industrial Internet communication protocols (such as Modbus, Profibus, etc.) parsing services, and the device access middleware supports a variety of device access services such as sensors, PLCs, CNC machine tools, industrial robots, etc. After the device is connected, according to the characteristics of various heterogeneous industrial Internet communication protocols and the general interaction model, a general collaborative semantics is abstracted. Then, based on the collaborative semantics, the middle-layer protocol is implemented, so that all the underlying heterogeneous industrial Internet communication protocols interact with the middle-layer protocol through adapters, and then realize mutual collaboration through the middle-layer protocol.

[0055] As an optional implementation, the management platform is used to perform static parameter configuration on the services or microservices in the multiple service middlewares, and interactively combine the multiple service middlewares according to dynamic application requirements.

[0056] In some embodiments, the management platform integrates the services or microservices in the various service middlewares required by industrial applications into a runtime system by combining static configuration with dynamic combination. Static configuration selects and configures the corresponding service middleware parameters. For example, for device access middleware, the relevant service link information should be configured according to the type of database it connects to (MYSQL or ORACLE, etc.); for data security middleware, the user name, password, license certificate and other information should be configured according to the security policy provided. Dynamic combination is based on the needs of industrial applications, combining the services or microservices in the various service middlewares required by industrial applications into a middleware runtime system in a loosely coupled form. Loose coupling means that each service or microservice can run independently without affecting other services, and can also be used in combination with other services. Combining services or microservices in a variety of service middlewares in a loosely coupled form can support the construction of a more complex middleware runtime system. The middleware runtime system collaborates with a variety of service middlewares so that the combination of services or microservices is displayed as a whole in the application-oriented manner, and the operating environment of a variety of service middlewares can be distributed on different platforms without the need for specific adjustments and modifications to the underlying hardware and operating system.

[0057] As an optional implementation, Figure 4 As shown, the management platform includes a service combination module, and the service combination module includes:

[0058] A service registration unit, wherein the service registration unit is used to create and maintain a registry for the services or microservices in the multiple service middlewares, and the registry is used to store attribute information of the multiple middlewares.

[0059] In some embodiments, the service registration unit creates a registry for various service middleware that provide services and maintains the registry. The registry can classify the services or microservices of the various service middleware and describe how to obtain the services or microservices to facilitate the discovery of related services by searching the registry, thereby establishing a connection and obtaining the corresponding services.

[0060] As an optional implementation, continue as Figure 4 As shown, the service combination module also includes:

[0061] A service configuration unit, wherein the service configuration unit is used to configure parameters of services or microservices in the multiple service middlewares.

[0062] In some embodiments, the service configuration unit is used to centrally manage the configuration information of services or microservices of various service middlewares, and to select and configure the parameters of the middlewares, and to support the addition, deletion, modification and publication of configuration information.

[0063] As an optional implementation, continue as Figure 4 As shown, the service combination module also includes:

[0064] A service integration unit is used to set the interaction mode between the added service middleware, service or microservice and the existing service middleware, service or microservice according to a preset decision logic.

[0065] In some embodiments, the service integration unit adds services or microservices in the service middleware required to implement new functions according to the decision logic, and integrates them with the services or microservices in the existing service middleware, so as to quickly implement new functional applications.

[0066] As an optional implementation, continue as Figure 4 As shown, the service combination module also includes:

[0067] A service composition optimization unit is used to optimize the combination of services or microservices in a variety of service middlewares based on a reference point non-dominated sorting genetic algorithm.

[0068] In some embodiments, the service composition optimization unit optimizes the middleware service composition according to the business process. Combining services or microservices of multiple service middleware deployed from multiple locations such as edge servers, industrial gateways, and the cloud. Selecting the best service combination to meet application requirements is an NP-hard problem. Therefore, in the service composition process, the service composition multi-objective optimization method, that is, the classic NSGA-Ⅲ algorithm (based on the reference point non-dominated sorting genetic algorithm) is used for optimization to reduce service access delays and network resource consumption.

[0069] As an optional implementation, continue as Figure 4 As shown, the service combination module also includes:

[0070] A service calling module, which is used to create calling modes and calling methods for services or microservices in some or all of the service middlewares in a variety of service middlewares according to corresponding combinations, publish the calling modes and calling methods to a registry, and bind the calling addresses and calling methods of some or all of the services or microservices.

[0071] In some embodiments, the service calling module performs mutual calls between services or microservices according to the service or microservice combination relationship. Before calling, it is necessary to first create a call relationship, determine the call method, and publish the call relationship and call method to the registry, and then find the corresponding call service and bind the service address and method.

[0072] In some other preferred implementations, the service composition module may also include a message distribution unit for sending messages to various service middlewares, a security management unit for performing security management according to corresponding security policies, and a log management unit for recording service execution status.

[0073] like Figure 5As shown, the operation order of each unit of the service composition module in the management platform when receiving a service request is exemplarily shown. When the service composition module receives a service request, that is, when a new service supplier provides a new service middleware or a new service or a new microservice, the service registration module first maintains or creates a registry for services or microservices in multiple service middlewares. After completing the maintenance or creation of the registry, the service configuration unit configures the newly added service middleware, service or microservice. After completing the configuration, the service integration unit integrates the newly added service middleware, service or microservice with the existing service middleware, service or microservice. After the integration is completed, the service combination optimization unit optimizes the multiple service middleware including the newly added service middleware, service or microservice to form an optimized service or microservice combination. Finally, the service call module creates a call relationship based on the optimized service or microservice combination, determines the call method, and publishes the call relationship and call method to the registry, and then finds the corresponding call service and binds the service address and method.

[0074] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A service-based middleware integration system, characterized in that: include: Multiple service middlewares, wherein the multiple service middlewares are distributed in multiple layers of devices in the end-edge-cloud system, each service middleware includes more than one service, and each service includes more than one microservice; A soft bus, the soft bus being communicatively connected with the services or microservices in the multiple service middlewares, and the soft bus being used for data interaction between the services or microservices in the multiple service middlewares; A management platform is communicatively connected with the multiple service middlewares, and the management platform combines the services or microservices in the multiple service middlewares in response to application requirements, so that some or all of the services or microservices in the multiple service middlewares run and interact according to corresponding combinations.

2. The service-based middleware integration system according to claim 1, characterized in that: The multiple service middlewares include: one or more of field protocol support middleware, device access middleware, device management middleware, data security middleware, data stream processing middleware, data exchange middleware, data transfer middleware, industrial software data integration middleware and industrial control system integration middleware.

3. The service-based middleware integration system according to claim 2, characterized in that: The end-edge-cloud system includes: an enterprise cloud platform, an edge server, an industrial gateway, and a heterogeneous industrial control system on the field side.

4. The service-based middleware integration system according to claim 3, characterized in that: The data security middleware, data transfer middleware, industrial software data integration middleware, device management middleware and the data stream processing middleware are run on the enterprise cloud platform of the end-edge cloud system; The data exchange middleware and the industrial control system integration middleware run on the edge server in the end-edge cloud system; The field protocol supports the middleware running on the industrial gateway in the end-edge cloud system; The device access middleware runs on the industrial gateway or edge server in the end-edge cloud system.

5. The service-based middleware integration system according to claim 1, characterized in that: The management platform is used to perform static parameter configuration on the services or microservices in the multiple service middlewares, and to interactively combine the multiple service middlewares according to dynamic application requirements.

6. The service-based middleware integration system according to claim 5, characterized in that: The management platform includes a service combination module, and the service combination module includes: A service registration unit, wherein the service registration unit is used to create and maintain a registry for the services or microservices in the multiple service middlewares, and the registry is used to store attribute information of the multiple middlewares.

7. The service-based middleware integration system according to claim 5, characterized in that: The service combination module also includes: A service configuration unit, wherein the service configuration unit is used to configure parameters of services or microservices in the multiple service middlewares.

8. The service-based middleware integration system according to claim 5, characterized in that: The service combination module also includes: A service integration unit is used to set the interaction mode between the added service middleware, service or microservice and the existing service middleware, service or microservice according to a preset decision logic.

9. The service-based middleware integration system according to claim 5, characterized in that: The service combination module also includes: A service composition optimization unit is used to optimize the combination of services or microservices in a variety of service middlewares based on a reference point non-dominated sorting genetic algorithm.

10. The service-based middleware integration system according to claim 5, characterized in that: The service combination module also includes: A service calling module, which is used to create calling modes and calling methods for services or microservices in some or all of the service middlewares in a variety of service middlewares according to corresponding combinations, publish the calling modes and calling methods to a registry, and bind the calling addresses and calling methods of some or all of the services or microservices.

Images