Interworking of legacy appliances in virtualized networks

Patent metadata

Field	Value
Publication number	US-11818008-B2
Application number	US-202217945455-A
Country	US
Kind code	B2
Filing date	Sep 15, 2022
Priority date	Sep 27, 2017
Publication date	Nov 14, 2023
Grant date	Nov 14, 2023

Abstract

A computing apparatus, including: a hardware platform; and an interworking broker function (IBF) hosted on the hardware platform, the IBF including a translation driver (TD) associated with a legacy network appliance lacking native interoperability with an orchestrator, the IBF configured to: receive from the orchestrator a network function provisioning or configuration command for the legacy network appliance; operate the TD to translate the command to a format consumable by the legacy network appliance; and forward the command to the legacy network appliance.

First claim

What is claimed is:

1. A non-transitory computer-readable memory storing instructions for being executed by at least one machine, the at least one machine to be associated with server system hardware, the server system hardware being for use in association with network functions, the network functions to be provided, at least in part, via network devices, the server system hardware to be associated with a management and orchestration (MANO) stack, the MANO stack to be associated with an Openstack-compatible virtual infrastructure manager (VIM), the instructions, when executed by the at least one machine, resulting in the server system hardware being configured for performance of operations comprising:
obtaining, via simple network management protocol (SNMP), data from the network devices, the data being for use by at least one virtual machine (VM) instance in generating identifying information related to (1) existence of the network functions and/or network devices and (2) configuration of the network functions and/or network devices;
obtaining, via at least one command line interface request, other data from at least certain of the network devices for use in generating the identifying information; and
dynamically creating and/or terminating at least one network function-related instance that is for use in providing at least one of the network functions;
wherein:
the at least one VM instance is associated with the VIM and/or the MANO stack;
the identifying information is for being provided to the MANO stack via an application programming interface (API);
the server system hardware is configurable to comprise at least one accelerator;
the network devices comprise one or more virtual machines to be executed using physical computer hardware;
the network functions are configurable to comprise at least one virtual network function associated with a telecommunications network function virtualization infrastructure;
the at least one virtual network function is configurable to implement, at least in part, a session border controller for use in association with voice over Internet Protocol (VOIP) communication;
the network functions are also configurable to implement, at least in part, one or more of:
a firewall; and/or
network address translation; and

the at least one network function-related instance is:
comprised in at least one stack that is associated with the VIM; and
to be implemented via at least one container.

2. The non-transitory computer-readable memory of claim 1 , wherein:
the server system hardware is for use with at least one switching and/or routing fabric; and
the at least one switching and/or routing fabric is configurable for use in network traffic communication (1) to and from at least one wide area network, and/or (2) in a data center.

3. The non-transitory computer-readable memory of claim 2 , wherein:
the MANO stack and/or VIM are to generate, based upon the identifying information, one or more management and/or configuration requests associated with the network devices.

4. A method implemented using server system hardware, the server system hardware being for use in association with network functions, the network functions to be provided, at least in part, via network devices, the server system hardware to be associated with a management and orchestration (MANO) stack, the MANO stack to be associated with an Openstack-compatible virtual infrastructure manager (VIM), the method comprising:
obtaining, via simple network management protocol (SNMP), data from the network devices, the data being for use by at least one virtual machine (VM) instance in generating identifying information related to (1) existence of the network functions and/or network devices and (2) configuration of the network functions and/or network devices;
obtaining, via at least one command line interface request, other data from at least certain of the network devices for use in generating the identifying information; and
dynamically creating and/or terminating at least one network function-related instance that is for use in providing at least one of the network functions;
wherein:
the at least one VM instance is associated with the VIM and/or the MANO stack;
the identifying information is for being provided to the MANO stack via an application programming interface (API);
the server system hardware is configurable to comprise at least one accelerator;
the network devices comprise one or more virtual machines to be executed using physical computer hardware;
the network functions are configurable to comprise at least one virtual network function associated with a telecommunications network function virtualization infrastructure;
the at least one virtual network function is configurable to implement, at least in part, a session border controller for use in association with voice over Internet Protocol (VOIP) communication;
the network functions are also configurable to implement, at least in part, one or more of:
a firewall; and/or
network address translation; and

the at least one network function-related instance is:
comprised in at least one stack that is associated with the VIM; and
to be implemented via at least one container.

5. The method of claim 4 , wherein:
the server system hardware is for use with at least one switching and/or routing fabric; and
the at least one switching and/or routing fabric is configurable for use in network traffic communication (1) to and from at least one wide area network, and/or (2) in a data center.

6. The method of claim 5 , wherein:
the MANO stack and/or VIM are to generate, based upon the identifying information, one or more management and/or configuration requests associated with the network devices.

7. A server system hardware for use in association with network functions, the network functions to be provided, at least in part, via network devices, the server system hardware to be associated with a management and orchestration (MANO) stack, the MANO stack to be associated with an Openstack-compatible virtual infrastructure manager (VIM), the server system hardware comprising:
at least one server node to obtain, via simple network management protocol (SNMP), data from the network devices, the data being for use by at least one virtual machine (VM) instance in generating identifying information related to (1) existence of the network functions and/or network devices and (2) configuration of the network functions and/or network devices; and
at least one other server node for use in dynamically creating and/or terminating at least one network function-related instance that is for use in providing at least one of the network functions;
wherein:
the server system hardware is also to obtain, via at least one command line interface request, other data from at least certain of the network devices for use in generating the identifying information;
the at least one VM instance is associated with the VIM and/or the MANO stack;
the identifying information is for being provided to the MANO stack via an application programming interface (API);
the server system hardware is configurable to comprise at least one accelerator;
the network devices comprise one or more virtual machines to be executed using physical computer hardware;
the network functions are configurable to comprise at least one virtual network function associated with a telecommunications network function virtualization infrastructure;
the at least one virtual network function is configurable to implement, at least in part, a session border controller for use in association with voice over Internet Protocol (VOIP) communication;
the network functions are also configurable to implement, at least in part, one or more of:
a firewall; an

Assignees

• Intel Corp

Inventors

• Browne John J
• Verrall Timothy
• Tahhan Maryam
• Mcgrath Michael J
• Harte Sean
• Devey Kevin
• Kenny Jonathan
• Macnamara Christopher

Classifications

• H04L41/0896

  Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title

• H04L41/0873 Primary

  Checking configuration conflicts between network elements · CPC title

• H04L41/0897

  by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities · CPC title

• H04L41/0895 Primary

  Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title

• H04L41/0806

  for initial configuration or provisioning, e.g. plug-and-play · CPC title