Instantiation method of multi-access edge computing system and multi-access edge computing system

Abstract

This disclosure relates to an instantiation method and a multi-access edge computing system, and pertains to the field of communication technology. The method includes: a multi-access edge application orchestrator (MEAO) receiving an instantiation request from an operating support system (OSS), wherein the instantiation request includes an application description (AppD) corresponding to an application (App); the MEAO generating a network service description (NSD) based on the instantiation request, wherein the NSD includes resource description information of the network required by the application, and the network includes a mobile network; the MEAO sending the NSD to a network function virtualization orchestrator (NFVO) and instructing the NFVO to instantiate the application and the network based on the NSD.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an instantiation method of a multi-access edge computing system and a multi-access edge computing system. Background Art

[0002] With the advancement of 5G (5th Generation Mobile Communication Technology), all industries are moving towards informatization and intelligence, and applications are becoming more and more abundant. Therefore, operators deploy networks in advance and wait for the arrival of services in order to provide a good user experience.

[0003] However, the ultra-dense 5G base stations, the large number of base stations and the number of edges have far exceeded the imagination of operators. The industry estimates that 5G energy consumption will be several times that of 4G, and operators' electricity bills will soar. When it comes to 6G's requirement of intelligent connection of all things, the energy consumption will be astronomical. Summary of the invention

[0004] The inventors found that current networks are deployed in advance and are open 24 hours a day, but in fact the network usage efficiency is not equal, especially for small and medium-sized enterprise customers. They know their active periods and peak periods to a certain extent, and they are good at calculations and have strict control over corporate costs. In addition, there are tourist attractions with large traffic during holidays and diverse businesses, and a large number of facilities are not needed during non-holidays, which will result in low utilization of network resources and waste of network resources.

[0005] A technical problem to be solved by the present disclosure is: how to improve the utilization rate of network resources.

[0006] According to some embodiments of the present disclosure, a method for instantiating a multi-access edge computing system is provided, including: a multi-access edge application orchestrator MEAO receives an instantiation request sent by an operation support system OSS, wherein the instantiation request includes: an application description AppD corresponding to an application App; MEAO generates a network service description NSD according to the instantiation request, wherein the NSD includes: resource description information of a network required by the App, the network including: a mobile network; MEAO sends the NSD to a network function virtualization orchestrator NFVO, and instructs NFVO to instantiate the App and the network according to the NSD.

[0007] In some embodiments, MEAO sends NSD to the network function virtualization orchestrator NFVO, and instructs NFVO to instantiate App and network according to NSD, including: MEAO sends a create network service NS request to NFVO, wherein the create NS request includes: NSD; MEAO receives a create NS response returned by NFVO, wherein the create NS response includes: information that NS creation is completed; MEAO sends an instantiation NS request to NFVO, wherein the instantiation NS request is used to instruct NFVO to create a virtualized network function module VNF corresponding to the App and a VNF corresponding to the network, and instantiate the VNF corresponding to the App and the VNF corresponding to the network.

[0008] In some embodiments, the method further includes: NFVO instantiating the App and the network according to the NSD.

[0009] In some embodiments, NFVO instantiates App and network according to NSD, including: NFVO creates corresponding NS according to NSD and instantiates NS; NFVO instructs the network function module manager VNFM corresponding to the App to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App according to the instantiated NS, and instructs the VNFM corresponding to the network to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

[0010] In some embodiments, instructing the VNFM corresponding to the network to create the VNF corresponding to the network and instantiating the VNF corresponding to the network includes: the NFVO sends a first VNF ​​creation request to the VNFM corresponding to the network, wherein the first VNF ​​creation request is used to instruct the VNFM corresponding to the network to create the VNF corresponding to the network; the NFVO receives a first VNF ​​creation response sent by the VNFM corresponding to the network, wherein the first VNF ​​creation response includes: information that the creation of the VNF corresponding to the network is completed; the NFVO sends a first instantiated VNF request to the VNFM corresponding to the network, wherein the first instantiated VNF request is used to instruct the VNFM corresponding to the network to instantiate the VNF corresponding to the network; the NFVO receives a first instantiated VNF response returned by the VNFM corresponding to the network, wherein the first instantiated VNF response includes: information that the instantiation of the VNF corresponding to the network is completed.

[0011] In some embodiments, instructing the VNFM corresponding to the App to create the VNF corresponding to the App and instantiating the VNF corresponding to the App includes: the NFVO sends a second VNF creation request to the VNFM corresponding to the App, wherein the second VNF creation request is used to instruct the VNFM corresponding to the App to create the VNF corresponding to the App; the NFVO receives a second VNF creation response sent by the VNFM corresponding to the App, wherein the second VNF creation response includes: information that the creation of the VNF corresponding to the App is completed; the NFVO sends a second instantiation VNF request to the VNFM corresponding to the App, wherein the second instantiation VNF request is used to instruct the VNFM corresponding to the App to instantiate the VNF corresponding to the App; the NFVO receives a second instantiation VNF response returned by the VNFM corresponding to the App, wherein the second instantiation VNF response includes: information that the instantiation of the VNF corresponding to the App is completed.

[0012] In some embodiments, the method also includes: the VNFM corresponding to the App creates a virtualized network function module VNF corresponding to the App, and instantiates the VNF corresponding to the App; the VNFM corresponding to the network creates a VNF corresponding to the network, and instantiates the VNF corresponding to the network.

