Method of deploying multi-access edge compute applications

Abstract

The application provides a method, a system and a device for receiving, by a platform manager node, virtualized network function, VNF, instance information from a wireless communication node; selecting, by the platform manager node, a multi-access edge computing platform, MEP, from a plurality of candidate MEPs according to the VNF instance information; and sending, by the platform manager node, a first configuration request including the VNF instance information to the selected MEP.

Description

[0001] This document generally relates to wireless communication, specifically to multi-access edge computing (MEC).

[0002] In a Network Function Virtualization (NFV) environment, MEC applications can be treated as virtualized network functions (VNFs) by NFV Management and Orchestration (MANO) components. The MEC system can delegate some orchestration and lifecycle management (LCM) tasks to the NFV-MANO system (also referred to as NFV-MANO in this disclosure).

[0003] In some approaches, the Multi-access Edge Application Orchestrator (MEAO) process and Application Programming Interface (API) are used to trigger the instantiation of the NFV-MANO system for the MEC application. However, it remains unclear how to use an Operations Support System (OSS) or Business Support System (BSS) to trigger the instantiation of the VNF instance used in the MEC system by the NFV-MANO system.

[0004] Some aspects of this disclosure relate to methods, systems, and apparatus for sending VNF instance information to a target Multi-access Edge Computing Platform (MEP).

[0005] One aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: receiving Virtualized Network Function (VNF) instance information from a wireless communication node by a platform manager node; selecting a Multi-Access Edge Computing Platform (MEP) from a plurality of candidate MEPs based on the VNF instance information by the platform manager node; and sending a first configuration request including the VNF instance information to the selected MEP by the platform manager node.

[0006] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: an orchestrator node selecting a MEPM-V from a plurality of candidate Multi-Access Edge Platform Manager-Network Function Virtualization (MEPM-V) instances based on VNF instance information; and the orchestrator node sending the VNF instance information to the selected MEPM-V, wherein the selected MEPM-V is configured to manage a MEP.

[0007] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: receiving VNF instance information from a MEPM-V by an edge computing platform node; wherein the MEPM-V selects an edge computing platform node from candidate nodes based on the VNF instance information.

[0008] Another aspect of this disclosure relates to a wireless communication method. In one embodiment, the wireless communication method includes: sending VNF instance information from a virtualization management node to an OSS or BSS; wherein the VNF instance information is used to select a MEP from a plurality of candidate MEPs, and the VNF instance information is sent to the selected MEP.

[0009] Another aspect of this disclosure relates to a platform manager node. In one embodiment, the platform manager node includes a communication unit and a processor. The processor is configured to receive Virtualized Network Function (VNF) instance information from a wireless communication node; select a Multi-Access Edge Computing Platform (MEP) from a plurality of candidate MEPs based on the VNF instance information; and send a first configuration request including the VNF instance information to the selected MEP.

[0010] Another aspect of this disclosure relates to an orchestrator node. In one embodiment, the orchestrator node includes a communication unit and a processor. The processor is configured to select a MEPM-V from a plurality of candidate Multi-Access Edge Platform Manager-Network Function Virtualization (MEPM-V) instances based on VNF instance information; and to send the VNF instance information to the selected MEPM-V, wherein the selected MEPM-V is configured to manage the MEP.

[0011] Another aspect of this disclosure relates to an edge computing platform node. In one embodiment, the edge computing platform node includes a communication unit and a processor. The processor is configured to receive VNF instance information from MEPM-V, wherein MEPM-V selects the edge computing platform node from candidate nodes based on the VNF instance information.

[0012] Another aspect of this disclosure relates to a virtualization management node. In one embodiment, the virtualization management node includes a communication unit and a processor. The processor is configured to send VNF instance information to an OSS or BSS, wherein the VNF instance information is used to select a MEP from a plurality of candidate MEPs, and the VNF instance information is sent to the selected MEP.

[0013] Various embodiments may preferably implement the following features.

[0014] Preferably, the VNF instance information includes the location information of the corresponding VNF instance.

