Extended VLAN Tagging for Service Instance Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Ethernet network standards, such as IEEE 802.1Q and 802.1ad, are inadequate for handling the increasing number of broadcast domains and service instances in Metro Area Networks (MAN) and Wide Area Networks (WAN), particularly in point-to-point applications, and lack support for tunneling end-user MAC addresses and Frame Check Sums.
Innovation Solution
The introduction of an extended VLAN (E-VLAN) mechanism that differentiates between broadcast domains and service instance domains, using a 20-bit VLAN ID/Service ID field, allows for up to one million service instances and supports MAC tunneling, enabling efficient handling of large numbers of broadcast domains and service instances, and can be used as both a broadcast domain and service instance identifier.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If IEEE 802.1Q VLAN tagging is used to identify broadcast domains and service instances, then standard compatibility is maintained, but the capacity is limited to 4,094 service instances per broadcast domain
Solution Approach 1:
The patent segments the identification space by introducing a hierarchical structure with broadcast domain identifiers and service instance identifiers as separate fields. This segmentation allows the system to support tens of thousands of service instances within a single broadcast domain, overcoming the 4,094 limit of traditional IEEE 802.1Q VLAN tagging while maintaining standard compatibility.
Solution Approach 2:
The patent adds another dimension to the identification space by introducing a 20-bit service instance identifier field in addition to the traditional VLAN identifier. This dimensional expansion transforms the limited 12-bit VLAN space into a much larger addressing space capable of supporting tens of thousands of service instances per broadcast domain.
2Adaptability or versatility
If traditional VLAN tagging is used, then implementation simplicity is maintained, but support for MAC address and Frame Check Sum tunneling is lacking
Solution Approach 1:
The patent implements nesting by encapsulating customer MAC addresses and Frame Check Sums within the extended packet format. The customer data is nested inside a structure that includes the extended VLAN identifier and service instance identifier, allowing tunneling functionality while maintaining a structured and manageable packet format.
Solution Approach 2:
The extended packet format serves multiple functions simultaneously: it identifies broadcast domains, identifies service instances, enables MAC address tunneling, and supports Frame Check Sum tunneling. This multi-functionality achieves the required tunneling capability without proportionally increasing complexity, as all features are integrated into a single unified format.
3Quantity of substance
If the number of broadcast domains exceeds 4K limit, then network scalability is achieved, but existing standards become inadequate
Solution Approach 1:
The patent changes the parameter size for service instance identification from 12 bits to 20 bits, expanding the capacity from 4,094 to over one million service instances per broadcast domain. This parameter change allows the network to scale to tens of thousands of broadcast domains while maintaining compliance with extended versions of the VLAN standards.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
A method of operation for a provider edge device of a core network includes receiving a customer frame from an access network; the customer frame having a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length. The first VLAN tag including a service instance identifier. The service instance identifier of the first VLAN tag is then mapped into a second VLAN tag of a second predetermined bit length greater than the first predetermined bit length. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.