Industrial Internet of Things platform operation and maintenance system, method, equipment and medium

Abstract

The present disclosure provides an operation and maintenance system, method, device and medium of an industrial Internet of Things platform, wherein the operation and maintenance system includes a cloud, an edge computing end, a device end and a CI / CD module, wherein the CI / CD module includes a customer environment publishing platform, a GitLab unit, a Jenkins unit and an operation and maintenance server. The present disclosure realizes one-click selection of the code branch of the customer application service to be maintained by the customer through the mutual cooperation of the customer environment publishing platform, GitLab and Jenkins and the operation and maintenance server, and automatically packages and publishes it to the specified customer environment. Under the premise of supporting cross-platform deployment, the upgrade process is simplified, the operation and maintenance complexity is reduced, and offline upgrades are supported. After the upgrade is initiated on the customer environment publishing platform, there is no need to coordinate the power-on of all edge computing ends. When the edge computing end is powered on, it can automatically discover the new version and upgrade automatically, which greatly reduces the labor cost of starting the customer factory.

Description

Technical Field

[0001] The present disclosure relates to the technical field of Internet of Things, and in particular to an operation and maintenance system, method, device and medium of an industrial Internet of Things platform. Background Art

[0002] With the rapid development of IoT technology, more and more smart devices are widely deployed to form industrial IoT platforms. These devices cover multiple fields such as industrial automation, smart city construction, and healthcare. The huge amount of data they generate requires fast or near-instant processing so that decisions can be made quickly. However, the traditional cloud computing model requires all data to be transmitted to the cloud for processing, which not only increases network latency, but may also cause the cloud server to be overloaded due to the huge amount of data.

[0003] Conventional server data acquisition methods usually perform data processing tasks on the server after acquiring device data. Due to network transmission delays, the response time for data processing often exceeds 100 milliseconds. However, customers' reverse control operations in factories often require a delay of less than 10 milliseconds.

[0004] To address these challenges, edge computing technology has emerged. It enables local data processing by deploying computing power near where the data is generated, thereby effectively reducing the time delay of data transmission and alleviating the pressure on cloud servers. However, the existing edge computing solutions bring the following challenges due to the introduction of edge computing services:

[0005] Difficult application deployment: It is difficult to deploy services in edge servers or edge gateways for the first time.

[0006] System upgrade traffic occupies a large amount of resources: Each time an edge service is upgraded, a large number of gateways are needed, resulting in a large increase in traffic costs for some customers using the external network.

[0007] Complex resource management: Since the services in the edge gateway or edge server occupy physical resources at the same time, when a service fails, it is likely to occupy a large amount of physical resources, causing all other services to fail, making it impossible to isolate and limit resources.

[0008] Long project implementation time: The conversion cycle from concept to actual application is long, which affects the rapid advancement of the project. Standardized development and deployment processes are needed to accelerate project implementation, including CI / CD (continuous integration / continuous delivery) and DevOps (development and operation integration) practices.

[0009] High system upgrade cost: Ordinary OTA (over-the-air) upgrades rely on powering on the edge gateway, which usually requires coordination with factory customers, resulting in a lot of manpower costs.

[0010] At the same time, in edge computing environments, gateway devices and industrial computers usually have limited physical resources and are numerous. Therefore, applications deployed on these edge devices need to be lightweight, that is, they occupy little storage space and consume few resources during operation. In addition, compared with the ordinary Internet, the available bandwidth of the Industrial Internet of Things is relatively limited. This requires that when upgrading edge services, the amount of data transmission should be minimized to reduce the demand for bandwidth.

[0011] At the same time, industrial Internet of Things projects are different from traditional Internet projects. Customers usually do not have operation and maintenance capabilities. The upgrade and maintenance of industrial Internet of Things platforms often require support from software providers. The large number of factories, short upgrade time window, multiple edge gateway architectures, and uncertain power-on time have greatly increased the difficulty of development and operation and maintenance, and brought high operation and maintenance costs; in edge computing scenarios, data cloud-edge transmission traffic is difficult to control and requires high security. Summary of the invention

[0012] The technical problem to be solved by the present disclosure is to overcome the defects of the prior art, such as the difficulty in operation and maintenance of industrial Internet of Things projects, high edge computing data latency, difficulty in data management and control, and limited resources on the edge computing side, and to provide an operation and maintenance system, method, equipment and medium for an industrial Internet of Things platform.

[0013] The present invention solves the above technical problems through the following technical solutions:

[0014] In a first aspect, an operation and maintenance system of an industrial Internet of Things platform is provided, wherein the industrial Internet of Things platform is deployed with a number of customer application services;

[0015] The operation and maintenance system includes a cloud, an edge computing end, a device end, and a CI / CD module;

[0016] The edge computing end is respectively connected to the device end and the cloud end in communication, and the CI / CD module is connected to the cloud end in communication;

[0017] The CI / CD module includes a customer environment publishing platform, a GitLab (a code platform) unit, a Jenkins (a continuous integration tool) unit, and an operation and maintenance server;

[0018] The cloud comprises a client server;

[0019] The customer environment publishing platform is used to record and manage the customer environment information corresponding to the customer application service;

[0020] The GitLab unit is used to manage the program code corresponding to the customer application service;

[0021] The Jenkins unit is used to configure the operation configuration file corresponding to the program code based on the customer environment information, and generate the upgrade maintenance data corresponding to the customer application service based on the program code and the operation configuration file, and transmit the upgrade maintenance data to the operation and maintenance server;

[0022] The client server is used to receive the upgrade and maintenance data, and upgrade the client application service based on the upgrade and maintenance data to achieve operation and maintenance of the industrial Internet of Things platform.

