CN113300865A

CN113300865A - Management and control method, network system, equipment and storage medium

Info

Publication number: CN113300865A
Application number: CN202010425712.3A
Authority: CN
Inventors: 白常明
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-05-19
Filing date: 2020-05-19
Publication date: 2021-08-24
Anticipated expiration: 2040-05-19
Also published as: CN113300865B

Abstract

The embodiment of the application provides a management and control method, a network system, equipment and a storage medium. In the embodiment of the application, the edge cloud system and the mobile communication network including the MEC node are fused, the central management and control device in the edge cloud system is allowed to manage the target MEC node, and the management and control of the target MEC node are realized through the mutual cooperation among the central management and control device, the MEC edge management and control device and the MEC network management system in the mobile communication network, so that the MEC node closer to the end side can be used for providing edge computing service for a user, the service response time delay is favorably reduced, and the bandwidth cost is reduced.

Description

Management and control method, network system, equipment and storage medium

Technical Field

The present application relates to the field of network technologies, and in particular, to a management and control method, a network system, a device, and a storage medium.

Background

With the arrival of the age of 5G and the internet of things and the gradual increase of cloud computing applications, the requirements of a terminal on the performances of time delay, bandwidth and the like of cloud resources are higher and higher, and the traditional centralized cloud network cannot meet the increasingly high cloud resource requirements of the terminal.

With the advent of edge computing technology, the concept of edge clouds has been created. At present, an edge cloud sinks cloud computing resources and edge cloud nodes to a place close to a terminal user in a distributed deployment mode, but most of the current edge cloud nodes provide edge computing services based on the position of an original Internet Data Center (IDC) machine room, and a certain distance and time delay are still provided from a distance end side.

Disclosure of Invention

Aspects of the present application provide a management and control method, a network system, a device, and a storage medium, which are used to reduce service response latency and reduce bandwidth cost.

An embodiment of the present application provides a network system, including: the method comprises the following steps that central management and control equipment in an edge cloud system, an MEC network management system in a mobile communication network, target multi-access edge computing MEC nodes managed by the central management and control equipment, and MEC edge management and control equipment; the central management and control equipment is used for receiving first monitoring data reported by the MEC edge management and control equipment; managing and controlling IT resources on the target MEC node according to the first monitoring data; the MEC network management system is used for receiving second monitoring data reported by the MEC edge management and control equipment; controlling CT resources on the MEC node according to the second monitoring data; and the MEC edge management and control equipment is used for monitoring the IT resources on the target MEC node and reporting the obtained first monitoring data to the central management and control equipment, and monitoring the CT resources on the target MEC node and reporting the obtained second monitoring data to the MEC network management system.

The embodiment of the present application further provides a management and control method, which is applicable to MEC edge management and control equipment, and the method includes: monitoring IT resources and CT resources on a target MEC node managed by a central management and control device in an edge cloud system in a mobile communication network; reporting first monitoring data obtained by monitoring IT resources to central control equipment, so that the central control equipment can control the IT resources on a target MEC node; and reporting second monitoring data obtained by monitoring the CT resources to an MEC network management system in the mobile communication network so that the MEC network management system can control the CT resources on the MEC nodes.

The embodiment of the present application further provides a management and control method, which is applicable to a central management and control device in an edge cloud system, and the method includes: receiving first monitoring data reported by MEC edge management and control equipment, wherein the first monitoring data is obtained by the MEC edge management and control equipment monitoring IT resources on a target MEC node managed by central management and control equipment in a mobile communication network; and managing and controlling the IT resources on the target MEC node according to the first monitoring data.

The embodiment of the present application further provides a management and control method, which is applicable to an MEC network management system in a mobile communication network, and the method includes: receiving second monitoring data reported by the MEC edge management and control equipment, wherein the second monitoring data are obtained by monitoring CT resources on target MEC nodes managed by central management and control equipment in an edge cloud system in a mobile communication network by the MEC edge management and control equipment; and managing and controlling the CT resources on the target MEC node according to the second monitoring data.

The embodiment of the present application further provides an MEC edge management and control device, including: a memory and a processor; a memory for storing a computer program; a processor coupled with the memory for executing the computer program for: monitoring IT resources and CT resources on a target MEC node managed by a central management and control device in an edge cloud system in a mobile communication network; reporting first monitoring data obtained by monitoring IT resources to central control equipment, so that the central control equipment can control the IT resources on a target MEC node; and reporting second monitoring data obtained by monitoring the CT resources to an MEC network management system in the mobile communication network so that the MEC network management system can control the CT resources on the MEC nodes.

An embodiment of the present application further provides a central management and control device, including: a memory, a processor, and a communications component; a memory for storing a computer program; a processor coupled with the memory for executing the computer program for: receiving first monitoring data reported by MEC edge management and control equipment through a communication component, wherein the first monitoring data is obtained by monitoring IT resources on a target MEC node managed by central management and control equipment in a mobile communication network by the MEC edge management and control equipment; and managing and controlling the IT resources on the target MEC node according to the first monitoring data.

An embodiment of the present application further provides an MEC network management device, including: a memory, a processor, and a communications component; a memory for storing a computer program; a processor coupled with the memory for executing the computer program for: receiving second monitoring data reported by the MEC edge control equipment through the communication assembly, wherein the second monitoring data are obtained by monitoring CT (computer tomography) resources on target MEC nodes managed by central control equipment in an edge cloud system in a mobile communication network by the MEC edge control equipment; and managing and controlling the CT resources on the target MEC node according to the second monitoring data.

The present application further provides a computer-readable storage medium storing a computer program, which, when executed by one or more processors, causes the one or more processors to implement the steps in any one of the management and control methods provided by the present application.

In the embodiment of the application, the edge cloud system and the mobile communication network including the MEC node are fused, the central management and control device in the edge cloud system is allowed to manage the target MEC node, and the management and control of the target MEC node are realized through the mutual cooperation among the central management and control device, the MEC edge management and control device and the MEC network management system in the mobile communication network, so that the MEC node closer to the end side can be used for providing edge computing service for a user, the service response time delay is favorably reduced, and the bandwidth cost is reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1a is a schematic structural diagram of a network system according to an exemplary embodiment of the present application;

fig. 1b is a schematic structural diagram of another network system provided in an exemplary embodiment of the present application;

fig. 1c is an interaction flowchart of a nanotube MEC node according to an exemplary embodiment of the present disclosure;

fig. 1d is an interaction flowchart of another nanotube MEC node provided in an exemplary embodiment of the present application;

fig. 2a is a schematic structural diagram of another network system provided in an exemplary embodiment of the present application;

fig. 2b is a schematic structural diagram of a central management and control device, an MEC network management system, and an MEC edge management and control device according to an exemplary embodiment of the present disclosure;

FIG. 3 is a schematic flow chart of a control method provided in an exemplary embodiment of the present application;

FIG. 4 is a schematic flow chart diagram of another method of management provided in an exemplary embodiment;

FIG. 5 is a schematic flow chart diagram illustrating yet another method of management provided in an exemplary embodiment of the present application;

fig. 6 is a schematic structural diagram of an MEC edge management and control apparatus according to an exemplary embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a central management and control device according to an exemplary embodiment of the present application;

fig. 8 is a schematic structural diagram of an MEC network management device according to an exemplary embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

For the technical problem, in the embodiment of the present application, an edge cloud computing solution is provided, in which an IT (Internet Technology) and a CT (Communication Technology) network are fused, that is, an edge cloud system and a mobile Communication network including a multi-access edge computing (MEC) node are fused, a central management and control device is allowed to manage a target MEC node, and management and control of the target MEC node are realized through mutual cooperation between the central management and control device, the MEC edge management and control device, and an MEC network management system in the mobile Communication network, so that an MEC node closer to an end side can be used to provide an edge computing service for a user, service response delay is reduced, and bandwidth cost is reduced.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Fig. 1a is a schematic structural diagram of a network system according to an exemplary embodiment of the present application. As shown in fig. 1a, the network system 100 includes: a central management and control device 101 in the edge cloud system 104, and a target MEC node 102a and an MEC network management system 103 in the mobile communication network 105.

The edge cloud system 104 in this embodiment is a cloud computing platform constructed on an edge infrastructure based on cloud computing technology and edge computing capability, and is a cloud platform having computing, networking, storage, security, and other capabilities at an edge location. The edge cloud is a relative concept, and refers to a cloud computing platform relatively close to an end side, or the edge cloud is different from a central cloud or a traditional cloud computing platform, the central cloud or the traditional cloud computing platform may include a data center or a computer room with a large resource scale and a centralized location, the edge cloud is composed of a plurality of edge cloud nodes 106, the resource scale of a single edge cloud node 106 is small, but the number of the edge cloud nodes 106 is large, so that the coverage range of the edge cloud is wider.

In the edge cloud system 104 of this embodiment, a central management and control device 101 is deployed, and the central management and control device 101 uses an edge cloud node 106 as a management and control object to perform unified management and control on at least one edge cloud node 106 in the edge cloud system 104 in terms of resource scheduling, mirror image management, instance management, operation and maintenance, network, security, and the like, so as to place cloud computing services into each edge cloud node 106 for processing. In terms of deployment implementation, the central management and control device 101 may be deployed in one or more cloud computing data centers, or may be deployed in one or more conventional data centers, and the central management and control device 101 may also be deployed in one or more edge cloud nodes 106 managed by the central management and control device, which is not limited in this embodiment.

For the edge cloud node 106, various resources, such as computing resources like CPU and GPU, storage resources like memory and hard disk, and network resources like bandwidth, may be provided externally. In addition, the edge cloud node 106 may also create a corresponding instance according to the mirror image, and provide various cloud computing services to the outside through the instance. The image here refers to a basic file required to create an instance in the edge cloud node 106, and may be, for example, an image file such as an operating system, an application, or an operation configuration required to provide a cloud computing service for a user, and may be a file that meets the computing deployment requirement of the edge cloud node 106 and is manufactured according to a certain format according to a specific series of files. In addition, the image may be various forms, such as a Virtual Machine (VM) image file, a container (Docker) image file, or various types of application package files, and the image form may be related to a virtualization technology that needs to be used by the cloud computing service, which is not limited in this embodiment. Corresponding to mirroring, the implementation of an instance may be a virtual machine, a container, an application, or the like.

In a deployment implementation, the edge cloud system 104 is deployed near the end side, for example, may be deployed within a certain level of territory near the end side. The designated region range (the designated region range may be a continent, a country, a province, etc.) may be longitudinally classified, and may be sequentially divided into a plurality of levels from high to low, such as a first level, a second level, a third level, a fourth level, etc., which may be determined according to an application scenario. Alternatively, the designated geographical area may be classified vertically according to the administrative level within the designated geographical area, for example, the designated geographical area may be divided vertically into: regional level, province level, city level, district level, etc. In this scenario, the central cloud system is typically deployed at a regional level, the edge cloud nodes 106 in the edge cloud system 104 are typically deployed at a province level, a small number of main prefecture levels and prefecture levels deploy the edge cloud nodes 106, but deployment of the edge cloud nodes 106 is difficult or impossible at most prefecture levels and prefecture levels. Therefore, the edge cloud nodes 106 are located at a certain distance from the end-side devices located at the local city level and the prefecture level, and a certain communication delay exists between the end-side devices and the edge cloud nodes 106.

In view of the above problems, the network system 100 provided in this embodiment introduces the mobile communication network 105 including the MEC node 102, merges cloud networks (i.e., the edge cloud and the mobile communication network), and provides an edge computing service for the end-side device by means of the MEC node 102 closer to the end-side device in the mobile communication network 105, so as to achieve the purpose of reducing communication delay.

In this embodiment, the network architecture and the adopted communication system of the mobile communication network 105 are not limited, and all the mobile communication networks 105 including the MEC node 102 are suitable for the embodiment of the present application. For example, the mobile communication network 105 may be a 5G mobile communication network (referred to as a 5G network for short), or may be a higher-standard mobile communication network that may appear in the future. The mobile communication network 105 of any standard is divided from the application point of view, and its architecture mainly includes but is not limited to: an Access Network (RAN) 107 and a Core Network (Core Network, CN) 108; the architecture mainly includes a Backbone Network (Backbone Network) and an access Network, which are divided from the transmission perspective. Further, the mobile communication network may further include: support Network (Supporting Network). Both the access network 107 and the core network 108 include some functional entities (or called network elements). For example, the base station is a main network element in the access network 107, and is mainly responsible for providing a wireless access function for an end user (e.g., a mobile phone, a tablet computer, etc. of the user). The core network 108 is used as a "management center" of the mobile communication network, and includes a network element responsible for access and mobility management, a network element responsible for data grouping, a network element responsible for charging control, and the like, and is mainly responsible for managing data of the terminal user, and performing related processing such as processing, distribution, charging, and the like on the data, so as to achieve the purpose of "route switching".

The network elements included in the access network 107 and the core network 108 of the mobile communication network 105 may also be different according to different network systems. Taking a 5G network as an example, the access network 107 in the 5G network mainly includes a 5G base station; the 5G base station is mainly used for providing a 5G air interface protocol function and supporting communication with the user equipment and the 5G core network. According to the logic function division, the 5G base station can be divided into a 5G baseband unit and a 5G radio frequency unit, and the two units can be connected through a Common Public Radio Interface (CPRI) or an eccri interface; the 5G baseband unit is responsible for new radio, NR, baseband protocol processing, and the 5G radio frequency unit mainly completes conversion between NR baseband signals and radio frequency signals and transceiving processing functions of NR radio frequency signals. From the device architecture perspective, the 5G base station may employ, but is not limited to: the Antenna comprises a Baseband processing Unit, an Active Antenna processing Unit (BBU-AAU), a distribution Unit, a Centralized Unit, an Active Antenna processing Unit (CU-DU-AAU), a BBU-RRU-Antenna (Antenna), a CU-DU-RRU-Antenna and the like. From the device morphology perspective, the 5G base station may include, but is not limited to: lamp pole basic station, well lid basic station, unmanned aerial vehicle basic station, 5G blade formula basic station, liquid cooling basic station etc.. Accordingly, the 5G Core Network (5G Core Network, 5GC)108 includes, but is not limited to, the following Network functions and entities: network elements such as an Authentication Server Function (AUSF), a User Plane Function (UPF), an Access and Mobility Management Function (AMF), a Unified Data Management (UDM), a Network open Function (NEF), a Session Management Function (SMF), a Network Slice Selection Function (NSSF), a Network storage Function (NF) and NRF, a Policy Control Function (PCF), and an Application layer Function (AF) are not shown in the figure.

In this embodiment, the mobile communication network 105 includes, in addition to the above listed network elements: an MEC node 102 and an MEC network management system 103. MEC node 102 includes, among other things, a series of edge infrastructures including, but not limited to: distributed Data Centers (DCs), wireless rooms or clusters, edge devices such as computing devices and/or storage devices, and corresponding network environments, among others. The MEC node 102 may provide various resources to the outside, such as computing resources like CPU and GPU, storage resources like memory and hard disk, network resources like bandwidth, and the like. In addition, the MEC node 102 may also create a corresponding instance according to the mirror image, and provide various cloud computing services to the outside through the instance. See above for a description of the mirror image.

In the mobile communication network 105, the MEC network management system 103 manages and controls at least one MEC node 102 in the mobile communication network 105 in various aspects such as resource scheduling, operation and maintenance, network, security, and the like, by using the MEC node 102 as a management and control object. In terms of deployment implementation, the MEC network management system 103 may be deployed in the core network separately as an independent core network element, or the function of the MEC network management system 103 may also be deployed in the core network in a distributed manner on a related network element, for example, AMF, PGW, PCF, and the like. In fig. 1a and 1b, the MEC network management system 103 is illustrated as an example and deployed in a core network as an independent network element, but is not limited thereto.