[0013] In some embodiments, the method further includes: when the MEC platform manager - network function virtualization MEPM-V subscribes to the lifecycle notification to the VNFM corresponding to the App, the VNFM corresponding to the App notifies the MEPM-V of the information that the VNF corresponding to the App is instantiated. Alternatively, when the MEPM-V subscribes to the lifecycle notification to the VNFM corresponding to the network, the VNFM corresponding to the network notifies the MEPM-V of the information that the VNF corresponding to the network is instantiated.

[0014] In some embodiments, MEPM-V includes: a MEC network element manager and a MEC application rule and request manager. The VNFM corresponding to the App notifies the MEC application rule and request manager of the information that the VNF corresponding to the App is instantiated. The VNFM corresponding to the network notifies the MEC network element manager of the information that the VNF corresponding to the network is instantiated.

[0015] In some embodiments, the method also includes: when the VNF corresponding to the App and the VNF corresponding to the network are instantiated, MEAO requests the MEC platform manager - network function virtualization MEPM-V to configure the instance of the App and the instance of the network.

[0016] In some embodiments, MEAO requests MEPM-V to configure a network instance, including: MEAO sends a network instance configuration request to MEPM-V, wherein the network instance configuration request includes: configuration parameters of the network instance; MEPM-V sends a network instance configuration request to the VNF corresponding to the network, wherein the network instance configuration request is used to instruct the VNF corresponding to the network to configure relevant resources of the network; MEPM-V receives a network instance configuration response returned by the VNF corresponding to the network, wherein the network instance configuration response includes: information on completion of configuring the network instance; MEAO receives the network instance configuration response returned by MEPM-V.

[0017] In some embodiments, the method also includes: the VNF corresponding to the network configures relevant resources of the network to implement at least one of the wireless access network RAN ​​distributed unit DU, the RAN central unit CU, the core network CN user plane UP and the CN control plane CP; wherein, RAN DU and RAN CU are configured to provide the functions of access network network elements in the mobile network, and CN UP and CN CP are configured to provide the functions of core network network elements in the mobile network.

[0018] In some embodiments, MEAO requests MEPM-V to configure an instance of App, including: MEAO sends a request to configure the application instance to MEPM-V, wherein the request to configure the application instance includes: configuration parameters of the instance of App; MEPM-V sends a request to configure the application instance to the virtualized network function module VNF of the MEC platform, wherein the request to configure the application instance is used to indicate relevant rules for the VNF of the MEC platform to configure the App; MEPM-V receives a response to configure the application instance returned by the VNF of the MEC platform, wherein the response to configure the application instance includes: information on completion of configuring the instance of App; MEAO receives the response to configure the application instance returned by MEPM-V.

[0019] In some embodiments, NSD includes at least one of: the number of wireless access networks RAN, the processing capacity of RAN, the number of core networks CN, the processing capacity of CN, the direction of N3 interface, the direction of N6 interface, the connection information between RAN and non-edge network, and the connection information between CN and non-edge network.

[0020] According to some other embodiments of the present disclosure, an access edge application orchestrator is provided, including: a receiving unit, used to receive an instantiation request sent by an operation support system OSS, wherein the instantiation request includes: an application description AppD corresponding to the application App; a generating unit, used to generate a network service description NSD according to the instantiation request, wherein the NSD includes: resource description information of a network required by the App, the network including: a mobile network; a sending unit, used to send the NSD to a network function virtualization orchestrator NFVO, and instruct the NFVO to instantiate the App and the network according to the NSD.

[0021] According to some further embodiments of the present disclosure, a multi-access edge computing system is provided, comprising: a multi-access edge application orchestrator of any of the aforementioned embodiments; and NFVO, for instantiating App and network according to NSD.

[0022] In some embodiments, NFVO is used to create a corresponding NS according to NSD and instantiate the NS, instruct the network function module manager VNFM corresponding to the App to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App according to the instantiated NS, and instruct the VNFM corresponding to the network to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

[0023] In some embodiments, the system includes: a VNFM corresponding to the App, used to create a virtualized network function module VNF corresponding to the App, and instantiate the VNF corresponding to the App; a VNFM corresponding to the network, used to create a VNF corresponding to the network, and instantiate the VNF corresponding to the network.

[0024] In some embodiments, the system includes: a MEC platform manager - network function virtualization MEPM-V, which is used to receive information on the completion of instantiation of the VNF corresponding to the App sent by the VNFM corresponding to the App when MEPM-V subscribes to lifecycle notifications to the VNFM corresponding to the App, or, when MEPM-V subscribes to lifecycle notifications to the VNFM corresponding to the network, receive information on the completion of instantiation of the VNF corresponding to the network sent by the VNFM corresponding to the network.

[0025] In some embodiments, MEPM-V includes: a MEC network element manager and a MEC application rule and request manager, the MEC application rule and request manager is used to receive information on the completion of instantiation of the VNF corresponding to the App sent by the VNFM corresponding to the App, and the MEC network element manager is used to receive information on the completion of instantiation of the VNF corresponding to the network sent by the VNFM corresponding to the network.