[0023] Optionally, the client application service includes a cloud application service, and the cloud is used to run the cloud application service;

[0024] The CI / CD module also includes a Kubernetes (a cloud-native computing framework) unit;

[0025] The operation and maintenance server transmits the cloud upgrade maintenance data corresponding to the cloud application service to the customer server through the Kubernetes unit to achieve the upgrade of the cloud application service.

[0026] Optionally, the client application service includes an edge application service, and the edge computing end is used to run the edge application service;

[0027] The cloud also includes KubeEdge CloudCore (the cloud-native edge computing framework’s cloud-based operating component);

[0028] The edge computing end includes KubeEdge EdgeCore (edge ​​running component of the cloud native edge computing framework) component;

[0029] The operation and maintenance server transmits the edge upgrade maintenance data corresponding to the edge application service to the customer server through the KubeEdge CloudCore component;

[0030] The client server transmits the edge upgrade maintenance data to the edge computing end through the KubeEdge EdgeCore component to implement the upgrade of the edge application service.

[0031] Optionally, the edge application service includes edge gateway service, edge application service and edge node resource management service;

[0032] Among them, the edge node resource management service is implemented based on the KubeEdge EdgeCore component.

[0033] Optionally, the edge application service includes a data collection service and a data processing service;

[0034] The edge gateway service includes at least one of a data encryption service, a data compression service, a data transmission service, and a flow control service.

[0035] Optionally, the cloud application service includes at least one of a data storage service, an online device management service, and a cloud center management service;

[0036] Among them, the cloud center management service is implemented based on the KubeEdge CloudCore component.

[0037] Optionally, the online device management service includes at least one of device authentication, device registration, device configuration, device monitoring, device alarm, and device data management.

[0038] In a second aspect, an operation and maintenance method of an industrial Internet of Things platform is provided. The operation and maintenance method of the industrial Internet of Things platform is implemented by the operation and maintenance system of the industrial Internet of Things platform described above; the operation and maintenance method comprises:

[0039] Obtain upgrade and maintenance data corresponding to customer application services;

[0040] Transmitting the upgrade maintenance data to the operation and maintenance server;

[0041] In response to a client's application service upgrade request, the upgrade maintenance data is obtained from the operation and maintenance server, and the upgrade maintenance data is transmitted to the client server to implement operation and maintenance of the industrial Internet of Things platform.

[0042] Optionally, the step of obtaining upgrade maintenance data corresponding to the customer application service includes:

[0043] Obtaining program code and customer environment information corresponding to the customer application service;

[0044] Acquire a running configuration file corresponding to the program code based on the customer environment information;

[0045] Generate upgrade maintenance data corresponding to the customer application service based on the program code and the operation configuration file.

[0046] In a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and used to run on the processor, wherein the processor implements the operation and maintenance method of the industrial Internet of Things platform described above when executing the computer program.

[0047] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the operation and maintenance method of the industrial Internet of Things platform described above is implemented.

[0048] In a fifth aspect, a computer program product is provided, including a computer program, which, when executed by a processor, implements the operation and maintenance method of the industrial Internet of Things platform described above.

[0049] On the basis of being in accordance with the common sense in the art, the above-mentioned preferred conditions can be arbitrarily combined to obtain the preferred embodiments of the present disclosure.

[0050] The positive and progressive effects of this disclosure are:

[0051] The operation and maintenance system, method, device and medium of the industrial Internet of Things platform disclosed in the present invention, through the mutual cooperation of the customer environment publishing platform, GitLab and Jenkins and the operation and maintenance server, can realize one-click selection of the code branch of the customer application service to be maintained by the customer, and automatically package and publish it to the specified customer environment. Under the premise of supporting cross-platform deployment, it simplifies the upgrade process, reduces the complexity of operation and maintenance, and supports offline upgrade. After the upgrade is initiated on the customer environment publishing platform, there is no need to coordinate the power-on of all edge computing ends. When the edge computing end is powered on, it can automatically discover the new version and upgrade automatically, which greatly reduces the labor cost of starting up the customer factory. Since the data processing task is placed on the gateway of the edge computing end, the data transmission delay is significantly reduced, and the real-time performance and response speed of the operation and maintenance system are improved.

[0052] Based on KubdEdge's support for cloud-native features, the operation and maintenance system can run customer service applications of different architectures at the same time; through Kubernetes, customer application services are deployed to the edge computing end, supporting rolling updates to ensure that customer application services remain available during the update process, ensuring the stability and reliability of customer application services during startup and operation, and realizing automatic synchronization configuration and automatic health checks. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 A first structural diagram of the operation and maintenance system of the industrial Internet of Things platform provided in Embodiment 1 of the present disclosure;

[0054] Figure 2 A second structural diagram of the operation and maintenance system of the industrial Internet of Things platform provided in Embodiment 1 of the present disclosure;

[0055] Figure 3 A first flow chart of the operation and maintenance method of the industrial Internet of Things platform provided in Embodiment 2 of the present disclosure;

[0056] Figure 4 A second flow chart of the operation and maintenance method of the industrial Internet of Things platform provided in Embodiment 2 of the present disclosure;

[0057] Figure 5 A schematic diagram of the operation and maintenance process of the operation and maintenance method of the industrial Internet of Things platform provided in Embodiment 2 of the present disclosure;

[0058] Figure 6 This is a schematic diagram of the structure of an electronic device provided in Embodiment 3 of the present disclosure. DETAILED DESCRIPTION

[0059] The present disclosure is further described below by way of examples, but the present disclosure is not limited to the scope of the examples.

