Management method and management device of edge computing gateway application and electronic equipment

Abstract

The invention provides a management method and a management device for an edge computing gateway application, and electronic equipment. The method comprises the following steps: acquiring management component information input by a user on a front-end platform; controlling a k3s container cluster management system to extract management component data in the cloud according to the management component information, wherein the k3s container cluster management system has a preset encapsulation format; and generating an edge computing gateway application at the edge computing gateway according to the management component data, wherein the edge computing gateway application comprises a virtual machine application and / or a container application. By adopting k3s, an edge computing gateway which has low-level hardware requirements and is suitable for resource limitation can be matched, the packaging format of k3s application is helm chart, and helm manages the chart through an API of k3s to provide unified application life cycle management for a virtual machine and a container application. The problems that in the prior art, the computing capacity of an edge computing gateway is limited, and the edge computing gateway is difficult to be compatible with virtual machines and container applications are solved.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and more specifically, to a method for managing edge computing gateway applications, a device for managing edge computing gateway applications, a computer-readable storage medium, and an electronic device. Background Art

[0002] With the rapid growth of IoT devices, traditional cloud-based centralized data processing methods are no longer able to effectively handle the massive amounts of data generated by edge devices due to limited network bandwidth, high transmission costs, and high response latency. Edge computing applications are highly complex. Unlike traditional gateways, which have limited computing power, edge computing requires intelligent computing capabilities. The diversity of development tools and programming languages ​​required has led to a proliferation of computer programming technologies and a lack of unified standards. The heterogeneous protocols used by device terminals and the variety of edge computing services also lead to high maintenance costs for both devices and applications. With the development of cloud computing and container technologies, Kubernetes has become an industry standard and leader, providing users with a powerful, flexible, and scalable platform for deploying and managing a wide range of applications. However, for applications that are difficult to containerize, such as traditional enterprise applications, legacy systems, or those requiring specialized hardware support, virtual machines remain a necessary and effective solution. However, it is difficult to uniformly deploy and manage both virtual machines and container applications. Summary of the Invention

[0003] The main purpose of this application is to provide a management method for edge computing gateway applications, a management device for edge computing gateway applications, a computer-readable storage medium and an electronic device, so as to at least solve the problem in the prior art that the computing power of edge computing gateways is limited and it is difficult to be compatible with virtual machines and container applications.

[0004] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a management method for edge computing gateway applications is provided, including: obtaining management component information input by a user on a front-end platform; according to the management component information, controlling the k3s container cluster management system to extract management component data in the cloud, the k3s container cluster management system having a preset encapsulation format; according to the management component data, generating an edge computing gateway application on the edge computing gateway, the edge computing gateway application including a virtual machine application and / or a container application.

[0005] Optionally, the management method also includes: obtaining a first operation instruction of the user on the front-end platform for the management component information; performing lifecycle management of the management component information in the interface according to the first operation instruction and the interface protocol of the k3s container cluster management system, the k3s container cluster management system is integrated with a custom plug-in, and the custom plug-in is used to customize the resource type of the management component information; and encapsulating the customized management component information into the interface of the k3s container cluster management system.

[0006] Optionally, the management method further includes: determining whether the management component information satisfies a first preset condition, the first preset condition including that the management component information is consistent with historical management component information; and when it is determined that the management component information satisfies the first preset condition, determining the management component data corresponding to the management component information based on the historical management component information.

[0007] Optionally, determining the management component data corresponding to the management component information based on the historical management component information includes: obtaining a correspondence table, the correspondence table representing the mapping relationship between the preset historical management component information and the preset management component data; and determining the management component data corresponding to the management component information based on the historical management component information and the correspondence table.

[0008] Optionally, the first operation instruction includes: view, create, modify and delete.

[0009] Optionally, data is transmitted between the front-end platform and the cloud via the http protocol.

[0010] Optionally, the protocol for data transmission between the cloud and the edge computing gateway includes the MQTT protocol.

[0011] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a management device for an edge computing gateway application is provided, including: an acquisition module for obtaining management component information input by a user on a front-end platform; a control module for controlling the k3s container cluster management system to extract management component data in the cloud according to the management component information, and the k3s container cluster management system has a preset encapsulation format; a generation module for generating an edge computing gateway application on the edge computing gateway according to the management component data, and the edge computing gateway application includes a virtual machine application and / or a container application.

