WO2020207265A1 - 网络系统、管控方法、设备及存储介质 - Google Patents

网络系统、管控方法、设备及存储介质 Download PDF

Info

Publication number
WO2020207265A1
WO2020207265A1 PCT/CN2020/081569 CN2020081569W WO2020207265A1 WO 2020207265 A1 WO2020207265 A1 WO 2020207265A1 CN 2020081569 W CN2020081569 W CN 2020081569W WO 2020207265 A1 WO2020207265 A1 WO 2020207265A1
Authority
WO
WIPO (PCT)
Prior art keywords
control device
cloud node
edge cloud
edge
management
Prior art date
Application number
PCT/CN2020/081569
Other languages
English (en)
French (fr)
Inventor
谢鹏
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2020207265A1 publication Critical patent/WO2020207265A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0695—Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/142—Network analysis or design using statistical or mathematical methods
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • This application relates to the field of Internet technology, in particular to a network system, management and control method, equipment and storage medium.
  • the concept of cloud computing is based on centralized resource management and control. Even if multiple data centers are used for interconnection, all software and hardware resources are still treated as unified resources for management, scheduling, and sales. With the advent of the era of 5G and the Internet of Things and the gradual increase of cloud computing applications, the terminal side has higher and higher requirements for cloud resources in terms of latency and bandwidth. The centralized cloud network can no longer meet the increasing demand on the terminal side. Cloud resource requirements.
  • Various aspects of the present application provide a network system, management and control method, equipment, and storage medium to reduce service response delay and bandwidth cost.
  • An embodiment of the present application provides a network system, including: a central management and control device, an edge management and control device, and at least one edge cloud node; the central management and control device is configured to receive information reported by the edge management and control device for the at least one edge cloud The monitoring data of the node, and the management and control of the at least one edge cloud node according to the monitoring data; the edge management and control device is used to monitor the at least one edge cloud node and report the monitoring data to the central management and control Device; and in the case where the central management and control device is not correct or unable to manage and control the at least one edge cloud node, autonomously manage and control the at least one edge cloud node.
  • An embodiment of the present application also provides a management and control method, including: determining that a central management and control device in a network system is incorrect or unable to manage and control at least one edge cloud node in the network system; and autonomously manage and control the at least one edge cloud node .
  • An embodiment of the present application also provides a management and control method, including: monitoring at least one edge cloud node in a network system; reporting monitoring data to a central management and control device in the network system for the central management and control device according to The monitoring data controls the at least one edge cloud node.
  • An embodiment of the present application also provides an edge management and 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 is caused to implement the application Steps in the method embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium storing a computer program.
  • the computer program is executed by one or more processors, the one or more processors are caused to implement the method in the method embodiment of the present application. A step of.
  • the ability of cloud computing is considered to be placed on the edge side closer to the terminal side. Therefore, a network system including edge cloud nodes is provided.
  • the central Control equipment and edge control equipment can fully and comprehensively control edge cloud nodes, which provides conditions for "putting cloud computing in edge cloud nodes closer to the terminal for processing", and can use the edge cloud nodes Resources provide users with cloud computing services, which is conducive to reducing response delays and reducing bandwidth costs.
  • Fig. 1a is a schematic structural diagram of a network system provided by an exemplary embodiment of this application.
  • FIG. 1b is a schematic structural diagram of a central management and control device and an edge management and control device provided by an exemplary embodiment of this application;
  • FIG. 1c is a schematic structural diagram of another network system provided by an exemplary embodiment of this application.
  • FIG. 2a is a schematic flowchart of a management and control method provided by an exemplary embodiment of this application;
  • FIG. 2b is a schematic flowchart of another management and control method provided by an exemplary embodiment of this application.
  • FIG. 3 is a schematic structural diagram of a central management and control device provided by an exemplary embodiment of this application.
  • FIG. 4 is a schematic structural diagram of an edge management and control device provided by an exemplary embodiment of this application.
  • a network system including at least one edge cloud node is provided.
  • a central control device and an edge control device are combined to fully and comprehensively control the edge cloud nodes, which solves the problem of edge cloud nodes.
  • This provides conditions for "putting cloud computing in the edge cloud node closer to the terminal for processing", and then can use the resources in the edge cloud node to provide users with cloud computing services, which is beneficial to reducing response delays. Reduce bandwidth costs.
  • Fig. 1a is a schematic structural diagram of a network system provided by an exemplary embodiment of this application.
  • the network system 100 includes: a central management and control device 101, an edge management and control device 103, and at least one edge cloud node 102.
  • 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, and is a cloud platform with computing, network, storage, and security capabilities at the edge.
  • Edge cloud is a relative concept.
  • Edge cloud refers to a cloud computing platform that is relatively close to the terminal. In other words, it is different from central cloud or traditional cloud computing platform.
  • Central cloud or traditional cloud computing platform can include large-scale resources and centralized locations. Data centers, and edge cloud nodes cover a wider network range, and therefore have the characteristics of being closer to the terminal.
  • the resource scale of a single edge cloud node is small, but the number of edge cloud nodes is large, and multiple edge cloud nodes constitute the original Part of the edge cloud in the embodiment.
  • the terminal in this embodiment refers to the demand side of cloud computing services, for example, it may be a terminal or a user side in the Internet, or a terminal or a user side in the Internet of Things.
  • the edge cloud network is a network based on the infrastructure between the central cloud or the 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.
  • edge infrastructures include, but are not limited to: distributed data centers (DC), wireless computer rooms or clusters, operations Communication networks, core network equipment, base stations, edge gateways, home gateways, computing devices and/or storage devices and other edge devices and corresponding network environments. It is explained here that the locations, capabilities, and included infrastructure of different edge cloud nodes 102 may be the same or different.
  • the network system 100 of this embodiment is combined with a central cloud or a traditional cloud computing platform and other central networks and terminals to form a "cloud edge-end three-body coordination" network architecture.
  • the network can be forwarded and stored.
  • Tasks such as computing and/or intelligent data analysis are processed in each edge cloud node 102 in the network system 100. Since each edge cloud node 102 is closer to the terminal, the response delay can be reduced and the central cloud or traditional cloud The pressure on the computing platform reduces bandwidth costs.
  • a central management and control device 101 is deployed.
  • the central management and control device 101 can take the edge cloud node 102 as the management and control object, in resource scheduling, image management, instance management and control, operation and maintenance, network, security, etc.
  • At least one edge cloud node 102 in the network system 100 is managed and controlled, so that cloud computing services are placed in each edge cloud node 102 for processing.
  • the central management and control device 101 can be deployed in one or more cloud computing data centers, or it can be deployed in one or more traditional data centers, and the central management and control device 101 can also be connected to at least one edge cloud managed by it.
  • the nodes jointly constitute an edge cloud network, which is not limited in this embodiment.
  • the edge cloud node 102 For an edge cloud node 102, various resources may be provided externally, such as computing resources such as CPU and GPU, storage resources such as memory and hard disk, and network resources such as bandwidth.
  • the edge cloud node 102 can also create a corresponding instance based on the image, and provide various services externally through the instance.
  • the image is the basic file required by the instance created in the edge cloud node. For example, it can be the image file of the operating system, application, or operation configuration required to provide the cloud computing service to the user. It can be in line with the edge cloud node computing Deployment requirements, a specific series of files are produced in a certain format.
  • images which can be virtual machine (VM) image files, container (Docker) image files, various types of application packaging files, etc.
  • VM virtual machine
  • Docker container
  • application packaging files etc.
  • the image form can be compatible with the virtualization technology required by cloud computing services. Regarding, this embodiment does not limit this.
  • the implementation form of the instance can be a virtual machine, container, or application.
  • the central management and control device 101 can perform resource scheduling on at least one edge cloud node 102 based on resource requirements alone, or can perform image management and distribution for at least one edge cloud node 102 based on mirroring requirements alone.
  • resource scheduling is performed on at least one edge cloud node 102 and mirroring is provided for at least one edge cloud node 102.
  • service requirements include resource requirements and mirroring requirements.
  • the central management and control device 101 may provide a requirement submission portal to the outside, and the requirement submission portal may be a web page, an application page, or a command window. The role of the requirement submission portal is for the requirement to submit its own requirement description information to the central control device 101.
  • the resource demand description information can be submitted to the central management and control device 101 through the above demand submission entry.
  • the resource demand description information includes: edge cloud node selection parameters and resource selection parameters; edge cloud node selection parameters include scheduling domains and/or For the performance requirements of edge cloud nodes, the resource selection parameters include resource type, resource quantity, and performance requirements for resource equipment.
  • the central management and control device 101 may perform resource scheduling on at least one edge cloud node according to the resource requirement description information.
  • a resource scheduling method includes: the central management and control device 101 determines the scheduled target edge cloud node and the scheduled target edge cloud node from at least one edge cloud node 102 of the network system 100 according to resource demand description information Resource information; according to the resource information, the corresponding resource device in the target edge cloud node is controlled to allocate or reserve resources.
  • the mirroring demand description information can be submitted to the central management and control device 101 through the above demand submission entry.
  • the mirroring demand description information can point to the mirror that needs to be used, which can be the mirror itself, or the name, ID and other identification types of the mirror.
  • Information can also be some information describing the functions of cloud computing services, and this information can reflect the required image.
  • the central management and control device 101 can determine the target image that needs to be provided to the first edge cloud node according to the image requirement description information; and provide the target image for the first edge cloud node, so that the first edge cloud node can create a corresponding instance based on the image.
  • the first edge cloud node may be any edge cloud node in the network system 100. In order to facilitate description and distinction, the image that needs to be provided to the first edge cloud node is called the target image.
  • the service demand description information can be submitted to the central management and control device 101 through the above demand submission portal.
  • the service demand description information includes resource demand description information and mirroring demand description information.
  • resource requirement description information and mirroring requirement description information please refer to the previous description, which will not be repeated here. It is worth noting that the resource requirement description information and the mirroring requirement description information in the service requirement description information can be submitted together or separately.
  • the central management and control device 101 can perform resource scheduling on at least one edge cloud node 102 in the network system 100 according to the service demand description information; provide a mirror image of the scheduled resources in the at least one edge cloud node 102 to use the The scheduled resources provide cloud computing services.
  • the central management and control device 101 can directly control and schedule at least one edge cloud node 102, but it is not limited to this.
  • an edge management and control device 103 is also included in the network system 100.
  • the number of edge management and control devices 103 may be one or multiple.
  • the edge management and control device 103 may be deployed in one or more edge cloud nodes 102.
  • an edge management and control device 103 is separately deployed in each edge cloud node 102.
  • each edge cloud node includes one or more resource devices.
  • the edge management and control device 103 may be deployed on one resource device in a centralized manner, or may be deployed on multiple resource devices in a distributed manner.
  • each edge cloud node can also include one or more proprietary devices.
  • the edge management and control device 103 can also be centrally deployed on a dedicated device or distributed on one dedicated device.
  • the proprietary device refers to the physical device used to deploy the edge management and control device 103, which is different from the resource device.
  • the edge management and control device 103 can also be deployed with the central management and control device 101, which is not limited here.
  • the central management and control device 101 can be deployed in one or more cloud computing data centers or traditional data centers, and can also be deployed in an edge cloud network together with at least one edge cloud node.
  • the edge management and control device 103 can assist and cooperate with the central management and control device 101 to manage and control at least one edge cloud node 102. With the assistance of the edge management and control device 103, the central management and control device 101 can manage and schedule at least one edge cloud node 102 more conveniently and efficiently, thereby achieving the purpose of making full use of edge resources.
  • the central management and control device 101 of this embodiment can be a logical device capable of resource scheduling, image management, operation and maintenance management, etc. These functions can be implemented on a physical machine or virtual machine, or can be distributed Deployed on multiple physical or virtual machines.
  • the central management and control device in this embodiment may also be one or more physical devices with capabilities such as resource scheduling and image management.
  • the embodiment of the present application does not limit the implementation structure of the central management and control device 101, and any device structure with the foregoing capabilities is applicable to the embodiment of the present application.
  • the edge management and control device 103 can also be a logical device, which has the ability to deploy a physical machine (for example, a resource device or a proprietary device in an edge cloud node) or a virtual machine. It can also be deployed on multiple physical machines (such as resource devices or proprietary devices in edge cloud nodes) or virtual machines in a decentralized manner.
  • the edge control device can also be one or more physical devices with corresponding capabilities.
  • the embodiments of the present application do not limit the implementation structure of the edge management and control device 103, and any device structure with corresponding capabilities is applicable to the embodiments of the present application.
  • a secure and encrypted communication channel is established between the central management and control device 101 and the edge management and control device 103, and interaction is performed based on the communication channel.
  • the communication channel includes a control interface and a data interface, and the central management and control device 101 interacts with the edge management and control device 103 on the control plane and the data plane based on the control interface and the 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 and control device 101 and the edge management and control device 103.
  • the control interface has but not limited to the following functions:
  • the central control device 101 can perform resource scheduling on edge cloud nodes from multiple dimensions through a control interface with resource scheduling capabilities (can be referred to as resource scheduling interface for short).
  • the edge cloud node is the central control device 101 for resource scheduling Object;
  • the central management and control device 101 can provide images to edge cloud nodes through a control interface with image management and distribution capabilities (referred to as image management interfaces), so that the edge cloud nodes can create images based on the received images Corresponding instances, providing cloud computing services through instances;
  • Operation and maintenance management capability 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).
  • the operation and maintenance management includes but is not limited to: control edge cloud nodes Application, virtualization software, etc., monitor the status, resource usage and infrastructure of the instance.
  • the central management and control device 101 of this embodiment has but not limited to the following functions:
  • service requirements such as service specifications, areas where services need to be deployed, operator network distribution, network delays, load conditions, bandwidth costs, required resource types and/or resource equipment performance requirements, etc.
  • Resource scheduling for edge cloud nodes such as service specifications, areas where services need to be deployed, operator network distribution, network delays, load conditions, bandwidth costs, required resource types and/or resource equipment performance requirements, etc.
  • the image required for cloud computing services can be obtained, and the image can be provided to the corresponding resource equipment in the edge cloud node for configuration and installation, so that the corresponding resource equipment can create corresponding instances to provide cloud computing services;
  • Manage and control edge cloud nodes including but not limited to: control the status of applications, virtualized components, instances, resource usage and/or infrastructure conditions in edge cloud nodes, and realize remote operation and maintenance, log management, etc. .
  • the central control equipment can also have other functions, such as security assurance functions, involving 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.
  • Security of cloud nodes responsible for maintaining networking information in the network system.
  • At least one edge cloud node 102 can form a resource pool, and each edge cloud node 102 serves as a scheduling object, and provides various resources or cloud computing services externally under the scheduling of the central management and control device 101.
  • the central management and control device 101 and the edge management and control device 102 cooperate with each other to perform resource scheduling on at least one edge cloud node 102 separately, or perform mirror management and distribution for at least one edge cloud node 102 separately, of course, it can also At least one edge cloud node 102 performs resource scheduling and provides a mirror image for at least one edge cloud node 102.
  • the management and control of the edge cloud node 102 in other aspects is also a problem that the network system 100 needs to solve. Successfully solving this problem is also "putting cloud computing at a distance. The basis of processing in the edge cloud node closer to the terminal.
  • the central management and control device 101 and the edge management and control device 102 cooperate with each other, and can also manage and control at least one edge cloud node 102 in other aspects.
  • the central management and control device can manage and control at least one edge cloud node with the assistance of the edge management and control device.
  • the edge management and control device can monitor at least one edge cloud node and report the monitoring data to the central management and control device for the central management and control device to manage and control at least one edge cloud node according to the monitoring data.
  • the central management and control device can control at least one edge cloud node based on the monitoring data reported by the edge management and control device.
  • at least one edge cloud node can be monitored and the monitoring data can be reported to the central management and control device.
  • the edge management and control device may periodically monitor at least one edge cloud node according to a timing task and report the monitoring data to the central management and control device.
  • the edge management and control equipment mainly performs functions such as monitoring, data collection, and reporting, and the management and control decisions are determined by the central management and control equipment.
  • the central management and control device controls the edge management and control device to monitor at least one edge cloud node, and the following optional implementation manners can be adopted but not limited to:
  • the central management and control device may send the first type of monitoring instruction to the edge management and control device to instruct the edge management and control device to monitor at least one edge cloud node from at least one monitoring dimension and to monitor at least one monitoring dimension.
  • the data is reported to the central control equipment.
  • the first type of monitoring instruction is a monitoring instruction that instructs the edge management and control device to monitor at least one edge cloud node from at least one monitoring dimension and report monitoring data in at least one monitoring dimension.
  • it can receive the first type of monitoring instructions sent by the central management and control equipment, and according to the first type of monitoring instructions, monitor at least one edge cloud node from at least one monitoring dimension, and monitor The monitoring data is reported to the central control equipment.
  • the central management and control device controls at least one edge cloud node according to the monitoring data in at least one monitoring dimension reported by the edge management and control device. It is worth noting that at least one monitoring dimension can be flexibly set according to application requirements and preset into edge control equipment and central control equipment. For examples of monitoring dimensions, refer to the subsequent embodiments.
  • the central management and control device may selectively manage and control at least one edge cloud node in a certain or certain monitoring dimensions. Based on this, the central management and control device can send the second type of monitoring instruction to the edge management and control device.
  • the second type of monitoring instruction corresponds to the specified monitoring dimension and is used to instruct the edge management and control device to monitor and report at least one edge cloud node in the specified monitoring dimension. Specify the monitoring data on the monitoring dimension.
  • For edge management and control equipment it can receive the second type of monitoring instructions sent by the central management and control equipment, monitor at least one edge cloud node in the specified monitoring dimension according to the second type of monitoring instructions, and report the monitoring data on the specified monitoring dimension Provide the central control equipment for the central control equipment to control at least one edge cloud node according to the monitoring data on the specified monitoring dimension.
  • the central management and control device is also used to receive the monitoring data on the specified monitoring dimension sent by the edge management and control device, and manage and control at least one edge cloud node according to the monitoring data on the specified monitoring dimension.
  • each designated monitoring dimension can correspond to a second-type monitoring instruction, that is, the central control device can send multiple second-type monitoring instructions to the edge control device, and each second-type monitoring instruction Correspond to a designated monitoring dimension.
  • multiple designated monitoring dimensions can also correspond to the same second-type monitoring instruction, that is, the central management and control device can send a second-type monitoring instruction to the edge management and control device.
  • Class monitoring instructions correspond to multiple specified monitoring dimensions.
  • the edge management and control device periodically monitors at least one edge cloud node according to a timing task may be based on a timing task to periodically monitor at least one edge cloud node from at least one monitoring dimension; further, it may The monitoring data on a monitoring dimension is reported to the central control equipment. Among them, the monitoring period on different monitoring dimensions may be the same or different.
  • the edge management and control device can scan the edge cloud node for security vulnerabilities every 10 minutes, or monitor the traffic of the edge cloud node every 5 minutes.
  • the aforementioned at least one monitoring dimension or designated monitoring dimension may include, but is not limited to, the following dimensions: the object dimension in the running state, the log dimension, the security dimension, the resource dimension, etc.
  • the object dimension in the running state may include the operating state dimension of the object and/or the life cycle dimension of the object;
  • the security dimension may include: the traffic attack dimension and/or the security vulnerability dimension.
  • the central management and control device with the assistance of the edge management and control device, manages and controls at least one edge cloud node, including but not limited to at least one of the following management and control examples:
  • Control example 1 The central control device controls the edge control device to monitor the status of objects in at least one edge cloud node in the running state.
  • the control method includes sending a first-type monitoring instruction to the edge management and control device or sending a second-type monitoring instruction corresponding to the operating state dimension of the object.
  • the edge management and control equipment is under the control of the central management and control equipment, or periodically according to timing tasks, monitors the status of the objects in the running state of at least one edge cloud node, and reports the running status of the monitored objects in the running state to Central control equipment.
  • the central management and control equipment identifies objects with abnormal operating status from the operating status of the objects in the operating status reported by the edge management and control equipment.
  • the objects with abnormal operating status are called target objects, and exception handling is performed on the target objects.
  • the objects in the running state in the edge cloud node include, but are not limited to: instances, images, containers, other virtual components, physical machines, CPUs, and/or hard disks.
  • the abnormal situation of the running state will be different.
  • possible abnormal conditions include, but are not limited to: interruption, error reporting, and/or failure.
  • possible abnormal conditions include, but are not limited to: crashes, black screens, alarms, and/or crashes of applications running on the physical machine.
  • the exception handling method will be different, for example, it can include but not limited to: alarm, stop or restart the target object, migrate, and/or delete and rebuild the target object, etc.
  • Control example 2 The central control device controls the edge control device to monitor the life cycle of at least one edge cloud node in the running state.
  • the control method includes sending the first type of monitoring instruction to the edge management and control device or sending the second type of monitoring instruction corresponding to the life cycle dimension of the object.
  • the edge control device is under the control of the central control device, or periodically according to a scheduled task, monitors the life cycle of at least one edge cloud node in the running state, and reports the life cycle of the monitored object in the running state Give the center control equipment.
  • the central control device controls the stopping, restarting, migration or deletion of the running object according to the life cycle of the running object reported by the edge control device.
  • Control example 3 The central control device controls the edge control device to collect log data in at least one edge cloud node.
  • the control method includes sending the first type of monitoring instruction to the edge management and control device or sending the second type of monitoring instruction corresponding to the log dimension.
  • the edge management and control device collects log data in at least one edge cloud node under the control of the central management and control device or periodically according to a timed task, and reports the collected log data to the central management and control device.
  • the central management and control device receives the log data reported by the edge management and control device, performs data analysis on the log data, and performs follow-up actions based on the data analysis results, such as billing, risk control, and/or adding or subtracting instances. Depending on the log data, follow-up actions will vary.
  • log data may include, but is not limited to: various performance, indicators and other data in edge cloud nodes, such as: instance bandwidth traffic, instance current running status, instance IO load, physical machine bandwidth traffic, physical machine The current operating status, the IO load of the physical machine, the operating status of the edge management and control equipment, and/or the operating status of other virtualization components, etc.
  • the central control device can not only collect the log data of each edge cloud node reported by the edge control device, but also has the ability to perform data inspection. For some data, if the data stored by the central control device is inconsistent with the data in the edge cloud node, The latest data can be actively synchronized with the edge cloud node, for example, the latest version of the image can be synchronized with the edge cloud node.
  • 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 the first type of monitoring instruction to the edge management and control device or sending the second type of monitoring instruction corresponding to the traffic attack dimension.
  • the edge management and control equipment is under the control of the central management and control equipment, or periodically according to a timing task, monitors the flow of at least one edge cloud node, and reports the monitored traffic attack events to the central management and control equipment.
  • the central management and control equipment blocks traffic attack events that occur in edge cloud nodes.
  • the edge management and control device may also report the monitored flow data to the central management and control device, and the central management and control device may also perform flow attack defense on at least one edge cloud node based on the flow data.
  • Control example 5 The central control device controls the edge control device to scan for network security vulnerabilities on at least one edge cloud node.
  • the control method includes sending the first type of monitoring instruction to the edge management and control device or sending the second type of monitoring instruction corresponding to the network security dimension.
  • the edge management and control equipment is under the control of the central management and control equipment, or periodically according to timing tasks, scans for network security vulnerabilities on at least one edge cloud node, and reports the scanned network security vulnerabilities to the central management and control equipment.
  • the central control equipment receives the network security vulnerabilities reported by the edge control equipment and fixes the network security vulnerabilities.
  • Control example 6 The central control device controls the edge control device to monitor the resource usage in at least one edge cloud node.
  • the control method includes sending the first type of monitoring instruction to the edge management and control device or sending the second type of monitoring instruction corresponding to the resource dimension.
  • the edge management and control device is under the control of the central management and control device, or periodically according to a timed task, monitors the resource usage in at least one edge cloud node, and reports the monitored resource usage information to the central management and control device.
  • the central management and control device performs resource expansion or reduction on at least one edge cloud node based on the resource usage information reported by the edge management and control device.
  • the resources here include various resource information, such as equipment resources such as physical machines, storage resources, computing resources such as CPUs and GPUs, and network resources such as bandwidth.
  • each edge management and control device can be under the control of the central management and control device, or periodically according to a timing task, to monitor and control the edge cloud node to which it belongs.
  • the monitoring data in the edge cloud node to which it belongs is reported to the central control equipment.
  • the central management and control device can receive the monitoring data reported by the edge management and control device in each edge cloud node, and manage and control each edge cloud node according to the monitoring data in each edge cloud node.
  • the embodiments of the present application do not limit the implementation structure of the central management and control device and the edge management and control device.
  • the structural framework of a central control equipment is shown in Figure 1b, including: a resource scheduling control module, a mirroring control module, and a central control module; the central control module further includes: a central monitoring unit, a central log unit, and a central security Unit etc.
  • the structural framework of an edge management and control device is shown in Figure 1b, including: a resource scheduling service module, a mirroring service module, and an edge management and control module; the edge management and control module further includes: an edge monitoring unit, an edge log unit, and an edge security unit Wait.
  • the resource scheduling management and control module in the central management and control device cooperates with the resource scheduling service module in the edge management and control device to perform resource scheduling on edge cloud nodes.
  • the resource scheduling function please refer to the description below.
  • the image management and control module in the central management and control device cooperates with the image service module in the edge management and control device to perform image management and distribution for edge cloud nodes.
  • image management and distribution functions please refer to the description below.
  • the central control module in the central control equipment and the edge control module in the edge control equipment cooperate with each other to manage and control edge cloud nodes.
  • the above management and control examples 1-6 can be implemented by the corresponding units in the central management and control module and the edge management and control module shown in Fig. 1b.
  • Control example 3 can be realized by the cooperation of the central log unit in the central control module and the edge log unit in the edge control module.
  • the central log unit sends the first type of monitoring instruction or the second type of monitoring instruction corresponding to the log dimension to the edge log unit; the edge log unit collects log data in the edge cloud node according to the first type or the second type of monitoring instruction And report to the central log unit; the central log unit performs data analysis on the log data and executes follow-up actions based on the data analysis results.
  • Control examples 4 and 5 can be realized by the central security unit in the central control module and the edge security unit in the edge control module.
  • the central security unit sends the first type of monitoring instruction to the edge security unit or sends the second type of operation and maintenance instruction corresponding to the traffic attack or the network security dimension; the edge security unit can respond to the first or second type of operation and maintenance instruction
  • Edge cloud nodes perform traffic monitoring or network security vulnerability scanning, and report 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 vulnerabilities.
  • the 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 repeated.
  • the central management and control equipment can understand the health, resource usage, log data and/or infrastructure conditions of each instance in the edge cloud node, and can realize remote operation and maintenance, log management, etc.
  • the edge management and control device in addition to the central management and control device that can manage and control at least one edge cloud node, the edge management and control device can autonomously control the edge cloud node when the central management and control device does not manage or control the edge cloud node. Manage and control at least one edge cloud node locally.
  • the edge management and control device can monitor the connection between it and the central management and control device. When the connection with the central management and control device is lost, it can be determined that the central management and control device cannot manage and control the edge cloud node, and it can autonomously monitor from at least one Dimension controls at least one edge cloud node.
  • the edge management and control device can wait to receive the first type sent by the central management and control device. Monitoring instructions. If the first type of monitoring instruction sent by the central control device is not received, it can be determined that the central control device is incorrect or unable to control at least one edge cloud node, and at least one edge cloud node can be autonomously controlled from at least one monitoring dimension Take control.
  • the edge management and control device and the central management and control device may pre-appoint the waiting time of the first type of monitoring instruction. If the waiting time is exceeded and the first type of monitoring instruction sent by the central management and control device is not received, it is determined that the first type of monitoring instruction is not received The first type of monitoring instructions sent by the central control equipment.
  • the edge management and control device may Waiting to receive the second type of monitoring instruction sent by the central control device. If the second type of monitoring instruction sent by the central control device is not received in the specified monitoring dimension, it can be determined that the central control device is not correct in the specified monitoring dimension or cannot detect at least one edge Cloud nodes are managed and controlled, and at least one edge cloud node can be managed and controlled autonomously from a specified monitoring dimension.
  • the edge management and control device autonomously manages at least one edge cloud node from at least one monitoring dimension when it loses the connection with the central management and control device, it can also lose the connection after the connection with the central management and control device is restored.
  • the control data during the connection period is synchronized to the central control equipment. It is worth noting that the control data mainly includes data such as control strategies, methods, and effects. Of course, it can also include monitoring data.
  • the above-mentioned at least one monitoring dimension or designated monitoring dimension may include but not limited to the following dimensions: the object dimension in the running state, the log dimension, the security dimension, the resource dimension, etc.
  • the object dimension in the running state may include the operating state dimension of the object and/or the life cycle dimension of the object;
  • the security dimension may include: the traffic attack dimension and/or the security vulnerability dimension.
  • the edge management and control device autonomously controls at least one edge cloud node, including but not limited to at least one of the following management and control examples:
  • Management and control example a autonomously monitor the status of objects in at least one edge cloud node in the running state, and perform exception handling for the monitored target objects whose running status is abnormal.
  • the objects in the running state and the abnormal conditions of the running state please refer to the above description, which will not be repeated here.
  • the edge management and control device when the edge management and control device performs abnormal processing on the target object, it is specifically used to: analyze the abnormal operating state of the target object, and determine at least one candidate processing method according to the analysis result; In the candidate processing method, the target processing method is acquired, and the target object is abnormally processed according to the target processing method.
  • the edge management and control device when the edge management and control device obtains the target processing mode, it is specifically used to: when the edge management and control device maintains a connection with the central management and control device, report at least one candidate processing method to the central management and control device for the central management and control device to use. Select the processing method; receive the processing method returned by the central control device as the target processing method; or, in the case that the edge control device loses the connection with the central control device, output at least one candidate processing method to the edge control personnel for the control personnel from it Select the processing method; in response to the selection operation of the edge management and control personnel, determine the selected processing method as the target processing method; or, in the case of loss of connection with the central control device, follow the set selection strategy to process at least one candidate Select the target processing method in the method.
  • Control example b Autonomously monitor the life cycle of the object in the running state in at least one edge cloud node, and control the object in the running state to stop, restart or delete after stopping according to the monitoring result. For containers or instances, you can control the container or instance to stop execution, restart after stopping, or delete the container or instance, etc.
  • Control example c autonomously collect log data in at least one edge cloud node, perform data analysis on the log data, and perform follow-up actions based on the data analysis results.
  • Log data includes, but is not limited to, the bandwidth traffic of the instance in the edge cloud node, the current running status of the instance, the IO load of the instance, the bandwidth traffic of the physical machine, the current running status of the physical machine, the IO load of the physical machine, and the operation of edge control equipment. Status and/or operation status of other virtualization components.
  • subsequent actions such as billing, risk control, and/or resource reallocation can be performed according to the analysis result of the log data, but it is not limited to this.
  • Control example d Autonomously monitor the traffic of at least one edge cloud node, and block the monitored traffic attack events.
  • Control example e Autonomously scan at least one edge cloud node for network security vulnerabilities, and fix the scanned network security vulnerabilities.
  • Control example f autonomously monitor the resource usage in at least one edge cloud node, and perform resource expansion or reduction on at least one edge cloud node according to the monitoring result.
  • the resources here include but are not limited to: equipment resources such as physical machines, storage resources such as memory and disks, computing resources such as CPU and GPU, and network resources such as bandwidth. For these resources, when the usage is high, the capacity can be expanded for these resources, and when the usage is low, the capacity can be reduced for these resources.
  • each edge management and control device can autonomously belong to the edge cloud node under the condition that the central management and control equipment is incorrect or cannot manage and control the edge cloud node to which it belongs Take control.
  • the edge management and control device may periodically manage and control at least one edge cloud node according to a timing task.
  • the edge management and control device can monitor the traffic of at least one edge cloud node every 10 minutes according to the scheduled task, and block the monitored traffic attack event.
  • the edge management and control device may scan for network security vulnerabilities on at least one edge cloud node every 5 minutes according to a scheduled task, and fix the scanned network security vulnerabilities.
  • the edge management and control device can also autonomously manage and control at least one edge cloud node according to other autonomous strategies. For example, it can autonomously manage and control at least one edge cloud node at a fixed time every day.
  • the above-mentioned management and control may be the management and control of the operation and maintenance dimension.
  • the central management and control device can perform operation and maintenance management and control on at least one edge cloud node with the assistance of the edge management and control device.
  • the aforementioned at least one monitoring dimension or the designated monitoring dimension can be the operation and maintenance dimension
  • the central management and control device can report at least one operation and maintenance dimension or the monitoring data on the designated operation and maintenance dimension reported by the edge management and control device.
  • An edge cloud node performs operation and maintenance control.
  • the edge management and control device can autonomously perform the operation and maintenance control on at least one edge cloud node.
  • the edge management and control device may perform O&M management and control on at least one edge cloud node according to the monitored at least one O&M dimension or monitoring data on a specified O&M dimension.
  • the central management and control device is combined with the edge management and control device, and the central management and control device can control at least one edge cloud with the assistance of the edge management and control device.
  • Nodes perform operation and maintenance management and control.
  • the edge management and control equipment also has a certain ability of self-operation and management. It can autonomously control the edge cloud when the central management and control equipment is not correct or the edge cloud node cannot be operated and maintained.
  • Nodes carry out operation and maintenance management and control, and realize two-level operation and maintenance management and control, which can more fully and comprehensively carry out operation and maintenance management and control of edge cloud nodes, and provide conditions for "putting cloud computing in edge cloud nodes closer to the terminal for processing".
  • the resources in the edge cloud nodes can be used to provide users with cloud computing services, which is beneficial to reduce response delays, reduce the pressure on the central cloud or traditional cloud computing platforms, and reduce bandwidth costs.
  • the central management and control device can perform resource scheduling on at least one edge cloud, which mainly refers to determining the target edge cloud node and target edge cloud node that can be scheduled from at least one edge cloud node 102 in the network system 100 according to service demand description information Scheduled resource information; the resource information is sent to the edge management and control device 103 for the edge management and control device 103 to control the corresponding resource device in the target edge cloud node for resource allocation or reservation.
  • the number of target edge cloud nodes can be specified by the user, or can be independently determined by the resource center management and control device according to the service requirement description information, and it can be one or more.
  • the service demand description information can be directly submitted by the service demander, or it can be extracted or calculated from the service-related information submitted by the service demander.
  • the service demander can be a user, an application, a physical machine, or another service that requires a certain service.
  • the resource scheduling function described here mainly includes the selection of edge cloud nodes and the resource scheduling within the edge cloud nodes, but it is not limited to these two aspects.
  • the internal resource scheduling of the edge cloud node is specifically embodied as the operation of determining the scheduled resource information in the target edge cloud node and providing resource information.
  • the main purpose is to allocate cloud computing services to the final at the granularity of each edge cloud node.
  • Basic resources such as server and other resource equipment.
  • the central control equipment can maintain the information of the resources contained in each edge cloud node as the basis for resource scheduling.
  • the service requirement description information includes edge cloud node selection parameters and resource selection parameters.
  • the edge cloud node selection parameter refers to the parameter required to select the target edge cloud node;
  • the resource selection parameter refers to the information required to select the scheduled resource in the edge cloud node.
  • the central management and control equipment can parse out the edge cloud node selection parameters and resource selection parameters from the service demand description information; determine the scheduled target edge cloud node from at least one edge cloud node according to the edge cloud node selection parameters, and according to the resource The selection parameters determine the scheduled resource information in the target edge cloud node.
  • the service requirement description information may include the scheduling domain and/or the QoS requirements of the cloud computing service, and these parameters may be used as edge cloud node selection parameters.
  • the scheduling domain points to the area where cloud computing services need to be deployed, which determines the geographic location of edge cloud nodes that should be scheduled.
  • the QoS requirements of cloud computing services may include the requirements of cloud computing services on network latency, load conditions, and/or bandwidth costs.
  • the central management and control device can select the edge cloud node that can meet the scheduling domain and/or QoS requirements as the target according to the QoS requirements of the scheduling domain and/or cloud computing service, combined with the geographic location and resource remaining amount of at least one edge cloud node Edge cloud node.
  • the central management and control device may select the edge cloud node pointed to by the scheduling domain as the target edge cloud node in combination with the geographic location of at least one edge cloud node according to the scheduling domain.
  • the central management and control device can also select the edge cloud node that meets the network delay, load and/or bandwidth cost requirements based on the QoS requirements of the cloud computing service, such as network delay, load conditions, and/or bandwidth cost requirements.
  • the edge cloud node serves as the target edge cloud node.
  • the central management and control equipment can also select the edge cloud node that can meet the scheduling domain and QoS requirements as the target edge cloud based on the QoS requirements of the scheduling domain and cloud computing services at the same time, combined with the geographic location and remaining amount of resources of at least one edge cloud node. node.
  • the service requirement description information can also include the resource type, the number of resources, and/or the performance of the resource equipment required by the cloud computing service. These parameters can be As a resource selection parameter. Based on this, after determining the target edge cloud node, the central management and control device can determine the scheduled resource information in the target edge cloud node according to the resource selection parameters.
  • the resource information here may include: resource type, resource quantity, and/or performance requirements for resource devices, so that the edge management and control device can control the corresponding resource device in the target edge cloud node to allocate or reserve resources accordingly.
  • 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 resource types such as bandwidth resources.
  • computing resources such as CPU and GPU
  • storage resources such as memory and hard disk
  • resource types such as bandwidth resources.
  • the number of resources can be 12 CPUs, 24 CPUs, etc.
  • memory resources such as an example
  • the number of resources can be 16G memory, 32G memory, etc.
  • bandwidth resources such as an example, the number of resources can be 1M bandwidth, 10M Bandwidth etc.
  • the central management and control device can also have the function of computing power orchestration.
  • the computing power orchestration is oriented to relatively complex application scenarios. Multiple cloud computing services are bound together as the smallest resource requirement unit. In this way, in the resource scheduling In the process, multiple cloud computing services can be bound together as a whole, and one or several edge cloud nodes can be selected for them, and the same or several edge cloud nodes can provide resources for them together. Computing power scheduling improves the diversity of resource scheduling and increases the flexibility of resource scheduling, but it does not affect the overall process of resource scheduling.
  • the above-mentioned resource scheduling function can be realized by the cooperation of the resource scheduling management and control module and the resource scheduling service module, and the detailed process will not be repeated.
  • the image management function of the central control device mainly refers to the management of images and the provision of required images for edge cloud nodes.
  • the edge cloud node can create an instance on the corresponding resource device according to the image, and then the created instance can provide users with required cloud computing services.
  • edge cloud nodes In practical applications, there are various scenarios where mirroring needs to be provided for edge cloud nodes.
  • a user such as a service demander
  • the central management and control device can provide a corresponding image for the scheduled target edge cloud node.
  • the central management and control device can provide a corresponding image for the scheduled target edge cloud node.
  • the central management and control device can provide a corresponding image for the scheduled target edge cloud node.
  • the edge cloud node of the computing service provides a corresponding image, so that the edge cloud node creates a new instance based on the image, so as to achieve the purpose of capacity expansion.
  • the edge cloud node that needs to be mirrored is recorded 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.
  • Depends. takes the central control device to provide a mirror image for the first edge cloud node as an example to describe the image management function of the central control device.
  • the central management and control device can first determine the target image that needs to be provided to the first edge cloud node; then, provide the target image for the first edge cloud node for use by the first edge cloud node
  • the target image provides cloud computing services.
  • a mirror library is maintained, and the mirror library is used to store images in the system.
  • Users can choose to use the mirror in the mirror library.
  • the user can be provided with a mirror configuration interface with a drop-down menu.
  • the drop-down menu includes many mirrors that can be selected by the user, and the user can choose the mirror to use.
  • the central control device can obtain the image required by the first edge cloud node from the mirror library, and then provide the image to the first edge cloud node, and use the image
  • the permissions are open to the corresponding users.
  • the central management and control device may directly issue the target image to the first edge cloud node, or instruct the first edge cloud node to download the target image to a designated storage location.
  • the central control device can also maintain the correspondence between the issued image and the edge cloud node where the issued image is located.
  • the correspondence relationship may include the identification information of the issued image and the identification information of the edge cloud node where the image has been issued.
  • the issued image refers to the image that the central control device has provided (for example, issued) to one or some edge cloud nodes; the edge cloud node where the issued image is located refers to the edge cloud node to which the issued image is provided.
  • the same image may be provided (for example, distributed) to one edge cloud node, or may be provided (for example, distributed) to multiple edge cloud nodes.
  • the central management and control device can also control the first edge cloud node from the image that already has the image.
  • Other edge cloud nodes acquire the image without directly providing the image to the first edge cloud node, which can reduce the processing burden of the central control device to a certain extent, and can also improve the efficiency of image acquisition under the condition of reasonable control.
  • the central management and control device may determine the mirror image that needs to be provided to the first edge cloud node.
  • the image provided by the cloud node is recorded as the target image; according to the information of the target image, a match is made in the correspondence between the maintained issued image and the edge cloud node where the issued image is located; if the corresponding relationship is matched with the target Mirror the corresponding second edge cloud node, which means that the target image has been provided to the second edge cloud node, then the target image at the second edge cloud node can be provided to the first edge cloud node; where the second edge cloud node
  • the node can also be an edge cloud node in the network system, and the number can be one or more.
  • the target image at the second edge cloud node can be obtained.
  • the central management and control device may specifically send the information of the second edge cloud node and the target mirror to the edge management and control device; the edge management and control device 103 may communicate with the second edge cloud node according to the The information of the target image, the target image at the second edge cloud node is provided to the corresponding resource device in the first edge cloud node for the corresponding resource device to create an instance that can provide cloud computing services based on the target image, and then provide it to the service demander The cloud computing service.
  • the information of the second edge cloud node may be any information that can identify the second edge cloud node, for example, it may be information such as the ID, name, or geographic location of the second edge cloud node.
  • the information of the target image can be any information that can identify the target image, such as the ID, name, or number of the target image.
  • the central management and control device 101 may specifically send the information of the second edge cloud node and the target image to the first edge cloud
  • the edge management and control device in the node is used for the edge management and control device in the first edge cloud node to obtain the target image from the second edge cloud node through the communication channel between it and the edge management and control device in the second edge cloud node and provide it to the second edge cloud node.
  • a corresponding resource device in an edge cloud node is used for the edge management and control device in the first edge cloud node to obtain the target image from the second edge cloud node through the communication channel between it and the edge management and control device in the second edge cloud node and provide it to the second edge cloud node.
  • the edge management and control device 103 in the first edge cloud node can receive the information of the second edge cloud node and the target image sent by the central management and control device 101, and according to the information of the second edge cloud node and the target image, it can communicate with the Second, the communication channel between the edge management and control devices in the edge cloud node, obtains the target image from the second edge cloud node, and provides the target image to the corresponding resource device in the first edge cloud node, so that the corresponding resource device can create an image based on the target image.
  • a process of obtaining the target image from the second edge cloud node includes: The edge management and control device 103 in the edge cloud node sends a request for obtaining the target image to the edge management and control device 103 in the second edge cloud node through the communication channel between it and the edge management and control device in the second edge cloud node. Carry the information of the target image.
  • the edge management and control device 103 in the second edge cloud node receives the request, and determines whether there is a target image in the second edge cloud node according to the target image information carried in the request, and whether there is a target image in the second edge cloud node
  • the target image is returned to the edge management and control device 103 in the first edge cloud node, or the target image is mirrored in the second edge cloud node
  • the storage address of is returned to the edge management and control device 103 in the first edge cloud node.
  • the edge management and control device 103 in the first edge cloud node receives the target image returned by the edge management and control device 103 in the second edge cloud node, or receives the target image returned by the edge management and control device 103 in the second edge cloud node in the second edge cloud
  • the storage address in the node read or download the target image according to the storage address.
  • the edge management and control device 103 in the first edge cloud node and the edge management and control device 103 in the second edge cloud node may establish a communication channel by themselves, or may establish a channel under the control of the central management and control device 101.
  • the central management and control device can also control the establishment of communication channels between different edge management and control devices, and is responsible for maintaining the information of the existing communication channels between the edge management and control devices, for example, which edge management and control devices have established communication channels and communication When the channel is established, the status of the communication channel, and the retention time information.
  • the central management and control device determines 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 and control device in the first edge cloud node, it can also According to the information of the existing communication channel between the maintained edge management and control devices, determine whether there is a communication channel between the edge management and control device in the first edge cloud node and the edge management and control device in the second edge cloud node; if the judgment result is No, that is, there is no communication channel between the edge management and control device in the first edge cloud node and the edge management and control device in the second edge cloud node, you can control the edge management and control device in the first edge cloud node and the second edge cloud.
  • the edge management and control device in the node establishes a communication channel, so that the edge management and control device in the first edge cloud node can obtain the target image from the second edge cloud node through the communication channel.
  • the central management and control device After the edge management and control device in the first edge cloud node establishes a communication channel with the edge management and control device in the second edge cloud node, the central management and control device provides information about the second edge cloud node and the target image to the first edge cloud node Edge control equipment in China.
  • the judgment result is yes, that is, there is already a communication channel between the edge management and control device in the first edge cloud node and the edge management and control device in the second edge cloud node, you can directly mirror the second edge cloud node and the target The information is provided to the edge management and control device in the first edge cloud node.
  • the central management and control device can also provide the edge management and control device in the first edge cloud node with the information of the second edge cloud node and the target image, according to the existing communication channels between the maintained edge management and control devices.
  • the central management and control device may also provide the target image at the second edge cloud node to the first edge cloud node according to the second edge cloud node.
  • the attribute of the cloud node determines whether the second edge cloud node is suitable for providing the target image for the first edge cloud node; if the judgment result is yes, that is, the second edge cloud node is suitable for providing the target image for the first edge cloud node, the first edge cloud node can be 2.
  • the target image at the edge cloud node is provided to the first edge cloud node; if the judgment result is no, the target image can be obtained from the image library and the target image is provided to the first edge cloud node.
  • the operator to which the second edge cloud node belongs can be combined to determine whether the operator to which the second edge cloud node belongs is the same as the operator to which the first edge cloud node belongs; if the judgment result is yes, it means that the second edge cloud node is The first edge cloud node is an edge cloud node under the same operator.
  • the two can perform data transmission, and the data transmission rate is faster than the cross-operator data transmission rate, which is suitable for providing target mirroring for the first edge cloud node.
  • the location attribute of the second edge cloud node can be combined to determine whether the distance between the second edge cloud node and the first edge cloud node is less than the set distance threshold; if the judgment result is yes, the second edge cloud node It is close to the first edge cloud node, which is suitable for providing target mirroring for the first edge cloud node. In this way, the second edge cloud node that is closer to the first edge cloud node provides a mirror image for the first edge cloud node, which is convenient for the first edge cloud node. The edge cloud node quickly obtains the image to improve efficiency.
  • the distance between the second edge cloud node and the first edge cloud node can be the average distance between two edge cloud nodes, or the distance between the centers of two edge cloud nodes, or two edge clouds
  • the distance between nodes and the nearest outer edge can be flexibly defined according to requirements.
  • the bandwidth attribute 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 determination result is yes, it means that the bandwidth resource of the second edge cloud node is relatively abundant, and it is suitable for The first edge cloud node provides the target image, so that the second edge cloud node with sufficient bandwidth resources provides the image for the first edge cloud node, which can ensure the transmission rate of the image, facilitate the first edge cloud node to quickly obtain the image, and improve efficiency .
  • the load attribute 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 judgment result is yes, it means that the load of the second edge cloud node is lighter, and it is suitable for The first edge cloud node provides the target image, so that the second edge cloud node with lighter load provides the image for the first edge cloud node. On the one hand, it can achieve load balancing, and on the other hand, it is also convenient for the first edge cloud node to quickly obtain the image. ,Improve efficiency.
  • the multiple attributes of the second edge cloud node can be combined to use the above several methods in combination, and then select a target image suitable for the first edge cloud node.
  • the second edge cloud node For example, if there are multiple second edge cloud nodes, the operators to which the multiple second edge cloud nodes belong can be combined to select from the multiple second edge cloud nodes that belong to the same operator as the first edge cloud node. Two edge cloud nodes; furthermore, if there are still multiple second edge cloud nodes selected, the load of the selected second edge cloud node may be further selected from the load to be the smallest or lower than the set load threshold The second edge cloud node provides a target image for the first edge cloud node.
  • the target image may have been provided to the first edge cloud node.
  • the image used is the same as the image used by the previous instance. If the edge cloud node still stores the image used by the previous instance, there is no need to repeatedly provide the image for the edge cloud node.
  • the central management and control device can determine the maintained issued image and the edge cloud node where the issued image is located before providing the target image at the second edge cloud node to the first edge cloud node Whether the first edge cloud node is included in the corresponding relationship; if the judgment result is yes, it indicates that the target image has been provided to the first edge cloud node, and the target image is still stored in the first edge cloud node, then the target image can be The information is provided to the first edge cloud node for the first edge cloud node to read the target image stored in it, without the need to transmit the target image again, which can save network resources consumed by the transmission of the target image; if the judgment result is no, it indicates that it has not been sent to The first edge cloud node has provided the target image, or the target image no longer exists in the first edge cloud node, the target image at the second edge cloud node may be provided to the first edge cloud node.
  • the edge management and control device when the edge management and control device is deployed in the first edge cloud node, if the central management and control device determines that the corresponding relationship between the maintained issued image and the edge cloud node where the issued image contains the target image, the target image
  • the image information is provided to the edge management and control device in the first edge cloud node, and the edge management and control device in the first edge cloud node can obtain the target image from the storage space of the image in the first edge cloud node according to the information of the target image, and set the target image
  • the image is provided 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 according to the target image.
  • the same edge cloud node may provide multiple cloud computing services for the same user or different users, and may receive multiple images, and these images will be stored in the edge cloud node.
  • Edge cloud nodes can provide a certain amount of storage space for storing images. Considering that the storage space of the image in the edge cloud node is limited, in order to have enough storage space to store the newly received image, the edge cloud node needs to eliminate the locally stored image.
  • the central management and control device is responsible for providing a mirroring elimination strategy for edge cloud nodes. The central management and control device can generate the elimination strategy of the image, deliver the elimination strategy to each edge cloud node, and each edge cloud node performs elimination processing on the stored image according to the elimination strategy.
  • the central management and control equipment can issue the elimination strategy to the edge management and control equipment, and the edge management and control equipment eliminates the images stored in each edge cloud node according to the elimination strategy. Furthermore, in the case where edge management and control equipment is deployed in each edge cloud node, the central management and control equipment can issue the elimination strategy to the edge management and control equipment in each edge cloud node, and the edge management and control equipment in each edge cloud node will be The elimination strategy eliminates the image stored in the edge cloud node to which it belongs.
  • the elimination strategy may be an elimination strategy with the earliest receiving time, that is, according to the receiving time of the image, the image with the earliest receiving time is preferentially eliminated.
  • the elimination strategy may be the elimination strategy with the least frequency of use, that is, the image with the least frequency of use is preferentially eliminated according to the frequency of use of the image.
  • the elimination strategy may be the elimination strategy with the largest resource occupation, that is, according to the size of the storage space occupied by the image, the image with the largest storage space is first eliminated.
  • the image stored in the node can be eliminated regularly according to the above elimination strategy; or, whenever a new image needs to be received or acquired, it can be judged whether there is enough storage space in the node for storage If there is not enough storage space in the current node for the new image, the image stored in the node is eliminated according to the above elimination strategy, so as to store the new image.
  • the edge in the first edge cloud node can determine whether there is enough storage space in the first edge cloud node to store the target image; if there is not enough storage space in the first edge cloud node, it will eliminate the image stored in the first edge cloud node according to the elimination strategy. In order to have enough storage space to store the target image. Optionally, if there is enough storage space in the first edge cloud node, the image stored in the first edge cloud node may not be eliminated temporarily.
  • the network system 100 further includes: an image construction device 104.
  • the image construction device 104 may be deployed in one or more edge cloud nodes, and is mainly responsible for the construction and verification of application images.
  • the image construction device 104 can provide an edge cloud environment, can build an image that is compatible with the edge cloud environment, and can also verify whether the image is compatible with the edge cloud environment.
  • the image that is not compatible with the edge cloud environment can be reconstructed or output Adapted prompt information, etc. Based on the image building device 104, the user can add a new image to the network system 100.
  • a user can submit a first request for adding a new image to the central management and control device.
  • the first request includes image construction information;
  • the device sends a construction request, which includes image construction information; after receiving the construction request, the image construction device obtains the image construction information from it, constructs an image adapted to the edge cloud environment based on the image construction information, and returns the constructed image to the center Control equipment; the central control equipment receives the newly constructed mirror image returned by the mirror construction equipment and adds it to the mirror library to continuously enrich the mirror library.
  • a mirroring rule and specification can be provided to users (such as service demanders), allowing users to make or generate mirrors by themselves.
  • the mirrors generated or made by users need to conform to the edge cloud Environmental safety, regulations and other related requirements.
  • the user can send a second request for adding a new image to the central control device.
  • the second request includes the image to be added.
  • the new image refers to the image made or generated by the user. This embodiment does not It does not limit the way users make or generate images.
  • the central control 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 construction device; the image construction device adapts the image to be added to the edge cloud environment; if it is to be added The image is adapted to the edge cloud environment, and the image construction device returns a message to the central control device that the new image is adapted to the edge cloud environment; if the new image is not compatible with the edge cloud environment, the image construction device returns to the central control device A message that the new image is not compatible with the edge cloud environment.
  • the central control equipment if it receives a message from the mirror construction device that the new image to be added is adapted to the edge cloud environment, it will add the new mirror to the mirror library; if the mirror construction service is received, the mirror construction device returns The message that the new image to be added is not compatible with the edge cloud environment, or informs the user to re-submit the new image after reconstruction, or informs the user to provide the reconstruction method of the new image for the image building service image building equipment According to the reconstruction method, the newly added image is reconstructed into an image adapted to the edge cloud environment.
  • the central control device can provide the reconstruction method to the image construction device, and the image construction device reconstructs the newly added image according to the reconstruction method to make it compatible with the edge cloud environment It adapts and returns the reconstructed image to the central control device; the central control device receives the reconstructed image and adds it to the mirror library.
  • the image construction device 104 can be a logical device with functions such as image construction and verification. These functions can be implemented on one physical machine or virtual machine, or distributed on multiple physical machines or virtual machines. on board. Of course, the image construction device 104 of this embodiment may also be one or more physical devices with functions such as image construction and verification.
  • the embodiments of this application do not limit the implementation structure of the image construction device, and any device structure with the above-mentioned functions is applicable to the embodiments of this application.
  • the central management and control device can count the usage frequency of each mirror in the mirror library regularly or in real time, use mirrors with a frequency less than the frequency threshold as the mirrors to be deleted, and execute the mirror deletion process to delete them.
  • the central management and control device may also receive a mirror deletion request submitted by a user (such as a service demander), use the mirror deleted in the mirror deletion request as a mirror to be deleted, and execute the mirror deletion process to delete it.
  • the image deletion request may carry information of the image to be deleted, such as ID, name, or serial number.
  • any of the above methods can be used to determine the image to be deleted.
  • the image to be deleted can be deleted from the mirror library on the one hand, and the image to be deleted can be indicated to be stored on the other hand.
  • the edge cloud node will delete the image to be deleted.
  • the central management and control device may match the maintained corresponding relationship between the issued image and the edge cloud node where the issued image is located according to the image to be deleted, and determine the edge cloud node storing the image to be deleted according to the matching result.
  • the third edge cloud node corresponding to the image to be deleted is matched in the corresponding relationship, it means that the image to be deleted has been issued to the third edge cloud node, and the image to be deleted is still stored in the third edge cloud node, so
  • the third edge cloud node sends a deletion instruction, and the deletion instruction carries information about the image to be deleted to instruct the third edge cloud node to delete the image to be deleted stored therein.
  • the third edge cloud node may be one or multiple.
  • the central management and control device may specifically send a deletion instruction to the edge management and control device 103; the edge management and control device 103 receives the deletion instruction issued by the central management and control device, and then deletes the instruction from the Obtain the information of the image to be deleted in, and determine whether the image to be deleted is stored in the third edge cloud node according to the information of the image to be deleted; if the image to be deleted is stored, delete the image to be deleted in the third edge cloud node.
  • the central management and control device 101 may specifically send a deletion instruction to the edge management and control device 103 in the third edge cloud node; the edge management and control device in the third edge cloud node 103 receives the delete instruction issued by the central management and control device, obtains the information of the image to be deleted from the delete instruction, and judges whether the image to be deleted is stored in the third edge cloud node according to the information of the image to be deleted; The image to be deleted stored in the third edge cloud node is deleted.
  • the central control device deletes the image to be deleted from the image library, and the edge cloud node storing the image to be deleted also deletes the image to be deleted stored in it, the image deletion process is completed.
  • the capabilities supported by hardware or software can be virtualized to provide computing, network, and computing for the instance.
  • the corresponding image will be mounted to the corresponding instance in the form of a system disk. After the instance is created, try 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 resource device provides computing, network, and storage resources for the instance under the control of the edge management and control device, including: the edge management and control device applies for related resources from the resources allocated or reserved in the target edge node cloud according to the resource template provided by the central management and control device
  • the computing resources, storage resources and/or network resources of the target edge cloud node are used to create related resources by calling the calculation, storage, network and other executors in the target edge cloud node.
  • resource creation actions include: processing storage-related resources, creating an instance system disk based on the configuration information and content of the image, creating a corresponding data disk based on the resource template; creating network resources that the instance depends on, such as IP addresses, virtual switches And so on; and combine resource templates to create computing resources.
  • the above-mentioned image management and distribution functions can be realized by the cooperation of the image management and control module and the image service module, and the detailed process will not be repeated.
  • the resource scheduling, image management, operation and maintenance of edge cloud nodes are uniformly controlled based on centralized management and control, and the edge cloud nodes can be managed and coordinated to the greatest extent. , It can reduce errors caused by single-point self-control or unsynchronized information of the entire network, and can use the characteristics of centralized management to achieve the optimization of resource scheduling, avoiding the waste of local resources at the edge.
  • the embodiments of the present application provide management and control methods from the perspective of edge management and control equipment, which are described in detail below.
  • FIG. 2a is a schematic flowchart of a management and control method provided by an exemplary embodiment of this application. This embodiment is described from the perspective of edge management and control equipment. As shown in Figure 2a, the method includes:
  • edge management and control device determines that the central management and control device is not correct or cannot manage and control the edge cloud node
  • at least one of the following methods may be adopted but not limited to:
  • Method 1 Determine whether to maintain a connection with the central management and control device, and in the case of loss of connection with the central management and control device, determine that the central management and control device cannot control the edge cloud node.
  • the central management and control device sends the first-type monitoring instruction to the edge management and control device to control the edge management and control device to monitor at least one edge cloud node. Based on this, the edge management and control device can determine whether it has received the first type of monitoring instruction sent by the central management and control device, and if it has not received the first type of monitoring instruction sent by the central management and control device, it can determine that the central management and control device is incorrect or unable to control the edge cloud. Nodes are managed and controlled.
  • the edge management and control device and the central management and control device may pre-appoint the waiting time of the first type of monitoring instruction. If the waiting time is exceeded and the first type of monitoring instruction sent by the central management and control device is not received, it is determined that the first type of monitoring instruction is not received The first type of monitoring instructions sent by the central control equipment.
  • the central management and control device sends the second type of monitoring instruction corresponding to the specified monitoring dimension to the edge management and control device to control the edge management and control device to monitor at least one edge cloud node from the specified monitoring dimension. Based on this, the edge management and control device can determine whether to receive the second type of monitoring instruction sent by the central control device in the designated monitoring dimension; if the second type of monitoring instruction sent by the central control device is not received in the designated monitoring dimension, determine the center The control equipment is incorrect or unable to control the edge cloud node in the specified monitoring dimension.
  • the edge management and control device can also synchronize the management and control data during the loss of connection to the central management and control device.
  • the edge control device can independently control the edge cloud node.
  • the edge management and control device controls the edge cloud nodes, including but not limited to at least one of the following operations:
  • the abnormal operating state of the target object may be analyzed, and at least one candidate processing method may be determined according to the analysis result; from the at least one candidate processing method Obtain the target processing method in, and perform exception processing on the target object according to the target processing method.
  • obtaining the target processing method from at least one candidate processing method includes:
  • While maintaining the connection with the central control device report at least one candidate processing method to the central control device for the central control device to select a processing method; receive the processing method returned by the central control device as the target processing method; or
  • the target processing method is selected from at least one candidate processing method according to the set selection strategy.
  • the selection strategy can be flexibly set according to the application scenario, which is not limited in this application.
  • the selection strategy can be to select the simplest processing method, or to select the processing method that consumes the least resources, and so on.
  • the performance or attributes of each processing method can be known in advance or judged in real time.
  • At least one candidate processing method can also be output to the edge management and control personnel, and the edge management and control personnel can select the target processing method to use.
  • This embodiment of the application does not limit this.
  • it can be output to terminal devices such as mobile phones and computers used by edge management personnel in the form of short messages, in-app messages, system messages, and/or emails.
  • each edge management and control device can autonomously belong to the edge cloud node under the condition that the central management and control equipment is incorrect or cannot manage and control the edge cloud node to which it belongs Take control.
  • the edge management and control device autonomously manages at least one edge cloud node, and may periodically manage and control at least one edge cloud node according to a timing task.
  • the edge management and control device can also autonomously manage and control at least one edge cloud node according to other autonomous strategies. For example, it can autonomously manage and control at least one edge cloud node at a fixed time every day.
  • the edge management and control device may also assist the central management and control device to manage and control at least one edge cloud node.
  • the process for the edge management and control equipment to assist the central management and control equipment to manage and control edge cloud nodes includes:
  • the edge management and control device may periodically monitor at least one edge cloud node from at least one monitoring dimension according to a timing task.
  • the edge management and control device can monitor at least one edge cloud node in the network system under the control of the central management and control device.
  • the embodiment of the present application does not limit it, and two alternative embodiments are described below.
  • the implementation process of step 21b includes: monitoring at least one edge cloud node from at least one monitoring dimension according to the first type of monitoring instruction sent by the central management and control device.
  • the implementation process of step 22b includes: reporting monitoring data in at least one monitoring dimension to the central management and control device, so that the central management and control device can manage and control at least one edge cloud node according to the monitoring data in at least one monitoring dimension.
  • the implementation process of step 21b includes: monitoring at least one edge cloud node in a designated monitoring dimension according to the second type of monitoring instruction sent by the central management and control device.
  • the implementation process of step 22b includes: reporting the monitoring data on the specified monitoring dimension to the central management and control device, so that the central management and control device can manage and control at least one edge cloud node according to the monitoring data on the specified monitoring dimension.
  • the edge management and control device can assist the central management and control device to manage and control edge cloud nodes from at least one monitoring dimension, as described below with examples.
  • the implementation process of step 21b includes: monitoring the status of an object in a running state in at least one edge cloud node.
  • the implementation process of step 22b includes: reporting the monitored operating state of the object in the operating state to the central management and control device, so that the central management and control device can identify the target object with an abnormal operating state and perform abnormal processing on the target object.
  • the implementation process of step 21b includes: monitoring the life cycle of an object in a running state in at least one edge cloud node.
  • the implementation process of step 22b includes: reporting the life cycle of the monitored object in the running state to the central control device, so that the central control device controls the stopping, restarting or deleting of the running object after stopping;
  • the implementation process of step 21b includes: collecting log data in at least one edge cloud node.
  • the implementation process of step 22b includes: reporting the log data to the central management and control device, so that the central management and control device can perform data analysis on the log data and perform subsequent actions according to the data analysis result;
  • the implementation process of step 21b includes: performing traffic monitoring on at least one edge cloud node.
  • the implementation process of step 22b includes: reporting the monitored traffic attack event to the central control device, so that the central control device can block the traffic attack event;
  • the implementation process of step 21b includes: performing network security vulnerability scanning on at least one edge cloud node.
  • the implementation process of step 22b includes: reporting the scanned network security vulnerabilities to the central control device, so that the central control device can repair the network security vulnerabilities;
  • the implementation process of step 21b includes: monitoring the resource usage in at least one edge cloud node.
  • the implementation process of step 22b includes: reporting the monitored resource usage information to the central management and control device, so that the central management and control device can expand or reduce the resource capacity of at least one edge cloud node.
  • the central control device is combined with the edge control device.
  • the edge control device can assist the central control device to manage and control at least one edge cloud node.
  • the edge control device also has a certain ability to manage and control itself. , It can autonomously control edge cloud nodes when the central control equipment is incorrect or unable to control edge cloud nodes. Two-level management and control can be achieved, which can more fully and comprehensively control edge cloud nodes. Computing is placed in edge cloud nodes closer to the terminal for processing" provides conditions, and can use the resources in edge cloud nodes to provide users with cloud computing services, which is beneficial to reduce response delays and reduce the impact of central cloud or traditional cloud computing platforms. Pressure to reduce bandwidth costs.
  • the “management and control” in the foregoing method embodiment may be the management and control of the operation and maintenance dimension.
  • the central management and control device can perform operation and maintenance management and control on at least one edge cloud node with the assistance of the edge management and control device.
  • the aforementioned at least one monitoring dimension or the designated monitoring dimension can be the operation and maintenance dimension
  • the central management and control device can report at least one operation and maintenance dimension or the monitoring data on the designated operation and maintenance dimension reported by the edge management and control device.
  • An edge cloud node performs operation and maintenance control.
  • the edge management and control device can autonomously perform the operation and maintenance control on at least one edge cloud node.
  • the edge management and control device may perform O&M management and control on at least one edge cloud node according to the monitored at least one O&M dimension or monitoring data on a specified O&M dimension.
  • FIG. 3 is a schematic structural diagram of a central management and control device provided by an exemplary embodiment of this application.
  • the central management and control device includes: a memory 31, a processor 32, and a communication component 33.
  • the memory 31 is used to store computer programs, and can be configured to store various other data to support operations on the central control device. Examples of these data include instructions, messages, pictures, videos, etc. used to operate any application or method on the central control device.
  • the processor 32 is coupled with the memory 31 and is configured to execute the computer program in the memory 31 to receive the monitoring data for at least one edge cloud node in the network system reported by the edge management and control device through the communication component 33, and according to the The monitoring data controls at least one edge cloud node.
  • the processor 32 is specifically configured to: send a first-type monitoring instruction to the edge management and control device through the communication component 33 to instruct the edge management and control device to monitor at least one edge cloud node from at least one monitoring dimension and The monitoring data on at least one monitoring dimension is reported to the central management and control device; at least one edge cloud node is managed and controlled according to the monitoring data on at least one monitoring dimension reported by the edge management and control device.
  • the first type of monitoring instruction is a monitoring instruction that instructs the edge management and control device to monitor at least one edge cloud node from at least one monitoring dimension and report monitoring data in at least one monitoring dimension. It is worth noting that the monitoring dimensions can be flexibly set according to application requirements and preset into edge control equipment and central control equipment.
  • the processor 32 is specifically configured to: send a second type of monitoring instruction to the edge management and control device through the communication component 33, the second type of monitoring instruction corresponds to a specified monitoring dimension, and is used to instruct the edge management and control device to perform an
  • the edge cloud node monitors and reports the monitoring data on the specified monitoring dimension; at least one edge cloud node is controlled according to the monitoring data on the specified monitoring dimension.
  • each designated monitoring dimension can correspond to a second-type monitoring instruction.
  • the above-mentioned at least one monitoring dimension or designated monitoring dimension may include but not limited to the following dimensions: the object dimension in the running state, the log dimension, the security dimension, the resource dimension, etc.
  • the object dimension in the running state may include the operating state dimension of the object and/or the life cycle dimension of the object;
  • the security dimension may include: the traffic attack dimension and/or the security vulnerability dimension.
  • the processor 32 is specifically configured to perform but not limited to at least one of the following operations:
  • Control the edge management and control device to monitor the status of objects in the running state in at least one edge cloud node; receive the running status of the objects in the running state reported by the edge management and control device; in the running state of the objects in the running state reported from the edge management and control device Identify the objects with abnormal operating status, and for ease of description and distinction, call the objects with abnormal operating status as target objects, and perform exception handling for the target objects; or
  • Control the edge management and control device to monitor the life cycle of the object in the running state in at least one edge cloud node; receive the life cycle of the object in the running state reported by the edge management and control device; according to the life of the object in the running state reported by the edge management and control device Period, control the object in the running state to stop, restart or delete after stopping; or
  • Control the edge management and control device to collect log data in at least one edge cloud node; receive the log data reported by the edge management and control device; perform data analysis on the log data, and perform follow-up actions based on the results of the data analysis, such as billing, risk control, and/or Add or delete examples, etc.; or
  • Control the edge management and control device to monitor the traffic of at least one edge cloud node; receive the traffic attack event reported by the edge management and control device; block the traffic attack event that occurs in the edge cloud node; or
  • Control the edge management and control device to scan for network security vulnerabilities on at least one edge cloud node; receive network security vulnerabilities reported by the edge management and control device; repair the network security vulnerabilities; or
  • Control the edge management and control device to monitor the resource usage in at least one edge cloud node; receive the resource usage information reported by the edge management and control device; and perform resource expansion or reduction on at least one edge cloud node according to the resource usage information reported by the edge management and control device.
  • the “management and control” in this embodiment may be the management and control of the operation and maintenance dimension.
  • the processor 32 may be specifically configured to: receive monitoring data for at least one edge cloud node in the network system reported by the edge management and control device, At least one edge cloud node is operated and maintained according to the monitoring data. Further, the processor 32 can also control the edge management and control device to monitor at least one edge cloud node from at least one operation and maintenance dimension or a specified operation and maintenance dimension; and according to at least one operation and maintenance dimension reported by the edge management and control device or the specified operation and maintenance dimension. Monitor data and perform operation and maintenance control on at least one edge cloud node.
  • edge management and control device For details on controlling the edge management and control device to monitor at least one edge cloud node from at least one operation and maintenance dimension or a designated operation and maintenance dimension, and to perform operation and maintenance management and control on at least one edge cloud node, please refer to the foregoing description, and will not be repeated here.
  • the central management and control device further includes: a display 34, a power supply component 35, an audio component 36 and other components. Only some of the components are schematically shown in FIG. 3, which does not mean that the central control equipment only includes the components shown in FIG. In addition, the components in the dashed box in Figure 3 are optional components, which may be determined by the implementation of the central control equipment. If the central management and control device is a server-shaped device, it may optionally not include the display 34 and the audio component 36; if the central management and control device is a terminal device-type device, it may optionally include the display 34 and the audio component 36.
  • an embodiment of the present application also provides a computer-readable storage medium storing a computer program.
  • the computer program is executed by one or more processors, the one or more processors can implement the above method in the above-mentioned method embodiments. Steps or operations performed by the equipment.
  • FIG. 4 is a schematic structural diagram of an edge management and control device provided by an exemplary embodiment of this application. As shown in FIG. 4, the device includes: a memory 41 and a processor 42.
  • the memory 41 is used to store computer programs, and can be configured to store various other data to support operations on edge management and control devices. Examples of these data include instructions, messages, pictures, videos, etc. for any application or method operating on edge control devices.
  • the processor 42 coupled with the memory 41, is configured to execute the computer program in the memory 41 to determine that the central control device in the network system is incorrect or cannot control at least one edge cloud node in the network system; One edge cloud node performs management and control.
  • the processor 42 is specifically configured to perform at least one of the following operations when determining that the central management and control device is incorrect or unable to manage and control the edge cloud node:
  • the edge control device loses the connection with the central control device, it is determined that the central control device cannot control at least one edge cloud node;
  • the central management and control device In the case that the second type of monitoring instruction sent by the central management and control device is not received in the specified monitoring dimension, it is determined that the central management and control device is incorrect or unable to control at least one edge cloud node in the specified monitoring dimension.
  • the processor 42 is further configured to synchronize the management and control data during the loss of connection to the central management and control device after the connection between the edge management and control device and the central management and control device is restored.
  • the processor 42 is specifically configured to perform at least one of the following operations when autonomously managing and controlling at least one edge cloud node:
  • the processor 42 when the processor 42 performs abnormal processing on the monitored target object whose operating status is abnormal, it is specifically configured to: analyze the abnormal operating status of the target object, and determine at least one candidate processing method according to the analysis result; The target processing method is acquired from at least one candidate processing method, and exception processing is performed on the target object according to the target processing method.
  • the edge management and control device of this embodiment further includes: a communication component 43.
  • the processor 42 obtains the target processing mode from the at least one candidate processing mode, it is specifically configured to report the at least one candidate processing mode to the central management and control device when the edge management and control device maintains a connection with the central management and control device to For the central control device to select a processing method; receive the processing method returned by the central control device through the communication component 43 as the target processing method; or, when the edge control device loses the connection with the central control device, output at least one candidate processing method to Edge control personnel, for the control personnel to choose the processing method; in response to the selection operation of the edge control personnel, determine the selected processing method as the target processing method; or, in the case of the edge control device loses the connection with the central control device, follow
  • the set selection strategy selects the target processing method from at least one candidate processing method.
  • 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 and control device, so that the central management and control device can monitor at least one edge cloud node according to the monitoring data. Cloud nodes are managed and controlled.
  • the processor 42 is further configured to monitor at least one edge cloud node under the control of the central management and control device.
  • the processor 42 is specifically configured to: monitor at least one edge cloud node from at least one monitoring dimension according to the first type of monitoring instruction sent by the central management and control device, and report monitoring data on the at least one monitoring dimension to the central management and control device , So that the central management and control device controls at least one edge cloud node based on the monitoring data on at least one monitoring dimension; or, according to the second type of monitoring instruction sent by the central management and control device, performs at least one edge cloud node on the designated monitoring dimension Monitor and report the monitoring data on the designated monitoring dimension to the central control device, so that the central control device can manage and control at least one edge cloud node according to the monitoring data on the designated monitoring dimension.
  • the processor 42 is further configured to periodically monitor the at least one edge cloud node from at least one monitoring dimension according to a timing task, and report monitoring data on the at least one monitoring dimension to the center A control device for the central control device to manage and control at least one edge cloud node according to monitoring data in at least one monitoring dimension.
  • processor 42 is specifically configured to perform at least one of the following operations when monitoring at least one edge cloud node and reporting the monitoring data to the central management and control device:
  • Monitor the resource usage in at least one edge cloud node and report 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.
  • each edge cloud node is separately deployed with an edge management and control device, and the processor 42 is specifically configured to autonomously manage and control the edge cloud node to which the edge management and control device belongs.
  • the “management and control” in this embodiment may be the management and control of the operation and maintenance dimension.
  • the processor 42 may be specifically used to: autonomously perform operation and maintenance control of at least one edge cloud node; or control the control of equipment in the center Monitor at least one edge cloud node from at least one operation and maintenance dimension or a designated operation and maintenance dimension.
  • autonomously performing operation and maintenance control of at least one edge cloud node, or monitoring at least one edge cloud node from at least one operation and maintenance dimension or a designated operation and maintenance dimension under the control of a central control device please refer to the previous description. This will not be repeated here.
  • the edge management and control device further includes: a display 44, a power supply component 45, an audio component 46 and other components. Only some components are schematically shown in FIG. 4, which does not mean that the edge management and control device only includes the components shown in FIG. 4. In addition, the components in the dashed box in FIG. 4 are optional components, which may be determined by the implementation of the edge control equipment. If the edge management and control device is a server type device, optionally, the display 44 and the audio component 46 may not be included; if the edge management and control device is a terminal device type, it may optionally include the display 44 and the audio component 46.
  • an embodiment of the present application also provides a computer-readable storage medium storing a computer program.
  • the computer program is executed by one or more processors, the one or more processors can implement the above method and the embodiments can be controlled by the edge. Steps or operations performed by the equipment.
  • the memory in Figures 3 and 4 above can be implemented by any type of volatile or non-volatile storage devices or their combination, 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 memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory magnetic memory
  • flash memory magnetic disk or optical disk.
  • the communication components in Figures 3 and 4 are configured to facilitate wired or wireless communication between the device where the communication component is located and other devices.
  • the device where the communication component is located can access a wireless network based on communication standards, such as WiFi, 2G or 3G, or a combination of them.
  • the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component may further 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.
  • NFC near field communication
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra wideband
  • Bluetooth Bluetooth
  • the display in FIGS. 3 and 4 described above includes a screen, and the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touch, sliding, and gestures on the touch panel. The touch sensor can not only sense the boundary of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
  • the power components in Figures 3 and 4 above provide power for various components of the equipment where the power components are located.
  • 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 for the device where the power supply component is located.
  • the audio component includes a microphone (MIC).
  • the microphone When the device where the audio component is located is in an operating mode, such as call mode, recording mode, and voice recognition mode, the microphone is configured to receive external audio signals.
  • the received audio signal can be further stored in a memory or sent via a communication component.
  • the audio component further includes a speaker for outputting audio signals.
  • the embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
  • the computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • the memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM).
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例提供一种网络系统、管控方法、设备及存储介质。在本申请实施例中，结合边缘计算的概念，考虑将云计算的能力放到距离终端侧更近的边缘侧，于是提供一种包括边缘云节点的网络系统，在该网络系统中，结合中心管控设备和边缘管控设备，可充分、全面地对边缘云节点进行管控，这为将云计算放到距离终端更近的边缘云节点中处理提供了条件，进而可借助边缘云节点中的资源为用户提供云计算服务，有利于降低服务响应时延，降低带宽成本。