In this embodiment, the number of MEC nodes 102 is not limited, and may be one or more, for example. It is noted that the location, number, capabilities, and contained infrastructure of different MEC nodes 102 may or may not be the same. In the present embodiment, the deployment location of the MEC node 102 in the mobile communication network 105 is not limited. For example, as shown in fig. 1a in the case where MEC node 102 is deployed in a RAN, after the base station(s), the terminal-initiated request and related data may reach edge cloud system 104 via the base station, MEC node 102. In an application scenario where the MEC node 102 is deployed on the RAN side, the network system 100 may provide some low-latency edge computing services, such as drone delivery service, autopilot, telemedicine diagnosis, robotic collaboration, telesurgery, and so on. For another example, after the Control Plane/User Plane (C/U) function of the core network 108 is separated, the User Plane Gateway (GW-UP) function moves down, and may move down to the RAN side, or may move down to the edge of the 5G core network, as shown in fig. 1b, and GW-UP moves down to the edge of the core network, and the MEC node 102 may be deployed at GW-UP, and in this scenario, the network system 100 may provide some low-latency and high-bandwidth edge computing services, such as Augmented Reality (AR), Virtual Reality (VR), mobile video monitoring, mobile broadcasting, public safety, and high definition video, for the end-side User. The GW-UP corresponds to a GW-CP, and the GW-CP corresponds to a control Plane (C-Plane) in a 5G core network and resides on a CN side. In fig. 1a and 1b, the number of MEC nodes 102 is illustrated as 2, but the present invention is not limited thereto.

Specifically, a cooperative channel for performing cooperative management and control on the target MEC node 102 is established between the central management and control device 101 and the MEC network management system 103, and the target MEC node 102a is managed based on the cooperative channel, so that the target MEC node 102a can be used to provide edge computing services, such as the above-listed services of automatic driving, remote medical diagnosis, robot cooperation, remote surgery, AR, VR, mobile video monitoring, mobile broadcasting, public security, high-definition video, by virtue of the advantage that the target MEC node 102a is closer to the end side. In the present embodiment, the MEC node 102 hosted by the central hosting apparatus 101 is referred to as a target MEC node and is labeled 102a in fig. 1a and 1 b. The number of target MEC nodes 102a may be one or multiple, and the number of target MEC nodes 102a is illustrated as 1 in fig. 1a and 1b, but is not limited thereto.

In this embodiment, a physical link exists between the central control device 101 and the target MEC node 102a, before the central control device 101 and the MEC network management system 103 establish a cooperative channel, the physical link is in a disabled state, and the central control device 101 cannot manage the target MEC node 102 a; after the central management and control device 101 establishes the cooperative channel with the MEC network management system 103, the physical link is enabled and is in an available state, which means that the central management and control device 101 can manage the target MEC node 102 a. Based on the physical link, the central management and control device 101 may establish a direct channel with the target MEC node 102a, and then manage the target MEC node 102a based on the direct channel. After the target MEC node 102a is managed by the central management and control device 101, the identity and the status of the target MEC node 102a in the edge cloud system 104 are the same as or similar to those of the edge cloud node 106, and the central management and control device 106 may perform various kinds of management on the target MEC node 102 a.

With reference to the interaction flowchart shown in fig. 1c, a description is given below of a flow for establishing a cooperative channel between the central control device 101 and the MEC network management system 103 for cooperatively controlling the target MEC node 102a, and managing the target MEC node 102a based on the cooperative channel, where the embodiment shown in fig. 1c includes the following steps:

11c, each MEC node 102 in the mobile communication network 105 reports MEC registration information to the MEC network management system 103.

12c, the target terminal 109 reports the terminal registration information to the MEC network management system 103.

13c, the MEC network management system 103 provides the information of candidate MEC nodes which can be managed in the mobile communication network 105 to the central management and control equipment 101.

14c, the central management and control equipment 101 determines a target MEC node 102a from the candidate MEC nodes.

15c, the central management and control device 101 initiates a resource admission application for the target MEC node 102a to the MEC network management system 103, so as to establish a cooperative channel with the MEC network management system 103.

16c, the central management and control equipment 101 manages the target MEC node 102a based on a through channel between the central management and control equipment and the target MEC node 102 a.

In this embodiment, the sequence of step 11c and step 12c is not limited, for example, step 11c and step 12c may be performed simultaneously; step 11c may be performed first, and then step 12c may be performed; step 12c may be implemented first, and then step 11c may be implemented, which may be determined according to the sequence in which the target terminal 109 and the MEC node initiate registration to the MEC network management system 103.

In step 11c, the MEC registration information includes information of the candidate MEC node, where the information of the MEC node includes information that can uniquely identify the MEC node, such as an ID, a MAC address, an IP address, location information, and the like of the MEC node, and may also include some other information, such as a resource type, an available resource amount, and the like included in the MEC node. In step 12c, the terminal registration information includes information of the target terminal 109, the target terminal 109 is a terminal that needs to use the edge computing service in the mobile communication network 105, and the information of the target terminal includes information that can uniquely identify the target device, such as an IP address, a MAC address, a device serial number, and the like of the target terminal, and may also include some other information, such as location information of the target terminal, information of a base station to which the target terminal belongs, and the like.

In step 13c, the MEC network management system 103 may determine candidate MEC nodes capable of being managed according to a certain policy. For example, an MEC node with spare resources may be considered a candidate MEC node that may be hosted. For another example, an MEC node having an amount of free resources greater than a set threshold may be regarded as a candidate MEC node that can be managed. Still alternatively, MEC nodes with specified resources (e.g., GPUs or CPUs) may be taken as candidate MEC nodes that can be hosted. Wherein the information of the candidate MEC node comprises: the identification, geographic location, and resource information (e.g., number of resources, type of resources) that can be hosted on the candidate MEC node.

In this embodiment, a specific implementation manner of providing, by the MEC network management system 103, information of candidate MEC nodes that can be managed in the mobile communication network 105 to the central management and control device 101 is not limited. For example, the MEC network management system 103 may actively push candidate MEC node information to the central management and control device 101; the MEC network management system 103 may also receive request information of the central management and control device 101, where the request information includes geographic locations, resource quantities, resource types, and the like of MEC nodes that need to be managed, and the MEC network management system 103 provides information of candidate MEC nodes that can be managed in the mobile communication network 105 to the central management and control device 101 according to the request information.

The candidate MEC nodes that can be managed in the mobile communication network 105 have resource information (e.g., resource quantity and resource type) that can be managed by the central management and control device 101, and in this embodiment, how the MEC network management system 103 determines which resource information can be managed by the central management and control device 101 is not limited. For example, the MEC network management system 103 may provide all resources in the candidate MEC nodes to the central management and control device 101, so that the central management and control device 101 manages all resources in the target MEC nodes determined from the candidate MEC nodes; or, the MEC network management system 103 may reserve a part of resources in the candidate MEC nodes, and provide the remaining resource information to the central management and control device 101 so that the central management and control device 101 manages the remaining resources in the target MEC node determined from the remaining resource information; or, the MEC network management system 103 selects resource information meeting the requirements according to the requirements of the central management and control device 101, and provides the resource information to the central management and control device 101, so that the central management and control device 101 can manage the resources meeting the requirements in the target MEC node determined by the central management and control device 101.

For step 14c, the central management and control device 101 determines a target MEC node 102a from the candidate MEC nodes according to the edge calculation requirement information and the information of the candidate MEC nodes. The edge computing requirement information may include, but is not limited to, MEC node selection parameters, resource selection parameters, and the like. Alternatively, the edge computing demand information may be provided to the central managing device 101 by the edge computing service demander. For example, the central control device 101 may provide a human-computer interaction interface for the edge computing service demander, and the edge computing service demander may submit the edge computing requirement information to the central control device 101 through the human-computer interaction interface provided by the central control device 101. The implementation form of the human-computer interaction interface is not limited in this embodiment.

In an optional embodiment, the man-machine interface provided by the central control apparatus 101 includes a query page and a purchase page. For an operator or an edge computing service demander of the network system 100, the operator or the edge computing service demander may enter an inquiry page provided by the central management and control device 101, and input edge computing requirement information on the inquiry page to inquire whether an MEC node meeting the edge computing requirement information exists in the network system 100; accordingly, the central management and control device 101 may obtain the edge calculation requirement information, determine the target MEC node 102a meeting the edge calculation requirement from the candidate MEC nodes according to the edge calculation requirement information, and after determining the target MEC node 102a, may return information of the MEC node meeting the edge calculation requirement information to the operator or the edge calculation service demander through the query page. Alternatively, for the edge computing service demander, a purchase page provided by the central management and control device 101 may be entered, and by inputting the edge computing requirement information on the purchase page to request that the corresponding edge computing service be deployed on the MEC node meeting the edge computing requirement information, the edge computing requirement information is provided to the central management and control device 101, and accordingly, the central management and control device 101 may determine the target MEC node 102a meeting the edge computing requirement from the candidate MEC nodes.

It should be noted that, besides the above man-machine interface manner, the central management and control device 101 may also obtain the edge computing requirement information in other manners. For example, the edge computing service demander may also embed edge computing requirement information in the central management and control device 101 in advance, and the central management and control device 101 may determine the target MEC node 102a from the candidate MEC nodes according to the embedded edge computing requirement information and the information of the candidate MEC nodes. Alternatively, the edge computing service demander may transmit the edge computing requirement information to the central control device 101 in a wired or wireless communication manner through other devices that can communicate with the central control device 101, such as a terminal device or a configuration device, and the central control device 101 may receive the edge computing requirement information transmitted by the other devices.

In an optional embodiment, the central management and control device 101 may analyze an MEC node selection parameter and a resource selection parameter from the edge calculation requirement information; and determining a target MEC node and target resources needing to be managed on the target MEC node from the candidate MEC nodes according to the MEC node selection parameters and the resource selection parameters and by combining the information of the candidate MEC nodes.

The resource selection parameters include the number of resources, the type of resources, and the like. The number of resources may be 1, 5, 100, etc., and the types of resources may include, but are not limited to, computing resources, storage resources, network resources, etc. In an alternative embodiment, the MEC node selection parameter includes: quality of Service (QoS) requirements for scheduling domain and/or edge computing services; where the dispatch domain points to an area where edge computing services need to be deployed, which determines the geographic location of the target MEC node 102 a. The QoS requirements of the edge computing service may include the requirements of the edge computing service for network latency, load conditions, and/or bandwidth costs, among others. Based on this, the central management and control device 101 may select, as the target MEC node 102a, an MEC node that can meet the scheduling domain and/or QoS requirements according to the geographic location of the candidate MEC node and the resource information that can be managed on the candidate MEC node.

For example, the central management and control device 101 may select, according to the scheduling domain, the MEC node 102 pointed by the scheduling domain as the target MEC node 102a in combination with the geographic location of the candidate MEC node. Or, the central management and control device 101 may further select, according to QoS requirements of the edge computing service, such as requirements of network latency, load conditions, and/or bandwidth costs, the MEC node 102 that meets the requirements of the network latency, the load conditions, and the bandwidth costs from the candidate MEC nodes as the target MEC node 102 a. Of course, the central management and control device 101 may also select, as the target MEC node 102a, the MEC node 102 that can simultaneously satisfy the requirements of the scheduling domain and the QoS, in combination with the QoS requirements of the scheduling domain and the edge computing service, and in combination with the geographic location of the candidate MEC node and the resource information (e.g., resource amount, resource type, etc.) available for admission.

It should be noted that, in the embodiment of the present application, a specific implementation manner of the center management and control device 101 acquiring the target MEC node 102a is not limited, the target MEC node 102a may be acquired according to the method provided in step 13c, and other manners may also be adopted. For example, the central management and control device 101 and the MEC network management system 103 may negotiate in advance a target MEC node 102a that needs to be managed.

In step 15c, after determining the target MEC node 102a, the central management and control device 101 initiates a resource admission application for the target MEC node 102a to the MEC network management system 103, so as to establish a cooperative channel with the MEC network management system 103.

Optionally, for a resource admission application initiated by the central management and control device 101, the MEC network management system 103 may not respond, and after the central management and control device 101 initiates the resource admission application, a cooperative channel is established with the MEC network management system 103 by default. Or, optionally, after the central management and control device 101 initiates a resource admission application, if the MEC network management system 103 receives the resource admission application, a response message is returned to the central management and control device 101; after receiving a response message returned by the MEC network management system 103, the central management and control device 101 determines that a cooperation channel is established with the MEC network management system 103; otherwise, if the response message returned by the MEC network management system 103 is not received, a resource admission application for the target MEC node 102a may be initiated to the MEC network management system 103 again.

After the cooperative channel is established with the MEC network management system 103, the central management and control device 101 obtains the admission authority for the target MEC node 102a, and then in step 16c, starts to admit the target MEC node 102 a. Optionally, the central management and control apparatus 101 may manage the target MEC node 102a based on a through channel between the central management and control apparatus and the target MEC node 102 a. Or, the central management and control device 101 may also manage the target MEC node 102a through a cooperative channel between the central management and control device and the MEC network management system 103 and a channel between the MEC network management system 103 and the target MEC node 102 a.

The central management and control device 101 may manage the target MEC node 102a, and includes at least one of the following management and control:

infrastructure management and control: managing and controlling the infrastructure of the target MEC node 102 a;

platform capacity management and control: managing and controlling the platform capacity of the target MEC node 102 a;

network channel management and control: a pass-through channel with target MEC node 102a is managed.

Regarding infrastructure management: the infrastructure of target MEC node 102a includes, but is not limited to: distributed Data Centers (DCs), wireless rooms or clusters, devices such as computing devices or storage devices, and corresponding network environments, etc. DC. The computer room or the cluster comprises a plurality of physical machines, and each physical machine can be provided with a plurality of resources such as virtual machines and containers. The management and control of the infrastructure of the target MEC node 102a mainly refers to a process of managing and controlling the infrastructure that can be managed in the target MEC node 102 a. The governing process includes but is not limited to: instruct the target MEC node 102a to report infrastructure information that can be managed, instruct the target MEC node 102a to configure infrastructure resources (e.g., virtual machines, containers, etc.) required by the central management and control device 101, and so on.

Regarding platform capability management: the platform capabilities of the target MEC node 102a refer to some processing capabilities that the target MEC node 102 has, such as operation and maintenance, alarms, acceleration, and the like. The step of managing and controlling the platform capability of the target MEC node 102a mainly refers to a process of determining whether the target MEC node 102a has some capabilities required by the edge cloud system 104 and capabilities required for providing edge computing services, and if not, controlling the target MEC node 102a to perform operations such as configuration or installation of related programs, so that the target MEC node 102a has corresponding capabilities. For example, a game is deployed on the target MEC node 102a, and if the game requires the use of an acceleration service, the central control device 101 needs to determine whether the target MEC node 102a supports an acceleration service protocol, and if not, the target MEC node 102a is controlled to install the acceleration service protocol; if so, further determining whether the protocol version conforms to the latest version, and if not, updating the acceleration service protocol to the latest version to perform acceleration management and control on the target MEC node 102 a. For another example, the edge cloud system 104 requests each edge cloud node to automatically report to the central control device 101 when an alarm event occurs, so that the central control device 101 needs to determine whether the target MEC node 102a has an automatic alarm capability, and if not, the target MEC node 102a is controlled to perform automatic alarm configuration, so that the target MEC node 102a has the automatic alarm capability.

