WO2021036265A1

WO2021036265A1 - Method and device for edge cloud fusion management

Info

Publication number: WO2021036265A1
Application number: PCT/CN2020/083406
Authority: WO
Inventors: 艾助雄; 刘万来; 周新中; 程先; 沈文忠
Original assignee: 华为技术有限公司
Priority date: 2019-08-23
Filing date: 2020-04-05
Publication date: 2021-03-04
Also published as: CN110633144A

Abstract

Provided are a method and a device for edge cloud fusion management, said method having applications for edge controllers in edge clouds of edge computing systems. An edge computing system comprises a central cloud, edge clouds, and edge nodes, wherein an edge controller and the edge nodes are communicatively connected. The method comprises: an edge controller monitors a task to be executed, said task being in an edge cloud, wherein the task to be executed comprises a task obtained from the central cloud or a task produced by the edge cloud; and, if the task to be executed comprises a first task specific to the edge node, the edge controller sends the first task to the edge node that corresponds to the first task, said node being registered in the edge cloud. The described technical solution uses an edge management controller in an edge cloud to manage an edge node and can reduce the resource consumption of a central cloud, and the edge cloud can differentiate types of tasks to be executed and contribute to carrying out the differentiated management and control of computing nodes and edge nodes within the edge cloud.

Description

Method and device for integrated management of edge cloud

Technical field

This application relates to the field of edge computing, and in particular to a method and device for edge cloud integration management.

Background technique

In the field of edge computing, such as video surveillance, industrial control, telecom multi-access edge computing (MEC) and other scenarios, there are central clouds, edge clouds, and edge nodes located outside the cloud in terms of installation, deployment and networking. Different forms.

For the purpose of unified management and control, overall planning and utilization of resources, and efficient business collaboration, it is often necessary to efficiently connect the central cloud, edge cloud, and edge nodes to form a cloud, which is commonly referred to as cloud-side collaboration. However, the number of edge nodes is large and geographically dispersed, how to manage and control edge nodes is a problem in the field of edge computing. Traditional technologies usually use the central cloud to uniformly manage and control edge nodes, which will occupy a large amount of resources of the central cloud.

Summary of the invention

This application provides a method and device for edge cloud integrated management to realize efficient management of edge nodes.

In a first aspect, a method for integrated management of edge clouds is provided. The method is applied to an edge controller in an edge cloud of an edge computing system. The edge computing system includes a central cloud, an edge cloud, and an edge node. The edge controller is in communication connection with the edge node, and the method includes: the edge controller monitors the task to be performed on the edge cloud, wherein the task to be performed includes a task obtained from the central cloud or The task generated by the edge cloud; when the task to be executed includes the first task for the edge node, the edge controller sends the first task to the first task registered on the edge cloud and corresponds to the first task; The edge node of a task.

The above technical solution uses the edge management controller in the edge cloud to manage the edge nodes, which can reduce the resource consumption of the central cloud, and the edge cloud can distinguish the types of tasks to be performed, which is helpful for computing nodes and edge nodes in the edge cloud. Differentiated management and control.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the edge controller receives registration request information sent by the edge node, and the edge controller checks the registration request information according to the registration request information. The legitimacy of the edge node is verified.

According to the method of the embodiment of the present application, the edge controller can be connected to an external identity authentication system. For example, the identity authentication system can be an identity and access management (identity and access management, IAM) server, and the edge controller can be responsible for the edge node The legitimacy of the edge node is authenticated during registration to prevent illegal and counterfeit edge node access.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the edge controller receives the access request information sent by the edge node, and the edge controller checks the access request information according to the access request information. The edge node performs access authentication.

According to the method of the embodiment of the present application, the edge controller authenticates the access request information of the edge node to prevent unauthorized access, and can also allow only certain edge nodes to access the specified service through the specified communication port.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the edge controller receives a data packet sent by the edge node, and the edge controller performs traffic filtering on the data packet .