Description

网络系统、管控方法、设备及存储介质
本申请要求2019年04月08日递交的申请号为201910277460.1、发明名称为“网络系统、管控方法、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网技术领域，尤其涉及一种网络系统、管控方法、设备及存储介质。
背景技术
目前，对云计算的概念都是基于集中式的资源管控来提出的，即使采用多个数据中心互联互通形式，依然将所有的软硬件资源视为统一的资源进行管理，调度和售卖。随着5G、物联网时代的到来以及云计算应用的逐渐增加，终端侧对云资源在时延、带宽等性能上的要求越来越高，集中式的云网络已经无法满足终端侧日渐增高的云资源需求。
发明内容
本申请的多个方面提供一种网络系统、管控方法、设备及存储介质，用以降低服务的响应时延，降低带宽成本。
本申请实施例提供一种网络系统，包括：中心管控设备，边缘管控设备，以及至少一个边缘云节点；所述中心管控设备，用于接收所述边缘管控设备上报的针对所述至少一个边缘云节点的监控数据，并根据所述监控数据对所述至少一个边缘云节点进行管控；所述边缘管控设备，用于对所述至少一个边缘云节点进行监控并将监控数据上报给所述中心管控设备；以及在所述中心管控设备不对或无法对所述至少一个边缘云节点进行管控的情况下，自主地对所述至少一个边缘云节点进行管控。
本申请实施例还提供一种管控方法，包括：确定网络系统中的中心管控设备不对或无法对所述网络系统中至少一个边缘云节点进行管控；自主地对所述至少一个边缘云节点进行管控。
本申请实施例还提供一种管控方法，包括：对网络系统中的至少一个边缘云节点进行监控；将监控数据上报给所述网络系统中的中心管控设备，以供所述中心管控设备根据所述监控数据对所述至少一个边缘云节点进行管控。
本申请实施例还提供一种边缘管控设备，包括：存储器和处理器；所述存储器，用 于存储计算机程序；当所述计算机程序被所述处理器执行时，致使所述处理器实现本申请方法实施例中的步骤。
本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，当所述计算机程序被一个或多个处理器执行时，致使所述一个或多个处理器实现本申请方法实施例中的步骤。
在本申请实施例中，结合边缘计算的概念，考虑将云计算的能力放到距离终端侧更近的边缘侧，于是提供一种包括边缘云节点的网络系统，在该网络系统中，结合中心管控设备和边缘管控设备，可充分、全面地对边缘云节点进行管控，这为“将云计算放到距离终端更近的边缘云节点中处理”提供了条件，进而可借助边缘云节点中的资源为用户提供云计算服务，有利于降低响应时延，降低带宽成本。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1a为本申请示例性实施例提供的一种网络系统的结构示意图；
图1b为本申请示例性实施例提供的中心管控设备与边缘管控设备的一种结构示意图；
图1c为本申请示例性实施例提供的另一种网络系统的结构示意图；
图2a为本申请示例性实施例提供的一种管控方法的流程示意图；
图2b为本申请示例性实施例提供的另一种管控方法的流程示意图；
图3为本申请示例性实施例提供的一种中心管控设备的结构示意图；
图4为本申请示例性实施例提供的一种边缘管控设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
针对现有集中式的云网络已经无法满足终端侧日渐增高的云资源需求的技术问题，在本申请一些实施例中，结合边缘计算的概念，考虑将云计算的能力放到距离终端侧更 近的边缘侧，于是提供一种包括至少一个边缘云节点的网络系统，在该网络系统中，结合中心管控设备和边缘管控设备，可充分、全面地对边缘云节点进行管控，解决了边缘云节点的管控问题，这为“将云计算放到距离终端更近的边缘云节点中处理”提供了条件，进而可借助边缘云节点中的资源为用户提供云计算服务，有利于降低响应时延，降低带宽成本。
以下结合附图，详细说明本申请各实施例提供的技术方案。
图1a为本申请示例性实施例提供的一种网络系统的结构示意图。如图1a所示，该网络系统100包括：中心管控设备101，边缘管控设备103，以及至少一个边缘云节点102。
本实施例的网络系统100是基于云计算技术和边缘计算的能力，构筑在边缘基础设施之上的云计算平台，是一种边缘位置的具备计算、网络、存储以及安全等能力的云平台。
与中心云或者传统的云计算平台相对应，本实施例的网络系统100可以视为一种边缘云网络系统。边缘云是个相对概念，边缘云是指相对靠近终端的云计算平台，或者说，与中心云或者传统的云计算平台相区别，中心云或者传统的云计算平台可以包括资源规模化且位置集中的数据中心，而边缘云节点覆盖的网络范围更广泛，也因此具备距离终端更近的特性，单个边缘云节点的资源规模较小，但是边缘云节点的数量多，多个边缘云节点构成了本实施例中边缘云的组成部分。本实施例的终端是指云计算服务的需求端，例如可以是互联网中的终端或者用户端，或者物联网中的终端或用户端。边缘云网络是基于中心云或者传统的云计算系统与终端之间的基础设施构建的网络。其中，网络系统100包括至少一个边缘云节点102，每个边缘云节点102包括一系列的边缘基础设施，这些边缘基础设施包括但不限于：分布式数据中心(DC)、无线机房或集群，运营商的通信网络、核心网设备、基站、边缘网关、家庭网关、计算设备和/或存储设备等边缘设备及对应的网络环境等等。在此说明，不同边缘云节点102的位置、能力以及包含的基础设施可以相同，也可以不相同。
其中，本实施例的网络系统100与中心云或传统的云计算平台等中心网络、终端结合可形成“云边端三体协同”的网络架构，在该网络架构中，可以将网络转发、存储、计算和/或智能化数据分析等任务放在网络系统100中的各边缘云节点102中处理，由于各边缘云节点102更靠近终端，因此可以降低响应时延，减轻中心云或传统的云计算平台的压力，降低带宽成本。
如何合理地调度多个边缘云节点资源，以及如何管控好多个边缘云节点以正确和稳定的逻辑进行云计算服务，是一个重要的挑战。在本实施例的网络系统100中，部署有中心管控设备101，中心管控设备101可以以边缘云节点102为管控对象，在资源调度，镜像管理，实例管控，运维，网络，安全等各方面对网络系统100中的至少一个边缘云节点102进行管控，从而将云计算服务放到各边缘云节点102中处理。在部署实施上，中心管控设备101可以部署在一个或多个云计算数据中心中，或者，可以部署在一个或多个传统数据中心中，中心管控设备101也可以和其管控的至少一个边缘云节点共同构成边缘云网络，本实施例对此不做限定。
对一个边缘云节点102来说，可以对外提供各种资源，例如CPU、GPU等计算资源，内存、硬盘等存储资源，带宽等网络资源等。另外，边缘云节点102还可以根据镜像创建相应实例，通过实例对外提供各种服务。其中，镜像是在边缘云节点中创建的实例所需的基础文件，例如可以是为用户提供云计算服务所需的操作系统、应用、或操作配置等镜像文件，其可以是符合边缘云节点计算部署要求，特定的一系列文件按照一定的格式制作成的文件。另外，镜像的形态是多样的，可以是虚拟机(Virtual Machine，VM)镜像文件、容器(Docker)镜像文件、各类型的应用打包文件等，镜像形态可以与云计算服务需要使用的虚拟化技术有关，本实施例对此不做限定。与镜像对应，实例的实现形态可以是虚拟机、容器或应用程序等。
在本实施例中，中心管控设备101可以单独根据资源需求对至少一个边缘云节点102进行资源调度，也可以单独根据镜像需求针对至少一个边缘云节点102进行镜像的管理和分发，当然，也可以根据服务需求既对至少一个边缘云节点102进行资源调度，又为至少一个边缘云节点102提供镜像。其中，服务需求包括了资源需求和镜像需求。例如，中心管控设备101可以对外提供需求提交入口，该需求提交入口可以是web页面、应用页面或命令窗等。该需求提交入口的作用是供需求方向中心管控设备101提交自己的需求描述信息。
对于资源需求方，可以通过上述需求提交入口向中心管控设备101提交资源需求描述信息，该资源需求描述信息包括：边缘云节点选择参数和资源选择参数；边缘云节点选择参数包括调度域和/或对边缘云节点的性能要求等，资源选择参数包括资源类型、资源数量以及对资源设备的性能要求等。中心管控设备101可根据资源需求描述信息，对至少一个边缘云节点进行资源调度。可选地，一种资源调度方式包括：中心管控设备101根据资源需求描述信息，从网络系统100的至少一个边缘云节点102中确定被调度的目 标边缘云节点以及目标边缘云节点中被调度的资源信息；根据该资源信息控制目标边缘云节点中相应资源设备进行资源分配或预留。
对于镜像需求方，可以通过上述需求提交入口向中心管控设备101提交镜像需求描述信息，该镜像需求描述信息可指向需要使用的镜像，可以是镜像本身，也可以是镜像的名称、ID等标识类信息，还可以是一些对云计算服务的功能进行描述的信息，这些信息可以反映出所需的镜像。中心管控设备101可根据镜像需求描述信息，确定需要向第一边缘云节点提供的目标镜像；并为第一边缘云节点提供该目标镜像，以供第一边缘云节点根据该镜像创建相应实例以提供相应的云计算服务。其中，第一边缘云节点可以是网络系统100中任一边缘云节点。为了便于描述和区分，将需要向第一边缘云节点提供的镜像称为目标镜像。
对服务需求方，可以通过上述需求提交入口向中心管控设备101提交服务需求描述信息，该服务需求描述信息包括资源需求描述信息和镜像需求描述信息。关于资源需求描述信息和镜像需求描述信息可参见前面的描述，在此不再赘述。值得的说明的是，服务需求描述信息中的资源需求描述信息和镜像需求描述信息可以是一并提交，也可以分开提交。中心管控设备101可根据服务需求描述信息，对网络系统100中至少一个边缘云节点102进行资源调度；为至少一个边缘云节点102中被调度的资源提供镜像，以利用至少一个边缘云节点中被调度的资源提供云计算服务。
关于上述资源调度的过程以及镜像管理和分发过程的详细描述，可参见下述实施例，在此暂不详述。
值得说明的是，在网络系统100中，中心管控设备101可以直接对至少一个边缘云节点102进行管控和调度，但并不限于此。如图1a所示，在网络系统100中，除了包括中心管控设备101和至少一个边缘云节点102之外，还包括边缘管控设备103。其中，边缘管控设备103的数量可以是一个，也可以是多个。另外，边缘管控设备103可以部署在一个或多个边缘云节点102中。在一可选实施例中，如图1a所示，每个边缘云节点102中分别部署边缘管控设备103。进一步，每个边缘云节点包括一台或多台资源设备，可选地，边缘管控设备103可集中部署在一台资源设备上，也可以分散部署在多台资源设备上。另外，每个边缘云节点除了包括资源设备之外，还可以包括一台或多台专有设备，可选地，边缘管控设备103也可以集中部署在一台专有设备上，或分散部署在多台专有设备上。其中，专有设备是指用来部署边缘管控设备103的物理设备，不同于资源设备。此外，边缘管控设备103也可以与中心管控设备101部署在一起，在此不作限定。 其中，中心管控设备101可以部署在一个或多个云计算数据中心或传统数据中心中，也可以和至少一个边缘云节点一起部署在边缘云网络中。
在本实施例中，边缘管控设备103可辅助、配合中心管控设备101对至少一个边缘云节点102进行管控和调度。在边缘管控设备103的协助下，中心管控设备101可以更加方便、高效地对至少一个边缘云节点102进行管控和调度，进而达到充分利用边缘资源的目的。
在此说明，本实施例的中心管控设备101可以是一台具有资源调度、镜像管理以及运维管理等能力的逻辑设备，这些功能可以部署一台物理机或虚拟机上实现，也可以分散性地部署在多台物理机或虚拟机上。当然，本实施例的中心管控设备也可以是一台或多台具有资源调度和镜像管理等能力的物理设备。本申请实施例并不限定中心管控设备101的实现结构，凡是具有上述能力的设备结构均适用于本申请实施例。
与中心管控设备101相类似，边缘管控设备103也可以是一台逻辑设备，其具有的能力可以部署一台物理机(例如边缘云节点中的资源设备或专有设备)或虚拟机上实现，也可以分散性地部署在多台物理机(例如边缘云节点中的资源设备或专有设备)或虚拟机上。当然，边缘管控设备也可以是一台或多台具有相应能力的物理设备。本申请实施例并不限定边缘管控设备103的实现结构，凡是具有相应能力的设备结构均适用于本申请实施例。
在本申请实施例中，中心管控设备101与边缘管控设备103之间建立安全、加密的通信通道，并基于该通信通道进行交互。该通信通道包括控制接口和数据接口，则中心管控设备101基于控制接口和数据接口与边缘管控设备103进行控制面和数据面的交互，完成对边缘云节点102的调度和管控。其中，数据接口用于在中心管控设备101与边缘管控设备103之间进行数据传输。控制接口具备但不限于以下功能：
1、资源调度能力：中心管控设备101通过具有资源调度能力的控制接口(可简称为资源调度接口)可从多个维度对边缘云节点进行资源调度，边缘云节点是中心管控设备101进行资源调度的对象；
2、镜像管理和分发能力：中心管控设备101通过具有镜像管理和分发能力的控制接口(简称为镜像管理接口)可将镜像提供给边缘云节点，这样，边缘云节点可根据收到的镜像创建相应实例，通过实例提供云计算服务；
3、运维管理能力：中心管控设备101通过具有运维管理能力的控制接口(简称为运维管理接口)对边缘云节点进行运维管理，运维管理包括但不限于：管控边缘云节点中 的应用、虚拟化软件等，监控实例的状态、资源使用量以及基础设施等。
与上述控制接口具有的能力相对应，本实施例的中心管控设备101具有但不限于以下功能：
1、可根据服务需求描述信息，例如服务的规格、需要部署服务的区域、运营商网络的分布、网络时延、负载情况、带宽成本、需要的资源类型和/或资源设备的性能要求等，对边缘云节点进行资源调度；
2、可获取云计算服务所需的镜像，将镜像提供给边缘云节点中相应资源设备进行配置安装，以供相应资源设备创建相应实例来提供云计算服务；
3、可对边缘云节点进行管控，包括但不限于：对边缘云节点中应用、虚拟化组件、实例的状态、资源用量和/或基础设施情况等进行管控，实现远程运维、日志管理等。
除上述功能之外，中心管控设备也可以具有其它一些功能，例如安全保障功能，涉及对中心管控设备的安全、中心管控设备与边缘管控设备之间以及边缘云节点之间的链路安全、边缘云节点的安全；负责维护网络系统中组网信息等。
下面对中心管控设备101与边缘管控设备103协同工作的过程进行说明：
在网络系统100中，至少一个边缘云节点102可形成资源池，每个边缘云节点102作为调度对象，在中心管控设备101的调度下对外提供各种资源或云计算服务。其中，中心管控设备101与边缘管控设备102相互配合，可以单独对至少一个边缘云节点102进行资源调度，也可以单独针对至少一个边缘云节点102进行镜像的管理和分发，当然，也可以既对至少一个边缘云节点102进行资源调度，又为至少一个边缘云节点102提供镜像。除了针对边缘云节点102进行资源调度和镜像管理和分发之外，在其它方面对边缘云节点102的管控也是网络系统100需要解决的一个问题，成功地解决该问题也是“将云计算放到距离终端更近的边缘云节点中处理”的基础。为此，中心管控设备101与边缘管控设备102相互配合，还可以在其它方面对至少一个边缘云节点102进行管控。
在本申请下述实施例中，将对中心管控设备101或者中心管控设备101与边缘管控设备103配合所实现的各种功能展开描述。
管控功能：
在本申请实施例中，中心管控设备可以在边缘管控设备的协助下，对至少一个边缘云节点进行管控。详细地，边缘管控设备可以对至少一个边缘云节点进行监控并将监控数据上报给中心管控设备，供中心管控设备根据监控数据对至少一个边缘云节点进行管控。中心管控设备可以根据边缘管控设备上报的监控数据对至少一个边缘云节点进行管 控。可选地，对边缘管控设备来说，可在中心管控设备的控制下，对至少一个边缘云节点进行监控并将监控数据上报给中心管控设备。或者，边缘管控设备可以根据定时任务，周期性地对至少一个边缘云节点进行监控并将监控数据上报给中心管控设备。无论是在哪种实施方式中，边缘管控设备主要发挥监控、数据采集、上报等功能，而管控决策由中心管控设备决定。
其中，中心管控设备控制边缘管控设备对至少一个边缘云节点进行监控，可以采用但不限于以下可选实施方式：
在一可选实施方式中，中心管控设备可以向边缘管控设备发送第一类监控指令，以指示边缘管控设备从至少一个监控维度对至少一个边缘云节点进行监控并将至少一个监控维度上的监控数据上报给中心管控设备。第一类监控指令是一种指示边缘管控设备从至少一个监控维度对至少一个边缘云节点进行监控并上报至少一个监控维度上的监控数据的监控指令。对边缘管控设备来说，可以接收中心管控设备发送的第一类监控指令，根据第一类监控指令，从至少一个监控维度上对至少一个边缘云节点进行监控，并将至少一个监控维度上的监控数据上报给中心管控设备。中心管控设备根据边缘管控设备上报的至少一个监控维度上的监控数据对至少一个边缘云节点进行管控。值得说明的是，至少一个监控维度可根据应用需求灵活设定，并预置到边缘管控设备和中心管控设备中。关于监控维度的举例参见后续实施例。
在另一可选实施方式中，中心管控设备可以有选择地在某个或某些监控维度上对至少一个边缘云节点进行管控。基于此，中心管控设备可以向边缘管控设备发送第二类监控指令，第二类监控指令与指定监控维度对应，用于指示边缘管控设备在指定监控维度上对至少一个边缘云节点进行监控并上报指定监控维度上的监控数据。对边缘管控设备来说，可接收中心管控设备发送的第二类监控指令，根据第二类监控指令在指定监控维度上对至少一个边缘云节点进行监控，并将指定监控维度上的监控数据上报给中心管控设备，以供中心管控设备根据指定监控维度上的监控数据对至少一个边缘云节点进行管控。中心管控设备还用于接收边缘管控设备发送的指定监控维度上的监控数据，根据指定监控维度上的监控数据对至少一个边缘云节点进行管控。
值得说明的是，指定监控维度可以是一个，也可以是多个。在指定监控维度是多个的情况下，每个指定监控维度可以对应一个第二类监控指令，即中心管控设备可以向边缘管控设备发送多个第二类监控指令，每个第二类监控指令对应一个指定监控维度。或者，在指定运维为度为多个的情况，多个指定监控维度也可以对应同一个第二类监控指 令，即中心管控设备可以向边缘管控设备发送一个第二类监控指令，该第二类监控指令对应多个指定监控维度。
可选地，边缘管控设备根据定时任务，周期性地对至少一个边缘云节点进行监控可以是根据定时任务，周期性地从至少一个监控维度对至少一个边缘云节点进行监控；进一步，可以将至少一个监控维度上的监控数据上报给中心管控设备。其中，不同监控维度上的监控周期可以相同，也可以不相同。例如，边缘管控设备可以每隔10分钟对边缘云节点进行一次安全漏洞扫描，或者每隔5分钟对边缘云节点进行流量监控。
上述至少一个监控维度或指定监控维度可以包括但不限于以下维度：处于运行态的对象维度，日志维度，安全维度，资源维度等。进一步，处于运行态的对象维度可包括对象的运行状态维度和/或对象的生命周期维度；安全维度可包括：流量攻击维度和/或安全漏洞维度。
结合上述列举的几个监控维度，中心管控设备在边缘管控设备协助下，对至少一个边缘云节点进行管控包括但不限于以下至少一种管控示例：
管控示例1：中心管控设备控制边缘管控设备对至少一个边缘云节点中处于运行态的对象进行状态监控。其中，控制方式包括向边缘管控设备发送第一类监控指令或发送与对象的运行状态维度对应的第二类监控指令。边缘管控设备在中心管控设备的控制下，或者，根据定时任务周期性地，对至少一个边缘云节点中处于运行态的对象进行状态监控，将监控到的处于运行态的对象的运行状态上报给中心管控设备。中心管控设备从边缘管控设备上报的处于运行态的对象的运行状态中识别出运行状态异常的对象，为便于描述和区分，将运行状态异常的对象称为目标对象，并针对目标对象进行异常处理。其中，边缘云节点中处于运行态的对象包括但不限于：实例、镜像、容器、其它虚拟组件、物理机、CPU和/或硬盘等。根据处于运行态的对象的不同，运行状态异常情况也会有所不同。例如，对实例来说，可能的异常情况包括但不限于：中断、报错和/或故障等。又例如，对物理机来说，可能的异常情况包括但不限于：死机、黑屏、报警和/或物理机上运行的应用程序出现闪退等。根据目标对象以及运行状态异常情况的不同，异常处理方式也会有所不同，例如可以包括但不限于：报警，停止或重启目标对象，迁移，和/或删除并重建目标对象等。
管控示例2：中心管控设备控制边缘管控设备对至少一个边缘云节点中处于运行态的对象的生命周期进行监控。其中，控制方式包括向边缘管控设备发送第一类监控指令或发送与对象的生命周期维度对应的第二类监控指令。边缘管控设备在中心管控设备的 控制下，或者，根据定时任务周期性地，监控至少一个边缘云节点中处于运行态的对象的生命周期，并将监控到的处于运行态的对象的生命周期上报给中心管控设备。中心管控设备根据边缘管控设备上报的处于运行态的对象的生命周期，控制处于运行态的对象停止、停止后重启、迁移或删除。
管控示例3：中心管控设备控制边缘管控设备采集至少一个边缘云节点中的日志数据。其中，控制方式包括向边缘管控设备发送第一类监控指令或发送与日志维度对应的第二类监控指令。边缘管控设备在中心管控设备的控制下，或者，根据定时任务周期性地，采集至少一个边缘云节点中的日志数据，并将采集到的日志数据上报给中心管控设备。中心管控设备接收边缘管控设备上报的日志数据，对日志数据进行数据分析，并根据数据分析结果执行后续动作，例如可以计费、风控和/或增减实例等。根据日志数据的不同，后续动作也会有所不同。可选地，日志数据可以包括但不限于：边缘云节点中各项性能、指标等数据，例如：实例的带宽流量、实例当前的运行情况、实例的IO负载、物理机的带宽流量、物理机当前的运行情况、物理机的IO负载、边缘管控设备的运行情况和/或其它虚拟化组件的运行情况等。
可选地，中心管控设备不仅可以收集边缘管控设备上报的各边缘云节点的日志数据，还具备数据巡检的能力，对于一些数据，若中心管控设备存储的与边缘云节点中的数据不一致，可以主动向该边缘云节点同步最新的数据，例如可以向边缘云节点同步最新版本的镜像等。
管控示例4：中心管控设备控制边缘管控设备对至少一个边缘云节点进行流量监控。其中，控制方式包括向边缘管控设备发送第一类监控指令或发送与流量攻击维度对应的第二类监控指令。边缘管控设备在中心管控设备的控制下，或者，根据定时任务周期性地，对至少一个边缘云节点进行流量监控，并将监控到的流量攻击事件上报给中心管控设备。中心管控设备对边缘云节点中出现的流量攻击事件进行阻断处理。可选地，边缘管控设备还可以将监控到的流量数据上报给中心管控设备，中心管控设备还可以根据流量数据对至少一个边缘云节点进行流量攻击防御等。
管控示例5：中心管控设备控制边缘管控设备对至少一个边缘云节点进行网络安全漏洞扫描。其中，控制方式包括向边缘管控设备发送第一类监控指令或发送与网络安全维度对应的第二类监控指令。边缘管控设备在中心管控设备的控制下，或者，根据定时任务周期性地，对至少一个边缘云节点进行网络安全漏洞扫描，并将扫描到的网络安全漏洞问题上报给中心管控设备。中心管控设备接收边缘管控设备上报的网络安全漏洞问 题，对该网络安全漏洞问题进行修复。
管控示例6：中心管控设备控制边缘管控设备监控至少一个边缘云节点中的资源用量。其中，控制方式包括向边缘管控设备发送第一类监控指令或发送与资源维度对应的第二类监控指令。边缘管控设备在中心管控设备的控制下，或者，根据定时任务周期性地，监控至少一个边缘云节点中的资源用量，并将监控到的资源用量信息上报给中心管控设备。中心管控设备根据边缘管控设备上报的资源用量信息，对至少一个边缘云节点进行资源扩容或减容。这里的资源包括各种资源信息，例如物理机等设备资源，存储资源，CPU、GPU等计算资源，带宽等网络资源等等。
进一步，若每个边缘云节点中均部署有边缘管控设备，则每个边缘管控设备可以在中心管控设备的控制下，或者，根据定时任务周期性地，对其所属边缘云节点进行监控并将其所属边缘云节点中的监控数据上报给中心管控设备。中心管控设备可以接收每个边缘云节点中的边缘管控设备上报的监控数据，根据每个边缘云节点中的监控数据对每个边缘云节点进行管控。
本申请实施例并不限定中心管控设备与边缘管控设备的实现结构。可选地，一种中心管控设备的结构框架如图1b所示，包括：资源调度管控模块、镜像管控模块以及中心管控模块；该中心管控模块进一步包括：中心监控单元、中心日志单元以及中心安全单元等。相应地，一种边缘管控设备的结构框架如图1b所示，包括：资源调度服务模块、镜像服务模块以及边缘管控模块；该边缘管控模块进一步包括：边缘监控单元、边缘日志单元以及边缘安全单元等。
其中，中心管控设备中的资源调度管控模块与边缘管控设备中的资源调度服务模块相互配合，可对边缘云节点进行资源调度，资源调度功能可参见下文中的描述。中心管控设备中的镜像管控模块与边缘管控设备中的镜像服务模块相互配合，可针对边缘云节点进行镜像的管理与分发等，镜像管理与分发功能可参见下文中的描述。
中心管控设备中的中心管控模块与边缘管控设备中的边缘管控模块相互配合，可对边缘云节点进行管控。上述管控示例1-6可由图1b所示中心管控模块和边缘管控模块中的相应单元配合实施。管控示例3可由中心管控模块中的中心日志单元和边缘管控模块中的边缘日志单元配合实现。详细地，中心日志单元向边缘日志单元发送第一类监控指令或发送与日志维度对应的第二类监控指令；边缘日志单元根据第一类或第二类监控指令采集边缘云节点中的日志数据并上报给中心日志单元；中心日志单元对日志数据进行数据分析，并根据数据分析结果执行后续动作。管控示例4和5，可由中心管控模块中 的中心安全单元和边缘管控模块中的边缘安全单元配合实现。详细地，中心安全单元向边缘安全单元发送第一类监控指令或发送与流量攻击或网络安全维度对应的第二类运维指令；边缘安全单元可以根据第一类或第二类运维指令对边缘云节点进行流量监控或网络安全漏洞扫描，并将监控到的流量攻击事件或网络漏洞安全问题上报给中心安全单元；中心安全单元对流量攻击事件进行阻断或对网络安全漏洞问题进行修复。管控示例1、2和6，可由中心管控模块中的中心监控单元和边缘管控模块中的边缘监控单元配合实现，详细实施过程不做赘述。
由上述可知，在边缘管控设备的协助下，中心管控设备可以了解边缘云节点中各实例的健康、资源用量、日志数据和/或基础设施的情况，可实现远程运维、日志管理等。
在本申请实施例中，除了中心管控设备可以对至少一个边缘云节点进行管控之外，在中心管控设备不对边缘云节点进行管控或者无法对边缘云节点进行管控的情况下，边缘管控设备可以自主地对至少一个边缘云节点进行管控。
例如，边缘管控设备可以监控其与中心管控设备之间的连接情况，在与中心管控设备失去连接的情况下，可以确定中心管控设备无法对边缘云节点进行管控，则可以自主地从至少一个监控维度对至少一个边缘云节点进行管控。
又例如，在中心管控设备通过向边缘管控设备发送第一类监控指令，以控制边缘管控设备对至少一个边缘云节点进行监控的方式下，边缘管控设备可以等待接收中心管控设备发送的第一类监控指令，若未接收到中心管控设备发送的第一类监控指令，可以确定中心管控设备不对或无法对至少一个边缘云节点进行管控，则可以自主地从至少一个监控维度对至少一个边缘云节点进行管控。可选地，边缘管控设备和中心管控设备可以预先约定第一类监控指令的等待时长，若超过了所述等待时长仍未接收到中心管控设备发送的第一类监控指令，则确定未接收到中心管控设备发送的第一类监控指令。
又例如，在中心管控设备通过向边缘管控设备发送与指定监控维度对应的第二类监控指令，以控制边缘管控设备从指定监控维度对至少一个边缘云节点进行监控的方式下，边缘管控设备可以等待接收中心管控设备发送的第二类监控指令，若在指定监控维度上未接收到中心管控设备发送的第二类监控指令，可以确定中心管控设备在指定监控维度上不对或无法对至少一个边缘云节点进行管控，则可以自主地从指定监控维度对至少一个边缘云节点进行管控。
进一步可选地，若边缘管控设备在与中心管控设备失去连接的情况下，自主地从至少一个监控维度对至少一个边缘云节点进行管控，则在与中心管控设备恢复连接后，还 可以将失去连接期间的管控数据同步给中心管控设备。值得说明的是，管控数据主要包括管控的策略、方式、效果等数据，当然，也可以包括监控数据。
上述至少一个监控维度或指定监控维度可以包括但不限于以下几个维度：处于运行态的对象维度，日志维度，安全维度，资源维度等。进一步，处于运行态的对象维度可包括对象的运行状态维度和/或对象的生命周期维度；安全维度可包括：流量攻击维度和/或安全漏洞维度。
结合上述列举的几个监控维度，边缘管控设备自主地对至少一个边缘云节点进行管控包括但不限于以下至少一种管控示例：
管控示例a：自主地对至少一个边缘云节点中处于运行态的对象进行状态监控，并针对监控到的运行状态异常的目标对象进行异常处理。关于处于运行态的对象以及运行状态异常情况等，可参见上文中的描述，在此不再赘述。
可选地，在示例a中，边缘管控设备在针对目标对象进行异常处理时，具体用于：对目标对象的异常运行状态进行分析，根据分析结果确定至少一种候选处理方式；从至少一种候选处理方式中获取目标处理方式，根据目标处理方式对目标对象进行异常处理。
更进一步，边缘管控设备在获取目标处理方式时，具体用于：在边缘管控设备与中心管控设备保持连接的情况下，将至少一种候选处理方式上报给中心管控设备，以供中心管控设备从中选择处理方式；接收中心管控设备返回的处理方式作为目标处理方式；或者，在边缘管控设备与中心管控设备失去连接的情况下，输出至少一种候选处理方式至边缘管控人员，以供管控人员从中选择处理方式；响应于边缘管控人员的选择操作，确定被选择的处理方式作为目标处理方式；或者，在与中心管控设备失去连接的情况下，按照设定的选择策略，从至少一种候选处理方式中选择目标处理方式。
管控示例b、自主地监控至少一个边缘云节点中处于运行态的对象的生命周期，并根据监控结果控制处于运行态的对象停止、停止后重启或删除。对于容器或实例，可以控制容器或实例停止执行、停止后重启、或者将容器或实例删除等。
管控示例c：自主地采集至少一个边缘云节点中的日志数据，对日志数据进行数据分析，并根据数据分析结果执行后续动作。日志数据包括但不限于边缘云节点中实例的带宽流量、实例当前的运行情况、实例的IO负载、物理机的带宽流量、物理机当前的运行情况、物理机的IO负载、边缘管控设备的运行情况和/或其它虚拟化组件的运行情况等。可选地，根据日志数据的分析结果可以进行计费、风控和/或资源重分配等后续动作，但不限于此。
管控示例d、自主地对至少一个边缘云节点进行流量监控，并针对监控到的流量攻击事件进行阻断处理。
管控示例e：自主地对至少一个边缘云节点进行网络安全漏洞扫描，并针对扫描到的网络安全漏洞问题进行修复。
管控示例f：自主地监控至少一个边缘云节点中的资源用量，并根据监控结果对至少一个边缘云节点进行资源扩容或减容。这里的资源包括但不限于：物理机等设备资源，内存、磁盘等存储资源，CPU、GPU等计算资源，带宽等网络资源。对这些资源来说，用量较高时，可以针对这些资源进行扩容，用量较低时，可以针对这些资源进行减容。
进一步，若每个边缘云节点中均部署有边缘管控设备，则每个边缘管控设备可以在中心管控设备不对或无法对其所属边缘云节点进行管控的情况下，自主地对其所属边缘云节点进行管控。
可选地，在上述边缘管控设备自主地对至少一个边缘云节点进行管控的示例a-示例e中，边缘管控设备可以根据定时任务，周期性地对至少一个边缘云节点进行管控。例如，在示例d中，边缘管控设备可以根据定时任务，每隔10分钟对至少一个边缘云节点进行流量监控，并针对监控到的流量攻击事件进行阻断处理。又例如，在示例e中，边缘管控设备可以根据定时任务，每隔5分钟对至少一个边缘云节点进行网络安全漏洞扫描，并针对扫描到的网络安全漏洞问题进行修复。当然，边缘管控设备也可以根据其它方式的自主策略，自主地对至少一个边缘云节点进行管控，例如可以在每天某个固定的时间点，自主地对至少一个边缘云节点进行管控。
在一些可选实施例中，上述管控可以是运维维度的管控。例如，中心管控设备可在边缘管控设备的协助下，对至少一个边缘云节点进行运维管控。在运维管控场景下，上述至少一个监控维度或指定监控维度可以是运维维度，则中心管控设备可以根据边缘管控设备上报的至少一个运维维度或指定运维维度上的监控数据，对至少一个边缘云节点进行运维管控。另外，在中心管控设备不对边缘云节点进行运维管控或者无法对边缘云节点进行运维管控的情况下，边缘管控设备可以自主地对至少一个边缘云节点进行运维管控。例如，边缘管控设备可以根据监控到的至少一个运维维度或指定运维维度上的监控数据，对至少一个边缘云节点进行运维管控。关于中心管控设备或边缘管控设备对至少一个边缘云节点进行运维管控的详细内容可参见前述实施例，在此不再赘述。
在运维管控场景下，结合上述示例1-6以及示例a-f可知，在本实施例中，中心管控设备与边缘管控设备相结合，中心管控设备可在边缘管控设备的协助下对至少一个边缘 云节点进行运维管控，除此之外，边缘管控设备也具备一定的自行运维管控的能力，可以在中心管控设备不对或无法对边缘云节点进行运维管控的情况下，自主地对边缘云节点进行运维管控，实现两级运维管控，可以更加充分、全面地对边缘云节点进行运维管控，为“将云计算放到距离终端更近的边缘云节点中处理”提供了条件，进而可借助边缘云节点中的资源为用户提供云计算服务，有利于降低响应时延，减轻中心云或传统云计算平台的压力，降低带宽成本。
资源调度功能：
中心管控设备可对至少一个边缘云进行资源调度，主要是指根据服务需求描述信息，从网络系统100中的至少一个边缘云节点102中确定可被调度的目标边缘云节点及目标边缘云节点中被调度的资源信息；将该资源信息发送给边缘管控设备103，以供边缘管控设备103控制目标边缘云节点中相应资源设备进行资源分配或预留。可选地，目标边缘云节点的数量可以由用户指定，也可以由资源中心管控设备根据服务需求描述信息自主确定，可以是一个，也可以是多个。服务需求描述信息可以由服务需求方直接提交，也可以是从服务需求方提交的服务相关的信息中提取或计算得到的。服务需求方可以是用户，也可以是应用、物理机或需要某一服务的另一服务等。
这里所描述的资源调度功能主要包括边缘云节点的选择和边缘云节点内的资源调度两个方面，但不限于这两个方面。其中，边缘云节点内部的资源调度具体体现为确定目标边缘云节点中被调度的资源信息和提供资源信息的操作，主要目的是在每一个边缘云节点的粒度上把云计算服务分配到最终的基础资源，例如服务器等资源设备上。其中，中心管控设备可维护各边缘云节点包含的资源的信息，作为资源调度的基础。
可选地，服务需求描述信息中包括边缘云节点选择参数和资源选择参数。边缘云节点选择参数是指选择目标边缘云节点所需的参数；资源选择参数是指选择边缘云节点内被调度的资源所需的信息。基于此，中心管控设备可以从服务需求描述信息中解析出边缘云节点选择参数和资源选择参数；根据边缘云节点选择参数从至少一个边缘云节点中确定被调度的目标边缘云节点，并根据资源选择参数确定目标边缘云节点中被调度的资源信息。
例如，服务需求描述信息中可以包括调度域和/或云计算服务的QoS要求，这些参数可以作为边缘云节点选择参数。其中，调度域指向需要部署云计算服务的区域，这决定了应该被调度的边缘云节点的地理位置。云计算服务的QoS要求可以包括云计算服务对 网络时延、负载情况和/或带宽成本等的要求。基于此，中心管控设备可以根据调度域和/或云计算服务的QoS要求，结合至少一个边缘云节点的地理位置和资源剩余量，选择能够满足调度域和/或QoS要求的边缘云节点作为目标边缘云节点。
例如，中心管控设备可以根据调度域，结合至少一个边缘云节点的地理位置，选择调度域指向的边缘云节点作为目标边缘云节点。或者，中心管控设备还可以根据云计算服务的QoS要求，例如网络时延、负载情况和/或带宽成本等要求，从边缘云节点中选择满足网络时延、负载情况和/或带宽成本要求的边缘云节点作为目标边缘云节点。当然，中心管控设备也可以同时根据调度域和云计算服务的QoS要求，结合至少一个边缘云节点的地理位置和资源剩余量，选择能够同时满足调度域和QoS要求的边缘云节点作为目标边缘云节点。
服务需求描述信息中除了包含调度域和/或云计算服务的QoS要求这些信息之外，还可以包括云计算服务所需的资源类型、资源数量和/或资源设备的性能等参数，这些参数可以作为资源选择参数。基于此，中心管控设备在确定目标边缘云节点之后，可以根据资源选择参数确定目标边缘云节点中被调度的资源信息。这里的资源信息可以包括：资源类型、资源数量和/或对资源设备的性能要求等信息，便于边缘管控设备据此控制目标边缘云节点中相应资源设备进行资源分配或预留。例如，资源类型可以包括但不限于：CPU、GPU等计算资源，内存、硬盘等存储资源，带宽资源等资源类型。以CPU资源为例，资源数量可以是12个CPU、24个CPU等，以内存资源为例，资源数量可以是16G内存、32G内存等；以带宽资源为例，资源数量可以是1M带宽，10M带宽等。
可选地，中心管控设备还可以具有算力编排的功能，算力编排是面向相对复杂一些的应用场景，将多个云计算服务绑定在一起作为最小的资源需求单元，这样，在资源调度过程中，可将绑定在一起的多个云计算服务作为整体，为它们选择同一个或几个边缘云节点，由同一个或几个边缘云节点为它们共同提供资源。算力编排完善了资源调度的多样性，增加了资源调度的灵活性，但未对资源调度的整体流程产生影响。
结合图1b所示中心管控设备和边缘管控设备的实现结构，上述资源调度功能可由资源调度管控模块和资源调度服务模块配合实现，详细过程不再赘述。
镜像管理与分发功能：
中心管控设备的镜像管理功能，主要是指对镜像进行管理，并为边缘云节点提供所需的镜像。这样，边缘云节点可根据镜像在相应资源设备上创建实例，进而由所创建的 实例为用户提供所需的云计算服务。
在实际应用中，需要为边缘云节点提供镜像的场景是多种多样的。例如，在用户(例如服务需求方)提交服务需求描述信息的情况下，中心管控设备可以为被调度的目标边缘云节点提供相应镜像。又例如，在边缘云节点上已有实例为用户提供云计算服务的情况下，用户需要进行业务扩容时，可以向中心管控设备提交扩容需求，为了实现扩容目的，需要为目前正为用户提供云计算服务的边缘云节点提供相应镜像，以便该边缘云节点基于镜像创建新的实例，从而达到扩容的目的。为便于描述和区分，在下面描述中，将需要为其提供镜像的边缘云节点记为第一边缘云节点，第一边缘云节点可以是网络系统中的任一边缘云节点，具体视应用场景而定。下面以中心管控设备为第一边缘云节点提供镜像为例，对中心管控设备的镜像管理功能进行说明。
在需要为第一边缘云节点提供镜像时，中心管控设备可以先确定需要向第一边缘云节点提供的目标镜像；然后，为第一边缘云节点提供目标镜像，以供第一边缘云节点利用目标镜像提供云计算服务。
在本实施例的网络系统100中，维护有镜像库，该镜像库用于存储系统中的镜像。用户可以选择使用镜像库中的镜像。例如，可以向用户提供一个镜像配置界面，该界面上设有下拉菜单，下拉菜单包括很多可供用户选择的镜像，用户可以选择自己使用的镜像。基于此，在需要为第一边缘云节点提供镜像时，中心管控设备可以从镜像库中获取第一边缘云节点所需的镜像，然后将镜像提供给第一边缘云节点，并将镜像的使用权限开放给相应用户。可选地，中心管控设备可以直接将目标镜像下发给第一边缘云节点，也可以指示第一边缘云节点到指定存储位置下载目标镜像。
除此之外，中心管控设备还可以维护已下发镜像与已下发镜像所在边缘云节点的对应关系。该对应关系中可以包括已下发镜像的标识信息与已发下镜像所在边缘云节点的标识信息。已下发镜像是指中心管控设备已经提供(例如下发)给某个或某些边缘云节点的镜像；已下发镜像所在边缘云节点是指已下发镜像被提供给的边缘云节点。同一镜像可能被提供(例如下发)给一个边缘云节点，也可能被提供(例如下发)给多个边缘云节点。
基于所维护的已下发镜像与已下发镜像所在边缘云节点的对应关系，在需要为第一边缘云节点提供镜像时，中心管控设备还可以控制第一边缘云节点从已经具有该镜像的其它边缘云节点获取该镜像，无需直接向第一边缘云节点提供镜像，一定程度上可以减轻中心管控设备的处理负担，在控制合理的情况下，还可以提高镜像的获取效率。
详细地，在需要为第一边缘云节点提供镜像时，中心管控设备可以确定需要向第一边缘云节点提供的镜像，为了便于描述和区分，在本申请实施例中，将需要向第一边缘云节点提供的镜像记为目标镜像；根据目标镜像的信息，在所维护的已下发镜像与已下发镜像所在边缘云节点的对应关系中进行匹配；若在该对应关系中匹配到与目标镜像对应的第二边缘云节点，这说明该目标镜像已经被提供给第二边缘云节点，则可以将第二边缘云节点处的目标镜像提供给第一边缘云节点；其中，第二边缘云节点也可以网络系统中的边缘云节点，其数量可以是一个，也可以是多个。对第一边缘云节点来说，可在中心管控设备101的控制下，获取第二边缘云节点处的目标镜像。
在此说明，在网络系统100包括边缘管控设备103的情况下，中心管控设备具体可以将第二边缘云节点与目标镜像的信息发送给边缘管控设备；边缘管控设备103根据第二边缘云节点与目标镜像的信息，将第二边缘云节点处的目标镜像提供给第一边缘云节点中的相应资源设备，供相应资源设备根据目标镜像创建可提供云计算服务的实例，进而为服务需求方提供该云计算服务。其中，第二边缘云节点的信息可以是任何能够标识第二边缘云节点的信息，例如可以是第二边缘云节点的ID、名称或地理位置等信息。目标镜像的信息可以是任何能够标识目标镜像的信息，例如可以是目标镜像的ID、名称或编号等。
进一步，在第一边缘云节点和第二边缘云节点中均部署有边缘管控设备103的情况下，则中心管控设备101具体可以将第二边缘云节点与目标镜像的信息发送给第一边缘云节点中的边缘管控设备，供第一边缘云节点中的边缘管控设备通过其与第二边缘云节点中的边缘管控设备之间的通信通道从第二边缘云节点处获取目标镜像并提供给第一边缘云节点中的相应资源设备。对第一边缘云节点中的边缘管控设备103来说，可接收中心管控设备101发送的第二边缘云节点和目标镜像的信息，根据第二边缘云节点与目标镜像的信息，通过其与第二边缘云节点中的边缘管控设备之间的通信通道，从第二边缘云节点处获取目标镜像，将目标镜像提供给第一边缘云节点中相应资源设备，供相应资源设备根据目标镜像创建可提供云计算服务的实例，进而提供云计算服务。
更进一步，第一边缘云节点中的边缘管控设备103通过其与第二边缘云节点中的边缘管控设备之间的通信通道，从第二边缘云节点获取目标镜像的一种过程包括：第一边缘云节点中的边缘管控设备103通过其与第二边缘云节点中的边缘管控设备之间的通信通道，向第二边缘云节点中的边缘管控设备103发送获取目标镜像的请求，该请求中携带有目标镜像的信息。第二边缘云节点中的边缘管控设备103接收该请求，根据该请求 中携带的目标镜像的信息，判断第二边缘云节点中是否存在目标镜像，在第二边缘云节点中存在目标镜像的情况下，通过其与第一边缘云节点中边缘管控设备103之间的通信通道，将目标镜像返回给第一边缘云节点中的边缘管控设备103，或者，将目标镜像在第二边缘云节点中的存储地址返回给第一边缘云节点中的边缘管控设备103。第一边缘云节点中的边缘管控设备103接收第二边缘云节点中的边缘管控设备103返回的目标镜像，或者接收第二边缘云节点中的边缘管控设备103返回的目标镜像在第二边缘云节点中的存储地址，根据该存储地址读取或下载目标镜像。
值得说明的是，第一边缘云节点中的边缘管控设备103与第二边缘云节点中的边缘管控设备103可以自行建立通信通道，也可以在中心管控设备101的控制下建立通道。可选地，中心管控设备还可以控制不同边缘管控设备之间建立通信通道，并负责维护边缘管控设备之间已有通信通道的信息，例如可以维护哪些边缘管控设备之间已经建立通信通道，通信通道何时建立，通信通道的状态，保持时长等信息。基于此，中心管控设备在确定目标镜像已经被提供给第二边缘云节点之后，且在将第二边缘云节点和目标镜像的信息提供给第一边缘云节点中的边缘管控设备之前，还可以根据所维护的边缘管控设备之间已有通信通道的信息，判断第一边缘云节点中的边缘管控设备与第二边缘云节点中的边缘管控设备之间是否已经存在通信通道；若判断结果为否，即第一边缘云节点中的边缘管控设备与第二边缘云节点中的边缘管控设备之间尚不存在通信通道，则可以控制第一边缘云节点中的边缘管控设备和第二边缘云节点中的边缘管控设备建立通信通道，以便于第一边缘云节点中的边缘管控设备能够通过该通信通道从第二边缘云节点处获取目标镜像。并且，在第一边缘云节点中的边缘管控设备与第二边缘云节点中的边缘管控设备建立通信通道之后，中心管控设备将第二边缘云节点和目标镜像的信息提供给第一边缘云节点中的边缘管控设备。当然，若判断结果为是，即第一边缘云节点中的边缘管控设备与第二边缘云节点中的边缘管控设备之间已经存在通信通道，则可以直接将第二边缘云节点和目标镜像的信息提供给第一边缘云节点中的边缘管控设备。
值得说明的是，中心管控设备也可以在将第二边缘云节点和目标镜像的信息提供给第一边缘云节点中的边缘管控设备之后，根据所维护的边缘管控设备之间已有通信通道的信息，判断第一边缘云节点中的边缘管控设备与第二边缘云节点中的边缘管控设备之间是否已经存在通信通道；若判断结果为否，即第一边缘云节点中的边缘管控设备与第二边缘云节点中的边缘管控设备之间尚不存在通信通道，则可以控制第一边缘云节点中的边缘管控设备和第二边缘云节点中的边缘管控设备建立通信通道，以便于第一边缘云 节点中的边缘管控设备能够通过该通信通道从第二边缘云节点处获取目标镜像。
在一些可选实施例中，为了保证第一边缘云节点获取目标镜像的效率，中心管控设备在将第二边缘云节点处的目标镜像提供给第一边缘云节点之前，还可以根据第二边缘云节点的属性，判断第二边缘云节点是否适合为第一边缘云节点提供目标镜像；若判断结果为是，即第二边缘云节点适合为第一边缘云节点提供目标镜像，则可以将第二边缘云节点处的目标镜像提供给第一边缘云节点；若判断结果为否，则可以从镜像库中获取目标镜像并将目标镜像提供给第一边缘云节点。
值得说明的是，根据应用场景和应用需求的不同，可以结合第二边缘云节点的不同属性，从不同角度判断第二边缘云节点是否适合为第一边缘云节点提供目标镜像。下面举例说明：
例如，可以结合第二边缘云节点所属的运营商，判断第二边缘云节点所属的运营商与第一边缘云节点所属的运营商是否相同；若判断结果为是，说明第二边缘云节点与第一边缘云节点是同运营商下的边缘云节点，两者可以进行数据传输，且数据传输速率相对于跨运营商的数据传输速率要快，适合为第一边缘云节点提供目标镜像。
又例如，可以结合第二边缘云节点的位置属性，判断第二边缘云节点到第一边缘云节点之间的距离是否小于设定的距离阈值；若判断结果为是，说明第二边缘云节点与第一边缘云节点相距较近，适合为第一边缘云节点提供目标镜像，这样由与第一边缘云节点相距较近的第二边缘云节点为第一边缘云节点提供镜像，便于第一边缘云节点快速获取到镜像，提高效率。第二边缘云节点到第一边缘云节点之间的距离可以是两个边缘云节点之间的平均距离，也可以是两个边缘云节点的中心之间的距离，还可以是两个边缘云节点相距最近的外边缘之间的距离等，可根据需求灵活定义。
又例如，可以结合第二边缘云节点的带宽属性，判断第二边缘云节点的可用带宽是否大于设定带宽阈值；若判断结果为是，说明第二边缘云节点的带宽资源比较充裕，适合为第一边缘云节点提供目标镜像，这样由带宽资源比较充裕的第二边缘云节点为第一边缘云节点提供镜像，可保证镜像的传输速率，便于第一边缘云节点快速获取到镜像，提高效率。
又例如，可以结合第二边缘云节点的负载属性，判断第二边缘云节点的负载量是否小于设定负载量阈值；若判断结果为是，说明第二边缘云节点的负载较轻，适合为第一边缘云节点提供目标镜像，这样由负载较轻的第二边缘云节点为第一边缘云节点提供镜 像，一方面可实现负载均衡，另一方面也便于第一边缘云节点快速获取到镜像，提高效率。
值得说明的是，上面列举的几种方式可以择一使用，也可以以任意组合方式组合使用，关于组合使用的情况，对此不做过多描述。
进一步，在第二边缘云节点为多个的情况下，可以结合第二边缘云节点的多个属性，对上述几种方式进行组合使用，进而从中选择出适合为第一边缘云节点提供目标镜像的第二边缘云节点。例如，若第二边缘云节点为多个，则可以结合多个第二边缘云节点所属的运营商，从多个第二边缘云节点中选择出与第一边缘云节点属于同一运营商的第二边缘云节点；进而，若选择出的第二边缘云节点仍为多个，则可以进一步根据选择出的第二边缘云节点的负载量，从中选择负载量最小或低于设定负载量阈值的第二边缘云节点，为第一边缘云节点提供目标镜像。
在一些可选实施例中，有可能已经向第一边缘云节点提供过目标镜像，例如，在业务扩容场景中，在目前正在为服务需求方提供云计算服务的边缘云节点中创建新实例需要使用的镜像与之前已有实例使用的镜像相同，如果该边缘云节点中还保存有之前已有实例使用的镜像，则可以不用重复为该边缘云节点提供镜像。针对这种情况，为了节约资源，中心管控设备在将第二边缘云节点处的目标镜像提供给第一边缘云节点之前，可以判断所维护的已下发镜像与已下发镜像所在边缘云节点的对应关系中是否包括第一边缘云节点；若判断结果为是，表明已经向第一边缘云节点提供过目标镜像，且第一边缘云节点中仍保存有目标镜像，则可以将目标镜像的信息提供给第一边缘云节点，供第一边缘云节点读取其中存储的目标镜像，无需再次传输目标镜像，这可节约传输目标镜像消耗的网络资源等；若判断结果为否，表明尚未向第一边缘云节点提供过目标镜像，或者第一边缘云节点中已经不存在目标镜像，则可以将第二边缘云节点处的目标镜像提供给第一边缘云节点。其中，在第一边缘云节点中部署有边缘管控设备的情况下，若中心管控设备判断出所维护的已下发镜像与已下发镜像所在边缘云节点的对应关系中包含目标镜像，可以将目标镜像的信息提供给第一边缘云节点中的边缘管控设备，第一边缘云节点中的边缘管控设备根据目标镜像的信息可以从第一边缘云节点中存储镜像的空间中获取目标镜像，将目标镜像提供给第一边缘云节点中的相应资源设备，以供相应资源设备根据目标镜像创建可提供云计算服务的实例。
进一步可选地，同一边缘云节点有可能为同一用户或不同用户提供多种云计算服务， 也就可能接收到多个镜像，这些镜像会被存储在边缘云节点中。边缘云节点可以提供一定存储空间，用来存储镜像。考虑到边缘云节点中镜像的存储空间有一定限制，为了能有足够的存储空间存储新接收的镜像，边缘云节点需要对本地存储的镜像进行淘汰处理。在本实施例中，中心管控设备负责为边缘云节点提供镜像的淘汰策略。中心管控设备可以生成镜像的淘汰策略，将该淘汰策略下发至各边缘云节点，各边缘云节点按照该淘汰策略对所存储的镜像进行淘汰处理。其中，在网络系统中包括边缘管控设备的情况下，中心管控设备可以将淘汰策略下发至边缘管控设备，由边缘管控设备根据淘汰策略对各边缘云节点中存储的镜像进行淘汰处理。进一步，在每个边缘云节点中均部署有边缘管控设备的情况下，中心管控设备可以将淘汰策略下发给各边缘云节点中的边缘管控设备，由各边缘云节点中的边缘管控设备根据淘汰策略对其所属边缘云节点中存储的镜像进行淘汰处理。
可选地，淘汰策略可以是接收时间最早淘汰策略，即按照镜像的接收时间，优先淘汰接收时间最早的镜像。或者，淘汰策略可以是使用频次最少淘汰策略，即按照镜像的使用频率，优先淘汰使用频次最少的镜像。或者，淘汰策略可以是占用资源最大淘汰策略，即按照镜像占用的存储空间的大小，优先淘汰占用存储空间最大的镜像。
对边缘云节点来说，可以定期按照上述淘汰策略，对本节点中存储的镜像进行淘汰处理；或者，也可以在每当需要接收或获取新的镜像时，判断本节点中是否有足够存储空间存储新的镜像，并在本节点中没有足够存储空间时，按照上述淘汰策略，对本节点中存储的镜像进行淘汰处理，以便于存储新的镜像。以第一边缘云节点需要从第二边缘云节点获取目标镜像为例，在第一边缘云节点中的边缘管控设备从第二边缘云节点处获取目标镜像之前，第一边缘云节点中的边缘管控设备可以判断第一边缘云节点中是否有足够存储空间存储目标镜像；若第一边缘云节点中没有足够存储空间，则根据淘汰策略，对第一边缘云节点中存储的镜像进行淘汰处理，以便有足够存储空间存储目标镜像。可选地，若第一边缘云节点中有足够存储空间，则可以暂时不对第一边缘云节点中存储的镜像进行淘汰处理。
可选地，如图1c所示，该网络系统100还包括：镜像构建设备104。该镜像构建设备104可部署在一个或多个边缘云节点中，主要负责应用镜像的构建、验证等。镜像构建设备104可以提供边缘云环境，可以构建与边缘云环境适配的镜像，也可以验证镜像是否与边缘云环境适配，对于与边缘云环境不适配的镜像可以重构，或输出不适配的提 示信息等。基于镜像构建设备104，用户可以向网络系统100中新增镜像。
在一种新增镜像的可选实施方式中，用户(例如服务需求方)可以向中心管控设备提交新增镜像的第一请求，该第一请求中包括镜像构建信息；中心管控设备向镜像构建设备发送构建请求，该构建请求包括镜像构建信息；镜像构建设备接收到构建请求之后，从中获取镜像构建信息，根据镜像构建信息构建与边缘云环境适配的镜像，将所构建的镜像返回给中心管控设备；中心管控设备接收镜像构建设备返回的新构建的镜像，并添加到镜像库中，不断丰富镜像库。
在另一种新增镜像的可选实施方式中，可以面向用户(例如服务需求方)提供一种镜像的规则和规范，让用户自己制作或生成镜像，用户生成或制作的镜像需要符合边缘云环境的安全、规范等相关要求。用户在制作或生成镜像之后，可以向中心管控设备发送新增镜像的第二请求，该第二请求中包括待新增镜像，该新增镜像是指用户制作或生成的镜像，本实施例并不限定用户制作或生成镜像的方式。中心管控设备接收第二请求，从第二请求中获取待新增镜像，将待新增镜像发送给镜像构建设备；镜像构建设备将待新增镜像与边缘云环境进行适配；若待新增镜像与边缘云环境适配，镜像构建设备向中心管控设备返回待新增镜像与边缘云环境适配的消息；若待新增镜像与边缘云环境不适配，镜像构建设备向中心管控设备返回待新增镜像与边缘云环境不适配的消息。
对中心管控设备来说，若接收到镜像构建设备返回的待新增镜像与边缘云环境适配的消息，则将待新增镜像添加至镜像库中；若接收到镜像构建服务镜像构建设备返回的待新增镜像与边缘云环境不适配的消息，或者通知用户对待新增镜像进行重构后重新提交，或者通知用户提供待新增镜像的重构方法，以供镜像构建服务镜像构建设备按照该重构方法将待新增镜像重构成与边缘云环境适配的镜像。若用户提供待新增镜像的重构方法，则中心管控设备可以将该重构方法提供给镜像构建设备，镜像构建设备按照该重构方法对待新增镜像进行重构，使之与边缘云环境相适配，并将重构后的镜像返回给中心管控设备；中心管控设备接收重构后的镜像并添加到镜像库中。
在此说明，镜像构建设备104可以是一台具有镜像构建、验证等功能的逻辑设备，这些功能可以部署一台物理机或虚拟机上实现，也可以分散性地部署在多台物理机或虚拟机上。当然，本实施例的镜像构建设备104也可以是一台或多台具有镜像构建、验证等功能的物理设备。本申请实施例并不限定镜像构建设备的实现结构，凡是具有上述功能的设备结构均适用于本申请实施例。
在本申请实施例中，不仅可以向镜像库中新增镜像，也可以删除没有用或长时间不 用的镜像，以节约存储空间。例如，中心管控设备可以定期或实时地统计镜像库中各镜像的使用频次，将使用频次小于频次阈值的镜像作为待删除镜像，并执行镜像删除流程将其删除。又例如，中心管控设备也可以接收用户(例如服务需求方)提交的镜像删除请求，将该镜像删除请求指示删除的镜像作为待删除镜像，并执行镜像删除流程将其删除。其中，镜像删除请求中可以携带需要删除的镜像的信息，例如ID、名称或编号等。
对中心管控设备来说，可以采用但不限于上述任一方式确定待删除镜像，在确定待删除镜像之后，一方面可以将待删除镜像从镜像库中删除，另一方面可以指示存储有待删除镜像的边缘云节点将待删除镜像删除。其中，中心管控设备可以根据待删除镜像，在所维护的已下发镜像与已下发镜像所在边缘云节点的对应关系中进行匹配，根据匹配结果确定存储有待删除镜像的边缘云节点。若在该对应关系中匹配到与待删除镜像对应的第三边缘云节点，说明曾经向第三边缘云节点下发过待删除镜像，且第三边缘云节点中仍存储有待删除镜像，于是向第三边缘云节点发送删除指令，该删除指令中携带有待删除镜像的信息，以指示第三边缘云节点将其中存储的待删除镜像删除。第三边缘云节点可能是一个，也可能是多个。
在此说明，在网络系统100包括边缘管控设备103的情况下，中心管控设备具体可以将删除指令发送给边缘管控设备103；边缘管控设备103接收中心管控设备下发的删除指令，从该删除指令中获取待删除镜像的信息，根据待删除镜像的信息，判断第三边缘云节点中是否存储有待删除镜像；如果存储有待删除镜像，将第三边缘云节点中的待删除镜像删除。进一步，若第三边缘云节点中部署有边缘管控设备103，则中心管控设备101具体可以将删除指令发送给第三边缘云节点中的边缘管控设备103；第三边缘云节点中的边缘管控设备103接收中心管控设备下发的删除指令，从该删除指令中获取待删除镜像的信息，根据待删除镜像的信息，判断第三边缘云节点中是否存储有待删除镜像；如果存储有待删除镜像，将第三边缘云节点中的存储的待删除镜像删除。
当中心管控设备将待删除镜像从镜像库中删除，且存储有待删除镜像的边缘云节点也将其中存储的待删除镜像删除后，镜像删除流程完成。
对边缘云节点中的资源设备来说，无论以何种方式，在获取镜像后，在边缘管控设备103的控制下可通过硬件或软件支持的能力以虚拟化的形式为实例提供计算、网络和存储等资源，对应的镜像会以系统盘的形式挂载到对应的实例。在实例创建完成后，对实例尝试启动，在成功启动对应的实例后，就可以利用这些资源设备的能力提供云计算服务。其中，资源设备在边缘管控设备的控制下为实例提供计算、网络和存储等资源包 括：边缘管控设备根据中心管控设备提供的资源模板从目标边缘节云点内分配或预留的资源中申请相关的计算资源、存储资源和/或网络资源；通过调用目标边缘云节点内的计算、存储、网络等执行器进行相关资源的创建动作。其中，资源的创建动作包括：处理存储相关的资源，根据镜像的配置信息及镜像内容创建实例的系统盘，根据资源模板创建对应的数据盘；创建实例依赖的网络资源，例如IP地址、虚拟交换机等；以及结合资源模板创建计算资源。
结合图1b所示中心管控设备和边缘管控设备的实现结构，上述镜像管理与分发功能可由镜像管控模块和镜像服务模块配合实现，详细过程不再赘述。
综上可知，在本申请实施例提供的网络系统中，基于集中管控的方式对边缘云节点的资源调度，镜像管理，运维等进行统一管控，可以最大程度的对边缘云节点进行管理和协调，可降低出现单点自制或全网信息不同步而导致的错误，而且可以利用集中管控的特性达到资源调度的最优化，避免出现边缘局部资源浪费的情况。
除了上述网络系统之外，本申请实施例从边缘管控设备的角度提供了管控方法，下面分别进行详细描述。
图2a为本申请示例性实施例提供的一种管控方法的流程示意图。该实施例是从边缘管控设备的角度进行的描述，如图2a所示，该方法包括：
21a、确定网络系统中的中心管控设备不对或无法对网络系统中至少一个边缘云节点进行管控。
22a、自主地对至少一个边缘云节点进行管控。
在一可选实施例中，边缘管控设备在确定中心管控设备不对或无法对边缘云节点进行管控时，可以采用但不限于以下至少一种方式：
方式1：判断是否与中心管控设备保持连接，在与中心管控设备失去连接的情况下，确定中心管控设备无法对边缘云节点进行管控。
方式2：中心管控设备通过向边缘管控设备发送第一类监控指令，以控制边缘管控设备对至少一个边缘云节点进行监控。基于此，边缘管控设备可以判断是否接收到中心管控设备发送的第一类监控指令，在未接收到中心管控设备发送的第一类监控指令的情况下，确定中心管控设备不对或无法对边缘云节点进行管控。可选地，边缘管控设备和中心管控设备可以预先约定第一类监控指令的等待时长，若超过了所述等待时长仍未接收到中心管控设备发送的第一类监控指令，则确定未接收到中心管控设备发送的第一类 监控指令。
方式3：中心管控设备通过向边缘管控设备发送与指定监控维度对应的第二类监控指令，以控制边缘管控设备从指定监控维度对至少一个边缘云节点进行监控。基于此，边缘管控设备可以判断是否在指定监控维度上接收中心管控设备发送的第二类监控指令；在指定监控维度上未接收到中心管控设备发送的第二类监控指令的情况下，确定中心管控设备在指定监控维度上不对或无法对边缘云节点进行管控。
进一步，在方式1中，在边缘管控设备与中心管控设备恢复连接后，边缘管控设备还可以将失去连接期间的管控数据同步给中心管控设备。
无论是哪种方式，在确定中心管控设备在指定监控维度上不对或无法对边缘云节点进行管控的情况下，边缘管控设备可以自主地对边缘云节点进行管控。可选地，边缘管控设备对边缘云节点进行管控，包括但不限于以下至少一种操作：
对至少一个边缘云节点中处于运行态的对象进行状态监控，并针对监控到的运行状态异常的目标对象进行异常处理；
监控至少一个边缘云节点中处于运行态的对象的生命周期，并根据监控结果控制处于运行态的对象停止、停止后重启、迁移或删除；
采集至少一个边缘云节点中的日志数据，对日志数据进行数据分析，并根据数据分析结果执行后续动作；
对至少一个边缘云节点进行流量监控，并针对监控到的流量攻击事件进行阻断处理；
对至少一个边缘云节点进行网络安全漏洞扫描，并针对扫描到的网络安全漏洞问题进行修复；
监控至少一个边缘云节点中的资源用量，并根据监控结果对至少一个边缘云节点进行资源扩容或减容。
进一步可选地，在针对监控到的运行状态异常的目标对象进行异常处理时，可以对目标对象的异常运行状态进行分析，根据分析结果确定至少一种候选处理方式；从至少一种候选处理方式中获取目标处理方式，根据目标处理方式对目标对象进行异常处理。
可选地，从至少一种候选处理方式中获取目标处理方式，包括：
在与中心管控设备保持连接的情况下，将至少一种候选处理方式上报给中心管控设备，以供中心管控设备从中选择处理方式；接收中心管控设备返回的处理方式作为目标处理方式；或者
在与中心管控设备失去连接的情况下，输出至少一种候选处理方式至边缘管控人员， 以供管控人员从中选择处理方式；响应于边缘管控人员的选择操作，确定被选择的处理方式作为目标处理方式；或者
在与中心管控设备失去连接的情况下，按照设定的选择策略，从至少一种候选处理方式中选择目标处理方式。关于选择策略可根据应用场景灵活设定，本申请对此不做限定。例如，选择策略可以是选择最简单的处理方式，或者选择资源消耗最少的处理方式，等等。关于每种处理方式的性能或属性，可以预先获知，也可以实时判断。
值得说明的是，在边缘管控设备与中心管控设备保持连接的情况下，也可以将至少一种候选处理方式输出给边缘管控人员，由边缘管控人员从中选择使用的目标处理方式。本申请实施例对此不做限定，例如可以以短信、应用内消息、系统消息和/或邮件等方式输出到边缘管控人员使用的手机、电脑等终端设备上。
进一步，若每个边缘云节点中均部署有边缘管控设备，则每个边缘管控设备可以在中心管控设备不对或无法对其所属边缘云节点进行管控的情况下，自主地对其所属边缘云节点进行管控。
可选地，边缘管控设备自主地对至少一个边缘云节点进行管控，可以根据定时任务，周期性地对至少一个边缘云节点进行管控。当然，边缘管控设备也可以根据其它方式的自主策略，自主地对至少一个边缘云节点进行管控，例如可以在每天某个固定的时间点，自主地对至少一个边缘云节点进行管控。
进一步，除了边缘管控设备自主地对至少一个边缘云节点进行管控之外，边缘管控设备也可以协助中心管控设备对至少一个边缘云节点进行管控。如图2b所示，边缘管控设备协助中心管控设备对边缘云节点进行管控的流程包括：
21b、对网络系统中的至少一个边缘云节点进行监控；
22b、将监控数据上报给网络系统中的中心管控设备，以供中心管控设备根据监控数据对至少一个边缘云节点进行管控。
可选地，边缘管控设备可以根据定时任务，周期性地从至少一个监控维度对至少一个边缘云节点进行监控。或者，边缘管控设备可在中心管控设备的控制下，对网络系统中的至少一个边缘云节点进行监控。关于中心管控设备对边缘管控设备的控制方式，本申请实施例不做限定，两种可选实施例如下所述。
在一可选实施例中，步骤21b的实施过程包括：根据中心管控设备发送的第一类监控指令，从至少一个监控维度对至少一个边缘云节点进行监控。相应地，步骤22b的实施过程包括：将至少一个监控维度上的监控数据上报给所述中心管控设备，以供中心管 控设备根据至少一个监控维度上的监控数据对至少一个边缘云节点进行管控。
在另一可选实施例中，步骤21b的实施过程包括：根据中心管控设备发送的第二类监控指令，在指定监控维度上对至少一个边缘云节点进行监控。相应地，步骤22b的实施过程包括：将指定监控维度上的监控数据上报给中心管控设备，以供中心管控设备根据指定监控维度上的监控数据对至少一个边缘云节点进行管控。
进一步可选地，边缘管控设备可以从至少一个监控维度协助中心管控设备对边缘云节点进行管控，下面举例说明。
在示例1中，步骤21b的实施过程包括：对至少一个边缘云节点中处于运行态的对象进行状态监控。相应地，步骤22b的实施过程包括：将监控到的处于运行态的对象的运行状态上报给中心管控设备，以供中心管控设备识别运行状态异常的目标对象并对目标对象进行异常处理。
在示例2中，步骤21b的实施过程包括：监控至少一个边缘云节点中处于运行态的对象的生命周期。相应地，步骤22b的实施过程包括：将监控到的处于运行态的对象的生命周期上报给中心管控设备，以供中心管控设备控制处于运行态的对象停止、停止后重启或删除；
在示例3中，步骤21b的实施过程包括：采集至少一个边缘云节点中的日志数据。相应地，步骤22b的实施过程包括：将日志数据上报给中心管控设备，以供中心管控设备对日志数据进行数据分析并根据数据分析结果执行后续动作；
在示例4中，步骤21b的实施过程包括：对至少一个边缘云节点进行流量监控。相应地，步骤22b的实施过程包括：将监控到的流量攻击事件上报给中心管控设备，以供中心管控设备对流量攻击事件进行阻断处理；
在示例5中，步骤21b的实施过程包括：对至少一个边缘云节点进行网络安全漏洞扫描。相应地，步骤22b的实施过程包括：将扫描到的网络安全漏洞问题上报给中心管控设备，以供中心管控设备对网络安全漏洞问题进行修复；
在示例6中，步骤21b的实施过程包括：监控至少一个边缘云节点中的资源用量。相应地，步骤22b的实施过程包括：将监控到的资源用量信息上报给中心管控设备，以供中心管控设备对至少一个边缘云节点进行资源扩容或减容。
在上述方法实施例中，中心管控设备与边缘管控设备相结合，边缘管控设备可以协助中心管控设备对至少一个边缘云节点进行管控，除此之外，边缘管控设备也具备一定的自行管控的能力，可以在中心管控设备不对或无法对边缘云节点进行管控的情况下， 自主地对边缘云节点进行管控，实现两级管控，可以更加充分、全面地对边缘云节点进行管控，为“将云计算放到距离终端更近的边缘云节点中处理”提供了条件，进而可借助边缘云节点中的资源为用户提供云计算服务，有利于降低响应时延，减轻中心云或传统云计算平台的压力，降低带宽成本。
值得说明的是，上述方法实施例中的“管控”可以是运维维度的管控。例如，中心管控设备可在边缘管控设备的协助下，对至少一个边缘云节点进行运维管控。在运维管控场景下，上述至少一个监控维度或指定监控维度可以是运维维度，则中心管控设备可以根据边缘管控设备上报的至少一个运维维度或指定运维维度上的监控数据，对至少一个边缘云节点进行运维管控。另外，在中心管控设备不对边缘云节点进行运维管控或者无法对边缘云节点进行运维管控的情况下，边缘管控设备可以自主地对至少一个边缘云节点进行运维管控。例如，边缘管控设备可以根据监控到的至少一个运维维度或指定运维维度上的监控数据，对至少一个边缘云节点进行运维管控。关于中心管控设备或边缘管控设备对至少一个边缘云节点进行运维管控的详细内容可参见前述实施例，在此不再赘述。
需要说明的是，在上述实施例及附图中的描述的一些流程中，包含了按照特定顺序出现的多个操作，但是应该清楚了解，这些操作可以不按照其在本文中出现的顺序来执行或并行执行，操作的序号如21a、22a等，仅仅是用于区分开各个不同的操作，序号本身不代表任何的执行顺序。另外，这些流程可以包括更多或更少的操作，并且这些操作可以按顺序执行或并行执行。需要说明的是，本文中的“第一”、“第二”等描述，是用于区分不同的消息、设备、模块等，不代表先后顺序，也不限定“第一”和“第二”是不同的类型。
图3为本申请示例性实施例提供的一种中心管控设备的结构示意图。如图3所示，该中心管控设备包括：存储器31、处理器32和通信组件33。
存储器31，用于存储计算机程序，并可被配置为存储其它各种数据以支持在中心管控设备上的操作。这些数据的示例包括用于在中心管控设备上操作的任何应用程序或方法的指令，消息，图片，视频等。
处理器32，与存储器31耦合，用于执行存储器31中的计算机程序，以用于：通过通信组件33接收边缘管控设备上报的针对网络系统中的至少一个边缘云节点的监控数据，并根据该监控数据对至少一个边缘云节点进行管控。
在一可选实施例中，处理器32具体用于：通过通信组件33向边缘管控设备发送第 一类监控指令，以指示边缘管控设备从至少一个监控维度对至少一个边缘云节点进行监控并将至少一个监控维度上的监控数据上报给中心管控设备；根据边缘管控设备上报的至少一个监控维度上的监控数据对至少一个边缘云节点进行管控。第一类监控指令是一种指示边缘管控设备从至少一个监控维度对至少一个边缘云节点进行监控并上报至少一个监控维度上的监控数据的监控指令。值得说明的是，监控维度可根据应用需求灵活设定，并预置到边缘管控设备和中心管控设备中。
或者，处理器32具体用于：通过通信组件33向边缘管管控设备发送第二类监控指令，第二类监控指令与指定监控维度对应，用于指示边缘管控设备在指定监控维度上对至少一个边缘云节点进行监控并上报指定监控维度上的监控数据；根据指定监控维度上的监控数据对至少一个边缘云节点进行管控。
值得说明的是，指定监控维度可以是一个，也可以是多个。在指定监控维度是多个的情况下，每个指定监控维度可以对应一个第二类监控指令。
上述至少一个监控维度或指定监控维度可以包括但不限于以下几个维度：处于运行态的对象维度，日志维度，安全维度，资源维度等。进一步，处于运行态的对象维度可包括对象的运行状态维度和/或对象的生命周期维度；安全维度可包括：流量攻击维度和/或安全漏洞维度。
结合上述列举的几个监控维度，处理器32具体用于执行但不限于以下至少一种操作：
控制边缘管控设备对至少一个边缘云节点中处于运行态的对象进行状态监控；接收边缘管控设备上报的处于运行态的对象的运行状态；从边缘管控设备上报的处于运行态的对象的运行状态中识别出运行状态异常的对象，为便于描述和区分，将运行状态异常的对象称为目标对象，并针对目标对象进行异常处理；或者
控制边缘管控设备对至少一个边缘云节点中处于运行态的对象的生命周期进行监控；接收边缘管控设备上报的处于运行态的对象的生命周期；根据边缘管控设备上报的处于运行态的对象的生命周期，控制处于运行态的对象停止、停止后重启或删除；或者
控制边缘管控设备采集至少一个边缘云节点中的日志数据；接收边缘管控设备上报的日志数据；对日志数据进行数据分析，并根据数据分析结果执行后续动作，例如可以计费、风控和/或增减实例等；或者
控制边缘管控设备对至少一个边缘云节点进行流量监控；接收边缘管控设备上报的流量攻击事件；对边缘云节点中出现的流量攻击事件进行阻断处理；或者
控制边缘管控设备对至少一个边缘云节点进行网络安全漏洞扫描；接收边缘管控设备上报的网络安全漏洞问题；对该网络安全漏洞问题进行修复；或者
控制边缘管控设备监控至少一个边缘云节点中的资源用量；接收边缘管控设备上报的资源用量信息；根据边缘管控设备上报的资源用量信息，对至少一个边缘云节点进行资源扩容或减容。
可选地，本实施例中的“管控”可以是运维维度的管控，则，处理器32，具体可用于：接收边缘管控设备上报的针对网络系统中的至少一个边缘云节点的监控数据，并根据该监控数据对至少一个边缘云节点进行运维管控。进一步，处理器32还可以控制边缘管控设备从至少一个运维维度或指定运维维度针对至少一个边缘云节点进行监控；并根据边缘管控设备上报的至少一个运维维度或指定运维维度上的监控数据，对至少一个边缘云节点进行运维管控。关于控制边缘管控设备从至少一个运维维度或指定运维维度针对至少一个边缘云节点进行监控以及对至少一个边缘云节点进行运维管控的详细内容可参见前面描述，在此不再赘述。
进一步，如图3所示，该中心管控设备还包括：显示器34、电源组件35和音频组件36等其它组件。图3中仅示意性给出部分组件，并不意味着中心管控设备只包括图3所示组件。另外，图3中虚线框内的组件为可选组件，具体可视中心管控设备实现形态而定。如果中心管控设备是服务器形态的设备，可选地，可以不包括显示器34和音频组件36；若中心管控设备是终端设备形态的设备，可选地，可以包括显示器34和音频组件36。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，计算机程序被一个或多个处理器执行时，致使一个或多个处理器实现上述方法实施例中可由中心管控设备执行的各步骤或操作。
图4为本申请示例性实施例提供的一种边缘管控设备的结构示意图。如图4所示，该设备包括：存储器41和处理器42。
存储器41，用于存储计算机程序，并可被配置为存储其它各种数据以支持在边缘管控设备上的操作。这些数据的示例包括用于在边缘管控设备上操作的任何应用程序或方法的指令，消息，图片，视频等。
处理器42，与存储器41耦合，用于执行存储器41中的计算机程序，以用于：确定网络系统中的中心管控设备不对或无法对网络系统中至少一个边缘云节点进行管控；自主地对至少一个边缘云节点进行管控。
在一可选实施例中，处理器42在确定中心管控设备不对或无法对边缘云节点进行管控时，具体用于执行以下至少一种操作：
在边缘管控设备与中心管控设备失去连接的情况下，确定中心管控设备无法对至少一个边缘云节点进行管控；或者
在未接收到中心管控设备发送的第一类监控指令的情况下，确定中心管控设备不对或无法对至少一个边缘云节点进行管控；或者
在指定监控维度上未接收到中心管控设备发送的第二类监控指令的情况下，确定中心管控设备在指定监控维度上不对或无法对至少一个边缘云节点进行管控。
进一步，处理器42还用于：在边缘管控设备与中心管控设备恢复连接后，将失去连接期间的管控数据同步给中心管控设备。
在一可选实施例中，处理器42在自主地对至少一个边缘云节点进行管控时，具体用于执行以下至少一种操作：
对至少一个边缘云节点中处于运行态的对象进行状态监控，并针对监控到的运行状态异常的目标对象进行异常处理；
监控至少一个边缘云节点中处于运行态的对象的生命周期，并根据监控结果控制处于运行态的对象停止、停止后重启或删除；
采集至少一个边缘云节点中的日志数据，对日志数据进行数据分析，并根据数据分析结果执行后续动作；
对至少一个边缘云节点进行流量监控，并针对监控到的流量攻击事件进行阻断处理；
对至少一个边缘云节点进行网络安全漏洞扫描，并针对扫描到的网络安全漏洞问题进行修复；
监控至少一个边缘云节点中的资源用量，并根据监控结果对至少一个边缘云节点进行资源扩容或减容。
进一步可选地，处理器42在针对监控到的运行状态异常的目标对象进行异常处理时，具体用于：对目标对象的异常运行状态进行分析，根据分析结果确定至少一种候选处理方式；从至少一种候选处理方式中获取目标处理方式，根据目标处理方式对目标对象进行异常处理。
可选地，如图4所示，本实施例的边缘管控设备还包括：通信组件43。处理器42在从至少一种候选处理方式中获取目标处理方式时，具体用于：在边缘管控设备与中心管控设备保持连接的情况下，将至少一种候选处理方式上报给中心管控设备，以供中心 管控设备从中选择处理方式；通过通信组件43接收中心管控设备返回的处理方式作为目标处理方式；或者，在边缘管控设备与中心管控设备失去连接的情况下，输出至少一种候选处理方式至边缘管控人员，以供管控人员从中选择处理方式；响应于边缘管控人员的选择操作，确定被选择的处理方式作为目标处理方式；或者，在边缘管控设备与中心管控设备失去连接的情况下，按照设定的选择策略，从至少一种候选处理方式中选择目标处理方式。
在一可选实施例中，处理器42还用于：对网络系统中的至少一个边缘云节点进行监控，并将监控数据上报给中心管控设备，以供中心管控设备根据监控数据对至少一个边缘云节点进行管控。
可选地，处理器42还用于：在中心管控设备的控制下，对至少一个边缘云节点进行监控。例如，处理器42具体用于：根据中心管控设备发送的第一类监控指令，从至少一个监控维度对至少一个边缘云节点进行监控，并将至少一个监控维度上的监控数据上报给中心管控设备，以供中心管控设备根据至少一个监控维度上的监控数据对至少一个边缘云节点进行管控；或者，根据中心管控设备发送的第二类监控指令，在指定监控维度上对至少一个边缘云节点进行监控，并将指定监控维度上的监控数据上报给中心管控设备，以供中心管控设备根据指定监控维度上的监控数据对至少一个边缘云节点进行管控。
可选地，可选地，处理器42还用于根据定时任务，周期性地从至少一个监控维度对所述至少一个边缘云节点进行监控，并将至少一个监控维度上的监控数据上报给中心管控设备，以供中心管控设备根据至少一个监控维度上的监控数据对至少一个边缘云节点进行管控。
进一步可选地，处理器42在对至少一个边缘云节点进行监控并将监控数据上报给中心管控设备时，具体用于执行以下至少一种操作：
对至少一个边缘云节点中处于运行态的对象进行状态监控，将监控到的处于运行态的对象的运行状态上报给中心管控设备，以供中心管控设备识别运行状态异常的目标对象并对目标对象进行异常处理；
监控至少一个边缘云节点中处于运行态的对象的生命周期，并将监控到的处于运行态的对象的生命周期上报给中心管控设备，以供中心管控设备控制处于运行态的对象停止、停止后重启或删除；
采集至少一个边缘云节点中的日志数据，并将日志数据上报给中心管控设备，以供中心管控设备对日志数据进行数据分析并根据数据分析结果执行后续动作；
对至少一个边缘云节点进行流量监控，并将监控到的流量攻击事件上报给中心管控设备，以供中心管控设备对流量攻击事件进行阻断处理；
对至少一个边缘云节点进行网络安全漏洞扫描，并将扫描到的网络安全漏洞问题上报给中心管控设备，以供中心管控设备对网络安全漏洞问题进行修复；
监控至少一个边缘云节点中的资源用量，并将监控到的资源用量信息上报给中心管控设备，以供中心管控设备对至少一个边缘云节点进行资源扩容或减容。
可选地，每个边缘云节点中分别部署有边缘管控设备，则处理器42具体用于：自主地对其所属边缘管控设备所属边缘云节点进行管控。
可选地，本实施例中的“管控”可以是运维维度的管控，则，处理器42，具体可用于：自主地对至少一个边缘云节点进行运维管控；或者在中心管控设备的控制下从至少一个运维维度或指定运维维度针对至少一个边缘云节点进行监控。关于自主地对至少一个边缘云节点进行运维管控，或在中心管控设备的控制下从至少一个运维维度或指定运维维度针对至少一个边缘云节点进行监控的详细内容可参见前面描述，在此不再赘述。
进一步，如图4所示，该边缘管控设备还包括：显示器44、电源组件45和音频组件46等其它组件。图4中仅示意性给出部分组件，并不意味着边缘管控设备只包括图4所示组件。另外，图4中虚线框内的组件为可选组件，具体可视边缘管控设备实现形态而定。如果边缘管控设备是服务器形态的设备，可选地，可以不包括显示器44和音频组件46；若边缘管控设备是终端设备形态的设备，可选地，可以包括显示器44和音频组件46。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，计算机程序被一个或多个处理器执行时，致使一个或多个处理器实现上述方法实施例中可由边缘管控设备执行的各步骤或操作。
上述图3和图4中的存储器可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
上述图3和图4中的通信组件被配置为便于通信组件所在设备和其他设备之间有线或无线方式的通信。通信组件所在设备可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件还可以包括 近场通信(NFC)模块，射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术等。
上述图3和图4中的显示器包括屏幕，其屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。
上述图3和图4中的电源组件，为电源组件所在设备的各种组件提供电力。电源组件可以包括电源管理系统，一个或多个电源，及其他与为电源组件所在设备生成、管理和分配电力相关联的组件。
上述图3和图4中的音频组件，可被配置为输出和/或输入音频信号。例如，音频组件包括一个麦克风(MIC)，当音频组件所在设备处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器或经由通信组件发送。在一些实施例中，音频组件还包括一个扬声器，用于输出音频信号。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或 多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (21)

  1. 一种网络系统，其特征在于，包括：中心管控设备，边缘管控设备，以及至少一个边缘云节点；
    所述中心管控设备，用于接收所述边缘管控设备上报的针对所述至少一个边缘云节点的监控数据，并根据所述监控数据对所述至少一个边缘云节点进行管控；
    所述边缘管控设备，用于对所述至少一个边缘云节点进行监控并将监控数据上报给所述中心管控设备；以及在所述中心管控设备不对或无法对所述至少一个边缘云节点进行管控的情况下，自主地对所述至少一个边缘云节点进行管控。
  2. 根据权利要求1所述的网络系统，其特征在于，所述边缘管控设备具体用于：
    在与所述中心管控设备失去连接的情况下，自主地从至少一个监控维度对所述至少一个边缘云节点进行管控；
    或者
    在未接收到所述中心管控设备发送的第一类监控指令的情况下，自主地从至少一个监控维度对所述至少一个边缘云节点进行管控
    或者
    若在指定监控维度上未接收到所述中心管控设备发送的第二类监控指令，自主地从所述指定监控维度对所述至少一个边缘云节点进行管控。
  3. 根据权利要求2所述的网络系统，其特征在于，所述边缘管控设备还用于：
    在与所述中心管控设备恢复连接后，将失去连接期间的管控数据同步给所述中心管控设备。
  4. 根据权利要求1-3任一项所述的网络系统，其特征在于，所述边缘管控设备在自主对所述至少一个边缘云节点进行管控时，具体用于执行以下至少一种操作：
    对所述至少一个边缘云节点中处于运行态的对象进行状态监控，并针对监控到的运行状态异常的目标对象进行异常处理；
    监控所述至少一个边缘云节点中处于运行态的对象的生命周期，并根据监控结果控制所述处于运行态的对象停止、停止后重启、迁移或删除；
    采集所述至少一个边缘云节点中的日志数据，对所述日志数据进行数据分析，并根据数据分析结果执行后续动作；
    对所述至少一个边缘云节点进行流量监控，并针对监控到的流量攻击事件进行阻断处理；
    对所述至少一个边缘云节点进行网络安全漏洞扫描，并针对扫描到的网络安全漏洞问题进行修复；
    监控所述至少一个边缘云节点中的资源用量，并根据监控结果对所述至少一个边缘云节点进行资源扩容或减容。
  5. 根据权利要求4所述的网络系统，其特征在于，所述边缘管控设备在针对目标对象进行异常处理时，具体用于：
    对所述目标对象的异常运行状态进行分析，根据分析结果确定至少一种候选处理方式；
    从所述至少一种候选处理方式中获取目标处理方式，根据所述目标处理方式对所述目标对象进行异常处理。
  6. 根据权利要求5所述的网络系统，其特征在于，所述边缘管控设备在获取目标处理方式时，具体用于：
    在与所述中心管控设备保持连接的情况下，将所述至少一种候选处理方式上报给所述中心管控设备，以供所述中心管控设备从中选择处理方式；接收所述中心管控设备返回的处理方式作为所述目标处理方式；或者
    在与所述中心管控设备失去连接的情况下，输出所述至少一种候选处理方式至边缘管控人员，以供所述管控人员从中选择处理方式；响应于所述边缘管控人员的选择操作，确定被选择的处理方式作为所述目标处理方式；或者
    在与所述中心管控设备失去连接的情况下，按照设定的选择策略，从所述至少一种候选处理方式中选择所述目标处理方式。
  7. 根据权利要求1-3任一项所述的网络系统，其特征在于，所述边缘管控设备在对所述至少一个边缘云节点进行监控并将监控数据上报给所述中心管控设备时，具体用于执行以下至少一种操作：
    对所述至少一个边缘云节点中处于运行态的对象进行状态监控，将监控到的所述处于运行态的对象的运行状态上报给所述中心管控设备，以供所述中心管控设备识别运行状态异常的目标对象并对所述目标对象进行异常处理；
    监控所述至少一个边缘云节点中处于运行态的对象的生命周期，并将监控到的所述处于运行态的对象的生命周期上报给所述中心管控设备，以供所述中心管控设备控制所述处于运行态的对象停止、停止后重启或删除；
    采集所述至少一个边缘云节点中的日志数据，并将所述日志数据上报给所述中心管 控设备，以供所述中心管控设备对所述日志数据进行数据分析并根据数据分析结果执行后续动作；
    对所述至少一个边缘云节点进行流量监控，并将监控到的流量攻击事件上报给所述中心管控设备，以供所述中心管控设备对所述流量攻击事件进行阻断处理；
    对所述至少一个边缘云节点进行网络安全漏洞扫描，并将扫描到的网络安全漏洞问题上报给所述中心管控设备，以供所述中心管控设备对所述安全漏洞问题进行修复；
    监控所述至少一个边缘云节点中的资源用量，并将监控到的资源用量信息上报给所述中心管控设备，以供所述中心管控设备对所述至少一个边缘云节点进行资源扩容或减容。
  8. 根据权利要求1-3任一项所述的网络系统，其特征在于，每个边缘云节点中分别部署有边缘管控设备；
    其中，每个边缘云节点中的边缘管控设备具体用于：对其所属边缘云节点进行监控并将监控数据上报给所述中心管控设备；以及在所述中心管控设备不对或无法对其所属边缘云节点进行管控的情况下，自主地对其所属边缘云节点进行管控。
  9. 一种管控方法，其特征在于，包括：
    确定网络系统中的中心管控设备不对或无法对所述网络系统中至少一个边缘云节点进行管控；
    自主地对所述至少一个边缘云节点进行管控。
  10. 根据权利要求9所述的方法，其特征在于，确定网络系统中的中心管控设备不对或无法对所述网络系统中至少一个边缘云节点进行管控，包括以下至少一种方式：
    在与所述中心管控设备失去连接的情况下，确定所述中心管控设备无法对所述至少一个边缘云节点进行管控；
    在未接收到所述中心管控设备发送的第一类监控指令的情况下，确定所述中心管控设备不对或无法对所述至少一个边缘云节点进行管控；
    在指定监控维度上未接收到所述中心管控设备发送的第二类监控指令的情况下，确定所述中心管控设备在所述指定监控维度上不对或无法对所述至少一个边缘云节点进行管控。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    在与所述中心管控设备恢复连接后，将失去连接期间的管控数据同步给所述中心管控设备。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，自主地对所述至少一个边缘云节点进行管控，包括以下至少一种方式：
    对所述至少一个边缘云节点中处于运行态的对象进行状态监控，并针对监控到的运行状态异常的目标对象进行异常处理；
    监控所述至少一个边缘云节点中处于运行态的对象的生命周期，并根据监控结果控制所述处于运行态的对象停止、停止后重启、迁移或删除；
    采集所述至少一个边缘云节点中的日志数据，对所述日志数据进行数据分析，并根据数据分析结果执行后续动作；
    对所述至少一个边缘云节点进行流量监控，并针对监控到的流量攻击事件进行阻断处理；
    对所述至少一个边缘云节点进行网络安全漏洞扫描，并针对扫描到的网络安全漏洞问题进行修复；
    监控所述至少一个边缘云节点中的资源用量，并根据监控结果对所述至少一个边缘云节点进行资源扩容或减容。
  13. 根据权利要求12所述的方法，其特征在于，针对监控到的运行状态异常的目标对象进行异常处理，包括：
    对所述目标对象的异常运行状态进行分析，根据分析结果确定至少一种候选处理方式；
    从所述至少一种候选处理方式中获取目标处理方式，根据所述目标处理方式对所述目标对象进行异常处理。
  14. 根据权利要求13所述的方法，其特征在于，从所述至少一种候选处理方式中获取目标处理方式，包括：
    在与所述中心管控设备保持连接的情况下，将所述至少一种候选处理方式上报给所述中心管控设备，以供所述中心管控设备从中选择处理方式；接收所述中心管控设备返回的处理方式作为所述目标处理方式；或者
    在与所述中心管控设备失去连接的情况下，输出所述至少一种候选处理方式至边缘管控人员，以供所述管控人员从中选择处理方式；响应于所述边缘管控人员的选择操作，确定被选择的处理方式作为所述目标处理方式；或者
    在与所述中心管控设备失去连接的情况下，按照设定的选择策略，从所述至少一种候选处理方式中选择所述目标处理方式。
  15. 根据权利要求9-11任一项所述的方法，其特征在于，每个边缘云节点中分别部署有边缘管控设备，则自主地对所述至少一个边缘云节点进行管控，包括：
    每个边缘云节点中的边缘管控设备自主地对其所属边缘云节点进行管控。
  16. 一种管控方法，其特征在于，包括：
    对网络系统中的至少一个边缘云节点进行监控；
    将监控数据上报给所述网络系统中的中心管控设备，以供所述中心管控设备根据所述监控数据对所述至少一个边缘云节点进行管控。
  17. 根据权利要求16所述的方法，其特征在于，对网络系统中的至少一个边缘云节点进行监控，包括：
    根据所述中心管控设备发送的第一类监控指令，从至少一个监控维度对所述至少一个边缘云节点进行监控；
    或者
    根据所述中心管控设备发送的第二类监控指令，在指定监控维度上对所述至少一个边缘云节点进行监控；或者
    根据定时任务，周期性地从至少一个监控维度对所述至少一个边缘云节点进行监控。
  18. 根据权利要求16所述的方法，其特征在于，对网络系统中的至少一个边缘云节点进行监控，并将监控数据上报给所述网络系统中的中心管控设备，以供所述中心管控设备根据所述监控数据对所述至少一个边缘云节点进行管控，包括以下至少一种方式：
    对所述至少一个边缘云节点中处于运行态的对象进行状态监控，将监控到的所述处于运行态的对象的运行状态上报给所述中心管控设备，以供所述中心管控设备识别运行状态异常的目标对象并对所述目标对象进行异常处理；
    监控所述至少一个边缘云节点中处于运行态的对象的生命周期，并将监控到的所述处于运行态的对象的生命周期上报给所述中心管控设备，以供所述中心管控设备控制所述处于运行态的对象停止、停止后重启、迁移或删除；
    采集所述至少一个边缘云节点中的日志数据，并将所述日志数据上报给所述中心管控设备，以供所述中心管控设备对所述日志数据进行数据分析并根据数据分析结果执行后续动作；
    对所述至少一个边缘云节点进行流量监控，并将监控到的流量攻击事件上报给所述中心管控设备，以供所述中心管控设备对所述流量攻击事件进行阻断处理；
    对所述至少一个边缘云节点进行网络安全漏洞扫描，并将扫描到的网络安全漏洞问题上报给所述中心管控设备，以供所述中心管控设备对所述网络安全漏洞问题进行修复；
    监控所述至少一个边缘云节点中的资源用量，并将监控到的资源用量信息上报给所述中心管控设备，以供所述中心管控设备对所述至少一个边缘云节点进行资源扩容或减容。
  19. 根据权利要求16-18任一项所述的方法，其特征在于，每个边缘云节点中分别部署有边缘管控设备，则对网络系统中的至少一个边缘云节点进行监控并将监控数据上报给所述网络系统中的中心管控设备，包括：
    每个边缘云节点中的边缘管控设备对其所属边缘云节点进行监控并将其所述边缘云节点中的监控数据上报给所述中心管控设备。
  20. 一种边缘管控设备，其特征在于，包括：存储器和处理器；
    所述存储器，用于存储计算机程序；当所述计算机程序被所述处理器执行时，致使所述处理器实现权利要求9-19任一项所述方法中的步骤。
  21. 一种存储有计算机程序的计算机可读存储介质，其特征在于，当所述计算机程序被一个或多个处理器执行时，致使所述一个或多个处理器实现权利要求9-19任一项所述方法中的步骤。
