Network system, management and control method, device and storage medium

Abstract

Embodiments of the present application provide a network system, a management and control method, equipment and a storage medium. In the embodiments of the present application, in combination with the concept of edge computing, the ability of cloud computing is considered to be placed on the edge side closer to the terminal side, and thus a network system including an edge cloud node is provided. In the network system, in combination with a central management and control device and an edge management and control device, the edge cloud node can be fully and comprehensively managed and controlled, which provides a condition for processing the cloud computing in the edge cloud node closer to the terminal, and thus the cloud computing service can be provided for the user by means of the resources in the edge cloud node, which is beneficial to reducing the service response delay and reducing the bandwidth cost.

Description

[0001] This case involves application number 2019102774601, application date April 8, 2019, and patent title "Network System". This is a divisional application of a patent application for "system, control method, equipment and storage medium". Technical Field

[0002] This application relates to the field of Internet technology, and in particular to a network system, control method, device and storage medium. Background Technology

[0003] Currently, the concept of cloud computing is based on centralized resource management. Even with multiple interconnected data centers, all hardware and software resources are still managed, scheduled, and sold as a unified resource. However, with the advent of 5G and the Internet of Things, and the increasing application of cloud computing, the demands on cloud resources from the terminal side in terms of latency, bandwidth, and other performance aspects are becoming increasingly stringent. Centralized cloud networks can no longer meet the growing cloud resource needs of the terminal side. Summary of the Invention

[0004] This application provides a network system, management method, device, and storage medium to reduce service response latency and bandwidth costs.

[0005] This application provides a network system including: a central control device, an edge control device, and at least one edge cloud node; the central control device is configured to receive monitoring data reported by the edge control device for the at least one edge cloud node, and to control the at least one edge cloud node based on the monitoring data; the edge control device is configured to monitor the at least one edge cloud node and report the monitoring data to the central control device; and to autonomously control the at least one edge cloud node when the central control device is not able to control or is unable to control the at least one edge cloud node.

[0006] This application also provides a control method, including: determining that the central control device in the network system is not functioning correctly or is unable to control at least one edge cloud node in the network system; and autonomously controlling the at least one edge cloud node.

[0007] This application embodiment also provides a management and control method, including: monitoring at least one edge cloud node in a network system; and reporting the monitoring data to a central management and control device in the network system, so that the central management and control device can manage and control the at least one edge cloud node based on the monitoring data.

[0008] This application also provides an edge control device, including: a memory and a processor; the memory is used to store a computer program; when the computer program is executed by the processor, the processor causes the processor to implement the steps in the method embodiments of this application.

[0009] This application also provides a computer-readable storage medium storing a computer program, which, when executed by one or more processors, causes the one or more processors to implement the steps in the method embodiments of this application.

[0010] In this embodiment of the application, the concept of edge computing is incorporated, and the capabilities of cloud computing are considered to be placed at the edge, which is closer to the terminal. Thus, a network system including edge cloud nodes is provided. In this network system, the central management and control equipment and the edge management and control equipment are combined to fully and comprehensively manage the edge cloud nodes. This provides the conditions for "processing cloud computing in edge cloud nodes closer to the terminal". In turn, cloud computing services can be provided to users by using the resources in the edge cloud nodes, which is beneficial to reducing response latency and bandwidth costs. Attached Figure Description

[0011] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0012] Figure 1a A schematic diagram of the structure of a network system provided for an exemplary embodiment of this application;

[0013] Figure 1b A schematic diagram of a central control device and an edge control device provided for an exemplary embodiment of this application;

[0014] Figure 1c A schematic diagram of another network system provided as an exemplary embodiment of this application;

[0015] Figure 2a A flowchart illustrating a control method provided for an exemplary embodiment of this application;

[0016] Figure 2b A flowchart illustrating another control method provided for an exemplary embodiment of this application;

[0017] Figure 3 A schematic diagram of the structure of a central control device provided for an exemplary embodiment of this application;

[0018] Figure 4 This is a schematic diagram of the structure of an edge control device provided as an exemplary embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] To address the technical problem that existing centralized cloud networks can no longer meet the ever-increasing demand for cloud resources on the terminal side, some embodiments of this application incorporate the concept of edge computing, considering placing cloud computing capabilities closer to the terminal side at the edge. Thus, a network system including at least one edge cloud node is provided. In this network system, by combining central control equipment and edge control equipment, the edge cloud node can be fully and comprehensively managed, solving the edge cloud node management problem. This provides the conditions for "processing cloud computing in edge cloud nodes closer to the terminal," thereby enabling the provision of cloud computing services to users using the resources in the edge cloud nodes, which helps reduce response latency and bandwidth costs.

[0021] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0022] Figure 1a This is a schematic diagram of the structure of a network system provided for an exemplary embodiment of this application. For example... Figure 1a As shown, the network system 100 includes: a central control device 101, an edge control device 103, and at least one edge cloud node 102.

[0023] The network system 100 in this embodiment is a cloud computing platform built on edge infrastructure based on cloud computing technology and edge computing capabilities. It is a cloud platform with computing, networking, storage and security capabilities at the edge.

[0024] In contrast to centralized clouds or traditional cloud computing platforms, the network system 100 of this embodiment can be considered an edge cloud network system. Edge cloud is a relative concept; it refers to a cloud computing platform relatively close to the terminal. In other words, it differs from centralized clouds or traditional cloud computing platforms. Centralized clouds or traditional cloud computing platforms can include data centers with large-scale resources and centralized locations, while edge cloud nodes cover a wider network range and are therefore closer to the terminal. A single edge cloud node has a smaller resource scale, but the number of edge cloud nodes is large, and multiple edge cloud nodes constitute the edge cloud in this embodiment. The terminal in this embodiment refers to the demand side of cloud computing services, such as terminals or user terminals in the Internet of Things (IoT). The edge cloud network is a network built based on the infrastructure between a centralized cloud or traditional cloud computing system and the terminal. The network system 100 includes at least one edge cloud node 102, and each edge cloud node 102 includes a series of edge infrastructures, including but not limited to: distributed data centers (DCs), wireless equipment rooms or clusters, operator communication networks, core network equipment, base stations, edge gateways, home gateways, computing devices and / or storage devices, and corresponding network environments, etc. It should be noted that the location, capabilities, and included infrastructure of different edge cloud nodes 102 may or may not be the same.

[0025] In this embodiment, the network system 100, combined with a central cloud or traditional cloud computing platform and other central networks and terminals, can form a "cloud-edge-device three-body collaborative" network architecture. In this network architecture, tasks such as network forwarding, storage, computing and / or intelligent data analysis can be processed in each edge cloud node 102 in the network system 100. Since each edge cloud node 102 is closer to the terminal, response latency can be reduced, the pressure on the central cloud or traditional cloud computing platform can be alleviated, and bandwidth costs can be reduced.

[0026] How to rationally schedule resources from multiple edge cloud nodes and effectively manage them to provide cloud computing services in a correct and stable manner is a significant challenge. In the network system 100 of this embodiment, a central management device 101 is deployed. The central management device 101 can manage at least one edge cloud node 102 within the network system 100, focusing on resource scheduling, image management, instance management, operation and maintenance, network, and security. This allows cloud computing services to be processed on each edge cloud node 102. In terms of deployment, the central management device 101 can be deployed in one or more cloud computing data centers, or in one or more traditional data centers. The central management device 101 can also form an edge cloud network together with the at least one edge cloud node it manages; this embodiment does not impose any limitations on this.

[0027] An edge cloud node 102 can provide various resources to the outside world, such as computing resources like CPU and GPU, storage resources like memory and hard disk, and network resources like bandwidth. Furthermore, the edge cloud node 102 can create corresponding instances based on images and provide various services through these instances. An image is the basic file required for creating an instance in the edge cloud node. For example, it can be an image file containing the operating system, applications, or operation configurations needed to provide cloud computing services to users. It can be a specific series of files created according to a certain format, conforming to the computing deployment requirements of the edge cloud node. In addition, the form of an image is diverse; it can be a Virtual Machine (VM) image file, a Docker image file, or various types of application packages. The image form may be related to the virtualization technology used by the cloud computing service, but this embodiment does not limit this. Corresponding to the image, the implementation form of an instance can be a virtual machine, a container, or an application.

[0028] In this embodiment, the central control device 101 can schedule resources for at least one edge cloud node 102 independently based on resource requirements, and can also manage and distribute images for at least one edge cloud node 102 independently based on image requirements. Alternatively, it can both schedule resources for at least one edge cloud node 102 and provide images to at least one edge cloud node 102 based on service requirements. Service requirements include both resource requirements and image requirements. For example, the central control device 101 can provide a request submission portal, which can be a web page, application page, or command window, etc. The purpose of this request submission portal is to allow requesters to submit their request description information to the central control device 101.

[0029] For resource requesters, resource request description information can be submitted to the central control device 101 through the aforementioned request submission portal. This resource request description information includes: edge cloud node selection parameters and resource selection parameters. The edge cloud node selection parameters include the scheduling domain and / or performance requirements for the edge cloud node, while the resource selection parameters include resource type, resource quantity, and performance requirements for the resource devices. The central control device 101 can perform resource scheduling on at least one edge cloud node based on the resource request description information. Optionally, a resource scheduling method includes: the central control device 101 determining the target edge cloud node to be scheduled and the scheduled resource information in the target edge cloud node from at least one edge cloud node 102 in the network system 100 based on the resource request description information; and controlling the corresponding resource devices in the target edge cloud node to allocate or reserve resources based on the resource information.

[0030] For those requesting image requests, they can submit image request descriptions to the central control device 101 through the aforementioned request submission portal. This description can point to the required image, and may include the image itself, its name, ID, or other identifying information, or descriptions of cloud computing service functions. This information reflects the required image. Based on the image request description, the central control device 101 determines the target image to be provided to the first edge cloud node and provides this target image to the first edge cloud node, allowing it to create corresponding instances and provide the appropriate cloud computing services. The first edge cloud node can be any edge cloud node in the network system 100. For ease of description and distinction, the image to be provided to the first edge cloud node is referred to as the target image.

[0031] For service requesters, service request descriptions can be submitted to the central control device 101 through the aforementioned request submission portal. These descriptions include resource and image request information. For details on resource and image request information, please refer to the preceding descriptions; they will not be repeated here. It is worth noting that resource and image request information can be submitted together or separately. Based on the service request descriptions, the central control device 101 can perform resource scheduling on at least one edge cloud node 102 in the network system 100; and provide mirroring for the scheduled resources on at least one edge cloud node 102 to provide cloud computing services using the scheduled resources on at least one edge cloud node.

[0032] For a detailed description of the above resource scheduling process and the image management and distribution process, please refer to the following embodiments, which will not be elaborated here.

