IP Library Granted Patent US 11,656,890
Granted Patent B2
US 11,656,890 · App. 16/377,961 · Granted May 23, 2023

Utilizing physical systems and virtual systems for virtual network functions

Inventor: Paul Miller (Derry, NH)
Assignee: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
G06F9/45558G06F9/5077H04L12/4641H04L41/0896G06F2009/4557G06F2009/45595H04L43/0817H04L43/16H04L45/306
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,656,890
App. No.
16/377,961
Granted
May 23, 2023
Kind
B2
Abstract

A method includes provisioning a first Virtual Network Function (VNF) component on a first virtual machine, the first virtual machine being supported by a first physical computing system, provisioning a second VNF component directly on a second physical computing system, and using, within a telecommunications network, a VNF that includes both the first VNF component running on the first virtual machine and the second VNF component running directly on the second physical computing system. The method further includes, with a VNF manager, determining that a third VNF component should be provisioned, and in response to determining that the third VNF component is capable of utilizing a hardware accelerator associated with a third physical computing system, implementing the third VNF component on the third physical computing system.

Claims (32)

1. A method comprising:

provisioning a first Virtual Network Function (VNF) component on a first virtual machine, the first virtual machine being supported by a first physical computing system;

provisioning a second VNF component directly on a second physical computing system;

using, within a telecommunications network, a VNF that includes both the first VNF component running on the first virtual machine and the second VNF component running directly on the second physical computing system;

with a VNF manager, in response to determining that a third VNF component is capable of utilizing a hardware accelerator associated with a third physical computing system, implementing the third VNF component to run on a host operating system providing direct access to the third physical computing system;

with the VNF manager, determining that a fourth VNF component should be provisioned; and

with the VNF manager, determining that the fourth VNF component does not require use of the hardware accelerator, implementing the fourth VNF component on the first virtual machine.

2. The method of claim 1 , wherein the hardware accelerator comprises one of: Data Plane Development Kit (DPDK) and Media Software Development Kit (MSDK).

3. The method of claim 1 , wherein the hardware accelerator comprises a technology that allows for faster digital signal processing.

4. The method of claim 1 , wherein the second VNF component comprises functions associated with the hardware accelerator.

5. The method of claim 1 , wherein the second VNF component may be allocated or de-allocated dynamically.

6. The method of claim 1 , further comprising, in response to determining that the second VNF component will have improved performance without use of a hypervisor, implementing the second VNF component directly on the second physical computing system.

7. The method of claim 1 , wherein the VNF comprises a virtualization of one of: a Session Border Controller (SBC), an Internet Protocol (IP) Multimedia Subsystem (IMS) network function, and a telephony application server network function.

8. The method of claim 1 , further comprising, through use of a database that includes information about the third VNF component, determining whether the third VNF component is to be provisioned on either the first virtual machine or directly on the third physical computing machine.

9. A method comprising,

with a Virtual Network Function (VNF) manager, sending a first instruction to a Network Function Virtualization Infrastructure (NFVI) to use a first virtual machine to provide a first VNF component, the first virtual machine being supported by at least one of a plurality of physical computing systems; and

with the VNF manager, sending a second instruction to the VNFI to use one of the plurality of physical computing systems to directly support a second VNF component, the first VNF component and the second VNF component both being used to provide a VNF;

in response to a change in demand for the VNF, determining that a third VNF component should be provisioned;

in response to determining that the third VNF component is capable of utilizing a hardware accelerator, instructing the NFVI to implement the third VNF component to run on a host operating system providing direct access to an available one of the plurality of physical computing systems;

in response to a change in demand for the VNF, determining that a fourth VNF component should be provisioned; and

in response to determining that the fourth VNF component will have improved performance without use of a hypervisor, implementing the fourth VNF component directly on the available one of the plurality of physical computing systems.

10. The method of claim 9 , wherein the one of the plurality of physical computing systems to directly support the second VNF component is provisioned using Metal as a Service (MaaS).

11. The method of claim 9 , wherein the available one of the plurality of physical computing systems comprises the hardware accelerator.

12. A system comprising:

a processor; and

a memory comprising machine readable instructions that when executed by the processor, cause the system to:

with a Virtual Network Function (VNF) manager, send a first instruction to a Network Function Virtualization Infrastructure (NFVI) to use a first virtual machine to provide a first VNF component, the first virtual machine being supported by at least one of a plurality of physical computing systems; and

with the VNF manager, send a second instruction to the VNFI to use one of the plurality of physical computing systems to directly support a second VNF component, the first VNF component and the second VNF component both being used to provide a VNF;

in response to a change in demand for the VNF, determine that a third VNF component should be provisioned; and

in response to determining that the third VNF component is capable of utilizing a hardware accelerator, instruct the NFVI to implement the third VNF component to run on a host operating system providing direct access to an available one of the plurality of physical computing systems.

13. The system of claim 12 , wherein the system is further to determine, in response to a change in demand for the VNF, that a fourth VNF component should be provisioned.

14. The system of claim 13 , wherein the system is further configured to, in response to determining that the fourth VNF component will have improved performance without use of a hypervisor, implement the fourth VNF component directly on the available one of the plurality of physical computing systems.

Assignments (3)
SHORT-FORM PATENTS SECURITY AGREEMENT Recorded Sep 5, 2024
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 068857/0290 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 22, 2022
From: MILLER, PAUL
To: GENBAND US LLC
Reel/Frame 059342/0707 →
MERGER Recorded Mar 22, 2022
From: GENBAND US LLC
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
Reel/Frame 059342/0752 →