[0026] In some embodiments, the system includes: a VNF corresponding to the network; wherein MEPM-V is used to receive a configuration network instance request sent by MEAO, and send a configuration network instance request to the VNF corresponding to the network, wherein the configuration network instance request is used to instruct the VNF corresponding to the network to configure relevant resources of the network, and receive a configuration network instance response returned by the VNF corresponding to the network, wherein the configuration network instance response includes: information on completion of configuring the network instance; returning the configuration network instance response to MEAO; the VNF corresponding to the network is used to receive the configuration network instance request, configure relevant resources of the network, and return the configuration network instance response to MEPM-V.

[0027] According to some further embodiments of the present disclosure, an electronic device is provided, including: a processor; and a memory coupled to the processor, for storing instructions, which, when executed by the processor, causes the processor to execute an instantiation method as described in any of the aforementioned embodiments.

[0028] After receiving the instantiation request sent by OSS (Operations Support System), MEAO (MEC Application Orchestrator) in the MEC (Multi-access Edge Computing) system of the present disclosure generates NSD (Network Service Descriptor) according to the instantiation request. NSD includes: resource description information of the network required by App, and then MEAO sends NSD to NFVO (Network Functions Virtualization NFV Orchestrator) and instructs NFVO to instantiate App and network according to NSD. The method of the present disclosure can instantiate the network according to the resources of the network required by App, quickly open the network required by the application, and does not need to be deployed in advance, thereby improving the utilization rate of network resources and reducing the waste of network resources.

[0029] In addition, the network is enabled in the MEO system, and the "application" and "network" are integrated into the design, breaking the existing idea that the MEC system only serves the application APP, and instantiating the network, especially the wireless mobile network, on the MEC system. The problem of "processing delay" and "transmission delay" is fundamentally solved, the delay is shortened, the bandwidth is increased, and the high-bandwidth and low-latency services are better served.

[0030] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0032] Figure 1 A flowchart illustrating an instantiation method of a multi-access edge computing system according to some embodiments of the present disclosure is provided.

[0033] Figure 2 An architectural diagram of a multi-access edge computing system according to some embodiments of the present disclosure is shown.

[0034] Figure 3 An architectural diagram of a multi-access edge computing system according to other embodiments of the present disclosure is shown.

[0035] Figure 4 A flowchart illustrating an instantiation method of a multi-access edge computing system according to some other embodiments of the present disclosure is provided.

[0036] Figure 5 A schematic diagram showing the structure of a multi-access edge application orchestrator according to some embodiments of the present disclosure is shown.

[0037] Figure 6 A schematic diagram showing the structure of a multi-access edge computing system according to some embodiments of the present disclosure.

[0038] Figure 7 A schematic diagram showing the structure of an electronic device according to some embodiments of the present disclosure.

[0039] Figure 8 A schematic diagram showing the structure of an electronic device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0041] This disclosure proposes an instantiation method in a MEC system. Figures 1 to 4 Give a description.

[0042] Figure 1The following is a flowchart of some embodiments of the instantiation method of the multi-access edge computing system disclosed in the present invention. Figure 1 As shown, the method of this embodiment includes: steps S102 to S106.

[0043] In step S102, MEAO receives an instantiation request sent by OSS.

[0044] OSS receives business requirements from suppliers and can convert them into AppD (App Descriptor) and send them to MEAO. The instantiation request includes: AppD corresponding to the application App. AppD contains the minimum computing resources, virtual storage resources, network resources, service list required for App operation, DNS (Domain Name System) rules, FQDN (Fully Qualified Domain Name) information, and the maximum latency and bandwidth that the App can tolerate. AppD is the basis for App instantiation. For specific content, please refer to the existing ETSI (European Telecommunications Standards Institute) standards, which will not be repeated here.

[0045] In step S104, MEAO generates NSD according to the instantiation request.

[0046] NSD includes, for example, resource description information of the network required by the App, and the network includes: a mobile network. For example, in a 5G network scenario, NSD includes, for example, resource description information of the 5G network required by the App. The network may also be other wireless networks, not limited to the examples given.

[0047] For example, NSD includes: the number of RAN (Radio Access Network), the processing capacity of RAN, the number of CN (Core Network), the processing capacity of CN, the direction of N3 interface, the direction of N6 interface, the connection information between RAN and non-edge network, and at least one of the connection information between CN and non-edge network. The resource description information of the network required by the App can be determined according to actual business needs and is not limited to the examples given. The resource description information of the network required by the App can be added on the basis of the existing NSD. Other contents can refer to the existing standards and will not be repeated here.

[0048] In step S106 , MEAO sends the NSD to NFVO and instructs NFVO to instantiate the App and network according to the NSD.

[0049] In some embodiments, MEAO sends a create NS (Network Service) request to NFVO, wherein the create NS request includes: NSD; MEAO receives a create NS response returned by NFVO, wherein the create NS response includes: information that NS creation is completed; MEAO sends an instantiate NS request to NFVO, for instructing NFVO to create a VNF (Virtualised Network Function) corresponding to the App and a VNF corresponding to the network, and instantiate the VNF corresponding to the App and the VNF corresponding to the network.

[0050] In some embodiments, after step S106, the following may be included: in step S108, the NFVO instantiates the App and the network according to the NSD.

[0051] In some embodiments, NFVO instructs the VNFM (Virtualised Network Function Manager) corresponding to the App to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App based on the instantiated NS, and instructs the VNFM corresponding to the network to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