[0033] It is worth noting that in network system 100, the central control device 101 can directly control and schedule at least one edge cloud node 102, but is not limited to this. For example... Figure 1a As shown, in network system 100, in addition to a central control device 101 and at least one edge cloud node 102, an edge control device 103 is also included. The number of edge control devices 103 can be one or more. Furthermore, the edge control device 103 can be deployed in one or more edge cloud nodes 102. In an optional embodiment, as... Figure 1aAs shown, each edge cloud node 102 deploys an edge management device 103. Further, each edge cloud node includes one or more resource devices. Optionally, the edge management device 103 can be centrally deployed on one resource device or distributed across multiple resource devices. In addition to resource devices, each edge cloud node may also include one or more dedicated devices. Optionally, the edge management device 103 can also be centrally deployed on one dedicated device or distributed across multiple dedicated devices. Here, dedicated devices refer to the physical devices used to deploy the edge management device 103, which are different from resource devices. Furthermore, the edge management device 103 can also be deployed together with the central management device 101, without limitation. The central management device 101 can be deployed in one or more cloud computing data centers or traditional data centers, or it can be deployed together with at least one edge cloud node in the edge cloud network.

[0034] In this embodiment, the edge management device 103 can assist and cooperate with the central management device 101 in managing and scheduling at least one edge cloud node 102. With the assistance of the edge management device 103, the central management device 101 can more conveniently and efficiently manage and schedule at least one edge cloud node 102, thereby achieving the goal of fully utilizing edge resources.

[0035] It should be noted that the central control device 101 in this embodiment can be a logical device with capabilities such as resource scheduling, image management, and operation and maintenance management. These functions can be implemented on a single physical machine or virtual machine, or they can be distributed across multiple physical machines or virtual machines. Of course, the central control device in this embodiment can also be one or more physical devices with capabilities such as resource scheduling and image management. This application does not limit the implementation structure of the central control device 101; any device structure with the above capabilities is applicable to this application embodiment.

[0036] Similar to the central control device 101, the edge control device 103 can also be a logical device. Its capabilities can be implemented on a single physical machine (e.g., a resource device or dedicated device in an edge cloud node) or a virtual machine, or distributed across multiple physical machines (e.g., resource devices or dedicated devices in edge cloud nodes) or virtual machines. Of course, the edge control device can also be one or more physical devices with corresponding capabilities. This application does not limit the implementation structure of the edge control device 103; any device structure with corresponding capabilities is applicable to this application.

[0037] In this embodiment, a secure and encrypted communication channel is established between the central management device 101 and the edge management device 103, and interaction is performed based on this communication channel. This communication channel includes a control interface and a data interface. The central management device 101 interacts with the edge management device 103 on the control plane and data plane based on the control interface and data interface to complete the scheduling and management of the edge cloud node 102. The data interface is used for data transmission between the central management device 101 and the edge management device 103. The control interface has, but is not limited to, the following functions:

[0038] 1. Resource scheduling capability: The central control device 101 can perform resource scheduling on edge cloud nodes from multiple dimensions through a control interface with resource scheduling capability (which can be referred to as the resource scheduling interface). The edge cloud nodes are the objects of resource scheduling by the central control device 101.

[0039] 2. Image management and distribution capabilities: The central control device 101 can provide images to edge cloud nodes through a control interface with image management and distribution capabilities (referred to as the image management interface). In this way, the edge cloud nodes can create corresponding instances based on the received images and provide cloud computing services through the instances.

[0040] 3. Operation and maintenance management capabilities: The central control device 101 performs operation and maintenance management on edge cloud nodes through a control interface with operation and maintenance management capabilities (referred to as the operation and maintenance management interface). Operation and maintenance management includes, but is not limited to: managing applications and virtualization software in edge cloud nodes, monitoring instance status, resource usage, and infrastructure.

[0041] Corresponding to the capabilities of the aforementioned control interface, the central control device 101 of this embodiment has, but is not limited to, the following functions:

[0042] 1. Resource scheduling can be performed on edge cloud nodes based on service requirement descriptions, such as service specifications, regions where services need to be deployed, distribution of carrier networks, network latency, load conditions, bandwidth costs, required resource types and / or performance requirements of resource devices.

[0043] 2. It can obtain the images required for cloud computing services, provide the images to the corresponding resource devices in the edge cloud nodes for configuration and installation, so that the corresponding resource devices can create corresponding instances to provide cloud computing services;

[0044] 3. It can manage and control edge cloud nodes, including but not limited to: managing the status, resource usage and / or infrastructure of applications, virtualization components and instances in edge cloud nodes, and enabling remote operation and maintenance, log management, etc.

[0045] In addition to the functions mentioned above, the central control equipment may also have other functions, such as security protection functions, which involve the security of the central control equipment, the link security between the central control equipment and the edge control equipment and the edge cloud nodes, and the security of the edge cloud nodes; and are responsible for maintaining the network information in the network system.

[0046] The following describes the collaborative working process between the central control device 101 and the edge control device 103:

[0047] In network system 100, at least one edge cloud node 102 can form a resource pool. Each edge cloud node 102 acts as a scheduling object, providing various resources or cloud computing services to the outside world under the scheduling of central management device 101. The central management device 101 and edge management device 102 cooperate to independently schedule resources for at least one edge cloud node 102, manage and distribute images for at least one edge cloud node 102, or both schedule resources and provide images for at least one edge cloud node 102. Besides resource scheduling and image management and distribution for edge cloud node 102, managing edge cloud node 102 in other aspects is also a problem that network system 100 needs to solve. Successfully solving this problem is the foundation for "processing cloud computing in edge cloud nodes closer to the terminal." Therefore, the central management device 101 and edge management device 102 cooperate to manage at least one edge cloud node 102 in other aspects.

[0048] In the following embodiments of this application, various functions implemented by the central control device 101 or by the central control device 101 in conjunction with the edge control device 103 will be described.

[0049] Control functions:

[0050] In this embodiment, the central control device can manage at least one edge cloud node with the assistance of the edge control device. Specifically, the edge control device can monitor at least one edge cloud node and report the monitoring data to the central control device, which then manages the at least one edge cloud node based on the monitoring data. The central control device can manage at least one edge cloud node based on the monitoring data reported by the edge control device. Optionally, the edge control device can monitor at least one edge cloud node and report the monitoring data to the central control device under the control of the central control device. Alternatively, the edge control device can periodically monitor at least one edge cloud node and report the monitoring data to the central control device according to a scheduled task. Regardless of the implementation, the edge control device mainly performs monitoring, data collection, and reporting functions, while the control decisions are made by the central control device.

[0051] The central control equipment controls the edge control equipment to monitor at least one edge cloud node, and the following optional implementation methods can be adopted, but are not limited to:

[0052] In one optional implementation, the central control device can send a first type of monitoring instruction to the edge control device, instructing the edge control device to monitor at least one edge cloud node from at least one monitoring dimension and report the monitoring data from at least one monitoring dimension to the central control device. The first type of monitoring instruction is a monitoring instruction that instructs the edge control device to monitor at least one edge cloud node from at least one monitoring dimension and report the monitoring data from at least one monitoring dimension. The edge control device can receive the first type of monitoring instruction sent by the central control device, monitor the at least one edge cloud node from at least one monitoring dimension according to the first type of monitoring instruction, and report the monitoring data from at least one monitoring dimension to the central control device. The central control device manages the at least one edge cloud node based on the monitoring data from at least one monitoring dimension reported by the edge control device. It is worth noting that the at least one monitoring dimension can be flexibly set according to application requirements and pre-configured in both the edge control device and the central control device. Examples of monitoring dimensions are provided in subsequent embodiments.

[0053] In another optional implementation, the central control device can selectively manage at least one edge cloud node on one or more monitoring dimensions. Based on this, the central control device can send a second type of monitoring instruction to the edge control device. This second type of monitoring instruction corresponds to a specified monitoring dimension and instructs the edge control device to monitor at least one edge cloud node on the specified monitoring dimension and report the monitoring data on that dimension. The edge control device can receive the second type of monitoring instruction sent by the central control device, monitor at least one edge cloud node on the specified monitoring dimension according to the instruction, and report the monitoring data on that dimension to the central control device, so that the central control device can manage at least one edge cloud node based on the monitoring data on the specified dimension. The central control device is also used to receive the monitoring data on the specified monitoring dimension sent by the edge control device and manage at least one edge cloud node based on the monitoring data on the specified dimension.

[0054] It's worth noting that there can be one or more specified monitoring dimensions. When there are multiple specified monitoring dimensions, each dimension can correspond to one type of second-level monitoring instruction. This means the central management device can send multiple type-two monitoring instructions to the edge management device, with each instruction corresponding to one specified monitoring dimension. Alternatively, when there are multiple specified monitoring dimensions, these dimensions can also correspond to the same type-two monitoring instruction. In other words, the central management device can send one type-two monitoring instruction to the edge management device, and this instruction can correspond to multiple specified monitoring dimensions.

[0055] Optionally, the edge management device can periodically monitor at least one edge cloud node according to a scheduled task. This can be done by periodically monitoring at least one edge cloud node from at least one monitoring dimension. Furthermore, the monitoring data from at least one monitoring dimension can be reported to the central management device. The monitoring cycles for different monitoring dimensions can be the same or different. For example, the edge management device can perform a security vulnerability scan on the edge cloud node every 10 minutes, or perform traffic monitoring on the edge cloud node every 5 minutes.

[0056] The aforementioned monitoring dimension or specified monitoring dimension may include, but is not limited to, the following dimensions: object dimension in runtime, log dimension, security dimension, resource dimension, etc. Furthermore, the object dimension in runtime may include the object's runtime status dimension and / or the object's lifecycle dimension; the security dimension may include: traffic attack dimension and / or security vulnerability dimension.

[0057] Combining the monitoring dimensions listed above, the central control device, with the assistance of the edge control device, manages at least one edge cloud node, including but not limited to at least one of the following control examples:

[0058] Control Example 1: The central control device controls the edge control device to monitor the status of at least one running object in an edge cloud node. The control method includes sending a first type of monitoring instruction to the edge control device or sending a second type of monitoring instruction corresponding to the running status dimension of the object. Under the control of the central control device, or periodically according to a scheduled task, the edge control device monitors the status of at least one running object in an edge cloud node and reports the running status of the monitored objects to the central control device. The central control device identifies objects with abnormal running status from the running status reported by the edge control device. For ease of description and differentiation, these objects with abnormal running status are referred to as target objects, and anomaly handling is performed on the target objects. The running objects in the edge cloud node include, but are not limited to: instances, images, containers, other virtual components, physical machines, CPUs, and / or hard drives. The abnormal running status conditions will vary depending on the object. For example, for instances, possible abnormal conditions include, but are not limited to, interruptions, errors, and / or failures. For example, for a physical machine, possible abnormal situations include, but are not limited to: system crashes, black screens, alarms, and / or application crashes while running on the physical machine. Depending on the target object and the abnormal running state, the abnormal handling methods will also differ, and may include, but are not limited to: issuing alarms, stopping or restarting the target object, migrating, and / or deleting and rebuilding the target object.