[0060] Prefixes such as "first" and "second" are used in the embodiments of the present disclosure only to distinguish different description objects, and have no limiting effect on the position, order, priority, quantity or content of the described objects. The use of prefixes such as ordinal numbers to distinguish description objects in the embodiments of the present disclosure does not constitute a limitation on the described objects. For the statement of the described objects, please refer to the description in the context of the embodiments, and no unnecessary limitation should be constituted due to the use of such prefixes. In addition, in the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

[0061] In the embodiments of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0062] The following is a further explanation of the professional terms in this disclosure:

[0063] Physical resources: including computing resources (such as CPU, GPU), storage resources (memory, hard disk) and network resources (bandwidth, latency).

[0064] Resource management: involves the dynamic allocation, scheduling and recycling of resources to ensure efficient use of resources.

[0065] Data transmission delay: refers to the time interval from the generation of data to the completion of processing, which is particularly important for applications with high real-time requirements.

[0066] Containerization: Use container technology (such as Docker) to package applications and their dependencies for rapid deployment and migration.

[0067] Microservice architecture: decomposes the application into multiple small, independent services, each of which can be independently developed, deployed, and scaled.

[0068] Cloud native: An approach to building and running applications that leverages containerization, microservices, and automation to take advantage of the benefits of cloud computing.

[0069] Edge Gateway Box: A dedicated hardware device that integrates computing, storage, and network functions. It is deployed near the data source and is used to process and analyze data from IoT devices in real time to reduce latency and improve response speed, similar to a small server.

[0070] CI / CD: Continuous Integration / Continuous Delivery, which uses automated tools and processes to automatically build, test, and deploy code.

[0071] DevOps: Integration of development and operation, improving the efficiency of software development and deployment by improving the cooperation between development and operation teams.

[0072] Release platform: a platform used to manage all customer environment information and facilitate operation and maintenance to select code branches and release them to the customer production environment with one click.

[0073] Kubernetes: An open source container orchestration platform for automating the deployment, scaling, and management of containerized applications.

[0074] KubeEdge: An open source edge computing platform that extends Kubernetes capabilities to edge nodes and enables cloud-edge collaborative management.

[0075] GitLab: A complete DevOps platform that provides code hosting, CI / CD, project management and other functions.

[0076] Docker: An open source containerization platform for automating the deployment, operation, and management of applications.

[0077] Example 1

[0078] This embodiment provides an operation and maintenance system for an industrial Internet of Things platform, such as Figure 1 and Figure 2 As shown, the industrial IoT platform is deployed with several customer application services;

[0079] The operation and maintenance system includes the cloud 1, the edge computing end 2, the device end 3 and the CI / CD module 4;

[0080] The edge computing end 2 is connected to the device end 3 and the cloud end 1 in communication, and the CI / CD module 4 is connected to the cloud end 1 in communication;

[0081] The CI / CD module 4 includes a customer environment publishing platform 41, a GitLab unit 42, a Jenkins unit 43, and an operation and maintenance server 44;

[0082] The cloud 1 includes a client server 11;

[0083] The customer environment publishing platform 41 is used to record and manage customer environment information corresponding to customer application services;

[0084] The GitLab unit 42 is used to manage program codes corresponding to customer application services;

[0085] The Jenkins unit 43 is used to configure the operation configuration file corresponding to the program code based on the customer environment information, and to generate the upgrade maintenance data corresponding to the customer application service based on the program code and the operation configuration file, and to transmit the upgrade maintenance data to the operation and maintenance server 44;

[0086] The client server 11 is used to receive upgrade and maintenance data, and upgrade client application services based on the upgrade and maintenance data to achieve operation and maintenance of the industrial Internet of Things platform.

[0087] The device side refers to the physical equipment in the customer's factory, which can be any device that can communicate with the edge computing side, such as sensors, injection molding machines, die-casting machines, etc.

[0088] The edge computing end can be an edge gateway box, an industrial computer, an edge server, etc. The edge computing end is mainly used to process the operation data of the device end. Since the data processing task is placed on the edge computing end (such as an edge gateway box), the data transmission delay is significantly reduced, and the real-time performance and response speed of the operation and maintenance system are improved.

[0089] Customer application services can also be called microservices. Usually, back-end developers use compiled languages ​​such as C++, Python, and Golang to develop and implement them. They have the advantages of fast development, low cost, and small storage space.

[0090] For example, when using Golang for development, thanks to the highly optimized compiler and the compact concurrent program writing advantage supported by the language itself, each application service is less than 15MB. In addition, Golang's high performance and low resource consumption make the application run more smoothly and stably on the edge computing end.

[0091] The operation and maintenance system of the industrial Internet of Things platform of this embodiment, through the mutual cooperation of the customer environment publishing platform, GitLab unit, Jenkins unit and the operation and maintenance server, can realize one-click selection of the code branch of the customer application service to be maintained by the customer, and automatically package and publish it to the specified customer environment. It supports cross-platform deployment, simplifies the upgrade process, reduces the complexity of operation and maintenance, and supports offline upgrades. After the upgrade is initiated on the customer environment publishing platform, there is no need to coordinate the power-on of all edge computing terminals. When the edge computing terminal is powered on, it can automatically discover the new version and upgrade automatically, which greatly reduces the labor cost of starting up the customer factory. Since the data processing task is placed on the gateway of the edge computing terminal, the data transmission delay is significantly reduced, and the real-time and response speed of the operation and maintenance system are improved.