PCT/CN2020/081569 2019-04-08 2020-03-27 网络系统、管控方法、设备及存储介质 WO2020207265A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910277460.1 2019-04-08
CN201910277460.1A CN111800281B (zh) 2019-04-08 2019-04-08 网络系统、管控方法、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020207265A1 true WO2020207265A1 (zh) 2020-10-15

Family

ID=72751904

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/081569 WO2020207265A1 (zh) 2019-04-08 2020-03-27 网络系统、管控方法、设备及存储介质

Country Status (2)

Country Link
CN (2) CN117411765A (zh)
WO (1) WO2020207265A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114760221A (zh) * 2022-03-31 2022-07-15 深信服科技股份有限公司 一种业务监控方法、系统和存储介质
CN116887220A (zh) * 2023-08-10 2023-10-13 谷梵科技(青田)有限公司 基于云边协同的v2x服务高可用方法、系统、装置及存储介质
CN116938835A (zh) * 2023-09-18 2023-10-24 北京交通大学 工业物联网场景下的带宽资源分配方法及电子设备

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333669B (zh) * 2020-12-01 2023-04-18 杭州都市高速公路有限公司 车路协同路侧基站系统的安全检查方法、装置和电子设备
CN112565415B (zh) * 2020-12-03 2022-05-31 杭州谐云科技有限公司 一种基于云边协同的跨地域资源纳管系统和纳管方法
CN112769230A (zh) * 2020-12-22 2021-05-07 南方电网深圳数字电网研究院有限公司 基于容器技术的分布式边缘微云监控系统
CN113296903A (zh) * 2021-02-01 2021-08-24 阿里巴巴集团控股有限公司 边缘云系统、边缘管控方法、管控节点及存储介质
CN112448858B (zh) * 2021-02-01 2021-04-23 腾讯科技（深圳）有限公司 网络通信控制方法及装置、电子设备和可读存储介质
CN113114656B (zh) * 2021-04-07 2022-11-18 北京中嘉和信通信技术有限公司 基于边缘云计算的基础设施布局方法
CN113487033B (zh) * 2021-07-30 2023-05-23 上海壁仞智能科技有限公司 以图形处理器为执行核心的推理方法和装置
CN113342478B (zh) * 2021-08-04 2022-02-01 阿里云计算有限公司 资源管理方法、设备、网络系统及存储介质
CN114301809B (zh) * 2021-12-31 2024-02-09 郑州云海信息技术有限公司 一种边缘计算平台架构
CN114024967B (zh) * 2022-01-10 2022-03-25 广东电力信息科技有限公司 一种基于云边和边边协同架构的iaas数据处理系统及方法
CN114567648A (zh) * 2022-03-24 2022-05-31 阿里巴巴（中国）有限公司 分布式云系统
CN117857568A (zh) * 2023-12-25 2024-04-09 慧之安信息技术股份有限公司 基于云边协同的边缘设备增容配置方法和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150245160A1 (en) * 2014-02-24 2015-08-27 International Business Machines Corporation Techniques for Mobility-Aware Dynamic Service Placement in Mobile Clouds
US20190064787A1 (en) * 2017-08-31 2019-02-28 Rockwell Automation Technologies, Inc. Discrete manufacturing hybrid cloud solution architecture
CN109462654A (zh) * 2018-11-30 2019-03-12 深圳市中电数通智慧安全科技股份有限公司 一种智慧应急控制系统
CN109495585A (zh) * 2018-12-19 2019-03-19 上海上实龙创智慧能源科技股份有限公司 一种边缘网络与云端的分级控制方法
CN109510723A (zh) * 2018-11-19 2019-03-22 深圳友讯达科技股份有限公司 网关设备、物联网事务管控系统及方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109120542A (zh) * 2018-08-20 2019-01-01 国云科技股份有限公司 一种基于边缘计算的流量管理系统及其实现方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150245160A1 (en) * 2014-02-24 2015-08-27 International Business Machines Corporation Techniques for Mobility-Aware Dynamic Service Placement in Mobile Clouds
US20190064787A1 (en) * 2017-08-31 2019-02-28 Rockwell Automation Technologies, Inc. Discrete manufacturing hybrid cloud solution architecture
CN109510723A (zh) * 2018-11-19 2019-03-22 深圳友讯达科技股份有限公司 网关设备、物联网事务管控系统及方法
CN109462654A (zh) * 2018-11-30 2019-03-12 深圳市中电数通智慧安全科技股份有限公司 一种智慧应急控制系统
CN109495585A (zh) * 2018-12-19 2019-03-19 上海上实龙创智慧能源科技股份有限公司 一种边缘网络与云端的分级控制方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
JAIN, RAKESH ET AL.: "Cloud to Edge: Distributed Deployment of Process-Aware IoT Applications", 2017 IEEE INTERNATIONAL CONFERENCE ON EDGE COMPUTING (EDGE), 11 September 2017 (2017-09-11), XP033151597, DOI: 20200609154427A *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114760221A (zh) * 2022-03-31 2022-07-15 深信服科技股份有限公司 一种业务监控方法、系统和存储介质
CN114760221B (zh) * 2022-03-31 2024-02-23 深信服科技股份有限公司 一种业务监控方法、系统和存储介质
CN116887220A (zh) * 2023-08-10 2023-10-13 谷梵科技(青田)有限公司 基于云边协同的v2x服务高可用方法、系统、装置及存储介质
CN116887220B (zh) * 2023-08-10 2024-05-24 谷梵科技(青田)有限公司 基于云边协同的v2x服务高可用方法、系统、装置及存储介质
CN116938835A (zh) * 2023-09-18 2023-10-24 北京交通大学 工业物联网场景下的带宽资源分配方法及电子设备
CN116938835B (zh) * 2023-09-18 2023-11-17 北京交通大学 工业物联网场景下的带宽资源分配方法及电子设备

