Structured GEM Port ID for GPON Priority Differentiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In GPON networks, existing methods for addressing Ethernet streams using GEM Port IDs struggle with differentiating priorities in downstream directions, leading to asymmetric traffic flows and inefficient mapping table configurations, as they rely on assumptions about priority bits and require pre-configuring all possible priorities.
Innovation Solution
A method where the GEM port ID is structured with a part mapped to layer 2 addressing and another part related to priority, allowing only a configurable number of bits to be copied for priority, enabling dynamic learning and compatibility with various ONT implementations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all possible priorities are pre-configured in the mapping table, then priority differentiation is ensured, but table space is wasted and configuration complexity increases
Solution Approach 1:
The GEM Port ID is segmented into multiple parts: a first part copied from Ethernet frame fields (MAC address/VLAN-ID) and a second part representing priority bits. This segmentation allows the mapping table to store only essential addressing information while priority is handled separately, reducing table space requirements.
Solution Approach 2:
The mapping table configuration becomes dynamic rather than static. Instead of pre-configuring all possible priorities, the system learns and adapts to actual priority usage patterns in the network, configuring only the priorities that are actually needed, thus optimizing table space utilization.
2Reliability
If all possible priorities are pre-configured in the mapping table, then priority differentiation is ensured, but configuration complexity increases
Solution Approach 1:
The system transitions from static pre-configuration to dynamic learning-based configuration. The OLT learns actual priority usage from upstream traffic and automatically configures the mapping table accordingly, eliminating the need for manual pre-configuration of all possible priorities and reducing configuration complexity.
Solution Approach 2:
The mapping table configuration becomes self-service through automatic learning mechanisms. The system monitors upstream traffic, identifies actual priority usage patterns, and automatically configures itself without requiring manual intervention, thereby reducing configuration complexity while maintaining reliability.
3Ease of operation
If priority bits are assumed rather than explicitly structured, then mapping is simplified, but downstream priority differentiation fails
Solution Approach 1:
The GEM Port ID is explicitly segmented into a first part (copied from Ethernet frame) and a second part (priority bits). This explicit structuring ensures that priority information is properly preserved and differentiated in downstream traffic, eliminating the failures associated with assuming priority bits.
Solution Approach 2:
The system changes the parameter structure of the GEM Port ID to explicitly include priority bits as a separate component. This parameter change ensures that priority information is maintained throughout the mapping process, enabling reliable priority differentiation in downstream directions while maintaining mapping simplicity through structured copying.
Data Source
Figure 1
Figure 2
AI summary
The present invention relates to a method for addressing Ethernet streams (12) by means of a structured GEM Port ID (9), wherein an implementation in an OLT (13) as part of a GPON network (14) is provided. In a GPON network (14), between an ONT (15) and the OLT (13), an Ethernet frame (11) is transported, the Ethernet frame (11) is encapsulated in a GEM layer and the Ethernet frame (11) is addressed in a GEM header (8), through a GEM port ID (9), characterized in that, the GEM port ID (9) is structured, wherein a part is mapped to the layer 2 addressing (17) and wherein another part relates to a priority (19). In upstream direction on the OLT (13), just a part of the GEM port ID (9) in a mapping table (4) is saved, whereas in downstream direction, by means of a Source-MAC and/or a VLAN-ID, a corresponding part of the GEM port ID (9) is read out from the mapping table (4).