[0092] As a code repository management system, GitLab supports code version control and management. Developers submit code (i.e. the aforementioned code data) to the GitLab repository to ensure code integrity and traceability. Code review and merging are performed through GitLab's Merge Requests function to ensure code quality. After each code submission, GitLab automatically triggers the CI / CD module to start the subsequent build and test process.

[0093] The customer environment publishing platform records and manages all customer production environments, including cluster entry, release records, current service versions, system architecture, etc., and provides environment management, version management, and configuration management functions. Operation and maintenance personnel directly determine the environment to be updated on the customer environment publishing platform. Through the integration of the customer environment publishing platform and the Jenkins unit, one-click selection of code branches is achieved. Operation and maintenance personnel can select a specific code branch and then click the release button to trigger automatic packaging and deployment with one click; according to the selected release environment, the corresponding configuration files are automatically loaded, including environment variables, application configuration, etc., to ensure the normal operation of customer application services in the target environment.

[0094] Use Jenkins units to automatically compile and package the code. Define build and test steps through Jenkins Pipeline (a workflow framework) to ensure the stability and reliability of the code. By reading the Dockerfile (container file) in the code repository, Jenkins packages the compiled application into a Docker image (i.e. the aforementioned upgrade maintenance data) to ensure the portability and consistency of the application. Jenkins uploads the generated Docker image to the operation and maintenance server to ensure the security and availability of the image, and adds tags to the uploaded image to identify the version information and build time, which facilitates subsequent version management and rollback.

[0095] In an optional embodiment, the client application service includes a cloud application service, and the cloud is used to run the cloud application service;

[0096] CI / CD module 4 also includes Kubernetes unit 45;

[0097] The operation and maintenance server 44 transmits the cloud upgrade maintenance data corresponding to the cloud application service to the client server 11 through the Kubernetes unit 45 to achieve the upgrade of the cloud application service.

[0098] The Kubernetes unit enables communication between the operation and maintenance server and the cloud, and enables upgrades to cloud application services.

[0099] The customer environment publishing platform records and manages customer environment information, and is integrated with GitLab, Jenkins, the operation and maintenance Kubernetes unit, and the operation and maintenance server to form a CI / CD module, which enables the CI / CD module to have a one-click upgrade function, greatly simplifying the upgrade and deployment process and reducing operation and maintenance costs.

[0100] The operation and maintenance server transmits the cloud upgrade and maintenance data corresponding to the cloud application service to the customer server through the Kubernetes unit, thereby realizing the upgrade of the cloud application service.

[0101] Through Kubernete's Deployment (an instance) and StatefulSet (an instance) resources, customer application services are deployed to customer servers and edge computing terminals, supporting rolling updates of application services to ensure that customer application services remain available during the update process, ensuring the stability and reliability of customer application services during startup and operation, and achieving automatic synchronization of configurations and automatic health checks.

[0102] In an optional implementation, the client application service includes an edge application service, and the edge computing end is used to run the edge application service;

[0103] The cloud 1 also includes a KubeEdge CloudCore component 12;

[0104] The edge computing end 2 includes a KubeEdge EdgeCore component 21;

[0105] The operation and maintenance server 44 transmits the edge upgrade maintenance data corresponding to the edge application service to the customer server 11 through the KubeEdge CloudCore component 12;

[0106] The client server 11 transmits the edge upgrade maintenance data to the edge computing end 2 through the KubeEdge EdgeCore component 21 to achieve the upgrade of the edge application service.

[0107] like Figure 2 As shown, the edge computing end is an edge gateway box and / or an edge server, and the KubeEdge EdgeCore component can be integrated in the edge gateway box or the edge server. For example, the X86 architecture edge gateway box includes KubeEdgeEdgeCore, which can provide edge gateway services and edge application services; the ARM architecture edge gateway box includes KubeEdgeEdgeCore, which can provide edge gateway services and edge application services; the edge server includes KubeEdge EdgeCore, which can provide edge gateway services and edge application services.

[0108] The KubeEdge CloudCore component and the KubeEdge EdgeCore component work together to enable communication between the operation and maintenance server and the cloud and edge computing ends, and to upgrade edge application services.

[0109] The operation and maintenance server transmits the edge upgrade and maintenance data corresponding to the edge application service to the customer server through the KubeEdge CloudCore component; the customer server transmits the edge upgrade and maintenance data to the edge computing end through the KubeEdge EdgeCore component to achieve the upgrade of the edge application service.

[0110] Traditional Kubernetes is only suitable for managing IoT projects (i.e., customer application services) deployed purely in the cloud, and cannot manage nodes on the edge computing side. When a node on the edge computing side is offline, the Kubernetes cluster will detect that the node is offline and automatically dispatch the edge application service to other nodes, which is not suitable for edge computing scenarios. The disclosed operation and maintenance system inherits KubeEdge, and thus has offline autonomy capabilities. Even if the edge node is offline, its internal application services can be governed by KubeEdge EdgeCore and run normally.

[0111] Kubernetes does not have the ability to coordinate cloud and edge, and can only be used for IoT projects that collect and process data on the cloud server side, which results in the need to increase the transmission delay of cloud-edge communication for data processing. The disclosed operation and maintenance system supports using KubeEdge to deploy application services to the edge computing side, directly processing data on the edge computing side, reducing system latency, and meeting latency-sensitive requirements such as device reverse control.

[0112] In the traditional Kubernetes operation and maintenance process, Kubelet (node ​​management component) is large in size and occupies a lot of resources. In this disclosure, KubeEdge uses EdgeCore with a lightweight architecture to replace Kubelet, and uses a modular design to allow the shutdown of inapplicable modules. Combined with support for dynamic resource management and low-power mode, the resource overhead used to support operation and maintenance components is minimized.

