CN113300899B

CN113300899B - Network capability opening method, network system, device and storage medium

Info

Publication number: CN113300899B
Application number: CN202010296523.0A
Authority: CN
Inventors: 白常明
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-04-15
Filing date: 2020-04-15
Publication date: 2022-08-30
Anticipated expiration: 2040-04-15
Also published as: CN113300899A

Abstract

The embodiment of the application provides a network capacity opening method, a network system, equipment and a storage medium. In the embodiment of the application, a mobile communication network is fused with an edge cloud system, network capacity provided by a network capacity unit in the mobile communication network is opened to a central control device, the central control device acquires network capacity parameters corresponding to cloud computing services, and transmits the network capacity matched with the network capacity requirement to the cloud computing services based on the network capacity parameters, so that the cloud computing services can use the network capacity in the mobile communication network, and the advantages of the network capacity in the mobile communication network are fully exerted.

Description

Network capability opening method, network system, device and storage medium

Technical Field

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

Background

The 5G network abstracts more and wider network capacity, and has the key technology of 5G network capacity opening. The network capability in the 5G network can be used for internal network elements and applications of the communication network, and can be opened to the outside, so as to fully exert the advantages of the 5G network capability.

Although network capabilities have been open for a long time, no standard is followed for the specific implementation of network capabilities. In particular, there are many application scenarios of 5G network capability, such as enterprise communication, edge computing, logistics tracking, etc., and the open modes of 5G network capability are different for different application scenarios. How to open the 5G network capability facing the edge computing is a technical problem to be solved in the 5G network capability opening process.

Disclosure of Invention

Aspects of the present invention provide a network capability opening method, a network system, a device, and a storage medium for fully taking advantage of network capabilities in a mobile communication network.

An embodiment of the present application provides a network system, including: the system comprises a central management and control device in an edge cloud system, a network capacity open platform in a mobile communication network and at least one network capacity unit in the mobile communication network; the network capacity opening platform is used for opening the network capacity provided by at least one network capacity unit to the central control equipment; returning target network capacity parameters to the central control equipment according to a network capacity calling request initiated by the central control equipment; the central management and control equipment is used for: initiating a network capacity calling request to a network capacity open platform according to the network capacity requirement of the cloud computing service; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter returned by the network capacity open platform so that the cloud computing service can use the target network capacity.

An embodiment of the present application further provides a network system, including: the mobile communication system comprises a central management and control device in an edge cloud system and at least one network capacity unit in a mobile communication network; the network capacity unit is used for providing network capacity and providing respective network capacity parameters for the central management and control equipment; the central management and control equipment is used for: according to the network capacity requirement of the cloud computing service, determining a target network capacity parameter from the network capacity parameters of at least one network capacity unit, and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service so as to enable the cloud computing service to use the target network capacity.

The embodiment of the present application further provides a network capability opening method, which is applicable to a central control device in an edge cloud system, and the method includes: according to the network capacity requirement of the cloud computing service, a network capacity calling request is initiated to a network capacity open platform in the mobile communication network so as to provide a target network capacity parameter returned by the network capacity open platform; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter returned by the network capacity open platform so that the cloud computing service can use the target network capacity.

The embodiment of the present application further provides a network capability opening method, which is applicable to a network capability opening platform in a mobile communication network, and the method includes: opening network capacity provided by at least one network capacity unit in the mobile communication network to a central management and control device in the edge cloud system; receiving a network capacity calling request initiated by a central control device, wherein the network capacity calling request is initiated according to the network capacity requirement of the cloud computing service; and returning a target network capacity parameter to the central control equipment according to a network capacity calling request initiated by the central control equipment, wherein the target network capacity parameter points to the target network capacity matched with the network capacity requirement.

An embodiment of the present application further provides a central management and control device, including: a memory and a processor; the memory is used for storing a computer program; a processor is coupled with the memory for executing a computer program for: according to the network capacity requirement of the cloud computing service, a network capacity calling request is initiated to a network capacity open platform in the mobile communication network so as to provide a target network capacity parameter returned by the network capacity open platform; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter returned by the network capacity open platform so that the cloud computing service can use the target network capacity.

An embodiment of the present application further provides a network capability opening device, including: a memory and a processor; a memory for storing a computer program; a processor is coupled with the memory for executing a computer program for: opening network capacity provided by at least one network capacity unit in a mobile communication network to a central management and control device in an edge cloud system; receiving a network capacity calling request initiated by a central control device, wherein the network capacity calling request is initiated according to the network capacity requirement of the cloud computing service; and returning a target network capacity parameter to the central control equipment according to a network capacity calling request initiated by the central control equipment, wherein the target network capacity parameter points to the target network capacity matched with the network capacity requirement.

The embodiment of the present application further provides a network capacity opening method, which is applicable to a central control device in an edge cloud system, and the method includes: acquiring network capability parameters provided by at least one network capability unit in a mobile communication network; determining a target network capacity parameter from the network capacity parameters of at least one network capacity unit according to the network capacity requirement of the cloud computing service; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service so that the cloud computing service can use the target network capacity.

An embodiment of the present application further provides a central management and control device, including: a memory and a processor; the memory is used for storing a computer program; a processor is coupled with the memory for executing a computer program for: acquiring network capability parameters provided by at least one network capability unit in a mobile communication network; determining a target network capacity parameter from the network capacity parameters of at least one network capacity unit according to the network capacity requirement of the cloud computing service; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service so that the cloud computing service can use the target network capacity.

Embodiments of the present application also provide a computer readable storage medium storing a computer program, which when executed by a processor causes the processor to implement any one of the steps of the network capability opening method.

In the embodiment of the application, a mobile communication network is fused with an edge cloud system, network capacity provided by a network capacity unit in the mobile communication network is opened to a central control device, the central control device acquires network capacity parameters corresponding to cloud computing services, and transmits the network capacity matched with the network capacity requirement to the cloud computing services based on the network capacity parameters, so that the cloud computing services can use the network capacity in the mobile communication network, and the advantages of the network capacity in the mobile communication network are fully exerted.

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 central management and control device for managing MEC nodes according to an exemplary embodiment of the present disclosure;

fig. 1d is an interaction flowchart of another central management and control device for managing MEC nodes according to an exemplary embodiment of the present disclosure;

fig. 2a is an interaction flowchart of a mobile communication network opening a network capability to an edge cloud system according to an exemplary embodiment of the present application;

fig. 2b is an interaction flowchart of another mobile communication network opening network capability to an edge cloud system according to an exemplary embodiment of the present application;

fig. 3a is a schematic flowchart of a network capability opening method according to an exemplary embodiment of the present application;

fig. 3b is a schematic flowchart of another network capability opening method provided in an exemplary embodiment of the present application;

fig. 4 is a flowchart illustrating a further method for opening network capability according to an exemplary embodiment of the present application;

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

fig. 6 is a schematic structural diagram of a network capability openness device according to an exemplary embodiment of the present application.

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.

Aiming at the technical problem of how to open 5G network capacity for edge computing, in the embodiment of the application, a mobile communication network is fused with an edge cloud system, the network capacity provided by a network capacity unit in the mobile communication network is open for a central control device, the central control device acquires network capacity parameters corresponding to cloud computing services, and transmits the network capacity matched with the network capacity requirement to the cloud computing services based on the network capacity parameters, so that the cloud computing services can use the network capacity in the mobile communication network, and the advantages of the network capacity in the mobile communication network are fully exerted.

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 system 100 includes: the central management and control device 101 in the edge cloud system 104, the network capability open platform 111 in the mobile communication network 105, and the at least one network capability unit 112 in the mobile communication network 105.

In the present embodiment, the network architecture of the mobile communication network 105 and the communication system adopted are not limited. For example, the mobile communication network may be a 4G-standard mobile communication network, a 5G-standard 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 architecture of the mobile communication network 105, regardless of the standard, is divided from a business perspective, and mainly includes but is not limited to: an Access Network 107(Radio Access Network, RAN) and a Core Network 108(Core Network, CN); 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 element forms included in the access network 107 and the core network 108 of the mobile communication network 105 may be different according to different network systems. As shown in fig. 1a and 1b, taking a 5G network as an example, the 5G access network 107 mainly includes a 5G base station; the 5G base station is mainly configured to provide a 5G air interface protocol function, and support communication with the user equipment and the 5G core network 108. 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, as shown in fig. 1a and 1b, the 5G Core Network 108(5G Core Network, 5GC) 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 playback Function, NRF), a Policy Control Function (Policy Control Function, PCF), and an Application layer Function (AF). In addition, IT should be noted that the 5G network includes, in addition to various network elements in the access network 107 and the core network 108, some software systems 113, such as a BOSS system, operation and maintenance subsystems of each layer of network (e.g., operation and maintenance subsystem of the access network 107, operation and maintenance subsystem of the core network 108, operation and maintenance subsystem of a backbone network), an IT operation and maintenance subsystem, a network management system, and the like, as shown in fig. 1a and fig. 1 b. The BOSS system is an important software platform system for realizing 5G network operation, management and maintenance, and has the main functions of charging, authentication, customer relationship maintenance, network management, network optimization and the like.

Network elements in the mobile communication network 105 and associated software systems may provide network capabilities. In the embodiments of the present application, a network element and/or a software system that can provide some network capability is referred to as a network capability unit 112. In addition, in the embodiment of the present application, the manner in which the network capability unit 112 provides the network capability is not limited, for example, a certain network capability unit alone may provide a certain network capability, or a plurality of network capability units cooperate with each other to provide a certain network capability together. The network capability provided by the network capability unit 112 in the mobile communication network 105 may be different according to different mobile communication network systems. In addition, different network capability units 112 generally provide different network capabilities. The following is an example of a 5G network:

