Edge application plug-in management method and related equipment based on Internet of Things technology

Abstract

The present application provides an edge application plug-in management method and related equipment based on Internet of Things technology, which are used to improve the reliability of edge application plug-in deployment. The infrastructure managed by the cloud platform is connected to the edge node, and the infrastructure stores at least one edge application plug-in. The cloud platform manages an application plug-in list including edge attributes corresponding to at least one edge application plug-in. The cloud platform obtains attribute change information sent by the edge node, including the second edge attribute of the edge node at the second time. The edge attribute of the edge node at the first time before the second time is the first edge attribute, and the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in. According to the attribute change information and the application plug-in list, a second edge application plug-in that meets the second edge attribute is determined, and the second edge application plug-in belongs to at least one edge application plug-in. Transmit the second edge application plug-in to the edge node.

Description

[0001] This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on October 7, 2023, with application number 202311289947.4 and invention name “A method for software plug-in adaptive edge hardware”, the entire contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of cloud computing, and in particular to an edge application plug-in management method and related equipment based on Internet of Things technology. Background Art

[0003] The current mainstream cloud computing technology supports cloud, edge, and end to achieve collaborative operations among cloud, edge, and end. Among them, edge nodes are located between cloud platforms and business devices. They are functional modules with computing, network, and storage capabilities, and are also the core of edge computing services. By deploying edge application plug-ins on edge nodes, the functions of edge nodes can be expanded. However, how to deploy them is an urgent problem to be solved.

[0004] In the related method, the cloud platform's application plug-in library includes edge application plug-ins, and the cloud platform remains unchanged after deploying edge application plug-ins for edge nodes. When the attributes of edge nodes change, the previously deployed edge application plug-ins may not be able to run on edge nodes, resulting in improper deployment of edge application plug-ins and low reliability of edge application plug-in deployment. Summary of the invention

[0005] The present application provides a plug-in processing method and related devices for improving the reliability of edge application plug-in deployment.

[0006] In a first aspect, the present application provides an edge application plug-in management method based on Internet of Things technology, which is applied on a cloud platform and includes:

[0007] The infrastructure managed by the cloud platform is connected to the edge node, and at least one edge application plug-in is stored on the infrastructure. The cloud platform also manages the application plug-in list, which includes the edge attribute corresponding to at least one edge application plug-in. The cloud platform obtains the attribute change information sent by the edge node, and the attribute change information includes the second edge attribute of the edge node at the second time. In addition, at the first time before the second time, the edge attribute of the edge node is the first edge attribute, the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in. In other words, the attribute information of the edge node changes from the first edge attribute at the first time to the second edge attribute at the second time. The cloud platform determines the second edge application plug-in that meets the second edge attribute from at least one edge application plug-in based on the attribute change information and the application plug-in list, and transmits the second edge application plug-in to the edge node, so that the edge node deploys the second edge application plug-in. Among them, the second edge application plug-in that meets the second edge attribute refers to an edge application plug-in that can run normally under the operating conditions corresponding to the second edge attribute.

[0008] Based on the above description, it can be known that in this application, the cloud platform determines the edge application plug-in that meets the edge attributes of the edge node at the current moment from at least one edge application plug-in managed by the cloud platform based on the attribute change information sent by the edge node and in combination with the application plug-in list, keeps the edge application plug-in matching the attributes of the edge node, and ensures that the edge application plug-in runs normally on the edge node. In other words, the edge application plug-in running on the edge node is not static, but changes with the changes in the edge attributes to match the edge node, which improves the reliability of the edge application plug-in deployment.

[0009] In some optional implementations of the first aspect, at the first time, the application plug-in list also includes the correspondence between the edge node and the first edge application plug-in. After determining the second edge application plug-in that meets the second edge attribute, the cloud platform can also update the application plug-in list, and the updated application plug-in list includes the correspondence between the edge node and the second edge application plug-in. That is, the application plug-in list also includes the correspondence between the edge node and the edge application plug-in.

[0010] In this application, the correspondence between edge nodes and edge application plug-ins is included in the application plug-in list. When deploying edge application plug-ins, the correspondence can be directly used, which reduces the complexity of edge application plug-in deployment. In addition, the correspondence will change as the attributes of the edge nodes change, further ensuring the accuracy of edge application plug-in deployment.

[0011] In some optional implementations of the first aspect, the edge node is also connected to a service device, and the edge attribute of the edge node also includes the service attribute of the service device. That is, the aforementioned first edge attribute also includes the first service attribute of the service device at the first time, and the second edge attribute also includes the second service attribute of the service device at the second time.

[0012] In this application, in the solution where the edge node is connected to the business device, the edge attributes of the edge node also include the business attributes of the business device, which fully considers the actual situation of the edge node, so that the deployed edge application plug-in can run normally on the edge node, further improving the accuracy of the edge application plug-in deployment.

[0013] In some optional implementations of the first aspect, before obtaining the attribute change information sent by the edge node, the cloud platform sends a probe to the edge node, and the probe is used to detect the attribute change of the edge node. In this scheme, the attribute change information obtained by the cloud platform is obtained by the edge node through the probe detecting the edge node within the first time threshold. Among them, the first time threshold indicates the period of the edge node detecting its own attribute changes, that is, the edge node periodically detects its own attribute changes and reports the attribute change information to the cloud platform.

[0014] In this application, the edge node can detect attribute changes by itself through the probe and actively report to the cloud platform, which reduces the amount of information exchange between the cloud platform and the edge node and saves network resources. At the same time, in this solution, the cloud platform does not need to detect edge nodes in real time, which reduces the resource consumption of the cloud platform.

[0015] In some optional implementations of the first aspect, before obtaining the attribute change information sent by the edge node, the cloud platform may send subscription information to the edge node, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on a first time threshold.

[0016] In this application, the cloud platform has multiple ways to obtain attribute change information, which enriches the implementation method of the technical solution of this application and improves the flexibility of the technical solution. Furthermore, in the solution where the cloud platform sends subscription information to the edge node to obtain attribute change information, the cloud platform can obtain attribute change information in a timely manner, avoiding untimely updates of edge application plug-ins due to untimely detection, and further improving the accuracy of edge application plug-in matching.

[0017] In some optional implementations of the first aspect, the edge attributes of the edge node include at least one of the following: hardware resources or software environment of the edge node, hardware resources or software environment of the business device connected to the edge node. Among them, hardware resources refer to the resources of the hardware device running the edge application plug-in. The software environment includes the software network environment and the software running environment.

[0018] In the present application, there are multiple possibilities for edge attributes of edge nodes, which enriches the implementation methods of the technical solutions of the present application.

[0019] In some optional implementations of the first aspect, when an edge node is connected to a cloud platform edge node for the first time, the cloud platform may create an edge node in an application plug-in list, as well as a corresponding relationship between an edge application plug-in that matches the edge attributes of the edge node when the edge node is first connected.

[0020] In some optional implementations of the first aspect, in a scenario where a cloud platform and an edge node establish a communication connection for the first time, the cloud platform sends an edge operation framework to the edge node, and the edge operation framework is used to enable the edge node to communicate with the cloud platform.

[0021] In the present application, when the edge node and the cloud platform establish a communication connection for the first time, it is only necessary to send a lightweight base to the edge node. The operation is simple and reduces the complexity of the technical solution of the present application.

[0022] In some optional implementations of the first aspect, the cloud platform transmits the second edge application plug-in to the edge node, including multiple possibilities. The cloud platform may send the second edge application plug-in to the edge node, or the edge node deployed with the probe may automatically pull the second edge application plug-in. The specifics are not limited here.

[0023] In this application, the cloud platform can send the second edge application plug-in to the edge node. In this solution, the edge node does not need to deploy a probe, thereby reducing the resource occupation of the edge node. In addition, the edge node can also automatically pull the second edge application plug-in without the need for cloud platform processing, thereby reducing the resource consumption of the cloud platform.

[0024] In a second aspect, the present application provides an edge application plug-in management method based on Internet of Things technology, which is applied to edge nodes and includes:

[0025] The edge node is connected to the infrastructure managed by the cloud platform, and at least one edge application plug-in is stored on the infrastructure. The cloud platform is also used to manage the application plug-in list, and the application plug-in list includes the edge attribute corresponding to at least one edge application plug-in. The edge node sends attribute change information to the cloud platform, and the attribute change information includes the second edge attribute of the edge node at the second time. Among them, at the first time before the second time, the edge attribute of the edge node is the first edge attribute. The edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in. In other words, the attribute information of the edge node changes from the first edge attribute at the first time to the second edge attribute at the second time. The edge node obtains a second edge application plug-in that meets the second edge attribute, and the second edge application plug-in is determined from at least one edge application plug-in based on the attribute change information and the application plug-in list.

[0026] Based on the above description, it can be known that in this application, the cloud platform determines the edge application plug-in that meets the edge attributes of the edge node at the current moment from at least one edge application plug-in managed by the cloud platform based on the attribute change information sent by the edge node and in combination with the application plug-in list, keeps the edge application plug-in matching the attributes of the edge node, and ensures that the edge application plug-in runs normally on the edge node. In other words, the edge application plug-in running on the edge node is not static, but changes with the changes in the edge attributes to match the edge node, which improves the reliability of the edge application plug-in deployment.

[0027] In some optional implementations of the second aspect, at the first time, the application plug-in list also includes a correspondence between the edge node and the first edge application plug-in. At the second time, the application plug-in list includes a correspondence between the edge node and the second edge application plug-in. That is, the application plug-in list also includes a correspondence between the edge node and the edge application plug-in.

[0028] In this application, the correspondence between edge nodes and edge application plug-ins is included in the application plug-in list. When deploying edge application plug-ins, the correspondence can be directly used, which reduces the complexity of edge application plug-in deployment. In addition, the correspondence will change as the attributes of the edge nodes change, further ensuring the accuracy of edge application plug-in deployment.

[0029] In some optional implementations of the second aspect, the edge node is connected to a service device, the first edge attribute further includes a first service attribute of the service device at a first time, and the second edge attribute further includes a second service attribute of the service device at a second time.

[0030] In this application, in the solution where the edge node is connected to the business device, the edge attributes of the edge node also include the business attributes of the business device, which fully considers the actual situation of the edge node, so that the deployed edge application plug-in can run normally on the edge node, further improving the accuracy of the edge application plug-in deployment.

[0031] In some optional implementations of the second aspect, before the edge node sends the attribute change information to the cloud platform, it also obtains a probe sent by the cloud platform, which is used to detect the attribute change of the edge node. The edge node detects the attribute change of the edge node through the probe within the first time threshold and obtains the attribute change information. Among them, the first time threshold indicates the period of the edge node detecting its own attribute change, that is, the edge node periodically detects its own attribute change and reports the attribute change information to the cloud platform.

[0032] In this application, the edge node can detect attribute changes by itself through the probe and actively report to the cloud platform, which reduces the amount of information exchange between the cloud platform and the edge node and saves network resources. At the same time, in this solution, the cloud platform does not need to detect edge nodes in real time, which reduces the resource consumption of the cloud platform.

[0033] In some optional implementations of the second aspect, before sending the attribute change information to the cloud platform, the edge node obtains subscription information sent by the cloud platform, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on a first time threshold.

[0034] In this application, the cloud platform has multiple ways to obtain attribute change information, which enriches the implementation method of the technical solution of this application and improves the flexibility of the technical solution. Furthermore, in the solution where the cloud platform sends subscription information to the edge node to obtain attribute change information, the cloud platform can obtain attribute change information in a timely manner, avoiding untimely updates of edge application plug-ins due to untimely detection, and further improving the accuracy of edge application plug-in matching.

[0035] In some optional implementations of the second aspect, obtaining the second edge application plug-in that satisfies the second edge attribute may be that the edge node pulls the second edge application plug-in that satisfies the second edge attribute from at least one edge application plug-in through a probe.

[0036] In this application, the edge node automatically pulls the second edge application plug-in, which does not require cloud platform processing, thereby reducing resource consumption of the cloud platform.

[0037] In some optional implementations of the second aspect, obtaining the second edge application plug-in that satisfies the second edge attribute may also be that the edge node receives the second edge application plug-in that satisfies the second edge attribute and is issued by the cloud platform.

[0038] In the present application, the cloud platform may send a second edge application plug-in to the edge node. In this solution, the edge node may not deploy probes, thereby reducing the resource usage of the edge node.

[0039] In some optional implementations of the second aspect, the hardware resources or software environment of the edge node, and the hardware resources or software environment of the service device connected to the edge node.

[0040] In the present application, there are multiple possibilities for edge attributes of edge nodes, which enriches the implementation methods of the technical solutions of the present application.

[0041] In some optional implementations of the second aspect, when the first edge node establishes a communication connection with the cloud platform for the first time, the first edge node receives an edge operation framework from the cloud platform, where the edge operation framework is used to enable the first edge node to communicate with the cloud platform.

[0042] In the present application, when the edge node and the cloud platform establish a communication connection for the first time, it is only necessary to send a lightweight base to the edge node. The operation is simple and reduces the complexity of the technical solution of the present application.

[0043] In a third aspect, the present application provides a cloud platform, the cloud platform is used to manage infrastructure, the infrastructure is connected to an edge node, wherein at least one edge application plug-in is stored on the infrastructure, and the cloud platform is also used to manage an application plug-in list, the application plug-in list includes at least one edge attribute corresponding to the edge application plug-in. The cloud platform includes a transceiver unit and a processing unit.

[0044] The transceiver unit is used to obtain the attribute change information sent by the edge node, and the attribute change information includes the second edge attribute of the edge node at the second time. Wherein, at the first time before the second time, the edge attribute of the edge node is the first edge attribute. The edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in.

[0045] The processing unit is used to determine a second edge application plug-in that meets the second edge attribute according to the attribute change information and the application plug-in list, where the second edge application plug-in belongs to at least one edge application plug-in.

[0046] The transceiver unit is also used to transmit the second edge application plug-in to the edge node.

[0047] The cloud platform is used to execute the method shown in the aforementioned first aspect, or any possible implementation of the first aspect, and its beneficial effects are as shown in the first aspect, or any possible implementation of the first aspect, and will not be repeated here.

[0048] In a fourth aspect, the present application provides an edge node, the edge node is connected to an infrastructure managed by a cloud platform, wherein at least one edge application plug-in is stored on the infrastructure, the cloud platform is also used to manage an application plug-in list, the application plug-in list includes at least one edge attribute corresponding to the edge application plug-in, and the edge node includes:

[0049] A transceiver unit is used to send attribute change information to the cloud platform, wherein the attribute change information includes a second edge attribute of the edge node at a second time. At a first time before the second time, the edge attribute of the edge node is a first edge attribute. The edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in. A second edge application plug-in that meets the second edge attribute is obtained, and the second edge application plug-in is determined by the cloud platform from the at least one edge application plug-in according to the attribute change information and the application plug-in list.

[0050] The edge node is used to execute the method shown in the aforementioned second aspect, or any possible implementation of the second aspect, and its beneficial effects are as shown in the second aspect, or any possible implementation of the second aspect, and are not repeated here.

[0051] In a fifth aspect, the present application provides a computing device cluster, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster implements the method disclosed in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.

[0052] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer device cluster, enables the computer device cluster to implement the method disclosed in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.

[0053] In a seventh aspect, the present application provides a computer-readable storage medium comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method disclosed in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.

[0054] The beneficial effects shown in the fifth to seventh aspects of the present application are similar to the methods disclosed in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 A schematic diagram of a system architecture provided for an embodiment of the present application;

[0056] Figure 2 Another schematic diagram of a system architecture provided for an embodiment of the present application;

[0057] Figure 3 A flowchart of an edge application plug-in management method based on Internet of Things technology provided in an embodiment of the present application;

[0058] Figure 4 Another flowchart of the edge application plug-in management method based on Internet of Things technology provided in an embodiment of the present application;