[0052] In the above embodiment, after receiving the instantiation request sent by OSS, MEAO in the MEC system generates NSD according to the instantiation request, and NSD includes: resource description information of the network required by App, and then MEAO sends NSD to NFVO and instructs NFVO to instantiate App and network according to NSD. The method of the above embodiment can instantiate the network according to the resources of the network required by App, quickly open the network required by the application, and do not need to deploy in advance, thereby improving the utilization rate of network resources and reducing the waste of network resources.

[0053] In addition, the network is enabled in the MEO system, and the "application" and "network" are integrated into the design, breaking the existing idea that the MEC system only serves the application APP, and instantiating the network, especially the wireless mobile network, on the MEC system. The problem of "processing delay" and "transmission delay" is fundamentally solved, the delay is shortened, the bandwidth is increased, and the high-bandwidth and low-latency services are better served.

[0054] The method disclosed in this disclosure is based on a new MEC system architecture. Figure 2As shown in the figure, the solution of the present disclosure adds a MEC network and a MEC network lifecycle manager (shown in a shadowed manner) to the existing MEC system software architecture, so as to deploy the mobile network in the MEC system closer to the user. The MEC network is located in the MEC host and is deployed in a distributed manner. The MEC network is configured as a network instance running on VI (Virtualisation infrastructure) to provide mobile network functions. The MEC network interacts with the MEC platform through the Mm reference point.

[0055] The MEC platform manager includes: MEC network life cycle manager (MEC network life cycle mgmt). The MEC network life cycle manager is configured to manage the life cycle of the MEC network. The MEC network interacts with the MEC network life cycle manager through the Mm reference point.

[0056] Some existing functions of the MEC host, MEC platform, MEC App, VI, MEC platform manager, MEO and VIM, as well as the functions of some existing modules can refer to the existing standards and will not be repeated here. Figure 2 The three reference points Mm, Mp and Mx are numbered respectively. The reference points between the MEC network and the MEC platform and the MEC platform manager are shown as Mmx and Mmy, which can be renumbered according to actual needs.

[0057] like Figure 2 As shown, the MEC network may include: at least one of: RAN (Radio Access Network) DU (Distributed Unit) 111, RAN CU (Centralized Unit), CN (Core Network) UP (User Plane) and CN CP (Control Plane); wherein, RAN DU and RAN CU are configured to provide the functions of access network elements in a mobile network, and CN UP and CN CP are configured to provide the functions of core network elements in a mobile network.

[0058] RAN DU: It is a distributed unit of RAN, which mainly handles physical layer functions and layer 2 functions with real-time requirements, and is close to users; RAN CU: It is a centralized deployment unit of RAN, which mainly includes non-real-time wireless high-level protocol stack functions; CN UP: It is the user plane of the core network, which is the entrance and exit of applications from the mobile network and the external network; CN CP: It is the control plane of the core network, which can be centrally deployed. The above four functional units can be selectively deployed according to business needs. For example, RAN CU and CN CP can be deployed without deployment, and only RAN DU and CN UP can be deployed.

[0059] The MEC network lifecycle manager is responsible for the lifecycle management of the MEC Network. For specific functions, please refer to the requirements of 3GPP SA5 for the lifecycle management of mobile networks, without changing the existing mobile network mechanism. The MEC network lifecycle manager 151 is located at the MEC system level and can be centrally deployed / centrally managed according to user / enterprise requirements, or distributedly deployed on demand.

[0060] like Figure 3 The figure shows the architecture diagram of the MEC system in the NFV (Network Functions Virtualization) scenario.

[0061] In the NFV scenario, the MEC network is deployed as MEC network VNF, the MEC platform is deployed as MEC platform VNF, the MEC application is deployed as MEC application VNF, and the VI is deployed as NFVI (NFV Infrastructure, Network Function Virtualization Infrastructure).

[0062] In the NFV scenario, the MEC platform manager is deployed as the MEC platform manager - NFV (MEPM-V). MEPM-V includes: MEC network element manager (MEC network element mgmt), and entrusts the lifecycle management of the MEC network to the VNFM (Virtualised Network Function Manager) corresponding to the MEC network. The VNFM corresponding to the MEC network can include MEC Network RAN VNFM, MEC Network CN VNFM manages the lifecycles of RAN and CN respectively.

[0063] MEO is deployed as MEAO (MEC Application Orchestrator), which interacts with NFVO (NFV Orchestrator) to perform resource orchestration, and orchestrates MEC application VNF and MEC network VNF into one or more NFV NS. MEC network VNF, MEC network element manager, and VNFM corresponding to MEC network (shown in shaded form) are added to the existing MEC system architecture in the NFV scenario. The functions of other modules can refer to existing standards and will not be repeated here.

[0064] Combine the following Figure 4 Other embodiments of the instantiation method of the present disclosure are described.

[0065] Figure 4 Flowcharts of other embodiments of the instantiation method of the multi-access edge computing system disclosed in the present invention. Figure 4 As shown, the method of this embodiment includes: steps S402 to S431.

[0066] In step S402, OSS sends an instantiation request to MEAO.

[0067] For example, the instantiation request is an instantiate application request.

[0068] In step S404, MEAO generates NSD according to the instantiation request, wherein NSD includes: resource description information of the network required by the App, and the network includes: a mobile network.

[0069] In step S406, MEAO sends a create NS request to NFVO, wherein the create NS request includes: NSD.