Also Published As

Publication number Publication date
CN111800281B (zh) 2023-08-04
CN117411765A (zh) 2024-01-16
CN111800281A (zh) 2020-10-20

Similar Documents

Publication Publication Date Title
WO2020207265A1 (zh) 网络系统、管控方法、设备及存储介质
WO2020207266A1 (zh) 网络系统、实例管控方法、设备及存储介质
WO2020207267A1 (zh) 网络系统、镜像管理方法、设备及存储介质
WO2020207264A1 (zh) 网络系统、服务提供与资源调度方法、设备及存储介质
CN113726846B (zh) 边缘云系统、资源调度方法、设备及存储介质
US11842208B2 (en) Virtual provisioning with implementation resource boundary awareness
CN113342478B (zh) 资源管理方法、设备、网络系统及存储介质
WO2022161430A1 (zh) 边缘云系统、边缘管控方法、管控节点及存储介质
CN113301078B (zh) 网络系统、服务部署与网络划分方法、设备及存储介质
CN106844198B (zh) 一种分布式调度自动化测试平台及方法
US10013662B2 (en) Virtual resource cost tracking with dedicated implementation resources
CN106533723B (zh) 虚拟资源调度方法、装置及系统
WO2013104217A1 (zh) 基于云基础设施的针对应用系统维护部署的管理系统和方法
CN113301102A (zh) 资源调度方法、设备、边缘云网络、程序产品及存储介质
CN111800285B (zh) 实例迁移方法和装置以及电子设备
CN113296882A (zh) 容器编排方法、设备、系统及存储介质
CN114598665A (zh) 资源调度方法、装置和计算机可读存储介质及电子设备
CN114301909B (zh) 边缘分布式管控系统、方法、设备及存储介质
WO2023066053A1 (zh) 业务请求处理方法、网络设备及计算机可读存储介质
CN114443293A (zh) 一种大数据平台的部署系统及方法
CN113138717B (zh) 节点部署方法、设备及存储介质
Majumdar Cloud-Based Smart-Facilities Management
CN114697219A (zh) 网络控制方法、直播网络的控制方法、设备及系统
CN113918297A (zh) 一种分布式调度系统、分布式调度方法、设备及介质
CN110008130A (zh) 回收站特性的自动化测试方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20787799

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20787799

Country of ref document: EP

Kind code of ref document: A1