Virtual Network Abstraction via Unified ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network architectures using multiple-level virtualization with MPLS, IGP, and VPN IDs complicate network abstraction and switching, making it difficult to manage forwarding tables and traffic handling across multiple domains.
Innovation Solution
A method utilizing a single network identifier (ID) to abstract and switch virtual networks, where a network controller determines a virtual network topology and assigns a virtual network ID to define a single forwarding domain across a physical network, enabling nodes to identify and forward traffic between end clients within this domain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If multiple-level network abstraction with multiple IDs (VPN ID, IGP MT ID, MPLS MT ID) is used to distinguish different virtual networks, then virtual network identification and routing capability is improved, but network architecture complexity and switching difficulty increases
Solution Approach 1:
The patent merges multiple separate ID systems (VPN ID, IGP MT ID, MPLS MT ID) into a unified Virtual Network ID (VNID) system. Each VNID uniquely identifies a virtual network and its associated forwarding domain, eliminating the need for multiple hierarchical ID layers and their corresponding mapping tables, thus reducing network architecture complexity while maintaining virtual network identification capability.
Solution Approach 2:
The Virtual Network ID serves multiple functions simultaneously: it identifies the virtual network, defines the forwarding domain, and enables traffic classification. This multi-functional ID system replaces the previous multi-ID system where each ID had a specific function, simplifying the overall network abstraction mechanism.
2Reliability
If multiple-level virtualization with separate forwarding domains for each virtual network is implemented, then traffic isolation and security between virtual networks is improved, but forwarding table management and traffic handling complexity increases
Solution Approach 1:
The patent combines multiple separate forwarding domains into a single unified forwarding domain that is shared across all virtual networks. The Virtual Network ID acts as a classifier to distinguish traffic belonging to different virtual networks within this shared domain, eliminating the need for separate forwarding tables for each virtual network and simplifying forwarding table management while maintaining traffic isolation through VNID-based classification.
3Device complexity
If a single Virtual Network ID is used to define a single forwarding domain across the physical network, then network architecture complexity is reduced, but the ability to distinguish different virtual networks within the same forwarding domain must be achieved through alternative means
Solution Approach 1:
The patent introduces the Virtual Network ID as an intermediary classification field that sits between the physical network infrastructure and the virtual network services. The VNID is inserted into packet headers (e.g., as a VLAN tag or MPLS label) and used by network nodes to classify and forward traffic to the appropriate virtual network, enabling precise virtual network distinction within the unified forwarding domain without requiring multiple IDs.
Data Source
AI summary
Embodiments are provided herein to enable single level network abstraction for a service across one or more domains. The embodiments use a single network ID to identify a service and a corresponding virtual network topology across any number of domains at a physical network. A virtual network topology can be abstracted for each service, based on the physical underlying network topology. A network controller determines, for a service, the virtual network topology within a physical network, and binds the service to the virtual network topology via a virtual network ID, which defines a single forwarding domain of the virtual network topology across the physical network. The virtual network ID is then indicated to the nodes of the virtual network topology, thus enabling the nodes to identify and forward traffic for the service, within the single forwarding domain, between end clients from edge to edge of the physical network.