in the embodiment of the present application, the network capabilities provided by the network capability unit 112 in the 5G network are divided into a wireless capability, a wired capability, a charging capability, an operation and maintenance capability, a slicing capability, and the like, but are not limited thereto. Where radio capability refers to network capabilities provided by a network element and/or software system 113 in the 5G access network 107. For example, as shown in fig. 1a, the 5G base station in the 5G access network 107 may provide some wireless capability to the outside as the network capability unit 112. Wireless capabilities include, but are not limited to: wireless positioning capability, Radio Network Information Service (RNIS) capability, air interface transmission quality monitoring capability, air interface delay monitoring capability, air interface congestion monitoring capability, and the like. The wired capability refers to a network capability provided by the network elements and/or the software systems 113 in the network, such as the 5G core network 108, the backbone network, or the private network, which are connected in a wired manner. For example, network elements such as UDM, SMF, UPF, AF, etc. in the 5G core network 108 as the network capability unit 112 may provide some wired capabilities to the outside. Among these, wired capabilities include, but are not limited to: the ability to provide Quality of Service (QoS) for network links, the ability to provide network topology, etc. For another example, the UPF in the 5G network, the PCF, and the charging subsystem in the BOSS system, etc. as the network capability unit 112 cooperate with each other to provide the charging capability to the outside, as shown in fig. 1 a; billing capabilities include, but are not limited to: video traffic charging capability, traffic packet charging capability, and the like. For another example, the operation and maintenance subsystem of the 5G access network 107, the operation and maintenance subsystem of the core network 108, the IT operation and maintenance subsystem, and the operation and maintenance subsystem in the BOSS system may be used as the network capability unit 112 to cooperate with each other to provide the operation and maintenance capability; the operation and maintenance capabilities include, but are not limited to: automatic monitoring, system safety reinforcement, disaster recovery construction and the like. For another example, network elements from the access network 107 to the core network 108 in the 5G network cooperate with each other as the network capability unit 112 to provide the slicing capability to the outside. The slicing capability is an on-demand networking capability, and a plurality of virtual network slices can be separated from the infrastructure of a 5G network, and each network slice is logically isolated from the access network 107 to the core network 108, so that different service qualities can be provided, and various application requirements can be met.

In order to facilitate opening the network capability in the mobile communication network 105 to the outside, the mobile communication network 105 in the embodiment of the present application further includes a network capability opening platform 111, and the network capability opening platform 111 is mainly responsible for management or operation related to the opening of the network capability. For example, the network capability opening platform 111 may obtain information of various network capabilities existing in the mobile communication network 105, provide various network capability information to the network capability demander, and be responsible for mapping the network capability requirement of the network capability demander to the corresponding network capability unit 112, obtain network capability parameters from the corresponding network capability unit 112 and feed back the network capability parameters to the service demander, and so on. In deployment implementation, the network capability open platform 111 may be deployed in the mobile communication network 105 as an independent network element, for example, may be deployed in the access network 107 as an independent access network element, or may be deployed in the core network 108 as an independent core network element; alternatively, the functions of the network capability openness platform 111 may also be deployed on one or more existing network elements in the mobile communication network 105, for example, may be deployed in network elements such as AMF, UDM, SMF, UPF, AF, and PCF in a 5G network. In fig. 1a and fig. 1b, a network capability open platform 111 is illustrated as an example deployed in the core network 108 as an independent network element.

In this embodiment, the network capability demanding party may be a network element and an application inside the mobile communication network 105, that is, the network capability open platform 111 may provide a corresponding network capability for the network element and the application inside the mobile communication network 105. The network capability demander can be, among other things, an application, system, device, service or computing node, etc. external to the mobile communications network 105. In the embodiment of the present application, in order to improve the flexibility of the network capability opening and fully exert the advantage of the network capability in the mobile communication network 105, the edge cloud system 104 and the mobile communication network 105 are integrated, the network capability in the mobile communication network 105 can be opened toward the edge cloud system 104, and the network capability opening platform 111 cooperates with the central management and control device 101, so that the cloud computing service in the edge cloud system 104 can use the network capability in the mobile communication network 105. The edge cloud system 104 in the embodiment of the present application will be described first.

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. Edge cloud is a relative concept, which refers to a cloud computing platform relatively close to the end side, or an edge cloud is distinguished from a central cloud or a traditional cloud computing platform, which may include a data center or a computer room with a large resource scale and a centralized location, and an edge cloud is composed of a plurality of edge nodes 106 (as shown in fig. 1a), where the resource scale of a single edge node 106 is small, but the coverage of the edge cloud system 104 is wider by a plurality of edge nodes 106.

A central management and control device 101 is also deployed in the edge cloud system 104. The central control device 101 uses the edge node 106 as a control object, and performs unified control on at least one edge node 106 in the edge cloud system 104 in terms of resource scheduling, mirror image management, instance control, operation and maintenance, network, security, and the like, so as to place the cloud computing service in each edge node 106 for processing. In terms of deployment implementation, the central control apparatus 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 control apparatus 101 may also be deployed in one or more edge nodes 106 that it controls, which is not limited in this embodiment.

For edge node 106, a series of edge infrastructures are included, 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 edge node 106 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 edge 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 node 106, and may be, for example, an image file of an operating system, an application, or an operating configuration required to provide a cloud computing service for a user, which may be a file manufactured according to a certain format according to a specific series of files and in accordance with the computing deployment requirements of the edge node 106. 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 the present embodiment, the edge nodes 106 include, but are not limited to: edge cloud nodes deployed on own resources by the provider of the edge cloud system 104, and edge cloud nodes deployed on third-party resources by the provider of the edge cloud system 104 are referred to as cooperative nodes. Alternatively, the edge cloud nodes deployed on the own resources by the provider of the edge cloud system 104 may be, but are not limited to: edge Node Service (ENS). The ENS node can provide global coverage elastic distributed computing resources close to terminal users, response time delay, center load and overall cost can be optimized through near calculation and processing of terminal data, services are sunk to the edge of the end side, and calculation time delay and cost are effectively reduced. For the cooperative nodes, the cooperative nodes are different according to the different third-party resources. For example, the third-party resource may be a server, a switch, or the like in a power distribution room near the end user, and the provider of the edge cloud system 104 may deploy the video service on the server, the switch, or the like in the power distribution room to provide the video service to the end user through the cooperating node; as another example, the third party resource is a game server provided by a game service provider near the end user, and the edge cloud system provider may deploy the game service on the game server for providing the game service to the end user through the collaboration node in the immediate vicinity.

Further optionally, as shown in fig. 1b, the mobile communication network 105 in this embodiment further includes: at least one MEC node 102 and an MEC network management system 103. The MEC network management system 103 uses the MEC node 102 as a management and control object, and can manage and control 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. In deployment implementation, the MEC network management system 103 may be deployed in the mobile communication network 105 as an independent network element, for example, may be deployed in the access network 107 as an independent access network element, or may be deployed in the core network 108 as an independent core network element; alternatively, the function of the MEC network management system 103 may also be deployed on one or more existing network elements in the mobile communication network 105, for example, may be deployed in network elements such as AMF, UDM, SMF, UPF, AF, and PCF in a 5G network. In addition, the MEC node 102 may be deployed in the core network 108 or in the access network 107, which is not limited to this. In fig. 1b, the MEC network management system 103 is taken as an independent network element to be deployed in the core network 108, and the MEC node 102 is deployed in the access network 107 for example.

In a scenario where the mobile communication network 105 and the edge cloud system 104 are integrated, the central management and control device 101 may cooperate with the MEC network management system 103 in the mobile communication network 105 to manage the MEC nodes 102 in the mobile communication network 105. Based on this, the edge node 106 in the edge cloud system 104 may further include: MEC node 102 hosted by central hosting device 101 in mobile communication network 105. Specifically, a cooperation channel for performing cooperative management and control on the MEC node 102 is established between the central management and control device 101 and the MEC network management system 103 in the mobile communication network 105, and the MEC node 102 is managed based on the cooperation channel, and by virtue of the advantage that the MEC node 102 is closer to the end side, the MEC node 102 is utilized to provide edge computing service for the end user nearby. For the related flow of the central management and control device 101 and the MEC network management system 103 cooperating with each other to manage the MEC nodes, reference may be made to the description of the embodiments shown in fig. 1c to fig. 1d, which will not be described in detail herein.

In the embodiment of the present application, the network capability opening platform 111 in the mobile communication network 105 and the central management and control device 101 in the edge cloud system 104 are mutually matched, and a set of process for opening the network capability can be established between the mobile communication network 105, the edge cloud system 104 and the cloud computing service, so that the mobile communication network 105 can open the network capability for the edge cloud system 104, and the cloud computing service in the edge cloud system 104 can call or use the network capability opened by the mobile communication network, so that the network capability in the mobile communication network 105 can be fully exerted in various edge computing services, and finally the network capability in the mobile communication network 105 is expanded into the edge computing category.

The following describes a process of the mobile communication network 105 opening network capability to the edge cloud system 104 with reference to the interaction flow chart shown in fig. 2 a. The embodiment shown in fig. 2a comprises the following steps:

21a, the network capability opening platform 111 opens the network capability provided by the at least one network capability unit 112 to the central control device 101.

22a, the central management and control device 101 initiates a network capability calling request to the network capability open platform 111 according to the network capability requirement of the cloud computing service.

23a, the network capability opening platform 111 returns the target network capability parameter to the central control device 101 according to the network capability calling request initiated by the central control device 101.

24a, the central management and control equipment 101 transparently transmits the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter, so that the cloud computing service can use the target network capacity.

In step 21a, the network capability opening platform 111 may uniformly collect the network capabilities provided by at least one network capability unit 112 in the mobile communication network 105, and open the network capabilities to the edge cloud system 104 (specifically, the central management and control device 101 in the edge cloud system 104) through the capability opening interface, so that the edge cloud system 104 can call or use the corresponding network capabilities as required. Optionally, the network capability opening platform 111 may construct a network capability Application Programming Interface (API) according to the network capability provided by the at least one network capability unit 112, and open the network capability API to the central control device 101, so that the central control device 101 initiates a network capability call request. For the central control device 101, a network capability call request may be initiated to the network capability opening platform 111 through a network capability API provided by the network capability opening platform 111.

In the present embodiment, the embodiment of constructing the network capability API according to the network capability provided by the at least one network capability unit 112 is not limited. For example, a network capability API may be respectively constructed for the network capabilities provided by each network capability unit 112, and the central management and control device 101 may invoke the corresponding network capability API according to the actual service requirements, and initiate a network capability call request to the network capability open platform 111. Or, the network capabilities provided by the at least one network capability unit 112 may be summarized to uniformly construct a composite network capability API, and the central management and control device 101 may initiate a network capability call request to the network capability open platform 111 through the composite network capability API. Or, a customized network capability API may be provided for the service demand party, and the central management and control device 101 may initiate a network capability call request to the network capability open platform 111 through the customized network capability API, which is not limited herein.