[0015] Preferably, the wireless communication node is a Multi-Access Edge Application Orchestrator (MEAO), and the platform manager node is configured to receive a second configuration request from the MEAO, including VNF instance information.

[0016] Preferably, the wireless communication node is a VNF manager (VNFM), and the platform manager node is configured to subscribe to notifications that include VNF instance information from the VNFM.

[0017] Preferably, the platform manager node is configured to send a first configuration request to the MEP in response to the platform manager node being able to meet the location requirements in the VNF instance information.

[0018] Preferably, the platform manager node is configured to obtain multi-access edge computing (MEC) configuration information by sending a request including VNF instance information to MEAO, and send a first configuration request to MEP based on the MEC configuration information.

[0019] Preferably, the platform manager node is configured to receive VNF instance information from the MEC system portal.

[0020] Preferably, the VNF instance information includes the location information of the corresponding VNF instance.

[0021] Preferably, the orchestrator node is configured to receive VNF instance information from the Operation Support System (OSS) or the Business Support System (BSS).

[0022] Preferably, the orchestrator node is configured to send VNF instance information to MEPM-V based on the location information of the VNF instance information.

[0023] Preferably, the orchestrator node is configured to receive subscription notifications, including VNF instance information, from the Network Functions Virtualization Orchestrator (NFVO).

[0024] Preferably, the orchestrator node is configured to provide MEC configuration information to MEPM-V, allowing MEPM-V to send configuration requests to the MEP based on the MEC configuration information.

[0025] Preferably, the orchestrator node is configured to receive VNF instance information from the MEC system portal.

[0026] Preferably, the VNF instance information is included in the configuration request from MEPM-V that requests configuration of the MEC application.

[0027] Preferably, the edge computing platform node is configured to receive VNF instance information from the MEC system portal.

[0028] Preferably, the virtualization management node is configured to determine the VNF instance information from OSS or BSS based on the deployment location constraints if they are provided.

[0029] Preferably, the virtualization management node is configured to send a subscription notification to MEAO that includes VNF instance information.

[0030] Preferably, the virtualization management node is configured to send a subscription notification, including VNF instance information, to at least one MEPM-V.

[0031] Preferably, the virtualization management node is configured to select a VNFM to instantiate a VNF instance, and the selected VNFM sends a subscription notification based on the location information of the VNF instance.

[0032] Preferably, the edge computing platform node is configured to receive VNF instance information from the NFV management portal.

[0033] This disclosure relates to a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the wireless communication method described in any of the foregoing methods.

[0034] The exemplary embodiments disclosed herein are intended to provide features that will become apparent from the following description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications may be made to the disclosed embodiments without departing from the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0035] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged without departing from the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and that this disclosure is not limited to the specific order or hierarchy presented, unless otherwise expressly stated.

[0036] The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, description and claims.

[0037] Figure 1 The architecture of the European Telecommunications Standards Institute (ETSI) NFV according to an embodiment of this disclosure is shown.

[0038] Figure 2 A framework for an MEC according to an embodiment of this disclosure is shown, and general entities involved in the MEC are illustrated.

[0039] Figure 3 The infrastructure for deploying an MEC system in an NFV environment according to an embodiment of this disclosure is shown.

[0040] Figure 4 A schematic diagram illustrating the process of instantiating an NFV instance for an MEC application according to an embodiment of this disclosure is shown.

[0041] Figure 5 A deployment environment consisting of an NFV-MANO system and a MEC system according to an embodiment of this disclosure is shown.

[0042] Figure 6 A schematic diagram of a method according to an embodiment of the present disclosure is shown.

[0043] Figure 7 A schematic diagram of a method according to an embodiment of the present disclosure is shown.

[0044] Figure 8 A schematic diagram of a method according to an embodiment of the present disclosure is shown.

[0045] Figure 9 A schematic diagram of a method according to an embodiment of the present disclosure is shown.

[0046] Figure 10 A schematic diagram of a method according to an embodiment of the present disclosure is shown.