[0070] In step S408, NFVO creates a corresponding NS according to NSD, and sends a create NS response (create NSresponse) to MEAO, wherein the create NS response includes: information on completion of NS creation.

[0071] In step S410 , the MEAO sends an instantiate NS request to the NFVO.

[0072] The instantiation NS request is used to instruct NFVO to create the virtualized network function module VNF corresponding to the App and the VNF corresponding to the network, and to instantiate the VNF corresponding to the App and the VNF corresponding to the network.

[0073] In step S412, the NFVO creates a request (create VNF request) to the first VNF ​​of the VNFM corresponding to the network.

[0074] The first VNF ​​creation request is used to instruct the VNFM corresponding to the network to create the VNF corresponding to the network.

[0075] In step S414, the VNFM corresponding to the network creates the VNF corresponding to the network, and sends a first VNF ​​creation response (create VNF response) to the NFVO, wherein the first VNF ​​creation response includes: information on the completion of creation of the VNF corresponding to the network.

[0076] In step S416, the NFVO sends a first instantiate VNF request to the VNFM corresponding to the network, wherein the first instantiate VNF request is used to instruct the VNFM corresponding to the network to instantiate the VNF corresponding to the network.

[0077] In step S418, the VNFM corresponding to the network instantiates the VNF corresponding to the network, and sends a first instantiated VNF response (instantiate VNF response) to the NFVO, wherein the first instantiated VNF response includes: information on completion of instantiation of the VNF corresponding to the network.

[0078] Parallel to steps S412 to S418 also include:

[0079] In step S413, the NFVO sends a second VNF creation request to the VNFM corresponding to the App, wherein the second VNF creation request is used to instruct the VNFM corresponding to the App to create the VNF corresponding to the App.

[0080] In step S415, the VNFM corresponding to the App creates the VNF corresponding to the App, and sends a second VNF creation response to the NFVO, wherein the second VNF creation response includes: information on the completion of the creation of the VNF corresponding to the App.

[0081] In step S417, the NFVO sends a second VNF instantiation request to the VNFM corresponding to the App, wherein the second VNF instantiation request is used to instruct the VNFM corresponding to the App to instantiate the VNF corresponding to the App.

[0082] In step S419, the VNFM corresponding to the App instantiates the VNF corresponding to the App, and sends a second instantiated VNF response to the NFVO, wherein the second instantiated VNF response includes: information on completion of instantiation of the VNF corresponding to the App.

[0083] The above steps S413 to S419 may refer to existing standards.

[0084] In step S420, when MEPM-V (MEC Platform Manager - Network Function Virtualization) subscribes to the lifecycle notification of the VNFM corresponding to the network, the VNFM corresponding to the network notifies MEPM-V of the information (LCMnotification (completed)) of the completion of the instantiation of the VNF corresponding to the network. This step is optional.

[0085] In step S421, when MEPM-V has subscribed to lifecycle notifications from the VNFM corresponding to the App, the VNFM corresponding to the App notifies MEPM-V of the completion of instantiation of the VNF corresponding to the App.

[0086] In some embodiments, MEPM-V includes: a MEC network element manager (MEC network element mgmt) and a MEC application rules and request manager (MEC app rules & reqs mgmt). The VNFM corresponding to the App notifies the MEC application rules and request manager of the information that the VNF corresponding to the App is instantiated. The VNFM corresponding to the network notifies the MEC network element manager of the information that the VNF corresponding to the network is instantiated.

[0087] In step S422, the NFVO sends an instantiation NS response to the MEAO, wherein the instantiation NS response includes: information indicating that the instantiation of the NS is completed.

[0088] In some embodiments, when the VNF corresponding to the App and the VNF corresponding to the network are instantiated, MEAO requests the MEC platform manager - network function virtualization MEPM-V to configure the instance of the App and the instance of the network. The specific steps are as follows.

[0089] In step S424, MEAO sends a configure network instance request to MEPM-V, wherein the configure network instance request includes: configuration parameters of the instance of the configuration network.

[0090] Configuration parameters for configuring an instance of a network may be obtained by the NSD.

[0091] In step S426, MEPM-V sends a network instance configuration request to the VNF corresponding to the network, wherein the network instance configuration request is used to instruct the VNF corresponding to the network to configure relevant resources of the network.

[0092] In step S428, the VNF corresponding to the network configures the relevant resources of the network and returns a configure network instance response (configure network instance response) to MEPM-V, wherein the configure network instance response includes: information on the completion of configuring the network instance.

[0093] In some embodiments, the VNF corresponding to the network configures the relevant resources of the network to implement at least one of RAN CU, RAN DU, CNCP and CN UP; wherein RAN DU and RAN CU are configured to provide the functions of access network elements in the mobile network, and CN UP and CN CP are configured to provide the functions of core network elements in the mobile network. That is, the software of MEC Network is loaded, and the MEC Network VNF is changed into RAN CU, RAN DU, CN CP, and CN UP.

[0094] In step S430, MEPM-V returns a configuration network instance response to MEAO.

[0095] Parallel to steps S424 to S430 also include:

[0096] In step S425, MEAO sends a configure app instance request to MEPM-V, wherein the configure app instance request includes: configuration parameters of the instance of the configuration App.

[0097] In step S427, MEPM-V sends an application instance configuration request to the VNF of the MEC platform, wherein the application instance configuration request is used to instruct the VNF of the MEC platform to configure the relevant rules of the App.