In step 22a, the central managing device 101 may acquire the network capacity requirement of the cloud computing service. Here, the cloud computing service refers to a cloud computing service that the service demander needs to provide by the edge cloud system 104, and the cloud computing service needs to be deployed on one or more edge nodes 106 in the edge cloud system 104. In the present embodiment, the manner in which the central management and control apparatus 101 acquires the network capacity requirement of the cloud computing service is not limited. For example, when the service demander needs the edge cloud system 104 to provide cloud computing services for the service demander, the network capability requirement of the cloud computing service may be determined, and the network capability requirement may be provided to the central management and control device 101 through a human-computer interaction interface (e.g., a web page, an application page, a command window, or the like) provided by the central management and control device 101; based on this, the central management apparatus 101 may receive the network capacity requirement of its required cloud computing service provided by the service demander. Or, the network capacity requirement of the cloud computing service may be preset in the central control device 101 in advance, and based on this, the central control device 101 may directly obtain the preset network capacity requirement of the cloud computing service.

In the embodiment of the application, the content of the network capacity requirement is not limited, and the content of the network capacity requirement is different according to different cloud computing services. For example, the network capability requirements may include the type of network capability required by the cloud computing service, the length of use of the network capability, the manner of use, and other requirements for the network capability. After acquiring the network capacity requirement of the cloud computing service, the central management and control device 101 may accordingly initiate a network capacity invocation request to the network capacity opening platform 111. In the embodiment of the present application, the content of the network capability invocation request is also not limited. For example, the network capability invocation request may include, but is not limited to: the inquiry information of whether the required network capacity can be provided or not can also carry relevant information such as the service duration, the use mode and the requirement of the cloud computing service on the network capacity, the deployment position of the cloud computing service and the like. In addition, in the embodiment of the present application, an implementation that the central control device 101 initiates a network capability calling request to the network capability opening platform 111 is not limited. For example, the central managing and controlling device 101 may first send query information to the network capability openness platform 111 on whether the network capability (e.g., location capability) required by the cloud computing service can be provided; after the information that the network capacity openness platform 111 can provide the network capacity required by the cloud computing service is returned, relevant information such as the use duration, the use mode and the requirement for the network capacity of the cloud computing service and the deployment position of the cloud computing service is sent to the network capacity openness platform 111, so that the network capacity openness platform 111 can obtain the required network capacity parameters for the cloud computing service. For another example, the central management and control device 101 may send, in one communication process, query information that is included in the network capability calling request and is used for providing the required network capability, and related information such as a use duration, a use mode, a requirement for the network capability, a deployment location of the cloud computing service, and the like of the cloud computing service to the network capability open platform 111, so that the network capability open platform 111 obtains a required network capability parameter for the cloud computing service. For convenience of description, the network capability parameter acquired by the network capability openness platform 111 for the cloud computing service is referred to as a target network capability parameter.

In step 23a, the network capability opening platform 111 may obtain a required target network capability parameter for the cloud computing service according to the network capability calling request, and return the target network capability parameter to the central control device 101, so that the central control device 101 transparently transmits the target network capability matching with the network capability requirement of the cloud computing service according to the target network capability parameter. In the embodiment of the present application, an implementation manner of obtaining the target network capability parameter for the cloud computing service by the network capability open platform 111 is not limited, and the following description is given by way of example.

In an optional embodiment, the network capability openness platform 111 may determine, according to the network capability invocation request, a target network capability unit from at least one network capability unit 112, where the target network capability unit refers to the network capability unit 112 that may provide the network capability requested by the network capability invocation request; and then, acquiring the target network capacity parameters from the target network capacity unit and returning the target network capacity parameters to the central management and control device 101. Specifically, the network capability opening platform 111 may maintain a correspondence between the identifier of each network capability unit 112 and the type of the network capability provided by each network capability unit 112; based on this, the network capability open platform 111 may analyze the type of the network capability required by the cloud computing service from the network capability call request, match the analyzed type of the network capability in the foregoing corresponding relationship, determine a target network capability unit, obtain a target network capability parameter from the target network capability unit, and return the target network capability parameter to the central management and control device 101 through the network capability API.

In another alternative embodiment, the network capability openness platform 111 may maintain a correspondence between the identifier of each network capability unit, the type of the network capability provided by each network capability unit 112, and the network capability parameter corresponding to each network capability unit 112. Based on this, the network capability open platform 111 may analyze the type of the network capability required by the cloud computing service from the network capability call request, match the analyzed type of the network capability in the foregoing corresponding relationship, determine the target network capability unit and the target network capability parameter corresponding thereto, and return the target network capability unit and the target network capability parameter to the central management and control device 101 through the network capability API.

In the above-mentioned alternative embodiments, the target network capability unit may be one, or may be multiple, for example, 2, 5, etc. The target network capability parameter refers to configuration information required to invoke or use the network capability provided by the target network capability element. From these configuration information, the central control apparatus 101 may know which one or more network capability units capable of providing network capabilities for the cloud computing service, how to invoke or use the network capabilities provided by these network capability units 112, and which edge nodes are covered by these network capability units 112 (which means that the cloud computing service may be deployed to which edge nodes), and so on.

In step 24a, the central management and control device 101 may receive the target network capability parameter returned by the network capability opening platform 111; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter so that the cloud computing service can use the target network capacity. The target network capability refers to a network capability provided by the target network capability unit, and may include, for example, a charging capability, a positioning capability, a link QoS capability, a network topology capability, a slicing capability, and the like.

In the embodiment of the present application, an implementation manner in which the center management and control device 101 transparently transmits the target network capability to the cloud computing service according to the target network capability parameter is not limited. In an alternative embodiment, as shown in fig. 1a and 1b, a network capability open adaptation layer 114 is deployed in the edge cloud system 104, the network capability open adaptation layer 114 on the one hand being capable of interfacing with at least one network capability unit 112 in the mobile communication network 105; the term "interface" here means that the network capability openness adaptation layer 114 can establish a communication connection with the at least one network capability unit 112, and perform data transmission and interaction, for example, can obtain data related to network capabilities provided or generated by the at least one network capability unit 112; on the other hand, the central management and control device 101 may issue the target network capability parameter to the network capability open adaptation layer 114, and the network capability open adaptation layer 114 encapsulates the target network capability into a service API adapted to the cloud computing service according to the target capability parameter, and provides the service API to the cloud computing service, so that the cloud computing service uses the target network capability.

In the above alternative embodiment, the network capability openness adaptation layer 114 may determine the target network capability unit according to the target capability parameter. Optionally, the network capability open adaptation layer 114 may also determine, according to the target capability parameter, a manner of invoking the target network capability provided by the target network capability unit, and information such as an edge node or a location where the cloud computing service is located. The network capability open adaptation layer 114 serves as an adaptation layer between the target network capability unit and the cloud computing service, and is capable of acquiring data related to the target network capability provided by the target network capability unit, encapsulating the data related to the target network capability according to the service requirement of the cloud computing service, adding a service attribute to the data, and providing the data with the added service attribute to the cloud computing service in a service API manner, so as to achieve the purpose that the cloud computing service uses the target network capability. For example, the target network capability unit is a base station, and the target network capability is a positioning capability provided by the base station, the network capability open adaptation layer 114 may obtain location information of each terminal or user that needs to use the cloud computing service from the base station, package service attribute information such as an ID of the cloud computing service, an ID of an edge node where the cloud computing service is located, and a type of the cloud computing service on the basis of the location information to obtain a service API, and then provide the service API to the cloud computing service, and the cloud computing service may obtain the packaged data through the service API, thereby achieving a purpose of using the location information of each terminal or user. In addition to the above positioning capability, the target network capability may also be a traffic charging capability provided by a charging subsystem in the UPF, PCF, and BOSS systems, etc.

In the embodiment of the present application, the deployment position of the network capability open adaptation layer 114 in the edge cloud system 104 is not limited. In an optional embodiment, as shown in fig. 1b, the network capability open adaptation layer 114 is deployed on the central control device 101, and based on this, the central control device 101 further needs to deploy the network capability open adaptation layer 114 locally in advance. In this alternative embodiment, the cloud computing services on all the edge nodes 106 call or use the network capabilities in the mobile communication network 105 through the network capability open adaptation layer 114 on the central management apparatus 101. Alternatively, in another alternative embodiment, as shown in fig. 1a, the network capability open adaptation layer 114 may be deployed in advance on each edge node 106 in the edge cloud system 104. In this alternative embodiment, the cloud computing service on each edge node 106 may invoke or use network capabilities in the mobile communications network 105 through the local network capability open adaptation layer 114. Or, in yet another optional embodiment, a target edge node where the cloud computing service can be deployed may be determined according to the deployment requirement of the cloud computing service, and the network capability open adaptation layer 114 is deployed on the target edge node. In this alternative embodiment, for the cloud computing service on each edge node 106, if there is a need to invoke or use the network capability in the mobile communication network 105, the network capability open adaptation layer 114 may be deployed on the local node as needed, and then the network capability in the mobile communication network 105 may be invoked or used by the local network capability open adaptation layer 114. The target edge node may be an MEC node hosted by the central control device 101 in the mobile communication network 105, or an edge cloud node (e.g., ENS node) deployed by an edge cloud system 104 provider, or a cooperative node deployed on a third-party resource by the edge cloud system 104 provider.

Further optionally, the determining that the target edge node of the cloud computing service may be deployed includes: the central management and control equipment 101 determines candidate edge nodes capable of deploying cloud computing services according to service demand information provided by a service demand party; and according to the target network capacity parameter, selecting the edge node covered by the target network capacity from the candidate edge nodes as a target edge node. Optionally, when deploying the cloud computing service, the service demander may provide, to the central management and control device 101, service requirement information corresponding to the cloud computing service, in addition to providing the network capability requirement of the cloud computing service to the central management and control device 101. The service requirement information comprises information such as the type, the deployment position, the resource requirement and the service performance requirement of the cloud computing service to be deployed.

It should be noted that the service requirement information and the network capability requirement may be submitted to the central control device 101 by the service requirement party, or the service requirement party may be separately provided to the central control device 101, which is not limited herein.