[0012] According to another aspect of the present application, a computer-readable storage medium is provided, which includes a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute the above-mentioned edge computing gateway application management method.

[0013] According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include a management method for executing the above-mentioned edge computing gateway application.

[0014] The technical solution of the present application is applied to obtain the management component information input by the user on the front-end platform; according to the management component information, the k3s container cluster management system is controlled to extract the management component data in the cloud; according to the management component data, an edge computing gateway application is generated on the edge computing gateway, and the edge computing gateway application includes a virtual machine application and / or a container application. By adopting lightweight Kubernetes, i.e. k3s, it can match the edge computing gateway with lower-level hardware requirements and is suitable for resource-constrained edge computing gateways, wherein the packaging format of the k3s application is helm chart, and helm manages the chart through the k3s API to provide unified application lifecycle management for virtual machine applications and container applications. It solves the problem in the prior art that the computing power of the edge computing gateway is limited and it is difficult to be compatible with virtual machine and container applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings that constitute part of this application are used to provide a further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute an improper limitation on this application. In the drawings:

[0016] Figure 1 A hardware structure block diagram of a mobile terminal for executing a management method for edge computing gateway applications provided in an embodiment of the present application is shown;

[0017] Figure 2 A schematic diagram of a process for managing an edge computing gateway application according to an embodiment of the present application is shown;

[0018] Figure 3 A schematic diagram of a process for managing another edge computing gateway application provided in accordance with an embodiment of the present application is shown;

[0019] Figure 4 A flow chart of another method for managing edge computing gateway applications provided in accordance with an embodiment of the present application is shown;

[0020] Figure 5 A flow chart of another method for managing edge computing gateway applications according to an embodiment of the present application is shown;

[0021] Figure 6A schematic diagram of building a helm chart application for a virtual machine according to an embodiment of the present application is shown;

[0022] Figure 7 A schematic diagram of building a helm chart application using containers and virtual machines according to an embodiment of the present application is shown;

[0023] Figure 8 A schematic diagram of the structure of a management device for edge computing gateway applications provided according to an embodiment of the present application is shown.

[0024] The above drawings include the following reference numerals:

[0025] 102. Processor; 104. Memory; 106. Transmission device; 108. Input / output device. DETAILED DESCRIPTION

[0026] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0027] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] As described in the background, edge computing applications are complex. Unlike traditional gateways, which have limited computing power, edge computing requires intelligent computing capabilities. For applications that are difficult to containerize, such as traditional enterprise applications, legacy systems, or those requiring specialized hardware, virtual machines (VMs) remain a necessary and effective solution. However, it's difficult to uniformly deploy and manage both VMs and containerized applications.

[0030] The technical solutions in the embodiments of the present invention will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present invention.

[0031] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure diagram of a mobile terminal of a management method for edge computing gateway application according to an embodiment of the present invention. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data, wherein the above mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0032] The memory 104 can be used to store computer programs, such as software programs and modules of application software, such as the computer program corresponding to the management method of the edge computing gateway application in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implementing the above-mentioned method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0033] In this embodiment, a management method for an edge computing gateway application running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0034] Figure 2 FIG. 1 is a flow chart of a method for managing edge computing gateway applications according to an embodiment of the present application. Figure 2 As shown, the method includes the following steps:

[0035] Step S1, a management method for edge computing gateway applications, comprising: obtaining management component information input by a user on a front-end platform;

[0036] Specifically, the front-end management interface (front-end platform) is open to users through a browser. On this interface, users can issue first operation instructions to applications, including viewing, creating, modifying, and deleting applications. The specific information of the application is the management component information Helm chart, which is used to manage the backend K3s. At this time, the management component information Helm chart is equivalent to a template and has no substantive content. Based on the template information, other modules in the backend are controlled to obtain the specific data of the template. The operations of the front-end management interface call the application programming interface (API) of the platform backend through the HTTP protocol.