[0098] In step S429, the VNF of the MEC platform configures the relevant rules of the App and returns a configure app instance response to MEPM-V, where the configure app instance response includes: information on the completion of configuring the App instance.

[0099] App-related rules, such as traffic rules, DNS rules, etc.

[0100] In step S431, MEPM-V returns a configuration application instance response to MEAO.

[0101] Steps S425 to S431 may refer to existing standards.

[0102] The method of the above embodiment, under the new MEC system architecture, builds the required resources and opens the network according to business needs, so as to meet the temporary or intermittent use of the business. OSS can collect business needs and issue instructions, and NFVO can uniformly pull up the entire application + network integrated edge network to solve business scenarios with extreme bandwidth + latency requirements and provide a better business experience. Application + network integration can achieve rapid intercommunication between different network elements, and at the same time can also be linked in control, quickly respond to business needs, instantiate applications and networks, and meet the ultimate business experience.

[0103] The present disclosure also provides a MEAO, Figure 5 Give a description.

[0104] Figure 5 FIG. 1 is a structural diagram of some embodiments of the multi-access edge application orchestrator disclosed in the present invention. Figure 5 As shown, the MEAO 50 of this embodiment includes: a receiving unit 510 , a generating unit 520 , and a sending unit 530 .

[0105] The receiving unit 510 is used to receive an instantiation request sent by the operation support system OSS, wherein the instantiation request includes: an application description AppD corresponding to the application App.

[0106] The generating unit 520 is used to generate a network service description NSD according to the instantiation request, wherein the NSD includes: resource description information of the network required by the App, and the network includes: a mobile network.

[0107] The sending unit 530 is used to send the NSD to the network function virtualization orchestrator NFVO, and instruct the NFVO to instantiate the App and the network according to the NSD.

[0108] Each unit of MEAO 50 can execute the method executed by MEAO in the aforementioned embodiment, which will not be described in detail here.

[0109] The present disclosure also provides a multi-access edge computing system. Figure 6 Give a description.

[0110] Figure 6 The structure diagram of some embodiments of the edge computing system of the present disclosure is shown in FIG. Figure 6 As shown, the system 6 of this embodiment includes: the MEAO 50 of the aforementioned embodiment; and the NFVO 61, which is used to instantiate the App and the network according to the NSD.

[0111] In some embodiments, NFVO 61 is used to create a corresponding NS according to NSD and instantiate the NS, instruct the network function module manager VNFM corresponding to the App to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App according to the instantiated NS, and instruct the VNFM corresponding to the network to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

[0112] In some embodiments, the system 6 also includes: a VNFM 62 corresponding to the App, which is used to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App; a VNFM 63 corresponding to the network, which is used to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

[0113] In some embodiments, the system 6 further includes: MEPM-V 64, which is used to receive information on the completion of instantiation of the VNF corresponding to the App sent by the VNFM 62 corresponding to the App when the MEPM-V 64 subscribes to the lifecycle notification to the VNFM 62 corresponding to the App, or, when the MEPM-V 64 subscribes to the lifecycle notification to the VNFM 62 corresponding to the network, receive information on the completion of instantiation of the VNF corresponding to the network sent by the VNFM 63 corresponding to the network.

[0114] In some embodiments, MEPM-V 64 includes: a MEC network element manager and a MEC application rule and request manager, the MEC application rule and request manager is used to receive the information on the completion of the instantiation of the VNF corresponding to the App sent by the VNFM 62 corresponding to the App, and the MEC network element manager is used to receive the information on the completion of the instantiation of the VNF corresponding to the network sent by the VNFM 63 corresponding to the network.

[0115] In some embodiments, system 6 also includes: VNF 65 corresponding to the network; MEPM-V 64 is used to receive a configuration network instance request sent by MEAO 50, and send a configuration network instance request to the VNF 65 corresponding to the network, wherein the configuration network instance request is used to instruct the VNF 65 corresponding to the network to configure relevant resources of the network, and receive a configuration network instance response returned by the VNF 65 corresponding to the network, wherein the configuration network instance response includes: information on completion of configuring the network instance; returning the configuration network instance response to MEAO 50; the VNF 65 corresponding to the network is used to receive the configuration network instance request, configure relevant resources of the network, and return the configuration network instance response to MEPM-V 64.

[0116] The electronic devices (such as various parts of the MEC system) in the embodiments of the present disclosure can be implemented by various computing devices or computer systems. Figure 7 as well as Figure 8 Give a description.

[0117] Figure 7 FIG. 1 is a structural diagram of some embodiments of the electronic device disclosed in the present invention. Figure 7 As shown, the electronic device 70 of this embodiment includes: a memory 710 and a processor 720 coupled to the memory 710 , and the processor 720 is configured to execute the instantiation method in any of some embodiments of the present disclosure based on instructions stored in the memory 710 .

[0118] The memory 710 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, an application program, a boot loader, a database, and other programs.