Regarding through channel management and control: the direct channel between the central control apparatus 101 and the target MEC node 102a needs to meet the requirements of the edge cloud system 104 or the edge computing service demander on data transmission reliability, security, and the like. Based on this, the central management and control device 101 may manage and control a network transmission protocol, an adopted encryption protocol, and the like used by the direct channel, for example, a network transmission protocol (TCP or UDP), an encryption protocol, and the like negotiated with the target MEC node 102a, and establish a three-layer, four-layer, or higher channel with the target MEC node 102a on the direct channel according to the negotiated network transmission protocol and encryption protocol, so as to perform secure data transmission.

With reference to the interaction flowchart shown in fig. 1d, another embodiment of establishing a cooperation channel for cooperatively controlling the target MEC node 102a between the central control device 101 and the MEC network management system 103, and managing the target MEC node 102a based on the cooperation channel includes the following steps:

11d, each MEC node 102 in the mobile communication network 105 reports MEC registration information to the MEC network management system 103.

12d, the target terminal 109 reports the terminal registration information to the MEC network management system 103.

13d, the MEC network management system 103 provides the information of candidate MEC nodes which can be managed in the mobile communication network 105 to the central management and control equipment 101.

14d, the central management and control equipment 101 determines a target MEC node 102a from the candidate MEC nodes.

15d, the central management and control equipment 101 initiates a resource admission application for the target MEC node 102a to the MEC network management system 103.

16d, the central management and control device 101 sends the data distribution rule and the resource allocation rule corresponding to the target MEC node 102a to the MEC network management system 103.

17d, configuring a data distribution rule and a resource configuration rule by the MEC network management system 103 to establish a cooperative channel with the central control device 101.

18d, the central management and control equipment 101 manages the target MEC node 102a based on the through channel between the central management and control equipment and the target MEC node 102 a.

In this embodiment, the sequence of the step 16d and the step 15d is not limited, for example, the step 16d and the step 15d may be implemented simultaneously; step 16d may be performed first, and then step 15d may be performed; step 15d may be performed first, and then step 16d may be performed, which is not limited.

For step 15d and step 16d, in the process of initiating a resource admission application to the MEC network management system, the central management and control device 101 may send a data distribution rule corresponding to the target MEC node 102a to the MEC network management system 103, and may also send a resource configuration rule corresponding to the target MEC node 102a to the MEC network management system 103. The central management and control device 101 may carry the data distribution rule and the resource configuration rule in the resource admission application and send the resource distribution rule and the resource configuration rule to the MEC network management system 103. Or, after sending the resource admission application, the data offloading rule and the resource configuration rule may also be sent to the MEC network management system 103 through an independent communication process. Further, the data distribution rule and the resource allocation rule may be sent to the MEC network management system 103 through the same communication process; or, the data offloading rule and the resource allocation rule may be sent to the MEC network management system 103 in different communication processes.

Regarding data splitting rules: the central control device 101 sends a data distribution rule corresponding to the target MEC node 102a to the MEC network management system 103, so that the MEC network management system 103 establishes a data plane channel between the target terminal 109 and the target MEC node 102 a.

Among them, the target terminal 109 is a terminal that needs to use the edge computing service in the mobile communication network 105. In the process that the MEC network management system 103 provides the candidate MEC node information to the central management and control device 101, the information of the target terminal 109 may also be provided to the central management and control device 101.

In this embodiment, the data offloading rule is used to distribute data traffic required by the edge computing service to the target MEC node 102a, so that the edge computing service can enjoy the edge computing service with high efficiency and low latency. In this embodiment, the data splitting rule is not limited, and in an optional embodiment, the splitting may be performed according to an IP address, where the data splitting rule includes: mapping relation of IP address of edge computing service and MAC address of MEC node. For example, the data distribution rule issued by the central control device 101 is as follows: the terminal IP address b1 — > MAC address d1 of MEC node c1 corresponding to the edge computing service a 1; the terminal IP address b2 — > MAC address d2 of MEC node c2 corresponding to the edge computing service a 2; after the MEC network management system 103 configures the data distribution rule, when the traffic from the IP address b1 arrives, the traffic is distributed to the MEC node c1 corresponding to the MAC address d1 according to the configured data distribution rule; when the traffic comes from the IP address b2, the traffic is distributed to the MEC node c2 corresponding to the MAC address d2 according to the configured data distribution rule. In another optional embodiment, the splitting may be performed according to a domain name, and the data splitting rule includes: and the mapping relation of the IP address of the MEC node is greater than the traffic domain name corresponding to the edge computing service. For example, the data distribution rule issued by the central control device 101 is as follows: the IP address h1 of the traffic domain name f1 — > MEC node g1 corresponding to the edge computing service e 1; the IP address h2 of the traffic domain name f2 — > MEC node g2 corresponding to the edge computing service e 2; after the MEC network management system 103 configures the data distribution rule, when the traffic from the domain name f1 arrives, the traffic is distributed to the MEC node g1 corresponding to the IP address h1 according to the configured data distribution rule; when the traffic comes from the domain name f2, the traffic is distributed to the MEC node g2 corresponding to the IP address h2 according to the configured data distribution rule.

For step 17d, in an optional embodiment, the MEC network management system 103 configures a data offloading rule to a UPF network element connected to the target MEC node 102a in the mobile communication network 105, and the UPF network element offloads the data from the target terminal 109 to the target MEC node 102a, so as to establish a data plane channel between the target terminal 109 and the target MEC node 102 a. Wherein, the UPF network element is responsible for distributing and guiding the traffic of the edge network to the target MEC node 102 a.

Regarding the resource allocation rules: the central control equipment 101 sends a resource configuration rule corresponding to a target MEC node 102a to the MEC network management system 103; the MEC network management system 103 configures the resource configuration rule into the target MEC node 102, so that the target MEC node 102a performs resource configuration for the edge computing service.

In this embodiment, the resource configuration rules include some rules or policies that instruct the target MEC node 102a to make resource reservations for the edge computing service. For example, target MEC node 102a has a total of 10 virtual machine resources, numbered virtual machine 1, virtual machine 2, … …, and virtual machine 10, respectively. Deploying 3 edge computing services on the target MEC node 102a, namely an edge computing service a1, an edge computing service a2 and an edge computing service A3, wherein each edge computing service requires 2 virtual machine resources, and the resource allocation rule may indicate that the target MEC node 102a randomly reserves 6 virtual machine resources for the 3 edge computing services, and the 6 virtual machine resources can be used by the 3 edge computing services; alternatively, the resource configuration rule may instruct the target MEC node 102a to allocate virtual machine 1 and virtual machine 2 for edge compute service a1, virtual machine 3 and virtual machine 4 for edge compute service a2, and virtual machine 5 and virtual machine 6 for edge compute service A3. For the target MEC node 102a, resource reservation is performed for the edge computing service according to the resource allocation rule.

In practical applications, the information related to the target MEC node 102a may change. The MEC network management system 103 and the central management and control device 101 also perform information synchronization for the target MEC node 102 a. That is, the MEC network management system 103 synchronizes the change information related to the target MEC node 102a occurring in the mobile communication network 105 to the central management and control device 101; the central management and control device 101 also synchronizes the change information related to the target MEC node 102a occurring in the edge cloud system 104 to the MEC network management system 103.

For example, the MEC network management system 103 notifies the central management and control device 101 that an edge computing service process is finished on a target MEC node 102a in the mobile communication network 105, the central management and control device 101 determines to release resources occupied by the edge computing service and sends a notification to the MEC network management system 103, and the MEC network management system 103 releases the resources occupied by the edge computing service on the target MEC node 102 a.

Further, over time, the requirements of the edge computing service and the information of the target terminal 109 may change, and the distribution rule needs to be adaptively changed in order to successfully provide the target terminal 109 with the correct edge computing service. For example, a new edge computing service needs to configure resources on the target MEC node 102a, but the resources on the target MEC node 102a do not meet the requirements of the new edge computing service, and at this time, the resources of the original edge computing service on the target MEC node are idle, so that the offloading rule needs to be modified, and part of the resources originally allocated to the original edge computing service is allocated to the new edge computing service. Or, if the current MEC node has insufficient resources, modifying the data distribution rule, and allocating resources for the new edge computing service by using other target MEC nodes. Based on this, the central management and control device 101 may send the data offloading rule to the MEC network management system 103 again when the data offloading rule changes, so that the MEC network management system 103 updates the data plane channel between the target terminal 109 and the target MEC node 102 a.

For example, if a new edge computing service is to be deployed on the target MEC node 102a, the central management and control device 101 may notify the MEC network management system 103 to allocate resources to the new edge computing service on the target MEC node 102a, but the resources on the target MEC node 102a are insufficient, the MEC network management system 103 may notify the central management and control device 101 to modify the offloading rules and send the modified offloading rules to the MEC network management system 103, and the MEC network management system 103 allocates resources to the new edge computing service on the target MEC node 102a according to the modified offloading rules.

In addition, over time, the original edge computing service process on the target MEC node 102 may end, which releases the resources occupied by the original edge computing service; new edge computing services may also be deployed, with a reset of resources on the MEC node. In an optional embodiment, the central management and control device 101 sends a new resource resetting or releasing message to the MEC network management system 103 when resetting or releasing the resource of the target MEC node 102a, so that the MEC network management system 103 controls the target MEC node 102a to reset or release the resource.

For example, the target MEC node 102a has deployed thereon the edge computing service B1, the edge computing service B2, the edge computing service B1, and the edge computing service B2 occupying resources of the target MEC node 102 a. After a period of time, the life cycle of the edge computing service B1 is ended, the MEC network management system 103 notifies the central control device 101 of the information of resource reduction, and the central control device 101 determines to release the resource on the target MEC node 102a, and then notifies the MEC network management system 103 to release the resource occupied by the target MEC node 102 a. After a while, the edge computing service demander needs to deploy the edge computing service B3 on the target MEC node 102a, the central management and control equipment 101 notifies the MEC network management system 103 to allocate resources for the edge computing service B3 at the target MEC node 102a, but there are not enough resources on the target MEC node 102a to allocate to the edge computing service B3, at this point, the MEC network management system 103 notifies the central management and control equipment 101 to modify the distribution rules, the central management and control equipment 101 modifies the distribution rules, and allocates part of the resources originally configured to the edge computing service B2 to the edge computing service B3 to form new distribution rules, the central management and control equipment 101 sends the new distribution rules to the MEC network management system 103, the MEC network management system 103 sends the new distribution rules to the UPF network element for configuration, after the configuration is successful, the target MEC node 102a successfully deploys the edge computing service B3, completing the resource reset.

After hosting, the central managing and controlling device 101 may deploy an edge cloud platform on the target MEC node 102a, where the edge cloud platform includes various resources required for providing the edge computing service, such as an edge cloud operating system, various types of software, and an instance required for the edge computing service, and the target MEC node 102a runs the instance to provide the edge computing service for the target terminal 109. Further, if the target MEC node 102a is a bare machine, the central management and control device 101 may further install an operating system for the target MEC node 102a, perform initial configuration, activation, and other related operations, which may be specifically determined according to the type of the target MEC node 102 a.

In the embodiment of the application, an edge cloud computing scheme for fusion of an IT and a CT network is provided, that is, an edge cloud system is fused with a mobile communication network including an MEC node, and a cooperation channel for performing cooperative control on the MEC node is established between a central control device and an MEC network management system, so that the central control device manages a target MEC node based on the cooperation channel, and thus, an MEC node closer to an end side can be used to provide an edge computing service for a user, service response delay is reduced, and bandwidth cost is reduced.

It should be noted that, in the embodiment of the present application, the coverage area of the mobile communication network including the MEC node 102 is not limited, and a mobile communication network that has already made full coverage is applicable to the embodiment of the present application, and a mobile communication network that has just made partial coverage is also applicable to the embodiment of the present application. The overall coverage or the partial coverage herein refers to the overall coverage or the partial coverage of a designated geographical range, and the designated geographical range may be a continent, a country, a region, a province, or the like.

For a new type of mobile communication network, it usually takes a certain time to fully cover a designated regional area, and in this process, the mobile communication network may be gradually deployed in different regions, for example, first deployed in a first-line city, then deployed in a second-line city, then deployed in a third-line city, etc., or first deployed in a hot-spot city, and gradually deployed from the hot-spot city, a business area, then to a residential area, then to a far-suburb county, etc. In the embodiment of the present application, a local network that is gradually deployed and covers a part of an area is referred to as a hot spot coverage area, and with the gradual deployment of a mobile communication network, a plurality of hot spot coverage areas may appear, and local coverage of a specified geographical area may be achieved through the hot spot coverage areas. The coverage areas of the hotspots mentioned in the embodiments of the present application all include an MEC node and an MEC network management system. Further optionally, the hot spot coverage areas may further include an access network element and a core network element; optionally, the access network element and the core network element may be of the same standard or of different standards.

Taking the 5G network as an example, in the 5G network deployment process, a 5G hotspot coverage area may be deployed in a first-line city, a main city, an important area, or the like, and then a 5G hotspot coverage area may be deployed in a second-line city, and the like. Under the non-independent Networking (NSA) architecture, a 5G hot spot coverage area comprises a 5G base station and a 4G core network, or a 4G base station and a 5G core network, and further comprises an MEC node and an MEC network management system. Under an independent networking (SA) architecture, a 5G hot spot coverage area comprises a 5G base station and a 5G core network, and further comprises an MEC node and an MEC network management system. In this embodiment, the number and the deployment location of the 5G hot spot coverage area are not limited, and may be determined by a mobile communication network operator.

Under the condition that the mobile communication network comprises a plurality of hotspot coverage areas where the MEC nodes and the MEC network management systems are deployed, the MEC network management systems can also provide the information of the hotspot coverage areas to which the MEC network management systems belong to the central control equipment; for the central management and control device, a target hotspot coverage area can be selected from a plurality of hotspot coverage areas; determining a target MEC node needing to be managed from MEC nodes in a target hotspot coverage area; further, a resource admission application aiming at the target MEC node is initiated to the MEC network management system in the target hotspot region so as to establish a cooperative channel with the MEC network management system; and carrying out nano-management on the target MEC node based on the cooperative channel so as to provide edge computing service by utilizing the target MEC node.

In the embodiment of the present application, a manner of selecting a target hotspot coverage area from a plurality of hotspot coverage areas by a center management and control device is not limited, and the following examples illustrate that:

for example, the central management and control device may use a plurality of hot spot coverage areas as target hot spot coverage areas, so that fusion between the edge cloud system and all the hot spot coverage areas may be achieved, and more MEC nodes may be managed. Alternatively, if an edge cloud node does not exist in a certain hotspot coverage area, the provider of the edge cloud system 104 may add an edge cloud node in the hotspot coverage area.

For another example, the central management and control device may also select, according to the deployment location of the edge cloud node in the edge cloud system, a hotspot coverage area that may cover the edge cloud node from the multiple hotspot coverage areas as a target hotspot coverage area.

For another example, the central management and control device may also select, according to the edge computing requirement of the edge computing service demander, a hotspot coverage area satisfying the edge computing requirement from the multiple hotspot coverage areas as a target hotspot coverage area. For a game service provider, a game service needs to be deployed in the edge cloud system, and the time delay of the game service is required to be not more than 50 milliseconds, so that the central management and control equipment can select a hot spot coverage area closer to the terminal from a plurality of hot spot coverage areas as a target hot spot coverage area, and after the MEC nodes in the target hot spot coverage area are managed, the game service can be deployed on the managed MEC nodes, so that the purpose of deploying the game service nearby is achieved, and the time delay requirement of the game service is met.

In addition, several methods for selecting the target hotspot coverage area listed above may be used alternatively, or in combination with the above embodiments.

Further, in the case that the mobile communication network of the embodiment of the present application is a 5G mobile communication network, for areas that are not covered by the 5G mobile communication network but are covered by a 4G mobile communication network, for the areas, the central management and control device in the edge cloud system may establish a communication connection with the core network in the 4G mobile communication network in the areas, so that the user terminal in the area may reach the edge cloud system through the core network through the base station in the 4G mobile communication network, so that the user in the area may also use the edge computing service provided by the edge cloud system.