For example, the service demander needs to deploy the map navigation service in the a city and the B city, the map navigation service needs the position information of the terminal device or the user using the service, that is, the map navigation service needs the positioning capability provided by the mobile communication network 105, and based on this, the service demander can submit the service requirement information that needs to deploy the map navigation service in the a city and the B city and the network capability requirement that needs the positioning capability to the central management and control device 101 at the same time. For the central control device 101, edge nodes in the city a and the city B may be determined as candidate edge nodes according to the city a and the city B in the service demand information. Further, the central control apparatus 101 may also initiate a network capability call request to the network capability opening platform 111 according to a network capability requirement, and the network capability opening platform 111 may return a target network capability parameter, where the target network capability parameter includes information of base stations capable of providing a positioning capability for a map navigation service, and information of cities covered by the base stations, such as a city a, a city M, and a city N. Then, the central control apparatus 101 may determine, in combination with the target network capability parameter, that the positioning capability in the mobile communication network 105 is not covered to the edge node in the B city, on which the map navigation service is not suitable to be deployed, and may determine that the positioning capability in the mobile communication network 105 is covered to the edge node in the a city, on which the map navigation service may be deployed, so that the target edge node may be determined from the edge node in the a city. Then, an instance corresponding to the map navigation service may be created on the target edge node, and the network capability open adaptation layer 114 may be deployed on the target edge node; furthermore, in subsequent operation, the map navigation service may invoke or use the positioning capability provided by the base station through the local network capability open adaptation layer 114.

For another example, the service demander needs to deploy the online education service in city C, and the service demander needs to know the link delay corresponding to the online education service, that is, the online education service needs to use the network link QoS capability provided by the mobile communication network. Based on this, the service demander may first provide the service demand information of the online education service that needs to be deployed in the city C to the central management and control device 101, and for the central management and control device 101, the candidate edge node may be determined from the edge node in the city C according to the service demand information. Further, the service requirement provides a network capacity requirement requiring the network link QoS capacity to the central control device 101, the central control device 101 may initiate a network capacity invoking request to the network capacity opening platform 111 according to the network capacity requirement, and the network capacity opening platform 111 may return a target network capacity parameter, where the target network capacity parameter includes information of network capacity units capable of providing the network link QoS capacity for the online education service and information of edge nodes covered by the network capacity units. Thereafter, the central managing device 101 may determine, from the candidate edge nodes, a target edge node to which the network link QoS capability in the mobile communication network 105 is to be covered in conjunction with the target network capability parameter, and deploy the online education service on the target edge node. Thereafter, a corresponding instance of the online education service may be created on the target edge node, and the network capability open adaptation layer 114 may be deployed on the target edge node; furthermore, in subsequent operation, the online education service may invoke or use the network link QoS capability provided by the corresponding network capability unit through the local network capability open adaptation layer 114.

In conjunction with the interaction flow diagram shown in fig. 2b, another embodiment for opening network capability of the mobile communication network 105 to the edge cloud system 104 includes the following steps:

21b, the network capability opening platform 111 opens the network capability provided by the at least one network capability unit 112 to the central control device 101.

22b, submitting the service requirement information and the network capacity requirement of the cloud computing service to the central management and control equipment 101 in the edge cloud system 104 by the service requirement direction.

23b, the central management and control device 101 initiates a network capability calling request to the network capability open platform 111 according to the network capability requirement of the cloud computing service.

24b, the network capability opening platform 111 returns the target network capability parameter to the central control device 101 according to the network capability calling request initiated by the central control device 101.

25b, the central management and control device 101 determines a target edge node capable of deploying the cloud computing service from the edge nodes in the edge cloud system 104 according to the service demand information and the target network capacity parameter.

26b, the central management and control device 101 associates the target network capacity parameter, the target edge node and the mirror image corresponding to the cloud computing service.

27b, the central management and control device 101 issues the mirror image corresponding to the cloud computing service to the target edge node, so as to deploy an instance corresponding to the cloud computing service at the target edge node.

28b, the cloud computing service on the target edge cloud node uses the target network capacity provided by the target network capacity unit in the operation process, and reports the use state and/or result information of the target network capacity to the central management and control device 101.

29b, the central management and control equipment 101 obtains the calling result of the target network capability according to the use state and/or the result information, and feeds the calling result back to the service demand party.

For a detailed description of step 21b, reference may be made to the foregoing embodiments, which are not repeated herein.

In step 22b, the edge node may carry the cloud computing service, and specifically, the service demander may submit the service requirement information of the cloud computing service to the central management and control device 101 in the edge cloud system 104, so that the central management and control device 101 performs resource scheduling and service carrying for the service. In addition, the cloud computing service carried by the edge node has a call demand for network capability (for example, 5G network capability) in the mobile communication network 105, and since the cloud computing service is run in the edge cloud system 104 and is subjected to resource scheduling and service carrying by the central management and control device 101, the call demand for the network capability by the cloud computing service also needs to be initiated by the central management and control device 101. In view of this, the service demander also needs to submit the network capacity requirements of the cloud computing service to the central management apparatus 101 in the edge cloud system 104. For details of the service requirement information and the network capability requirement, reference may be made to the foregoing embodiments, which are not described herein again.

After receiving the service requirement information and the network capacity requirement submitted by the service demander, the central management and control device 101 executes the operations in steps 23b and 24b on the one hand, and executes the operations in steps 25b-27b on the other hand. In step 23b and step 24b, the central management and control device 101 initiates a network capability calling request to the network capability open platform according to the network capability requirement of the cloud computing service. The network capability opening platform 111 returns the target network capability parameter to the central control device 101 according to the network capability calling request initiated by the central control device 101. In step 25b, the central management and control device 101 determines, according to the service requirement information and the target network capability parameter, a target edge node that can deploy the cloud computing service from edge nodes in the edge cloud system 104; in step 26b, associating the target network capacity parameter, the target edge node and a mirror image corresponding to the cloud computing service; in step 27b, the mirror image corresponding to the cloud computing service is sent to the target edge node, so as to deploy an instance corresponding to the cloud computing service at the target edge node. For details, reference may be made to the foregoing embodiments, which are not described herein again.

In step 28b, the target edge node deploys the mirror image and then performs instantiation operation, and the instance may call or use the target network capability according to the requirement during the execution process, and feeds back the use state and/or result information of the target network capability to the central management and control device 101. Correspondingly, the central control equipment 101 receives the use state and/or result information of the target network capacity reported by the instance; and obtaining a calling result of the target network capability according to the using state and/or the result information, and feeding the calling result back to the service demand party. Optionally, a network capability openness adaptation layer 114 is deployed on the central management and control device 101 or the target edge node, and the instance may invoke or use the target network capability through the network capability openness adaptation layer 114 in the execution process, and further specifically, the instance may achieve the purpose of using the target network capability by invoking a service API provided by the network capability openness adaptation layer 114.

According to the difference between the cloud computing service and the target network capability, the usage status and/or result information of the target network capability may also be different, which is illustrated as follows:

in an application scenario, a cloud computing service deployed on a target edge node by a service demand party is an internet of vehicles service, and a target network capability required to be used by the internet of vehicles service is a positioning capability provided by a base station, that is, the internet of vehicles service can call the positioning capability provided by the base station in the operation process, so that positioning information that a vehicle reaches two points of DE in the traveling process is acquired. Further, the internet of vehicles service may also compare the positioning information of the vehicle reaching two points of DE with the position information of the two points of DE in the map, so as to determine whether the positioning information given by the positioning capability is accurate, and feed back the accurate or inaccurate result to the central control device 101. If the comparison result is accurate, the central control device 101 may determine that the result of the positioning capability calling of the internet of vehicles service is successful, and feed back the result of the successful calling to the internet of vehicles service demander; if the comparison result is inaccurate, the central control device 101 may determine that the result of the positioning capability invoked by the car networking service this time is unsuccessful, and feed back the result of the unsuccessful invocation to the car networking service demander.

In another application scenario, cloud computing services deployed on a target edge node by a service demander are an internet of vehicles service and a video live broadcast service, the internet of vehicles service requires low time delay when driving, a user needs to watch the video live broadcast when driving, the low time delay and the high throughput of the system are required, therefore, network slices can be respectively constructed for the internet of vehicles service and the video live broadcast service by utilizing slice capability in a mobile communication network, and the required service quality is respectively provided for the internet of vehicles service and the video live broadcast service by utilizing different network slices. In the running process of the Internet of vehicles service and the live video service, whether the abnormal conditions such as interference with another service or resource robbery occur can be monitored; if no interference or resource robbery occurs between the car networking service and the video live broadcast service, the service state of the slicing capability is good; if interference or resource robbery and other situations occur between the car networking service and the video live broadcast service, the use state of the slicing capability is poor. The car networking service and the live video broadcast service can feed back the use state of the slicing capability to the central control equipment 101, if the use state of the slicing capability is good, the central control equipment 101 judges that the result of calling the slicing capability is successful, and feeds back the result of calling success to the service demand side; if the use state of the slicing capability is poor, the central management and control device 101 determines that the result of calling the slicing capability at this time is unsuccessful, and feeds back the result of calling the slicing capability that is unsuccessful to the service demand party.

In another application scenario, the cloud computing service deployed by the service demander on the target edge node is a live video service, and the target network capacity required by the live video service is the charging capacity provided by the BOSS system. The live video service can call the charging capability provided by the BOSS system in the running process to obtain the charging information generated by each terminal user watching the live video within a period of time, and compares the charging information obtained from the BOSS system with the actually generated flow charge, thereby judging whether the charging information given by the charging capability is accurate or not, and feeding back the accurate or inaccurate result to the central control equipment 101. If the result of the charging capability is accurate, the central control equipment 101 judges that the result of the charging capability calling of the live video service is successful, and feeds the calling successful result back to the live video service demand party; otherwise, the central control device judges that the result of the charging capability invoked by the live video service is unsuccessful, and feeds back the result of unsuccessful invocation to the live video service demand party.

For the above three cases, if the central control device 101 determines that the network capability is not successfully called this time, other fault tolerance or repair processes may be triggered. Other fault tolerance or repair procedures are not limited, for example, an alarm procedure may be started, or the central management and control device 101 may be notified to move the cloud computing service to another edge node, or a procedure of calling network capability again may be started, and so on.

