Forwarding Microchip NFV Backplane Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network functions virtualization (NFV) backplanes in cloud computing require additional virtualization components like virtual switches or I/O interfaces, leading to complexity, misconfiguration risks, and transparency issues for users and administrators.

Innovation Solution

A forwarding microchip is configured to serve as an NFV backplane, eliminating the need for additional virtualization components by using virtual ports for packet routing and switching, thereby simplifying the implementation and operation of NFV backplanes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If additional virtualization components like virtual switches or I/O interfaces are used to implement NFV backplane, then the NFV backplane functionality can be achieved, but the system complexity increases and misconfiguration risks arise

Engineering Contradiction:
ImproveNFV backplane functionalityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the NFV backplane functionality directly into the forwarding microchip, eliminating the need for separate virtualization components like virtual switches or I/O interfaces. The forwarding microchip is configured to perform both traditional packet forwarding and NFV backplane functions, including service chaining and virtual network function connectivity, thereby reducing system complexity while maintaining full NFV functionality.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The forwarding microchip is designed with multi-functionality to serve dual purposes: traditional packet forwarding and NFV backplane operations. By configuring the existing forwarding microchip to handle both roles, the patent eliminates the need for dedicated virtualization components, reducing complexity while preserving reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If additional virtualization components are deployed for NFV backplane, then NFV functionality is supported, but misconfiguration risks and transparency issues increase

Engineering Contradiction:
ImproveNFV functionalityVSAvoidmisconfiguration risks
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

By combining NFV backplane functionality into the forwarding microchip, the patent creates a unified, transparent architecture where NFV operations are handled seamlessly by the existing forwarding infrastructure. This integration eliminates the configuration complexity associated with separate virtualization components while maintaining full NFV adaptability and versatility.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3716551B1Network functions virtualization (NFV) backplane on forwarding microchip
Publication Date: 2024.08.07 JUNIPER NETWORKS INC
  • EP3716551B1 patent drawingFigure 1
  • EP3716551B1 patent drawingFigure 2
  • EP3716551B1 patent drawingFigure 3

AI summary

Techniques are disclosed for using a forwarding microchip to implement a network functions virtualization (NFV) backplane within a network device. In one example, processing circuitry of a forwarding microchip establishes a respective logical connection between each of a plurality of virtual ports of the forwarding microchip and each of a plurality of virtual ports configured for respective software-implemented virtual network functions (VNFs) executing on the network device. The processing circuitry receives packets via one or more physical ports of the forwarding microchip and forwards, using the logical connections between each of the plurality of virtual ports of the forwarding microchip and each of the plurality of virtual ports configured for the respective software-implemented VNFs, the packets to a Network Interface Controller (NIC) for forwarding to the plurality of virtual ports configured for the respective software-implemented VNFs.