[0037] Helm is the official package management tool for Kubernetes. It packages Kubernetes resource objects (such as Pods, Deployments, and Services) into Helm Charts (a Helm data format). This allows complex applications to be installed and managed in a Kubernetes cluster just like installing software packages. Helm packages contain all the necessary information for describing and deploying applications, such as the Chart.yaml file, the values.yaml file, and template files for various resource objects. Together, these constitute a Helm Chart. Pods are the smallest deployment unit in Kubernetes, used to run containerized applications. Pods can contain one or more containers that share network and storage resources. Deployments define how applications are deployed, specifying the number of replicas and update policies. Deployments ensure that applications always have the desired number of replicas and support rolling updates. Services expose access to applications to other applications or users. Services can access applications over networks inside or outside the cluster and support features such as load balancing and service discovery.

[0038] Step S2: According to the above management component information, control the k3s container cluster management system to extract management component data in the cloud, and the k3s container cluster management system has a preset packaging format;

[0039] Specifically, the platform's backend application is deployed in the cloud, with an internal API exposed to the front-end management interface for viewing, creating, modifying, and deleting Helmcharts CRD objects. Detailed information about Helmcharts CRD objects and operations on them are sent to the edge computing gateway via the MQTT protocol. K3s applications are packaged in the Helm chart (pre-defined packaging format). Helm manages charts through the K3s API, providing unified application lifecycle management for both virtual machine and container applications.

[0040] Step S3: Generate an edge computing gateway application on the edge computing gateway based on the management component data. The edge computing gateway application includes a virtual machine application and / or a container application.

[0041] Specifically, if Figure 3 As shown, k3s, kubevirt, and helm-controller (not shown) are deployed on the edge computing gateway device. helm-controller is a module that manages the management component information helm chart. When the helm-controller monitors the user managing and configuring the browser's front-end management platform, the first operation instruction issued contains the generation of a new helm chart object. The platform backend in the cloud converts the helm chart into a helmcharts crd and sends it to the edge gateway device. The data transmission uses the MQTT protocol to control k3s to generate a new helm application. The image information of the helm application is pulled from the private image repository in the cloud via the http protocol. The chart package required by the helm application is pulled from the private chart repository in the cloud via the http protocol. After the pulling is completed, a virtual machine or container application will be generated on the edge computing gateway. The edge device interacts with the calculation results and stored data in the edge computing gateway device through the network.

[0042] K3s receives the helmcharts CRD and performs corresponding operations (create, delete, update, view). Events of the helmcharts object are generated on the edge computing gateway. When the helm-controller component listens for the addition, deletion, and update events of the helmcharts object, it creates, deletes, and updates the helm application.

[0043] A Helm application is an application deployed in a Kubernetes cluster using a Helm Chart. Once a Helm package is packaged as a Helm Chart and deployed to the cluster using the HelmCharts Custom Resource Definition (CRD), it becomes a Helm application. A Helm application contains all of the application's configuration and resource objects, and its lifecycle is managed by the Helm Controller, including startup, update, rollback, and deletion operations.

[0044] Through this embodiment, the management component information input by the user on the front-end platform can be obtained; based on the above management component information, the k3s container cluster management system is controlled to extract the management component data in the cloud; based on the above management component data, an edge computing gateway application is generated on the edge computing gateway, and the above edge computing gateway application includes a virtual machine application and / or a container application. By adopting lightweight Kubernetes, i.e. k3s, it can match the hardware requirements with lower levels, and is suitable for resource-constrained edge computing gateways, wherein the packaging format of the k3s application is helm chart, and helm manages the chart through the k3s API, providing unified application lifecycle management for virtual machine applications and container applications. It solves the problem in the prior art that the computing power of the edge computing gateway is limited and it is difficult to be compatible with virtual machine and container applications.

[0045] In some optional embodiments, the above-mentioned management method also includes: obtaining a first operation instruction of the user on the above-mentioned management component information on the front-end platform; performing lifecycle management of the management component information in the above-mentioned interface according to the above-mentioned first operation instruction and the interface protocol of the above-mentioned k3s container cluster management system, the above-mentioned k3s container cluster management system is integrated with a custom plug-in, and the above-mentioned custom plug-in is used to customize the resource type of the above-mentioned management component information; encapsulating the customized management component information into the interface of the above-mentioned k3s container cluster management system.