[0113] Docker's layered construction and reuse technology is used in the process of generating upgrade maintenance data (also known as Docker image data). Each time the edge customer application service on the edge computing end is upgraded, a large amount of cache reuse can be done for the image layer, basic layer, intermediate layer, etc. The actual upgrade can reduce the used traffic to less than 3MB, reducing the traffic required for the upgrade, while ensuring the portability and consistency of the customer application service.

[0114] Since the data processing tasks are placed on the gateway at the edge computing end, the data transmission delay is significantly reduced, the real-time performance and response speed of the operation and maintenance system are improved, and based on the cloud-native features of KubdEdge, the operation and maintenance system can run customer service applications of different architectures at the same time.

[0115] At the same time, due to the cloud-native characteristics of Kubernetes+Docker, the operation and maintenance system can be seamlessly deployed in multiple architecture environments such as X86 (an instruction set architecture) and ARM (an instruction set architecture), ensuring consistency and compatibility on different hardware platforms.

[0116] In an optional embodiment, if Figure 2 As shown, edge application services include edge gateway services, edge application services, and edge node resource management services;

[0117] Among them, the edge node resource management service is implemented based on the KubeEdge EdgeCore component.

[0118] Specifically, edge application services include but are not limited to data collection services and data processing services. Edge gateway services include but are not limited to data encryption services, data compression services, data transmission services, and flow control services. Edge gateway services are used to provide unified gateway export services as the only channel for data transmission to ensure data security and consistency.

[0119] In an optional embodiment, the cloud application service includes at least one of a data storage service, an online device management service, and a cloud center management service;

[0120] Among them, the cloud center management service is implemented based on the KubeEdge CloudCore component.

[0121] Specifically, the online device management service includes at least one of device authentication, device registration, device configuration, device monitoring, device alarm, and device data management.

[0122] KubeEdge's EdgeCore is responsible for the resource management of edge nodes, including the dynamic allocation and recycling of computing resources, storage resources, and network resources. It works with KubeEdge's CloudCore to achieve collaborative management between the cloud center and edge nodes, supporting localized data processing and centralized management in the cloud.

[0123] At the edge computing end, a unified edge gateway service is used as the data export. The data reported to the cloud is encrypted, compressed, and the flow is controlled through the unified edge gateway service, which reduces resource consumption and improves the security and efficiency of data transmission. The unified management of the gateway service simplifies the configuration and maintenance of data transmission and enhances the overall security of the system.

[0124] After the Industrial Internet of Things platform is deployed in the customer's production environment, a network tunnel channel (such as VPN) will be deployed for subsequent Industrial Internet of Things platform upgrades. The customer environment publishing platform maintains the cluster entrances of all customer production environments. After the development and testing code (i.e. program code) is submitted to GitLab, by selecting the customer environment and code branch in the customer environment publishing platform, you can specify a one-click release update within the upgrade window allowed by the customer. Thanks to KubeEdge's offline node management technology, even if the gateway in the factory is not powered on, it will not affect the upgrade process. The upgrade image file of the customer application service will be synchronized to the image repository of the customer environment. After the gateway node is online, KubeEdge's EdgeCore will automatically notify KubeEdge's CloudCore to upgrade the customer application service.

[0125] Using a three-layer architecture of cloud, edge computing and device, the logic of data processing is decentralized to the edge gateway and / or edge server at the edge computing end close to the data source, which significantly improves the speed of data processing and makes its response time much lower than the traditional solution of processing data in the central server in the cloud. In some scenarios that require fast feedback, it is even possible to control directly at the edge computing end without interacting with the central server in the cloud, thereby achieving device control response within 10 milliseconds at the software level.

[0126] KubeEdge's CloudCore integrates some of the KubeEdge operation and maintenance management functions, and is used to deploy customer service application services on the edge computing side to the gateway or industrial computer, and is used in conjunction with the EdgeCore on the edge computing side. CloudCore is responsible for the communication and management between the cloud center and the edge nodes, provides cloud-edge collaborative management capabilities, and supports the scheduling and resource management of edge computing tasks.

[0127] When there is no need to upgrade the customer application service, the edge computing end is used to collect the initial operation data corresponding to the customer application service, and process the initial operation data into target operation data and transmit it to the cloud; the cloud is used to store the target operation data. Specifically, the initial operation data can be cleaned to obtain the target operation data.

[0128] Specifically, the cloud also includes EMQX (an open source IoT message middleware) message middleware. EMQX serves as the middleware for cloud communication in the disclosed operation and maintenance system. Different devices use independent topics to report data, achieving high concurrency in reporting data without interfering with each other.

[0129] The data storage service uses InfluxDB (an open source time series database) to store the time series data reported by the edge computing end (i.e. the target operation data mentioned above), stores the data content as the field data type, stores the device ID (identity code) as a tag, and stores data points (Point) in different formats in different measurement tables (Measurements) to speed up data query.

[0130] Common industrial Internet of Things operation and maintenance methods include: remote upgrade method based on OTA, server-side upgrade method based on Kubernetes, and upgrade method based on EdgeXFoundary (an edge computing platform).

[0131] Compared with the existing OTA-based remote upgrade method, the operation and maintenance system disclosed in the present invention has the following advantages:

[0132] a. Resource isolation and management capabilities: Traditional OTA can only remotely upgrade edge application services. However, thanks to the integration with Kubernetes and KubeEdge, this system not only has convenient upgrade capabilities, but also supports containerized deployment, which can better manage edge resource usage and isolate various application services from each other.