[0059] Figure 5 Another schematic diagram of a system architecture provided for an embodiment of the present application;

[0060] Figure 6 A schematic diagram of the structure of the cloud platform provided in the embodiment of the present application;

[0061] Figure 7 A schematic diagram of the structure of an edge node provided in an embodiment of the present application;

[0062] Figure 8 A schematic diagram of a structure of a computing device provided in an embodiment of the present application;

[0063] Fig. 9 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0064] Fig.10 Another structural diagram of a computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] The embodiments of the present application provide a plug-in processing method and related devices for improving the reliability and practicality of edge application plug-in deployment.

[0066] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0067] 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 sequence. It should be understood that the terms used in this way can be interchanged in appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attribute in the embodiments of the present application when describing. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment containing a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment. In addition, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or", describes the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B, can represent: A exists alone, A and B exist simultaneously, and B exists alone, wherein A, B can be singular or plural. The character " / " generally represents that the associated objects before and after are a kind of "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0068] First, the relevant concepts and terms involved in the embodiments of the present application are explained.

[0069] 1. Edge nodes and edge applications.

[0070] Edge nodes are relative to cloud computing data centers. They refer to network nodes with fewer intermediate links between them and the final access users. They can be a computer room or a physical device. Compared with direct access to the source station, the terminal access to the edge node will have better responsiveness and connection speed. The edge node is located between the cloud platform and the terminal, connecting the cloud platform and the terminal, and is usually presented in the form of a hardware entity.

[0071] Edge applications are executable applications deployed on edge nodes, responsible for executing specific services on edge nodes, such as data collection, data analysis, device linkage, report presentation, and configuration control equipment.

[0072] 2. Plug-ins.

[0073] Plug-ins are application extensions built on top of products. They are pluggable and are an advantage of the loosely coupled design of the product. They can be added or removed at any time as needed.

[0074] Edge application plug-ins are extensions of edge applications. They are developed on the cloud, remotely distributed and deployed on edge hardware, and based on the edge operation framework, they can run on edge hardware. They have the characteristics of pluggability, loose coupling, and easy assembly. The relationship between edge application plug-ins and edge nodes has gone through a process of static proxy, dynamic recording, and then containerization. Static proxy means that the relevant code of the edge application plug-in is strongly bound to the hardware and cannot be decoupled from the edge node. Dynamic loading means that the relevant code of the edge application plug-in is not strongly bound to the hardware and can be decoupled from the edge node. In the current edge computing market, the mainstream edge operation framework is containerization, which can realize cross-platform deployment of edge application plug-ins.

[0075] 3. Cloud platform and infrastructure.

[0076] The cloud platform is used to manage the cloud vendor's infrastructure, which is multiple cloud data centers located in different regions, where each region is equipped with at least one cloud data center. The cloud platform can provide interfaces related to cloud computing services, such as configuration pages (i.e., interfaces) or application programming interfaces (APIs) for tenants to access cloud services. Tenants can log in to the cloud platform with a pre-registered account and password, and after a successful login, they can select and purchase cloud services provided by the cloud data center in the predetermined area, such as object storage services, virtual machine services, container services, or other known cloud services.

[0077] 4. Tenants.

[0078] A top-level object used to manage cloud services and / or cloud resources. Tenants register their tenant accounts and set their tenant passwords on the cloud platform through a local client (such as a browser). The local client remotely logs in to the cloud platform through the tenant account and the set tenant password. The cloud platform provides a configuration interface or API for tenants to configure and use cloud services, wherein the cloud services are specifically provided by the infrastructure managed by the cloud platform as described above.

[0079] 5. Internet of things.

[0080] The Internet of Things is a network based on information carriers such as the Internet and traditional telecommunications networks, which enables all independently addressable physical objects to be interconnected. In other words, the Internet of Things is a network that interconnects ubiquitous terminal devices and facilities through various wired and / or wireless communication networks.

[0081] See below. Figure 1 and Figure 2 , Figure 1 and Figure 2All of them are schematic diagrams of system architecture provided in embodiments of the present application.

[0082] like Figure 1 As shown, the tenant logs into the cloud platform 30 through the client 10 via the Internet 20 using the account and password registered on the cloud platform 30. The cloud platform 30 is used to manage infrastructure, which includes multiple data centers set up in different regions, such as Figure 1 The region 1 shown includes cloud data center 1 and cloud data center 2, and region 2 includes cloud data center 3 and cloud data center 4. Each cloud data center is provided with multiple servers, and service instances (including at least one of virtual machines, containers, and dedicated hosts) are run on the servers.

[0083] In an embodiment of the present application, the infrastructure is connected to the edge node, and at least one edge application plug-in is stored on the infrastructure. Figure 1 As shown in the figure, the infrastructure establishes communication connections with N edge nodes, where N is an integer greater than 2. The cloud platform and edge nodes are included in the cloud-edge collaborative architecture, which fully utilizes the advantages of cloud computing and edge computing. Cloud computing is a computing model that provides computing resources and services to users and accesses them through the Internet. It has the characteristics of virtualization, automation, and service models. The emergence of cloud computing makes computing resources easier to obtain and manage, helping to reduce costs and improve efficiency. Edge computing emphasizes the transfer of computing resources and data processing capabilities to places closer to the data generation source. It has the characteristics of low latency and discreteness. At the same time, edge nodes can process data locally, reducing dependence on cloud platforms.

[0084] In addition, each edge node can also be connected to one or more business devices, or called end-side devices. In this solution, the cloud-edge collaborative architecture can be considered as an integrated "cloud-edge-end" architecture. In the edge application plug-in management method based on Internet of Things technology provided in an embodiment of the present application, the edge node or cloud platform can detect changes in the business devices connected to the edge node, which will be explained in detail later. See the following text for details.

[0085] It should be noted that Figure 1 Taking the example of the infrastructure managed by the cloud platform connecting N edge nodes, in actual applications, the infrastructure can also establish communication connections with a smaller number of edge nodes, which is not limited here.

[0086] Figure 2 The interaction between a cloud platform and an edge node in the embodiment of the present application is taken as an example.

[0087] like Figure 2As shown, the cloud platform obtains the edge attributes of the edge node by using the cloud-edge collaboration function provided by the cloud platform. You can also upload application plug-ins in the cloud management console, and the application plug-in library includes the application plug-in. The cloud platform can also manage the application plug-in list, which includes the edge attributes corresponding to the application plug-in.

[0088] Edge application plug-ins can be deployed on edge nodes, such as application plug-in A. The operation of application plug-in A is controlled by the plug-in runtime engine. Edge nodes can detect changes in their own attributes through probes and report the changes to the cloud platform, so that the cloud platform determines whether to update the edge application plug-in deployed on the edge node based on the attribute changes.

[0089] Optionally, the edge node can also be connected to a business device. In this case, the resources detected also include the business device hardware resources and software environment.

[0090] In the embodiment of the present application, after the cloud platform obtains the attribute change of the edge node, it will automatically deploy or remind the user to deploy the edge application plug-in adapted to the current edge node, and the edge node can also automatically pull the edge application plug-in adapted to the current edge node. The specific implementation process is described in detail later.

[0091] Next, see Figure 3 , Figure 3 A flow chart of an edge application plug-in management method based on Internet of Things technology provided in an embodiment of the present application includes:

[0092] 301. The cloud platform obtains attribute change information sent by the edge node, where the attribute change information includes a second edge attribute of the edge node at a second time.

[0093] In an embodiment of the present application, a cloud platform is used to manage an infrastructure, and the infrastructure is connected to an edge node, wherein at least one edge application plug-in is stored on the infrastructure. It can also be understood that an application plug-in library is deployed on the cloud platform, and the application plug-in library includes edge application plug-ins, and these edge application plug-ins are decoupled from the hardware. Specifically, the application plug-in library includes an identifier of an edge application plug-in, which is used to uniquely identify the edge application plug-in. The application plug-in library includes various types of edge application plug-ins, such as: protocol plug-ins, artificial intelligence (AI) plug-ins, database plug-ins, etc., which are not specifically limited here.