In the following embodiments shown in fig. 1c and 1d, taking a target MEC node as an example, a cooperative channel for performing cooperative control on the target MEC node is established between the central control device 101 and the MEC network management system 103, and a flow of receiving and managing the target MEC node based on the cooperative channel is described. As shown in FIG. 1c, the nanotube process comprises 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 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 from the candidate MEC nodes.

15c, the central management and control device 101 initiates a resource admission application for the target MEC node 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 based on a through channel between the central management and control equipment and the target MEC node.

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 is implemented, which may be specifically determined according to the sequence of initiating registration from the target terminal and the MEC node 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 a target terminal, the target terminal 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, MEC nodes with spare resources may be considered candidate MEC nodes that can be hosted. For another example, an MEC node having an amount of vacant 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., GPU or CPU) 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 a geographic location, a resource amount, a resource type, and the like of an MEC node that needs 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 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 a target MEC node meeting the edge calculation requirement from the candidate MEC nodes according to the edge calculation requirement information, and return information of the MEC node meeting the edge calculation requirement information to an operator or an edge calculation service demander through the query page after the target MEC node is determined. 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, 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, from the candidate MEC nodes, the determined target MEC node meeting the edge computing requirement.

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 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 required 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 domains and/or edge computing services; wherein the scheduling domain points to an area where edge computing services need to be deployed, which determines the geographical location of the target MEC node. 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, an MEC node that can meet the requirements of the scheduling domain and/or QoS 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 edge cloud node 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 a target MEC node. Of course, the central management and control device 101 may also select, as the target edge cloud node, the MEC node 102 that can simultaneously satisfy the QoS requirements of the scheduling domain and the edge computing service, according to 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 central control apparatus 101 for acquiring the target MEC node is not limited, the target MEC node 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 that needs to be managed.

In step 15c, after determining the target MEC node, the central management and control device 101 initiates a resource admission application for the target MEC node 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 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 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, and then in step 16c, admission management is performed on the target MEC node. Optionally, the central management and control device 101 may manage the target MCE node based on a direct channel between the central management and control device and the target MEC node. Or, the central management and control device 101 may also manage the target MCE node 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 MCE node.

The central management and control device 101 may manage a target MCE node, 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;

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

network channel management and control: and managing and controlling a direct channel between the direct channel and the target MEC node.

Regarding infrastructure management: the infrastructure of the target MEC node 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 have a plurality of resources such as virtual machines, containers and the like. The method is mainly used for managing and controlling the infrastructure of the target MEC node, and mainly refers to a process for managing and controlling the infrastructure which can be managed in the target MEC node. The governing process includes but is not limited to: instruct the target MEC node to report infrastructure information that can be managed, instruct the target MEC node 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 capability of the target MEC node refers to some processing capability that the target MEC node has, such as operation and maintenance, alarm, acceleration, etc. The step of managing and controlling the platform capability of the target MEC node mainly refers to a process of determining whether the target MEC node has some capabilities required by the edge cloud system 104 and whether the target MEC node has capabilities required for providing edge computing services, and controlling the target MEC node to perform operations such as configuration or installation of related programs and the like so that the target MEC node has corresponding capabilities in the absence of the target MEC node. For example, a game is deployed on a target MEC node, and if the game requires the use of an acceleration service, the central control device 101 needs to determine whether the target MEC node supports an acceleration service protocol, and if not, controls the target MEC node to install the acceleration service protocol; if the protocol version is not the latest version, the acceleration service protocol is updated to the latest version so as to perform acceleration management and control on the target MEC node. 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 has an automatic alarm capability, and if not, the target MEC node is controlled to perform automatic alarm configuration, so that the target MEC node has the automatic alarm capability.

Regarding through channel management and control: the direct channel between the central control device 101 and the target MEC node 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 used by negotiation with the target MEC node, and establish a three-layer, four-layer, or higher channel with the target MEC node 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, in which a cooperation channel for performing cooperative management and control on a target MEC node is established between the central management and control device 101 and the MEC network management system 103, and the target MEC node is managed 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 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 from the candidate MEC nodes.

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

16d, the central management and control device 101 sends the data distribution rule and the resource configuration rule corresponding to the target MEC node 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 MCE node based on a direct channel between the central management and control equipment and the target MEC node.

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

For step 14d and step 15d, 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 to the MEC network management system 103, and may also send a resource configuration rule corresponding to the target MEC node 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 to the MEC network management system 103, so that the MEC network management system 103 establishes a data plane channel between the target terminal and the target MEC node.

Wherein the target terminal is a terminal in the mobile communication network 105 that needs to use the edge computing service. 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 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, 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 represented by the flow 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 the data offloading rule to a UPF network element connected to the target MEC node in the mobile communication network 105, and the UPF network element offloads the data from the target terminal to the target MEC node, so as to establish a data plane channel between the target terminal and the target MEC node. The UPF network element is responsible for distributing and guiding the traffic of the edge network to the target MEC node.

Regarding the resource allocation rules: the central control equipment 101 sends a resource configuration rule corresponding to a target MEC node to the MEC network management system 103; the MEC network management system 103 configures the resource configuration rule into the target MEC node, so that the target MEC node 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 to perform resource reservation for the edge computing service. For example, the target MEC node has a total of 10 virtual machine resources, which are numbered virtual machine 1, virtual machine 2, … …, and virtual machine 10, respectively. Deploying 3 edge computing services on a target MEC node, wherein the edge computing services are respectively edge computing service A1, edge computing service A2 and edge computing service A3, each edge computing service needs 2 virtual machine resources, a resource configuration rule can indicate that the target MEC node 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 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. And for the target MEC node, performing resource reservation for the edge computing service according to the resource allocation rule.

In practical applications, the information related to the target MEC node 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. That is, the MEC network management system 103 synchronizes the change information related to the target MEC node 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 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 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.

Further, as time goes by, the requirements of the edge computing service and the information of the target terminal may change, and the distribution rule needs to be adaptively changed in order to successfully provide the target terminal with the correct edge computing service. For example, a new edge computing service needs to configure resources on a target MEC node, but the resources on the target MEC node 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 split rule needs to be modified, and part of the resources originally distributed to the original edge computing service is distributed 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 distribution rule to the MEC network management system 103 again when the data distribution rule changes, so that the MEC network management system 103 updates the data plane channel between the target terminal and the target MEC node.

For example, if a new edge computing service is to be deployed on a target MEC node, the central management and control device 101 may notify the MEC network management system 103 of allocating resources at the target MEC node for the new edge computing service, but the resources at the target MEC node are insufficient, the MEC network management system 103 may notify the central management and control device 101 of modifying the forking rules and send the modified forking rules to the MEC network management system 103, and the MEC network management system 103 allocates resources at the target MEC node for the new edge computing service according to the modified forking rules.

In addition, as time goes by, the original edge computing service process on the target MEC node 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, so that the MEC network management system 103 controls the target MEC node to reset or release the resource.

For example, the edge compute service B1, the edge compute service B2, the edge compute service B1, and the edge compute service B2 deployed on the target MEC node occupy the resources of the target MEC node. 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, and then notifies the MEC network management system 103 to release the resource occupied by the target MEC node. After a period of time, the edge computing service demander needs to deploy an edge computing service B3 on the target MEC node, the central management and control device 101 notifies the MEC network management system 103 to allocate resources to the edge computing service B3 on the target MEC node, but there is not enough resources allocated to the edge computing service B3 on the target MEC node, at this time, the MEC network management system 103 notifies the central management and control device 101 to modify the split rules, the central management and control device 101 modifies the split rules, allocates part of the resources originally configured to the edge computing service B2 to the edge computing service B3 to form new split rules, the central management and control device 101 sends the new split rules to the MEC network management system 103, the MEC network management system 103 sends the new split rules to the UPF network element for configuration, and after the configuration is successful, the target MEC node successfully deploys the edge computing service B3 to complete resource resetting.

After hosting, the central management and control apparatus 101 may deploy an edge cloud platform on the target MEC node, 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 runs the instance to provide the edge computing service for the target terminal. Further, if the target MEC node is a bare metal, the central management and control device 101 may further install an operating system, perform initial configuration, activation, and other related operations for the target MEC node, where the operations may be specific to the type of the target MEC node.

In this embodiment, an edge cloud computing scheme with an IT and CT network converged is provided, which may not only open a network capability provided by a network capability unit in a mobile communication network to a central management and control device, but also establish a cooperative channel between the central management and control device and an MEC network management system for performing cooperative management and control on an MEC node under the condition that the mobile communication network includes the MEC node, so that the central management and control device manages a target MEC node based on the cooperative channel, thereby providing an edge computing service for a user by using the MEC node closer to an end side, reducing a service response time delay, and reducing a bandwidth cost.

It should be noted that, in the embodiment of the present application, the coverage area of the mobile communication network including the MEC node is not limited, and the mobile communication network that has already made full coverage is applicable to the embodiment of the present application, and the 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 hot spot 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 hot spot 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. Optionally, if there is no edge cloud node in a certain hotspot coverage area, the provider of the edge cloud system 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.

It should be noted that several of the above-listed manners for selecting the target hot spot coverage area may be used alternatively, or may be used in combination with the above-listed manners for implementation.

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 these areas, the central management and control device in the edge cloud system may establish a communication connection with a core network in the 4G mobile communication network in these areas, so that the user terminal in the area may reach the edge cloud system through the core network through a 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.

An exemplary embodiment of the present application also provides another network system, including: a central management and control device in the edge cloud system, and at least one network capability unit in the mobile communication network. Compared with the network system in the foregoing embodiment, the network system of this embodiment no longer includes a network capability opening platform, but the network capability unit directly opens the network capability that it can provide to the outside. In the network system provided in this embodiment, at least one network capability unit may provide a network capability and may provide respective network capability parameters to the central management and control device; the central control device can acquire the respective network capability parameter of at least one network capability unit. Furthermore, when a cloud computing service with a network capacity requirement needs to be deployed in the edge cloud system, the central management and control device may determine a target network capacity parameter from the network capacity parameters of the at least one network capacity unit according to the network capacity requirement of the cloud computing service, and transparently transmit the target network capacity matched with the network capacity requirement to the cloud computing service, so that the cloud computing service uses the target network capacity.