According to the method of the embodiment of the present application, the edge controller may be responsible for filtering the data packets uploaded by the edge node, and only allow certain protocol data packets to be uploaded to the edge cloud.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the edge controller managing the state, log alarms, resource utilization, and node tasks of the edge node.

According to the method of the embodiment of the present application, the edge controller may be responsible for managing edge nodes, and functions may include edge node state management, log alarm management, resource utilization management, edge node task query and other functions.

In a second aspect, an edge controller is provided. The edge controller is located in an edge cloud of an edge computing system. The edge computing system includes a central cloud, an edge cloud, and an edge node. The edge node is in communication connection, and the edge controller includes: a task management module for monitoring tasks to be performed on the edge cloud, wherein the tasks to be performed include tasks and/or all tasks obtained from the central cloud. The task generated by the edge cloud; the task management module is further configured to send the first task to the corresponding task registered on the edge cloud when the task to be executed includes the first task for the edge node At the edge node of the first task.

With reference to the second aspect, in some implementation manners of the second aspect, the edge controller includes: an identity authentication module configured to authenticate the legitimacy of the edge node.

With reference to the second aspect, in some implementations of the second aspect, the edge controller includes: the edge controller further includes an authentication/access control module, and the authentication/access control module is configured to The access request of the edge node is authenticated.

With reference to the second aspect, in some implementation manners of the second aspect, the edge controller includes: a traffic filtering module configured to filter data packets sent by the edge node.

With reference to the second aspect, in some implementations of the second aspect, the edge controller includes: an edge node management module, the edge node management module is configured to monitor the status, log alarms, and resource utilization of the edge node And node tasks are managed.

With reference to the second aspect, in some implementations of the second aspect, the edge controller includes: an application programming interface (API), and the application programming interface is used to exchange data packets with an external interface. It should be understood that the modules of the edge controller can be tailored as required, and this application does not limit this. For example, in the simplified implementation, the API can be cut off, the edge cloud can directly call the function modules in the edge controller, and directly use the identity authentication module to directly access the identity authentication system.

Description of the drawings

FIG. 1 is a schematic diagram of the architecture of an edge cluster applicable to an embodiment of the present application.

Fig. 2 is a schematic diagram of a method for edge cloud convergence management provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of a system architecture of edge cloud convergence management provided by an embodiment of the present application.

FIG. 4 is a schematic diagram of the architecture of an edge controller provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of a process of establishing a system for convergent management of edge clouds provided by an embodiment of the present application.

Fig. 6 is a schematic diagram of a process for an edge node to access an edge cloud according to an embodiment of the present application.

detailed description

For the purpose of unified management and control, overall planning and utilization of resources, and efficient business collaboration, it is often necessary to efficiently connect the central cloud, edge cloud, and edge nodes to form a cloud, which is commonly referred to as cloud-side collaboration. However, the number of edge nodes is large and geographically dispersed, how to manage and control edge nodes is a problem in the field of edge computing.

Traditional technologies usually use the central cloud to uniformly manage and control edge nodes, which will occupy a large amount of resources of the central cloud.

For example, the current open source container management platform (Kubernetes, K8S) has been widely used in cloud computing and edge computing. At present, in the field of edge computing based on the K8S ecology, there are corresponding solutions for the central cloud to manage the edge nodes and the unified management of the central cloud and the edge cloud: for example, the edge environment container management platform (KubeEdge) solution can solve the central cloud Manage the problem of a single edge node outside the cloud; the lightweight container management platform (K3S) solution solves the lightweight problem of K8S applications in edge cloud scenarios. K3S combined with K8S's federal solution can also solve the central cloud and edge cloud management problem. However, there is no corresponding solution for the efficient management of edge nodes outside the cloud by lightweight K8S clusters such as K3S, which are tailored and applied in the edge cloud field.