[0059] Control Example 2: The central control device controls the edge control device to monitor the lifecycle of at least one running object in at least one edge cloud node. The control method includes sending a first type of monitoring command or a second type of monitoring command corresponding to the object's lifecycle dimension to the edge control device. Under the control of the central control device, or periodically according to a scheduled task, the edge control device monitors the lifecycle of at least one running object in at least one edge cloud node and reports the monitored lifecycle of the running objects to the central control device. Based on the lifecycle of the running objects reported by the edge control device, the central control device controls the running objects to stop, restart after stopping, migrate, or delete.

[0060] Control Example 3: The central control device controls the edge control device to collect log data from at least one edge cloud node. The control method includes sending a first type of monitoring instruction or a second type of monitoring instruction corresponding to the log dimension to the edge control device. Under the control of the central control device, or periodically according to a scheduled task, the edge control device collects log data from at least one edge cloud node and reports the collected log data to the central control device. The central control device receives the log data reported by the edge control device, performs data analysis on the log data, and executes subsequent actions based on the data analysis results, such as billing, risk control, and / or adding or removing instances. The subsequent actions will vary depending on the log data. Optionally, the log data may include, but is not limited to, various performance and metric data in the edge cloud node, such as: instance bandwidth traffic, current instance operating status, instance IO load, physical machine bandwidth traffic, current physical machine operating status, physical machine IO load, the operating status of the edge control device, and / or the operating status of other virtualization components.

[0061] Optionally, the central control device can not only collect log data from each edge cloud node reported by the edge control device, but also has the ability to inspect data. For some data, if the data stored by the central control device is inconsistent with the data in the edge cloud node, it can actively synchronize the latest data to the edge cloud node, such as synchronizing the latest version of the image to the edge cloud node.

[0062] Control Example 4: The central control device controls the edge control device to monitor the traffic of at least one edge cloud node. The control method includes sending a first type of monitoring command or a second type of monitoring command corresponding to the dimension of traffic attack to the edge control device. Under the control of the central control device, or periodically according to a scheduled task, the edge control device monitors the traffic of at least one edge cloud node and reports any monitored traffic attack events to the central control device. The central control device blocks traffic attack events occurring in the edge cloud nodes. Optionally, the edge control device can also report the monitored traffic data to the central control device, and the central control device can also perform traffic attack defense on at least one edge cloud node based on the traffic data.

[0063] Control Example 5: The central control device controls the edge control device to perform network security vulnerability scanning on at least one edge cloud node. The control method includes sending a first-type monitoring command or a second-type monitoring command corresponding to the network security dimension to the edge control device. Under the control of the central control device, or periodically according to scheduled tasks, the edge control device performs network security vulnerability scanning on at least one edge cloud node and reports the detected network security vulnerabilities to the central control device. The central control device receives the network security vulnerability reports from the edge control device and remediates the vulnerabilities.

[0064] Control Example 6: The central control device controls the edge control device to monitor the resource usage of at least one edge cloud node. The control method includes sending a first type of monitoring command or a second type of monitoring command corresponding to the resource dimension to the edge control device. Under the control of the central control device, or periodically according to a scheduled task, the edge control device monitors the resource usage of at least one edge cloud node and reports the monitored resource usage information to the central control device. Based on the resource usage information reported by the edge control device, the central control device expands or reduces the resource capacity of at least one edge cloud node. The resources here include various resource information, such as physical machine resources, storage resources, computing resources such as CPU and GPU, network resources such as bandwidth, etc.

[0065] Furthermore, if each edge cloud node is equipped with an edge management device, each edge management device can monitor its respective edge cloud node under the control of the central management device, or periodically according to scheduled tasks, and report the monitoring data from its respective edge cloud node to the central management device. The central management device can receive the monitoring data reported by the edge management devices in each edge cloud node and manage each edge cloud node based on the monitoring data.

[0066] This application does not limit the implementation structure of the central control device and the edge control device. Optionally, a structural framework for a central control device is as follows: Figure 1b As shown, it includes: a resource scheduling and control module, an image control module, and a central control module; the central control module further includes: a central monitoring unit, a central logging unit, and a central security unit, etc. Accordingly, the structural framework of an edge control device is as follows: Figure 1b As shown, it includes: a resource scheduling service module, an image service module, and an edge management module; the edge management module further includes: an edge monitoring unit, an edge logging unit, and an edge security unit, etc.

[0067] The resource scheduling and control module in the central control device works in conjunction with the resource scheduling service module in the edge control device to perform resource scheduling for edge cloud nodes. The resource scheduling function is described below. Similarly, the image management module in the central control device works in conjunction with the image service module in the edge control device to manage and distribute images for edge cloud nodes. The image management and distribution function is described below.

[0068] The central control module in the central control device and the edge control module in the edge control device work together to control edge cloud nodes. The control examples 1-6 above can be generated by... Figure 1b The corresponding units in the central control module and edge control module are implemented in cooperation. Control example 3 can be implemented by the central log unit in the central control module and the edge log unit in the edge control module. Specifically, the central log unit sends a first type of monitoring instruction or a second type of monitoring instruction corresponding to the log dimension to the edge log unit; the edge log unit collects log data from the edge cloud nodes according to the first or second type of monitoring instruction and reports it to the central log unit; the central log unit performs data analysis on the log data and executes subsequent actions based on the data analysis results. Control examples 4 and 5 can be implemented by the central security unit in the central control module and the edge security unit in the edge control module. Specifically, the central security unit sends a first type of monitoring instruction or a second type of operation and maintenance instruction corresponding to the traffic attack or network security dimension to the edge security unit; the edge security unit can perform traffic monitoring or network security vulnerability scanning on the edge cloud nodes according to the first or second type of operation and maintenance instruction, and reports the monitored traffic attack events or network vulnerability security issues to the central security unit; the central security unit blocks traffic attack events or repairs network security vulnerability issues. Control examples 1, 2 and 6 can be implemented by the central monitoring unit in the central control module and the edge monitoring unit in the edge control module. The detailed implementation process will not be elaborated here.

[0069] As can be seen from the above, with the assistance of edge management devices, central management devices can understand the health, resource usage, log data and / or infrastructure status of each instance in the edge cloud node, and can realize remote operation and maintenance, log management, etc.

[0070] In this embodiment of the application, in addition to the central control device being able to control at least one edge cloud node, the edge control device can autonomously control at least one edge cloud node when the central control device does not control or is unable to control the edge cloud node.

[0071] For example, edge control devices can monitor their connection with central control devices. If they lose connection with central control devices, they can determine that central control devices cannot control edge cloud nodes. Therefore, they can autonomously control at least one edge cloud node from at least one monitoring dimension.

[0072] For example, in a scenario where the central control device sends a first type of monitoring instruction to an edge control device to control the edge control device to monitor at least one edge cloud node, the edge control device can wait to receive the first type of monitoring instruction from the central control device. If it does not receive the first type of monitoring instruction from the central control device, it can be determined that the central control device is incorrect or unable to control at least one edge cloud node, and can then autonomously control at least one edge cloud node from at least one monitoring dimension. Optionally, the edge control device and the central control device can pre-agree on a waiting time for the first type of monitoring instruction. If the first type of monitoring instruction from the central control device is not received after the specified waiting time, it is determined that the first type of monitoring instruction from the central control device has not been received.

[0073] For example, in a scenario where the central control device sends a second type of monitoring instruction corresponding to a specified monitoring dimension to the edge control device to control the edge control device to monitor at least one edge cloud node from the specified monitoring dimension, the edge control device can wait to receive the second type of monitoring instruction sent by the central control device. If it does not receive the second type of monitoring instruction sent by the central control device in the specified monitoring dimension, it can be determined that the central control device is not or cannot control at least one edge cloud node in the specified monitoring dimension, and can then autonomously control at least one edge cloud node from the specified monitoring dimension.

[0074] Optionally, if the edge control device autonomously manages at least one edge cloud node from at least one monitoring dimension after losing connection with the central control device, it can also synchronize the control data during the period of connection loss to the central control device after reconnecting. It is worth noting that the control data mainly includes control strategies, methods, and effects; of course, it may also include monitoring data.

[0075] The aforementioned monitoring dimension or specified monitoring dimension may include, but is not limited to, the following dimensions: object dimension in runtime, log dimension, security dimension, resource dimension, etc. Furthermore, the object dimension in runtime may include the object's runtime status dimension and / or the object's lifecycle dimension; the security dimension may include: traffic attack dimension and / or security vulnerability dimension.

[0076] Combining the monitoring dimensions listed above, edge control devices autonomously manage at least one edge cloud node, including but not limited to at least one of the following management examples:

[0077] Control Example a: Autonomously monitor the status of objects in running state on at least one edge cloud node, and handle exceptions for target objects with abnormal running states. For details on objects in running state and abnormal running state conditions, please refer to the description above; it will not be repeated here.

[0078] Optionally, in Example a, when the edge control device performs anomaly handling on the target object, it is specifically used to: analyze the abnormal operating state of the target object, determine at least one candidate handling method based on the analysis results; obtain the target handling method from the at least one candidate handling method, and perform anomaly handling on the target object according to the target handling method.

[0079] Furthermore, when acquiring a target processing method, the edge control device specifically performs the following actions: when maintaining a connection with the central control device, it reports at least one candidate processing method to the central control device for selection; it receives the processing method returned by the central control device as the target processing method; or, when the edge control device loses connection with the central control device, it outputs at least one candidate processing method to the edge control personnel for selection; in response to the selection operation of the edge control personnel, it determines the selected processing method as the target processing method; or, when losing connection with the central control device, it selects the target processing method from at least one candidate processing method according to a set selection strategy.

[0080] Example b of the management system: Autonomously monitor the lifecycle of running objects on at least one edge cloud node, and control the stopping, restarting, or deletion of running objects based on the monitoring results. For containers or instances, it can control the stopping, restarting, or deletion of containers or instances.

[0081] Management Example c: Autonomously collect log data from at least one edge cloud node, perform data analysis on the log data, and execute subsequent actions based on the analysis results. Log data includes, but is not limited to, the bandwidth traffic of instances in the edge cloud node, the current operating status of the instances, the IO load of the instances, the bandwidth traffic of physical machines, the current operating status of physical machines, the IO load of physical machines, the operating status of edge management devices, and / or the operating status of other virtualization components. Optionally, subsequent actions such as billing, risk control, and / or resource reallocation can be performed based on the analysis results of the log data, but are not limited to these.

[0082] Example of management and control d: Autonomously monitor the traffic of at least one edge cloud node and block any traffic attack events detected.

[0083] Control Example e: Autonomously scan at least one edge cloud node for network security vulnerabilities and remediate the network security vulnerabilities detected.

[0084] Management Example f: Autonomously monitor the resource usage of at least one edge cloud node, and expand or reduce the resource capacity of at least one edge cloud node based on the monitoring results. These resources include, but are not limited to: physical machine resources, storage resources such as memory and disk, computing resources such as CPU and GPU, and network resources such as bandwidth. For these resources, expansion can be performed when usage is high, and reduction can be performed when usage is low.

[0085] Furthermore, if each edge cloud node is equipped with an edge management device, then each edge management device can autonomously manage its own edge cloud node even if the central management device is unable or unable to manage it.

