Operation and Maintenance System, Method, Device and Medium of Industrial Internet of Things Platform

Abstract

The present disclosure provides an operation and maintenance system, method, device and medium for an industrial Internet of Things platform. The operation and maintenance system includes a cloud, an edge computing end, a device end and a CI / CD module. The CI / CD module includes a customer environment release platform, a GitLab unit, a Jenkins unit and an operation and maintenance server. Through the mutual cooperation of the customer environment release platform, GitLab, Jenkins and the operation and maintenance server, the present disclosure realizes one-key selection of the code branch of the customer application service to be maintained by the customer, automatically packages and releases it to the specified customer environment. On the premise of supporting cross-platform deployment, the upgrade process is simplified, the operation and maintenance complexity is reduced, and offline upgrade is supported. After the upgrade is initiated on the customer environment release platform, it is not necessary to coordinate the power-on and startup of all edge computing ends. When the edge computing end is powered on, it can automatically detect the new version and automatically upgrade, greatly reducing the labor cost of powering on the customer factory.

Description

Technical Field

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

[0002] With the rapid development of Internet of Things technologies, more and more intelligent devices have been widely deployed, forming an industrial Internet of Things platform. 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 in order to make decisions 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 also may cause an excessive burden on the cloud server due to the large amount of data.

[0003] After obtaining device data by conventional server data acquisition methods, data processing tasks are usually executed on the server. Due to the time delay of network transmission, the response time of data processing often exceeds 100 milliseconds. However, the reverse control operations of customers in the factory often require a delay within 10 milliseconds.

[0004] To address these challenges, edge computing technology has emerged. By deploying computing capabilities near the location where data is generated, it enables local processing of data, thus effectively reducing the time delay of data transmission and alleviating the pressure on the cloud server. However, the existing edge computing solutions bring the following challenges due to the introduction of edge-side computing services:

[0005] Difficult application deployment: The initial deployment of services in edge servers or edge gateways is relatively difficult.

[0006] High resource consumption during system upgrade: Each time the edge-side service is upgraded, due to the large number of gateways, the upgrade requires a large amount of traffic, resulting in a significant increase in traffic costs for some customers using the external network.

[0007] Complex resource management: Since the services in edge gateways or edge servers simultaneously occupy physical resources, when an abnormal situation occurs in a certain service, it is very likely to occupy a large amount of physical resources, causing all other services to be abnormal and unable to achieve resource isolation and limitation.

[0008] Long project implementation time: The conversion cycle from concept to actual application is relatively long, which affects the rapid progress of the project. Standardized development and deployment processes are required to accelerate project implementation, including CI / CD (Continuous Integration / Continuous Delivery) and DevOps (Development and Operations Integration) practices.

[0009] High system upgrade cost: Ordinary OTA (Over-the-Air) upgrades rely on the power-on and startup of edge gateways, usually requiring coordination with factory customers to cooperate, resulting in a lot of labor costs.

[0010] Meanwhile, in the edge computing environment, gateway devices and industrial computers usually have limited physical resources and a large number of them. Therefore, the applications deployed on these edge devices need to have lightweight features, 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 the services at the edge, 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 the operation and maintenance capabilities, and the upgrade and maintenance of industrial Internet of Things platforms often need to be supported by the software providers. Problems such as a large number of factories, short upgrade time windows, multiple edge gateway architectures, and uncertain power-on times have greatly increased the difficulty of development and operation and maintenance, bringing high operation and maintenance costs; in the edge computing scenario, the data cloud-edge transmission traffic is difficult to control, and the security requirements are high. Summary of the Invention

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

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

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