After the central management and control device manages the target MEC node 102a, various management and control needs to be performed on the target MEC node 102 a. The target MEC node 102a in the embodiment of the present application is different from a conventional MEC node and is also different from a conventional edge cloud node, and the target MEC node 102a both belongs to a mobile communication network and is managed by an edge cloud system, so resources on the target MEC node 102a can be divided into two types, one type is an IT resource, and the other type is a CT resource. The IT resources refer to resources that need to be managed and controlled by the central management and control device 101 on the target MEC node 102a under the condition that the target MEC node 102a is managed and controlled by the central management and control device 101; correspondingly, the CT resource refers to a resource that needs to be managed and controlled by the MEC network management system 103 on the target MEC node 102a when the target MEC node 102a is managed and controlled by the central management and control device 101. Whether IT resources or CT resources, include physical resources such as infrastructure, network links, etc., as well as software resources running on physical resources such as infrastructure.

The IT resources are mainly controlled by the central control device 101, and are roughly divided into two levels, where the first level is software and hardware resources managed by the central control device 101 on the target MEC node 102a, and the first level mainly includes various hardware resources managed by the central control device 101 in the target MEC node 102a, such as computing resources of a source CPU, a GPU, a server, and the like, storage resources of a memory, a hard disk, and the like, network resources of a network card, and the like, and software resources of a virtual machine, a basic application, system software, and the like which have been deployed on the hardware resources; the second layer is a software resource further deployed on the managed software and hardware resources by the central control device 101 according to requirements, and mainly refers to various applications, program modules, various middleware, instances providing cloud computing services, system platforms required for providing cloud computing services, data (such as image files) and the like deployed on the managed software and hardware resources by the central control device 101, and further includes various cloud computing services provided for users through virtual machines, instances or containers and the like, such as online education services, online video services, online game services, online shopping services and the like.

The CT resource refers to a part of the resource on the target MEC node 102 that cannot be managed or cannot be managed by the central management and control device 101. Since the target MEC node 102a belongs to the mobile communication network and the deployment of the target MEC node 102a is mainly controlled by the MEC network management system 103, CT resources that cannot be managed or managed by the central management and control device 101 on the target MEC node 102a need to be continuously managed and controlled by the MEC network management system 103. Among these, CT resources include, but are not limited to: the communication network links to which the target MEC node 102a relates, the infrastructure in the target MEC node 102a, and the communication network elements deployed in the target MEC node 102a, etc. Here, the infrastructure that can be managed by the MEC network management system 103 in the target MEC node 102a includes infrastructure that is not managed by the central management apparatus 101, and may also include infrastructure that is managed by the central management apparatus 101. The management and control of the infrastructure managed by the central management and control device 101 in the target MEC node 102a by the MEC network management system 103 mainly refers to some management and control related to whether these infrastructures can be used normally, for example, management and control of the power-on and power-off states of these infrastructures; these infrastructures can be used normally after being powered up, and the management of these infrastructures can be completed by the central management device 101.

In order to implement the control of the target MEC node 102a, as shown in fig. 2a, the network system 100 of the embodiment of the present application further includes an MEC edge control device 110. The central management and control device 101, the MEC network management system 103 and the MEC edge management and control device 110 are mutually matched to realize management and control of the target MEC node 102 a.

The number of the MEC edge policing devices 110 may be one or multiple. MEC edge policing apparatus 110 may be deployed outside of target MEC node 102a, or may be deployed in one or more target MEC nodes 102 a. In an optional embodiment, an MEC edge policing apparatus 110 is deployed in each target MEC node 102 a. In fig. 2a, the MEC edge management and control device 110 is deployed in each target MEC node 102a, but not limited thereto. Further, each target MEC node 102a includes one or more resource devices, and optionally, the MEC edge management and control device 110 may be centrally deployed on one resource device, or may be deployed on multiple resource devices in a decentralized manner. In addition, each target MEC node 102a may include one or more proprietary devices in addition to the resource devices, and optionally, the MEC edge management and control device 110 may also be centrally deployed on one proprietary device or dispersedly deployed on multiple proprietary devices. The dedicated device refers to a physical device dedicated to deploy the MEC edge controller 110, and is different from the resource device. Furthermore, the MEC edge policing apparatus 110 may also be deployed with the central policing apparatus 101, and is not limited herein.

It should be noted that the central control device 101 in this embodiment may be a logic device having the capabilities of resource scheduling, mirror image management, operation and maintenance management, and these functions may be deployed on one physical machine or virtual machine, or may be deployed on multiple physical machines or virtual machines in a distributed manner. Of course, the central management and control device 101 in this embodiment may also be one or more physical devices with the capabilities of resource scheduling, mirror image management, and the like. The embodiment of the present application does not limit the implementation structure of the center management and control device 101, and any device structure having the above-described capability is suitable for the embodiment of the present application.

Similar to the central management apparatus 101, the MEC edge management apparatus 110 may also be a logical apparatus, and may have a capability deployed on one physical machine (e.g., a resource apparatus or a dedicated apparatus in the target MEC node 102 a) or a virtual machine, or may be deployed dispersedly on multiple physical machines (e.g., a resource apparatus or a dedicated apparatus in the target MEC node 102 a) or virtual machines. Of course, the MEC edge management and control device 110 may also be one or more physical devices with corresponding capabilities. The embodiment of the present application does not limit the implementation structure of the MEC edge management and control device 110, and any device structure with corresponding capability is suitable for the embodiment of the present application.

Similar to the central management and control device 101, the MEC network management system 103 may also be a logical device, and its capability may be deployed on one physical machine or virtual machine, or may be deployed on multiple physical machines or virtual machines in a distributed manner. Of course, the MEC network management system 103 may also be one or more physical devices with corresponding capabilities. The embodiment of the present application does not limit the implementation structure of the MEC network management system 103, and any device structure with corresponding capability is suitable for the embodiment of the present application.

In this embodiment of the present application, the central management and control device 101 and the MEC network management system 103 may implement management and control on the target MEC node 102a with the aid of the MEC edge management and control device 110. For the MEC edge management and control device 110, IT may know the IT resources and the CT resources on the target MEC node 102a in advance, and then monitor the IT resources and the CT resources on the target MEC node 102a, and report the monitoring data of the IT resources and the monitoring data of the CT resources to the central management and control device 101 and the MEC network management system 103, respectively. For convenience of description and distinction, the monitoring data of the IT resources are simply referred to as first monitoring data; the monitoring data for the CT resource is referred to as second monitoring data. Accordingly, the central management and control device 101 may receive the first monitoring data reported by the MEC edge management and control device 110, and manage and control the IT resources on the target MEC node 102a according to the first monitoring data. The MEC network management system 103 may receive second monitoring data reported by the MEC edge management and control device 110, and manage and control CT resources on the MEC node according to the second monitoring data.

Optionally, for the MEC edge management and control device 110, the IT resources on the target MEC node 102a may be monitored under the control of the central management and control device 101, and the obtained first monitoring data may be reported to the central management and control device 101. In addition, the MEC edge management and control device 110 may also monitor CT resources on the target MEC node 102a and report the obtained second monitoring data to the MEC network management system 103 under the control of the MEC network management system 103. Alternatively, the MEC edge management and control device 110 may periodically monitor the IT resources on the target MEC node 102a according to the timing task and report the first monitoring data to the central management and control device 101. Alternatively, the MEC edge management and control device 110 may periodically monitor the CT resource on the target MEC node 102a according to the timing task and report the second monitoring data to the MEC network management system 103. In any embodiment, the MEC edge management and control device 110 mainly performs functions of monitoring, data acquisition, reporting, and the like, and the management and control decision is mainly determined by the central management and control device 101 or the MEC network management system 103.

The central management and control device 101 controls the MEC edge management and control device 110 to monitor the IT resources on the target MEC node 102a, and may adopt but is not limited to the following optional embodiments:

in an optional embodiment, the central management and control device 101 may send a first type of monitoring instruction to the MEC edge management and control device 110 to instruct the MEC edge management and control device 110 to monitor the IT resources on the target MEC node 102a from at least one monitoring dimension and report the first monitoring data on the at least one monitoring dimension to the central management and control device 101. The first type of monitoring instruction is a monitoring instruction that instructs the MEC edge management and control device 110 to monitor the target MEC node 102a from at least one monitoring dimension and report first monitoring data in at least one monitoring dimension. For the MEC edge management and control device 110, a first type of monitoring instruction sent by the central management and control device 101 may be received, the IT resources on the target MEC node 102a are monitored from at least one monitoring dimension according to the first type of monitoring instruction, and first monitoring data on the at least one monitoring dimension is reported to the central management and control device 101. The central management and control device 101 manages and controls the target MEC node 102a according to the first monitoring data on at least one monitoring dimension reported by the MEC edge management and control device 110. It should be noted that at least one monitoring dimension can be flexibly set according to application requirements, and is preset in the MEC edge management and control device 110 and the central management and control device 101. See the subsequent examples for examples of monitoring dimensions.

In another alternative embodiment, the central administration facility 101 may selectively monitor IT resources on the target MEC node 102a in one or some monitoring dimensions. Based on this, the central management and control device 101 may send a second type of monitoring instruction to the MEC edge management and control device, where the second type of monitoring instruction corresponds to the specified monitoring dimension, and is used to instruct the MEC edge management and control device 110 to monitor the IT resources on the target MEC node 102a in the specified monitoring dimension and report the first monitoring data in the specified monitoring dimension. For the MEC edge management and control device 110, the second type of monitoring instruction sent by the central management and control device 101 may be received, the IT resources on the target MEC node 102a are monitored in the specified monitoring dimension according to the second type of monitoring instruction, and the first monitoring data in the specified monitoring dimension is reported to the central management and control device 101, so that the central management and control device 101 manages and controls the target MEC node 102a according to the monitoring data in the specified monitoring dimension. The central management and control device 101 is further configured to receive first monitoring data in a specified monitoring dimension, which is sent by the MEC edge management and control device 110, and manage and control the target MEC node 102a according to the first monitoring data in the specified monitoring dimension.

It should be noted that the designated monitoring dimension may be one or more. In the case that the designated monitoring dimensions are multiple, each designated monitoring dimension may correspond to one second-class monitoring instruction, that is, the central management and control device 101 may send multiple second-class monitoring instructions to the MEC edge management and control device 110, where each second-class monitoring instruction corresponds to one designated monitoring dimension. Or, in the case that the designated operation and maintenance dimensions are multiple, multiple designated monitoring dimensions may also correspond to the same second type of monitoring instruction, that is, the central management and control device 101 may send one second type of monitoring instruction to the MEC edge management and control device 110, where the second type of monitoring instruction corresponds to multiple designated monitoring dimensions.

Optionally, the MEC edge management and control device 110 may periodically monitor the IT resources on the target MEC node 102a according to the timing task, where the periodically monitoring the IT resources on the target MEC node 102a from at least one monitoring dimension according to the timing task; further, the first monitoring data in at least one monitoring dimension may be reported to the central control device 101. The monitoring periods in different monitoring dimensions may be the same or different. For example, the MEC edge management and control device 110 may perform security vulnerability scanning on the target MEC node 102a every 10 minutes, or perform traffic monitoring on the target MEC node 102a every 5 minutes.

The at least one monitoring dimension or the specified monitoring dimension may include, but is not limited to, the following dimensions: object dimensions, log dimensions, security dimensions, resource dimensions, etc. in the run state. Further, the dimension of the object in the running state may include a running state dimension of the object and/or a lifecycle dimension of the object; the security dimensions may include: a traffic attack dimension and/or a security vulnerability dimension. The first type of monitoring data is obtained by the MEC edge management and control device 110 monitoring the IT resources on the at least one target MEC node 102a in at least one monitoring dimension or a specified monitoring dimension.

In combination with the above-listed monitoring dimensions, an example of the central management and control device 101 managing and controlling the IT resources on at least one target MEC node 102a with the assistance of the MEC edge management and control device 110 is as follows:

regulation example C1: the central management and control device 101 controls the MEC edge management and control device 110 to perform state monitoring on the objects in the operating state in the IT resources on the target MEC node 102 a. The control method includes sending a first type of monitoring instruction or sending a second type of monitoring instruction corresponding to the operation state dimension of the object to the MEC edge management and control device 110. The MEC edge management and control device 110 performs state monitoring on the object in the running state in the IT resource on the target MEC node 102a under the control of the central management and control device 101, or periodically according to the timing task, and reports the running state of the monitored object in the running state to the central management and control device 101. The central management and control device 101 identifies an object with an abnormal operating state from the operating states of the objects in the operating state reported by the MEC edge management and control device 110, and for convenience of description and distinction, the object with the abnormal operating state is referred to as a target object, and exception handling is performed on the target object. Among the objects in the operating state in the IT resources of the target MEC node 102a, the objects include, but are not limited to: a virtual machine monitor (hypervisor), a virtual machine, an instance, a container, middleware responsible for logging, middleware responsible for security, a physical machine, a CPU and/or hard disk, and the like. The abnormal conditions of the running state are different according to different objects in the running state. For example, for the purposes of the examples, possible abnormal situations include, but are not limited to: interrupts, error reports, and/or malfunctions, etc. As another example, for a physical machine, possible abnormal situations include, but are not limited to: the system comprises the following steps of halting, screen blacking, alarming and/or flash quitting of application programs running on the physical machine and the like. The exception handling manner may also be different according to the target object and the exception condition of the running state, and may include, but is not limited to: alerting, stopping or restarting the target object, migrating, and/or deleting and rebuilding the target object, etc.

Regulation example C2: the central management and control device 101 controls the MEC edge management and control device 110 to monitor the lifecycle of the objects in the operating state in the IT resources on the target MEC node 102 a. The control method includes sending a first type of monitoring instruction or sending a second type of monitoring instruction corresponding to the life cycle dimension of the object to the MEC edge management and control device 110. The MEC edge management and control device 110 monitors the lifecycle of the object in the running state in the IT resource on the target MEC node 102a under the control of the central management and control device 101, or periodically according to the timing task, and reports the monitored lifecycle of the object in the running state to the central management and control device 101. The central management and control device 101 controls the object in the running state to stop, restart after stopping, migrate or delete according to the life cycle of the object in the running state reported by the MEC edge management and control device 110.

Regulation example C3: the central management and control device 101 controls the MEC edge management and control device 110 to collect log data of the IT resources on the target MEC node 102 a. The control method includes sending a first type of monitoring instruction or sending a second type of monitoring instruction corresponding to the log dimension to the MEC edge management and control device 110. The MEC edge management and control device 110 collects log data of the IT resources on the target MEC node 102a under the control of the central management and control device 101, or periodically according to a timing task, and reports the collected log data to the central management and control device 101. The central management and control device 101 receives the log data reported by the MEC edge management and control device 110, performs data analysis on the log data, and performs subsequent actions according to the data analysis result, such as charging, wind control, and/or adding or subtracting instances. The follow-up action will be different according to the log data. Alternatively, the log data may include, but is not limited to: data of various performances, indexes and the like in the target MEC node 102a, for example: bandwidth traffic of the instance, current operation of the instance, IO load of the instance, bandwidth traffic of the physical machine, current operation of the physical machine, IO load of the physical machine, operation of the MEC edge management apparatus 110, and/or operation of other virtualized components, and the like.

Optionally, the central management and control device 101 may collect log data of the IT resources on each target MEC node 102a reported by the MEC edge management and control device 110, and further have a data polling capability, and for some data, if the data stored in the central management and control device 101 is inconsistent with the data in the target MEC node 102a, the central management and control device may actively synchronize the latest data with the target MEC node 102a, for example, synchronize the latest version of the mirror image with the target MEC node 102 a.