[0086] Optionally, in Examples a-e above, where the edge management device autonomously manages at least one edge cloud node, the edge management device can periodically manage at least one edge cloud node according to a scheduled task. For example, in Example d, the edge management device can monitor the traffic of at least one edge cloud node every 10 minutes according to a scheduled task and block any traffic attacks detected. As another example, in Example e, the edge management device can perform network security vulnerability scanning on at least one edge cloud node every 5 minutes according to a scheduled task and fix any network security vulnerabilities detected. Of course, the edge management device can also autonomously manage at least one edge cloud node according to other autonomous policies, such as autonomously managing at least one edge cloud node at a fixed time each day.

[0087] In some optional embodiments, the aforementioned control can be operational / maintenance-level control. For example, the central control device can perform operational / maintenance control on at least one edge cloud node with the assistance of the edge control device. In an operational / maintenance control scenario, the aforementioned at least one monitoring dimension or designated monitoring dimension can be an operational / maintenance dimension. The central control device can then perform operational / maintenance control on at least one edge cloud node based on the monitoring data reported by the edge control device on at least one operational / maintenance dimension or a designated operational / maintenance dimension. Alternatively, if the central control device does not perform operational / maintenance control on the edge cloud node or is unable to perform such control, the edge control device can autonomously perform operational / maintenance control on at least one edge cloud node. For example, the edge control device can perform operational / maintenance control on at least one edge cloud node based on the monitoring data on at least one operational / maintenance dimension or a designated operational / maintenance dimension. For details regarding the operational / maintenance control of at least one edge cloud node by the central control device or the edge control device, please refer to the foregoing embodiments, which will not be repeated here.

[0088] In the context of operation and maintenance management, as illustrated in Examples 1-6 and Example af above, in this embodiment, the central management device and the edge management device are combined. The central management device can perform operation and maintenance management on at least one edge cloud node with the assistance of the edge management device. In addition, the edge management device also has a certain degree of self-operation and maintenance management capability. It can autonomously perform operation and maintenance management on the edge cloud node when the central management device is unable or unable to perform operation and maintenance management on the edge cloud node, thus achieving two-level operation and maintenance management. This allows for more comprehensive and thorough operation and maintenance management of the edge cloud node, providing the conditions for "processing cloud computing in edge cloud nodes closer to the terminal." Consequently, the resources in the edge cloud node can be used to provide cloud computing services to users, which helps reduce response latency, alleviate the pressure on the central cloud or traditional cloud computing platform, and reduce bandwidth costs.

[0089] Resource scheduling function:

[0090] The central control device can perform resource scheduling for at least one edge cloud. This mainly involves determining, based on service demand description information, the target edge cloud node to be scheduled from at least one edge cloud node 102 in the network system 100, along with the resource information to be scheduled within that target edge cloud node. This resource information is then sent to the edge control device 103, which controls the corresponding resource devices within the target edge cloud node to allocate or reserve resources. Optionally, the number of target edge cloud nodes can be specified by the user or determined autonomously by the resource center control device based on the service demand description information; it can be one or multiple. The service demand description information can be directly submitted by the service requester or extracted or calculated from service-related information submitted by the service requester. The service requester can be a user, an application, a physical machine, or another service requiring a specific service.

[0091] The resource scheduling function described here mainly includes, but is not limited to, two aspects: the selection of edge cloud nodes and resource scheduling within edge cloud nodes. Specifically, resource scheduling within edge cloud nodes involves determining the resources to be scheduled within the target edge cloud node and providing that information. The primary purpose is to allocate cloud computing services to the final underlying resources, such as servers, at the granularity of each edge cloud node. The central management device maintains information about the resources contained in each edge cloud node, serving as the basis for resource scheduling.

[0092] Optionally, the service requirement description information includes edge cloud node selection parameters and resource selection parameters. Edge cloud node selection parameters refer to the parameters required to select the target edge cloud node; resource selection parameters refer to the information required to select the resources to be scheduled within the edge cloud node. Based on this, the central control device can parse the edge cloud node selection parameters and resource selection parameters from the service requirement description information; determine the target edge cloud node to be scheduled from at least one edge cloud node based on the edge cloud node selection parameters; and determine the resource information to be scheduled within the target edge cloud node based on the resource selection parameters.

[0093] For example, the service requirement description information may include QoS requirements for the scheduling domain and / or cloud computing services. These parameters can be used as selection parameters for edge cloud nodes. The scheduling domain refers to the region where cloud computing services need to be deployed, which determines the geographical location of the edge cloud node to be scheduled. The QoS requirements for cloud computing services may include the cloud computing service's requirements regarding network latency, load conditions, and / or bandwidth costs. Based on this, the central management device can select an edge cloud node that meets the scheduling domain and / or QoS requirements as the target edge cloud node, based on the QoS requirements of the scheduling domain and / or cloud computing services, combined with the geographical location and remaining resource availability of at least one edge cloud node.

[0094] For example, the central control device can select the edge cloud node pointed to by the scheduling domain as the target edge cloud node based on the scheduling domain and the geographical location of at least one edge cloud node. Alternatively, the central control device can also select the edge cloud node that meets the QoS requirements of cloud computing services, such as network latency, load conditions, and / or bandwidth cost requirements, as the target edge cloud node. Of course, the central control device can also select the edge cloud node that can simultaneously meet the scheduling domain and QoS requirements of cloud computing services, combined with the geographical location and remaining resources of at least one edge cloud node, as the target edge cloud node.

[0095] In addition to QoS requirements for the scheduling domain and / or cloud computing services, the service requirement description information may also include parameters such as the resource type, quantity, and / or performance of the resource devices required by the cloud computing services. These parameters can serve as resource selection parameters. Based on this, after determining the target edge cloud node, the central control device can determine the scheduled resource information within the target edge cloud node according to the resource selection parameters. This resource information can include: resource type, resource quantity, and / or performance requirements for resource devices, facilitating the edge control device to control the allocation or reservation of resources for the corresponding resource devices in the target edge cloud node. For example, resource types may include, but are not limited to: computing resources such as CPU and GPU, storage resources such as memory and hard disk, and bandwidth resources. For example, the quantity of CPU resources could be 12 CPUs, 24 CPUs, etc.; the quantity of memory resources could be 16GB or 32GB; and the quantity of bandwidth resources could be 1Mbps or 10Mbps.

[0096] Optionally, the central control equipment can also have computing power orchestration capabilities. Computing power orchestration is designed for more complex application scenarios, binding multiple cloud computing services together as the smallest unit of resource demand. In this way, during resource scheduling, the multiple bound cloud computing services can be treated as a whole, selecting the same or several edge cloud nodes for them to jointly provide resources. Computing power orchestration enhances the diversity and flexibility of resource scheduling without affecting the overall resource scheduling process.

[0097] Combination Figure 1b The implementation structure of the central control device and the edge control device shown is illustrated. The above-mentioned resource scheduling function can be implemented by the resource scheduling control module and the resource scheduling service module working together. The detailed process will not be repeated here.

[0098] Image management and distribution functions:

[0099] The image management function of the central control device mainly refers to the management of images and the provision of the required images to edge cloud nodes. In this way, edge cloud nodes can create instances on the corresponding resource devices based on the images, and then the created instances can provide users with the necessary cloud computing services.

[0100] In practical applications, there are various scenarios where mirroring is required for edge cloud nodes. For example, when a user (e.g., a service requester) submits a service request description, the central management device can provide a corresponding mirror for the target edge cloud node. Another example is when an edge cloud node already provides cloud computing services to a user; if the user needs to expand their service, they can submit an expansion request to the central management device. To achieve this expansion, a corresponding mirror needs to be provided to the edge cloud node currently providing cloud computing services, so that the edge cloud node can create new instances based on the mirror, thus achieving the expansion goal. For ease of description and distinction, the edge cloud node requiring a mirror in the following description will be referred to as the first edge cloud node. The first edge cloud node can be any edge cloud node in the network system, depending on the application scenario. The following example of the central management device providing a mirror to the first edge cloud node illustrates the mirror management function of the central management device.

[0101] When it is necessary to provide an image to the first edge cloud node, the central control device can first determine the target image that needs to be provided to the first edge cloud node; then, it can provide the target image to the first edge cloud node so that the first edge cloud node can use the target image to provide cloud computing services.

[0102] In the network system 100 of this embodiment, an image library is maintained to store images within the system. Users can select images from the image library. For example, an image configuration interface can be provided to users, featuring a drop-down menu with a variety of images available for selection. Based on this, when an image needs to be provided to a first edge cloud node, the central control device can retrieve the required image from the image library, provide the image to the first edge cloud node, and grant access to the image to the corresponding user. Optionally, the central control device can directly send the target image to the first edge cloud node or instruct the first edge cloud node to download the target image from a specified storage location.

[0103] In addition, the central control equipment can maintain the correspondence between distributed images and the edge cloud nodes where those images reside. This correspondence can include the identification information of the distributed images and the identification information of the edge cloud nodes where the distributed images reside. A distributed image refers to an image that the central control equipment has provided (e.g., distributed) to one or more edge cloud nodes; the edge cloud node where the distributed image resides refers to the edge cloud node to which the distributed image was provided. The same image may be provided (e.g., distributed) to one edge cloud node or to multiple edge cloud nodes.

[0104] Based on the maintained correspondence between the distributed images and the edge cloud nodes where the distributed images are located, when it is necessary to provide an image to the first edge cloud node, the central management device can also control the first edge cloud node to obtain the image from other edge cloud nodes that already have the image, without having to directly provide the image to the first edge cloud node. This can reduce the processing burden of the central management device to a certain extent, and under reasonable control, it can also improve the efficiency of image acquisition.

[0105] In detail, when it is necessary to provide an image to the first edge cloud node, the central control device can determine the image that needs to be provided to the first edge cloud node. For ease of description and distinction, in this embodiment, the image that needs to be provided to the first edge cloud node is denoted as the target image. Based on the information of the target image, a match is made in the maintained correspondence between distributed images and the edge cloud nodes where the distributed images are located. If a second edge cloud node corresponding to the target image is matched in the correspondence, it means that the target image has been provided to the second edge cloud node, and the target image at the second edge cloud node can be provided to the first edge cloud node. The second edge cloud node can also be an edge cloud node in the network system, and its number can be one or more. For the first edge cloud node, the target image at the second edge cloud node can be obtained under the control of the central control device 101.

[0106] In the case where network system 100 includes edge management device 103, the central management device can specifically send information about the second edge cloud node and the target image to the edge management device. Based on this information, the edge management device 103 provides the target image from the second edge cloud node to the corresponding resource device in the first edge cloud node. The corresponding resource device then creates an instance that provides cloud computing services based on the target image, thereby providing the cloud computing service to the service requester. The information about the second edge cloud node can be any information that can identify it, such as its ID, name, or geographical location. The information about the target image can be any information that can identify it, such as its ID, name, or number.

