Multi-access edge computing system and service processing method

Abstract

The present disclosure relates to a multi-access edge computing system and a processing method for services, and to the field of communication technology. The system disclosed in the present disclosure includes: a MEC network, a MEC platform, one or more MEC application apps, and a virtualized infrastructure VI set in a multi-access edge computing MEC host, wherein the MEC network is configured as a network instance running on the VI, providing mobile network functions; the MEC platform is configured to enable the MEC network and the MEC App to provide and use a set of basic functions required for MEC services; each MEC App is configured as an application instance running on the VI; the VI is configured to provide computing, storage, and network resources for running the MEC App and the MEC network; the MEC network interacts with the MEC platform through the Mm reference point, each MEC App interacts with the MEC platform through the Mp reference point, and the MEC platform interacts with the VI through the Mp reference point.

Description

Technical Field

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

[0002] With the advancement of 5G (5th Generation Mobile Communication Technology), all walks of life are moving towards informatization and intelligence, and applications are becoming more and more abundant, but most of them are large-bandwidth and low-latency services, such as XR (Extended Reality) services. Therefore, there is an increasing demand for MEC (Multi-access Edge Computing) systems.

[0003] The current MEC systems are designed based on APPs, and their main functions are to manage and serve APPs. In the post-5G and even 6G era, a single application solution can no longer meet the extreme requirements of bandwidth and latency for services. For example, if you want to achieve an immersive experience, you need a latency of no more than 10ms and a downlink rate of no less than 4Gbps, which poses unprecedented challenges to both MEC systems and networks. Summary of the invention

[0004] The inventor found that the current MEC system is a pure application system. The terminal needs to communicate with the MEC system through a mobile network (e.g., 5G network). For example, MEO (MEC Orchestrator) acts as an AF (Application Function) to communicate with the 5G network; or, the APP directly acts as an AF to communicate with the 5G network NEF through the proxy NEF (Network Exposure Function). In either case, the network and the application are separated, which can only solve the problem of "applications" being close to users, rather than fundamentally solving the problem of "services" being close to users. Under the 5G goal for vertical industries, this separated architecture obviously cannot meet the requirements, let alone the higher requirements of future services for bandwidth and latency.

[0005] A technical problem to be solved by the present disclosure is to propose a MEC system architecture to increase service bandwidth and reduce service latency.

[0006] According to some embodiments of the present disclosure, a multi-access edge computing system is provided, including: a MEC network, a MEC platform, one or more MEC application apps and a virtualized infrastructure VI arranged in a multi-access edge computing MEC host, wherein the MEC network is configured as a network instance running on the VI to provide mobile network functions; the MEC platform is configured to enable the MEC network and the MEC App to provide and use a set of basic functions required for MEC services; each MEC App is configured as an application instance running on the VI; the VI is configured to provide computing, storage and network resources for running the MEC App and the MEC network; the MEC network interacts with the MEC platform through the Mm reference point, each MEC App interacts with the MEC platform through the Mp reference point, and the MEC platform interacts with the VI through the Mp reference point.

[0007] In some embodiments, the MEC network is also configured to transmit application-related information exchanged between the terminal and the MEC platform; the MEC platform is also configured to exchange application-related information with the terminal through the MEC network, and to exchange corresponding application-related information with each MEC App; each MEC App is also configured to exchange application-related information corresponding to the MEC App with the MEC platform, and to process the application-related information corresponding to the MEC App.

[0008] In some embodiments, the system further includes: a MEC platform manager, wherein the MEC platform manager includes: a MEC network lifecycle manager, the MEC network lifecycle manager is configured to manage the lifecycle of the MEC network, and the MEC network interacts with the MEC network lifecycle manager through the Mm reference point.

[0009] In some embodiments, the MEC network includes: at least one of a radio access network RAN ​​distributed unit DU, a RAN central unit CU, a core network CN user plane UP and a CN control plane CP; wherein, the RAN DU and the RAN CU are configured to provide the functions of an access network element in a mobile network, and the CN UP and the CN CP are configured to provide the functions of a core network element in a mobile network.