Regulation example C4: the central management and control device 101 controls the MEC edge management and control device 110 to perform traffic monitoring on the IT resources on the target MEC node 102 a. The control method includes sending a first type of monitoring instruction or sending a second type of monitoring instruction corresponding to the traffic attack dimension to the MEC edge management and control device 110. The MEC edge management and control device 110 performs traffic monitoring on the IT resources on the target MEC node 102a under the control of the central management and control device 101, or periodically according to a timing task, and reports the monitored traffic attack event to the central management and control device 101. The central management and control device 101 performs blocking processing on a traffic attack event occurring in the target MEC node 102 a. Optionally, the MEC edge management and control device 110 may further report the monitored traffic data to the central management and control device 101, and the central management and control device 101 may further perform, according to the traffic data, traffic attack defense and the like on the IT resources on the target MEC node 102 a.

Regulation example C5: the central management and control device 101 controls the MEC edge management and control device 110 to perform network security vulnerability scanning on the IT resources on the target MEC node 102 a. The control method includes sending a first type of monitoring instruction or sending a second type of monitoring instruction corresponding to the network security dimension to the MEC edge management and control device 110. The MEC edge management and control device 110 scans network security vulnerabilities of IT resources on the target MEC node 102a under the control of the central management and control device 101, or periodically according to a timing task, and reports the scanned network security vulnerabilities to the central management and control device 101. The central management and control device 101 receives the network security vulnerability reported by the MEC edge management and control device 110, and repairs the network security vulnerability.

Regulation example C6: the central management and control device 101 controls the MEC edge management and control device 110 to monitor the resource usage of the IT resources on the target MEC node 102 a. The control method includes sending a first type of monitoring instruction or sending a second type of monitoring instruction corresponding to the resource dimension to the MEC edge management and control device 110. The MEC edge management and control device 110 monitors the resource usage amount of the IT resources on the target MEC node 102a under the control of the central management and control device 101, or periodically according to the timing task, and reports the monitored resource usage amount information to the central management and control device 101. The central management and control device 101 performs resource expansion or volume reduction on the target MEC node 102a according to the resource usage information reported by the MEC edge management and control device 110. The resources include various resource information, such as device resources like physical machines, storage resources like memories and hard disks, and computing resources like CPUs, GPUs and virtual machines, and so on. For example, the number of CPU cores running the corresponding instances of the edge computing service on the original target MEC node 102a is 2, and the MEC edge management and control device 110 monitors that the CPU resources are insufficient, the central management and control device 101 expands the capacity of the corresponding instances of the edge computing service, and expands the number of CPU cores from 2 to 4.

Further, if each target MEC node 102a is deployed with an MEC edge management and control device 110, each MEC edge management and control device 110 may monitor the IT resources on the target MEC node 102a to which IT belongs and report the obtained first monitoring data to the central management and control device 101 under the control of the central management and control device 101, or periodically according to a timed task. The central management and control device 101 may receive first monitoring data reported by the MEC edge management and control device 110 in each target MEC node 102a, and manage and control the IT resources in the target MEC node 102a to which each MEC edge management and control device 110 belongs according to the first monitoring data reported by each MEC edge management and control device 110. Similarly, each MEC edge management and control device 110 may monitor the CT resource on the target MEC node 102a to which it belongs and report the obtained second monitoring data to the MEC network management system 103 under the control of the MEC network management system 103 or periodically according to the timing task. The MEC network management system 103 may receive second monitoring data reported by the MEC edge management and control device 110 in each target MEC node 102a, and manage and control CT resources in the target MEC node 102a to which each MEC edge management and control device 110 belongs according to the second monitoring data reported by each MEC edge management and control device 110.

In this embodiment, the implementation manner in which the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the CT resources on the target MEC node 102a is the same as or similar to the implementation manner in which the central management and control device 101 controls the MEC edge management and control device 110 to monitor the IT resources on the target MEC node 102a, and details may be referred to the foregoing embodiment and are not described herein again.

The MEC network management system 103 may control the MEC edge management and control device 110 to monitor CT resources on the target MEC node 102a in at least one monitoring dimension or a specified monitoring dimension. Wherein the at least one monitoring dimension or the specified monitoring dimension may include, but is not limited to, the following dimensions: the system comprises infrastructure dimension, communication network link dimension, communication network element dimension and the like, wherein the infrastructure dimension mainly refers to the dimension of the power-on and power-off state of the infrastructure; communication network link dimensions may include, but are not limited to: a health status dimension of a communication network link, a security status dimension of a communication network link, a protocol status dimension of a communication network link, a traffic status dimension on a communication network link, etc. The second monitoring data is obtained by monitoring, by the MEC edge management and control device 110, the CT resource on the target MEC node 102a in at least one monitoring dimension or a specified monitoring dimension.

An example of the MEC network management system 103 managing and controlling CT resources on the target MEC node 102a with the assistance of the MEC edge management and control device 110 is as follows:

regulation example D1: the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the power on and power off states of the infrastructure in the CT resources of the target MEC node 102 a. The control method includes sending a first type of monitoring instruction to the MEC edge management and control device 110 or sending a second type of monitoring instruction corresponding to the power-on and power-off state dimension of the infrastructure. The MEC edge management and control device 110 monitors the power on and power off states of the infrastructure in the CT resource under the control of the MEC network management system 103, or periodically according to the timing task, and reports the monitored power on and power off states of the infrastructure to the MEC network management system 103. The MEC network management system 103 receives the power-on and power-off states of the infrastructure reported by the MEC edge management and control device 110, performs data analysis on the power-on and power-off states of the infrastructure, and executes subsequent actions according to data analysis results. For example, power-up control is performed for an infrastructure that is not powered but should be powered up, or power-down control is performed for an infrastructure that is powered down but has not yet been powered down. For another example, too many devices that need to be powered on at the same time may cause excessive line current, thereby causing damage to the line or the devices, and the MEC network management system 103 may control the number of devices powered on at a time, and power on the devices in batches. For another example, the power-off of the device may cause a related service interruption, and the MEC network management system 103 may perform the power-off operation on the related device when the device is out of service.

Regulation example D2: the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the health state of a communication network link (the communication network link belongs to a CT resource) of the target MEC node 102a, wherein the control manner includes sending a first type of monitoring instruction to the MEC edge management and control device 110 or sending a second type of monitoring instruction corresponding to the health state dimension of the communication network link. The MEC edge management and control device 110 monitors the health state of the communication network link of the target MEC node 102a under the control of the MEC network management system 103 or periodically according to the timing task, and reports the monitored health state of the communication network link to the MEC network management system 103. The MEC network management system 103 stores the detected health status information of the communication network link, where the health status of the communication network link includes but is not limited to: network health, network outages, network failures, network congestion, and the like. If the health status of the communication network link is network interruption or network failure, the MEC network management system 103 may switch the service or application traffic on the communication network link to another communication network link, so as to ensure that the service or application, etc., can provide services normally.

Regulation example D3: the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the security state of the communication network link of the target MEC node 102a, wherein the control mode includes sending a first type of monitoring instruction to the MEC edge management and control device 110 or sending a second type of monitoring instruction corresponding to the security state dimension of the communication network link. The MEC edge management and control device 110 monitors the security state of the communication network link in the CT resource under the control of the MEC network management system 103, or periodically according to the timing task, and reports the monitored security state of the communication network link to the MEC network management system 103. The MEC network management system 103 stores the detected health status information of the communication network link, where the security status of the communication network link includes but is not limited to: whether hacking, IP address spoofing, MAC address spoofing, etc. Under the condition that the health of the communication network link is threatened, the MEC network management system 103 may collect corresponding protective measures to protect the health of the communication network link.

Regulation example D4: the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the protocol state of the communication network link of the target MEC node 102 a. The control method includes sending a first type of monitoring instruction to the MEC edge management and control device 110 or sending a second type of monitoring instruction corresponding to a protocol state dimension of the communication network link. The MEC edge management and control device 110 monitors the protocol state of the communication network link in the CT resource under the control of the MEC network management system 103, or periodically according to the timing task, and reports the monitored protocol state information to the MEC network management system 103. The MEC network management system 103 receives the protocol state of the communication network link reported by the MEC edge management and control device 110, and performs related processing on the protocol state of the communication network link. For example, taking the communication network link using the HTTP protocol as an example, the protocol states involved in the HTTP protocol may include but are not limited to: the server successfully processed the request, redirection, client error, server error, etc. If the state of the HTTP protocol is abnormal, the target MEC node 102a cannot normally communicate, and the MEC network management system 103 may output an alarm message indicating that the state of the HTTP protocol is abnormal, or perform fault diagnosis and troubleshooting on the condition that the state of the HTTP protocol is abnormal. Further, if the MEC network management system 103 finds that an HTTP protocol has an error that is not supported by the HTTP version, the MEC network management system 103 may upgrade the HTTP version used by the server.

Regulation example D5: the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the traffic state on the communication network link of the target MEC node 102 a. The control method includes sending a first type of monitoring instruction to the MEC edge management and control device 110 or sending a second type of monitoring instruction corresponding to a traffic state dimension on a communication network link. The MEC edge management and control device 110 monitors the traffic state of the network link in the CT resource under the control of the MEC network management system 103 or periodically according to the timing task, and reports the monitored traffic state information to the MEC network management system 103. The MEC network management system 103 receives and stores the traffic state of the communication network link reported by the MEC edge management and control device 110; further, the flow control mechanism may be enabled for the communication network link when the flow state of the communication network link is abnormal. IT should be noted that, in this embodiment, the traffic in the IT resource is usually counted by taking a certain user, a certain service, a certain application, or a certain instance as a granularity, while the traffic on the communication network link in the CT resource is counted by taking the communication network link as a granularity, and one communication network link can simultaneously carry the traffic of multiple users, multiple services, multiple applications, or multiple instances. When detecting a traffic anomaly on a communication network link, for example, a traffic peak, an instant large-traffic attack, etc., the MEC network management system 103 may perform global traffic blocking processing on the communication network link where the traffic anomaly occurs, or allocate sufficient bandwidth resources to some applications according to different bandwidth control strategies, and block the traffic of other applications, which is not limited to this. Further optionally, the MEC network management system 103 may further perform traffic attack defense and the like on the target MEC node 102a according to the traffic data.

Regulation example D6: the MEC network management system 103 controls the MEC edge management and control device 110 to monitor the health state of the communication network elements in the CT resource of the target MEC node 102 a. The control method includes sending a first type of monitoring instruction to the MEC edge management and control device 110 or sending a second type of monitoring instruction corresponding to the health status dimension of the communication network element. The MEC edge management and control device 110 monitors the health state of the communication network element in the CT resource under the control of the MEC network management system 103, or periodically according to the timing task, and reports the monitored health state information to the MEC network management system 103. The MEC network management system 103 receives and stores the health state of the communication network element reported by the MEC edge management and control device 110.

Wherein the communication network element is a network element in a mobile communication network operating on the target MEC node 102a, for example, including but not limited to: a UPF network element that provides a local breakout function for the target MEC node 102 a. The UPF network element is a core network element responsible for local offloading, and the UPF network element may be deployed on one physical machine or virtual machine in the target MEC node 102a, or may be deployed on multiple physical machines or virtual machines in the target MEC node 102a in a distributed manner. Of course, the UPF network element may also be deployed in the access network independently, or, as shown in fig. 1a and 1b, in the core network, which is not limited to this. In this embodiment, the UPF network element is deployed in the target MEC node 102a, and is not shown in fig. 2 a. If the virtual machine bearing the UPF network element in the target MEC node 102a is abnormal, the UPF network element may work abnormally, which may seriously affect the transmission quality of data, and may cause problems of packet loss, delay, and the like. In this embodiment, the health status of the communication network element may be defined as an unstable status and a stable status, and may also be defined as several statuses with very poor quality, good quality, very good quality, and the like. The communication network element deployed in the target MEC node 102a may provide basic services for objects such as examples, services, applications, or middleware in the IT resource, monitor and know the health state of the communication network element deployed in the target MEC node 102a in real time, so as to ensure normal operation of the objects such as the examples, services, applications, or middleware in the IT resource, and perform troubleshooting when a fault or an abnormality occurs.

In a cloud network convergence scenario, the central management and control device 101, the MEC edge management and control device 110, and the MEC network management system 103 cooperate with each other, so that a target MEC node 102a (including IT resources and CT resources) can be managed or scheduled, and the MEC edge management and control device 110 can also synchronize corresponding management or scheduling information to the MEC network management system 103 and the central management and control device 101 in the mobile communication network. Optionally, in the central management and control device 101, the MEC network management system 103, and the MEC edge management and control device 110, corresponding components or modules may be deployed and communicate with each other through the internet, so as to implement management or scheduling of the target MEC node 102a (including IT resources and CT resources). In the embodiment of the present application, implementation structures of the center management and control device 101, the MEC network management system 103, and the MEC edge management and control device 110 are not limited. Optionally, as shown in fig. 2b, a structural framework of a central management and control device 101 at least includes: a central management and control module 101a and a central middleware module 101 b; the central middleware module 101b includes, but is not limited to: a central monitoring module 101c, a central log module 101d, a central security module 101e, etc. Accordingly, a structural framework of the MEC edge management and control apparatus 110 is shown in fig. 2b, and at least includes: an edge policing module 110a and an edge middleware module 110b, the edge middleware module 110b including, but not limited to: an edge monitoring module 110c, an edge logging module 110d, an edge security module 110e, etc. Accordingly, as shown in fig. 2b, a structural framework of the MEC network management system 103 at least includes: an MEC administration synchronization module 103a and an MEC edge middleware module 103b, the MEC edge middleware module 103b including, but not limited to: MEC edge monitoring module 103c, MEC edge logging module 103d, and MEC edge security module 103e, etc. In fig. 2b, the modules required for controlling the target MEC node 102a in the central control device 101, the MEC network management system 103 and the MEC edge control device 110 are mainly illustrated, but the internal structures of the central control device 101, the MEC network management system 103 and the MEC edge control device 110 are not limited thereto.

The central management and control module 101a, the edge management and control module 110a, and the MEC management and control synchronization module 103a cooperate with each other to complete the management of the target MEC node 102a, and for the management process of the target MEC node 102a, reference may be made to the foregoing embodiments, which are not described herein again. In addition, the central management and control module 101a faces the edge computing service demander, and the managed resources on the target MEC node 102a can provide the edge computing service for the edge computing service demander. The central management and control module 101a may receive various commands or information sent by the edge computing demander, and cooperate with the edge management and control module 110a according to various commands or information sent by the edge computing service demander, may deploy objects, such as instances, containers, various middleware, and the like, required by the edge computing service demander in the managed resources on the target MEC node 102a, and is responsible for managing and controlling the life cycle of the objects, such as the instances, the containers, the various middleware, and the like. For example, the central policing module 101a may issue a mirror image to the edge policing module 110a, instructing the edge policing module 110a to create an instance, orchestrate a container, etc. on the managed resource on the target MEC node 102a according to the mirror image. The edge management module 110a receives the instruction of the central management module 101a, instructs a virtualized component (e.g., a hypervisor) or other execution component on the target MEC node 102a to perform a corresponding action according to the instruction, and returns the execution result to the central management module 101a, the MEC management synchronization module 103a, or other corresponding modules. The MEC management and control synchronization module 103a may synchronize information of each module, component, or resource on the central management and control device 101 and the target MEC node 102a in real time during data synchronization or command execution between the central management and control module 101a and the edge management and control module 110a, and store the information.