[0094] The cloud platform is also used to manage the application plug-in list, which includes at least one edge attribute corresponding to an edge application plug-in. In other words, the application plug-in list includes the correspondence between the edge application plug-in and the edge attribute. Among them, the edge attributes corresponding to the edge application plug-in reflect the resources required to run the edge application plug-in and / or the software environment corresponding to the running of the edge application plug-in from multiple angles, including the characteristics and operating conditions of the edge application plug-in. The characteristics of the edge application plug-in can also be understood as the capabilities of the edge application plug-in, for example, whether it can write to the database, whether it has firewall functions, etc., which are not specifically limited here. The operating conditions of the edge application plug-in include the software environment and hardware resources on which the running of the edge application plug-in depends.

[0095] At a first time before the second time, the edge attribute of the edge node is a first edge attribute; the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in stored on the infrastructure.

[0096] In the embodiment of the present application, there are multiple possible ways for the cloud platform to obtain the attribute change information of the edge node, which are described below respectively:

[0097] In some optional implementations, before obtaining the attribute change information sent by the edge node, the cloud platform sends a probe to the edge node, and the probe is used to detect the attribute change of the edge node. In this solution, the cloud platform obtains the attribute change information sent by the edge node, which can be received from the edge node. The attribute change information is obtained by the edge node through the probe detecting the edge node within a first time threshold. The first time threshold is the period for the edge node to detect its own attribute changes.

[0098] In some optional implementations, in the solution where the cloud platform sends probes to the edge nodes, the edge nodes may also continuously detect their own attribute information, and when attribute changes are detected, send attribute change information to the cloud platform.

[0099] In this application, the edge node can detect attribute changes by itself through the probe and actively report to the cloud platform, which reduces the amount of information exchange between the cloud platform and the edge node and saves network resources. At the same time, in this solution, the cloud platform does not need to detect edge nodes in real time, which reduces the resource consumption of the cloud platform.

[0100] In some optional implementations, before the cloud platform obtains the attribute change information sent by the edge node, the cloud platform may also send subscription information to the edge node, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on the first time threshold.

[0101] In this application, the cloud platform has multiple ways to obtain attribute change information, which enriches the implementation method of the technical solution of this application and improves the flexibility of the technical solution. Furthermore, in the solution where the cloud platform sends subscription information to the edge node to obtain attribute change information, the cloud platform can obtain attribute change information in a timely manner, avoiding untimely updates of edge application plug-ins due to untimely detection, and further improving the accuracy of edge application plug-in matching.

[0102] In some optional implementations, before the cloud platform obtains the attribute change information sent by the edge node, the cloud platform may also send a detection instruction to the edge node, and the detection instruction is used to detect the edge node. The first edge node may not perceive the detection instruction sent by the cloud platform, that is, it is the cloud platform that actually detects the attribute change of the first edge node. After the cloud platform detects, it obtains response information for the detection information, and the response information includes the attribute change information of the edge node.

[0103] In the embodiment of the present application, there are multiple possibilities for the edge attributes of the edge node. In the solution where the edge node is not connected to a service device, the edge attributes include the hardware resources and software environment of the edge node. In the solution where the edge node is connected to a service device, the edge attributes also include the hardware resources or software environment of the service device connected to the edge node.

[0104] Hardware resources refer to the resources of the hardware devices that run edge application plug-ins, such as hardware version, hardware storage space, hardware architecture, etc. The software environment includes the software network environment (such as network bandwidth, network latency, port software environment, etc.), software operating environment (such as application programming interface (API) changes, memory space required to install edge application plug-ins, etc., which are used to describe the software operating environment).

[0105] In the present application, there are multiple possibilities for edge attributes of edge nodes, which enriches the implementation methods of the technical solutions of the present application.

[0106] Accordingly, there are many possible situations in which the attributes of edge nodes change, including the increase or decrease of hardware resources, or changes in the software environment, such as the addition of business equipment (such as processors, memory, storage cards, AI acceleration cards) to edge nodes, containerization of connected sub-devices, and changes in the attributes of newly added resources such as databases. Among them, the edge node can also detect the interface connected to the business device, for example, whether the business device is connected through an interface such as RS-232, RS-485, or registered jack (RJ) 45. For example, the increase or decrease of network latency, the decrease or increase of network bandwidth, etc.

[0107] In addition, it should be noted that the changes in the attributes of edge nodes can be either minor changes in the hardware resources or software environment of the edge nodes, or major changes. Minor changes refer to changes that are not sufficient to change the application plug-ins deployed on the edge nodes, such as a reduction in memory space and the amount of reduction does not reach the change threshold, or the remaining memory space is not lower than the critical value, etc. Major changes refer to changes that may prevent the edge application plug-ins that have been deployed on the edge nodes from running (for example, reducing hardware resources, etc.), or changes that may require the new deployment of edge application plug-ins on the edge nodes (for example, adding databases, AI acceleration cards, etc.).

[0108] Optionally, the attribute change indicated by the attribute change information may be considered to be a significant change in the edge attribute of the edge node. In this solution, it is possible to avoid resource waste caused by frequent information transmission between the cloud platform and the edge node.

[0109] 302. The cloud platform determines the second edge application plug-in that meets the second edge attribute based on the attribute change information and the application plug-in list.

[0110] Based on the above description, the application plug-in list includes the correspondence between the edge application plug-in and the edge attribute. Then, after obtaining the attribute change information, the cloud platform can determine the second edge application plug-in that meets the second edge attribute indicated by the attribute change information from at least one edge application plug-in managed by the cloud platform according to the application plug-in list.

[0111] 303. Transmit the second edge application plug-in between the cloud platform and the edge node.

[0112] In the embodiment of the present application, there are multiple possible ways to transmit the second application plug-in between the cloud platform and the edge node, which are described below respectively:

[0113] In some optional implementations, the cloud platform sends the second edge application plug-in to the edge node. In other words, the edge node receives the first edge application plug-in sent by the cloud platform.

[0114] In the present application, the cloud platform may send a second edge application plug-in to the edge node. In this solution, the edge node may not deploy probes, thereby reducing the resource usage of the edge node.

[0115] In some optional implementations, the edge node may also automatically pull the second edge application plug-in through a probe. In this solution, the cloud platform may not perceive the pulling action of the edge node.

[0116] In this application, the edge node automatically pulls the second edge application plug-in, which does not require cloud platform processing, thereby reducing resource consumption of the cloud platform.

[0117] Based on the above description, it can be known that in this application, the cloud platform determines the edge application plug-in that meets the edge attributes of the edge node at the current moment from at least one edge application plug-in managed by the cloud platform based on the attribute change information sent by the edge node and in combination with the application plug-in list, keeps the edge application plug-in matching the attributes of the edge node, and ensures that the edge application plug-in runs normally on the edge node. In other words, the edge application plug-in running on the edge node is not static, but changes with the changes in the edge attributes to match the edge node, which improves the reliability of the edge application plug-in deployment.

[0118] In the above description, according to the attribute change information and the plug-in application list, it is determined that the subject of the second edge application plug-in that meets the second edge attribute is the cloud platform, that is, the execution subject of step 302 is the cloud platform. In actual applications, the execution subject of this step can also be an edge node, which is explained below.

[0119] In the solution where the edge node includes a probe, after the edge node determines the attribute change information of the edge node, the edge application list can be read through the probe, and the second edge application plug-in that meets the second edge attribute can be determined based on the attribute change information and the plug-in application list. Then, the second edge application plug-in that meets the second edge attribute is pulled from at least one edge application plug-in through the probe to deploy the second edge application plug-in to the edge node.

[0120] For example, assuming that the edge node is first connected to the instrumentation equipment through the RS485 serial line, the probe automatically identifies the attribute changes of the edge node and reports them to the cloud platform. The edge node reads the application plug-in list, determines the second edge application plug-in that meets the second edge attribute of the edge node, and automatically pulls the second edge application plug-in (i.e., protocol plug-in) through the probe, and deploys the second edge application plug-in on the edge node.