[0010] In some embodiments, the CN CP includes: an access and mobility management function AMF instance and a session management function SMF instance, and the application-related information includes: a service request, the RAN CU is configured to receive a service request sent by the terminal and forward the service request to the AMF instance; the AMF instance is configured to forward the service request to the SMF instance; the SMF instance is configured to forward the service request to the MEC platform.

[0011] In some embodiments, the CN UP includes: a user plane function UPF instance, application-related information includes: first service data and / or second service data, the RAN DU is configured to receive the first service data sent by the terminal, forward the first service data to the UPF instance, and / or receive the second service data returned by the UPF instance and send it to the terminal; the UPF instance is configured to forward the first service data to the MEC platform, and / or receive the second service data returned by the MEC platform, and send it to the RANDU.

[0012] In some embodiments, in the network function virtualization NFV scenario, the MEC network is deployed as a MEC network virtualized network function module VNF, the MEC platform is deployed as a MEC platform VNF, the MEC application is deployed as a MEC application VNF, and the VI is deployed as a network function virtualization infrastructure NFVI.

[0013] In some embodiments, in the network function virtualization NFV scenario, the MEC platform manager is deployed as the MEC platform manager-NFV, and the MEC platform manager-NVF includes: a MEC network element manager, and entrusts the lifecycle management of the MEC network to the virtualized network function module manager VNFM corresponding to the MEC network.

[0014] In some embodiments, the system further includes: a multi-access edge orchestrator MEO interacting with the MEC platform manager through an Mm reference point; the MEO is configured to control the MEC network and the instantiation of the MEC application.

[0015] In some embodiments, in the network function virtualization NFV scenario, MEO is deployed as a MEC application orchestrator MEAO, which interacts with the NFV orchestrator NFVO to perform resource orchestration, and orchestrates the MEC application virtualized network function module VNF and the MEC network VNF into one or more NFV network services NS.

[0016] According to some other embodiments of the present disclosure, a method for processing services of a multi-access edge computing system based on any of the aforementioned embodiments is provided, including: application-related information exchanged between an MEC network transmission terminal and an MEC platform; application-related information corresponding to the interaction between the MEC platform and each MEC App; and the MEC App processing the corresponding application-related information.

[0017] In some embodiments, the method further includes: the MEC network lifecycle manager manages the lifecycle of the MEC network. In some embodiments, the application-related information includes: service requests, and the application-related information interacted between the MEC network transmission terminal and the MEC platform includes: the RAN CU in the MEC network receives the service request sent by the terminal; the RAN CU forwards the service request to the AMF instance in the MEC network; the AMF instance forwards the service request to the SMF instance in the MEC network; the SMF instance forwards the service request to the MEC platform.

[0018] In some embodiments, application-related information includes: first business data, and application-related information exchanged between the MEC network transmission terminal and the MEC platform includes: the RAN DU receiving terminal in the MEC network sends the first business data; the RAN DU sends the first business data to the UPF instance in the MEC network; the UPF instance sends the first business data to the MEC platform.

[0019] In some embodiments, application-related information includes: second business data, and application-related information exchanged between the MEC network transmission terminal and the MEC platform includes: the UPF instance in the MEC network receives the second business data sent by the MEC platform; the UPF instance sends the second business data to the RAN DU in the MEC network; and the RAN DU sends the second business data to the terminal.

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

[0021] The present disclosure proposes a MEC system, including a MEC network, a MEC platform, a MEC application and a VI arranged in a MEC host. The MEC network is a network instance running on the VI, providing mobile network functions, transmitting application-related information interacting between terminals and the MEC platform, and the MEC platform also interacts with each MEC application to obtain corresponding application-related information. Based on the architecture of the MEC system disclosed in the present disclosure, the "application" and "network" are designed to be integrated, breaking the idea that the existing MEC system only serves application APPs, and instantiating the network, especially the wireless mobile network, on the MEC system. Solve the problem from the fundamental "processing delay" and "transmission delay", shorten the delay, increase the bandwidth, and better serve large-bandwidth and low-latency services.