[0047] Figure 11An example of a schematic diagram of a wireless communication node according to an embodiment of the present disclosure is shown.

[0048] In non-virtualized networks, network functions (NFs) are implemented by integrating vendor-specific software and hardware. The development of Network Function Virtualization (NFV) technology decouples software from hardware. Since network components are no longer an integration of hardware and software, software and hardware development can be independent. Virtualized Network Functions (VNFs) allow networks to respond quickly and automatically to the traffic and service demands running on them. Figure 1 The architecture of the European Telecommunications Standards Institute (ETSI) NFV according to an embodiment of this disclosure is shown.

[0049] Multi-access Edge Computing (MEC) allows MEC applications to become pure software entities running within a virtualized infrastructure. Figure 2 A framework for an MEC according to an embodiment of this disclosure is shown, and general entities involved in the MEC are illustrated.

[0050] MEC and NFV are complementary concepts. The way MEC infrastructure is designed allows for a variety of different deployment options for MEC systems. Figure 3 The infrastructure for deploying an MEC system in an NFV environment according to an embodiment of this disclosure is shown.

[0051] In an NFV environment, the NFV Management and Orchestration (MANO) component can treat MEC applications as Virtualized Network Functions (VNFs). The MEC system can delegate some orchestration and lifecycle management (LCM) tasks to the NFV-MANO system and the Virtual Network Function Manager (VNFM) functionality. The MEC application used for the VNF instantiation process (i.e., LCM tasks) consists of two parts:

[0052] 1) The first part is to instantiate the VNF for MEC applications, which includes creating the necessary virtualization resources and initial configuration of the VNF instance.

[0053] 2) The second part is that the MEC Platform Manager-NFV (MEPM-V) sends configurations to the MEC platform (including traffic rules, DNS rules, required and optional services, services generated by application instances, etc.).

[0054] Figure 4 A schematic diagram illustrating the process of instantiating an NFV instance for an MEC application according to an embodiment of this disclosure is shown. Figure 4 In this process, the MEC system (e.g., the Multi-Access Edge Application Orchestrator (MEAO) within it) triggers the NFV-MANO (e.g., the NFV-MANO system) to perform the VNF initialization process and returns all relevant information, especially the identifier (ID) of the created VNF instance, to the MEC system. Therefore, Figure 4 The process shown can be considered as the MEC system (or MEAO) dominant process.

[0055] In a business environment, MEC and NFV may belong to different departments. MEC management may not be allowed to directly trigger NFV-MANO to perform certain operations. In this case, a method is needed to enable the Operations Support System (OSS) to trigger the NFV-MANO instantiation process. The MEC system can then use MEC applications to take over the created VNF instances. Note that the number of MEAOs, MEPM-Vs, and / or MEPs in the MEC system can vary. Figure 3 The number shown is not specified. In more complex management topologies, there may be multiple MEAOs, MEPM-Vs, and / or MEPs. Furthermore, the management domain of the MEC system may not be exactly the same as the management domain of the NFV-MANO. Figure 5 A deployment environment according to an embodiment of this disclosure is illustrated, wherein the management domain of NFV-MANO covers the management domains of two MEC systems. Each MEC system manages a management domain with multiple MEPM-Vs, each MEPM-V controlling one or more MEC hosts, and the MEC hosts are deployed at different or the same NFV Infrastructure (NFVI) sites. The MEAO in the management domain of each MEC system is connected to the Network Functions Virtualization Orchestrator (NFVO) in the management domain of NFV-MANO. The MEPM-V in the management domain of each MEC system is connected to one of the VNFMs in the management domain of NFV-MANO.

[0056] With corresponding Figure 4 Compared to the MEC system in the embodiments, Figure 5 The MEC system in the OSS may not be able to verify the interaction between OSS and NFV-MANO. Therefore, it is necessary to figure out how to select a MEC host from all candidate hosts on the same site, and how to make the selected MEC host take over the VNF instance so that the selected MEC host can continue to configure MEC applications for the VNF instance.