The central monitoring module 101c is responsible for monitoring the operation states of the modules, components and the like in the central control equipment 101 on one hand, and can control the modules, components and the like in the central control equipment 101; on the other hand, the edge monitoring module 110c is responsible for receiving first monitoring data corresponding to each IT resource (for example, each module, instance, mirror image, container, physical machine, etc.) in the target MEC node 102a, which is reported by the edge monitoring module, and managing and controlling each IT resource in the target MEC node 102a according to the first monitoring data. The central monitoring module 101c may also perform related alarm when an abnormality or problem occurs in a certain module, component, or the like in the central management and control device 101 or on the target MEC node 102a, and synchronize the alarm information to the MEC edge monitoring module 103c in the MEC network management system 103. The MEC management and control synchronization module 103a in the MEC network management system 103 may also be responsible for synchronizing the status and information of the central monitoring module 101c and the edge monitoring module 110 c. The edge monitoring module 110c is responsible for monitoring the IT resources and the CT resources in the target MEC node 102a, and synchronizes the first monitoring data and the second monitoring data to the central monitoring module 101c and the MEC edge monitoring module 103c, respectively. Further optionally, the edge monitoring module 110c may also autonomously monitor and control the IT resources, such as modules, instances, images, containers, physical machines, and the like, on the target MEC node 102a when the central management and control device 101 is out of contact, and may perform timely warning after an exception occurs, and for this part, reference may be made to the following embodiments.

The central log module 101d is responsible for collecting or processing log data in the central management and control device 101 on one hand, and synchronizing the collected log data to the MEC edge log module 103d in the MEC network management system 103; on the other hand, the method may receive the log data related to the IT resource in the target MEC node 102a sent by the edge log module 110d, and synchronize the received log data to the MEC edge log module 103 d. In addition, the central logging module 101d also has a data polling capability, for example, for the same event or related events, if the data generated by the central management and control device 101 is not consistent with the data generated by the central management and control device 102a, the central logging module 101d may synchronize the latest data with the target MEC node 102a again, and may transmit the latest data synchronized with the target MEC node 102a to the MEC edge logging module 103d for storage. Correspondingly, the edge log module 110d is mainly configured to collect data such as various performance and index data generated in the target MEC node, for example, instance bandwidth flow, an instance current operating condition, an instance IO load, a physical machine bandwidth flow, a physical machine current operating condition, a physical machine IO load, an operating condition of the edge management and control module, an operating condition of a virtualization component, and the like, and archive and classify the data according to resource types to obtain log data of an IT resource and log data of a CT resource, and transmit the log data of the IT resource and the log data of the CT resource to the central log module 101d and the MEC edge log module 103d, respectively, for relevant logics such as data analysis, charging, monitoring, and the like.

The edge security module 110e mainly monitors flow attacks in the target MEC node 102a, is responsible for network vulnerability scanning and the like, archives and classifies the monitored data according to the resource types to obtain security data of the IT resources and security data of the CT resources, and respectively transmits the security data of the IT resources and the security data of the CT resources to the central security module 101e and the MEC edge security module 103e for security control of the target MEC node 102 a.

Further, as shown in fig. 2b, the MEC edge management device 110 is deployed in the target MEC node 102a, in this case, the edge monitoring module 110c, the edge log module 110d, the edge middleware module 110b such as the edge security module 110e in the MEC edge management device 110 may obtain, through the virtualization component in the target MEC node 102a, the virtual machine or container, the physical resource carrying the virtual machine or container, and the instance, component, or program module running in the virtual machine or container, and process these data into the first monitoring data or the second monitoring data required for management, and send the first monitoring data or the second monitoring data to the corresponding central middleware module 101b or the MEC edge middleware module 103 b.

Optionally, the above-mentioned control examples C1-C6 may be implemented by respective modules in the central control facility 101 and the MEC edge control facility 110 shown in fig. 2 b. In detail, in the control example C3, the edge log module collects log data of the IT resources in the target MEC node 102a and reports the log data to the central log module 101 d; the central log module 101d performs data analysis on the log data and executes subsequent actions according to the data analysis result. Meanwhile, the central logging module 101d synchronizes the received log data for the IT resources to the MEC edge logging module 103d of the MEC network management system 103. In control examples C4 and C5, the edge security module 110e may perform traffic monitoring or network security vulnerability scanning on the IT resources of the target MEC node 102a, and report the monitored traffic attack event or network vulnerability security problem to the central security module 101e, so as to perform security control on the target MEC node 102 a. The control examples C1, C2, and C6 may be implemented by the central monitoring module 101C in the central control device 101 and the edge monitoring module 110C in the MEC edge control device 110 in a matching manner, and detailed implementation processes are not described in detail.

In the control example D1-D6, the edge monitoring module 110c in the MEC edge control device 110 monitors CT resources on the target MEC node 102a, and synchronously monitors the obtained second monitoring data to the MEC edge monitoring module 103c in the MEC network management system 103.

In addition, the MEC network management system 103 provides part or all of the second monitoring data obtained from the CT resource to the central management and control device 101, so that the central management and control device 101 performs management and control on the IT resource on the target MEC node 102 a. Based on this, the central management and control device 101 may obtain at least part of the second monitoring data related to the IT resources from the MEC network management system 103; and managing the IT resources on the target MEC node 102a by combining at least part of the second monitoring data and the first monitoring data.

In this embodiment, the central control device 101 does not limit the implementation manner of obtaining at least part of the second monitoring data related to the IT resource from the MEC network management system 103. For example, the MEC network management system 103 may actively provide at least part of the second monitoring data related to the IT resource to the central management and control device 101. For another example, the central management and control device 101 periodically or aperiodically goes to the MEC network management system 103 to obtain at least part of the second monitoring data related to the IT resources.

For example, if the central control device 101 obtains that the running state of the instance on the target MEC node 102a is interrupted according to the obtained first monitoring data, further, the central control device 101 may obtain second monitoring data from the MEC network management system 103, and if the security state of the communication network link in the second monitoring data is determined to be attacked, the central control device 101 may migrate, delete, and reestablish the service, and the like, to the service on the target MEC node.

For another example, if the central control device 101 obtains that the service delay of the instance on the target MEC node 102a is large according to the obtained first monitoring data, further, the central control device 101 may obtain the second monitoring data from the MEC network management system 103, if the health state of the communication network link in the second monitoring data is determined to be in a good network state, the central control device 101 further obtains the resource usage amount of the IT resource in the first monitoring data, and if the service delay is determined to be too large and is caused by insufficient resource usage amount, the central control device 101 adopts a capacity expansion policy to expand the computation resource, the storage resource, or the bandwidth resource and the like on the target MEC node 102 a.

As can be seen from the above, with the assistance of the MEC edge management and control device 110 and the MEC network management system 103, the central management and control device 101 can know the health, the resource usage, the log data and/or the infrastructure condition of each instance in the target MEC node 102a, and can implement remote operation and maintenance, log management, and the like.

IT should be noted that, in the above embodiment, regarding monitoring and control of the IT resources and the CT resources in the target MEC node 102a, the central middleware module 101b, the edge middleware module 110b, and the MEC edge middleware module 103b are directly implemented in cooperation, but not limited thereto. For example, each middleware module may only provide monitoring and control data, and the specific management and control process may be implemented by the central management and control module 101a, the edge management and control module 110a, and the MEC management and control synchronization module 103 a. For example, the edge monitoring module 110c is responsible for monitoring modules, instances, mirrors, containers, physical machines, and the like on the target MEC node 102a, archiving and classifying the monitored data according to the resource type to obtain first monitoring data and second monitoring data, and uploading the first monitoring data and the second monitoring data to the central monitoring module 101c and the MEC edge monitoring module 103 c; the central monitoring module 101c analyzes the first monitoring data, and when an abnormal condition of the IT resource is found, the central monitoring module 101c notifies the central management and control module 101a, and the central management and control module 101a and the edge management and control module 110a cooperate with each other to manage and control the abnormal condition of the IT resource; similarly, the MEC edge monitoring module 103c analyzes the second monitoring data, and when an abnormal condition of the CT resource is found, notifies the MEC management and control synchronization module 103a, and the MEC management and control synchronization module 103a and the edge management and control module 110c cooperate with each other to manage and control the CT resource in the abnormal condition. The monitoring and control process for log data and security data is similar to that described above, and will not be described in detail.

In this embodiment of the application, except that the central management and control device 101 may manage and control the IT resources on the target MEC node 102a, in a case that the central management and control device 101 does not manage or cannot manage and control the IT resources on the target MEC node 102a, the MEC edge management and control device 110 may autonomously manage and control the IT resources on the target MEC node 102a, thereby implementing two-stage management and control of the IT resources. Further optionally, if each target MEC node 102a is deployed with an MEC edge management and control device 110, for each MEC edge management and control device 110, IT may autonomously manage and control the IT resources on the target MEC node 102a to which IT belongs, when the central management and control device 101 does not or cannot manage and control the IT resources on the target MEC node 102a to which IT belongs.

For example, the MEC edge management and control device 110 may monitor IT layer network connection between the MEC edge management and control device 101 and CT layer network connection between the MEC edge management and control device 103. A CT layer network connection refers to a physical link implemented by a physical line between two nodes, such as a physical carrier, e.g., a cable, an optical fiber, or an electromagnetic wave. An IT-layer network connection refers to a logical link implemented on the basis of a physical connection. Multiple logical links can be carried on one physical link, and when CT layer network connection is lost, multiple IT layer network connection carried by the physical link is also lost. In practical applications, the MEC edge management and control device 110 may lose an IT layer network connection with the central management and control device 101 or lose a CT layer network connection with the MEC network management system 103. In this case, in order for the IT resources on target MEC node 102a to function properly, MEC edge policing apparatus 110 may autonomously police the IT resources on target MEC node 102 a.

For another example, when the central management and control device 101 sends a first type of monitoring instruction to the MEC edge management and control device 110 to monitor the IT resources on the target MEC node 102a, the MEC edge management and control device 110 may wait to receive the first type of monitoring instruction sent by the central management and control device 101, and if the first type of monitoring instruction sent by the central management and control device 101 is not received, IT may be determined that the central management and control device 101 does not or cannot manage the target MEC node 102a, and the IT resources on the target MEC node 102a may be autonomously managed and controlled from at least one monitoring dimension. Optionally, the MEC edge management and control device 110 and the central management and control device 101 may agree in advance on a waiting duration of the first type of monitoring instruction, and if the waiting duration is exceeded and the first type of monitoring instruction sent by the central management and control device 101 is still not received, it is determined that the first type of monitoring instruction sent by the central management and control device 101 is not received.

For another example, when the central management and control device 101 sends the second type of monitoring instruction corresponding to the specified monitoring dimension to the MEC edge management and control device 110 to monitor the IT resources on the target MEC node 102a from the specified monitoring dimension, the MEC edge management and control device 110 may wait to receive the second type of monitoring instruction sent by the central management and control device 101, and if the second type of monitoring instruction sent by the central management and control device 101 is not received in the specified monitoring dimension, IT may be determined that the central management and control device 101 does not or cannot control the IT resources on the target MEC node 102a in the specified monitoring dimension, and then the IT resources on the target MEC node 102a may be autonomously managed and controlled from the specified monitoring dimension.

Optionally, the at least one monitoring dimension or the specified monitoring dimension may include, but is not limited to, the following dimensions: object dimensions, log dimensions, security dimensions, resource dimensions, etc. in the run state. Further, the dimension of the object in the running state may include a running state dimension of the object and/or a lifecycle dimension of the object; the security dimensions may include: a traffic attack dimension and/or a security vulnerability dimension.

An example of the MEC edge policing device 110 autonomously policing the IT resources on the target MEC node 102a is as follows:

regulation example E1: the state monitoring is performed autonomously on the object in the operating state in the IT resource of the target MEC node 102a, and the exception handling is performed on the target object with the abnormal monitored operating state.

Regulation example E2: the lifecycle of the object in the running state in the IT resources of the target MEC node 102a is autonomously monitored, and the object in the running state is controlled to stop, restart after stop, migrate or delete according to the monitoring result. For a container or instance, the container or instance may be controlled to stop executing, restart after stopping, delete, etc.

Regulation example E3: the log data in the IT resources of the target MEC node 102a are autonomously collected, data analysis is performed on the log data, and follow-up actions are executed according to the data analysis result. The log data includes, but is not limited to, bandwidth traffic of the instance in the target MEC node 102a, current operating conditions of the instance, IO load of the instance, bandwidth traffic of the physical machine, current operating conditions of the physical machine, IO load of the physical machine, operating conditions of the edge policing device, and/or operating conditions of other virtualized components, and the like. Optionally, subsequent actions such as charging, wind control and/or resource reallocation can be performed according to the analysis result of the log data, but is not limited thereto.

Regulation example E4: traffic monitoring is autonomously performed on the IT resources of the target MEC node 102a, and blocking processing is performed on the monitored traffic attack events.

Regulation example E5: and autonomously scanning the IT resources of the target MEC node 102a for network security vulnerabilities and repairing the scanned network security vulnerabilities.

Regulation example E6: and the resource usage of the IT resources in the target MEC node 102a is autonomously monitored, and the resource expansion or reduction of the IT resources in the target MEC node 102a is carried out according to the monitoring result. Resources herein include, but are not limited to: device resources such as a physical machine, storage resources such as a memory and a magnetic disk, computing resources such as a CPU and a GPU, and network resources such as bandwidth. For these resources, when the usage amount is high, capacity expansion may be performed for these resources, and when the usage amount is low, capacity reduction may be performed for these resources.

Regarding the monitoring process for IT resources in the management examples E1 to E6 and the process of management according to the monitoring data, the differences are similar to the above management examples C1 to C6, except that: whether reporting of the monitoring data and performing of the management and control process are required to be performed by different entities is different, and therefore, for the related description, reference may be made to the description of the management and control examples C1-C6, which is not described herein again.

Further, in an optional embodiment, in a case that the MEC edge management and control device 110 loses an IT layer network connection with the central management and control device 101, the MEC edge management and control device 110 may autonomously manage and control the IT resources on the target MEC node 102a from at least one monitoring dimension, and after the IT layer network connection is restored with the central management and control device 101, the management and control data of the IT resources during the period of losing the IT layer network connection may be synchronized to the central management and control device 101. It should be noted that the management and control data mainly includes data of management and control policies, manners, effects, and the like, and may also include monitoring data.

In yet another optional embodiment, when the MEC edge management and control device 110 loses CT layer network connection with the MEC network management system, the MEC edge management and control device 110 may autonomously manage and control the IT resources on the target MEC node 102a from at least one monitoring dimension, and after restoring CT layer network connection with the MEC network management system 103, synchronize the management and control data of the IT resources during the period of losing CT layer network connection to the central management and control device 101, and synchronize the second monitoring data of the CT resources during the period of losing CT layer network connection to the MEC network management system 103.

Fig. 3 is a schematic flowchart of a management and control method provided in an exemplary embodiment of the present application, and is applicable to an MEC edge management and control device, where the method includes:

31. monitoring IT resources and CT resources on a target MEC node managed by a central management and control device in an edge cloud system in a mobile communication network;

32. reporting first monitoring data obtained by monitoring IT resources to central control equipment, so that the central control equipment can control the IT resources on a target MEC node;

33. and reporting second monitoring data obtained by monitoring the CT resources to an MEC network management system in the mobile communication network so that the MEC network management system can control the CT resources on the MEC nodes.