[0022] 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

[0023] 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.

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

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

[0026] Figure 3 A schematic diagram of the structure of a multi-access edge computing system in an NFV scenario according to some embodiments of the present disclosure is shown.

[0027] Figure 4 A flowchart illustrating a method for processing services according to some embodiments of the present disclosure is provided.

[0028] Figure 5 A flowchart illustrating a method for processing services according to other embodiments of the present disclosure is provided.

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

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

[0031] 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.

[0032] This disclosure proposes a MEC system, Figures 1 to 3 Give a description.

[0033] Figure 1 Figure 1 is an architecture diagram of some embodiments of the MEC system disclosed in the present invention. Figure 1As shown, the system 10 of this embodiment includes: a MEC host (MEC Host) 100, a MEC network (MEC network) 110 arranged in the MEC host, a MEC platform 120 (MEC platform, MEP), one or more MEC Apps 130 and a VI (Virtualisation infrastructure, virtualization infrastructure) 140.

[0034] In some embodiments, the MEC network 110 is configured as a network instance running on the VI 140 to provide mobile network functions; the MEC platform 120 is configured to enable the MEC network 110 and the MEC App 130 to provide and use a set of basic functions required for MEC services; each MEC App 130 is configured as an application instance running on the VI 140; the VI 140 is configured to provide computing, storage, and network resources for running the MEC App and the MEC network. The MEC network 110 is located on the MEC host and is deployed in a distributed manner.

[0035] In some embodiments, the MEC network 110 interacts with the MEC platform 120 through the Mm reference point. The MEC App 130 interacts with the MEC platform 120 through the Mp reference point. The MEC platform 120 interacts with the VI 140 through the Mp reference point.

[0036] VI 140 provides computing, storage, and network resources for running MEC App 130 and MEC network 110. MEC platform 120 is a collection of basic functions required to run MEC App 130 and MEC network 110 on VI 140 and enable them to provide and use MEC services (MECservice). MEC App 130 is instantiated on VI 140 based on the configuration or request verified by MEC management.

[0037] In some embodiments, the system 10 further includes: a MEC platform manager (MEC platform manager) 150. The MEC platform manager 150 includes: a MEC network life cycle manager (MEC network life cycle mgmt) 151. The MEC network life cycle manager 151 is configured to manage the life cycle of the MEC network 110, and the MEC network 110 interacts with the MEC network life cycle manager 151 through the Mm reference point.

[0038] The MEC network lifecycle manager 151 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.

[0039] In some embodiments, the system 10 further includes: a MEO (MEC orchestrator) 160 that interacts with the MEC platform manager 150 through an Mm reference point; the MEO 160 is configured to control the instantiation of the MEC network 110 and the MEC application 130 .

[0040] In some embodiments, the system 10 further includes: VIM 170 (Virtualisation infrastructure manager) for managing the allocation and release of virtual computing, storage and network resources, and managing the image files of the MEC network 110 and the MEC application 130, and is also responsible for collecting information on virtualized resources and reporting it to upper management entities such as the MEC platform manager 150 and the MEO 160 through Mm.

[0041] like Figure 2 As shown, the solution of the present disclosure adds MEC network and MEC network lifecycle manager to the existing MEC system software architecture, so as to deploy the mobile network in the MEC system closer to the user. Some existing functions of MEC host 100, MEC platform 120, MEC App 130, VI 140, MEC platform manager 150, MEO 160 and VIM 170, as well as functions of some existing modules, can refer to existing standards and will not be repeated here. Figure 2 In the figure, the three reference points Mm, Mp and Mx are numbered respectively. The reference points between the MEC network 110 and the MEC platform 120 and the MEC platform manager 150 are shown as Mmx and Mmy, which can be renumbered according to actual needs.