[0107] Furthermore, when edge management devices 103 are deployed in both the first and second edge cloud nodes, the central management device 101 can specifically send information about the second edge cloud node and the target image to the edge management device in the first edge cloud node. This allows the edge management device in the first edge cloud node to obtain the target image from the second edge cloud node through its communication channel with the edge management device in the second edge cloud node and provide it to the corresponding resource device in the first edge cloud node. The edge management device 103 in the first edge cloud node can receive the information about the second edge cloud node and the target image sent by the central management device 101. Based on this information, it obtains the target image from the second edge cloud node through its communication channel with the edge management device in the second edge cloud node and provides the target image to the corresponding resource device in the first edge cloud node. The corresponding resource device then creates an instance that can provide cloud computing services based on the target image, thereby providing cloud computing services.

[0108] Furthermore, a process by which the edge management device 103 in the first edge cloud node obtains the target image from the second edge cloud node through its communication channel with the edge management device in the second edge cloud node includes: the edge management device 103 in the first edge cloud node sends a request to the edge management device 103 in the second edge cloud node to obtain the target image, the request carrying information about the target image. The edge management device 103 in the second edge cloud node receives the request, determines whether the target image exists in the second edge cloud node based on the target image information carried in the request, and if the target image exists in the second edge cloud node, returns the target image to the edge management device 103 in the first edge cloud node through its communication channel with the edge management device 103 in the first edge cloud node, or returns the storage address of the target image in the second edge cloud node to the edge management device 103 in the first edge cloud node. The edge control device 103 in the first edge cloud node receives the target image returned by the edge control device 103 in the second edge cloud node, or receives the storage address of the target image in the second edge cloud node returned by the edge control device 103 in the second edge cloud node, and reads or downloads the target image according to the storage address.

[0109] It is worth noting that the edge management device 103 in the first edge cloud node and the edge management device 103 in the second edge cloud node can establish a communication channel independently, or they can establish a channel under the control of the central management device 101. Optionally, the central management device can also control the establishment of communication channels between different edge management devices and is responsible for maintaining information on existing communication channels between edge management devices, such as which edge management devices have established communication channels, when the communication channels were established, the status of the communication channels, and the duration of the communication channels. Based on this, after determining that the target image has been provided to the second edge cloud node, and before providing the information of the second edge cloud node and the target image to the edge management device in the first edge cloud node, the central control device can also determine whether a communication channel already exists between the edge management device in the first edge cloud node and the edge management device in the second edge cloud node, based on the information of the existing communication channels maintained between the edge management devices. If the determination result is negative, meaning that a communication channel does not yet exist between the edge management device in the first edge cloud node and the edge management device in the second edge cloud node, the central control device can control the edge management device in the first edge cloud node and the edge management device in the second edge cloud node to establish a communication channel, so that the edge management device in the first edge cloud node can obtain the target image from the second edge cloud node through this communication channel. Furthermore, after the edge management device in the first edge cloud node establishes a communication channel with the edge management device in the second edge cloud node, the central control device provides the information of the second edge cloud node and the target image to the edge management device in the first edge cloud node. Of course, if the judgment result is yes, that is, there is already a communication channel between the edge control device in the first edge cloud node and the edge control device in the second edge cloud node, then the information of the second edge cloud node and the target image can be directly provided to the edge control device in the first edge cloud node.

[0110] It is worth noting that after the central control device provides the information of the second edge cloud node and the target image to the edge control device in the first edge cloud node, it can also determine whether a communication channel already exists between the edge control device in the first edge cloud node and the edge control device in the second edge cloud node based on the information of the existing communication channels between the maintained edge control devices. If the determination result is no, that is, there is no communication channel between the edge control device in the first edge cloud node and the edge control device in the second edge cloud node, it can control the edge control device in the first edge cloud node and the edge control device in the second edge cloud node to establish a communication channel so that the edge control device in the first edge cloud node can obtain the target image from the second edge cloud node through the communication channel.

[0111] In some optional embodiments, in order to ensure the efficiency of the first edge cloud node in acquiring the target image, the central control device may, before providing the target image at the second edge cloud node to the first edge cloud node, determine whether the second edge cloud node is suitable for providing the target image to the first edge cloud node based on the attributes of the second edge cloud node; if the determination result is yes, that is, the second edge cloud node is suitable for providing the target image to the first edge cloud node, then the target image at the second edge cloud node can be provided to the first edge cloud node; if the determination result is no, then the target image can be obtained from the image library and provided to the first edge cloud node.

[0112] It's worth noting that, depending on the application scenario and requirements, the suitability of a second edge cloud node for providing a target image for a first edge cloud node can be determined from different perspectives by considering the various attributes of the second edge cloud node. An example is provided below:

[0113] For example, by combining the operator to which the second edge cloud node belongs, it can be determined whether the operator to which the second edge cloud node belongs is the same as that to which the first edge cloud node belongs. If the result is yes, it means that the second edge cloud node and the first edge cloud node are edge cloud nodes under the same operator, and the two can transmit data. Moreover, the data transmission rate is faster than the data transmission rate across operators, making it suitable to provide a target image for the first edge cloud node.

[0114] For example, by combining the location attributes of the second edge cloud node, it can be determined whether the distance between the second edge cloud node and the first edge cloud node is less than a set distance threshold. If the result is yes, it means that the second edge cloud node is relatively close to the first edge cloud node, making it suitable to provide a target mirror for the first edge cloud node. In this way, having the second edge cloud node, which is closer to the first edge cloud node, provide a mirror for the first edge cloud node facilitates the first edge cloud node to quickly obtain the mirror, improving efficiency. The distance between the second edge cloud node and the first edge cloud node can be the average distance between the two edge cloud nodes, the distance between the centers of the two edge cloud nodes, or the distance between the nearest outer edges of the two edge cloud nodes, etc., and can be flexibly defined according to requirements.

[0115] For example, the bandwidth attributes of the second edge cloud node can be combined to determine whether the available bandwidth of the second edge cloud node is greater than the set bandwidth threshold. If the result is yes, it means that the bandwidth resources of the second edge cloud node are relatively abundant and suitable for providing the target image to the first edge cloud node. In this way, the second edge cloud node with abundant bandwidth resources can provide the image to the first edge cloud node, which can ensure the transmission rate of the image and facilitate the first edge cloud node to quickly obtain the image, thereby improving efficiency.

[0116] For example, the load attributes of the second edge cloud node can be combined to determine whether the load of the second edge cloud node is less than the set load threshold. If the result is yes, it means that the load of the second edge cloud node is relatively light and it is suitable to provide the target image for the first edge cloud node. In this way, the second edge cloud node with a lighter load can provide the image for the first edge cloud node, which can achieve load balancing on the one hand and facilitate the first edge cloud node to quickly obtain the image on the other hand, thus improving efficiency.

[0117] It is worth noting that the methods listed above can be used individually or in any combination. The combination of methods will not be described in detail here.

[0118] Furthermore, when there are multiple second edge cloud nodes, the above methods can be combined by considering multiple attributes of the second edge cloud nodes to select a suitable second edge cloud node to provide a target image for the first edge cloud node. For example, if there are multiple second edge cloud nodes, the second edge cloud node belonging to the same operator as the first edge cloud node can be selected based on the operator to which the multiple second edge cloud nodes belong. Furthermore, if there are still multiple selected second edge cloud nodes, the second edge cloud node with the smallest load or below a set load threshold can be selected to provide a target image for the first edge cloud node based on the load of the selected second edge cloud nodes.

[0119] In some alternative embodiments, the target image may have already been provided to the first edge cloud node. For example, in a business expansion scenario, the image used to create a new instance in an edge cloud node that is currently providing cloud computing services to service requesters is the same as the image used by the previous instance. If the edge cloud node still has the image used by the previous instance, then it is not necessary to provide the image to the edge cloud node again. To address this situation and conserve resources, before providing the target image from the second edge cloud node to the first edge cloud node, the central control device can determine whether the first edge cloud node is included in the maintained correspondence between distributed images and their corresponding edge cloud nodes. If the determination is yes, it indicates that the target image has already been provided to the first edge cloud node, and the first edge cloud node still stores the target image. In this case, the target image information can be provided to the first edge cloud node so that it can read the stored target image without needing to transmit it again, thus saving network resources consumed in transmitting the target image. If the determination is no, it indicates that the target image has not yet been provided to the first edge cloud node, or the target image no longer exists in the first edge cloud node. In this case, the target image from the second edge cloud node can be provided to the first edge cloud node. In the case where an edge management device is deployed in the first edge cloud node, if the central management device determines that the correspondence between the distributed images it maintains and the edge cloud nodes where the distributed images are located includes the target image, it can provide the target image information to the edge management device in the first edge cloud node. The edge management device in the first edge cloud node can obtain the target image from the image storage space in the first edge cloud node based on the target image information, and provide the target image to the corresponding resource device in the first edge cloud node so that the corresponding resource device can create an instance that can provide cloud computing services based on the target image.

[0120] Optionally, the same edge cloud node may provide multiple cloud computing services to the same user or different users, and thus may receive multiple images, which will be stored in the edge cloud node. The edge cloud node can provide a certain amount of storage space to store these images. Considering the limited storage space for images in the edge cloud node, in order to have sufficient storage space for newly received images, the edge cloud node needs to perform image eviction processing on its locally stored images. In this embodiment, the central management device is responsible for providing image eviction policies to the edge cloud nodes. The central management device can generate image eviction policies and distribute them to each edge cloud node, which then evicts the stored images according to the policy. Where the network system includes an edge management device, the central management device can distribute the eviction policy to the edge management device, which then evicts the images stored in each edge cloud node according to the policy. Furthermore, with edge management devices deployed in each edge cloud node, the central management device can distribute the elimination policy to the edge management devices in each edge cloud node, and the edge management devices in each edge cloud node can then eliminate the images stored in their respective edge cloud nodes according to the elimination policy.

[0121] Optionally, the eviction policy can be an earliest received time eviction policy, that is, eviction of the image with the earliest received time is prioritized. Alternatively, the eviction policy can be a least frequent use eviction policy, that is, eviction of the image with the least frequent use is prioritized. Alternatively, the eviction policy can be a maximum resource consumption eviction policy, that is, eviction of the image with the largest storage space consumption is prioritized.

[0122] For edge cloud nodes, the images stored in the node can be periodically evicted according to the aforementioned eviction policy. Alternatively, whenever a new image needs to be received or acquired, the node can determine if it has sufficient storage space to store the new image. If insufficient storage space exists, the existing images stored in the node can be evicted according to the aforementioned eviction policy to facilitate the storage of the new image. Taking the example of a first edge cloud node needing to acquire a target image from a second edge cloud node, before the edge control device in the first edge cloud node acquires the target image from the second edge cloud node, the edge control device in the first edge cloud node can determine if it has sufficient storage space to store the target image. If insufficient storage space exists, the existing images stored in the first edge cloud node can be evicted according to the eviction policy to ensure sufficient storage space for the target image. Optionally, if the first edge cloud node has sufficient storage space, the existing images stored in the first edge cloud node can be temporarily left un-evicted.