The target MEC node in the embodiment of the present application is different from a conventional MEC node and is also different from a conventional edge cloud node, and the target MEC node belongs to both a mobile communication network and is managed by an edge cloud system, so resources on the target MEC node can be divided into two types, one type is an IT resource, and the other type is a CT resource. The IT resources refer to resources which need to be managed and controlled by central management and control equipment on the target MEC node under the condition that the target MEC node is managed and controlled by the central management and control equipment; correspondingly, the CT resource refers to a resource that needs to be managed and controlled by the MEC network management system on the target MEC node when the target MEC node is managed and controlled by the central management and control device. Whether IT resources or CT resources, include physical resources such as infrastructure, network links, etc., as well as software resources running on physical resources such as infrastructure. For details of the IT resources and the CT resources, reference may be made to the foregoing embodiments, which are not described herein again.

In this embodiment of the present application, the central management and control device and the MEC network management system may implement management and control on the target MEC node with the assistance of the MEC edge management and control device. For the MEC edge management and control equipment, IT resources and CT resources on a target MEC node can be obtained in advance, the IT resources and the CT resources on the target MEC node can be monitored, and monitoring data of the IT resources and monitoring data of the CT resources are reported to the central management and control equipment and the MEC network management system respectively. For convenience of description and distinction, the monitoring data of the IT resources are simply referred to as first monitoring data; the monitoring data for the CT resource is referred to as second monitoring data. Correspondingly, the central management and control device may receive the first monitoring data reported by the MEC edge management and control device, and manage and control the IT resources on the target MEC node according to the first monitoring data. The MEC network management system can receive second monitoring data reported by the MEC edge management and control equipment and manage and control CT resources on the MEC nodes according to the second monitoring data.

Optionally, the MEC edge management and control device may monitor the IT resources on the target MEC node and report the obtained first monitoring data to the central management and control device under the control of the central management and control device. In addition, the MEC edge management and control device may also monitor CT resources on the target MEC node under the control of the MEC network management system and report the obtained second monitoring data to the MEC network management system. Or, the MEC edge management and control device may periodically monitor the IT resources on the target MEC node and report the first monitoring data to the central management and control device according to the timing task. Or, the MEC edge management and control device may periodically monitor the CT resource on the target MEC node according to the timing task and report the second monitoring data to the MEC network management system. In any embodiment, the MEC edge management and control device mainly performs functions of monitoring, data acquisition, reporting, and the like, and the management and control decision is mainly determined by the central management and control device or the MEC network management system.

In this embodiment, an execution sequence of reporting the monitored first monitoring data to the central management and control device or reporting the monitored second monitoring data to the MEC network management system is not limited. For example, the first monitoring data obtained by monitoring may be reported to the central management and control device, and then the second monitoring data obtained by monitoring may be reported to the MEC network management system. For another example, the second monitoring data obtained by monitoring may be reported to the MEC network management system, and then the first monitoring data obtained by monitoring may be reported to the central control device. For another example, the first monitoring data obtained through monitoring may be reported to the central management and control device, and the second monitoring data obtained through monitoring may be reported to the MEC network management system, which is not limited herein.

In an optional embodiment, the MEC edge management and control device monitors the IT resources and reports the first monitoring data to the central management and control device, including at least one of:

operation F1: monitoring the state of an object in an operation state in IT resources, reporting the monitored operation state of the object in the operation state to a central control device, so that the central control device can identify a target object with an abnormal operation state and perform exception processing on the target object;

operation F2: monitoring the life cycle of an object in an operation state in IT resources, and reporting the monitored life cycle of the object in the operation state to a central control device, so that the central control device can control the object in the operation state to stop, restart or delete after stopping;

operation F3: collecting log data of IT resources, and reporting the log data to central control equipment so that the central control equipment can perform data analysis on the log data and execute subsequent actions according to data analysis results;

operation F4: carrying out flow monitoring on IT resources, and reporting the monitored flow attack event to central control equipment so that the central control equipment can block the flow attack event;

operation F5: network security vulnerability scanning is carried out aiming at IT resources, and the scanned network security vulnerability problem is reported to central control equipment so that the central control equipment can repair the security vulnerability problem;

operation F6: monitoring the resource usage of the IT resources, and reporting the monitored resource usage information to the central control equipment so that the central control equipment can perform resource expansion or reduction on the IT resources.

For details of operations F1-F6, reference is made to the aforementioned regulatory examples C1-C6, which are not repeated herein.

In an optional embodiment, the MEC edge management and control device monitors CT resources and reports the second monitoring data to the MEC network management system, including at least one of the following operations:

operation G1: monitoring the power-on and power-off state of the infrastructure in the CT resources, and reporting the monitored power-on and power-off state of the infrastructure to an MEC network management system;

operation G2: monitoring the health state of a communication network link in CT resources, and reporting the monitored health state of the communication network link to an MEC network management system;

operation G3: monitoring the security state of a communication network link in CT resources, and reporting the monitored security state of the communication network link to an MEC network management system;

operation G4: monitoring the protocol state of a communication network link in the CT resources, and reporting the monitored protocol state of the communication network link to an MEC network management system;

operation G5: monitoring the traffic state on a communication network link in the CT resources, and reporting the monitored traffic state on the communication network link to an MEC network management system;

operation G6: and monitoring the health state of the communication network element in the CT resource, and reporting the monitored health state of the communication network element to the MEC network management system.

For details of operations G1-G6, reference is made to the aforementioned regulatory examples D1-D6, which are not repeated herein.

In the embodiment of the application, except that the central management and control device can manage and control the IT resources on the target MEC node, under the condition that the central management and control device does not manage or cannot manage and control the IT resources on the target MEC node, the MEC edge management and control device can autonomously manage and control the IT resources on the target MEC node, so that two-stage management and control of the IT resources are realized, the edge computing service in the IT resources can be ensured to normally operate, and the service quality of the edge computing service is improved. Further optionally, if each target MEC node is deployed with an MEC edge management and control device, for each MEC edge management and control device, IT may autonomously manage and control the IT resources on the target MEC node to which the central management and control device belongs, under the condition that the central management and control device does not or cannot manage and control the IT resources on the target MEC node to which the central management and control device belongs.

In practical applications, the MEC edge management and control device may lose an IT layer network connection with the central management and control device, or may lose a CT layer network connection with the MEC network management system. In this case, in order for the IT resources on the target MEC node to operate normally, the MEC edge management and control device may autonomously manage and control the IT resources on the target MEC node.

In an optional embodiment, the MEC edge management and control device autonomously manages and controls the IT resources of the target MEC node, including at least one of the following operations:

operation H1: and autonomously monitoring the state of an object in a running state in the IT resources of the target MEC node, and performing exception handling on the monitored target object with an abnormal running state.

Operation H2: and autonomously monitoring the life cycle of the object in the running state in the IT resources of the target MEC node, and controlling the object in the running state to stop, restart, migrate or delete after stopping according to the monitoring result. For a container or instance, the container or instance may be controlled to stop executing, restart after stopping, delete, etc.

Operation H3: and autonomously collecting log data in the IT resources of the target MEC node, performing data analysis on the log data, and executing subsequent actions according to the data analysis result. The log data includes, but is not limited to, bandwidth traffic of an instance in the target MEC node, current operating conditions of the instance, IO load of the instance, bandwidth traffic of the physical machine, current operating conditions of the physical machine, IO load of the physical machine, operating conditions of the edge management and control device, and/or operating conditions of other virtualized components. Optionally, subsequent actions such as charging, wind control and/or resource reallocation can be performed according to the analysis result of the log data, but is not limited thereto.

Operation H4: and autonomously carrying out traffic monitoring on IT resources of the target MEC node and carrying out blocking processing on the monitored traffic attack event.

Operation H5: and autonomously scanning the network security vulnerability of the IT resources of the target MEC node and repairing the scanned network security vulnerability problem.

Operation H6: and the resource usage of the IT resources in the target MEC node is autonomously monitored, and the resource expansion or the resource reduction of the IT resources in the target MEC node is carried out according to the monitoring result. Resources herein include, but are not limited to: device resources such as a physical machine, storage resources such as a memory and a magnetic disk, computing resources such as a CPU and a GPU, and network resources such as bandwidth. For these resources, when the usage amount is high, capacity expansion may be performed for these resources, and when the usage amount is low, capacity reduction may be performed for these resources.

For details of operations H1-H6, reference is made to the aforementioned regulatory examples E1-E6, which are not described herein again.

Further, in an optional embodiment, when the MEC edge management and control device loses IT layer network connection with the central management and control device, the MEC edge management and control device may autonomously manage and control the IT resources on the target MEC node, and after the IT layer network connection is restored with the central management and control device, the management and control data of the IT resources during the period of losing IT layer network connection may be synchronized to the central management and control device. It should be noted that the management and control data mainly includes data of management and control policies, manners, effects, and the like, and may also include monitoring data.

In yet another optional embodiment, when the MEC edge management and control device loses CT layer network connection with the MEC network management system, the MEC edge management and control device may autonomously manage and control the IT resources on the target MEC node, and after restoring CT layer network connection with the MEC network management system, synchronize the management and control data of the IT resources during the period of losing CT layer network connection to the central management and control device, and synchronize the second monitoring data of the CT resources during the period of losing CT layer network connection to the MEC network management system.

In this embodiment, an edge cloud system is integrated with a mobile communication network including an MEC node, a central management and control device in the edge cloud system is allowed to manage a target MEC node in the mobile communication network, the MEC edge management and control device is responsible for monitoring an IT resource and a CT resource on the target MEC node managed by the central management and control device respectively, and providing monitoring data to the central management and control device and the MEC network management system in the mobile communication network respectively, and the three cooperate with each other to realize management and control of the target MEC node, so that an MEC node closer to an end side can be used to provide edge computing service for a user, which is beneficial to reducing service response time delay and reducing bandwidth cost.

Fig. 4 is a schematic flowchart of another management and control method provided in an exemplary embodiment of the present application, which is applied to a central management and control device in an edge cloud system, and the method includes:

41. receiving first monitoring data reported by MEC edge management and control equipment, wherein the first monitoring data is obtained by the MEC edge management and control equipment monitoring IT resources on a target MEC node managed by central management and control equipment in a mobile communication network;

42. and managing and controlling the IT resources on the target MEC node according to the first monitoring data.

In an optional embodiment, the managing and controlling the IT resources on the target MEC node according to the first monitoring data includes: acquiring at least part of second monitoring data related to IT resources from an MEC network management system in a mobile communication network; and managing and controlling the IT resources on the target MEC node by combining at least part of the second monitoring data and the first monitoring data.

In this embodiment, the central control device 101 does not limit the implementation manner of obtaining at least part of the second monitoring data related to the IT resource from the MEC network management system 103. For example, the MEC network management system 103 may actively provide at least part of the second monitoring data related to the IT resource to the central management and control device 101. For another example, the central management and control device 101 periodically or aperiodically goes to the MEC network management system 103 to obtain at least part of the second monitoring data related to the IT resources. For details, reference may be made to the foregoing embodiments, which are not described herein again.

In this embodiment, the edge cloud system and the mobile communication network including the MEC node are integrated, allowing a central management and control device in the edge cloud system to manage a target MEC node, where the central management and control device is matched with the MEC edge management and control device, and managing and controlling the IT resources on the MEC node according to monitoring data of the MEC edge management and control device on the IT resources on the target MEC node, so that the MEC node closer to the end side can be used to provide edge computing services for users, which is beneficial to reducing service response delay and reducing bandwidth cost.

Fig. 5 is a schematic flowchart of another management and control method provided in an exemplary embodiment of the present application, which is applicable to an MEC network management system in a mobile communication network, and the method includes:

51. receiving second monitoring data reported by the MEC edge management and control equipment, wherein the second monitoring data are obtained by monitoring CT resources on target MEC nodes managed by central management and control equipment in an edge cloud system in a mobile communication network by the MEC edge management and control equipment;

52. and managing and controlling the CT resources on the target MEC node according to the second monitoring data.

For details of

steps

51 and 52, reference may be made to the related description in the foregoing system embodiment, and details are not repeated here.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps 31 to 33 may be device a; for another example, the execution subject of step 31 may be device a, and the execution subject of step 33 may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 31, 32, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

Fig. 6 is a schematic structural diagram of an MEC edge management and control device according to an exemplary embodiment of the present disclosure. As shown in fig. 6, the apparatus includes: a memory 64 and a processor 65.

A memory 64 for storing computer programs and may be configured to store other various data to support operations on the MEC edge policing apparatus. Examples of such data include instructions for any application or method operating on the MEC edge policing device, and the like.

The memory 64 may be implemented by any type or combination of volatile or non-volatile memory devices 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 or optical disks.

A processor 65, coupled to the memory 64, for executing computer programs in the memory 64 for: monitoring IT resources and CT resources on a target MEC node managed by a central management and control device in an edge cloud system in a mobile communication network; reporting first monitoring data obtained by monitoring IT resources to central control equipment, so that the central control equipment can control the IT resources on a target MEC node; and reporting second monitoring data obtained by monitoring the CT resources to an MEC network management system in the mobile communication network so that the MEC network management system can control the CT resources on the MEC nodes.

In an alternative embodiment, the processor 65 is further configured to: and under the condition that the central management and control equipment does not manage or cannot manage the IT resources on the target MEC node, the IT resources on the target MEC node are autonomously managed and controlled.

In an optional embodiment, when the central management and control device cannot manage and control the IT resources on the target MEC node, the processor 65 is specifically configured to: and under the condition that the IT layer network connection with the central management and control equipment is lost or the CT layer network connection with the MEC network management system is lost, the IT resources on the target MEC node are autonomously managed and controlled.

In an alternative embodiment, the processor 65 is further configured to: after the IT layer network connection is recovered with the central control equipment, the control data of the IT resources during the period of losing the IT layer network connection are synchronized to the central control equipment; or after restoring the network connection of the CT layer with the MEC network management system, synchronizing the control data of the IT resources to the central control equipment during the period of losing the network connection of the CT layer, and synchronizing the second monitoring data of the CT resources to the MEC network management system during the period of losing the network connection of the CT layer.

In an optional embodiment, the processor 65 is specifically configured to perform at least one of the following operations when autonomously managing the IT resources of the target MEC node: performing state monitoring on an object in an IT resource in an operating state, and performing exception handling on a target object with an abnormal monitored operating state; monitoring the life cycle of an object in an operation state in IT resources, and controlling the object in the operation state to stop according to a monitoring result, and restarting, migrating or deleting the object after stopping; collecting log data of IT resources, performing data analysis on the log data, and executing subsequent actions according to data analysis results; carrying out traffic monitoring on IT resources and carrying out blocking processing on the monitored traffic attack events; network security vulnerability scanning is carried out aiming at IT resources, and the scanned network security vulnerability problem is repaired; monitoring the usage amount of the IT resources, and performing resource expansion or volume reduction on the IT resources according to the monitoring result.

In an optional embodiment, when monitoring the IT resource and reporting the first monitoring data to the central control apparatus, the processor 65 is specifically configured to perform at least one of the following operations: monitoring the state of an object in an operation state in IT resources, reporting the monitored operation state of the object in the operation state to a central control device, so that the central control device can identify a target object with an abnormal operation state and perform exception processing on the target object; monitoring the life cycle of an object in an operation state in IT resources, and reporting the monitored life cycle of the object in the operation state to a central control device, so that the central control device can control the object in the operation state to stop, restart or delete after stopping; collecting log data of IT resources, and reporting the log data to central control equipment so that the central control equipment can perform data analysis on the log data and execute subsequent actions according to data analysis results; carrying out flow monitoring on IT resources, and reporting the monitored flow attack event to central control equipment so that the central control equipment can block the flow attack event; network security vulnerability scanning is carried out aiming at IT resources, and the scanned network security vulnerability problem is reported to central control equipment so that the central control equipment can repair the security vulnerability problem; monitoring the resource usage of the IT resources, and reporting the monitored resource usage information to the central control equipment so that the central control equipment can perform resource expansion or reduction on the IT resources.

