# US 11,442,791 B2 · Multiple server-architecture cluster for providing a virtual network function

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,442,791 B2
- Document ID: US11442791B2
- Status: Granted
- Kind: B2
- Application number: 17/002,503
- Filed: 2020-08-25
- Published: 2020-12-10
- Granted: 2022-09-13
- Earliest claimed: 2018-06-01
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Enqi Xu; Jingjing Zhang; Zhisai Chen; Wanhong Meng; Tiancheng Jing
- Web page: https://patentgrep.com/patent/US11442791B2

## CPC

- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/5072: {Grid computing}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates}
- H04L 41/5051: Service on demand, e.g. definition and deployment of services in real time
- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- H04L 41/5096: {wherein the managed service relates to distributed or central networked applications}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Provided is a method and a network apparatus in a cloud infrastructure. The network apparatus includes a processor, and a memory coupled to the processor, the memory for storing computer instructions that, when executed by the processor, cause the processor to generate a resource abstraction layer relating a network cluster including a first server architecture with a first resource set and a second server architecture with a second resource set, to generate an orchestration layer configured to receive a packet flow request and, in response to the packet flow request, schedule virtual network resources based on the resource abstraction layer for servicing a packet flow, and to deploy the virtual network resources to receive and service the packet flow.

## Claims

### Claim 1

A network apparatus in a cloud infrastructure, comprising:
a memory storing instructions; and
at least one processor in communication with the memory, the at least one processor configured, upon execution of the instructions, to perform the following steps:
generate a resource abstraction layer relating a network cluster including a first server architecture with a first resource set and a second server architecture with a second resource set, the first server architecture providing network functions having a higher throughput characteristic than the network functions provided by the second server architecture, the resource abstraction layer including a management and network orchestration parameter configured to provide a deployment template for virtual network resources to interconnect virtual network functions, and the network cluster scalable without utilizing a network card;
generate an orchestration layer configured to receive a packet flow request and, in response to the packet flow request, schedule the virtual network resources based on the resource abstraction layer for servicing a packet flow; and
deploy the virtual network resources to receive and service the packet flow.

### Claim 2 (depends on 1)

The network apparatus of claim 1, wherein the orchestration layer is further configured to schedule the virtual network resources for a tunnel connection between the first server architecture and the second server architecture for jointly servicing the packet flow.

### Claim 3 (depends on 1)

The network apparatus of claim 1, wherein the first server architecture is configured to service different functions than the second server architecture.

### Claim 4 (depends on 1)

The network apparatus of claim 1, wherein the first server architecture is configured to service at least one of:
a service function chaining (SFC) network function;
a point-to-point protocol over Ethernet (PPPOE) network function;
a link network address translation (NAT) network function; or
a router network function having the higher throughput characteristic and not suitable for offload to the second server architecture.

### Claim 5 (depends on 1)

The network apparatus of claim 1, wherein the second server architecture is configured to service at least one of:
a security network function;
a uniform resource locator (URL) filter network function; or
a parental control network function.

### Claim 6 (depends on 1)

The network apparatus of claim 1, wherein the packet flow request comprises a traffic flow classification for the packet flow.

### Claim 7 (depends on 1)

The network apparatus of claim 1, wherein the network cluster is one of a plurality of network clusters in a stem-leaf configuration to form the cloud infrastructure.

### Claim 8

A method comprising:
generating a resource abstraction layer relating a network cluster including a first server architecture with a first resource set and a second server architecture with a second resource set, the first server architecture providing network functions having a higher throughput characteristic than the network functions provided by the second server architecture, the resource abstraction layer including a management and network orchestration parameter configured to provide a deployment template for virtual network resources to interconnect virtual network functions, and the network cluster scalable without utilizing a network card;
generating an orchestration layer configured to receive a packet flow request and, in response to the packet flow request, scheduling the virtual network resources based on the resource abstraction layer for servicing a packet flow; and
deploying the virtual network resources to receive and service the packet flow.

### Claim 9 (depends on 8)

The method of claim 8, wherein the orchestration layer is further configured to schedule the virtual network resources for a tunnel connection between the first server architecture and the second server architecture for jointly servicing the packet flow.

### Claim 10 (depends on 8)

The method of claim 8, wherein the first server architecture is configured to service different functions than the second server architecture.

### Claim 11 (depends on 8)

The method of claim 8, wherein the first server architecture is configured to service at least one of:
a service function chaining (SFC) network function;
a point-to-point protocol over Ethernet (PPPOE) network function;
a link network address translation (NAT) network function; or
a router network function having the higher throughput characteristic and not suitable for offload to the second server architecture.

### Claim 12 (depends on 8)

The method of claim 8, wherein the second server architecture is configured to service at least one of:
a security network function;
a uniform resource locator (URL) filter network function; or
a parental control network function.

### Claim 13 (depends on 8)

The method of claim 8, wherein the packet flow request comprises a traffic flow classification for the packet flow.

### Claim 14 (depends on 8)

The method of claim 8, wherein the network cluster is one of a plurality of network clusters in a stem-leaf configuration to form a cloud infrastructure.

### Claim 15

A method in a cloud infrastructure, comprising:
generating, by a processor, a resource abstraction layer relating a network cluster including a first server architecture with a first resource set and a second server architecture with a second resource set, the first server architecture providing network functions having a higher throughput characteristic than the network functions provided by the second server architecture, the resource abstraction layer including a management and network orchestration parameter configured to provide a deployment template for virtual network resources to interconnect virtual network functions, and the network cluster scalable without utilizing a network card;
generating, by the processor, an orchestration layer configured to receive a packet flow request and, in response to the packet flow request, scheduling the virtual network resources based on the resource abstraction layer for servicing a packet flow; and
deploying, by the processor, the virtual network resources to receive and service the packet flow.

### Claim 16 (depends on 15)

The method of claim 15, wherein the orchestration layer is further configured to schedule the virtual network resources for a tunnel connection between the first server architecture and the second server architecture for jointly servicing the packet flow.

### Claim 17 (depends on 15)

The method of claim 15, wherein the first server architecture is configured to service different functions than the second server architecture.

### Claim 18 (depends on 15)

The method of claim 15, wherein the first server architecture is configured to service at least one of:
a service function chaining (SFC) network function;
a point-to-point protocol over Ethernet (PPPOE) network function;
a link network address translation (NAT) network function; or
a router network function having the higher throughput characteristic and not suitable for offload to the second server architecture.

### Claim 19 (depends on 15)

The method of claim 15, wherein the second server architecture is configured to service at least one of:
a security network function;
a uniform resource locator (URL) filter network function; or
a parental control network function.

### Claim 20 (depends on 15)

The method of claim 15, wherein the packet flow request comprises a traffic flow classification for the packet flow.