The control end of the KubeEdge architecture is on the cloud, and the computing nodes are distributed on the edge. Users can control and manage each edge node from the center. In order to deal with the possible impact of network disconnection on the business, KubeEdge can cache the metadata on the computing nodes locally. When the edge node is disconnected from the central node, the existing services on the edge node are not affected. The original intention of the KubeEdge solution design is to meet the need for edge nodes with limited resources to be incorporated into the central K8S ecosystem, such as the industrial Internet, the Internet of things (IoT), etc. In this scenario, edge computing nodes often do not need to be composed Cluster.

Therefore, the KubeEdge solution has the following technical defects:

(1) This solution only supports the management of a single edge node, and cannot manage an edge cluster, and the edge nodes cannot work in cluster mode.

(2) KubeEdge only needs a small amount of resources to run on the edge nodes, but a set of enhanced and complete K8S ecology needs to be deployed on the center side. The center side resource consumption is relatively large, which determines that the overall KubeEdge solution is not suitable for small applications. Large-scale edge cloud scenarios.

K3S is designed for R&D and operation and maintenance personnel who run K8S in a resource-limited environment. The purpose is to run small K8S clusters on edge nodes.

Therefore, the K3S solution has the following technical defects:

(1) K3S needs to run in a cluster environment, and does not support the operating environment of a single computing node.

(2) When K3S is deployed as an edge lightweight cluster, it does not support the management of individual edge nodes scattered outside the central cloud.

Due to resource constraints, the edge cloud cannot copy the solution of the central cloud to manage edge nodes. For example, the resources of the edge cloud may not be enough to support the deployment of multiple K8S instances to manage the edge nodes inside and outside the cloud, while one edge cloud manages access The number of edge nodes will not be as large as the number of edge nodes connected to the central cloud. Therefore, some complex features of the central cloud hosting solution are not required. For example, there is no need to consider the random registration of edge nodes in the central cloud hosting solution. Or select one instance from multiple K8S instances to register according to load balancing. When using a K8S or K3S to manage both in-cloud and out-of-cloud nodes, it is necessary to solve the security problems caused by the management of out-of-cloud nodes and the mutual interference that may be caused by mixed management of nodes designed for different tasks.

The main purpose of this application is to solve these problems of the outer edge nodes of the edge cloud management edge cloud based on the K8S ecology, and help build a complete closed loop of the cloud edge collaboration system including the central cloud, edge cloud and edge nodes.

The composition form of the edge node is a single processing device. This type of device is mainly used for nearby data access or processing, including but not limited to various general-purpose or special-purpose computers, which are not limited in the embodiments of the present application.

The edge cluster is composed of multiple processing devices, and the cluster node is the node that can perform calculations in the edge cluster.

As shown in Figure 1, the application scenario of this application is in the field of edge computing. The central cloud 110 manages the edge cloud 120 and the edge node 130 outside the central cloud. The edge cloud 120 can also access the next-level edge node 1201. .

Among them, the edge cloud 120 may be composed of an edge cluster, and its composition form may be multiple processing devices. Each processing device in the edge cloud 120 can be connected to other terminal devices 140 that are not in the edge cloud, and can be connected through other terminal devices 140. The information is collected, transmitted to the corresponding processing device in the edge cloud 120, and then transmitted to the central cloud or processed at the edge cloud 120.

The physical form of the edge node 130 can be a single processing device, and a single processing device can be connected to other terminal devices 140, and information can be collected through other terminal devices 140, transmitted to the processing device in the edge node 130, and then transmitted to the central cloud Or processing at the edge node 130.

It should be understood that the terminal device connected to the processing device may be an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user Device. The physical form of the edge node can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), A handheld device with a wireless communication function, a computing device, or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, etc., which are not limited in the embodiment of the present application.

