Management of GNB in network functions virtualization framework
Network Functions Virtualization (NFV) abstracts network functions, allowing them to be installed, controlled, and manipulated by software running on standardized compute nodes such as cloud computing platform rather than on dedicated hardware. In a 5G mobile communications network, the base station or gNB may be split into virtualized and non-virtualized network functions (NFs). Described herein are systems and methods for managing such gNBs within the NFV framework.
1. A method, comprising:
by a network functions virtualization orchestrator (NFVO):
receiving, via a network service (NS) update request from an operations support system/business support system (OSS/BSS), a request including a nsInstanceId parameter and an updateType parameter, to remove a physical network function (PNF) part from an NS instance with updateType set to RemovePnf, or add a new PNF part to the NS instance with updateType set to AddPnf, as indicated by parameters in the NS update request.
2. The method of claim 1 , wherein the method further comprises:
implementing a base station as a network function, NF, that is realized by a virtual network function (VNF) or a virtual network function component (VNFC) and the PNF or a physical network function component (PNFC).
3. The method of claim 1 , wherein the method further comprises:
using a network service descriptor (NSD) received from the OSS/BSS as a template to instantiate the NS.
4. The method of claim 3 , wherein the NSD includes a virtual link descriptor (VLD) that includes quality of service (QoS) information for an interface between a virtualized central unit (CU) and a virtualized distributed unit (DU) wherein the QoS information includes a transport bandwidth requirement.
5. The method of claim 1 , wherein the method further comprises:
creating an NS identifier for the NS and sending the NS identifier to the OSS/BSS.
6. The method of claim 1 , wherein, to update the NS as requested by the OSS/BSS, the method further comprises:
removing a PNF part of a base station from the NS instance;
adding a new PNF part of base station to the NS instance; or
replacing a PNF part of a base station in the NS instance.
7. The method of claim 6 , wherein the method further comprises:
adding a PNF part of the base station when adding a PNF part of the base station is indicated by a parameter in the NS update request.
8. The method of claim 7 , wherein the NS update request includes a parameter that specifies information relating to the PNF when the NS update request is to add a PNF.
9. The method of claim 6 , wherein the method further comprises removing a PNF part of the base station when removing a PNF part of the base station is indicated by a parameter in the NS update request.
10. The method of claim 9 , wherein, when the NS update request is to remove a PNF, the NS update request includes a parameter that specifies an identifier of PNF descriptor (PNFD) information relating to the PNF.
11. The method of claim 6 , wherein the method further comprises:
replacing a PNF part of the base station when replacing a PNF part of the base station is indicated by a parameter in the NS update request.
12. The method of claim 11 , wherein, when the NS update request is to replace a PNF, the NS update request includes a parameter that contains information on the PNF to be added and a parameter for the PNF to be replaced.
13. An apparatus, comprising:
at least one processor configured to cause a network functions virtualization orchestrator (NFVO) to:
receive, via a network service (NS) update request from an operations support system/business support system (OSS/BSS), a request including a nsInstanceId parameter and an updateType parameter, to remove a physical network function (PNF) part from an NS instance with updateType set to RemovePnf, or add a new PNF part to the NS instance with updateType set to AddPnf, as indicated by parameters in the NS update request.
14. The apparatus of claim 13 , wherein the at least one processor is further configured to cause the NFVO to:
send, upon request by the OSS/BSS, the OSS/BSS a location where a virtualized network function (VNF) part of a base station is deployed.
15. The apparatus of claim 13 , wherein the at least one processor is further configured to cause the NFVO to:
send, upon request by the OSS/BSS, the OSS/BSS information relating to a location of a virtualized network function (VNF) part of a base station when the VNF is instantiated or migrated to a new location.
16. The apparatus of claim 13 , wherein the at least one processor is further configured to cause the NFVO to:
update, upon receipt of a PNF descriptor (PNFD) updating request from the OSS/BSS, the PNFD that contains information relating to a location of PNF part of a base station; and
on-board, upon receipt of a PNFD on-board request from the OSS/BSS, the PNFD that contains information relating to a location of PNF part of the base station.
17. The apparatus of claim 13 , wherein the at least one processor is further configured to cause the NFVO to:
send, after performing an NS instantiation operation, an NS update operation, a PNFD update operation, or a PNF on-board operation, results of the operation to the OSS/BSS.
18. A non-transitory computer readable storage medium storing program instructions executable by at least one processor of a network manager (NM) wherein the program instructions are executable to cause the NM to:
request a network functions virtualization orchestrator (NFVO) via a network service (NS) update request, including a nsInstanceId parameter and an updateType parameter, to remove a physical network function (PNF) part from an NS instance with updateType set to RemovePnf, or add a new PNF part to the NS instance with updateType set to AddPnf, as indicated by parameters in the NS update request.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the NS update request includes a parameter that specifies information on the PNF when the NS update request is to add a PNF.
20. The non-transitory computer-readable storage medium of claim 18 , wherein the at least one processor is further configured to cause the NM to use a network service descriptor (NSD) which includes a virtual link descriptor (VLD) that includes quality of service (QoS) information for an interface between a virtualized central unit (CU) and a non-virtualized distributed unit (DU) wherein the QoS information includes a transport bandwidth requirement.