[0042] In some embodiments, the MEC network 110 is configured to transmit application-related information exchanged between the terminal and the MEC platform 120; the MEC platform 130 is configured to exchange application-related information with the terminal through the MEC network, and to exchange corresponding application-related information with each MEC App 130; each MEC App 130 is configured to exchange application-related information corresponding to the MEC App 130 with the MEC platform 120, and to process the application-related information corresponding to the MEC App 130.

[0043] like Figure 2 As shown, in some embodiments, the MEC network includes: at least one of: RAN (Radio Access Network) DU (Distributed Unit) 111, RAN CU (Centralized Unit) 112, CN (Core Network) UP (User Plane) 113 and CN CP (Control Plane) 114; 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.

[0044] 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.

[0045] In some embodiments, the CN CP includes: an AMF (Authentication Management Function, access and mobility management function) instance and an SMF (Session Management function, session management function) instance, and the application-related information includes: a service request and / or a service response. The AMF instance and the SMF instance can implement some or all of the functions of the AMF and SMF in the prior art.

[0046] The RAN CU 112 is configured to receive a service request sent by the terminal, forward the service request to the AMF instance, and / or receive a service response returned by the AMF instance and send it to the terminal.

[0047] The AMF instance is configured to forward the service request to the SMF instance, and / or receive the service response returned by the SMF instance and send it to the RAN CU 112.

[0048] The SMF instance is configured to forward the service request to the MEC platform 120, and / or receive the service response returned by the MEC platform 120 and send it to the AMF instance.

[0049] The terminal can select to access the RAN provided by the MEC system according to the cell selection or reselection scheme in the prior art. The RAN DU and RAN CU can realize the functions of the base station user plane and control plane. Then, the terminal interacts with the MEC platform through the AMF and SMF in the MEC system, and then the MEC platform interacts with the MEC App to send the corresponding service requests and / or service responses.

[0050] In some embodiments, the CN UP includes: a UPF (User Plane Function) instance, and the application related information includes: first service data and / or second service data. The UPF instance can implement part or all of the functions of the UPF in the prior art.

[0051] RAN DU 111 is configured to receive first service data sent by the terminal, forward the first service data to the UPF instance, and / or receive second service data returned by the UPF instance and send it to the terminal.

[0052] The UPF instance is configured to forward the first service data to the MEC platform 120 , and / or receive the second service data returned by the MEC platform 120 , and send it to the RAN DU 111 .

[0053] After the terminal accesses the corresponding service, it starts to interact with the MEC App for service data. The MEC system of the present disclosure only needs to go through the RAN DU, UPF, and MEC platform in the system.

[0054] In the prior art, the terminal initiates a service request, and the 5G network establishes a PDU link for it; the MEC system as the AF detects that the terminal (which has opened an account on the MEC platform) is in its service area and initiates a service that meets the requirements, so it decides to create a traffic steering request; the MEC system then creates a traffic steering request for the NEF (the NEF may be an edge NEF or a centrally deployed NEF, depending on the deployment situation) by calling the signaling Nnef_TrafficInfluence_Create serviceoperation; the NEF updates the request to the UDR (Unified Data Repository), and the UDR compares the received information with the existing information and updates it; due to the PCF (Policy ControlFunction, policy control function) subscribes to the update of UDR, so UDR sends the update information to PCF through Nudr_DM_Notify after the update; PCF, as the superior unit of SMF, further sends information to SMF by calling Npcf_SMPolicyControl_UpdateNotify, so that SMF executes the traffic steering requirements initiated by the MEC system; SMF executes the instructions of PCF and reconfigures the user plane, including selecting a new UPF and deleting the old UPF; SMF also sends the new UPF information to AMF, so that AMF configures the N3 (AMF and UPF) interface; the terminal uses the edge UPF as the N6 exit and uses the MEC system as the service bearer platform to use the service. The existing technology requires a complex process to guide the terminal's traffic to the MEC system. Through the solution disclosed in the present invention, the network and applications are all deployed in the MEC system. When the terminal initiates a service, it naturally selects the nearest / local wireless network, core network and platform. AMF, SMF, and UPF are all deployed and can be directly applied. As long as the terminal accesses the RAN in the MEC network, the relevant information can be directly transmitted through AMF, SMF, and UPF. There is no need for the MEC system to act as an AF to monitor changes in the terminal's location, and there is no need to go through the above-mentioned complex traffic guidance process, which greatly reduces latency and improves bandwidth.

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