The GB28181 standard of video surveillance is divided into provinces, cities, and counties according to administrative levels. The next level can be connected to and managed by the next level. As the number of cameras installed in each level of administrative unit is different, the amount of data generated is also different, and the requirements for computing and storage resources required by this level are also different. Generally speaking, a provincial or larger city level is suitable for deploying a central cloud, while a general city or county level is suitable for deploying one edge cloud, while multiple edge nodes can be deployed below the county level. The technical architecture of this application can be applied in video surveillance scenarios and deployed in the edge clusters at the city and county level to manage the next level of edge node problems, and can also be applied to other similar cloud computing technologies that have requirements, and there are also multiple levels. Scenarios that require domain networking are not limited in this application.

The main purpose of this application is to solve these problems existing in the outer edge nodes of the edge cloud management edge cloud based on the K8S ecology, and to provide a method for edge cloud management edge nodes to help build a cloud edge collaboration system that includes the central cloud and the edge. Complete closed loop of cloud and edge nodes.

The following describes the method for integrated management of edge cloud hosting edge clusters and edge nodes provided by the embodiments of the present application with reference to the accompanying drawings.

Wherein, the method of fusion management can be applied to the edge controller in the edge cloud of the edge computing system. The edge computing system includes a central cloud, an edge cloud, and an edge node, wherein the edge controller is in communication connection with the edge node.

Optionally, the edge cloud can be connected through a web socket, where each edge node connected to the edge cloud has a separate socket, that is, the edge cloud and each edge node pass through the web socket Realize point-to-point connection.

S201: The edge controller monitors tasks to be executed on the edge cloud, where the tasks to be executed include tasks obtained from the central cloud or tasks generated by the edge cloud.

Optionally, the task to be executed may be sent by the central cloud to the edge cloud or generated by the edge cloud itself, that is, the central cloud can manage the edge nodes through the edge cloud, and the edge cloud can also manage the edge nodes separately. The central cloud or edge cloud can assign corresponding tasks to edge nodes based on their status, computing power, location and other information, that is, all tasks to be executed have their corresponding execution subjects.

It should be understood that the task to be executed may be assigned to a single edge node or multiple edge nodes by the central cloud or edge cloud, and may be uniformly issued by the edge controller.

Optionally, the edge controller can be connected to an API server in the edge cloud, and the API server can be connected to an external interface to transmit data, which can include tasks to be performed on the edge cloud and the edge nodes registered on the edge cloud. Perform tasks.

S202: When the task to be executed includes the first task for the edge node, the edge controller sends the first task to the edge node registered on the edge cloud and corresponding to the first task.

Optionally, the first task may carry identification information to indicate its corresponding edge node, and the edge controller assigns the first task to the corresponding edge node through the identification information, where the corresponding edge node may be one or Multiple.

Optionally, the edge controller may monitor that the API server has obtained the command for the edge node in time or the call is triggered, and will immediately notify the edge node.

Optionally, the edge controller receives registration request information sent by the edge node, and the edge controller authenticates the legitimacy of the edge node according to the registration request information. Wherein, the registration request information may include the identity information of the edge node.

Optionally, the edge controller receives the access request information sent by the edge node, and the edge controller performs access authentication on the edge node according to the access request information.

Optionally, the edge controller receives the data packet sent by the edge node, and the edge controller performs traffic filtering on the data packet.

Optionally, the edge controller manages the status of the edge node, log alarms, resource utilization, and node tasks.

As shown in FIG. 3, the edge cloud 120 manages the first edge node 1301, the second edge node 1302, and the third edge node 1303. It should be understood that the edge cloud 120 can accommodate multiple edge nodes. The embodiment of the present application only selects three edge nodes as an example, and the present application does not limit the number of edge nodes.

Wherein, the edge cloud may include an edge controller 2101, and the edge controller 2101 may be connected to the API server 2102 in the edge cloud according to the K8S ecological interface standard.