[0057] Figure 7 A schematic diagram of a method according to an embodiment of the present disclosure is shown. Figure 7 The method shown can be used to extend the interface between OSS / BSS and MEC systems to provide VNF instance information to the MEC system.

[0058] In one embodiment, the NFV-MANO is a management system including an NFVO and at least one VNFM. In one embodiment, the NFV-MANO can be considered as a network node (e.g., a virtualization management node). In one embodiment, the NFV-MANO can be considered as a network node including different functions and / or sub-nodes.

[0059] In this embodiment, the application package, including the application image, has been uploaded to NFV-MANO as a VNF package. NFV-MANO performs instantiation based on the VNF package.

[0060] In this embodiment, the OSS / BSS requests NFV-MANO to instantiate a VNF instance based on an application package (e.g., a VNF package). Deployment location constraints can also be sent to NFV-MANO (step 701). In one embodiment, deployment location constraints can be location constraints of the VNF instance, such as latitude and longitude coordinates, data center identifiers, multiple identifiers for multiple data centers, server rack identifiers, and server identifiers.

[0061] In step 702, after instantiating the VNF instance as needed, NFV-MANO sends a response to OSS / BSS.

[0062] It should be noted that if there are no deployment location constraints in the request, or if NFV-MANO has already updated the deployment location constraints based on the VNF instantiation location information, then the VNF instantiation location information will be sent as a parameter in the response.

[0063] In step 703, the OSS / BSS requests MEAO to instantiate the application. In one embodiment, VNF instance information (i.e., VNF instance details) is sent as a parameter in the request. In one embodiment, the VNF instance includes the location information of the VNF instance. In another embodiment, the location information of the VNF instance includes the aforementioned deployment location constraints and / or the location information of the VNF instantiation.

[0064] In one embodiment, if there is more than one MEC system in the region that meets one or more requirements (e.g., deployment location constraints) in the VNF instance information, the OSS / BSS sends a request to each MEAO of the MEC system that meets one or more requirements (e.g., deployment location constraints) in the VNF instance information.

[0065] In step 704, MEAO selects a MEC host based on VNF instance information (e.g., deployment location constraints). MEAO sends a first configuration application request to the MEPM-V managing the selected MEC host, wherein the VNF information is included as a parameter in the first configuration application request.

[0066] In step 705, MEPM-V sends a second configuration application request to the MEP on the selected MEC host, wherein VNF information is included as a parameter in the second configuration application request.

[0067] In step 706, the MEP sends a first configuration application response to the MEPM-V. The MEPM-V sends a second configuration application response to the MEAO. The MEAO sends an instantiation application response to the OSS / BSS.

[0068] Figure 8 A schematic diagram of a method according to an embodiment of the present disclosure is shown. Figure 8 The method shown can be used to extend the interface between NFV and MEC systems. In this embodiment, the application package, including the application image, has been uploaded to NFV-MANO as a VNF package. The MEC system confirms that the application package has been uploaded to NFV-MANO. Furthermore, an MEC application may belong to more than one MEC system.

[0069] In step 801, MEAO in the MEC system sends a subscription request to NFVO in NFVO-MANO, along with a filter for notifications related to VNF instantiation.

[0070] In step 802, the OSS / BSS requests NFV-MANO to instantiate a VNF instance based on the application package. Deployment location constraints are also sent to NFV-MANO.

[0071] In step 803, after instantiating the VNF instance as needed, NFV-MANO sends a response to OSS / BSS.

[0072] It should be noted that if there are no deployment location constraints in the request, or if NFV-MANO has already updated the deployment location constraints based on the VNF instantiation location information, then the VNF instantiation location information will be sent as a parameter in the response.

[0073] In step 804, the NFVO in NFV-MANO sends a notification to MEAO, along with VNF instance information. Details of the VNF instance information can be found by referring to the paragraphs above, and will not be repeated here.