[0123] Optionally, such as Figure 1c As shown, the network system 100 also includes an image building device 104. This image building device 104 can be deployed in one or more edge cloud nodes and is primarily responsible for building and verifying application images. The image building device 104 can provide an edge cloud environment, build images adapted to that environment, verify image compatibility, and reconstruct or output incompatibility warnings for incompatible images. Based on the image building device 104, users can add new images to the network system 100.

[0124] In one alternative implementation of adding a new image, a user (e.g., a service requester) can submit a first request to the central management device to add a new image, the first request including image build information; the central management device sends a build request to the image building device, the build request including image build information; after receiving the build request, the image building device obtains the image build information from it, builds an image adapted to the edge cloud environment according to the image build information, and returns the built image to the central management device; the central management device receives the newly built image returned by the image building device and adds it to the image library, continuously enriching the image library.

[0125] In another optional implementation of adding an image, a set of rules and specifications for images can be provided to users (e.g., service requesters), allowing users to create or generate their own images. The images created or generated by users must meet the security, specifications, and other relevant requirements of the edge cloud environment. After creating or generating an image, the user can send a second request for adding an image to the central management device. This second request includes the image to be added, which refers to the image created or generated by the user. This embodiment does not limit the method by which the user creates or generates the image. The central management device receives the second request, obtains the image to be added from the second request, and sends the image to be added to the image building device. The image building device adapts the image to be added to the edge cloud environment. If the image to be added is adapted to the edge cloud environment, the image building device returns a message to the central management device indicating that the image to be added is adapted to the edge cloud environment; if the image to be added is not adapted to the edge cloud environment, the image building device returns a message to the central management device indicating that the image to be added is not adapted to the edge cloud environment.

[0126] For the central control device, if it receives a message from the image building device indicating that the image to be added is compatible with the edge cloud environment, it adds the image to the image library. If it receives a message from the image building service indicating that the image to be added is incompatible with the edge cloud environment, it either notifies the user to reconstruct the image and resubmit it, or notifies the user to provide a reconstruction method for the image to be added, so that the image building service can reconstruct the image to be added according to the reconstruction method to adapt it to the edge cloud environment. If the user provides a reconstruction method for the image to be added, the central control device can provide the reconstruction method to the image building device, which will reconstruct the image to be added according to the reconstruction method to adapt it to the edge cloud environment and return the reconstructed image to the central control device. The central control device receives the reconstructed image and adds it to the image library.

[0127] It should be noted that the image building device 104 can be a logical device with image building and verification functions. These functions can be implemented on a single physical machine or virtual machine, or they can be distributed across multiple physical machines or virtual machines. Of course, the image building device 104 in this embodiment can also be one or more physical devices with image building and verification functions. This application embodiment does not limit the implementation structure of the image building device; any device structure with the above functions is applicable to this application embodiment.

[0128] In this embodiment, not only can images be added to the image library, but unused or long-unused images can also be deleted to save storage space. For example, the central management device can periodically or in real-time count the usage frequency of each image in the image library, designate images with usage frequencies below a frequency threshold as images to be deleted, and execute the image deletion process to remove them. Alternatively, the central management device can also receive image deletion requests submitted by users (e.g., service requesters), designate the images to be deleted in the request as images to be deleted, and execute the image deletion process to remove them. The image deletion request may carry information about the image to be deleted, such as its ID, name, or number.

[0129] For the central control equipment, the image to be deleted can be determined using any of the methods mentioned above, but not limited to these. After determining the image to be deleted, it can either delete the image from the image library or instruct the edge cloud node storing the image to delete it. Specifically, the central control equipment can match the image to be deleted against the maintained mapping between distributed images and their corresponding edge cloud nodes. Based on the matching result, it determines the edge cloud node storing the image to be deleted. If a third edge cloud node corresponding to the image to be deleted is matched in this mapping, it indicates that the image to be deleted was previously distributed to the third edge cloud node, and the third edge cloud node still stores the image to be deleted. Therefore, a deletion command is sent to the third edge cloud node, carrying information about the image to be deleted, instructing the third edge cloud node to delete the image stored there. There may be one or more third edge cloud nodes.

[0130] In the case where network system 100 includes edge management device 103, the central management device can send a deletion command to the edge management device 103. The edge management device 103 receives the deletion command from the central management device, retrieves the information of the image to be deleted from the command, and determines whether the image to be deleted is stored in the third edge cloud node based on this information. If the image to be deleted is stored, it is deleted from the third edge cloud node. Furthermore, if the third edge cloud node has an edge management device 103 deployed therein, the central management device 101 can send a deletion command to the edge management device 103 in the third edge cloud node. The edge management device 103 in the third edge cloud node receives the deletion command from the central management device, retrieves the information of the image to be deleted from the command, and determines whether the image to be deleted is stored in the third edge cloud node based on this information. If the image to be deleted is stored, it is deleted from the third edge cloud node.

[0131] The image deletion process is complete once the central control device removes the image to be deleted from the image library, and the edge cloud node storing the image to be deleted also deletes the image stored therein.

[0132] For resource devices in edge cloud nodes, regardless of the method used, after acquiring the image, under the control of edge management device 103, they can provide computing, network, and storage resources to the instance in a virtualized form through hardware or software capabilities. The corresponding image will be mounted to the corresponding instance as a system disk. After the instance is created, an attempt is made to start the instance. After the corresponding instance is successfully started, the capabilities of these resource devices can be used to provide cloud computing services. The provision of computing, network, and storage resources by resource devices to the instance under the control of the edge management device includes: the edge management device applying for relevant computing, storage, and / or network resources from the resources allocated or reserved within the target edge cloud node according to the resource template provided by the central management device; and performing resource creation actions by calling the computing, storage, and network executors within the target edge cloud node. The resource creation actions include: processing storage-related resources; creating the instance's system disk according to the image's configuration information and content; creating the corresponding data disk according to the resource template; creating network resources that the instance depends on, such as IP addresses and virtual switches; and creating computing resources in conjunction with the resource template.

[0133] Combination Figure 1b The implementation structure of the central control device and the edge control device shown is illustrated. The above-mentioned image management and distribution functions can be implemented by the image control module and the image service module working together. The detailed process will not be described in detail.

[0134] In summary, the network system provided in this application embodiment uses a centralized management approach to uniformly manage and control the resource scheduling, image management, and operation and maintenance of edge cloud nodes. This approach can maximize the management and coordination of edge cloud nodes, reduce errors caused by single-point self-management or network-wide information asynchrony, and optimize resource scheduling by leveraging the characteristics of centralized management and control, thus avoiding the waste of local edge resources.

[0135] In addition to the network system described above, this application provides a management method from the perspective of edge management devices, which will be described in detail below.

[0136] Figure 2a This is a flowchart illustrating a control method provided for an exemplary embodiment of this application. This embodiment is described from the perspective of an edge control device, such as... Figure 2a As shown, the method includes:

[0137] 21a. Determine that the central control device in the network system is incorrect or unable to control at least one edge cloud node in the network system.

[0138] 22a. Autonomously manage at least one edge cloud node.

[0139] In one optional embodiment, when the edge control device determines that the central control device is incorrect or unable to control the edge cloud nodes, it may employ at least one of the following methods:

[0140] Method 1: Determine whether the connection with the central control device is maintained. If the connection with the central control device is lost, determine that the central control device cannot control the edge cloud node.

[0141] Method 2: The central control device sends a first-type monitoring command to the edge control device to control the edge control device to monitor at least one edge cloud node. Based on this, the edge control device can determine whether it has received the first-type monitoring command sent by the central control device. If it has not received the first-type monitoring command sent by the central control device, it determines that the central control device is incorrect or unable to control the edge cloud node. Optionally, the edge control device and the central control device can pre-agree on a waiting time for the first-type monitoring command. If the first-type monitoring command sent by the central control device is not received after the waiting time, it is determined that the first-type monitoring command sent by the central control device has not been received.

[0142] Method 3: The central control device sends a second type of monitoring instruction corresponding to a specified monitoring dimension to the edge control device to control the edge control device to monitor at least one edge cloud node from the specified monitoring dimension. Based on this, the edge control device can determine whether it receives the second type of monitoring instruction sent by the central control device in the specified monitoring dimension; if it does not receive the second type of monitoring instruction sent by the central control device in the specified monitoring dimension, it determines that the central control device is not or cannot control the edge cloud node in the specified monitoring dimension.

[0143] Furthermore, in Method 1, after the edge control device and the central control device reconnect, the edge control device can also synchronize the control data during the period of disconnection to the central control device.

[0144] Regardless of the method used, if it is determined that the central control device is incorrect or unable to control the edge cloud nodes in the specified monitoring dimension, the edge control device can autonomously control the edge cloud nodes. Optionally, the edge control device's control of the edge cloud nodes includes, but is not limited to, at least one of the following operations:

[0145] Monitor the status of objects in the running state in at least one edge cloud node, and handle exceptions for target objects whose running status is abnormal.

[0146] Monitor the lifecycle of objects in the running state in at least one edge cloud node, and control the objects in the running state to stop, restart after stopping, migrate or delete based on the monitoring results;

[0147] Collect log data from at least one edge cloud node, perform data analysis on the log data, and execute subsequent actions based on the data analysis results;

[0148] Traffic monitoring is performed on at least one edge cloud node, and traffic attack events detected are blocked.

[0149] Perform network security vulnerability scanning on at least one edge cloud node and remediate the network security vulnerabilities detected.

[0150] Monitor the resource usage of at least one edge cloud node, and expand or reduce the resource capacity of at least one edge cloud node based on the monitoring results.

[0151] Alternatively, when handling anomalies in a target object whose operating status is abnormal, the abnormal operating status of the target object can be analyzed, and at least one candidate handling method can be determined based on the analysis results; the target handling method can be obtained from the at least one candidate handling method, and the target object can be handled according to the target handling method.

[0152] Optionally, the target processing method is obtained from at least one candidate processing method, including:

[0153] While maintaining connection with the central control equipment, at least one candidate processing method is reported to the central control equipment for selection; the processing method returned by the central control equipment is received as the target processing method; or

[0154] In the event of a loss of connection with the central control equipment, at least one candidate processing method is output to the edge control personnel for selection; in response to the selection operation by the edge control personnel, the selected processing method is determined as the target processing method; or

[0155] In the event of a loss of connection with the central control equipment, a target processing method is selected from at least one candidate processing method according to a pre-defined selection strategy. The selection strategy can be flexibly configured based on the application scenario, and this application does not impose any limitations on it. For example, the selection strategy could be to choose the simplest processing method, or the processing method with the least resource consumption, and so on. The performance or attributes of each processing method can be known in advance or determined in real time.

[0156] It is worth noting that, while maintaining a connection between the edge control device and the central control device, at least one candidate processing method can be output to the edge control personnel, who can then select the target processing method from among them. This application embodiment does not limit this; for example, it can be output to the terminal devices used by the edge control personnel, such as mobile phones and computers, via SMS, in-app messages, system messages, and / or emails.