[0046] Specifically, if Figure 4 As shown in the figure, the k3s platform on the edge computing gateway receives the helmchartscrd object and corresponding operations (including adding, deleting, modifying and viewing) issued by the platform background, thereby performing the corresponding viewing, creation, modification and deletion of the helmcharts crd object; the operation events of the helmcharts crd object are monitored by the helm-controller, and the helm-controller generates the corresponding lifecycle management operations of the helm application.

[0047] Custom Resource Definitions (CRD) are a way to define custom resource types in Kubernetes. HelmCharts CRD is a specific custom resource type that encapsulates the description and operations of the Helm package into the Kubernetes API, making the Helm package a first-class citizen in the Kubernetes cluster. In this way, users can directly operate the Helm Chart through the Kubernetes API or command-line tools without having to use Helm commands directly. The Helm Controller is the component responsible for monitoring HelmCharts CRD operations. When the HelmCharts CRD is detected, the Helm Controller will automatically deploy, update, or delete the Helm package in the Kubernetes cluster.

[0048] While users can still deploy, update, and manage applications using Helm commands directly, they lose some of the advantages of manipulating Helm Charts through the Kubernetes API. Specifically, using Helm commands directly requires users to switch between Helm and Kubernetes, managing different tools and command sets, which increases complexity and potential errors. Helm's automation capabilities are relatively limited, requiring users to manually perform many deployment and update steps. By contrast, manipulating CRDs through the Kubernetes API leverages Kubernetes' automated controllers to perform operations, reducing manual intervention.

[0049] HelmCharts CRD objects are a combination of Helm and Kubernetes, making Helm package management more automated and integrated. Through HelmCharts CRDs, the front-end management interface can perform unified lifecycle management of applications on the edge computing gateway, including deployment, updates, and deletion. This simplifies application management, improves operational efficiency, and reduces the complexity and risks associated with application updates and maintenance.

[0050] A custom plugin (kubeVirt) integrates Kubernetes' network and storage plugins, enabling VMs to use Kubernetes' network policies (e.g., NetworkPolicies) and storage classes (e.g., PersistentVolumeClaims, PVCs). This means VMs can share network and storage resources like containers, enjoying Kubernetes services such as resource isolation, access control, and persistent storage.

[0051] In some optional embodiments, the above-mentioned management method also includes: judging whether the above-mentioned management component information satisfies a first preset condition, the above-mentioned first preset condition including that the above-mentioned management component information is consistent with the historical management component information; when judging that the above-mentioned management component information satisfies the above-mentioned first preset condition, determining the management component data corresponding to the above-mentioned management component information based on the above-mentioned historical management component information.

[0052] Specifically, when the helm application is generated, it will start the application according to the process created by the k8s cluster helm application. At the same time, the k8s cluster will download the specified image and chart package from the cloud warehouse and cloud chart package based on the information carried in the helmcharts crd object, and then create the relevant k8s objects in the chart package in the cluster to run the application. If it is determined that the application has been created before, the image and chart of the historical management component information of the historical application will have been pulled to the node local cache. The image will be cached in the image management storage of k3s, and the chart package can be cached and stored in the local chart warehouse of k3s. When the same application is pulled up for the second time, it can be started directly using the image and chart on the edge computing gateway to avoid pulling from the cloud over the network, thereby improving the user experience.

[0053] Specifically, if Figure 5 As shown, when a user manages and configures an application through the HTTP protocol from the browser's front-end management platform, if the application is previously created, the image and chart of the historical management component information of the historical application will have been pulled to the node's local cache. The edge computing gateway device pulls the image from the private image repository in the cloud based on the corresponding relationship table, and pulls the chart from the private chart repository. The pulling process uses the HTTP protocol. The platform backend converts the pulled image and chart into a Helm chart CRD and sends it to K3s integrated with Kubevirt to generate virtual machines and container applications. The edge device interacts with the computation results and stored data in the edge computing gateway device through the network.