[0056] In the NFV scenario, the MEC network is deployed as a MEC network VNF 310 (Virtualised Network Function), the MEC platform is deployed as a MEC platform VNF 320, the MEC application is deployed as a MEC application VNF 330, and the VI is deployed as an NFVI (NFV Infrastructure) 340.

[0057] In the NFV scenario, the MEC platform manager is deployed as MEC platform manager-NFV (MEPM-V) 350. The MEC platform manager-NVF includes: MEC network element manager (MEC network element mgmt) 351, and entrusts the lifecycle management of the MEC network to the VNFM (Virtualised Network Function Manager) 362 corresponding to the MEC network.

[0058] In the NFV scenario, MEO is deployed as MEAO (MEC Application Orchestrator) 360, which interacts with NFVO (NFV Orchestrator) 370 to perform resource orchestration and orchestrate MEC application VNF and MEC network VNF into one or more NFV NS (Network Service).

[0059] The solution disclosed in the present invention adds MEC network VNF, MEC network element manager, and VNFM corresponding to MEC network to the architecture of the existing MEC system in the NFV scenario. The functions of other modules can refer to the existing standards and will not be repeated here.

[0060] The above embodiment proposes a MEC system, including a MEC network, a MEC platform, a MEC application and a VI arranged in a MEC host. The MEC network is a network instance running on the VI, providing mobile network functions, and transmitting application-related information exchanged between the terminal and the MEC platform. The MEC platform also interacts with each MEC application to exchange corresponding application-related information. Based on the architecture of the MEC system of the above embodiment, the "application" and the "network" are designed as an integrated whole, breaking the idea that the existing MEC system only serves application APPs, and instantiating the network, especially the wireless mobile network, on the MEC system. Solve the problem from the fundamental "processing delay" and "transmission delay", shorten the delay, increase the bandwidth, and better serve large-bandwidth and low-latency services.

[0061] The present disclosure also proposes a method for processing services of the MEC system based on the aforementioned embodiment, including: application-related information exchanged between the MEC network transmission terminal and the MEC platform; application-related information corresponding to the interaction between the MEC platform and each MEC App; and the MEC App processes the corresponding application-related information. In some embodiments, the method further includes: a MEC network lifecycle manager manages the lifecycle of the MEC network.

[0062] Combine the following Figures 4-5 The processing method of the above business is described in detail.

[0063] Figure 4 Flowcharts of some embodiments of the processing method of the disclosed business. Figure 4 As shown, the method of this embodiment includes: steps S402 to S410.

[0064] In step S402, the terminal sends a service request to the RAN CU in the MEC network, and correspondingly, the RAN CU receives the service request sent by the terminal.

[0065] The service request may include the identifier of the MEC App.

[0066] In step S404, the RAN CU forwards the service request to the AMF instance in the MEC network.

[0067] In step S406, the AMF instance forwards the service request to the SMF instance in the MEC network.

[0068] In step S408, the SMF instance forwards the service request to the MEC platform.

[0069] In step S410, the MEC platform forwards the service request to the corresponding MEC App for processing.

[0070] The processing process of MEC App can refer to the existing technology and will not be repeated here.

[0071] If the MEC App wants to return a service response, for example, the MEC App sends a service response to the MEC platform. The MEC platform sends the service response to the SMF instance in the MEC network. The SMF instance forwards the service response to the AMF instance in the MEC network. The AMF instance forwards the service response to the RAN CU in the MEC network. The RAN CU forwards the service response to the terminal.

[0072] After the service request of the terminal is accepted, the service data can be transmitted.