In an optional embodiment, when monitoring the CT resource and reporting the second monitoring data to the MEC network management system, the processor 65 is specifically configured to perform at least one of the following operations: monitoring the power-on and power-off state of the infrastructure in the CT resources, and reporting the monitored power-on and power-off state of the infrastructure to an MEC network management system; monitoring the health state of a communication network link in CT resources, and reporting the monitored health state of the communication network link to an MEC network management system; monitoring the security state of a communication network link in CT resources, and reporting the monitored security state of the communication network link to an MEC network management system; monitoring the protocol state of a communication network link in the CT resources, and reporting the monitored protocol state of the communication network link to an MEC network management system; monitoring the traffic state on a communication network link in the CT resources, and reporting the monitored traffic state on the communication network link to an MEC network management system; and monitoring the health state of the communication network element in the CT resource, and reporting the monitored health state of the communication network element to the MEC network management system.

Further, as shown in fig. 6, the MEC edge management and control apparatus further includes: communication components 66, display 67, power components 68, audio components 69, and the like. Only some of the components are schematically shown in fig. 6, and it is not meant that the MEC edge policing apparatus includes only the components shown in fig. 6. In addition, the components shown by the dashed boxes in fig. 6 are optional components, not necessary components, and may be determined according to the implementation form of the MEC edge management and control device. If the MEC edge policing apparatus is implemented as a legacy server, a cloud server, a server array, or the like, the components shown by the dashed boxes may not be included.

The MEC edge management and control equipment provided by the embodiment of the application can monitor IT resources and CT resources on a target MEC node managed by central management and control equipment respectively in a scene that an edge cloud system is fused with a mobile communication network containing MEC nodes, and provides monitoring data for the central management and control equipment and an MEC network management system in the mobile communication network respectively.

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, which when executed by one or more processors, causes the one or more processors to implement the steps that can be performed by the MEC edge management and control device in the foregoing management and control method embodiment.

Fig. 7 is a schematic structural diagram of a central management and control device according to an exemplary embodiment of the present application. As shown in fig. 7, the apparatus includes: memory 74, processor 75, and communications component 76.

A memory 74 for storing computer programs and may be configured to store other various data to support operations on the central administration device. Examples of such data include instructions for any application or method operating on the central governing device, contact data, phonebook data, messages, pictures, videos, and the like.

The memory 74 may be implemented by any type or combination of volatile or non-volatile memory devices 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 or optical disks.

A processor 75, coupled to the memory 74, for executing computer programs in the memory 74 for: receiving first monitoring data reported by the MEC edge management and control equipment through a communication component 76, wherein the first monitoring data is obtained by monitoring IT (information technology) resources on a target MEC node managed by central management and control equipment in a mobile communication network by the MEC edge management and control equipment; and managing and controlling the IT resources on the target MEC node according to the first monitoring data.

In an optional embodiment, when the processor 75 manages and controls the IT resources on the target MEC node according to the first monitoring data, IT is specifically configured to: acquiring at least part of second monitoring data related to IT resources from an MEC network management system in a mobile communication network; and managing and controlling the IT resources on the target MEC node by combining at least part of the second monitoring data and the first monitoring data.

Further, as shown in fig. 7, the center managing and controlling apparatus further includes: display 77, power supply 78, audio 79 and other components. Only some of the components are schematically shown in fig. 7, and it is not meant that the central managing device includes only the components shown in fig. 7. In addition, the components shown by the dashed boxes in fig. 7 are optional components, not necessary components, and may be determined according to the implementation form of the central control device. If the central managing device is implemented as a traditional server, a cloud server, an array of servers, etc., the components shown in the dashed boxes may not be included.

The central management and control device provided by the embodiment of the application can manage and control target MEC nodes in a mobile communication network under the scene that an edge cloud system is fused with the mobile communication network comprising MEC nodes, and is matched with the MEC edge management and control device, and can manage and control IT resources on the MEC nodes according to monitoring data of the MEC edge management and control device on the IT resources on the target MEC nodes, so that the MEC nodes closer to the end side can be utilized to provide edge computing services for users, service response time delay is favorably reduced, and bandwidth cost is reduced.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing a computer program, which when executed by one or more processors causes the one or more processors to implement the steps that can be performed by the central management and control device in the foregoing management and control method embodiments.

Fig. 8 is a schematic structural diagram of an MEC network management device according to an exemplary embodiment of the present disclosure. The MEC network management equipment can be implemented as the MEC network management system in the foregoing embodiment. As shown in fig. 8, the apparatus includes: memory 84, processor 85, and communications component 86.

The memory 84 is used for storing computer programs and can be configured to store other various data to support operations on the MEC network management device. Examples of such data include instructions for any application or method operating on the MEC network management device, contact data, phonebook data, messages, pictures, videos, etc.

The memory 84 may be implemented by any type or combination of volatile or non-volatile memory devices 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 or optical disks.

A processor 85 coupled to the memory 84 for executing computer programs in the memory 84 for: receiving second monitoring data reported by the MEC edge management and control equipment through the communication component 86, wherein the second monitoring data are obtained by monitoring CT resources on target MEC nodes managed by central management and control equipment in an edge cloud system in the mobile communication network by the MEC edge management and control equipment; and managing and controlling the CT resources on the target MEC node according to the second monitoring data. For details of the control of the CT resource on the target MEC node according to the second monitoring data, reference may be made to the descriptions in control examples D1-D6 in the foregoing system embodiment, and details are not repeated here.

Further, as shown in fig. 8, the MEC network management device further includes: a display 87, a power supply component 88, an audio component 89, and the like. Only some components are schematically shown in fig. 8, and it is not meant that the MEC network management device includes only the components shown in fig. 8. In addition, the components shown by the dashed line boxes in fig. 8 are optional components, not necessarily optional components, and may specifically depend on the implementation form of the MEC network management device. If the MEC network management device is implemented as a traditional server, a cloud server, a server array, or the like, the components shown by the dashed boxes may not be included.

The MEC network management equipment provided by the embodiment of the application can allow central management and control equipment in the edge cloud system to manage a target MEC node under the scene that the edge cloud system is fused with a mobile communication network containing the MEC node, and is matched with the central management and control equipment and the MEC edge management and control equipment, and can manage and control CT resources on the target MEC node according to monitoring data of the CT resources on the target MEC node, which is reported by the MEC edge management and control equipment, so that the MEC node closer to the end side can be utilized to provide edge computing service for a user, service response delay is favorably reduced, and bandwidth cost is reduced.

Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, where the computer program, when executed by one or more processors, causes the one or more processors to implement the steps that can be executed by the MEC network management system in the foregoing control method embodiment.

The communication components of fig. 6-8 described above are configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, a 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

The displays in fig. 6-8 described above include screens, which may include Liquid Crystal Displays (LCDs) and Touch Panels (TPs). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The power supply components of fig. 6-8 described above provide power to the various components of the device in which the power supply components are located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

The audio components of fig. 6-8 described above may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

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

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A network system, comprising: the method comprises the following steps that central management and control equipment in an edge cloud system, an MEC network management system in a mobile communication network, target multi-access edge computing MEC nodes managed by the central management and control equipment, and MEC edge management and control equipment;

the central management and control device is configured to receive first monitoring data reported by the MEC edge management and control device; managing and controlling IT resources on the target MEC node according to the first monitoring data;

the MEC network management system is used for receiving second monitoring data reported by the MEC edge management and control equipment; managing and controlling CT resources on the MEC node according to the second monitoring data;

the MEC edge management and control equipment is used for monitoring the IT resources on the target MEC node and reporting the obtained first monitoring data to the central management and control equipment, and monitoring the CT resources on the target MEC node and reporting the obtained second monitoring data to the MEC network management system.

2. The system of claim 1, wherein the MEC edge management and control facility is further to:

and under the condition that the central management and control equipment does not manage or cannot manage the IT resources on the target MEC node, autonomously managing and controlling the IT resources on the target MEC node.

3. The system of claim 2, wherein the MEC edge management and control facility is to:

and under the condition that the IT layer network connection with the central management and control equipment is lost or the CT layer network connection with the MEC network management system is lost, the IT resources on the target MEC node are autonomously managed and controlled.

4. The system of claim 3, wherein the MEC edge management and control facility is further to:

after the IT layer network connection is recovered with the central control equipment, the control data of the IT resources during the period of losing the IT layer network connection are synchronized to the central control equipment;

alternatively, the first and second electrodes may be,

after restoring the network connection of the CT layer with the MEC network management system, synchronizing the control data of the IT resources to the central control equipment during the period of losing the network connection of the CT layer, and synchronizing the second monitoring data of the CT resources to the MEC network management system during the period of losing the network connection of the CT layer.

5. The network system according to claim 3 or 4, wherein the MEC edge management and control device, when autonomously managing and controlling the IT resources of the target MEC node, is specifically configured to perform at least one of the following operations:

performing state monitoring on the object in the IT resource in the running state, and performing exception handling on the monitored target object with the abnormal running state;

monitoring the life cycle of an object in the IT resource in the running state, and controlling the object in the running state to stop, restart after stopping, migrate or delete according to the monitoring result;

collecting log data of the IT resources, performing data analysis on the log data, and executing subsequent actions according to data analysis results;

carrying out traffic monitoring on the IT resources, and carrying out blocking processing on the monitored traffic attack events;

network security vulnerability scanning is carried out aiming at the IT resources, and the scanned network security vulnerability problem is repaired;

and monitoring the usage amount of the IT resources, and performing resource expansion or volume reduction on the IT resources according to a monitoring result.

6. The network system according to any one of claims 1 to 4, wherein the MEC edge management and control device is configured to perform at least one of the following operations when monitoring the IT resources and reporting the obtained first monitoring data to the central management and control device:

performing state monitoring on an object in an operation state in the IT resource, and reporting the monitored operation state of the object in the operation state to the central control equipment, so that the central control equipment can identify a target object with an abnormal operation state and perform exception processing on the target object;

monitoring the life cycle of an object in an operation state in the IT resources, and reporting the monitored life cycle of the object in the operation state to the central control equipment, so that the central control equipment can control the object in the operation state to stop, restart after stopping or delete;

collecting log data of the IT resources, and reporting the log data to the central control equipment so that the central control equipment can perform data analysis on the log data and execute subsequent actions according to data analysis results;

carrying out traffic monitoring on the IT resources, and reporting the monitored traffic attack event to the central control equipment so that the central control equipment can block the traffic attack event;

network security vulnerability scanning is carried out on the IT resources, and the scanned network security vulnerability problem is reported to the central control equipment so that the central control equipment can repair the security vulnerability problem;

and monitoring the resource usage amount of the IT resources, and reporting the monitored resource usage amount information to the central control equipment so that the central control equipment can perform resource capacity expansion or capacity reduction on the IT resources.

7. The network system according to any one of claims 1 to 4, wherein the MEC edge management and control device is configured to perform at least one of the following operations when monitoring the CT resource and reporting the obtained second monitoring data to the MEC network management system:

monitoring the power-on and power-off state of the infrastructure in the CT resources, and reporting the monitored power-on and power-off state of the infrastructure to the MEC network management system;

monitoring the health state of a communication network link in the CT resource, and reporting the monitored health state of the communication network link to the MEC network management system;

monitoring the security state of a communication network link in the CT resource, and reporting the monitored security state of the communication network link to the MEC network management system;

monitoring the protocol state of a communication network link in the CT resource, and reporting the monitored protocol state of the communication network link to the MEC network management system;

monitoring the traffic state on a communication network link in the CT resource, and reporting the monitored traffic state on the communication network link to the MEC network management system;

and monitoring the health state of the communication network element in the CT resource, and reporting the monitored health state of the communication network element to the MEC network management system.

8. The network system according to any one of claims 1 to 4, wherein the central management apparatus is further configured to:

acquiring at least part of second monitoring data related to the IT resources from the MEC network management system; and managing and controlling the IT resources on the target MEC node by combining at least part of the second monitoring data and the first monitoring data.

9. The network system according to any one of claims 1 to 4, wherein an MEC edge management and control device is deployed in each target MEC node.

10. A management and control method is suitable for MEC edge management and control equipment, and comprises the following steps:

monitoring IT resources and CT resources on a target MEC node managed by a central management and control device in an edge cloud system in a mobile communication network;

reporting first monitoring data obtained by monitoring the IT resources to the central control equipment so that the central control equipment can control the IT resources on the target MEC node; and

and reporting second monitoring data obtained by monitoring the CT resources to an MEC network management system in the mobile communication network so that the MEC network management system can control the CT resources on the MEC nodes.

11. The method of claim 10, further comprising:

12. The method of claim 11, wherein autonomously managing the IT resources on the target MEC node in the event that the central managing device is unable to manage the IT resources on the target MEC node comprises:

13. The method of claim 12, further comprising:

alternatively, the first and second electrodes may be,

14. The method of claim 12 or 13, wherein autonomously managing IT resources of the target MEC node comprises at least one of:

15. The method according to any one of claims 10 to 13, wherein monitoring the IT resource and reporting the first monitoring data to the central management and control device includes at least one of:

16. The method according to any one of claims 10 to 13, wherein monitoring the CT resource and reporting the second monitoring data to the MEC network management system comprises at least one of:

17. A management and control method is suitable for a central management and control device in an edge cloud system, and comprises the following steps:

receiving first monitoring data reported by MEC edge management and control equipment, wherein the first monitoring data is obtained by monitoring IT (information technology) resources on a target MEC node managed by the central management and control equipment in a mobile communication network by the MEC edge management and control equipment;

and managing and controlling the IT resources on the target MEC node according to the first monitoring data.

18. The method of claim 17, wherein managing IT resources on the target MEC node according to the first monitoring data comprises:

acquiring at least part of second monitoring data related to the IT resources from an MEC network management system in a mobile communication network;

and managing and controlling the IT resources on the target MEC node by combining at least part of the second monitoring data and the first monitoring data.

19. A management and control method, adapted to an MEC network management system in a mobile communication network, the method comprising:

receiving second monitoring data reported by MEC edge management and control equipment, wherein the second monitoring data are obtained by monitoring CT resources on a target MEC node managed by central management and control equipment in an edge cloud system in the mobile communication network by the MEC edge management and control equipment;

and managing and controlling the CT resources on the target MEC node according to the second monitoring data.

20. An MEC edge management and control apparatus, comprising: a memory and a processor;

the memory for storing a computer program;

the processor, coupled with the memory, to execute the computer program to:

monitoring IT resources and CT resources on a target MEC node managed by a central management and control device in an edge cloud system in a mobile communication network; reporting first monitoring data obtained by monitoring the IT resources to the central control equipment so that the central control equipment can control the IT resources on the target MEC node; and reporting second monitoring data obtained by monitoring the CT resources to an MEC network management system in the mobile communication network so that the MEC network management system can control the CT resources on the MEC nodes.

21. A central management and control device, comprising: a memory, a processor, and a communications component;

the memory for storing a computer program;

the processor, coupled with the memory, to execute the computer program to:

receiving first monitoring data reported by MEC edge management and control equipment through the communication component, wherein the first monitoring data are obtained by monitoring IT resources on a target MEC node managed by the central management and control equipment in a mobile communication network by the MEC edge management and control equipment;

22. An MEC network management device, comprising: a memory, a processor, and a communications component;

the memory for storing a computer program;

the processor, coupled with the memory, to execute the computer program to:

receiving second monitoring data reported by MEC edge management and control equipment through the communication assembly, wherein the second monitoring data are obtained by monitoring CT resources on target MEC nodes managed by central management and control equipment in an edge cloud system in the mobile communication network by the MEC edge management and control equipment;

23. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by one or more processors, causes the one or more processors to implement the steps of the method of any one of claims 10-19.