[0054] Specifically, if Figure 6As shown, helm chart is a standard format for encapsulating k3s container applications. Users can upload the application chart package and image to a private repository in the cloud. The virtual machine VM application is generated using the kubevirt plug-in. The encapsulated helm chart consists of kubevirt's virtual machine virtualmachine, data volume datavolume, and service service. Among them, virtualmachine, datavolume, and service include: Chart.yaml file and values.yaml file. Among them, virtualmachine is used to define and deploy resource objects of virtual machine instances, including virtual machine configuration, image, network settings and other information. datavolume: a resource object used to provide persistent storage for virtual machines. Data volumes can be mounted to virtual machines to retain data when the virtual machine is restarted. service: used to define the services and access methods provided by the virtual machine, such as exposing ports, load balancing and other functions, so that the virtual machine can be accessed by other applications or users.

[0055] Specifically, the above-mentioned cloud is deployed with a private image repository and a private chart repository to store the images and helm chart package files of all user applications; the application images are pre-followed to the private image repository on the cloud, and the chart packages written by the application according to the helm specification are pre-stored in the private chart repository on the cloud. The platform backend application is configured with user authentication information for accessing the private image repository and private chart repository on the cloud. The user account login front-end page can access and read and write the application images of the private image repository on the cloud and the chart packages of the private chart repository by calling the API of the platform backend application.

[0056] In addition, K3s objects can be further integrated and used through Helm chart to deploy combined container applications. For example, an application adopts a microservice architecture and consists of more than a dozen single service applications, including databases, middleware, and front-end applications. Through Helm chart specifications, this multi-application combination chart can be combined, such as Figure 7As shown, if the application also includes virtual machines, such as 5G network elements, the user name UPF uses virtual machines (configured with direct network cards, large page memory, CPU core binding, exclusive physical resources, etc.) to improve application performance. Through Helm charts, containers (deployment of the Kubernetes standard object (container Helm chart), stateful replica sets (StatefulSet), services (Service), and configuration maps (ConfigMap), etc.) and virtual machines (VirtualMachine, DataVolume, and Service of the Kubernetes extended KubeVirt custom object (VM Helm chart), etc.) can be combined to build a comprehensive Helm chart application. The comprehensive Helm chart application is managed using the architecture and technology provided in this application. Virtual machine and container applications include: Chart.yaml file and Values.yaml file. Statefulset is used to deploy stateful applications, such as databases or message queues. It ensures that each replica has a unique identity and stable network identifier. This helps ensure data persistence and orderly expansion. Configmap is used to store application configuration data, such as environment variables and configuration files. It allows configuration data to be separated from application code, making the application easier to manage and maintain.

[0057] In some optional embodiments, the above-mentioned determining the management component data corresponding to the above-mentioned management component information based on the above-mentioned historical management component information includes: obtaining a correspondence table, the above-mentioned correspondence table representing the mapping relationship between the preset historical management component information and the preset management component data; determining the management component data corresponding to the above-mentioned management component information based on the above-mentioned historical management component information and the above-mentioned correspondence table.

[0058] Specifically, each time new management component information is generated, the image and chart data of the management component information will be stored, so that there is a preset relationship between the management component information, the image and the chart data. When more new management component information is generated, a correspondence table between the management component information, the image and the chart data will be formed. The management component information is obtained according to the user's instructions. If the management component information has been generated before, the corresponding image and chart data can be directly found through the correspondence table.

[0059] An embodiment of the present application also provides a management device for an edge computing gateway application, including: an acquisition module for acquiring management component information input by a user on a front-end platform; a control module for controlling the k3s container cluster management system to extract management component data in the cloud based on the above management component information; and a generation module for generating an edge computing gateway application on the edge computing gateway based on the above management component data, wherein the edge computing gateway application includes a virtual machine application and / or a container application.

[0060] The following introduces the management device of the edge computing gateway application provided in the embodiment of the present application.

[0061] Figure 8 Schematic diagram of a management device for edge computing gateway application according to an embodiment of the present application. Figure 8 As shown, the device includes: an acquisition module 10, which is used to obtain management component information input by the user on the front-end platform; a control module 20, which is used to control the k3s container cluster management system to extract management component data in the cloud according to the above management component information; a generation module 30, which is used to generate an edge computing gateway application on the edge computing gateway according to the above management component data, and the above edge computing gateway application includes a virtual machine application and / or a container application.