[0119] Figure 8 FIG. 1 is a structural diagram of some other embodiments of the electronic device disclosed in the present invention. Figure 8 As shown, the electronic device 80 of this embodiment includes: a memory 810 and a processor 820, which are similar to the memory 710 and the processor 720 respectively. It can also include an input and output interface 830, a network interface 840, a storage interface 850, etc. These interfaces 830, 840, 850 and the memory 810 and the processor 820 can be connected, for example, via a bus 860. Among them, the input and output interface 830 provides a connection interface for input and output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 840 provides a connection interface for various networked devices, for example, it can be connected to a database server or a cloud storage server. The storage interface 850 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0120] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0121] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0122] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0123] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0124] The above are only preferred embodiments of the present disclosure and are not intended to limit the present disclosure. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present disclosure should be included in the protection scope of the present disclosure.

Claims

1. A method for instantiating a multi-access edge computing system, comprising: The multi-access edge application orchestrator MEAO receives an instantiation request sent by the operation support system OSS, wherein the instantiation request includes: an application description AppD corresponding to the application App, wherein the AppD includes network resources required by the App, a maximum tolerable delay, and a bandwidth; The MEAO generates a network service description NSD according to the instantiation request, wherein the NSD includes: resource description information of the network required by the App, and the network includes: a mobile network; The MEAO sends a create network service NS request to the network function virtualization orchestrator NFVO, wherein the create NS request includes: the NSD; The MEAO receives a create NS response returned by the NFVO, wherein the create NS response includes: information indicating that NS creation is completed; The MEAO sends an instantiation NS request to the NFVO, wherein the instantiation NS request is used to instruct the NFVO to create a virtualized network function module VNF corresponding to the App and a VNF corresponding to the network, and instantiate the VNF corresponding to the App and the VNF corresponding to the network.

2. The instantiation method according to claim 1, further comprising: The NFVO instantiates the App and the network according to the NSD.

3. The instantiation method according to claim 2, wherein: The NFVO instantiating the App and the network according to the NSD includes: The NFVO creates a corresponding NS according to the NSD and instantiates the NS; The NFVO instructs the network function module manager VNFM corresponding to the App to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App based on the instantiated NS, and instructs the VNFM corresponding to the network to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

4. The instantiation method according to claim 3, wherein: The instructing the VNFM corresponding to the network to create the VNF corresponding to the network and instantiating the VNF corresponding to the network includes: The NFVO sends a first VNF ​​creation request to the VNFM corresponding to the network, wherein the first VNF ​​creation request is used to instruct the VNFM corresponding to the network to create the VNF corresponding to the network; The NFVO receives a first VNF ​​creation response sent by the VNFM corresponding to the network, wherein the first VNF ​​creation response includes: information that the VNF corresponding to the network is created; The NFVO sends a first VNF ​​instantiation request to the VNFM corresponding to the network, wherein the first VNF ​​instantiation request is used to instruct the VNFM corresponding to the network to instantiate the VNF corresponding to the network; The NFVO receives a first instantiated VNF response returned by the VNFM corresponding to the network, wherein the first instantiated VNF response includes: information on completion of instantiation of the VNF corresponding to the network.

5. The instantiation method according to claim 3, wherein: The instructing the VNFM corresponding to the App to create the VNF corresponding to the App and instantiating the VNF corresponding to the App includes: The NFVO sends a second VNF creation request to the VNFM corresponding to the App, wherein the second VNF creation request is used to instruct the VNFM corresponding to the App to create the VNF corresponding to the App; The NFVO receives a second VNF creation response sent by the VNFM corresponding to the App, wherein the second VNF creation response includes: information that the VNF corresponding to the App is created; The NFVO sends a second VNF instantiation request to the VNFM corresponding to the App, wherein the second VNF instantiation request is used to instruct the VNFM corresponding to the App to instantiate the VNF corresponding to the App; The NFVO receives a second instantiated VNF response returned by the VNFM corresponding to the App, wherein the second instantiated VNF response includes: information on completion of instantiation of the VNF corresponding to the App.

6. The instantiation method according to claim 3, further comprising: The VNFM corresponding to the App creates a virtualized network function module VNF corresponding to the App, and instantiates the VNF corresponding to the App; The VNFM corresponding to the network creates the VNF corresponding to the network and instantiates the VNF corresponding to the network.

7. The instantiation method according to claim 6, further comprising: In the case where the MEC platform manager - network function virtualization MEPM-V subscribes to the lifecycle notification of the VNFM corresponding to the App, the VNFM corresponding to the App notifies the MEPM-V of the information that the VNF corresponding to the App is instantiated. Alternatively, In the case that the MEPM-V subscribes to the lifecycle notification from the VNFM corresponding to the network, the VNFM corresponding to the network notifies the MEPM-V of the information that the VNF corresponding to the network is instantiated.

8. The instantiation method according to claim 7, wherein: The MEPM-V includes: a MEC network element manager and a MEC application rule and request manager. The VNFM corresponding to the App notifies the MEC application rule and request manager of the information that the VNF corresponding to the App is instantiated. The VNFM corresponding to the network notifies the MEC network element manager of the information that the VNF corresponding to the network is instantiated.

9. The instantiation method according to claim 1, further comprising: When the VNF corresponding to the App and the VNF corresponding to the network are instantiated, the MEAO requests the MEC platform manager - network function virtualization MEPM-V to configure the instance of the App and the instance of the network.