In the embodiment of the present application, an implementation manner in which at least one network capability unit provides respective network capability parameters to the central control device is not limited, and any implementation manner in which the network capability parameters of the network capability unit can be provided to the central control device is applicable to the embodiment of the present application. In an optional embodiment, the at least one network capability unit may construct a network capability API according to the network capability provided by the at least one network capability unit, and open the network capability API to the central control device, so that the central control device may obtain the network capability parameter of the at least one network capability unit through the network capability API provided by the at least one network capability unit. In another optional embodiment, the operator of the mobile communication network may also publish the network capability parameter of the at least one network capability element on an official website, a public platform, or the like, based on which the central management and control apparatus may obtain the network capability parameter of the at least one network capability element on the official website, the public platform, or the like of the operator. For the explanation and contents of the network capability parameters, reference may be made to the foregoing embodiments, which are not described herein again.

In an optional embodiment, a network capability open adaptation layer is deployed in the edge cloud system, and the network capability open adaptation layer is in butt joint with at least one network capability unit; the central control device can issue the target network capacity parameter to the network capacity open adaptation layer, the network capacity open adaptation layer packages the target network capacity into a service API adapted to the cloud computing service, and the service API is provided for the cloud computing service so that the cloud computing service can use the target network capacity. For a description of the network capability open adaptation layer, reference may be made to the foregoing embodiments, which are not described herein again.

It should be noted that the network system provided in this embodiment is different from the network systems shown in fig. 1a and fig. 1b in that at least one network capability unit in this embodiment is directly interfaced with a central management and control device, opens a network capability to the central management and control device, and provides respective network capability parameters, and the whole process does not involve a network capability opening platform, and other contents are the same as or similar to those in the foregoing embodiments, and specific contents may refer to the foregoing embodiments and are not described herein again.

Fig. 3a is a schematic flowchart of a method for opening network capability according to an exemplary embodiment of the present application, where the method is applied to a central control device in an edge cloud system, and the method includes:

31a, initiating a network capacity calling request to a network capacity open platform in a mobile communication network according to the network capacity requirement of the cloud computing service so as to provide a target network capacity parameter returned by the network capacity open platform;

and 32a, transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter returned by the network capacity open platform, so that the cloud computing service can use the target network capacity.

In step 31a, the central management and control device may acquire a network capacity requirement of the cloud computing service. The cloud computing service refers to a cloud computing service which is provided by a service demander and needs to be provided by an edge cloud system, and the cloud computing service needs to be deployed to one or more edge nodes in the edge cloud system. In this embodiment, the manner in which the central control device acquires the network capacity requirement of the cloud computing service is not limited. For details, reference may be made to the foregoing embodiments and no further description is provided herein.

In the embodiment of the application, the content of the network capacity requirement is not limited, and the content of the network capacity requirement is different according to different cloud computing services. For example, the network capability requirements may include the type of network capability required for the cloud computing service, the length of time the network capability is used, the manner of use, and other requirements for the network capability. After the network capacity requirement of the cloud computing service is obtained, the central management and control device can accordingly initiate a network capacity calling request to the network capacity open platform. In the embodiment of the present application, the content of the network capability invocation request is also not limited. In addition, in the embodiment of the present application, an implementation manner in which the central control device initiates the network capability call request to the network capability open platform is not limited. For details, reference may be made to the foregoing embodiments, which are not described herein again. For convenience of description, the network capability parameter acquired by the network capability open platform for the cloud computing service is referred to as a target network capability parameter.

In step 32a, the central management and control device may receive a target network capability parameter returned by the network capability open platform; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter so that the cloud computing service can use the target network capacity. The target network capability refers to a network capability provided by the target network capability unit, and may include, but is not limited to: wireless capability, wired capability, charging capability, operation and maintenance capability, slicing capability and the like.

In this embodiment, an implementation manner in which the central control device transparently transmits the target network capability to the cloud computing service according to the target network capability parameter is not limited. In an optional embodiment, a network capability open adaptation layer is deployed in the edge cloud system, and the network capability open adaptation layer can be in interface with at least one network capability unit in the mobile communication network; the term "interface" here means that the network capability open adaptation layer can establish a communication connection with at least one network capability unit, and perform data transmission and interaction, for example, can acquire data related to network capability provided or generated by at least one network capability unit; on the other hand, the central control device may issue the target network capacity parameter to the network capacity open adaptation layer, and the network capacity open adaptation layer encapsulates the target network capacity into a service API adapted to the cloud computing service according to the target capacity parameter, and provides the service API to the cloud computing service, so that the cloud computing service uses the target network capacity.

In the above optional embodiment, the network capability openness adaptation layer may determine the target network capability unit according to the target capability parameter. Optionally, the network capability open adaptation layer may also determine, according to the target capability parameter, a manner of invoking the target network capability provided by the target network capability unit, and information such as an edge node or a location where the cloud computing service is located. The network capacity open adaptation layer is used as an adaptation layer between the target network capacity unit and the cloud computing service, can acquire data related to the target network capacity provided by the target network capacity unit, can package the data related to the target network capacity according to the service requirement of the cloud computing service, adds a service attribute to the data, and provides the data with the added service attribute to the cloud computing service in a service API mode, so that the purpose that the cloud computing service uses the target network capacity is achieved. For details, reference may be made to the foregoing embodiments, which are not described herein again.

In the embodiment of the present application, the deployment position of the network capability open adaptation layer in the edge cloud system is not limited. In an optional embodiment, the network capability open adaptation layer is deployed on the central management and control device, and based on this, the central management and control device further needs to deploy the network capability open adaptation layer locally in advance. In this alternative embodiment, the cloud computing service on all edge nodes calls or uses the network capability in the mobile communication network through the network capability open adaptation layer on the central management and control device. Or, in another alternative embodiment, the network capability open adaptation layer may be deployed on each edge node in the edge cloud system in advance. In this alternative embodiment, the cloud computing service on each edge node may invoke or use network capabilities in the mobile communications network through the local network capability open adaptation layer. Or, in yet another optional embodiment, a target edge node where the cloud computing service can be deployed may be determined according to a deployment requirement of the cloud computing service, and a network capability open adaptation layer is deployed on the target edge node. In this optional embodiment, for the cloud computing service on each edge node, if there is a need to invoke or use a network capability in the mobile communication network, the network capability open adaptation layer may be deployed on the local node as needed, and then the network capability in the mobile communication network is invoked or used through the local network capability open adaptation layer. The target edge node may be an MEC node hosted by a central management and control device in the mobile communication network, or an edge cloud node (e.g., an ENS node) deployed by an edge cloud system provider, or a cooperative node deployed on a third-party resource by the edge cloud system provider.

Further optionally, the determining that the target edge node of the cloud computing service can be deployed includes: the method comprises the steps that a central management and control device determines candidate edge nodes capable of deploying cloud computing services according to service demand information provided by a service demand party; and according to the target network capacity parameter, selecting the edge node covered by the target network capacity from the candidate edge nodes as a target edge node. Optionally, when deploying the cloud computing service, the service demander may provide the network capacity requirement of the cloud computing service to the central management and control device, and may also provide service requirement information corresponding to the cloud computing service to the central management and control device. The service requirement information comprises information such as the type, the deployment position, the resource requirement and the service performance requirement of the cloud computing service to be deployed.

It should be noted that the service requirement information and the network capability requirement may be submitted to the central control device by the service requirement party, or the service requirement party may be separately provided to the central control device, which is not limited herein. For details, reference may be made to the foregoing embodiments, which are not described herein again.

In an optional embodiment, after determining that a target edge node of the cloud computing service can be deployed, associating a target network capacity parameter, the target edge node, and a mirror image corresponding to the cloud computing service; and issuing the mirror image corresponding to the cloud computing service to the target edge node so that the target edge node deploys the instance corresponding to the cloud computing service. In addition, in order to record more contents related to the cloud computing service, in addition to the above information, service requirement information, network capability requirement information, terminal device information, and the like may be associated, which is not limited.

And the target edge node deploys the mirror image and then performs instantiation operation, the instance can call or use the target network capacity according to the requirement in the execution process, and feeds back the use state and/or result information of the target network capacity to the central control equipment. Correspondingly, the central management and control equipment receives the use state and/or result information of the target network capacity reported by the example; and obtaining a calling result of the target network capability according to the using state and/or the result information, and feeding the calling result back to the service demand party. Optionally, a network capability open adaptation layer is deployed on the central management and control device or the target edge node, and the instance may invoke or use the target network capability through the network capability open adaptation layer in the execution process, and further specifically, the instance may achieve the purpose of using the target network capability by invoking a service API provided by the network capability open adaptation layer.

Fig. 3b is a schematic flowchart of another network capability opening method provided in an exemplary embodiment of the present application, where the method is applied to a central control device in an edge cloud system, and the method includes:

31b, acquiring respective network capability parameters provided by at least one network capability unit in the mobile communication network;

32b, determining a target network capacity parameter from the network capacity parameters of at least one network capacity unit according to the network capacity requirement of the cloud computing service;

and 33b, transmitting the target network capacity matched with the network capacity requirement to the cloud computing service in a transparent mode so that the cloud computing service can use the target network capacity.

In the embodiment of the present application, an implementation manner in which at least one network capability unit provides respective network capability parameters to the central control device is not limited, and any implementation manner in which the network capability parameters of the network capability unit can be provided to the central control device is applicable to the embodiment of the present application. In an optional embodiment, at least one network capability unit may construct a network capability API according to the network capability provided by the network capability unit, and open the network capability API to the central control device, so that the central control device may obtain the network capability parameter of at least one network capability unit through the network capability API provided by each of the at least one network capability unit. In another optional embodiment, the operator of the mobile communication network may also publish the network capability parameter of the at least one network capability element on an official website, a public platform, or the like, based on which the central management and control apparatus may obtain the network capability parameter of the at least one network capability element on the official website, the public platform, or the like of the operator. For the explanation and contents of the network capability parameters, reference may be made to the foregoing embodiments, which are not described herein again.