[0062] Through this embodiment, the management component information input by the user on the front-end platform can be obtained through the acquisition module; the control module controls the k3s container cluster management system to extract the management component data in the cloud based on the above management component information, and the k3s container cluster management system has a preset packaging format; the generation module generates an edge computing gateway application on the edge computing gateway based on the above management component data, and the above edge computing gateway application includes a virtual machine application and / or a container application. By adopting lightweight Kubernetes, namely k3s, it can match the hardware requirements with lower levels, and is suitable for resource-constrained edge computing gateways, wherein the packaging format of the k3s application is helm chart, and helm manages the chart through the k3s API, providing unified application lifecycle management for virtual machine applications and container applications. Solve the problem that the computing power of the edge computing gateway in the prior art is limited and it is difficult to be compatible with virtual machine and container applications.

[0063] In some optional embodiments, the management device also includes a first acquisition module, a management module and an encapsulation module, wherein the first acquisition module is used to obtain the user's first operation instruction on the above-mentioned management component information on the front-end platform; the management module is used to perform life cycle management of the management component information in the above-mentioned interface according to the above-mentioned first operation instruction and the interface protocol of the above-mentioned k3s container cluster management system, and the above-mentioned k3s container cluster management system is integrated with a custom plug-in, and the above-mentioned custom plug-in is used to customize the resource type of the above-mentioned management component information; the encapsulation module is used to encapsulate the customized management component information into the interface of the above-mentioned k3s container cluster management system.

[0064] In some optional embodiments, the management device also includes a judgment module and a first determination module, wherein the judgment module is used to judge whether the above-mentioned management component information meets the first preset condition, and the above-mentioned first preset condition includes that the above-mentioned management component information is consistent with the historical management component information; the first determination module is used to determine the management component data corresponding to the above-mentioned management component information based on the above-mentioned historical management component information when it is judged that the above-mentioned management component information meets the above-mentioned first preset condition.

[0065] In some optional embodiments, the determination module includes a second acquisition module and a second determination module, wherein the second acquisition module is used to obtain a correspondence table, the correspondence table representing the mapping relationship between the preset historical management component information and the preset management component data; the second determination module is used to determine the management component data corresponding to the above-mentioned management component information based on the above-mentioned historical management component information and the above-mentioned correspondence table.

[0066] In some optional implementations, the first operation instruction in the first acquisition module includes: view, create, modify and delete.

[0067] In some optional implementations, data is transmitted between the front-end platform in the acquisition module and the cloud in the control module via the http protocol.

[0068] In some optional embodiments, the protocol for data transmission between the cloud in the control module and the edge computing gateway in the generation module includes the MQTT protocol.

[0069] The management device for the edge computing gateway application may include a processor and memory. The acquisition module, control module, and generation module are stored as program units in the memory, and the processor executes the program units stored in the memory to implement the corresponding functions. The modules are all located in the same processor; alternatively, the modules may be located in different processors in any combination.

[0070] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0071] An embodiment of the present invention provides a computer-readable storage medium, which includes a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute the management method of the edge computing gateway application.

[0072] Specifically, the management method of edge computing gateway applications includes:

[0073] Step S1, a management method for edge computing gateway applications, comprising: obtaining management component information input by a user on a front-end platform;

[0074] Step S2: Based on the above management component information, control the k3s container cluster management system to extract management component data in the cloud;

[0075] Step S3: Generate an edge computing gateway application on the edge computing gateway based on the management component data. The edge computing gateway application includes a virtual machine application and / or a container application.

[0076] An embodiment of the present invention provides an electronic device, comprising a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, at least the following steps are performed:

[0077] Step S1, a management method for edge computing gateway applications, comprising: obtaining management component information input by a user on a front-end platform;

[0078] Step S2: Based on the above management component information, control the k3s container cluster management system to extract management component data in the cloud;

[0079] Step S3: Generate an edge computing gateway application on the edge computing gateway based on the management component data. The edge computing gateway application includes a virtual machine application and / or a container application.

[0080] The electronic devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0081] The present application also provides a computer program product, which, when executed on a data processing device, is adapted to execute a program for initializing at least the following method steps:

[0082] Step S1, a management method for edge computing gateway applications, comprising: obtaining management component information input by a user on a front-end platform;

[0083] Step S2: Based on the above management component information, control the k3s container cluster management system to extract management component data in the cloud;

[0084] Step S3: Generate an edge computing gateway application on the edge computing gateway based on the management component data. The edge computing gateway application includes a virtual machine application and / or a container application.

[0085] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, can be centralized on a single computing device, or can be distributed across a network of multiple computing devices. They can be implemented using program code executable by the computing device, and thus, can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described herein can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0086] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0087] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0088] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0089] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0090] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0091] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0092] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0093] The management method and management device of the edge computing gateway application described above in this application can achieve the following beneficial effects:

[0094] 1. This application provides an edge computing cloud management platform based on k3s+kubevirt to manage the resources of the edge computing gateway. It can utilize the elastic scaling characteristics of k3s resources and surrounding ecological components to flexibly orchestrate applications without intrusion on the host's network and storage.

[0095] 2. The k3s provided in this application is based on the helm chart application packaging format. Helm manages charts through the k3s API and provides unified application lifecycle management. The helm-controller management based on this system can solve the shortcomings of edge computing gateway application operation, maintenance and upgrade.

[0096] 3. This application can use a local front-end management interface, a local platform backend, a local private image repository, and a local private chart package repository, so as to achieve independence from cloud components and achieve offline autonomy.

[0097] 4. This application can build a k3s cluster for multiple edge computing gateways, select one of them as the core control node master, and the other nodes as working nodes worker, to perform resource management for multiple edge computing gateways to achieve the purpose of resource expansion and contraction.

[0098] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0099] The foregoing description is merely a preferred embodiment of the present application and is not intended to limit the present application. Persons skilled in the art will readily appreciate that various modifications and variations are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A management method for edge computing gateway applications, characterized in that: include: Obtain management component information entered by the user on the front-end platform; According to the management component information, control the k3s container cluster management system to extract management component data in the cloud, and the k3s container cluster management system has a preset packaging format; An edge computing gateway application is generated at the edge computing gateway according to the management component data, wherein the edge computing gateway application includes a virtual machine application and / or a container application.

2. The management method according to claim 1, characterized in that: The management method also includes: Obtaining a first operation instruction of a user on the front-end platform for the management component information; According to the first operation instruction and the interface protocol of the k3s container cluster management system, life cycle management is performed on the management component information in the interface, the k3s container cluster management system is integrated with a custom plug-in, and the custom plug-in is used to customize the resource type of the management component information; The customized management component information is encapsulated into the interface of the k3s container cluster management system.

3. The management method according to claim 1, characterized in that: The management method also includes: Determining whether the management component information satisfies a first preset condition, wherein the first preset condition includes that the management component information is consistent with historical management component information; In the case where it is determined that the management component information satisfies the first preset condition, management component data corresponding to the management component information is determined according to the historical management component information.

4. The management method according to claim 3, characterized in that: The determining, according to the historical management component information, management component data corresponding to the management component information includes: Acquire a correspondence table, wherein the correspondence table represents a mapping relationship between preset history management component information and preset management component data; According to the historical management component information and the corresponding relationship table, the management component data corresponding to the management component information is determined.

5. The management method according to claim 2, characterized in that: The first operation instructions include: view, create, modify and delete.

6. The management method according to claim 1, characterized in that: The front-end platform and the cloud are connected via the HTTP protocol for data transmission.

7. The management method according to claim 1, characterized in that: The protocol for data transmission between the cloud and the edge computing gateway includes the MQTT protocol.

8. A management device for edge computing gateway application, characterized in that: include: The acquisition module is used to obtain the management component information entered by the user on the front-end platform; A control module, used to control the k3s container cluster management system to extract management component data in the cloud according to the management component information, wherein the k3s container cluster management system has a preset encapsulation format; A generation module is used to generate an edge computing gateway application in the edge computing gateway according to the management component data, and the edge computing gateway application includes a virtual machine application and / or a container application.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the management method of the edge computing gateway application according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a management method for executing the edge computing gateway application described in any one of claims 1 to 7.

Images