GPON PPPoE Configuration via OMCI Object Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing GPON system cannot support accessing in a manner of PPPoE dial-up, limiting its application and service development.
Innovation Solution
A PPPoE configuration method is implemented in the GPON system, where the OLT instructs the ONU to create or delete a PPPoE management object instance and associate it with an IP host config data management object instance, enabling or disabling the PPPoE function switch, and modifying PPPoE dial-up parameters, thus supporting PPPoE dial-up access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the GPON system uses only static or DHCP configuration modes for IP address allocation, then the system can be implemented with existing OMCI standards, but the system cannot support PPPoE dial-up access mode
Solution Approach 1:
The patent segments the IP configuration functionality by creating a separate PPPoE management object instance distinct from the existing IP host config data management object. This segmentation allows PPPoE dial-up access to be supported as an independent configuration mode without interfering with existing static or DHCP modes, thereby improving adaptability while maintaining manageable complexity through modular object design.
Solution Approach 2:
The patent implements nesting by associating the PPPoE management object instance with the IP host config data management object instance through identifier matching. The PPPoE object is nested within the existing OMCI framework structure, allowing it to leverage existing management mechanisms while providing additional functionality. This nested approach enables PPPoE support without requiring a complete redesign of the configuration system.
2Adaptability or versatility
If the OLT configures IP host config data ME through OMCI with only static or DHCP modes, then the configuration can be managed through existing mechanisms, but the application scope of GPON system is limited
Solution Approach 1:
The patent enhances the universality of the OMCI configuration system by making the IP host config data management object multi-functional. By adding the PPPoE function switch and supporting multiple access modes (static, DHCP, and PPPoE dial-up) within the same configuration framework, the system can serve diverse service requirements without requiring separate management mechanisms for each access mode.
Solution Approach 2:
The patent implements preliminary action by pre-configuring the PPPoE management object instance and its associated parameters (user name, password, service ID, VLAN ID, etc.) in advance through OMCI messages from the OLT to the ONU. This allows the PPPoE dial-up functionality to be ready and available before actual user access attempts, ensuring complete configuration information is available and eliminating the need for dynamic configuration during access operations.
3Adaptability or versatility
If a PPPoE management object instance is created and associated with IP host config data, then PPPoE dial-up access is enabled, but the system requires additional configuration parameters and management overhead
Solution Approach 1:
The patent extracts PPPoE-specific configuration parameters (user name, password, service ID, VLAN ID, etc.) from the general IP configuration context and places them in a dedicated PPPoE management object instance. This extraction allows PPPoE configuration to be handled independently with its own set of parameters, reducing the complexity burden on the general IP configuration system while enabling comprehensive PPPoE functionality.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
The disclosure discloses a Point-to-Point Protocol over Ethernet (PPPOE) configuration method for a Gigabit-Capable Passive Optical Network (GPON) system. The method comprises: an Optical Line Terminal (OLT) instructing an Optical Network Unit (ONU) to create or delete a PPPoE management object instance and associate the PPPoE management object instance with an IP host config data management object instance; and the ONU creating the PPPoE management object instance according to the creation instruction from the OLT, and turning on a PPPoE function switch in the IP host config data management object instance; or the ONU deleting the PPPoE management object instance according to the deletion instruction from the OLT, and turning off the PPPoE function switch in the IP host config data management object instance. The disclosure also discloses a GPON system. With the disclosure, the problem that the existing GPON system cannot support accessing in a manner of PPPoE dial-up is solved, and the PPPoE scenario requirements are met.