It should be noted that the difference between the network capability opening method provided in this embodiment and the network capability opening method shown in fig. 3a is that at least one network capability unit in this embodiment directly interfaces with the central management and control device, opens the network capability to the central management and control device, and provides respective network capability parameters, and the whole process does not involve a network capability opening platform, and other contents are the same as or similar to those in the foregoing embodiment, and specific contents may refer to the foregoing embodiment, and are not described again here.

Fig. 4 is a flowchart of another network capability opening method provided in an exemplary embodiment of the present application, where the method is applied to a network capability opening platform in a mobile communication network, and the method includes:

41. opening network capacity provided by at least one network capacity unit in the mobile communication network to a central management and control device in the edge cloud system;

42. receiving a network capacity calling request initiated by a central control device, wherein the network capacity calling request is initiated according to the network capacity requirement of the cloud computing service;

43. and returning a target network capacity parameter to the central control equipment according to a network capacity calling request initiated by the central control equipment, wherein the target network capacity parameter points to the target network capacity matched with the network capacity requirement.

In step 41, the network capabilities provided by the at least one network capability unit include at least one of: wireless capability, wired capability, billing capability, operation and maintenance capability, and slicing capability. The network capability opening platform can uniformly collect network capabilities provided by at least one network capability unit in the mobile communication network, and open the network capabilities to the edge cloud system (specifically, a central management and control device in the edge cloud system) through the capability opening interface, so that the edge cloud system can call or use the corresponding network capabilities as required. Optionally, the network capability opening platform may construct a network capability application programming interface API according to the network capability provided by the at least one network capability unit, and open the network capability API to the central control device, so that the central control device initiates the network capability call request. The network capacity calling request is initiated by the central management and control equipment according to the network capacity requirement of the cloud computing service. In this embodiment, the embodiment of constructing the network capability API according to the network capability provided by at least one network capability unit is not limited. For details, reference may be made to the foregoing embodiments, which are not described herein again.

In the embodiment of the application, the content of the network capacity requirement is not limited, and the content of the network capacity requirement is different according to different cloud computing services. In the embodiment of the present application, the content of the network capability invocation request is also not limited. For details, reference may be made to the foregoing embodiments, which are not described herein again.

In step 43, the network capability open platform may obtain a required target network capability parameter for the cloud computing service according to the network capability call request, and return the target network capability parameter to the central control device, so that the central control device transparently transmits the target network capability matching with the network capability requirement to the cloud computing service according to the target network capability parameter. In the embodiment of the present application, an implementation manner that the network capability open platform acquires the target network capability parameter for the cloud computing service is not limited, which is illustrated below.

In an optional embodiment, the network capability openness platform may determine, according to the network capability invocation request, a target network capability unit from the at least one network capability unit, where the target network capability unit is a network capability unit that can provide the network capability requested by the network capability invocation request; and then, acquiring the target network capacity parameters from the target network capacity unit and returning the target network capacity parameters to the central management and control equipment. Specifically, the network capability open platform may maintain a correspondence between the identifier of each network capability unit and the type of the network capability provided by each network capability unit; based on the network capacity open platform, the network capacity open platform can analyze the type of the network capacity required by the cloud computing service from the network capacity call request, match the analyzed type of the network capacity in the corresponding relation, determine a target network capacity unit, acquire target network capacity parameters from the target network capacity unit and return the target network capacity parameters to the central control equipment through a network capacity API.

In another alternative embodiment, the network capability openness platform may maintain a correspondence between the identifier of each network capability unit, the type of the network capability provided by each network capability unit, and the network capability parameter corresponding to each network capability unit. Based on the method, the network capacity open platform can analyze the type of the network capacity required by the cloud computing service from the network capacity call request, match the analyzed network capacity type in the corresponding relation, determine the target network capacity unit and the corresponding target network capacity parameter, and return the target network capacity unit and the corresponding target network capacity parameter to the central control equipment through the network capacity API.

In the above-mentioned alternative embodiments, the target network capability unit may be one, or may be multiple, for example, 2, 5, etc. The target network capability parameter refers to configuration information required to invoke or use the network capability provided by the target network capability unit. According to the configuration information, the central management and control device can know which one or more network capacity units capable of providing network capacity for the cloud computing service, how to call or use the network capacity provided by the network capacity units, which edge nodes are covered by the network capacity units (which means that the cloud computing service can be deployed to which edge nodes), and the like.

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 41 to 43 may be device a; for another example, the execution subject of

steps

41 and 42 may be device a, and the execution subject of step 43 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 41, 42, 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. 5 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. 5, the center regulating apparatus includes: a memory 54 and a processor 55.

Further, as shown in fig. 5, the center managing and controlling apparatus further includes: communications component 56, display 57, power component 58, audio component 59, and the like. Only some of the components are schematically shown in fig. 5, and it is not meant that the central managing device includes only the components shown in fig. 5. In addition, the components shown in the dashed boxes in fig. 5 are optional components, not required components.

A memory 54 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 54 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 55 coupled to the memory 54 for executing computer programs in the memory 54 for: according to the network capacity requirement of the cloud computing service, a network capacity calling request is initiated to a network capacity open platform in the mobile communication network so as to provide a target network capacity parameter returned by the network capacity open platform; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter returned by the network capacity open platform so that the cloud computing service can use the target network capacity.

In an optional embodiment, a network capability open adaptation layer is deployed in the edge cloud system, the network capability open adaptation layer is in butt joint with a network capability unit in the mobile communication network, and the processor 55 is specifically configured to, when transmitting, to the cloud computing service, the target network capability matched with the network capability requirement according to the target network capability parameter returned by the network capability open platform, in order for the cloud computing service to use the target network capability: and issuing the target network capacity parameters to a network capacity open adaptation layer, packaging the target network capacity into a service API adapted to the cloud computing service by the network capacity open adaptation layer, and providing the service API to the cloud computing service so that the cloud computing service can use the target network capacity.

In an optional embodiment, before issuing the target network capability parameter to the network capability open adaptation layer, the processor 55 is further configured to: a network capacity open adaptation layer is deployed locally in a central control device in advance; or, a network capacity open adaptation layer is deployed on each edge node in the edge cloud system in advance; or determining a target edge node where the cloud computing service can be deployed, and deploying a network capability open adaptation layer on the target edge node.

In an optional embodiment, when determining that the target edge node of the cloud computing service may be deployed, the processor 55 is specifically configured to: determining candidate edge nodes capable of deploying cloud computing services according to service demand information provided by a service demand party; and according to the target network capacity parameters, selecting the edge nodes covered by the target network capacity from the candidate edge nodes as target edge nodes.

In an optional embodiment, after determining that the target edge node of the cloud computing service can be deployed, the processor 55 is further configured to: associating the target network capacity parameter, the target edge node and a mirror image corresponding to the cloud computing service; and issuing the mirror image corresponding to the cloud computing service to the target edge node so that the target edge node deploys the instance corresponding to the cloud computing service.

In an alternative embodiment, processor 55 is further configured to: receiving the use state and/or result information of the target network capacity reported by the instance through the communication component 56; and obtaining a calling result of the target network capability according to the using state and/or the result information, and feeding the calling result back to the service demand party.

Accordingly, the present application also provides a computer readable storage medium storing a computer program, which when executed by a processor causes the processor to implement the steps in the method embodiment shown in fig. 3 a.

The embodiment of the present application further provides another central control device, which has the same or similar structure as the central control device provided in the embodiment shown in fig. 5, and the internal structure thereof can refer to the embodiment shown in fig. 5. The difference from the central management and control device shown in fig. 5 is that: the functions performed by the processor in executing the computer programs stored in the memory vary. The central control apparatus of the present embodiment, the processor thereof executes the computer program in the memory for: acquiring network capability parameters provided by at least one network capability unit in a mobile communication network; determining a target network capacity parameter from the network capacity parameters of at least one network capacity unit according to the network capacity requirement of the cloud computing service; and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service so that the cloud computing service can use the target network capacity.

In an optional embodiment, a network capability open adaptation layer is deployed in the edge cloud system, and the network capability open adaptation layer is in butt joint with at least one network capability unit; when the processor transparently transmits the target network capacity matched with the network capacity requirement to the cloud computing service according to the target network capacity parameter returned by the network capacity open platform, the processor is specifically configured to: and issuing the target network capacity parameter to a network capacity open adaptation layer, packaging the target network capacity into a service API adapted to the cloud computing service by the network capacity open adaptation layer, and providing the service API for the cloud computing service so that the cloud computing service can use the target network capacity.

Accordingly, the present application also provides a computer readable storage medium storing a computer program, and when the computer program is executed by a processor, the computer program causes the processor to implement the steps in the method embodiment shown in fig. 3 b.

Fig. 6 is a schematic structural diagram of a network capability openness device according to an exemplary embodiment of the present application. As shown in fig. 6, the apparatus includes: a memory 64 and a processor 65.

Further, as shown in fig. 6, the network capability openness device further includes: communication components 66, display 67, power components 68, audio components 69, and the like. Only some components are schematically shown in fig. 6, and it is not meant that the network capability openness device includes only the components shown in fig. 6. In addition, the components shown in the dashed boxes in fig. 6 are optional components, not required components.

The memory 64 is used for storing computer programs and may be configured to store other various data to support operations on the network capability openness device. Examples of such data include instructions for any application or method operating on a network capable open device, contact data, phonebook data, messages, pictures, videos, 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: opening network capacity provided by at least one network capacity unit in a mobile communication network to a central management and control device in an edge cloud system; receiving, by the communication component 66, a network capacity invoking request initiated by the central management and control device, where the network capacity invoking request is initiated according to a network capacity requirement of the cloud computing service; and returning a target network capacity parameter to the central control equipment according to a network capacity calling request initiated by the central control equipment, wherein the target network capacity parameter points to the target network capacity matched with the network capacity requirement.

In an optional embodiment, when the processor 65 opens the network capability provided by at least one network capability unit in the mobile communication network to the central management and control device in the edge cloud system, the processor is specifically configured to: and constructing a network capability application programming interface API according to the network capability provided by the at least one network capability unit, and opening the network capability API to the central control equipment so that the central control equipment can initiate a network capability calling request.

In an optional embodiment, when the processor 65 returns the target network capability parameter to the central management and control device according to a network capability call request initiated by the central management and control device, specifically, the processor is configured to: determining a target network capacity unit from at least one network capacity unit according to the network capacity calling request; and acquiring the target network capacity parameters from the target network capacity unit and returning the target network capacity parameters to the central control equipment.