Optionally, the edge controller 2101 is used in the edge cloud 120 to manage remote edge nodes, perform identity authentication and access control on the edge nodes, issue control commands for the edge nodes, and process the status and alarms reported by the edge nodes. Data such as logs. The edge controller 2101 can also monitor the task to be executed on the API server 2102. When the task to be executed includes the first task for the edge node, the edge controller sends the first task to the corresponding first task registered on the edge cloud. Edge node.

Optionally, the edge controller 2101 may connect to the node agent in the edge node through the cloud edge communication agent 2104, and then manage the edge node. As shown in FIG. 3, the edge cloud 120 can manage the first edge node 1301, the second edge node 1302, and the third edge node 1303 through the edge controller 2101.

Optionally, the edge cloud 120 may also include an in-cloud controller 2103, which can be connected to the computing node agent 2201 through the in-cloud controller 2103 to control the computing node 220, which is an edge cluster managed by the edge cloud 120 A cluster node in the.

Optionally, the technical solutions of the embodiments of the present application can also be implemented based on K3S ecology.

The embodiment of this application realizes the integrated management and scheduling of edge nodes and central clouds based on the K8S ecology, and builds a base for the collaboration of edge cloud and edge nodes in management, data, tasks, and resources. This base not only realizes the convenience of management, operation and maintenance. , And meet business flexibility. Flexibility and safety requirements. It solves the problem of separation between the edge node management and the central cluster management of the current edge computing solution based on the K8S ecology, and avoids the waste of resources caused by the construction of multiple K8S clusters or K8S instances and the difficulty of collaboration between clusters.

As shown in FIG. 4, the edge controller 2101 may also include a task management module 350. The task management module 350 may be used to monitor tasks to be performed on the edge cloud. The tasks to be performed may include tasks for edge nodes; the task management module also uses When the task to be executed includes the first task for the edge node, the first task is sent to the edge node corresponding to the first task registered on the edge cloud.

Optionally, the first task may carry identification information to indicate its corresponding edge node, and the task management module 350 assigns the first task to the corresponding edge node through the identification information, where the corresponding edge node may be one or more. It's multiple.

Optionally, the task management module 350 may be connected to an API server in the edge cloud, and is responsible for monitoring the API server in the edge cloud, and obtain related commands or tasks sent by the edge cloud to the edge node.

Optionally, the edge controller 2101 may further include an identity authentication module 320, and the identity authentication module 320 may be responsible for authenticating the legitimacy of the edge node when the edge node is registered, so as to prevent illegal and counterfeit edge node access.

Optionally, the edge controller 2101 may also include an authentication/access control module 330. The authentication/access control module 330 is responsible for authenticating the access request information of the edge nodes to prevent unauthorized access, and it may also allow only certain edge nodes to pass through The specified communication port accesses the specified service.

Optionally, the edge controller 2101 may further include a traffic filtering module 340. The traffic filtering module 340 may be responsible for filtering data packets uploaded by the edge node, and only allow certain protocol data packets to be uploaded to the edge cloud.

Optionally, the edge controller 2101 may also include an edge node management module 360. The edge node management module 360 may be responsible for managing edge nodes. The functions may include edge node status management, log alarm management, resource utilization management, and edge node task query And other functions.

Optionally, the edge controller 2101 may also include API310. API310 can be used to exchange data packets with the outside. It should be understood that each module in the edge controller can send data transmitted with the external interface to API310, which is sent by API310. To the target interface, the response data can also be received from the target interface and forwarded to the module in the edge controller. The API 310 can be connected to an external identity authentication system 240 for identity authentication. For example, the identity authentication system 240 can be an IAM server. The API 310 can also be connected to the management console 230 to facilitate viewing and operating edge nodes.

Optionally, the module of the edge controller can be tailored as required, which is not limited in this application. For example, in the simplified implementation, the API can be cut off, the edge cloud can directly call the function modules in the edge controller, and directly use the identity authentication module to directly access the identity authentication system.

The edge cloud includes an edge controller, and the edge controller monitors tasks to be executed on the edge cloud. When the task to be executed is a task for an edge node, the edge controller sends the task to an edge node registered on the edge cloud. S401: Select an edge cluster, and the edge cluster includes multiple cluster nodes.