[0157] Furthermore, if each edge cloud node is equipped with an edge management device, then each edge management device can autonomously manage its own edge cloud node even if the central management device is unable or unable to manage it.

[0158] Optionally, the edge control device can autonomously manage at least one edge cloud node, periodically according to scheduled tasks. Alternatively, the edge control device can also autonomously manage at least one edge cloud node using other autonomous strategies, such as managing at least one edge cloud node at a fixed time each day.

[0159] Furthermore, in addition to autonomously managing at least one edge cloud node, the edge management device can also assist the central management device in managing at least one edge cloud node. For example... Figure 2b As shown, the process by which edge control devices assist central control devices in managing edge cloud nodes includes:

[0160] 21b. Monitor at least one edge cloud node in the network system;

[0161] 22b. Report the monitoring data to the central control device in the network system so that the central control device can manage at least one edge cloud node based on the monitoring data.

[0162] Optionally, the edge management device can periodically monitor at least one edge cloud node from at least one monitoring dimension according to a scheduled task. Alternatively, the edge management device can monitor at least one edge cloud node in the network system under the control of the central management device. This application does not limit the control method of the central management device over the edge management device; two optional embodiments are described below.

[0163] In an optional embodiment, step 21b includes monitoring at least one edge cloud node from at least one monitoring dimension according to a first type of monitoring instruction sent by the central management device. Correspondingly, step 22b includes reporting monitoring data from at least one monitoring dimension to the central management device, so that the central management device can manage at least one edge cloud node based on the monitoring data from at least one monitoring dimension.

[0164] In another optional embodiment, step 21b includes monitoring at least one edge cloud node on a specified monitoring dimension according to the second type of monitoring instruction sent by the central management device. Correspondingly, step 22b includes reporting the monitoring data on the specified monitoring dimension to the central management device, so that the central management device can manage at least one edge cloud node based on the monitoring data on the specified monitoring dimension.

[0165] Alternatively, the edge control device can assist the central control device in managing the edge cloud nodes from at least one monitoring dimension, as illustrated below.

[0166] In Example 1, step 21b includes monitoring the status of objects in a running state at least one edge cloud node. Correspondingly, step 22b includes reporting the running status of the monitored objects to the central control device, so that the central control device can identify target objects with abnormal running status and handle the anomalies.

[0167] In Example 2, step 21b includes monitoring the lifecycle of objects in a running state on at least one edge cloud node. Correspondingly, step 22b includes reporting the monitored lifecycle of objects in a running state to the central management device, so that the central management device can control the objects in a running state to stop, restart, or delete.

[0168] In Example 3, step 21b includes collecting log data from at least one edge cloud node. Correspondingly, step 22b includes reporting the log data to the central control device, which then performs data analysis on the log data and executes subsequent actions based on the analysis results.

[0169] In Example 4, the implementation process of step 21b includes: monitoring traffic at at least one edge cloud node. Correspondingly, the implementation process of step 22b includes: reporting monitored traffic attack events to the central control device, so that the central control device can block the traffic attack events.

[0170] In Example 5, step 21b includes performing a network security vulnerability scan on at least one edge cloud node. Correspondingly, step 22b includes reporting the detected network security vulnerabilities to the central control device for remediation.

[0171] In Example 6, step 21b includes monitoring resource usage in at least one edge cloud node. Correspondingly, step 22b includes reporting the monitored resource usage information to the central control device, so that the central control device can expand or reduce the resource capacity of at least one edge cloud node.

[0172] In the above method embodiments, the central control device and the edge control device are combined. The edge control device can assist the central control device in managing at least one edge cloud node. In addition, the edge control device also has a certain degree of self-management capability. It can autonomously manage the edge cloud node when the central control device is unable or unable to manage it, thus achieving two-level management. This allows for more comprehensive and thorough management of the edge cloud node, providing the conditions for "processing cloud computing in edge cloud nodes closer to the terminal". In turn, the resources in the edge cloud node can be used to provide cloud computing services to users, which helps to reduce response latency, alleviate the pressure on the central cloud or traditional cloud computing platform, and reduce bandwidth costs.

[0173] It is worth noting that the "control" in the above method embodiments can be control at the operational level. For example, the central control device can perform operational control on at least one edge cloud node with the assistance of the edge control device. In the operational control scenario, the at least one monitoring dimension or designated monitoring dimension can be an operational dimension. The central control device can then perform operational control on at least one edge cloud node based on the monitoring data reported by the edge control device on at least one operational dimension or designated operational dimension. Furthermore, if the central control device does not perform operational control on the edge cloud node or is unable to perform operational control on the edge cloud node, the edge control device can autonomously perform operational control on at least one edge cloud node. For example, the edge control device can perform operational control on at least one edge cloud node based on the monitoring data on at least one operational dimension or designated operational dimension. For details regarding the operational control of at least one edge cloud node by the central control device or edge control device, please refer to the foregoing embodiments, which will not be repeated here.

[0174] It should be noted that some processes described in the above embodiments and accompanying drawings include multiple operations appearing in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear in this document, or they may be executed in parallel. The operation numbers, such as 21a, 22a, etc., are merely used to distinguish different operations and do not represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should also be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to different types.

[0175] Figure 3 This is a schematic diagram of a central control device provided for an exemplary embodiment of this application. (See diagram below.) Figure 3 As shown, the central control equipment includes: a memory 31, a processor 32, and a communication component 33.

[0176] Memory 31 is used to store computer programs and can be configured to store various other data to support operation on the central control device. Examples of this data include instructions, messages, images, videos, etc., for any application or method used to operate on the central control device.

[0177] The processor 32, coupled to the memory 31, is used to execute a computer program in the memory 31 for: receiving monitoring data reported by the edge management device for at least one edge cloud node in the network system via the communication component 33, and managing the at least one edge cloud node based on the monitoring data.

[0178] In an optional embodiment, the processor 32 is specifically configured to: send a first type of monitoring instruction to the edge management device via the communication component 33, instructing the edge management device to monitor at least one edge cloud node from at least one monitoring dimension and report the monitoring data from at least one monitoring dimension to the central management device; and manage the at least one edge cloud node based on the monitoring data from at least one monitoring dimension reported by the edge management device. The first type of monitoring instruction is a monitoring instruction that instructs the edge management device to monitor at least one edge cloud node from at least one monitoring dimension and report the monitoring data from at least one monitoring dimension. It is worth noting that the monitoring dimensions can be flexibly set according to application requirements and are pre-configured in the edge management device and the central management device.

[0179] Alternatively, the processor 32 is specifically used to: send a second type of monitoring instruction to the edge management device via the communication component 33. The second type of monitoring instruction corresponds to a specified monitoring dimension and is used to instruct the edge management device to monitor at least one edge cloud node in the specified monitoring dimension and report the monitoring data in the specified monitoring dimension; and manage at least one edge cloud node based on the monitoring data in the specified monitoring dimension.

[0180] It's worth noting that there can be one or more specified monitoring dimensions. When there are multiple specified monitoring dimensions, each specified monitoring dimension can correspond to one type II monitoring instruction.

[0181] The aforementioned monitoring dimension or specified monitoring dimension may include, but is not limited to, the following dimensions: object dimension in runtime, log dimension, security dimension, resource dimension, etc. Furthermore, the object dimension in runtime may include the object's runtime status dimension and / or the object's lifecycle dimension; the security dimension may include: traffic attack dimension and / or security vulnerability dimension.

[0182] In conjunction with the monitoring dimensions listed above, processor 32 is specifically used to perform, but is not limited to, at least one of the following operations:

[0183] The control edge management device monitors the status of objects in running state at least one edge cloud node; receives the running status of objects in running state reported by the edge management device; identifies objects with abnormal running status from the running status reported by the edge management device, and for ease of description and differentiation, refers to objects with abnormal running status as target objects, and performs anomaly handling on target objects; or

[0184] The control edge management device monitors the lifecycle of running objects in at least one edge cloud node; receives the lifecycle information of running objects reported by the edge management device; and controls the running objects to stop, restart, or delete based on the lifecycle information reported by the edge management device; or

[0185] Control the edge management device to collect log data from at least one edge cloud node; receive log data reported by the edge management device; perform data analysis on the log data, and execute subsequent actions based on the data analysis results, such as billing, risk control, and / or adding or removing instances; or

[0186] Control the edge management device to monitor traffic to at least one edge cloud node; receive traffic attack events reported by the edge management device; block traffic attack events occurring in the edge cloud node; or

[0187] Control the edge management device to perform network security vulnerability scanning on at least one edge cloud node; receive network security vulnerability issues reported by the edge management device; and remediate the network security vulnerability issues; or

[0188] Control the edge management device to monitor the resource usage of at least one edge cloud node; receive resource usage information reported by the edge management device; and expand or reduce the resource capacity of at least one edge cloud node based on the resource usage information reported by the edge management device.

[0189] Optionally, in this embodiment, "control" can be control at the operational level. Specifically, processor 32 can be used to: receive monitoring data reported by the edge control device for at least one edge cloud node in the network system, and perform operational control on the at least one edge cloud node based on the monitoring data. Further, processor 32 can also control the edge control device to monitor the at least one edge cloud node from at least one operational level or a specified operational level; and perform operational control on the at least one edge cloud node based on the monitoring data reported by the edge control device in at least one operational level or a specified operational level. For details regarding controlling the edge control device to monitor the at least one edge cloud node from at least one operational level or a specified operational level and to perform operational control on the at least one edge cloud node, please refer to the preceding description, which will not be repeated here.

[0190] Furthermore, such as Figure 3 As shown, the central control equipment also includes other components such as a display 34, a power supply unit 35, and an audio unit 36. Figure 3 The diagram only shows some components and does not mean that the central control equipment includes only these components. Figure 3 The components shown. Additionally... Figure 3 The components within the dashed box are optional and depend on the implementation form of the central control device. If the central control device is a server-type device, the display 34 and audio component 36 may be excluded; if the central control device is a terminal device, the display 34 and audio component 36 may be included.

[0191] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by one or more processors, causes the one or more processors to perform the steps or operations that can be executed by the central control device in the above method embodiments.

[0192] Figure 4 This is a schematic diagram of the structure of an edge control device provided for an exemplary embodiment of this application. Figure 4 As shown, the device includes a memory 41 and a processor 42.

[0193] Memory 41 is used to store computer programs and can be configured to store various other data to support operation on the edge control device. Examples of this data include instructions, messages, images, videos, etc., for any application or method used to operate on the edge control device.

[0194] The processor 42, coupled to the memory 41, is used to execute a computer program in the memory 41 for: determining that the central control device in the network system is not or unable to control at least one edge cloud node in the network system; and autonomously controlling at least one edge cloud node.

[0195] In an optional embodiment, when the processor 42 determines that the central control device is incorrect or unable to control the edge cloud nodes, it is specifically configured to perform at least one of the following operations:

[0196] If the edge control device loses connection with the central control device, it is determined that the central control device is unable to control at least one edge cloud node; or