Accordingly, embodiments of the present application further provide a computer-readable storage medium storing a computer program, where the computer program can implement the steps that can be executed by the network capability opening device in the foregoing network capability opening method embodiment.

The communication components of fig. 5 and 6 described above are configured to facilitate wired or wireless communication between the device in which the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, a mobile communication network such as 2G, 3G, 4G/LTE, 5G, or the like, 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 comprises a Near Field Communication (NFC) module to facilitate short-range communication. 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. 5 and 6 described above include screens, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive 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. 5 and 6 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. 5 and 6 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 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 system comprises a central management and control device in an edge cloud system, a network capacity open platform in a mobile communication network and at least one network capacity unit in the mobile communication network;

the network capacity opening platform is used for opening the network capacity provided by the at least one network capacity unit to the central control equipment; returning target network capacity parameters to the central control equipment according to a network capacity calling request initiated by the central control equipment;

the central management and control equipment is used for: according to the network capacity requirement of the cloud computing service, a network capacity calling request is sent to the network capacity open platform; according to target network capacity parameters returned by the network capacity open platform, transmitting target network capacity matched with the network capacity requirement to the cloud computing service in a transparent mode so that the cloud computing service can use the target network capacity;

the cloud computing service is deployed on a target edge node in an edge cloud system, the edge cloud system is a cloud computing platform deployed close to an end side, and the target edge node is an edge node covered by the target network capacity.

2. The system according to claim 1, wherein the network capability open platform is specifically configured to: and constructing a network capability Application Programming Interface (API) according to the network capability provided by the at least one network capability unit, and opening the network capability API to the central control equipment so that the central control equipment can initiate the network capability calling request.

3. The system according to claim 1, wherein the network capability open platform is specifically configured to: determining a target network capacity unit from the at least one network capacity unit according to the network capacity calling request; and acquiring the target network capacity parameters from the target network capacity unit and returning the target network capacity parameters to the central management and control equipment.

4. The system according to any one of claims 1-3, wherein a network capability open adaptation layer is deployed in the edge cloud system, the network capability open adaptation layer interfacing with the at least one network capability unit;

the central management and control device is specifically configured to: and issuing the target network capacity parameter to the network capacity open adaptation layer, packaging the target network capacity into a service API adapted to the cloud computing service by the network capacity open adaptation layer, and providing the service API for the cloud computing service so that the cloud computing service can use the target network capacity.

5. The system of claim 4, wherein the central management device is further configured to:

deploying the network capacity open adaptation layer locally in advance; alternatively, the first and second liquid crystal display panels may be,

deploying the network capacity open adaptation layer on each edge node in the edge cloud system in advance; alternatively, the first and second electrodes may be,

determining a target edge node where the cloud computing service can be deployed, and deploying the network capability open adaptation layer on the target edge node.

6. The system according to claim 5, characterized in that the central management and control device is specifically configured to:

determining candidate edge nodes capable of deploying the cloud computing service according to service demand information provided by a service demand party;

and according to the target network capacity parameter, selecting the edge node covered by the target network capacity from the candidate edge nodes as the target edge node.

7. The system of claim 6, wherein the central management device is further configured to:

associating the target network capacity parameter, the target edge node and a mirror image corresponding to the cloud computing service; and

and issuing the mirror image corresponding to the cloud computing service to the target edge node so that the target edge node deploys the instance corresponding to the cloud computing service.

8. The system of claim 7, wherein the central management device is further configured to:

receiving the use state and/or result information of the target network capacity reported by the instance;

and obtaining a calling result of the target network capability according to the using state and/or result information, and feeding back the calling result to the service demand party.

9. The system of claim 5, wherein the target edge node is an MEC node hosted by the central hosting facility in the mobile communication network, an edge cloud node deployed by the edge cloud system provider, or a partner node deployed by the edge cloud system provider in cooperation with a third party.

10. A system according to any of claims 1-3, wherein the network capabilities provided by the at least one network capability unit comprise at least one of: wireless capability, wired capability, billing capability, operation and maintenance capability, and slicing capability.

11. A network system, comprising: the mobile communication system comprises a central management and control device in an edge cloud system and at least one network capacity unit in a mobile communication network;

the at least one network capacity unit is used for providing network capacity and providing respective network capacity parameters for the central management and control equipment;

the central management and control equipment is used for: according to the network capacity requirement of the cloud computing service, determining a target network capacity parameter from the network capacity parameters of the at least one network capacity unit, and transmitting the target network capacity matched with the network capacity requirement to the cloud computing service so that the cloud computing service can use the target network capacity;

12. The system according to claim 11, wherein said at least one network capability unit is specifically configured to: and constructing a network capacity application programming interface API according to the network capacity provided by the central control device, and opening the network capacity API to the central control device so that the central control device can acquire the network capacity parameters of the at least one network capacity unit.

13. The system according to claim 11 or 12, wherein a network capability open adaptation layer is deployed in the edge cloud system, and the network capability open adaptation layer interfaces with the at least one network capability unit;

14. A network capacity opening method is applicable to a central management and control device in an edge cloud system, and comprises the following steps:

according to the network capacity requirement of the cloud computing service, a network capacity calling request is sent to a network capacity open platform in a mobile communication network, so that a target network capacity parameter returned by the network capacity open platform can be provided;

according to target network capacity parameters returned by the network capacity open platform, transmitting target network capacity matched with the network capacity requirement to the cloud computing service so that the cloud computing service can use the target network capacity;

15. The method of claim 14, wherein a network capability open adaptation layer is deployed in the edge cloud system, and the network capability open adaptation layer interfaces with a network capability unit in a mobile communication network;

according to the target network capacity parameter returned by the network capacity open platform, transmitting the target network capacity matched with the network capacity requirement to the cloud computing service in a transparent mode so that the cloud computing service can use the target network capacity, and the method comprises the following steps:

and issuing the target network capacity parameters to the network capacity open adaptation layer, packaging the target network capacity into a service API adapted to the cloud computing service by the network capacity open adaptation layer, and providing the service API to the cloud computing service so that the cloud computing service can use the target network capacity.

16. The method of claim 15, wherein before sending the target network capability parameter to the network capability open adaptation layer, the method further comprises:

the network capacity open adaptation layer is deployed in the center management and control equipment in advance; alternatively, the first and second electrodes may be,

17. The method of claim 16, wherein determining a target edge node at which the cloud computing service may be deployed comprises:

18. The method of claim 17, after determining a target edge node at which the cloud computing service can be deployed, further comprising:

19. The method of claim 18, further comprising:

20. The method of claim 16, wherein the target edge node is an MEC node hosted by the central hosting facility in the mobile communications network, an edge cloud node deployed by the edge cloud system provider, or a partner node deployed by the edge cloud system provider in cooperation with a third party.

21. The method of any of claims 14-20, wherein the target network capabilities comprise at least one of: wireless capability, wired capability, billing capability, operation and maintenance capability, and slicing capability.

22. A network capability opening method, which is applied to a network capability opening platform in a mobile communication network, the method comprising:

opening network capacity provided by at least one network capacity unit in a mobile communication network to a central management and control device in an edge cloud system;

receiving a network capacity calling request initiated by the central control equipment, wherein the network capacity calling request is initiated according to the network capacity requirement of the cloud computing service;

returning a target network capacity parameter to the central control equipment according to a network capacity calling request initiated by the central control equipment, wherein the target network capacity parameter points to the target network capacity matched with the network capacity requirement;

23. The method of claim 22, wherein opening network capabilities provided by at least one network capability element in the mobile communication network to a central management device in the edge cloud system comprises:

and constructing a network capability Application Programming Interface (API) according to the network capability provided by the at least one network capability unit, and opening the network capability API to the central control equipment so that the central control equipment can initiate the network capability calling request.

24. The method according to claim 23, wherein returning target network capability parameters to the central management and control device according to the network capability call request initiated by the central management and control device includes:

determining a target network capacity unit from the at least one network capacity unit according to the network capacity calling request; and acquiring the target network capacity parameters from the target network capacity unit and returning the target network capacity parameters to the central management and control equipment.

25. A central management and control device, comprising: a memory and a processor;

the memory is used for storing a computer program; the processor is coupled with the memory for executing the computer program for:

according to the network capacity requirement of the cloud computing service, a network capacity calling request is sent to a network capacity open platform in a mobile communication network, so that a target network capacity parameter returned by the network capacity open platform can be provided; according to target network capacity parameters returned by the network capacity open platform, transmitting target network capacity matched with the network capacity requirement to the cloud computing service in a transparent mode so that the cloud computing service can use the target network capacity;

26. A network capability openness device, comprising: a memory and a processor;

the memory for storing a computer program; the processor is coupled with the memory for executing a computer program for:

opening network capacity provided by at least one network capacity unit in the mobile communication network to a central management and control device in the edge cloud system; receiving a network capacity calling request initiated by the central control equipment, wherein the network capacity calling request is initiated according to the network capacity requirement of the cloud computing service; returning a target network capacity parameter to the central control equipment according to a network capacity calling request initiated by the central control equipment, wherein the target network capacity parameter points to the target network capacity matched with the network capacity requirement;

the cloud computing service is deployed on a target edge node in an edge cloud system, the edge cloud system is a cloud computing platform deployed on a near end side, and the target edge node is an edge node covered by the target network capacity.

27. A network capacity opening method is applicable to a central management and control device in an edge cloud system, and comprises the following steps:

acquiring network capability parameters provided by at least one network capability unit in a mobile communication network;

determining a target network capacity parameter from the network capacity parameters of the at least one network capacity unit according to the network capacity requirement of the cloud computing service;

transparently transmitting a target network capability matched with the network capability requirement to the cloud computing service so that the cloud computing service can use the target network capability;

28. A central management and control device, comprising: a memory and a processor;

acquiring network capability parameters provided by at least one network capability unit in a mobile communication network; determining a target network capacity parameter from the network capacity parameters of the at least one network capacity unit according to the network capacity requirement of the cloud computing service; transparently transmitting a target network capability matched with the network capability requirement to the cloud computing service so that the cloud computing service can use the target network capability;

29. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, causes the processor to carry out the steps of the method of any one of claims 14-24 and 27.