[0133] b. Lower development costs: Thanks to the integration with Kubernetes, it can support one-click deployment according to the deployment, and supports advanced operation and maintenance functions such as cross-platform deployment, one-click rollback, offline upgrade, etc. These functions no longer need to be redeveloped to reduce development costs.

[0134] 2. Compared with the existing Kubernetes-based server upgrade method, the disclosed operation and maintenance system has the following advantages:

[0135] a. Support offline autonomy: Traditional Kubernetes is only suitable for managing IoT projects deployed purely in the cloud, and cannot manage edge nodes. When an edge node is offline, the Kubernetes cluster will detect that the node is offline and automatically dispatch the application service to other nodes, which is not suitable for edge computing scenarios. This system inherits KubeEdge and therefore has offline autonomy. Even if the edge node is offline, its internal application services can be governed by KubeEdgeEdgeCore and run normally.

[0136] b. Support cloud-edge coordination and lower latency: Kubernetes does not have cloud-edge coordination capabilities and can only be used for IoT projects that collect and process data on the server side, which results in the need to increase the transmission delay of cloud-edge communication for data processing. This system supports using KubeEdge to deploy application services to the edge side, directly process data on the edge side, reduce system latency, and meet latency-sensitive requirements such as device reverse control.

[0137] 3. The disclosed operation and maintenance system has the following advantages compared with the existing upgrade method based on EdgeXFoundary:

[0138] a. Stronger cloud-edge coordination capabilities: KubeEdge can achieve seamless collaborative management of the cloud and the edge. Users can uniformly manage applications and devices on edge nodes on the cloud. Although EdgeX Foundry supports a variety of southbound protocols, it does not have the capabilities of intelligent edge systems such as cloud-side collaboration and management of edge applications and devices.

[0139] b. Easier development: KubeEdge allows developers to write regular applications based on HTTP (Hypertext Transfer Protocol) or MQTT (Message Queue Telemetry Transport Protocol), containerize them, and then run the applications in any more suitable location, Edge or Cloud. Although EdgeX Foundry provides data filtering, format conversion, and rule engines, it is not as good as KubeEdge in simplifying development.

[0140] c. Stronger O&M capabilities: KubeEdge is built on Kubernetes. Users can orchestrate applications, manage devices, and monitor application and device status on Edge nodes, just like in traditional Kubernetes clusters. Although EdgeX Foundry provides an application service layer, it does not have native support for Kubernetes.

[0141] As for the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only illustrative, in which the units described as separate components may or may not be physically separated, and the components as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution.

[0142] Example 2

[0143] This embodiment provides an operation and maintenance method for an industrial Internet of Things platform, such as Figure 3 As shown, the operation and maintenance method of the industrial Internet of Things platform is implemented by the operation and maintenance system of the industrial Internet of Things platform in the embodiment; the operation and maintenance method includes:

[0144] S1. Obtain upgrade and maintenance data corresponding to customer application services.

[0145] S2. Transmit the upgrade and maintenance data to the operation and maintenance server.

[0146] S3. In response to the customer's application service upgrade request, the upgrade and maintenance data is obtained from the operation and maintenance server, and the upgrade and maintenance data is transmitted to the customer server to realize the operation and maintenance of the industrial Internet of Things platform.

[0147] Specifically, the industrial Internet of Things platform is deployed with a number of customer application services; the operation and maintenance system includes the cloud, edge computing, device and CI / CD modules; the CI / CD modules include the customer environment publishing platform, GitLab unit, Jenkins unit and operation and maintenance server; the cloud includes the customer server; the customer environment publishing platform is used to record and manage the customer environment information corresponding to the customer application service; the GitLab unit is used to manage the program code corresponding to the customer application service; the Jenkins unit is used to configure the running configuration file corresponding to the program code based on the customer environment information, and generate the upgrade and maintenance data corresponding to the customer application service based on the program code and the running configuration file, and transmit the upgrade and maintenance data to the operation and maintenance server; the customer server is used to receive the upgrade and maintenance data, and upgrade the customer application service based on the upgrade and maintenance data to realize the operation and maintenance of the industrial Internet of Things platform.

[0148] The operation and maintenance method of the industrial Internet of Things platform of this embodiment is implemented by the operation and maintenance system of the industrial Internet of Things platform in the embodiment. The operation and maintenance method has the same working principle as the operation and maintenance system. For details, please refer to the contents disclosed in Example 1, which will not be repeated here.

[0149] In an optional embodiment, if Figure 4 As shown, the above step S1 includes:

[0150] S11. Obtain the program code and customer environment information corresponding to the customer application service.

[0151] S12. Obtaining a running configuration file corresponding to the program code based on the customer environment information.

[0152] S13. Generate upgrade maintenance data corresponding to the customer application service based on the program code and the operation configuration file.

[0153] Specifically, the program code corresponding to the customer application service is obtained through the GitLab unit, the customer environment information corresponding to the customer application service is obtained through the customer environment publishing platform, the running configuration file corresponding to the program code is obtained through the Jenkins unit, and the upgrade and maintenance data corresponding to the customer application service is generated based on the program code and the running configuration file.

[0154] Combine the following Figure 5 , further explaining the operation and maintenance method of the industrial Internet of Things platform disclosed in the present invention:

[0155] like Figure 5 As shown in the figure, GitLab unit is used as the code repository management system to support code version control and management. Developers submit code (i.e. the aforementioned code data) to the GitLab repository to ensure the integrity and traceability of the code. Through GitLab's Merge Requests function, code review and merging are performed to ensure code quality; after each code submission, GitLab automatically triggers the CI / CD module to start the subsequent building and testing process.