[0197] If no Type I monitoring command is received from the central control device, it is determined that the central control device is incorrect or unable to control at least one edge cloud node; or

[0198] If no second-type monitoring instruction is received from the central control device in the specified monitoring dimension, it is determined that the central control device is not or cannot control at least one edge cloud node in the specified monitoring dimension.

[0199] Furthermore, the processor 42 is also used to: synchronize the control data lost during the period of disconnection to the central control device after the edge control device and the central control device reconnect.

[0200] In an alternative embodiment, when the processor 42 autonomously manages at least one edge cloud node, it specifically performs at least one of the following operations:

[0201] Monitor the status of objects in the running state in at least one edge cloud node, and handle exceptions for target objects whose running status is abnormal.

[0202] Monitor the lifecycle of objects in the running state in at least one edge cloud node, and control the objects in the running state to stop, restart or delete them after stopping based on the monitoring results;

[0203] Collect log data from at least one edge cloud node, perform data analysis on the log data, and execute subsequent actions based on the data analysis results;

[0204] Traffic monitoring is performed on at least one edge cloud node, and traffic attack events detected are blocked.

[0205] Perform network security vulnerability scanning on at least one edge cloud node and remediate the network security vulnerabilities detected.

[0206] Monitor the resource usage of at least one edge cloud node, and expand or reduce the resource capacity of at least one edge cloud node based on the monitoring results.

[0207] Further optionally, when the processor 42 performs exception handling for a target object whose operating state is abnormal, it is specifically used to: analyze the abnormal operating state of the target object, determine at least one candidate processing method based on the analysis results; obtain the target processing method from the at least one candidate processing method, and perform exception handling on the target object according to the target processing method.

[0208] Optionally, such as Figure 4 As shown, the edge control device in this embodiment further includes a communication component 43. When the processor 42 obtains a target processing method from at least one candidate processing method, it is specifically configured to: report at least one candidate processing method to the central control device while the edge control device and the central control device remain connected, so that the central control device can select a processing method from them; receive the processing method returned by the central control device as the target processing method through the communication component 43; or, when the edge control device and the central control device lose connection, output at least one candidate processing method to the edge control personnel, so that the personnel can select a processing method from them; in response to the selection operation of the edge control personnel, determine the selected processing method as the target processing method; or, when the edge control device and the central control device lose connection, select the target processing method from at least one candidate processing method according to a set selection strategy.

[0209] In an optional embodiment, the processor 42 is further configured to: monitor at least one edge cloud node in the network system and report the monitoring data to the central management device so that the central management device can manage at least one edge cloud node based on the monitoring data.

[0210] Optionally, the processor 42 is further configured to: monitor at least one edge cloud node under the control of the central management device. For example, the processor 42 is specifically configured to: monitor at least one edge cloud node from at least one monitoring dimension according to a first type of monitoring instruction sent by the central management device, and report the monitoring data of the at least one monitoring dimension to the central management device, so that the central management device can manage at least one edge cloud node based on the monitoring data of the at least one monitoring dimension; or, monitor at least one edge cloud node in a specified monitoring dimension according to a second type of monitoring instruction sent by the central management device, and report the monitoring data of the specified monitoring dimension to the central management device, so that the central management device can manage at least one edge cloud node based on the monitoring data of the specified monitoring dimension.

[0211] Optionally, the processor 42 is also configured to periodically monitor the at least one edge cloud node from at least one monitoring dimension according to a scheduled task, and report the monitoring data from at least one monitoring dimension to the central management device, so that the central management device can manage the at least one edge cloud node based on the monitoring data from at least one monitoring dimension.

[0212] Further optionally, when monitoring at least one edge cloud node and reporting the monitoring data to the central control device, the processor 42 specifically performs at least one of the following operations:

[0213] The status of objects in the running state in at least one edge cloud node is monitored, and the running status of the monitored objects in the running state is reported to the central management and control equipment so that the central management and control equipment can identify target objects with abnormal running status and handle the abnormality of the target objects.

[0214] Monitor the lifecycle of objects in the running state in at least one edge cloud node, and report the monitored lifecycle of objects in the running state to the central management and control equipment, so that the central management and control equipment can control the objects in the running state to stop, restart or delete them after stopping;

[0215] Collect log data from at least one edge cloud node and report the log data to the central control device so that the central control device can perform data analysis on the log data and execute subsequent actions based on the data analysis results;

[0216] Traffic monitoring is performed on at least one edge cloud node, and the monitored traffic attack events are reported to the central control equipment so that the central control equipment can block the traffic attack events.

[0217] Perform network security vulnerability scanning on at least one edge cloud node and report the detected network security vulnerabilities to the central control equipment so that the central control equipment can fix the network security vulnerabilities.

[0218] Monitor the resource usage in at least one edge cloud node and report the monitored resource usage information to the central management equipment so that the central management equipment can expand or reduce the resource capacity of at least one edge cloud node.

[0219] Optionally, if each edge cloud node is equipped with an edge management device, then the processor 42 is specifically used to: autonomously manage the edge cloud node to which its edge management device belongs.

[0220] Optionally, the "control" in this embodiment can be control at the operation and maintenance level. Specifically, the processor 42 can be used to: autonomously perform operation and maintenance control on at least one edge cloud node; or monitor at least one edge cloud node from at least one operation and maintenance level or a specified operation and maintenance level under the control of the central control device. For details regarding autonomously performing operation and maintenance control on at least one edge cloud node, or monitoring at least one edge cloud node from at least one operation and maintenance level or a specified operation and maintenance level under the control of the central control device, please refer to the preceding description, which will not be repeated here.

[0221] Furthermore, such as Figure 4 As shown, the edge control device also includes other components such as a display 44, a power supply component 45, and an audio component 46. Figure 4 The diagram only shows some components and does not mean that the edge control device only includes... Figure 4 The components shown. Additionally... Figure 4 The components within the dashed box are optional and depend on the implementation form of the edge control device. If the edge control device is a server-type device, the display 44 and audio component 46 may be omitted; if the edge control device is a terminal device, the display 44 and audio component 46 may be included.

[0222] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by one or more processors, causes the one or more processors to perform the steps or operations that can be executed by the edge control device in the above method embodiments.

[0223] The above Figure 3 and Figure 4 The memory in the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0224] The above Figure 3 and Figure 4 The communication component is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component may also include a Near Field Communication (NFC) module, Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, etc.

[0225] The above Figure 3 and Figure 4 The display includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions, but also the duration and pressure associated with the touch or swipe operation.

[0226] The above Figure 3 and Figure 4 The power supply component provides power to the various components of the device in which it resides. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which it resides.

[0227] The above Figure 3 and Figure 4 The audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0228] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0229] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0230] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0231] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0232] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, a network interface, and memory. Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

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

[0234] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0235] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A network system, characterized in that, include: The device includes a central control device, an edge control device, and at least one edge cloud node, wherein an instance is running in the at least one edge cloud node, and the instance is created based on an image file; The central control device is used to receive monitoring data reported by the edge control device for the at least one edge cloud node, and to control the at least one edge cloud node according to the monitoring data. The edge control device is used to monitor the at least one edge cloud node and report the monitoring data to the central control device; and to autonomously control the at least one edge cloud node when the central control device is not able to control or is unable to control the at least one edge cloud node, wherein the controlled object includes at least the instance.

2. The network system according to claim 1, characterized in that, The edge control device is specifically used for: In the event of a loss of connection with the central control device, it can autonomously manage at least one edge cloud node; After reconnecting with the central control device, the control data collected during the period of disconnection will be synchronized to the central control device.

3. The network system according to claim 2, characterized in that, When the edge management device autonomously manages the at least one edge cloud node, it specifically performs at least one of the following operations: The status of objects in the running state in the at least one edge cloud node is monitored, and abnormal handling is performed on target objects whose running state is abnormal. The objects in the running state include at least the instance. Monitor the lifecycle of objects in the running state in at least one edge cloud node, and control the objects in the running state to stop, restart after stopping, migrate, or delete based on the monitoring results; Collect log data from at least one edge cloud node, perform data analysis on the log data, and execute subsequent actions based on the data analysis results; Traffic monitoring is performed on at least one edge cloud node, and traffic attack events detected are blocked. Perform network security vulnerability scanning on the at least one edge cloud node and fix the network security vulnerabilities detected. Monitor the resource usage in at least one edge cloud node, and expand or reduce the resource capacity of the at least one edge cloud node based on the monitoring results.

4. The network system according to any one of claims 1-3, characterized in that, Each edge cloud node is equipped with an edge management device; or, there is one edge management device, and the at least one edge cloud node shares the same edge management device; or, the number of edge management devices is less than the number of edge cloud nodes, and at least some edge cloud nodes share the same edge management device.

5. A control method, characterized in that, include: It is determined that the central control device in the network system is incorrect or unable to control at least one edge cloud node in the network system, wherein an instance is running in the at least one edge cloud node, and the instance is created based on an image file; The system autonomously manages at least one edge cloud node, wherein the managed object includes at least the instance.

6. The method according to claim 5, characterized in that, Autonomously managing the at least one edge cloud node includes at least one of the following methods: The status of objects in the running state in the at least one edge cloud node is monitored, and abnormal handling is performed on target objects whose running state is abnormal. The objects in the running state include at least the instance. Monitor the lifecycle of objects in the running state in at least one edge cloud node, and control the objects in the running state to stop, restart after stopping, migrate, or delete based on the monitoring results; Collect log data from at least one edge cloud node, perform data analysis on the log data, and execute subsequent actions based on the data analysis results; Traffic monitoring is performed on at least one edge cloud node, and traffic attack events detected are blocked. Perform network security vulnerability scanning on the at least one edge cloud node and fix the network security vulnerabilities detected. Monitor the resource usage in at least one edge cloud node, and expand or reduce the resource capacity of the at least one edge cloud node based on the monitoring results.

7. The method according to claim 6, characterized in that, For target objects whose operational status is abnormal as detected by monitoring, perform exception handling, including: Analyze the abnormal operating state of the target object, and determine at least one candidate processing method based on the analysis results; Obtain a target processing method from the at least one candidate processing method, and perform anomaly processing on the target object according to the target processing method. The target processing method includes stopping the target object, restarting the target object, migrating the target object, and / or deleting and rebuilding the target object.

8. A control method, characterized in that, include: When the central control device in the network system manages at least one edge cloud node in the network system, the at least one edge cloud node is monitored, and an instance is running in the at least one edge cloud node, the instance being created based on an image file; The monitoring data is reported to the central control device so that the central control device can manage the at least one edge cloud node based on the monitoring data; In the event that the central control device is not capable of controlling or is unable to control the at least one edge cloud node, the device autonomously controls the at least one edge cloud node, wherein the controlled object includes at least the instance.

9. An edge control device, characterized in that, include: Memory and processor; The memory is used to store a computer program; when the computer program is executed by the processor, it causes the processor to perform the steps of the method according to any one of claims 5-8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by one or more processors, it causes the one or more processors to perform the steps of the method according to any one of claims 5-8.

Images