[0121] For example, if a module with AI computing power such as a graphics processing unit (GPU) or a natural processing unit (NPU) card is inserted into the edge node, the probe detects its model and reports the change to the cloud platform. Similar to the previous example, the edge node automatically pulls the second edge application plug-in (i.e., AI plug-in) that meets the second edge attribute of the edge node through the probe and deploys it to the edge node.

[0122] It is understandable that for the probe, when scanning the application plug-in list once, as long as there is an edge application plug-in in the application plug-in list that matches the edge attribute of the edge node and has not been deployed to the edge node, the probe can pull the edge application plug-in to the edge node.

[0123] In this application, the edge node can automatically pull the second edge application plug-in without the need for cloud platform processing, thereby reducing the resource consumption of the cloud platform.

[0124] In some optional implementations, the application plug-in list may include the correspondence between edge application plug-ins and edge attributes as shown above, and may also include the correspondence between edge application plug-ins and edge nodes. The correspondence here means that on a certain edge node, one or more edge application plug-ins corresponding to the edge node in the application plug-in list can be deployed.

[0125] Exemplarily, at the first time, the application plug-in list also includes the correspondence between the edge node and the first edge application plug-in. At the second time, the application plug-in list includes the correspondence between the edge node and the second edge application plug-in.

[0126] It is understandable that the attribute change information obtained by the cloud platform indicates the second edge attribute of the edge node at the second time. After determining the second edge application plug-in that meets the second edge attribute, the cloud platform updates the application plug-in list. The updated application plug-in list includes the correspondence between the edge node and the second edge application plug-in. In other words, the process of the cloud platform updating the application plug-in list includes: obtaining the current edge attribute of the edge node, determining the edge application plug-in that meets the current edge attribute based on the correspondence between the edge application plug-in and the edge attribute included in the application plug-in list, and then updating the correspondence between the edge application plug-in and the edge node included in the application plug-in list.

[0127] Optionally, in the edge application list, the edge node may be indicated by an edge node identifier. The edge node identifier is used to uniquely identify the edge node, such as a device serial number (SN), a custom identifier, etc., which is not specifically limited here.

[0128] In some optional implementations, taking the target edge node as an example, if the target edge node identifier is not included in the application plug-in list before the update, then the aforementioned update process actually establishes a corresponding relationship between the target edge node and the edge application plug-in that normally runs on the target node. In other words, when the target edge node is connected to the cloud platform for the first time, the cloud platform can establish a corresponding relationship for the target edge node in the plug-in registration list.

[0129] In some optional implementations, if the target edge node already has a corresponding edge application plug-in in the application plug-in list before updating, the identifier of the edge application plug-in that meets the current edge attribute of the target node can be written into the edge application plug-in set corresponding to the edge node.

[0130] Exemplarily, the update of the application plug-in list is described below using a table as an example.

[0131]

[0132] Assume that Table 1 is the application plug-in list before the update. As shown in Table 1, edge node A1 corresponds to edge application plug-ins B1 and B2, edge node A2 corresponds to edge application plug-in B3, and edge node A3 corresponds to edge application plug-in B4. The updated application plug-in list is shown in Table 2. Edge node A2 no longer corresponds to edge application plug-in B3, and edge node A1 corresponds to edge application plug-in B3.

[0133] Optionally, the corresponding relationship in the application plug-in list shown in Table 2 may also be expressed in the form shown in the following Table 3:

[0134] Table 3

[0135]

[0136] It should be noted that Tables 1 to 3 are only examples of the application plug-in list in tabular form, and do not limit the form of expression of the application plug-in list. In actual applications, the application plug-in list can also adopt other forms that can reflect the correspondence between edge nodes and edge application plug-ins, such as: key-value pairs, code definitions, etc., which are not specifically limited here.

[0137] In this application, the correspondence between edge nodes and edge application plug-ins is included in the application plug-in list. When deploying edge application plug-ins, the correspondence can be directly used, which reduces the complexity of edge application plug-in deployment. In addition, the correspondence will change as the attributes of the edge nodes change, further ensuring the accuracy of edge application plug-in deployment.

[0138] It should also be noted that in the embodiment of the present application, there are multiple scenarios that trigger the cloud platform to update the application plug-in list, which are described below respectively:

[0139] In some optional implementations, after the cloud platform obtains the property change information, it automatically updates the application plug-in list.

[0140] In some optional implementations, after the cloud platform obtains the property change information, it sends a reminder to the user, reminding the user to manually update the application plug-in list. In other words, the cloud platform responds to the user's operation instruction and updates the application plug-in list. The cloud platform can send a reminder to the user through SMS, email, interface display, etc.

[0141] In some optional implementations, if the cloud platform does not receive the user's operation instructions within a preset period of time, the cloud platform can automatically update the application plug-in list or send a reminder to the user again until the user responds and then performs the corresponding operation.

[0142] In addition, it is understandable that when users use the cloud platform, they are actually purchasing related services provided by the cloud platform. Then, in some optional implementations, the edge application plug-ins included in the application plug-in list may be edge application plug-ins corresponding to the services purchased by the user. When the attribute change information indicates that the attribute change of the edge node is a newly added resource of the edge node, and the edge application plug-in corresponding to the newly added resource is not included in the original application plug-in list, the cloud platform can remind the user to purchase / rent the cloud service corresponding to the edge application plug-in. Optionally, the edge application plug-in can be sent to the edge node after the cloud service is purchased / rented. It can also be sent to the edge node first, and then the edge application plug-in can be activated after the user completes the purchase / rental of the cloud service. Alternatively, a trial function for the edge application plug-in can also be provided. After the trial period expires, the cloud service purchase / rental is required before the edge application plug-in can continue to be used.

[0143] For example, assume that the edge node does not have AI capabilities, and the user who uses the edge node has not purchased the AI ​​service of the cloud platform, that is, the user's application plug-in list does not include the AI ​​application plug-in. After adding an AI chip to the edge node, the attribute change information indicates this change of the edge node, and the cloud platform can remind the user whether to purchase the AI ​​service to add the relevant information of the AI ​​application plug-in to the application plug-in list.

[0144] In some optional implementations, the edge node may also be connected to a service device. In this solution, the first edge attribute also includes a first service attribute of the service device at a first time, and the second edge attribute also includes a second service attribute of the service device at a second time. The service attributes include hardware resources and software environment of the service device.

[0145] In this application, in the solution where the edge node is connected to the business device, the edge attributes of the edge node also include the business attributes of the business device, which fully considers the actual situation of the edge node, so that the deployed edge application plug-in can run normally on the edge node, further improving the accuracy of the edge application plug-in deployment.

[0146] In some optional embodiments, the embodiment of the present application can deploy a lightweight base on the edge node, and then expand the edge node in the subsequent communication process. Specifically, when the cloud platform and the edge node establish a communication connection for the first time, at least one of the edge operation framework or the probe is sent to the edge node. Among them, the edge operation framework and the probe are both lightweight bases, and the edge operation framework is used to establish a communication connection between the edge node and the cloud platform, that is, the edge node communicates with the cloud platform through the edge operation framework. The probe is used to detect changes in the attributes of the edge node. Further, the edge operation framework includes some plug-ins, including plug-ins for detecting hardware status, operation and maintenance plug-ins, data forwarding plug-ins, etc. The plug-in for detecting hardware status is used to call the hardware driver to obtain the status change of the hardware. The operation and maintenance plug-in is used to detect the status of the application running on the edge node and / or the basic indicators of the operating system (such as CPU, memory, etc.). The data capture plug-in is used to forward the data of the edge node to the cloud platform or system.

[0147] As the attributes of the edge node change, the cloud platform updates the edge application plug-in corresponding to the edge node in the application plug-in list, so that the cloud platform or the edge application plug-in deploys the corresponding edge application plug-in for the edge application according to the application plug-in list, gradually expanding the capabilities of the edge node. The process of transmitting edge application plug-ins between the cloud platform and the edge node is similar to Figure 3 The embodiments shown are similar and will not be described again here.