[0156] Different customers correspond to different customer production environments. For example, customer A corresponds to customer environment A, and customer B corresponds to customer environment B. The customer environment publishing platform records and manages all customer production environments, including cluster entry, release records, current service versions, system architecture, etc., and provides environment management, version management, and configuration management functions. Operation and maintenance personnel directly determine the environment to be updated on the customer environment publishing platform. Through the integration of the customer environment publishing platform and the Jenkins unit, one-click selection of code branches is achieved. Operation and maintenance personnel can select a specific code branch and then click the release button to trigger automatic packaging and deployment with one click; according to the selected release environment, the corresponding configuration files are automatically loaded, including environment variables, application configuration, etc., to ensure the normal operation of customer application services in the target environment.

[0157] Use Jenkins units to automatically compile and package the code. Define build and test steps through Jenkins Pipeline to ensure the stability and reliability of the code. By reading the Dockerfile (container file) in the code repository, Jenkins packages the compiled application into a Docker image (i.e. the aforementioned upgrade maintenance data) to ensure the portability and consistency of the application. Jenkins uploads the generated Docker image to the operation and maintenance server to ensure the security and availability of the image, and adds tags to the uploaded image to identify the version information and build time, which facilitates subsequent version management and rollback.

[0158] Based on network tunneling, the images in the operation and maintenance server are synchronized to the customer server in the cloud, and the customer application services in the cloud and the edge are updated; the images are used to reduce the traffic required for subsequent updates of the edge computing gateway in the customer environment. Through Kubernetes' resource quotas (ResourceQuotas) and limit ranges (LimitRanges), the resource usage in the cluster is managed to ensure efficient use of resources.

[0159] Use KubeEdge to automatically notify edge nodes on the edge computing side of new customer application service update events, realize cloud-edge collaborative management and localized data processing. KubeEdge supports different architectures such as ARM and X86, and realizes seamless deployment across platforms. Through Kubernetes' Deployment and StatefulSet resources, customer application services are automatically deployed to customer servers and edge gateways on the edge computing side, supporting rolling updates to ensure that customer applications remain available during the update process. Use ConfigMap (a way to store data) and Secret (a way to store data) resources to synchronize application configuration files and sensitive information to ensure that the application is correctly configured in the target environment. Monitor the health status of the application through Liveness and Readiness probes to ensure the stability and reliability of the application during startup and operation, and realize automatic health checks.

[0160] The operation and maintenance method of the industrial Internet of Things platform disclosed in the present invention is based on the containerization technology of KubeEdge. The customer application services on the edge computing end can share the basic layer after containerization, which greatly reduces the consumption of storage space by the customer application services. Through lightweight container technology, resource management and utilization are optimized to ensure efficient operation under limited computing and storage resources, reduce hardware requirements, and containerization technology enables resource isolation of customer application services on the edge computing end, so that the system on the edge computing end will not affect other services due to the loss of control of a certain service.

[0161] The present invention combines the customer environment publishing platform, GitLab, Jenkins and operation and maintenance server to realize one-click selection of the code branch of the customer application service to be maintained by the customer, and automatically packages and publishes it to the specified customer environment. It supports cross-platform deployment, simplifies the upgrade process, reduces the complexity of operation and maintenance, and supports offline upgrades. After the upgrade is initiated on the customer environment publishing platform, there is no need to coordinate the power-on of all edge computing terminals. When the edge computing terminal is powered on, it can automatically discover the new version and upgrade automatically, which greatly reduces the labor cost of starting up the customer factory. The Docker technology is used to ensure the portability and consistency of customer application services and reduce the traffic required for upgrades.

[0162] Based on KubdEdge's support for cloud-native features, the operation and maintenance system can run customer service applications of different architectures at the same time; through Kubernetes, customer application services are deployed to the edge computing end, supporting rolling updates to ensure that customer application services remain available during the update process, ensuring the stability and reliability of customer application services during startup and operation, and realizing automatic synchronization configuration and automatic health checks.

[0163] In an optional implementation, the operation and maintenance method of the industrial Internet of Things platform also includes: collecting initial operation data corresponding to the customer application service, and processing the initial operation data into target operation data and transmitting it to the cloud; storing the target operation data in the cloud to realize the operation and maintenance of the industrial Internet of Things platform.

[0164] When there is no need to upgrade the customer application service, the edge computing end is used to collect the initial operation data corresponding to the customer application service, and process the initial operation data into target operation data and transmit it to the cloud; the cloud is used to store the target operation data. Specifically, the initial operation data can be cleaned to obtain the target operation data.

[0165] Example 3

[0166] Figure 6 This is a schematic diagram of the structure of an electronic device shown in an example embodiment of the present disclosure. The electronic device includes a memory, a processor, and a computer program stored in the memory and used to run on the processor. When the processor executes the computer program, the operation and maintenance method of the industrial Internet of Things platform in the above embodiment is implemented. Figure 6 The electronic device 80 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0167] like Figure 6 As shown, the electronic device 80 may be in the form of a general-purpose computing device, for example, it may be a server device. The components of the electronic device 80 may include, but are not limited to: at least one processor 81, at least one memory 82, and a bus 83 connecting different system components (including the memory 82 and the processor 81).

[0168] The bus 83 includes a data bus, an address bus, and a control bus.

[0169] The memory 82 may include a volatile memory, such as a random access memory (RAM) 821 and / or a cache memory 822 , and may further include a read-only memory (ROM) 823 .

