PON system ONU anti-collision management method and device
By differentiating between EPON and GPON processes for managing ONU resources, saving mapping relationships, and dynamically handling conflicts, the problem of disordered allocation after ONU restart in PON systems is solved, thereby improving system stability and resource utilization.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-10
- Publication Date
- 2026-03-13
Smart Images

Figure CN121665145A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of PON management technology, specifically to a method and device for anti-collision management of ONUs in a PON system. Background Technology
[0002] In current PON technology scenarios involving mixed 1G / 10G / 50G connections, when a single board or the system restarts, the PON chip reassigns LLIDs (Logical Link Identifiers) to reactivated EPON ONUs, and Alloc-IDs (Allocation Identifiers) and GEMPORTs (GPON Encapsulation Mode Ports, the smallest unit of data flow in GPON) to reactivated GPON ONUs. This disordered allocation triggers problems present in the 1GPON and 10G PON eras. Specifically, due to single board or system restarts, the disordered allocation by the PON chip causes changes in the LLIDs, Alloc-IDs, and GEMPORTs acquired by the same ONU. Even after the ONU's online card is reassigned, the resource information from before the line card restart is retained. This leads to ONU conflicts after a single board restart, causing ONUs to fail to connect or repeatedly connect and disconnect. Furthermore, this problem will persist in next-generation PON systems. Summary of the Invention
[0003] This application provides a method and device for anti-collision management of ONUs in a PON system, which can solve the technical problems of ONU mutual conflict, repeated online or inability to go online in the prior art.
[0004] In a first aspect, embodiments of this application provide a method for anti-collision management of an ONU in a PON system, the method comprising: Differentiate between EPON and GPON processes based on ONU type; In the EPON process, the mapping relationship between MAC and LLID under the PON port is saved, and the configuration is issued based on the mapping relationship after the system restarts; In the GPON process, Alloc ID and GEMPORT resources are divided into private resources and public resources. Resources are allocated based on ONUID, and configurations are issued based on the mapping relationship between ONUID and resources after system restart. During the deployment of ONU, conflicts are dynamically handled based on mapping relationships, and the saved mapping relationships are updated regularly.
[0005] In conjunction with the first aspect, in one implementation, the step of saving the mapping relationship between the MAC and LLID under the PON port in the EPON process includes: Record the mapping between MAC and LLID when the ONU comes online; During system operation, the mapping relationship is cyclically overwritten and saved at fixed intervals.
[0006] In conjunction with the first aspect, in one implementation, the step of issuing configurations based on the mapping relationship after a system restart during the EPON process includes: If the OLT or line card restarts, and initialization is complete but the light is not yet switched on, the latest saved mapping relationship will be sent to the PON chip.
[0007] In conjunction with the first aspect, in one implementation, during the ONU online process in the EPON process, conflicts are dynamically handled based on mapping relationships, including: If the ONU mapping relationship has not changed, and if the number of ONU mappings on a single PON port is less than or equal to the maximum supported number, ONUs with mapping relationships will be directly brought online, while ONUs without mapping relationships will be assigned LLIDs for online access.
[0008] In conjunction with the first aspect, in one implementation, during the ONU online process in the EPON process, conflicts are dynamically handled based on mapping relationships, including: If the ONU mapping relationship changes, the number of ONU mappings on a single PON port equals the maximum supported number. If all ONUs with mapping relationships are online, all mapping relationships are cleared and reprocessed. If some ONUs with mapping relationships are online, a foolproof mechanism is triggered, which includes dynamically deleting the mapping relationships of offline ONUs.
[0009] In conjunction with the first aspect, in one implementation, during the ONU online process in the EPON process, conflicts are dynamically handled based on mapping relationships, including: If the ONU's LLID is manually modified, clear the mapping relationship before the modification, establish a mapping relationship between the modified MAC and LLID, and re-trigger the ONU online process.
[0010] In conjunction with the first aspect, in one implementation, during the EPON process, when the ONU goes offline, including scenarios such as deauthorization, restart, manual deactivation, and adding to the blacklist, the MAC and LLID mapping relationship of the ONU will not be changed.
[0011] In conjunction with the first aspect, in one implementation, the step of dividing Alloc ID and GEMPORT resources into private and public resources in the GPON process, and allocating resources based on ONUID, includes: Allocate a preset number of private resources to each ONUID. If all private resources are allocated, allocate from public resources and mark the allocated public resources.
[0012] In conjunction with the first aspect, in one implementation, after the deauthorization operation in the GPON process, the resource allocation is cleared while the mapping relationship is retained.
[0013] Secondly, embodiments of this application provide a PON system ONU anti-collision management device, the device comprising: The judgment module is used to distinguish between EPON and GPON processes based on the ONU type. The EPON process module is used to save the mapping relationship between MAC and LLID under PON port in the EPON process, and to issue configuration based on the mapping relationship after system restart; The GPON process module is used to divide Alloc ID and GEMPORT resources into private and public resources in the GPON process, allocate resources according to ONUID, and issue configurations based on the mapping relationship between ONUID and resources after system restart. The management module is used to dynamically handle conflicts based on mapping relationships during the ONU go-live process and to periodically update the saved mapping relationships.
[0014] The beneficial effects of the technical solutions provided in this application include: This application differentiates the anti-collision management process into EPON and GPON processes based on ONU type. In the EPON process, the mapping relationship between ONU MAC and ONU LLID under the OLT PON port is stored, and configurations are issued based on this mapping relationship after system restart, ensuring that the PON chip directly uses the pre-configured mapping and avoiding disordered allocation. In the GPON process, Alloc ID and GEMPORT resources are divided into private and public resources, and resources are allocated based on ONU ID to optimize resource allocation and improve resource utilization. During ONU online deployment, conflicts are dynamically handled based on the mapping relationship, and the stored mapping relationship is updated periodically. This application employs dedicated anti-collision mechanisms for different protocol types, completely resolving resource conflicts in EPON and GPON hybrid deployments, and solving the technical problems of ONU mutual conflicts, repeated online deployments, or inability to go online existing in the prior art. This application provides an effective solution to the ONU resource conflict problem that occurs in 50G PON hybrid scenarios, improving system stability and customer experience. Attached Figure Description
[0015] Figure 1 This is a schematic diagram of the anti-collision management method for the ONU in a PON system according to an embodiment of this application; Figure 2 This is a schematic diagram illustrating the process of saving ONU information for EPON type in an embodiment of this application; Figure 3This is a schematic diagram of the ONU initialization process for the EPON type in this application embodiment; Figure 4 This is a schematic diagram of the ONU activation process for the EPON type in this application embodiment; Figure 5 This is a schematic diagram of the ONU activation process for the GPON type in this application embodiment. Detailed Implementation
[0016] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.
[0017] First, some of the technical terms used in this application will be explained to help those skilled in the art understand this application.
[0018] PON: Passive Optical Network.
[0019] EPON: Ethernet Passive Optical Network.
[0020] ONU: Optical Network Unit.
[0021] LLID: Logical Link Identifier.
[0022] GPON: Gigabit Passive Optical Network.
[0023] Alloc ID: Allocation Identifier, a unique identifier assigned to each T-CONT by the OLT in GPON technology.
[0024] GEMPORT: GPON Encapsulation Mode Port, the smallest unit of data flow in GPON.
[0025] OLT: Optical Line Terminal.
[0026] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0027] In a first aspect, this application provides an embodiment of a PON system ONU anti-collision management method, which includes the following steps: The EPON and GPON processes are distinguished based on the ONU type. Specifically, during the PON OLT initialization and activation process, the OLT divides the anti-collision management process into GPON and EPON processes according to the ONU type.
[0028] In the EPON process, the mapping relationship between ONU MAC and ONU LLID under the OLT PON port (hereinafter referred to as the MAC and LLID mapping relationship) is saved, and the configuration is issued based on the mapping relationship after the system restarts.
[0029] In the GPON process, Alloc ID and GEMPORT resources are divided into private resources and public resources. Resources are allocated based on ONUID, and configurations are issued based on the mapping relationship between ONUID and resources after system restart.
[0030] During ONU deployment, conflicts are dynamically handled based on mapping relationships, and the saved mapping relationships are updated periodically. These mapping relationships include the mapping between MAC addresses and LLIDs under the PON port in the EPON process; and the mapping between ONUIDs and assigned Alloc IDs and GEMPORTs in the GPON process.
[0031] In this embodiment, the EPON process and GPON process are distinguished according to the ONU type, and anti-conflict management is implemented according to different processes to ensure that the allocation method remains consistent before and after the OLT or line card restarts, thereby eliminating the occurrence of ONU conflicts in principle. During normal operation, the relevant configuration is updated and managed to improve the maintainability and compatibility of the system.
[0032] In one embodiment, for the EPON process, the mapping relationship between MAC and LLID is recorded when the ONU comes online; during system operation, the mapping relationship is cyclically overwritten and saved at fixed intervals.
[0033] Furthermore, based on the LLID assigned when the ONU first comes online, the mapping relationship between the MAC and LLID under the PON port is updated and saved in a file at fixed intervals. Specifically, PON+MAC+LLID information can be saved through mapping table entries, and the number of times to save can be set. In this embodiment, information about the EPONONUs that have come online with PON+MAC+LLID is saved every 24 hours. The saved information is a cyclic overwrite of the last ten historical information entries, with the overwrite position determined by the timestamp of the saved information, and the latest information overwriting the oldest information in the ten entries. After the information update is completed, it is written to a file for saving. In this embodiment, by dynamically updating the mapping table entries of ONU information and recording historical online information, it is easier for maintenance personnel to troubleshoot and locate problems, thus improving the maintainability of the equipment.
[0034] like Figure 2 As shown, a specific process for saving ONU information is provided, including the following steps: S101: Determine if 24 hours have been reached. If yes, proceed to S102; otherwise, end the process.
[0035] S102: Obtain current ONU online information.
[0036] S103: Determine the current PON+MAC+LLID information overwrite position based on the saved timestamp.
[0037] S104: Store the mapping table entry at the corresponding overwrite location and save it to a file.
[0038] The above configuration based on the mapping relationship after system restart includes: if the OLT or line card restarts, when the system initialization is complete and the light is not turned on yet, the latest mapping relationship (i.e., mapping table entry) saved by the OLT is sent to the PON chip. Specifically, the latest PON+MAC+LLID mapping relationship saved in the file is sent to the PON chip, and the MAC and LLID mapping relationships under the PON port are bound in advance.
[0039] like Figure 3 As shown, an ONU initialization process embodiment is provided, which specifically includes the following steps: S201: Line card restart and initialization.
[0040] S202: Determine if a mapping relationship configuration exists. If yes, proceed to S203; otherwise, proceed to S206.
[0041] S203: The line card writes the saved mapping table entries to the PON chip.
[0042] S204: Determine if an ONU is online. If yes, proceed to S206; otherwise, proceed to S205.
[0043] S205: Mapping table entries are fully matched; clear mapping table entries.
[0044] S206: Awaiting ONU launch.
[0045] S207: Enter the ONU activation process.
[0046] During ONU activation, the process determines whether to trigger a GPON or EPON process based on the ONU type. If the ONU is of EPON type, the MAC address of the activated ONU is used to determine whether the ONU was online before restarting, thus classifying ONUs into two types: newly online ONUs and previously activated ONUs.
[0047] During the deployment of ONU, conflicts were dynamically handled based on mapping relationships, with corresponding dynamic adjustments made for different scenarios, including: Before and after the OLT or line card restarts, the mapping relationship remains unchanged. At this time, the ONU (the activated ONU) can go online normally, and the mapped LLID is consistent before and after the restart.
[0048] Before and after an OLT or line card restart, the mapping relationship changes. For newly added ONUs, the relationship is saved in the mapping table entry. At this time, it is necessary to determine the relationship between the number of ONU mappings for a single PON port currently saved by the device (X) and the maximum number supported by a single PON port (i.e., maximum support capacity) (Y), and perform corresponding processing according to whether X equals Y and X is less than Y.
[0049] When X equals Y, if all X ONUs with mapping relationships are online, then the PON port has reached its maximum support capacity and no longer supports new ONU access. All mapping relationships are cleared, and the connection is reprocessed according to the initial online method.
[0050] When X equals Y, if X ONUs with a mapping relationship are partially online, it indicates that some ONUs are offline. This triggers a fail-safe mechanism, which includes dynamically deleting the mapping relationships of offline ONUs. The fail-safe mechanism prevents the inability to discover new ONUs; if a new ONU comes online, it is handled according to the initial online process.
[0051] When X is less than Y, ONUs with a mapping relationship can go online directly, while ONUs without a mapping relationship are assigned LLIDs to go online. When X equals Y, the above process applies.
[0052] During the aforementioned dynamic adjustment process, the MAC and LLID mapping relationship can be saved and foolproofed, facilitating smooth upgrades and backward compatibility of the PON system.
[0053] Furthermore, the dynamic conflict handling based on the mapping relationship also includes: after the ONU comes online, if the ONU's LLID is manually modified, the mapping relationship before the modification is cleared, the mapping relationship between the modified MAC and LLID is established, and the ONUs corresponding to the LLID before and after the manual modification are kicked offline, and the ONU online process is retried.
[0054] Furthermore, when an ONU is taken offline, including scenarios such as deauthorization, restart, manual deactivation, and adding to the blacklist, the MAC and LLID mapping relationship of the ONU will not be changed. When it is brought back online, conflicts are dynamically handled based on the above mapping relationship, and corresponding dynamic adjustments are made for different scenarios.
[0055] In this embodiment, the mapping relationship is saved by cyclically overwriting, thereby improving device maintainability. After a system restart, MAC and LLID mappings are automatically bound to avoid resource conflicts. Conflicts are dynamically handled based on the relationship between X and Y, enabling automated conflict resolution. LLIDs can also be automatically reset after manual modification, ensuring the consistency of the mapping relationship.
[0056] like Figure 4 The diagram shows an example of an ONU activation process for EPON type, which includes the following steps: S301: EPON type ONU activation.
[0057] S302: Determine if the ONU is newly online. If yes, proceed to S303; otherwise, proceed to S304.
[0058] S303: Save the new mapping relationship of ONU.
[0059] S304: Determine if X equals Y. If yes, proceed to S305; otherwise, proceed to S307.
[0060] S305: Determine if all X ONUs are online. If yes, proceed to S307; otherwise, proceed to S306. S306: Delete the MAC and LLID mapping relationships of ONUs that cannot go online.
[0061] S307: Determine if an ONU is online. If so, proceed to the ONU activation process and further determine whether the GPON or EPON process applies. If not, wait for the ONU activation process until an ONU comes online.
[0062] In one embodiment, for the GPON process, each ONU is assigned a unique ALLOC and GEMPORT based on the ONUID allocated when the ONU comes online. To prevent ONUs from competing for each other's resources, the allocation is managed and distributed in the following manner.
[0063] OLT will pre-divide the system's ALLOC and GEMPORT resources into two parts: one part is designated as private resources, and the other part is designated as public resources. The private resources are exclusively used by the ONUID, while the public resources are shared by all ONUs.
[0064] During ONU activation, if the ONU is of GPON type, the process first determines whether it's a temporary or formal activation. If it's temporary, no action is taken, and the process proceeds to the next step. If it's formal activation, a preset number of private resources are allocated to each ONU ID. For example, each authorized ONU ID will be allocated M ALLOCs and N GEMPORTs from the private resource pool. Each allocated ALLOC and GEMPORT is mapped to an ONU ID, meaning each ONU's private resource is unique and will not be allocated to other ONUs. Once all private resources for an ONU ID have been allocated, resources are allocated from public resources. The allocated ALLOCs and GEMPORTs are marked and saved to prevent other ONUs from using them.
[0065] In the GPON process, after the deauthorization operation, the resource allocation will be cleared, including both public and private parts. However, due to the mapping relationship, the resources allocated to the corresponding ONUID will remain consistent with the previous allocation.
[0066] This embodiment effectively prevents resource contention among ONUs by exclusively allocating private resources and marking public resources after allocation, ensuring stable ONU uptime. Retaining the mapping relationship after deauthorization ensures allocation consistency and avoids redundant configuration. Furthermore, prioritizing the allocation of private resources and supplementing public resources as needed improves system robustness and resource utilization.
[0067] like Figure 5 The diagram shows an example of an activation process for an ONU of type GPON, which includes the following steps: S401: ONU activation.
[0068] S402: Determine whether it is GPON or EPON type. If it is GPON type, proceed to S403; if it is EPON type, proceed to EPON process.
[0069] S403: Determine if it is officially activated. If yes, proceed to S404; otherwise, proceed to S405.
[0070] S404: Create ALLOC and GEMPORT resource configurations for ONUID, then proceed to S406.
[0071] S405: After the temporary activation process, proceed to S401.
[0072] S406: Allocate private resources ALLOC and GEMPORT based on the mapping relationship of ONUID.
[0073] S407: Determine whether the private resources have been allocated. If yes, proceed to S408; otherwise, proceed to S401.
[0074] S408: Allocate public resources ALLOC and GEMPORT based on the mapping relationship of ONUID.
[0075] S409: Mark ALLOC and GEMPORT for public resource allocation.
[0076] Secondly, embodiments of this application also provide a PON system ONU anti-collision management device, which includes a judgment module, an EPON process module, a GPON process module, and a management module.
[0077] The judgment module is used to distinguish between EPON and GPON processes based on the ONU type.
[0078] The EPON process module is used to save the mapping relationship between MAC and LLID under PON port in the EPON process, and to issue configuration based on the mapping relationship after system restart.
[0079] The GPON process module is used to divide Alloc ID and GEMPORT resources into private and public resources in the GPON process, allocate resources according to ONUID, and issue configurations based on the mapping relationship between ONUID and resources after system restart.
[0080] The management module is used to dynamically handle conflicts based on mapping relationships during the ONU go-live process and to periodically update the saved mapping relationships.
[0081] The functions of each module in the above-mentioned device correspond to the steps in the above-mentioned embodiment of the ONU anti-collision management method for a PON system, and their functions and implementation processes will not be described in detail here.
[0082] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.
[0083] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.
[0084] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.
[0085] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.
[0086] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.
[0087] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A method for anti-collision management of ONUs in a PON system, characterized in that, The method includes: Differentiate between EPON and GPON processes based on ONU type; In the EPON process, the mapping relationship between MAC and LLID under the PON port is saved, and the configuration is issued based on the mapping relationship after the system restarts; In the GPON process, Alloc ID and GEMPORT resources are divided into private resources and public resources. Resources are allocated based on ONUID, and configurations are issued based on the mapping relationship between ONUID and resources after system restart. During the deployment of ONU, conflicts are dynamically handled based on mapping relationships, and the saved mapping relationships are updated regularly.
2. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the EPON process, saving the mapping relationship between MAC and LLID under the PON port includes: Record the mapping between MAC and LLID when the ONU comes online; During system operation, the mapping relationship is cyclically overwritten and saved at fixed intervals.
3. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the EPON process, after the system restarts, the configuration is issued based on this mapping relationship, including: If the OLT or line card restarts, and initialization is complete but the light is not yet switched on, the latest saved mapping relationship will be sent to the PON chip.
4. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the EPON process, during the ONU's online process, conflicts are dynamically handled based on mapping relationships, including: If the ONU mapping relationship has not changed, and if the number of ONU mappings on a single PON port is less than or equal to the maximum supported number, ONUs with mapping relationships will be directly brought online, while ONUs without mapping relationships will be assigned LLIDs for online access.
5. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the EPON process, during the ONU's online process, conflicts are dynamically handled based on mapping relationships, including: If the ONU mapping relationship changes, the number of ONU mappings on a single PON port equals the maximum supported number. If all ONUs with mapping relationships are online, all mapping relationships are cleared and reprocessed. If some ONUs with mapping relationships are online, a foolproof mechanism is triggered, which includes dynamically deleting the mapping relationships of offline ONUs.
6. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the EPON process, during the ONU's online process, conflicts are dynamically handled based on mapping relationships, including: If the ONU's LLID is manually modified, clear the mapping relationship before the modification, establish a mapping relationship between the modified MAC and LLID, and re-trigger the ONU online process.
7. The PON system ONU anti-collision management method as described in claim 1, characterized in that: In the EPON process, when the ONU goes offline, including scenarios such as deauthorization, restart, manual deactivation, and adding to the blacklist, the MAC and LLID mapping relationship of the ONU will not be changed.
8. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the GPON process, Alloc ID and GEMPORT resources are divided into private and public resources, and resources are allocated based on ONUID, including: Allocate a preset number of private resources to each ONUID. If all private resources are allocated, allocate from public resources and mark the allocated public resources.
9. The PON system ONU anti-collision management method as described in claim 1, characterized in that, In the GPON process, after the deauthorization operation, resource allocation is cleared, but the mapping relationship is retained.
10. A PON system ONU anti-collision management device, characterized in that, The device includes: The judgment module is used to distinguish between EPON and GPON processes based on the ONU type. The EPON process module is used to save the mapping relationship between MAC and LLID under PON port in the EPON process, and to issue configuration based on the mapping relationship after system restart; The GPON process module is used to divide Alloc ID and GEMPORT resources into private and public resources in the GPON process, allocate resources according to ONUID, and issue configurations based on the mapping relationship between ONUID and resources after system restart. The management module is used to dynamically handle conflicts based on mapping relationships during the ONU go-live process and to periodically update the saved mapping relationships.