[0148] In the present application, when the edge node and the cloud platform establish a communication connection for the first time, it is only necessary to send a lightweight base to the edge node. The operation is simple and reduces the complexity of the technical solution of the present application.

[0149] In some optional implementations, before step 301, the cloud platform may obtain edge applications deployed on the cloud platform, register these edge applications in the application plug-in library of the cloud platform, and obtain application plug-ins corresponding to the edge applications.

[0150] Next, in conjunction with specific examples, the application plug-in management method based on the Internet of Things technology provided by the embodiment of the present application is summarized. Figure 4 , Figure 4 A flowchart of an application plug-in management method based on Internet of Things technology provided in an embodiment of the present application.

[0151] like Figure 4 As shown, the application plug-in library of the cloud platform includes one or more types of application plug-ins. The cloud platform also obtains the identification of the edge node and the attribute information of the edge node through the cloud-edge collaborative management function.

[0152] The cloud platform executes step ① to generate an application plug-in list based on the edge application plug-ins in the application plug-in library and the edge application attributes corresponding to the normal operation of the edge application plug-ins. When the cloud platform obtains attribute change information indicating attribute changes of the edge node through step ②, the cloud platform determines the edge application plug-in that matches the current edge attribute of the edge node from the application plug-in list based on the information.

[0153] For example, edge node 1 detects that an NPU card is inserted into edge node 1 through a probe, and executes step ③ to report this attribute change of edge node 1 to the cloud platform. Based on this attribute change and the edge application list, the cloud platform determines the edge application plug-in that matches the current edge attribute of edge node 1 from the edge application plug-ins managed by the cloud platform, that is, Figure 4 The cloud platform executes step ④ to send the AI ​​plug-in to edge node 1, so that edge node 1 deploys the AI ​​plug-in.

[0154] For example, when the cloud platform obtains the edge attribute change of edge node 2 through subscription information to a newly deployed time series database, it means that edge node 2 needs to connect data with other applications through API. Based on this attribute change and the edge application list, the cloud platform determines the edge application plug-in that matches the current edge attribute of edge node 2 from the edge application plug-ins managed by the cloud platform, that is, Figure 4 The cloud platform executes step ⑤ to deploy the database plug-in corresponding to the time series database to edge node 2 to meet the call docking of the time series database. This method can also be understood as the cloud platform automatically triggering the deployment of edge application plug-ins.

[0155] Next, the related equipment provided in the embodiments of the present application is described.

[0156] See also Figure 5 , Figure 5 A schematic diagram of the system architecture provided for an embodiment of the present application. Figure 5 The system includes a cloud platform and an edge node as an example. In actual applications, the system may also include a larger number of edge nodes, which is not limited here.

[0157] like Figure 5 As shown, in the embodiment of the present application, the cloud platform provides an application plug-in list, which includes edge attributes corresponding to edge application plug-ins. Optionally, the application plug-in list, as the basis for the deployment of edge application plug-ins, may also include the correspondence between edge nodes and edge application plug-ins, and is updated as the attributes of each edge node change.

[0158] The edge node includes a plug-in runtime engine, which provides technical support for the operation of edge application plug-ins, and can also deploy edge application plug-ins to edge nodes in the cloud-edge collaborative architecture.

[0159] Optionally, the edge node may also include a probe as a detection module for edge node resources, which is used to detect the software environment and hardware resources of the edge node, as well as the software environment and hardware resources of the business equipment connected to the edge node, including CPU, memory, storage space, newly inserted hardware expansion, port changes, application running environment changes, etc.

[0160] It should be noted that Figure 5 In the illustrated embodiment, the edge application plug-ins deployed on the edge node are application plug-in 1 and application plug-in 2 as an example. In actual applications, the edge node can also deploy a greater or lesser number of edge application plug-ins, which is not specifically limited here.

[0161] See also Figure 6 , Figure 6 A schematic diagram of the structure of the cloud platform provided in the embodiment of the present application. The cloud platform 600 is used to manage the infrastructure, which is connected to the edge node, wherein at least one edge application plug-in is stored on the infrastructure, and the cloud platform 600 is also used to manage the application plug-in list, which includes the edge attributes corresponding to at least one edge application plug-in. Figure 6 As shown, the cloud platform 600 includes a transceiver unit 601 and a processing unit 602 .

[0162] In some optional embodiments, the transceiver unit 601 is used to obtain attribute change information sent by the edge node, the attribute change information including a second edge attribute of the edge node at a second time; wherein, at a first time before the second time, the edge attribute of the edge node is a first edge attribute; the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in.

[0163] The processing unit 602 is configured to determine, according to the attribute change information and the application plug-in list, a second edge application plug-in that meets the second edge attribute, where the second edge application plug-in belongs to at least one edge application plug-in.

[0164] The transceiver unit 601 is further configured to transmit the second edge application plug-in to the edge node.

[0165] In some optional implementations, at the first time, the application plug-in list also includes the correspondence between the edge node and the first edge application plug-in; the processing unit is further used to update the application plug-in list, and the updated application plug-in list includes the correspondence between the edge node and the second edge application plug-in.

[0166] In some optional implementations, the edge node is connected to a service device, the first edge attribute further includes a first service attribute of the service device at a first time, and the second edge attribute further includes a second service attribute of the service device at a second time.

[0167] In some optional implementations, the transceiver unit 601 is further configured to send a probe to the edge node, the probe being used to detect attribute changes of the edge node. The attribute change information from the edge node is obtained by the edge node through the probe within the first time threshold.

[0168] In some optional implementations, the transceiver unit 601 is further used to send subscription information to the edge node, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on the first time threshold.

[0169] In some optional implementations, the edge attributes of the edge node include at least one of the following: hardware resources or software environment of the edge node, hardware resources or software environment of a service device connected to the edge node.

[0170] The cloud platform 600 is used to execute the aforementioned Figures 1 to 5 In the illustrated embodiment, the operations performed by the cloud platform are detailed as described above and will not be repeated here.

[0171] See also Figure 7 , Figure 7 A schematic diagram of the structure of an edge node provided in an embodiment of the present application. The edge node 700 is connected to an infrastructure managed by a cloud platform, wherein at least one edge application plug-in is stored on the infrastructure, and the cloud platform is also used to manage an application plug-in list, wherein the application plug-in list includes at least one edge attribute corresponding to the edge application plug-in.

[0172] In some optional implementations, the edge node 700 includes a transceiver unit 701, which is used to send attribute change information to the cloud platform, and the attribute change information includes a second edge attribute of the edge node at a second time. Wherein, at a first time before the second time, the edge attribute of the edge node is a first edge attribute; the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to at least one edge application plug-in.

[0173] The transceiver unit 701 is further configured to obtain a second edge application plug-in that meets a second edge attribute, where the second edge application plug-in is determined from at least one edge application plug-in according to the attribute change information and the application plug-in list.

[0174] In some optional implementations, at a first time, the application plug-in list also includes a correspondence between an edge node and a first edge application plug-in; at a second time, the application plug-in list includes a correspondence between an edge node and a second edge application plug-in.

[0175] In some optional implementations, the edge node 700 is connected to a service device, the first edge attribute further includes a first service attribute of the service device at a first time, and the second edge attribute further includes a second service attribute of the service device at a second time.

[0176] In some optional implementations, the edge node 700 further includes a processing unit 702 .

[0177] The transceiver unit 701 is also used to obtain the probe sent by the cloud platform, and the probe is used to detect the attribute change of the edge node;

[0178] The processing unit 702 is configured to detect attribute changes of edge nodes through probes within a first time threshold to obtain attribute change information.

[0179] In some optional implementations, the transceiver unit 701 is further used to obtain subscription information sent by the cloud platform, where the subscription information is used to instruct the edge node to push attribute change information to the cloud platform based on the first time threshold.

[0180] In some optional implementations, the transceiver unit 701 is specifically configured to pull, through a probe, a second edge application plug-in that satisfies a second edge attribute from at least one edge application plug-in.