[0073] Figure 5 Flowcharts of other embodiments of the processing method of the disclosed business. Figure 5 As shown, the method of this embodiment includes: steps S502 to S516.

[0074] In step S502, the terminal sends first service data to the RAN DU in the MEC network.

[0075] In step S504, the RAN DU sends the first service data to the UPF instance in the MEC network.

[0076] In step S506, the UPF instance sends the first service data to the MEC platform.

[0077] In step S508, the MEC platform forwards the first service data to the corresponding MEC App for processing.

[0078] In step S510, the MEC App sends the second service data to the MEC platform.

[0079] In step S512, the MEC platform sends the second service data to the UPF instance in the MEC network.

[0080] In step S514, the UPF instance sends the second service data to the RAN DU in the MEC network.

[0081] In step S516, the RAN DU sends the second service data to the terminal.

[0082] However, through the method of the above embodiment, the network and applications are all deployed in the MEC system. When the terminal initiates a service, it naturally selects the nearest / local wireless network, core network and platform. AMF, SMF and UPF are all deployed and can be directly applied. As long as the terminal accesses the RAN in the MEC network, the relevant information can be directly transmitted through AMF, SMF and UPF. There is no need for the MEC system to act as an AF to monitor the terminal location changes, and there is no need to go through the above-mentioned complex traffic guidance process, which greatly reduces the latency and improves the bandwidth.

[0083] The present disclosure proposes an enhanced MEC system architecture and method, which expands the existing MEC edge system architecture, solves the problem of "application" + "network" being close to users in an integrated manner, instantiates the wireless network on the MEC system, and adds management of the MEC network life cycle, so that OSS can uniformly send business information to MEO, and MEO can send instructions to MEPM according to business requirements. MEPM pulls up the entire network + application integrated network to solve business scenarios with extreme bandwidth + latency requirements and provide better business experience.

[0084] The electronic devices (e.g., multi-access edge computing systems) in the embodiments of the present disclosure may be implemented by various computing devices or computer systems. Figure 6 as well as Figure 7 Give a description.

[0085] Figure 6 FIG. 1 is a structural diagram of some embodiments of the electronic device disclosed in the present invention. Figure 6 As shown, the electronic device 60 of this embodiment includes: a memory 610 and a processor 620 coupled to the memory 610, and the processor 620 is configured to execute a service processing method in any of the embodiments of the present disclosure based on instructions stored in the memory 610.

[0086] The memory 610 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.

[0087] Figure 7 FIG. 1 is a structural diagram of some other 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, which are similar to the memory 610 and the processor 620 respectively. It can also include an input and output interface 730, a network interface 740, a storage interface 750, etc. These interfaces 730, 740, 750 and the memory 710 and the processor 720 can be connected, for example, via a bus 760. Among them, the input and output interface 730 provides a connection interface for input and output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 740 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 750 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0088] 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. Moreover, 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.

[0089] 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 box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes 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.

[0090] 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.

[0091] 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 A step that specifies a function in one or more boxes.

[0092] 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 multi-access edge computing system, comprising: The MEC network, MEC platform, one or more MEC application Apps and virtualized infrastructure VI are set in the multi-access edge computing MEC host, wherein: The MEC network is configured as a network instance running on the VI to provide mobile network functions; The MEC platform is configured as a set of basic functions required for the MEC network and the MEC App to provide and use MEC services; Each MEC App is configured as an application instance running on the VI; The VI is configured to provide computing, storage, and network resources for running the MEC App and the MEC network; The MEC network interacts with the MEC platform through the Mm reference point, each MEC App interacts with the MEC platform through the Mp reference point, and the MEC platform interacts with the VI through the Mp reference point.

2. The system according to claim 1, wherein: The MEC network is further configured to transmit application-related information exchanged between the terminal and the MEC platform; The MEC platform is further configured to interact with the terminal via the MEC network to exchange the application-related information, and interact with each MEC App to exchange the corresponding application-related information; Each MEC App is also configured to interact with the MEC platform to obtain application-related information corresponding to the MEC App, and to process the application-related information corresponding to the MEC App.