Among them, the administrator can select the appropriate edge cluster according to the actual arrangement and needs, and the multiple clusters in the edge centralization are used as the computing nodes controlled by the edge cloud.

S402: Create a cluster namespace (namespace) and an edge namespace.

Among them, the name space is to solve the naming problem under the same scope. Broadly speaking, a namespace is a way of encapsulating things. For example, in the operating system, a directory is used to group related files, and for the files in the directory, it plays the role of a namespace.

Since different tasks need to be performed on cluster nodes and edge nodes, the cluster nodes and edge nodes can be distinguished by creating different namespaces.

S403: Configure the edge controller to monitor the edge namespace.

Optionally, the edge controller may be responsible for monitoring the edge namespace to ensure that commands are not erroneously distributed to other unrelated namespaces, so that a management command for the edge node can be prevented from being distributed to the cluster nodes.

S404: Configure the in-cloud controller to monitor the cluster namespace.

Optionally, the controller in the cloud can be responsible for monitoring the cluster namespace to ensure that commands are not erroneously distributed to other unrelated namespaces, so as to prevent a management command for cluster nodes from being distributed to unrelated nodes Go in.

S405: Label the edge node and the cluster node with different labels.

Among them, because the namespace cannot be bound to the node, the cluster node and the edge node need to be marked with different marks. When the K8S executes the command, it can be scheduled according to the specified mark.

After S405, two operations can be performed. One is to create a process (Pod). Pod is the most basic scheduling unit of K8S. A Pod encapsulates one or more closely related containers; the other is to execute other commands.

When creating a Pod operation, the management process also includes:

S406: Create a Pod in the designated namespace.

Optionally, when creating a Pod, the algorithm in the scheduler in the edge cloud can accurately schedule tasks to the edge node according to the namespace, avoiding mistakenly assigning a task that should be created on the edge node. Created on the cluster node.

S407: Select a node according to the mark.

Optionally, when creating a Pod, the algorithm in the scheduler in the edge cloud can accurately schedule tasks to the edge node according to the mark, avoiding a task that should be created on the edge node on the cluster node by mistake create.

S408, the task runs on the designated node.

It should be understood that the key components responsible for the management of cluster nodes and edge nodes, such as edge controllers and cloud controllers, can respectively monitor the corresponding namespaces to ensure that commands are not distributed to other unrelated namespaces by mistake. Avoid a management command for edge nodes being distributed to cluster nodes.

When executing other commands, the management process also includes:

S409: Execute the command in the designated namespace.

S410: Monitor the command.

Optionally, key components responsible for the management of cluster nodes and edge nodes, such as edge controllers and cloud controllers, can monitor the corresponding namespaces respectively to ensure that commands are not distributed to other unrelated namespaces by mistake. It can avoid that a management command for edge nodes is distributed to cluster nodes.

S411: Send a command to the node agent (Kubelet).

The embodiment of this application realizes the integrated management and scheduling of edge nodes and central clouds based on the K8S ecology, and builds a base for the collaboration of edge cloud and edge nodes in management, data, tasks and resources. This base not only realizes the convenience of management, operation and maintenance , And meet business flexibility. Flexibility and safety requirements. It solves the problem of separation between the edge node management and the central cluster management of the current edge computing solution based on the K8S ecology, and avoids the waste of resources and the difficulty of collaboration between clusters caused by the construction of multiple K8S clusters or K8S instances.

Among them, the edge node can register in the edge cloud through the edge controller in the edge cloud, and access the edge cloud.

S501, the edge node starts.

S502, register to the edge cloud.

Optionally, after the edge node is started, it first registers with a designated edge cloud, and can send registration request information to the edge cloud, and the registration request information can include the identity information of the edge node.

S503, two-way identity authentication. If the authentication fails, the connection between the two parties is disconnected.