[0181] In some optional implementations, the transceiver unit 701 is specifically configured to receive a second edge application plug-in that meets the second edge attribute and is sent by the cloud platform.

[0182] In some optional implementations, the edge attributes of the edge node include at least one of the following: hardware resources or software environment of the edge node, hardware resources or software environment of a service device connected to the edge node.

[0183] The edge node 700 is used to perform the operation of any edge node in the aforementioned embodiments, as described above, and will not be repeated here.

[0184] It should be noted that, regardless of Figure 6 The transceiver unit 601 and the processing unit 602 in the embodiment shown are Figure 7 The transceiver unit 701 and the processing unit 702 of the illustrated embodiment may be implemented by software or hardware.

[0185] For example, the implementation of the processing unit 702 is described below by taking the processing unit 702 as an example. Similarly, the implementation of the transceiver unit 601, the processing unit 602, and the transceiver unit 701 can refer to the implementation of the processing unit 702.

[0186] As an example of a software functional unit, the processing unit 702 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the processing unit 702 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple data centers with similar geographical locations. Typically, a region may include multiple AZs.

[0187] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0188] As an example of a hardware functional unit, the processing unit 702 may include at least one computing device, such as a server, etc. Alternatively, the processing unit 702 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), etc. The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0189] The multiple computing devices included in the processing unit 702 can be distributed in the same region or in different regions. The multiple computing devices included in the processing unit 702 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the processing unit 702 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0190] See also Figure 8 , Figure 8 A schematic diagram of the structure of a computing device provided in an embodiment of the present application. The computing device 800 includes a processor 801, a communication interface 802, a bus 803, and a memory 804. The processor 801, the communication interface 802, and the memory 804 communicate with each other via the bus 803. In practical applications, communication can also be achieved through other means such as wireless transmission, which is not limited here.

[0191] It should be understood that the present application does not limit the number of processors and memories in the computing device 800 .

[0192] The processor 801 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP) or a digital signal processor (DSP).

[0193] The communication interface 802 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 800 and other devices or a communication network.

[0194] The bus 803 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 The bus 803 is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 803 may include a path for transmitting information between various components of the computing device 800 (for example, the memory 804, the processor 801, and the communication interface 802).