3. The system according to claim 1, further comprising: The MEC platform manager comprises: a MEC network lifecycle manager, wherein the MEC network lifecycle manager is configured to manage the lifecycle of the MEC network, and the MEC network interacts with the MEC network lifecycle manager through an Mm reference point.

4. The system according to claim 2, wherein: The MEC network includes: at least one of a radio access network RAN ​​distributed unit DU, a RAN central unit CU, a core network CN user plane UP and a 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.

5. The system according to claim 4, wherein: The CN CP includes: an access and mobility management function AMF instance and a session management function SMF instance, and the application related information includes: a service request, The RAN CU is configured to receive a service request sent by the terminal, and forward the service request to the AMF instance; The AMF instance is configured to forward the service request to the SMF instance; The SMF instance is configured to forward the service request to the MEC platform.

6. The system according to claim 4, wherein: The CN UP includes: a user plane function UPF instance, and the application related information includes: first service data and / or second service data, The RAN DU is configured to receive first service data sent by the terminal, forward the first service data to the UPF instance, and / or receive second service data returned by the UPF instance and send it to the terminal; The UPF instance is configured to forward the first service data to the MEC platform, and / or receive the second service data returned by the MEC platform and send it to the RAN DU.

7. The system according to claim 1, wherein: In the network function virtualization NFV scenario, the MEC network is deployed as a MEC network virtualized network function module VNF, the MEC platform is deployed as a MEC platform VNF, the MEC application is deployed as a MEC application VNF, and the VI is deployed as a network function virtualization infrastructure NFVI.

8. The system according to claim 3, wherein: In the network function virtualization NFV scenario, the MEC platform manager is deployed as a MEC platform manager-NFV, and the MEC platform manager-NVF includes: a MEC network element manager, and entrusts the lifecycle management of the MEC network to the virtualized network function module manager VNFM corresponding to the MEC network.

9. The system according to claim 3, further comprising: A multi-access edge orchestrator MEO interacting with the MEC platform manager via an Mm reference point; The MEO is configured to control the MEC network and the instantiation of the MEC application.

10. The system according to claim 9, wherein: In the network function virtualization NFV scenario, the MEO is deployed as the MEC application orchestrator MEAO, which interacts with the NFV orchestrator NFVO to perform resource orchestration, and orchestrates the MEC application virtualized network function module VNF and the MEC network VNF into one or more NFV network services NS.

11. A method for processing services of a multi-access edge computing system according to claim 1, comprising: The MEC network transmits application-related information that is exchanged between the terminal and the MEC platform; The MEC platform interacts with each MEC App to obtain application-related information; The MEC App processes the corresponding application related information.

12. The processing method according to claim 11, further comprising: The MEC network lifecycle manager manages the lifecycle of the MEC network.

13. The processing method according to claim 11, wherein: The application related information includes: service request, and the application related information exchanged between the MEC network transmission terminal and the MEC platform includes: The RAN CU in the MEC network receives the service request sent by the terminal; The RAN CU forwards the service request to the AMF instance in the MEC network; The AMF instance forwards the service request to the SMF instance in the MEC network; The SMF instance forwards the service request to the MEC platform.

14. The processing method according to claim 11, wherein: The application related information includes: first business data, and the application related information exchanged between the MEC network transmission terminal and the MEC platform includes: The RAN DU in the MEC network receives the first service data sent by the terminal; The RAN DU sends the first service data to the UPF instance in the MEC network; The UPF instance sends the first service data to the MEC platform.

15. The processing method according to claim 11, wherein: The application related information includes: second business data, and the application related information exchanged between the MEC network transmission terminal and the MEC platform includes: The UPF instance in the MEC network receives the second service data sent by the MEC platform; The UPF instance sends the second service data to the RAN DU in the MEC network; The RAN DU sends the second service data to the terminal.

16. 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 processing method according to any one of claims 11 to 15.

Images