Optionally, after the edge cloud receives the registration request information of the edge node, the identity authentication module of the edge controller in the edge cloud receives the identity information and authenticates the legitimacy of the edge node, and the edge cloud also sends the edge to the edge node. For the identity information of the cloud, the edge node also authenticates the legitimacy of the edge cloud. If any party fails in the two-way authentication process, the connection will be disconnected.

S504: The authentication is passed and the registration is successful.

Optionally, after the authentication is passed, the edge node is successfully registered to the edge cloud, and the edge node management module of the edge controller in the edge cloud can create a record for the edge node and save various information about the node.

S505: Access edge cloud resources.

Optionally, after successful registration, the edge node can request access to edge cloud resources

S506: Access authentication. If the edge cloud determines that the authority of the edge node is insufficient, it rejects the access request of the edge node.

Optionally, the authentication/access control module of the edge controller in the edge cloud authenticates the access request information sent by the edge node to prevent the edge node from unauthorized access to the protected resource.

S507, traffic filtering, if the edge cloud determines that the edge node generates illegal/malicious traffic, it rejects the access request of the edge node.

Optionally, after the access authentication is passed, the edge node can initiate an access request to the edge cloud or upload various data packets, and the traffic filtering module of the edge controller in the edge cloud scans the data packets to filter out illegal data packets or malicious data package.

In S508, all authentications are passed, and the edge node is permitted to access the edge cloud.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or central cloud. Transmission to another website site, computer, server or central cloud via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or central cloud integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for integrated management of edge clouds, characterized in that the method is applied to an edge controller in an edge cloud of an edge computing system, and the edge computing system includes a central cloud, an edge cloud, and an edge node, wherein the The edge controller communicates with the edge node, and the method includes:

The edge controller monitors the tasks to be executed on the edge cloud, where the tasks to be executed include tasks obtained from the central cloud or tasks generated by the edge cloud;

When the task to be executed includes a first task for an edge node, the edge controller sends the first task to an edge node registered on the edge cloud and corresponding to the first task.
The method according to claim 1, wherein the method further comprises:

The edge controller receives registration request information sent by the edge node, and the edge controller authenticates the legitimacy of the edge node according to the registration request information.
The method according to claim 1, wherein the method further comprises:

The edge controller receives the access request information sent by the edge node, and the edge controller performs access authentication on the edge node according to the access request information.
The method according to claim 1, wherein the method further comprises:

The edge controller receives the data packet sent by the edge node, and the edge controller performs traffic filtering on the data packet.
The method according to claim 1, wherein the method further comprises:

The edge controller manages the status of the edge node, log alarms, resource utilization, and node tasks.
An edge controller, characterized in that the edge controller is located in an edge cloud of an edge computing system, the edge computing system includes a central cloud, an edge cloud, and an edge node, wherein the edge controller and the edge Node communication connection, the edge controller includes:

A task management module, configured to monitor tasks to be executed on the edge cloud, where the tasks to be executed include tasks obtained from the central cloud and/or tasks generated by the edge cloud;

The task management module is further configured to, when the task to be executed includes the first task for the edge node, send the first task to a register corresponding to the first task on the edge cloud. Edge node.
The edge controller according to claim 6, wherein the edge controller comprises:

The identity authentication module is used to authenticate the legitimacy of the edge node.
The edge controller according to claim 6, wherein the edge controller comprises:

The edge controller further includes an authentication/access control module, and the authentication/access control module is used to authenticate the access request of the edge node.
The edge controller according to claim 6, wherein the edge controller comprises:

A flow filtering module, which is used to filter data packets sent by the edge node.
The edge controller according to claim 6, wherein the edge controller comprises:

An edge node management module, which is used to manage the state, log alarms, resource utilization and node tasks of the edge node.
The edge controller according to claim 6, wherein the edge controller comprises:

An application program interface, which is used to exchange data packets with an external interface.