[0170] The memory 82 may also include a program tool 825 (or utility) having a set (at least one) of program modules 824, such program modules 824 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0171] The processor 81 executes various functional applications and data processing by running the computer programs stored in the memory 82, such as the operation and maintenance method of the industrial Internet of Things platform provided in the above embodiment.

[0172] The electronic device 80 can also communicate with one or more external devices 84 (e.g., keyboards, pointing devices, etc.). This communication can be performed through an input / output (I / O) interface 85. In addition, the electronic device 80 can also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs) and / or public networks, such as the Internet) through a network adapter 86. As shown in the figure, the network adapter 86 communicates with other modules of the electronic device 80 through a bus 83. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 80, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, etc.

[0173] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into multiple units / modules to be embodied.

[0174] Example 4

[0175] The embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the operation and maintenance method of the industrial Internet of Things platform provided in the above embodiment 2 is implemented.

[0176] The readable storage medium may include but is not limited to: a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device or any suitable combination of the above.

[0177] Example 5

[0178] The embodiments of the present disclosure also provide a computer program product, including a computer program, which, when executed by a processor, implements the operation and maintenance method of the industrial Internet of Things platform provided in the above-mentioned embodiment 2.

[0179] Among them, the program code for executing the computer program product of the present disclosure can be written in any combination of one or more programming languages, and the program code can be executed completely on the user device, partially on the user device, as an independent software package, partially on the user device and partially on a remote device, or completely on the remote device.

[0180] Although the specific embodiments of the present disclosure are described above, those skilled in the art should understand that this is only an example, and the protection scope of the present disclosure is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present disclosure, but these changes and modifications all fall within the protection scope of the present disclosure.

Claims

1. An operation and maintenance system for an industrial Internet of Things platform, characterized in that: The industrial Internet of Things platform is deployed with several customer application services; The operation and maintenance system includes a cloud, an edge computing end, a device end, and a CI / CD module; The edge computing end is respectively connected to the device end and the cloud end in communication, and the CI / CD module is connected to the cloud end in communication; The CI / CD module includes a customer environment publishing platform, a GitLab unit, a Jenkins unit, and an operation and maintenance server; The cloud comprises a client server; The customer environment publishing platform is used to record and manage the customer environment information corresponding to the customer application service; The GitLab unit is used to manage the program code corresponding to the customer application service; The Jenkins unit is used to configure the operation configuration file corresponding to the program code based on the customer environment information, and generate the upgrade maintenance data corresponding to the customer application service based on the program code and the operation configuration file, and transmit the upgrade maintenance data to the operation and maintenance server; The client server is used to receive the upgrade and maintenance data, and upgrade the client application service based on the upgrade and maintenance data to achieve operation and maintenance of the industrial Internet of Things platform.

2. The operation and maintenance system according to claim 1, characterized in that: The client application service includes a cloud application service, and the cloud is used to run the cloud application service; The CI / CD module also includes a Kubernetes unit; The operation and maintenance server transmits the cloud upgrade maintenance data corresponding to the cloud application service to the customer server through the Kubernetes unit to achieve the upgrade of the cloud application service.

3. The operation and maintenance system according to claim 1, characterized in that: The client application service includes an edge application service, and the edge computing end is used to run the edge application service; The cloud also includes KubeEdge CloudCore components; The edge computing end includes KubeEdge EdgeCore components; The operation and maintenance server transmits the edge upgrade maintenance data corresponding to the edge application service to the customer server through the KubeEdge CloudCore component; The client server transmits the edge upgrade maintenance data to the edge computing end through the KubeEdge EdgeCore component to implement the upgrade of the edge application service.

4. The operation and maintenance system according to claim 3, characterized in that: The edge application services include edge gateway services, edge application services and edge node resource management services; Among them, the edge node resource management service is implemented based on the KubeEdge EdgeCore component.

5. The operation and maintenance system according to claim 4, characterized in that: The edge application services include data collection services and data processing services; The edge gateway service includes at least one of a data encryption service, a data compression service, a data transmission service, and a flow control service.

6. The operation and maintenance system according to claim 3, characterized in that: The cloud application service includes at least one of a data storage service, an online device management service, and a cloud center management service; Among them, the cloud center management service is implemented based on the KubeEdge CloudCore component.

7. The operation and maintenance system according to claim 6, characterized in that: The online device management service includes at least one of device authentication, device registration, device configuration, device monitoring, device alarm, and device data management.

8. An operation and maintenance method for an industrial Internet of Things platform, characterized in that: The operation and maintenance method of the industrial Internet of Things platform is implemented by the operation and maintenance system of the industrial Internet of Things platform according to any one of claims 1 to 7; the operation and maintenance method comprises: Obtain upgrade and maintenance data corresponding to customer application services; Transmitting the upgrade maintenance data to the operation and maintenance server; In response to a client's application service upgrade request, the upgrade maintenance data is obtained from the operation and maintenance server, and the upgrade maintenance data is transmitted to the client server to implement operation and maintenance of the industrial Internet of Things platform.

9. The operation and maintenance method according to claim 8, characterized in that: The step of obtaining the upgrade maintenance data corresponding to the client application service comprises: Obtaining program code and customer environment information corresponding to the customer application service; Acquire a running configuration file corresponding to the program code based on the customer environment information; Generate upgrade maintenance data corresponding to the customer application service based on the program code and the operation configuration file.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and used to run on the processor, characterized in that: When the processor executes the computer program, the operation and maintenance method of the industrial Internet of Things platform described in claim 8 or 9 is implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the operation and maintenance method of the industrial Internet of Things platform described in claim 8 or 9 is implemented.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the operation and maintenance method of the industrial Internet of Things platform described in claim 8 or 9 is implemented.

Images