IP Library Granted Patent US 11,405,798
Granted Patent B2
US 11,405,798 · App. 16/499,044 · Granted Aug 2, 2022

Management of gNB in network functions virtualization framework

Inventors: Yizhi Yao (Chandler, AZ); Joey Chou (Scottsdale, AZ)
Assignee: Apple Inc.
H04W16/18G06F9/45537G06F9/45558H04L41/0806H04L41/0816H04L41/5003H04L41/5054H04W4/50H04W24/02G06F2009/45562G06F2009/45595H04W84/02H04W88/08H04W88/18H04W92/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,405,798
App. No.
16/499,044
Granted
Aug 2, 2022
Kind
B2
Abstract

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.

Claims (40)

1. An apparatus comprising:

at least one processor configured to cause a network manager (NM) to:

request a network functions virtualization orchestrator (NFVO) to instantiate a network service (NS); and

request the NFVO via an 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.

2. The apparatus of claim 1 , wherein the NS update request includes a parameter that specifies information on the PNF when the NS update request is to add a PNF.

3. The apparatus of claim 1 , wherein when the NS update request is to remove the PNF, the NS update request includes a parameter that specifies an identifier of PNF descriptor (PNFD) information relating to the PNF.

4. The apparatus of claim 1 , wherein when the NS update request is to replace the 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.

5. The apparatus of claim 1 , wherein the at least one processor is further configured 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.

6. The apparatus of claim 1 , wherein the NFVO is configured to create an NS identifier for the NS and send the NS identifier to the NM.

7. The apparatus of claim 1 , wherein the at least one processor is further configured to request the NFVO to instantiate the NS such that it includes instantiation of a virtualized central unit (CU) for base station (BS) and deployment of one or more non-virtualized distributed units (DUs) for the BS.

8. The apparatus of claim 7 , wherein the BS is implemented as a network function (NF) that is realized by a virtual network function (VNF) or virtual network function component (VNFC) and the PNF or a physical network function component (PNFC).

9. The apparatus of claim 7 , wherein the NFVO uses a network service descriptor (NSD) received from the NM as a template to instantiate the NS.

10. A method, comprising:

by a network manager (NM):

requesting a network functions virtualization orchestrator (NFVO) to instantiate a network service (NS); and

requesting the NFVO via an 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.

11. The method of claim 10 , wherein the NS update request includes a parameter that specifies information on the PNF when the NS update request is to add a PNF.

12. The method of claim 10 , 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.

13. The method of claim 10 , further comprising:

using 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.

14. The method of claim 10 , wherein the NFVO is configured to create an NS identifier for the NS and send the NS identifier to the NM.

15. The method of claim 10 , further comprising:

requesting the NFVO to instantiate the NS such that it includes instantiation of a virtualized central unit (CU) for base station (BS) and deployment of one or more non-virtualized distributed units (DUs) for the BS.

16. The method of claim 15 , wherein the BS is implemented as a network function (NF) that is realized by a virtual network function (VNF) or virtual network function component (VNFC) and the PNF or a physical network function component (PNFC).

17. The method of claim 15 , wherein the NFVO uses a network service descriptor (NSD) received from the NM as a template to instantiate the NS.

18. A network manager (NM), comprising:

wireless communication circuitry; and

at least one processor coupled to the wireless communication circuitry and configured to cause the NM to:

request a network functions virtualization orchestrator (NFVO) to instantiate a network service (NS); and

request the NFVO via an 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 network manager 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 network manager of claim 18 , 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.

21. The network manager 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.

22. The network manager of claim 18 , wherein the NFVO is configured to:

create an NS identifier for the NS and send the NS identifier to the NM.

23. The network manager of claim 18 , wherein the at least one processor is further configured to cause the NM to:

request the NFVO to instantiate the NS such that it includes instantiation of a virtualized central unit (CU) for base station (BS) and deployment of one or more non-virtualized distributed units (DUs) for the BS.

24. The network manager of claim 23 , wherein the BS is implemented as a network function (NF) that is realized by a virtual network function (VNF) or virtual network function component (VNFC) and the PNF or a physical network function component (PNFC).

25. The network manager of claim 23 , wherein the NFVO uses a network service descriptor (NSD) received from the NM as a template to instantiate the NS.

Assignments (3)
CONFIRMATORY ASSIGNMENT Recorded Mar 30, 2023
From: INTEL CORP.
To: APPLE INC.
Reel/Frame 063190/0660 →
CONFIRMATORY ASSIGNMENT Recorded Aug 11, 2020
From: INTEL IP CORPORATION
To: INTEL CORPORATION
Reel/Frame 053455/0489 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2020
From: INTEL CORPORATION
To: APPLE INC.
Reel/Frame 053065/0418 →
Cited By (2)
US 12,273,938 US 12,625,718