10. The instantiation method according to claim 9, wherein: An example of the MEAO requesting the MEPM-V to configure the network includes: The MEAO sends a request to configure a network instance to the MEPM-V, wherein the request to configure a network instance includes: configuration parameters for configuring the instance of the network; The MEPM-V sends a network instance configuration request to the VNF corresponding to the network, wherein the network instance configuration request is used to instruct the VNF corresponding to the network to configure relevant resources of the network; The MEPM-V receives a configuration network instance response returned by the VNF corresponding to the network, wherein the configuration network instance response includes: information on completion of configuring the instance of the network; The MEAO receives the configuration network instance response returned by the MEPM-V.

11. The instantiation method according to claim 10, further comprising: The VNF corresponding to the network configures the relevant resources of the network to implement at least one of the radio access network RAN ​​distributed unit DU, RAN central unit CU, core network CN user plane UP and CN control plane CP; The RAN DU and the RAN CU are configured to provide the function of an access network element in a mobile network, and the CNUP and the CN CP are configured to provide the function of a core network element in a mobile network.

12. The instantiation method according to claim 9, wherein: The example of the MEAO requesting the MEPM-V to configure the App includes: The MEAO sends a request for configuring an application instance to the MEPM-V, wherein the request for configuring an application instance includes: configuration parameters for configuring the instance of the App; The MEPM-V sends a configuration application instance request to the virtualized network function module VNF of the MEC platform, wherein the configuration application instance request is used to instruct the VNF of the MEC platform to configure relevant rules of the App; The MEPM-V receives a configuration application instance response returned by the VNF of the MEC platform, wherein the configuration application instance response includes: information on completion of configuring the instance of the App; The MEAO receives the configuration application instance response returned by the MEPM-V.

13. The instantiation method according to any one of claims 1 to 12, wherein: The NSD includes: the number of wireless access networks RAN, the processing capacity of RAN, the number of core networks CN, the processing capacity of CN, the direction of N3 interface, the direction of N6 interface, the connection information between RAN and non-edge network, and at least one of the connection information between CN and non-edge network.

14. A multi-access edge application orchestrator MEAO, comprising: A receiving unit, configured to receive an instantiation request sent by an operation support system OSS, wherein the instantiation request includes: an application description AppD corresponding to the application App, wherein the AppD includes network resources required by the App, a maximum tolerable delay, and a bandwidth; A generating unit, configured to generate a network service description NSD according to the instantiation request, wherein the NSD includes: resource description information of a network required by the App, the network including: a mobile network; A sending unit, configured to send a create network service NS request to a network function virtualization orchestrator NFVO, wherein the create NS request includes: the NSD sends an instantiation NS request to the NFVO, wherein the instantiation NS request is used to instruct the NFVO to create a virtualized network function module VNF corresponding to the App and a VNF corresponding to the network, and instantiate the VNF corresponding to the App and the VNF corresponding to the network The receiving unit is further configured to receive a create NS response returned by the NFVO, wherein the create NS response includes: information indicating that NS creation is completed.

15. A multi-access edge computing system, comprising: The multi-access edge application orchestrator MEAO as claimed in claim 14; as well as The NFVO is configured to instantiate the App and the network according to the NSD.

16. The multi-access edge computing system according to claim 15, wherein: The NFVO is used to create a corresponding NS according to the NSD and instantiate the NS, instruct the network function module manager VNFM corresponding to the App to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App according to the instantiated NS, and instruct the VNFM corresponding to the network to create a VNF corresponding to the network and instantiate the VNF corresponding to the network.

17. The multi-access edge computing system according to claim 16, further comprising: The VNFM corresponding to the App is used to create a virtualized network function module VNF corresponding to the App and instantiate the VNF corresponding to the App; The VNFM corresponding to the network is used to create the VNF corresponding to the network and instantiate the VNF corresponding to the network.

18. The multi-access edge computing system according to claim 17, further comprising: MEC platform manager - network function virtualization MEPM-V, is used to receive the information of completion of instantiation of the VNF corresponding to the App sent by the VNFM corresponding to the App when the MEPM-V subscribes to the lifecycle notification to the VNFM corresponding to the App, or to receive the information of completion of instantiation of the VNF corresponding to the network sent by the VNFM corresponding to the network when the MEPM-V subscribes to the lifecycle notification to the VNFM corresponding to the network.

19. The multi-access edge computing system according to claim 18, wherein: The MEPM-V includes: a MEC network element manager and a MEC application rule and request manager, The MEC application rule and request manager is used to receive information on the completion of instantiation of the VNF corresponding to the App sent by the VNFM corresponding to the App, The MEC network element manager is used to receive information on completion of instantiation of the VNF corresponding to the network, sent by the VNFM corresponding to the network.

20. The multi-access edge computing system according to claim 18, further comprising: The VNF corresponding to the network; among them, The MEPM-V is used to receive a request for configuring a network instance sent by the MEAO, send a request for configuring a network instance to the VNF corresponding to the network, wherein the request for configuring a network instance is used to instruct the VNF corresponding to the network to configure relevant resources of the network, receive a response for configuring a network instance returned by the VNF corresponding to the network, wherein the response for configuring a network instance includes: information on completion of configuring the instance of the network; and return the response for configuring a network instance to the MEAO; The VNF corresponding to the network is used to receive the request to configure the network instance, configure the relevant resources of the network, and return the configured network instance response to the MEPM-V.

21. An electronic device, comprising: processor; as well as A memory coupled to the processor, for storing instructions, wherein when the instructions are executed by the processor, the processor executes the instantiation method according to any one of claims 1 to 13.

Images