[0074] In step 805, MEAO selects a MEC host based on VNF instance information (e.g., deployment location constraints). MEAO sends a first configuration application request to the MEPM-V managing the selected MEC host, wherein the VNF instance information is included as a parameter in the first configuration application request.

[0075] In step 806, MEPM-V sends a second configuration application request to the MEP on the selected MEC host, wherein VNF information is included as a parameter in the second configuration application request.

[0076] In step 807, the MEP sends a first configuration application response to the MEPM-V. The MEPM-V then sends a second configuration application response to the MEAO.

[0077] Figure 9 A schematic diagram of a method according to an embodiment of the present disclosure is shown. Figure 9 The method shown can be used to extend the interface between NFV and MEC systems. Figure 9 The application package, including the application image, has been uploaded to NFV-MANO as a VNF package. The MEC system confirms that the application package has been uploaded to NFV-MANO. It should be noted that a MEC application may belong to more than one MEC system. In a single MEC system, an application may belong to more than one MEC host.

[0078] In step 901, the MEPM-V in the MEC system sends a subscription request to the VNFM in the NFV-MANO, along with a filter for notifications related to VNF instantiation.

[0079] In step 902, the OSS / BSS requests NFV-MANO to instantiate a VNF instance based on the application package. Deployment location constraints are also sent to NFV-MANO.

[0080] In step 903, the NFVO in NFV-MANO selects the VNFM based on the deployment location constraints used to instantiate the VNF instance. After instantiating the VNF instance as needed, NFV-MANO sends a response to OSS / BSS.

[0081] It should be noted that if there are no deployment location constraints in the request, or if NFV-MANO has already updated the deployment location constraints based on the VNF instantiation location information, then the VNF instantiation location information will be sent as a parameter in the response.

[0082] In step 904, VNFM sends a notification to each MEPM-V that has subscribed to the notification. The notification contains VNF instance information. Details of the VNF instance information can be found by referring to the paragraphs above, and will not be repeated here.

[0083] In step 905, MEPM-V receives a notification and compares the VNF instance information (e.g., deployment location constraints) with its respective local information to check whether the VNF instance information (e.g., deployment location constraints) is within its management scope (e.g., MEPM-V's management scope).

[0084] In step 906, the MEPM-V with a matching management scope (e.g., management range) sends a configuration information request to MEAO, wherein the VNF instance information is included as a parameter in the configuration information request.

[0085] In step 907, MEAO selects configuration information based on the received VNF instance information. MEAO then sends a configuration information response containing the configuration information to the corresponding MEPM-V.

[0086] In step 908, MEPM-V sends a configuration application request to the MEP on the selected MEC host, wherein VNF information is included as a parameter in the configuration application request.

[0087] In step 909, the MEP sends a configuration application response to the MEPM-V.

[0088] Figure 10 A schematic diagram of a method for providing VNF instance information according to an embodiment of this disclosure is shown. Figure 10 The method shown can be used to transfer VNF instance information between NFV-MANO and MEC systems. Figure 10 The application package, including the application image, has been uploaded to NFV-MANO as a VNF package.

[0089] In one embodiment, the NFV-MANO is a management system including an NFVO and at least one VNFM. In one embodiment, the NFV-MANO can be considered as a network node (e.g., a virtualization management node). In one embodiment, the NFV-MANO can be considered as a network node including different functions and / or sub-nodes.

[0090] Specifically, the operator triggers NFV-MANO to instantiate a VNF instance for MEC applications through the NFV-MANO portal. The operator selects the application package and deployment location (step 1001).

[0091] In step 1002, after successfully instantiating the VNF instance, the operator receives feedback from NFV-MANO.

[0092] In step 1003, the operator selects the MEC host at the deployment location through the MEC system portal and provides the VNF instance information to the MEP on the MEC host.

[0093] In step 1004, the operator provides VNF instance information to MEPM-V and MEAO, which manages the MEC hosts, through the MEC system portal. This establishes a connection between the VNF instance and the MEC host.

[0094] In one embodiment, this disclosure provides a method for directly deploying MEC applications via NFV-MANO.

[0095] In one embodiment, VNF instance information is included in the instantiation application request between OSS / BSS and MEAO.

[0096] In one embodiment, VNF instance information is included in the configuration application request between MEAO and MEPM-V and / or between MEPM-V and MEP.

[0097] In one embodiment, the VNF instance location information is included in a notification sent from NFV-MANO to the MEC system.

[0098] In one embodiment, a configuration information request containing VNF instance information between MEPM-V and MEAO is defined.

[0099] In one embodiment, the MEC system portal is extended to transmit VNF ​​instance information to MEAO and / or MEPM-V and / or MEP.

[0100] Figure 11The diagram relates to a wireless communication node 110 according to an embodiment of this disclosure. The wireless communication node 110 may be a satellite, base station (BS), network entity, mobility management entity (MME), serving gateway (S-GW), packet data network (PDN) gateway (P-GW), radio access network (RAN) node, next-generation RAN (NG-RAN) node, gNB, eNB, data network, core network, radio network controller (RNC), MEPM-V, MEP, MEAO, or NFV-MANO, and is not limited herein. Furthermore, the wireless network node 120 may include (execute) at least one network function, such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), an Application Function (AF), etc. Wireless communication node 110 may include, for example, a processor 1100 (a microprocessor or application-specific integrated circuit, ASIC), a storage unit 1110, and a communication unit 1120. Storage unit 1110 may be any data storage device storing program code 1112 accessed and executed by processor 1100. Embodiments of storage unit 1110 include, but are not limited to, a Subscriber Identity Module (SIM), Read-Only Memory (ROM), flash memory, Random-Access Memory (RAM), hard disk, and optical data storage devices. Communication unit 1120 may be a transceiver and is used to send and receive signals (e.g., messages or packets) based on the processing results of processor 1100. In one embodiment, communication unit 1120 is connected via… Figure 11 At least one antenna 1122 shown transmits and receives signals.