[0195] The memory 804 may include a volatile memory, such as a random access memory (RAM). The memory 804 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0196] Optionally, the memory 804 stores executable program codes, and the processor 801 executes the executable program codes to respectively implement the aforementioned transceiver units (ie Figure 6 The transceiver unit 601 of the embodiment shown in the figure), the processing unit (i.e. Figure 6 The function of the processing unit 602 of the embodiment shown in the figure is implemented to realize the application plug-in management method based on the Internet of Things technology applied to the cloud platform. That is, the memory 804 stores instructions for executing the application plug-in management method based on the Internet of Things technology applied to the cloud platform.

[0197] Optionally, the memory 804 stores executable codes, and the processor 801 executes the executable codes to respectively implement the aforementioned transceiver units (ie Figure 7 The transceiver unit 701 and the processing unit (i.e. Figure 7 The function of the processing unit 702 of the embodiment shown in the figure is implemented to realize the application plug-in management method based on the Internet of Things technology applied to the edge node. That is, the memory 804 stores instructions for executing the application plug-in management method based on the Internet of Things technology applied to the edge node.

[0198] The embodiment of the present application also provides a computing device cluster, which includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some optional implementations, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0199] See also Fig. 9 and Fig.10 , Fig. 9 and Fig.10 All of them are structural schematic diagrams of the computing device cluster provided in embodiments of the present application.

[0200] like Fig. 9As shown, the computing device cluster includes at least one computing device 800. The memory 804 in one or more computing devices 800 in the computing device cluster may store the same instructions for executing the application plug-in management based on the Internet of Things technology applied to the cloud platform provided in the embodiment of the present application, or the same instructions for executing the application plug-in management method based on the Internet of Things technology applied to the edge node provided in the embodiment of the present application.

[0201] In some optional implementations, the memory 804 of one or more computing devices 800 in the computing device cluster may also store partial instructions for executing the application plug-in management method based on the Internet of Things technology applied to the cloud platform. In other words, the combination of one or more computing devices 804 can jointly execute instructions for executing the application plug-in management method based on the Internet of Things technology applied to the cloud platform.

[0202] In some optional implementations, the memory 804 of one or more computing devices 800 in the computing device cluster may also respectively store partial instructions for executing the application plug-in management method based on the Internet of Things technology applied to the edge node. In other words, the combination of one or more computing devices 804 can jointly execute the instructions for executing the application plug-in management method based on the Internet of Things technology applied to the edge node.

[0203] Optionally, the memory 804 in different computing devices 800 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the cloud platform 600. That is, the instructions stored in the memory 804 in different computing devices 800 may implement the functions of one or more units in the transceiver unit 601 and the processing unit 602.

[0204] Optionally, the memory 804 in different computing devices 800 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the edge node 700. That is, the instructions stored in the memory 804 in different computing devices 800 may implement the functions of one or more units in the transceiver unit 701 and the processing unit 702.

[0205] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network.

[0206] Fig.10 A possible implementation is shown. Fig.10As shown, two computing devices 800A and 800B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 804 in the computing device 800A stores instructions for executing the functions of the transceiver unit. At the same time, the memory 804 in the computing device 800B stores instructions for executing the functions of the processing unit.

[0207] It should be noted that in Fig.10 In the related solution of the computing device cluster shown in the figure for executing the functions of the aforementioned cloud platform, the memory 804 in the computing device 800A stores the execution Figure 6 In the embodiment shown, the memory 804 in the computing device 800B stores instructions for executing the functions of the transceiver unit 601. Figure 6 Instructions for the functionality of processing unit 602 in the illustrated embodiment. Fig.10 In the related solution of the computing device cluster shown in the figure for executing the functions of the aforementioned edge node, the memory 804 in the computing device 800A stores the execution Figure 7 In the embodiment shown, the memory 804 in the computing device 800B stores instructions for executing the functions of the transceiver unit 701. Figure 7 Instructions for the functionality of processing unit 702 in the illustrated embodiment.

[0208] Fig.10 The connection method between the computing device clusters shown can be based on the consideration that in the application plug-in management method based on the Internet of Things technology provided in the present application, processing operations and operations other than processing operations are executed separately, that is, the function of the receiving and transmitting unit is considered to be executed by the computing device 800A, and the function of the processing unit is considered to be executed by the computing device 800B.

[0209] It should be understood that Fig.10 The functions of the computing device 800A shown in FIG. 8 may also be completed by multiple computing devices 800. Similarly, the functions of the computing device 800B may also be completed by multiple computing devices 800.

[0210] In some optional implementations, the present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Fig. 9 and Fig.10 The connection method of the computing device cluster will not be described in detail here.

[0211] The embodiment of the present application also provides a computer program product including instructions. The computer program product may be a software or program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computer device, the at least one computer device executes the above-mentioned application plug-in management method based on the Internet of Things technology.

[0212] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by the computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned application plug-in management method based on the Internet of Things technology.

[0213] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0214] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for managing edge application plug-ins based on Internet of Things technology, characterized in that: The method is applied to a cloud platform, the cloud platform is used to manage infrastructure, the infrastructure is connected to an edge node, wherein at least one edge application plug-in is stored on the infrastructure, the cloud platform is also used to manage an application plug-in list, the application plug-in list includes edge attributes corresponding to the at least one edge application plug-in, and the method includes: Acquire attribute change information sent by the edge node, the attribute change information including a second edge attribute of the edge node at a second time; wherein, at a first time before the second time, the edge attribute of the edge node is a first edge attribute; the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to the at least one edge application plug-in; Determine, according to the attribute change information and the application plug-in list, a second edge application plug-in that meets the second edge attribute, where the second edge application plug-in belongs to the at least one edge application plug-in; The second edge application plug-in is transmitted to the edge node.

2. The method according to claim 1, characterized in that: At the first time, the application plug-in list also includes a correspondence between the edge node and the first edge application plug-in; After determining the second edge application plug-in that satisfies the second edge attribute, the method further includes: The application plug-in list is updated, wherein the updated application plug-in list includes a correspondence between the edge node and the second edge application plug-in.

3. The method according to claim 1 or 2, characterized in that: The edge node is connected to a service device, the first edge attribute further includes a first service attribute of the service device at the first time, and the second edge attribute further includes a second service attribute of the service device at the second time.

4. The method according to any one of claims 1 to 3, characterized in that Before acquiring the attribute change information sent by the edge node, the method further includes: Sending a probe to the edge node, wherein the probe is used to detect a property change of the edge node; The obtaining of the attribute change information sent by the edge node includes: The attribute change information is received from the edge node, where the attribute change information is obtained by the edge node detecting the edge node through a probe within a first time threshold.

5. The method according to any one of claims 1 to 3, characterized in that Before acquiring the attribute change information sent by the edge node, the method further includes: Subscription information is sent to the edge node, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on a first time threshold.

6. The method according to any one of claims 1 to 5, characterized in that The edge attribute of the edge node includes at least one of the following: The hardware resources or software environment of the edge node, and the hardware resources or software environment of the service equipment connected to the edge node.

7. A method for managing edge application plug-ins based on Internet of Things technology, characterized in that: The method is applied to an edge node, the edge node is connected to an infrastructure managed by a cloud platform, wherein at least one edge application plug-in is stored on the infrastructure, the cloud platform is further used to manage an application plug-in list, the application plug-in list includes edge attributes corresponding to the at least one edge application plug-in, and the method includes: Sending attribute change information to the cloud platform, the attribute change information including a second edge attribute of the edge node at a second time; wherein, at a first time before the second time, the edge attribute of the edge node is a first edge attribute; the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to the at least one edge application plug-in; A second edge application plug-in satisfying the second edge attribute is obtained, where the second edge application plug-in is determined from the at least one edge application plug-in according to the attribute change information and the application plug-in list.

8. The method according to claim 7, characterized in that At the first time, the application plug-in list also includes a correspondence between the edge node and the first edge application plug-in; At the second time, the application plug-in list includes a correspondence between the edge node and the second edge application plug-in.

9. The method according to claim 7 or 8, characterized in that: The edge node is connected to a service device, the first edge attribute further includes a first service attribute of the service device at the first time, and the second edge attribute further includes a second service attribute of the service device at the second time.

10. The method according to any one of claims 7 to 9, characterized in that Before sending the attribute change information to the cloud platform, the method further includes: Obtaining a probe sent by the cloud platform, where the probe is used to detect attribute changes of the edge node; The attribute change of the edge node is detected by the probe within a first time threshold to obtain the attribute change information.

11. The method according to claim 10, characterized in that Before sending the attribute change information to the cloud platform, the method further includes: Subscription information sent by the cloud platform is obtained, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on a first time threshold.

12. The method according to claim 10, characterized in that The acquiring the second edge application plug-in that meets the second edge attribute includes: The second edge application plug-in satisfying the second edge attribute is pulled from the at least one edge application plug-in through the probe.

13. The method according to any one of claims 7 to 11, characterized in that The acquiring the second edge application plug-in that meets the second edge attribute includes: Receive the second edge application plug-in that meets the second edge attribute and is issued by the cloud platform.

14. The method according to any one of claims 7 to 13, characterized in that The edge attribute of the edge node includes at least one of the following: The hardware resources or software environment of the edge node, and the hardware resources or software environment of the service equipment connected to the edge node.

15. A cloud platform, characterized in that: The cloud platform is used to manage infrastructure, the infrastructure is connected to the edge node, wherein at least one edge application plug-in is stored on the infrastructure, and the cloud platform is also used to manage an application plug-in list, the application plug-in list includes edge attributes corresponding to the at least one edge application plug-in; the cloud platform includes: a transceiver unit, configured to obtain attribute change information sent by the edge node, wherein the attribute change information includes a second edge attribute of the edge node at a second time; wherein, at a first time before the second time, the edge attribute of the edge node is a first edge attribute; the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to the at least one edge application plug-in; A processing unit, configured to determine, according to the attribute change information and the application plug-in list, a second edge application plug-in that satisfies the second edge attribute, where the second edge application plug-in belongs to the at least one edge application plug-in; The transceiver unit is further used to transmit the second edge application plug-in to the edge node.

16. The cloud platform according to claim 15, characterized in that: At the first time, the application plug-in list also includes a correspondence between the edge node and the first edge application plug-in; The processing unit is further configured to update the application plug-in list, wherein the updated application plug-in list includes a correspondence between the edge node and the second edge application plug-in.

17. The cloud platform according to claim 15 or 16, characterized in that: The edge node is connected to a service device, the first edge attribute further includes a first service attribute of the service device at the first time, and the second edge attribute further includes a second service attribute of the service device at the second time.

18. The cloud platform according to any one of claims 15 to 17, characterized in that: The transceiver unit is further used to send a probe to the edge node, where the probe is used to detect a property change of the edge node; The transceiver unit is specifically configured to receive the attribute change information from the edge node, where the attribute change information is obtained by the edge node detecting the edge node through a probe within a first time threshold.

19. The cloud platform according to any one of claims 15 to 17, characterized in that: The transceiver unit is further used to send subscription information to the edge node, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on a first time threshold.

20. The cloud platform according to any one of claims 15 to 19, characterized in that: The edge attribute of the edge node includes at least one of the following: hardware resources or software environment of the edge node, and hardware resources or software environment of a service device connected to the edge node.

21. An edge node connected to an infrastructure managed by a cloud platform, wherein: At least one edge application plug-in is stored on the infrastructure, and the cloud platform is further used to manage an application plug-in list, wherein the application plug-in list includes edge attributes corresponding to the at least one edge application plug-in, and the edge node includes: a transceiver unit, configured to send attribute change information to the cloud platform, wherein the attribute change information includes a second edge attribute of the edge node at a second time; wherein, at a first time before the second time, the edge attribute of the edge node is a first edge attribute; and the edge node runs a first edge application plug-in under the first edge attribute, and the first edge application plug-in belongs to the at least one edge application plug-in; The transceiver unit is further used to obtain a second edge application plug-in that meets the second edge attribute, where the second edge application plug-in is determined from the at least one edge application plug-in according to the attribute change information and the application plug-in list.

22. The edge node according to claim 21, characterized in that: At the first time, the application plug-in list also includes a correspondence between the edge node and the first edge application plug-in; At the second time, the application plug-in list includes a correspondence between the edge node and the second edge application plug-in.

23. The edge node according to claim 21 or 22, characterized in that: The edge node is connected to a service device, the first edge attribute further includes a first service attribute of the service device at the first time, and the second edge attribute further includes a second service attribute of the service device at the second time.

24. The edge node according to any one of claims 21 to 23, characterized in that: The edge node also includes a processing unit; The transceiver unit is further used to obtain a probe sent by the cloud platform, where the probe is used to detect attribute changes of the edge node; The processing unit is configured to detect attribute changes of the edge node through the probe within a first time threshold to obtain the attribute change information.

25. The edge node according to claim 24, characterized in that: The transceiver unit is further used to obtain subscription information sent by the cloud platform, where the subscription information is used to instruct the edge node to push the attribute change information to the cloud platform based on a first time threshold.

26. The edge node according to claim 24, characterized in that: The transceiver unit is specifically configured to pull the second edge application plug-in that meets the second edge attribute from the at least one edge application plug-in through the probe.

27. The edge node according to any one of claims 21 to 25, characterized in that: The transceiver unit is specifically configured to receive the second edge application plug-in that satisfies the second edge attribute and is sent by the cloud platform.

28. The edge node according to any one of claims 21 to 27, characterized in that: The edge attribute of the edge node includes at least one of the following: The hardware resources or software environment of the edge node, and the hardware resources or software environment of the service equipment connected to the edge node.

29. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 6 and 7 to 14.

30. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 6 and 7 to 14.

31. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method as claimed in any one of claims 1 to 6 and 7 to 14.

Images