[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 communicatively connected to the device end and the cloud, and the CI / CD module is communicatively connected to the cloud;

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

[0018] The cloud includes a customer server;

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

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

[0021] The Jenkins unit is used to configure the running configuration file corresponding to the program code based on the customer environment information, 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;

[0022] 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.

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

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

[0025] 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 to realize the upgrade of the cloud application service.

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

[0027] The cloud further includes a KubeEdge CloudCore (a cloud-side running component of the cloud-native edge computing framework) component;

[0028] The edge computing terminal includes a KubeEdge EdgeCore (an edge-side running component of the cloud-native edge computing framework) component;

[0029] 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;

[0030] The customer server transmits the edge upgrade and maintenance data to the edge computing terminal through the KubeEdge EdgeCore component to realize the upgrade of the edge application service.

[0031] Optionally, the edge application service includes an edge gateway service, an edge application service, and an 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 traffic 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 warning, and device data management.

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

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

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

[0041] In response to a customer application service upgrade request, obtain the upgrade and maintenance data from the operation and maintenance server, and transmit the upgrade and maintenance data to the customer server to implement the operation and maintenance of the industrial Internet of Things platform.

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

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

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

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

[0046] In a third aspect, an electronic device is provided, including a memory, a processor, and a computer program stored on 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 described above is implemented.

[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] 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 conforming to common knowledge in the art, the above preferred conditions can be combined arbitrarily to obtain various preferred examples of the present disclosure.

[0050] The positive and progressive effects of the present disclosure are as follows:

[0051] The operation and maintenance system, method, device and medium of the industrial Internet of Things platform of the present disclosure, through the mutual cooperation of the customer environment release platform, GitLab, Jenkins and the operation and maintenance server, realizes one-key selection of the code branch of the customer application service to be maintained by the customer, and automatically packages and releases it to the specified customer environment. On the premise of supporting cross-platform deployment, the upgrade process is simplified, the operation and maintenance complexity is reduced, and offline upgrade is supported. After the upgrade is initiated on the customer environment release platform, it is not necessary to coordinate the power-on and startup of all edge computing terminals. When the edge computing terminal is powered on, it can automatically detect the new version and automatically upgrade, greatly reducing the labor cost of the customer factory startup; 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 performance and response speed of the operation and maintenance system are improved.

[0052] Based on the cloud-native characteristics supported by KubdEdge, the operation and maintenance system can run customer service applications with different architectures at the same time; through Kubernetes, the customer application service is deployed to the edge computing terminal, supporting rolling updates to ensure the availability of the customer application service during the update process, and ensuring the stability and reliability of the customer application service during startup and operation, realizing automatic synchronization of configurations and automatic health checks. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 The first structural schematic 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 The second structural schematic 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 The first flowchart of the operation and maintenance method of the industrial Internet of Things platform provided in Embodiment 2 of the present disclosure;

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

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

[0058] Figure 6 Schematic diagram of the structure of the electronic device provided in Embodiment 3 of the present disclosure. Detailed implementation manners

[0059] The present disclosure will be further described below by way of embodiments, but the present disclosure is not limited thereto.

[0060] In the embodiments of the present disclosure, prefix words such as "first" and "second" are only used to distinguish different described objects, and have no restrictive effect on the position, order, priority, quantity or content of the described objects. The use of ordinal numbers and other prefix words for distinguishing described objects in the embodiments of the present disclosure does not constitute a limitation on the described objects. For the statements of the described objects, refer to the descriptions in the context of the embodiments, and no redundant limitation should be formed due to the use of such prefix words. In addition, in the description of this embodiment, unless otherwise specified, the meaning of "a 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 comply with the provisions of relevant laws and regulations and do not violate public order and good customs.

[0062] The following further explains the professional terms in the present disclosure:

[0063] Physical resources: include computing resources (such as CPUs, GPUs), storage resources (memory, hard disks), and network resources (bandwidth, latency).

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

[0065] Data transmission latency: 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: uses container technology (such as Docker) to package applications and their dependencies to achieve rapid deployment and migration.

[0067] Microservices architecture: decomposes an application into multiple small and independent services, and each service can be developed, deployed and scaled independently.

[0068] Cloud native: a method of building and running applications that takes advantage of containerization, microservices and automation to fully utilize the advantages of cloud computing.

[0069] Edge gateway box: a dedicated hardware device integrating computing, storage and network functions. It is deployed near the data source and is used to process and analyze data from Internet of Things devices in real time to reduce latency and improve response speed, similar to a small server.

[0070] CI / CD: Continuous Integration / Continuous Delivery, which realizes the automatic building, testing, and deployment of code through automated tools and processes.

[0071] DevOps: Development and Operations integration, which improves the efficiency of software development and deployment by enhancing the cooperation between development and operations teams.

[0072] Release platform: A platform for managing all customer environment information, facilitating the operation and maintenance team to select code branches with one click and release them to the customer production environment.

[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 the capabilities of Kubernetes to edge nodes, enabling cloud-edge collaborative management.

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

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

[0077] Embodiment 1

[0078] This embodiment provides an operation and maintenance system for an industrial Internet of Things platform, as Figure 1 and Figure 2 shown, where several customer application services are deployed on the industrial Internet of Things platform;

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

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

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

[0082] The cloud end 1 includes a customer server 11;

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

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

[0085] The Jenkins unit 43 is used to configure the running configuration file corresponding to the program code based on the customer environment information, 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 44;

[0086] The customer server 11 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.

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

[0088] The edge computing side can be an edge gateway box, an industrial control computer, an edge server, etc. The edge computing side is mainly used to process the operation data of the device side. Since the data processing task is placed on the edge computing side (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] The customer application service can also be called a microservice. Usually, backend developers use compiled languages such as C++, Python, and Golang to develop and implement it, which has the advantages of fast development, low cost, and small storage space occupation.

[0090] For example, when developed using Golang, due to the highly optimized compiler and the advantage of compact writing of concurrent programs supported by the language itself, each application service is less than 15MB, and the high performance and low resource consumption characteristics of Golang make the application run more smoothly and stably on the edge computing side.

[0091] The operation and maintenance system of the industrial Internet of Things platform in this embodiment realizes one-key selection of the code branch of the customer application service to be maintained by the customer, automatically packages and publishes it to the specified customer environment through the cooperation of the customer environment release platform, GitLab unit, Jenkins unit, and operation and maintenance server. On the premise of supporting cross-platform deployment, the upgrade process is simplified, the operation and maintenance complexity is reduced, and offline upgrade is supported. After the upgrade is initiated on the customer environment release platform, it is not necessary to coordinate the power-on of all edge computing sides. When the edge computing side is powered on, it can automatically detect the new version and upgrade automatically, greatly reducing the labor cost of powering on in the customer factory; since the data processing task is placed on the gateway of the edge computing side, the data transmission delay is significantly reduced, and the real-time performance and response speed of the operation and maintenance system are improved.

[0092] The GitLab unit, as a code repository management system, supports version control and management of code. Developers submit code (i.e., the aforementioned code data) to the GitLab repository to ensure the integrity and traceability of the code. Through the Merge Requests function of GitLab, code review and merging are carried out to ensure code quality. After each code submission, GitLab automatically triggers the CI / CD module to start the subsequent build and test processes.

[0093] The customer environment release platform records and manages all customer production environments, including cluster entrances, release records, current service versions, system architectures, etc., and provides environment management, version management, and configuration management functions. Operations personnel directly determine the environment to be updated and released on the customer environment release platform. Through the integration of the customer environment release platform and the Jenkins unit, one-click selection of code branches is achieved. Operations 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 configurations, etc., to ensure the normal operation of the customer application service in the target environment.

[0094] The Jenkins unit is used to achieve automatic compilation and packaging of code. Through Jenkins Pipeline (a workflow framework), build and test steps are defined 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 and maintenance data) to ensure the portability and consistency of the application. Jenkins uploads the generated Docker image to the operations server to ensure the security and availability of the image, and at the same time adds tags to the uploaded image to identify version information and build time for convenient subsequent version management and rollback.

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

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

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

[0098] Through the Kubernetes unit, communication between the operations server and the cloud is achieved, and the upgrade of the cloud application service is realized.

[0099] The customer environment release platform records and manages customer environment information. After integrating with GitLab, Jenkins, and the operation and maintenance Kubernetes units and operation and maintenance servers, it forms a CI / CD module, enabling the CI / CD module to have a one-click upgrade function, greatly simplifying the upgrade and deployment process, and reducing the 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 the Deployment (an instance) and StatefulSet (an instance) resources of Kubernetes, the customer application service is deployed to the customer server and the edge computing end, supporting the rolling update of the application service, ensuring the availability of the customer application service during the update process, ensuring the stability and reliability of the customer application service during startup and operation, and realizing automatic configuration synchronization and automatic health check.

[0102] In an optional implementation manner, the customer 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 the KubeEdge CloudCore component 12;

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

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

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

[0107] As Figure 2 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 and can provide edge gateway services and edge application services; the ARM architecture edge gateway box includes KubeEdgeEdgeCore and can provide edge gateway services and edge application services; the edge server includes KubeEdge EdgeCore and 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, the cloud, and the edge computing side, and to upgrade the edge application service.

[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 side through the KubeEdge EdgeCore component to upgrade the edge application service.

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

[0111] Kubernetes does not have the ability of cloud-edge coordination and can only be used for Internet of Things projects that collect and process data on the cloud side, resulting in an increase in the transmission delay of cloud-edge communication for data processing. The operation and maintenance system of the present disclosure supports deploying application services to the edge computing side using KubeEdge, directly performing data processing on the edge computing side, reducing system latency, and meeting latency-sensitive requirements such as device reverse control.

[0112] During the operation and maintenance process of traditional Kubernetes, Kubelet (node management component) is large in size and high in resource occupancy. In the present disclosure, KubeEdge uses EdgeCore with a lightweight architecture to replace Kubelet, and uses a modular design to allow disabling inapplicable modules. Combining dynamic resource management and support for low-power modes, the resource overhead used to support the operation and maintenance components is minimized.

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

[0114] Since the data processing tasks are carried out on the gateway at the edge computing side, the data transmission latency is significantly reduced, and the real-time performance and response speed of the operation and maintenance system are improved. Moreover, based on the cloud-native characteristics supported by KubdEdge, the operation and maintenance system can run customer service applications with different architectures simultaneously.

[0115] At the same time, due to the cloud-native characteristics of Kubernetes + Docker, the operation and maintenance system can be seamlessly deployed in multi-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 implementation, as Figure 2 shown, the 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, the edge application services include but are not limited to data collection services and data processing services. The edge gateway services include but are not limited to data encryption services, data compression services, data transmission services, and traffic control services. The edge gateway services are used to provide a unified gateway egress service, serving as the only channel for data transmission to ensure data security and consistency.

[0119] In an optional implementation, the cloud application services include at least one of data storage services, online device management services, and cloud center management services;

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

[0121] Specifically, the online device management services include at least one of device authentication, device registration, device configuration, device monitoring, device alerting, 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. Used in conjunction with KubeEdge's CloudCore, it realizes the collaborative management between the cloud center and edge nodes, supporting local data processing and centralized management in the cloud.

[0123] Using a unified edge gateway service as the data egress at the edge computing side, encrypting, compressing, and controlling the traffic of the data reported to the cloud through the unified edge gateway service, reducing resource consumption, and improving 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 the ability of cloud-edge coordination and can only be used for IoT projects with server-side data collection and processing, resulting in an increase in transmission latency for cloud-edge communication in data processing. This system supports deploying application services to the edge side using KubeEdge and directly performing data processing at the edge side, reducing system latency and meeting latency-sensitive requirements such as device reverse control.

[0137] 3. The operation and maintenance system of the present disclosure has the following advantages compared with the existing upgrade method based on EdgeX Foundary:

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

[0139] b. Easier development: KubeEdge allows developers to write conventional applications based on HTTP (HyperText Transfer Protocol) or MQTT (Message Queuing Telemetry Transport Protocol), containerize them, and then run the applications at a more suitable location in either Edge (edge) or Cloud (cloud). Although EdgeX Foundry provides data filtering, format conversion, and a rules engine, it is not as good as KubeEdge in simplifying development.

[0140] c. More powerful operation and maintenance capabilities: KubeEdge is built on Kubernetes. Users can orchestrate applications, manage devices, and monitor the status of applications and devices on Edge nodes just like in a traditional Kubernetes cluster. Although EdgeX Foundry provides an application service layer, it does not have native Kubernetes support.

[0141] For the system embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial descriptions of the method embodiments. The system embodiments described above are only illustrative. The units described as separate components may or may not be physically separated. The components as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the present disclosure.

[0142] Embodiment 2

[0143] This embodiment provides an operation and maintenance method for an industrial Internet of Things platform, asFigure 3 As shown in the figure, 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 the upgrade and maintenance data corresponding to the customer application service.

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

[0146] S3. In response to the customer application service upgrade request, obtain the upgrade and maintenance data from the operation and maintenance server, and transmit the upgrade and maintenance data to the customer server to implement the operation and maintenance of the industrial Internet of Things platform.

[0147] Specifically, several customer application services are deployed on the industrial Internet of Things platform; the operation and maintenance system includes a cloud end, an edge computing end, a device end, and a CI / CD module; the CI / CD module includes a customer environment release platform, a GitLab unit, a Jenkins unit, and an operation and maintenance server; the cloud end includes a customer server; the customer environment release 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, 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 implement the operation and maintenance of the industrial Internet of Things platform.

[0148] The operation and maintenance method of the industrial Internet of Things platform in this embodiment is implemented by the operation and maintenance system of the industrial Internet of Things platform in the embodiment. The working principles of the operation and maintenance method and the operation and maintenance system are the same. For details, refer to the content disclosed in Embodiment 1, and will not be elaborated here.

[0149] In an optional implementation manner, as Figure 4 shown, the above step S1 includes:

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

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

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

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

[0154] The following combines Figure 5 to further explain the operation and maintenance method of the industrial Internet of Things platform of the present disclosure:

[0155] As Figure 5 shown, use the GitLab unit as a code repository management system to support the version control and management of code. Developers submit the code (i.e., the aforementioned code data) to the GitLab repository to ensure the integrity and traceability of the code. Through the Merge Requests function of GitLab, conduct code review and merging to ensure code quality; after each code submission, GitLab automatically triggers the CI / CD module to start the subsequent build and test processes.

[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 release platform records and manages all customer production environments, including cluster entry, release records, current service version, system architecture, etc., and provides environment management, version management, and configuration management functions. The operation and maintenance personnel directly determine the environment to be updated and released on the customer environment release platform. Through the integration of the customer environment release platform and the Jenkins unit, one-click selection of code branches is achieved. The 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 configurations, etc., to ensure the normal operation of the customer application service in the target environment.

[0157] Use the Jenkins unit to achieve automatic compilation and packaging of code. Through the Jenkins Pipeline, define the build and test steps 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 and 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 at the same time adds tags to the uploaded image to identify the version information and build time for convenient subsequent version management and rollback.

[0158] Synchronize the images in the operation and maintenance server to the customer servers in the cloud based on network tunneling, update the cloud customer application services, and update the edge customer application services; reduce the traffic required for subsequent updates of the edge computing end gateways in the customer environment through the images. Manage the resource usage in the cluster through the ResourceQuotas and LimitRanges of Kubernetes to ensure the efficient utilization of resources.

[0159] Use KubeEdge to automatically notify the edge nodes at the edge computing end of new customer application service update events, realizing cloud-edge collaborative management and local processing of data. KubeEdge supports different architectures such as ARM and X86, enabling seamless cross-platform deployment. Through the Deployment and StatefulSet resources of Kubernetes, automatically deploy the customer application services to the customer servers and edge gateways at the edge computing end, supporting rolling updates to ensure the availability of customer applications during the update process. Use ConfigMap (a way to store data) and Secret (a way to store data) resources to synchronize the configuration files and sensitive information of the applications to ensure the correct configuration of the applications in the target environment. Through Liveness and Readiness probes, monitor the health status of the applications to ensure the stability and reliability of the applications during startup and operation, realizing automatic health checks.

[0160] The operation and maintenance method of the industrial Internet of Things platform of the present disclosure is based on the containerization technology of KubeEdge. After the customer application services at the edge computing end are containerized, they can share the basic layer, greatly reducing 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, reducing the requirements for hardware, and the containerization technology enables resource isolation of the customer application services at the edge computing end, so that the system at the edge computing end will not be affected by the out-of-control of a certain service and affect other services.

[0161] The present disclosure combines the customer environment release platform, GitLab, Jenkins, and the operation and maintenance server to realize one-key selection of the code branches of the customer application services to be maintained by the customer, and automatically package and release them to the specified customer environment. On the premise of supporting cross-platform deployment, the upgrade process is simplified, the operation and maintenance complexity is reduced, and offline upgrade is supported. After the upgrade is initiated on the customer environment release platform, it is not necessary to coordinate the power-on and startup of all edge computing ends. When the edge computing end is powered on, it can automatically discover the new version and automatically upgrade, greatly reducing the labor cost of powering on the customer factory; adopting Docker technology to ensure the portability and consistency of the customer application services and reduce the traffic required for upgrades.

[0162] Based on the cloud-native features supported by KubdEdge, the operation and maintenance system can run customer service applications with different architectures simultaneously; through Kubernetes, customer application services are deployed to the edge computing side, supporting rolling updates to ensure the availability of customer application services during the update process, and ensuring the stability and reliability of customer application services during startup and operation, achieving automatic configuration synchronization and automatic health checks.

[0163] In an optional embodiment, the operation and maintenance method of the industrial Internet of Things platform further includes: collecting the initial operation data corresponding to the customer application service, processing the initial operation data into target operation data, and transmitting it to the cloud; the cloud stores the target operation data 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 side is used to collect the initial operation data corresponding to the customer application service, 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] Embodiment 3

[0166] Figure 6 The structure diagram of an electronic device shown in an exemplary embodiment of the present disclosure. The electronic device includes a memory, a processor, and a computer program stored on the memory and configured 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 displayed electronic device 80 is merely an example and should not impose any limitations on the functions and usage scope of the embodiments of the present disclosure.

[0167] As Figure 6 shown, the electronic device 80 can be presented in the form of a general computing device, for example, it can be a server device. The components of the electronic device 80 may include, but are not limited to: at least one of the above processors 81, at least one of the above memories 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 volatile memory, such as random access memory (RAM) 821 and / or cache memory 822, and may further include 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 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0171] The processor 81 executes various functional applications and data processing by running 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 (such as a keyboard, a pointing device, etc.). Such communication can be carried out through the input / output (I / O) interface 85. And the electronic device 80 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the network adapter 86. As shown in the figure, the network adapter 86 communicates with other modules of the electronic device 80 through the bus 83. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination 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 and embodied by multiple units / modules.

[0174] Embodiment 4

[0175] The embodiments of the present disclosure also provide 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] Among them, the more specific computer-readable storage medium that can be adopted 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] Embodiment 5

[0178] 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 Embodiment 2 above.

[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 entirely on the user device, partially on the user device, executed as an independent software package, partially on the user device and partially on a remote device, or entirely on a remote device.

[0180] Although the specific implementation manners of the present disclosure have been 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. Without departing from the principle and essence of the present disclosure, those skilled in the art can make various changes or modifications to these implementation manners, 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