[0101] In one embodiment, storage unit 1110 and program code 1112 may be omitted, and processor 1100 may include storage unit storing program code.

[0102] The processor 1100 may, for example, implement any of the steps in the exemplary embodiments on the wireless communication node 110 by executing program code 1112.

[0103] The communication unit 1120 may be a transceiver. Alternatively or as a supplement, the communication unit 1120 may combine a transmitting unit and a receiving unit, and be configured to transmit signals to and receive signals from another wireless communication node, respectively.

[0104] According to embodiments of this disclosure, a wireless communication method is also provided. In one embodiment, the wireless communication method can be executed using a platform manager node (e.g., MEPM-V). In one embodiment, the platform manager node can be implemented using the aforementioned wireless communication node 110, but is not limited thereto.

[0105] In one embodiment, the wireless communication method includes: a platform manager node receiving virtualized network function (VNF) instance information from a wireless communication node; the platform manager node selecting a multiple candidate multi-access edge computing platforms (MEPs) based on the VNF instance information; and the platform manager node sending a first configuration request, including the VNF instance information, to the selected MEP.

[0106] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0107] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, this wireless communication method can be performed using an orchestrator node (e.g., MEAO). In one embodiment, the orchestrator node can be implemented using the aforementioned wireless communication node 110, but is not limited thereto.

[0108] In one embodiment, the wireless communication method includes an orchestrator node selecting a MEPM-V from a plurality of candidate Multi-Access Edge Platform Manager-Network Function Virtualization (MEPM-V) based on VNF instance information; and the orchestrator node sending VNF instance information to the selected MEPM-V, wherein the selected MEPM-V is configured to manage a MEP.

[0109] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0110] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, this wireless communication method can be performed using an edge computing platform node (e.g., a MEP). In one embodiment, the edge computing platform node can be implemented using the aforementioned wireless communication node 110, but is not limited thereto.

[0111] In one embodiment, the wireless communication method includes receiving VNF instance information from MEPM-V by an edge computing platform node; wherein MEPM-V selects an edge computing platform node from candidate nodes based on the VNF instance information.

[0112] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0113] According to embodiments of this disclosure, another wireless communication method is also provided. In one embodiment, this wireless communication method can be performed using a virtualized management node (e.g., NFV-MANO). In one embodiment, the virtualized management node can be implemented using the aforementioned wireless communication node 110, but is not limited thereto.

[0114] In one embodiment, the wireless communication method includes sending VNF instance information from a virtualization management node to an OSS or BSS; wherein the VNF instance information is used to select a MEP from a plurality of candidate MEPs, and the VNF instance information is sent to the selected MEP.

[0115] For details on this, please refer to the paragraphs above; they will not be repeated here.

[0116] While various embodiments of this disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations, and these figures are provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0117] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., generally does not restrict the number or order of these elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, referring to a first element and a second element does not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0118] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0119] Those skilled in the art will further appreciate that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination thereof), firmware, various forms of program or design code incorporating instructions (which may be referred to herein as “software” or “software unit” for convenience), or any combination of these technologies.

[0120] To clearly illustrate this interchangeability of hardware, firmware, and software, the functionality of various illustrative components, blocks, units, circuits, and steps has been generally described above. Whether this functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more of the functions described herein. The terms “configured to” or “configured for” as used herein in relation to a particular operation or function refer to processors, devices, components, circuits, structures, machines, units, etc., which are physically constructed, programmed, and / or arranged to perform a particular operation or function.

[0121] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, cells, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, cells, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor; however, alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0122] Computer-readable media include computer storage media and communication media (including any media capable of transferring computer programs or code from one place to another). Storage media can be any available medium that is accessible to a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that is accessible to a computer.

[0123] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for purposes of discussion, various units are described as discrete units; however, it will be apparent to those skilled in the art that two or more units can be combined to form a single unit performing the relevant functions according to embodiments of this disclosure.

[0124] Furthermore, in embodiments of this disclosure, memory or other storage devices and communication components may be employed. It should be understood that, for clarity, the above description has referenced various functional units and processors in describing embodiments of this disclosure. However, it will be apparent that any suitable functional distribution may be used among different functional units, processing logic elements, or domains without departing from this disclosure. For example, functionality illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means of providing said functionality and do not indicate a strict logical or physical structure or organization.

[0125] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be endowed with the widest scope consistent with the novel features and principles disclosed herein, as set forth in the appended claims.

Claims

1. A wireless communication method, comprising: The orchestrator node selects a MEPM-V from multiple candidate Multi-Access Edge Platform Manager - Network Function Virtualization MEPM-V based on the VNF instance information, wherein the VNF instance information includes the location information of the corresponding VNF instance; and The orchestrator node provides the selected MEPM-V with multi-access edge computing (MEC) configuration information, wherein the selected MEPM-V is configured to manage the multi-access edge computing platform (MEP).

2. The wireless communication method according to claim 1, wherein, The selected MEPM-V sends configuration information to the MEP, which includes traffic rules, DNS rules, required and optional services, and services generated by the application instance.

3. The wireless communication method according to claim 1, wherein, The orchestrator node is configured to receive the VNF instance information from the Operation Support System (OSS).

4. The wireless communication method according to claim 1, wherein, The orchestrator node is configured to receive subscription notifications, including information about the VNF instance, from the Network Functions Virtualization Orchestrator (NFVO).

5. The wireless communication method according to claim 1, wherein, The MEC configuration information is provided to the selected MEPM-V to allow the selected MEPM-V to send a configuration request to the MEP based on the MEC configuration information.

6. The wireless communication method according to claim 1, wherein, The orchestrator node is configured to receive the VNF instance information from the MEC system portal.

7. An orchestrator node, comprising: Communication unit; as well as A processor configured to execute the wireless communication method according to any one of claims 1 to 6.

8. A computer program product comprising computer-readable program medium code stored thereon, the computer-readable program medium code, when executed by a processor, causing the processor to perform the wireless communication method according to any one of claims 1 to 6.

Images