PON (Passive Optical Network) repairing method, device, equipment and medium

Abstract

The invention relates to the technical field of communication networks, and discloses a PON (Passive Optical Network) repairing method, device, equipment and medium, which can be applied to Fiber To Room (FTTR), enterprise-level Fiber To Room-Bus (FTTR-B) and broadband fusion terminal products, and comprises the following steps: detecting the connection state of at least two FTTR slave devices; when a loop is detected to be formed between the at least two FTTR slave devices, for each FTTR slave device in the loop, recording a unique identifier of an opposite end device connected with the FTTR slave device as a loop device identifier; and respectively sending an identification message carrying a corresponding loop device identification to each FTTR slave device in the loop, the identification message being used for indicating each FTTR slave device to query a corresponding target port in a lower device list, and closing the target port to release the loop. The problem that in the prior art, when an FTTR slave device loop is removed, operation of a lower device is affected is solved.

Description

Technical Field

[0001] The present invention relates to the technical field of communication networks, and in particular to a PON network repair method, device, equipment and medium. Background Art

[0002] When the PON downstream of an FTTR master device is connected to two or more FTTR slave devices to form a network, and a loop is formed due to a connection error between the slave devices, the broadcast data frames will circulate infinitely in the FTTR gateway, forming a broadcast storm, leading to network congestion and network resource exhaustion.

[0003] The existing technical solution is that when the FTTR master detects a network loop, it closes the uplink port of one of the FTTR slave devices in the loop. This resolves the loop on the FTTR master, allowing the network between the other FTTR slave and the FTTR master to return to normal. Closing the uplink port of the FTTR slave device resolves the loop on the FTTR slave device, but it affects the operation of downstream devices. Summary of the Invention

[0004] The present invention provides a PON network repair method, device, computer equipment and medium, which solves the problem in the prior art that when an FTTR slave device loop is removed, the operation of the downstream device will be affected.

[0005] In a first aspect, a PON network repair method is provided, which is applied to an FTTR main device, comprising: Detecting the connection status of at least two FTTR slave devices; When a loop is detected between the at least two FTTR slave devices, for each FTTR slave device in the loop, recording a unique identifier of a peer device connected thereto as a loop device identifier; An identification message carrying the corresponding loop device identification is sent to each FTTR slave device in the loop, wherein the identification message is used to instruct each FTTR slave device to query the corresponding target port in the downstream device list and close the target port to release the loop.

[0006] Optionally, the unique identifier includes at least one of a MAC address, a device serial number, and an IP address.

[0007] Optionally, when a loop is detected between the at least two FTTR slave devices, the method includes: generating a loop alarm event in response to detecting that a loop is formed between the at least two FTTR slave devices; The loop alarm event is sent to a management system.

[0008] Optionally, the network repair method further includes: In response to receiving a loop release message sent by the FTTR slave device, generating a loop alarm release event; The loop alarm release event is sent to the management system.

[0009] In a second aspect, a PON network repair method is provided, which is applied to an FTTR slave device, comprising: receiving an identification message carrying a corresponding loop device identifier sent by the FTTR master device, wherein the identification message is generated and sent by the FTTR master device when a loop is detected between at least two FTTR slave devices, by recording, for each FTTR slave device in the loop, a unique identifier of the opposite device connected thereto as the loop device identifier; The target port corresponding to the identification information is searched in the downstream device list, and the target port is closed to eliminate the loop.

[0010] Optionally, the network repair method further includes: When a new device is connected to the target port, opening the target port; Send a loop release message to the FTTR master device.

[0011] In a third aspect, a PON network repair device is provided, which is applied to an FTTR main device, comprising: A detection module is used to enable loop detection and detect the connection status of at least two FTTR slave devices in real time; a recording module configured to, when detecting that a loop is formed between the at least two FTTR slave devices, record, for each FTTR slave device in the loop, a unique identifier of a peer device connected thereto as a loop device identifier; The sending module is used to send a message carrying the corresponding loop device identifier to each FTTR slave device in the loop, so that each FTTR slave device searches for a port matching the loop device identifier in the downstream device list based on the received loop device identifier, and closes the matching port to release the loop.

[0012] In a fourth aspect, a PON network repair device is provided, which is applied to an FTTR slave device, including: a receiving module, configured to receive an identification message carrying a corresponding loop device identifier sent by an FTTR master device, wherein the identification message is generated and sent by the FTTR master device upon detecting that a loop is formed between at least two FTTR slave devices, by recording, for each FTTR slave device in the loop, a unique identifier of the opposite end device connected thereto as the loop device identifier; The closing module is used to query the target port corresponding to the identification information in the downstream device list, and close the target port to eliminate the loop.

[0013] In a fifth aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned PON network repair method when executing the computer program.

[0014] In a sixth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned PON network repair method are implemented.

[0015] The solution implemented by the aforementioned PON network repair method, apparatus, computer device, and medium detects the connection status of at least two FTTR slave devices. When a loop is detected between the at least two FTTR slave devices, the unique identifier of the device connected to each FTTR slave device's connection port in the loop is recorded as the loop device identifier. An identification message carrying the corresponding loop device identifier is sent to each FTTR slave device in the loop. The identification message instructs each FTTR slave device to query a list of downstream devices for the corresponding target port and close the target port to break the loop. This solves the prior art issue of affecting the operation of downstream devices when breaking an FTTR slave device loop. The present invention can be applied to fiber-to-the-room (FTTR), fiber-to-the-room-for-business (FTTR-B), and broadband converged terminal products. In this invention, the target port in the closed loop is the downstream port corresponding to the downstream device, not the upstream port. Therefore, only the loop link is disconnected, without affecting normal communication with other downstream devices. The present invention solves the problem in the prior art that the operation of the downstream equipment will be affected when the FTTR slave equipment loop is released. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0017] Figure 1 This is a flow chart of a PON network repair method according to an embodiment of the present invention; Figure 2 is another flowchart of a PON network repair method according to one embodiment of the present invention; Figure 3 This is a structural diagram of a PON network repair device according to an embodiment of the present invention; Figure 4 FIG. 1 is another structural diagram of a PON network repair device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0018] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present invention.

[0019] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0020] It will also be understood that the term "and / or" used in the present description and appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0021] As used in the present specification and the appended claims, the term “if” may be interpreted as “when” or “upon” or “in response to determining”, depending on the context. Similarly, the phrase “if it is determined” or “if compared to [described condition or event]” may be interpreted as meaning “upon determination” or “in response to determination” or “upon comparison to [described condition or event]” or “in response to comparison to [described condition or event]”, depending on the context.

[0022] In addition, in the description of the present specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0023] References to "one embodiment" or "some embodiments" in the present specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present invention. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0024] It should be understood that the order of execution of the steps in the following embodiments does not necessarily mean the order in which they are executed. The order in which each process is executed should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0025] In order to illustrate the technical solution of the present invention, specific embodiments are provided below.

[0026] See also Figure 1 As shown, Figure 1 A flowchart of a PON network repair method provided in an embodiment of the present invention, which is applied to an FTTR main device, includes the following steps: S11: Detect the connection status of at least two FTTR slave devices.

[0027] Fiber to the Room (FTTR) is a broadband access technology that extends fiber networks directly into users' rooms. FTTR technology is primarily used in homes and corporate offices. It provides each room with an independent fiber connection, enabling ultra-high-speed network transmission, meeting the needs of multiple devices for simultaneous high-speed internet access. The signal is stable and resistant to interference.

[0028] The FTTR master device is the core control node in the all-optical networking system of a home or small enterprise. It is equivalent to the "central brain" of the entire network. It is responsible for the overall management of all FTTR slave devices, allocating network resources, monitoring network status, and coordinating the handling of network failures (such as loops, congestion, etc.). It is a key device for achieving high-speed and stable network coverage throughout the house.

[0029] The FTTR slave device is the signal extension and terminal access node in the FTTR all-optical networking system, equivalent to the "branch extender" of the network. It is uniformly managed and controlled by the FTTR master device. It is mainly responsible for extending the network signal distributed by the FTTR master device to various rooms in the home or enterprise (such as bedrooms, study, living room), and providing wired or wireless access services for terminal devices (mobile phones, computers, smart homes, etc.).

[0030] Under normal circumstances, the networking methods of FTTR master and slave devices can be: FTTR slave devices are directly connected to the FTTR master device respectively; FTTR slave device A is directly connected to the FTTR master device, and other FTTR slave devices are connected to FTTR slave device A, but it is strictly prohibited to connect FTTR slave devices in a loop.

[0031] After the FTTR master device and multiple slave devices are successfully networked according to the networking specifications, loop detection is enabled. At this point, regardless of whether the slave device is successfully networked using PON, LAN wired, or wireless networking, the FTTR master device and slave devices can communicate normally.

[0032] However, if the FTTR slave devices are not networked according to networking specifications and incorrect links are made between them, a loop may form between at least two FTTR slave devices. Broadcast data frames will circulate endlessly between the FTTR slave devices, creating a broadcast storm and leading to network congestion and resource exhaustion. Therefore, it is necessary to detect the connection status of at least two FTTR slave devices, that is, to detect whether a loop has formed between the FTTR slave devices.

[0033] Detection methods generally include: The first method uses broadcast frame tag tracking to detect loops. This method exploits the fact that broadcast frames can circulate endlessly in a loop. By adding a "propagation tag" (such as a unique device identifier or a forwarding counter) to specific detection frames, the propagation path can be tracked. If the same frame is detected to be received repeatedly, and the tag indicates that it has passed through multiple FTTR slave devices, forming a closed loop, a loop is determined.

[0034] The second method is to detect loops based on port traffic anomalies. Loops can cause a large number of repeated broadcast frames to circulate between FTTR slave devices, causing a sudden increase in traffic on the relevant ports (far exceeding normal service traffic). The frame content is highly repetitive (for example, the same source MAC address and broadcast destination MAC address). Loops can be identified by monitoring port traffic characteristics.

[0035] The third method is based on extended detection using the Link Layer Discovery Protocol (LLDP). The FTTR slave device periodically sends messages containing its own information to the downstream device using the Link Layer Discovery Protocol (LLDP). If a loop occurs, the FTTR slave device will receive LLDP messages from a device that is not directly connected.

[0036] S12: When it is detected that a loop is formed between the at least two FTTR slave devices, for each FTTR slave device in the loop, the unique identifier of the opposite-end device connected thereto is recorded as a loop device identifier.

[0037] In an FTTR network, each FTTR slave device has a unique identifier (such as a MAC address, device serial number, logical ID, etc.). Each downstream port on each FTTR slave device also has a unique number (such as GE1 and GE2 on the FTTR slave device). When a loop is formed, the FTTR slave devices in the loop are connected to each other through their downstream ports. For example, FTTR slave device A's GE1 port connects to FTTR slave device B's GE2 port, FTTR slave device B's GE3 port connects to FTTR slave device C's GE4 port, and FTTR slave device C's GE5 port connects to FTTR slave device A's GE6 port. FTTR slave devices A, B, and C together form a loop.

[0038] After detecting the loop, first, all FTTR slave devices participating in the loop (such as FTTR slave devices A, B, and C mentioned above) are determined, and FTTR slave devices not participating in the loop (such as FTTR slave device D connected only with the FTTR master device) are excluded.

[0039] For each FTTR slave device participating in the loop, the unique identifier of the opposite end device directly connected thereto, i.e., the "loop device identifier", is extracted.

[0040] For example, there are three FTTR slave devices in the FTTR network, forming a loop: the GE1 port of FTTR slave device A—GE2 port of FTTR slave device B, GE3 port of FTTR slave device B—GE4 port of FTTR slave device C, GE5 port of FTTR slave device C—GE6 port of FTTR slave device A. The detection stage has confirmed that FTTR slave devices A, B, and C participate in the loop.

[0041] Then, the loop device identifiers are recorded: FTTR slave device A participates in the loop through the downlink ports GE1 and GE6, the GE1 port is directly connected to slave device B, and therefore the unique identifier of the opposite end device B (such as MAC: 00:11:22:33:44:55) is recorded, and the GE6 port is directly connected to slave device C, and therefore the unique identifier of the opposite end device C (such as MAC: 66:77:88:99:AA:BB) is recorded; FTTR slave device B participates in the loop through the downlink ports GE2 and GE3, the GE2 port is directly connected to slave device A, and therefore the unique identifier of the opposite end device A (such as MAC: CC:DD:EE:FF:11:22) is recorded, and the GE3 port is directly connected to FTTR slave device C, and therefore the unique identifier of the opposite end device C (66:77:88:99:AA:BB) is recorded; FTTR slave device C participates in the loop through the downlink ports GE4 and GE5, the GE4 port is directly connected to FTTR slave device B, and therefore the unique identifier of the opposite end device B (00:11:22:33:44:55) is recorded, and the GE5 port is directly connected to FTTR slave device A, and therefore the unique identifier of the opposite end device A (CC:DD:EE:FF:11:22) is recorded.

[0042] S13: Send an identification message carrying the corresponding loop device identifier to each FTTR slave device in the loop, respectively, and the identification message is used to instruct each FTTR slave device to query the corresponding target port in the hanging device list and close the target port to remove the loop.

[0043] This process is the core execution stage of network repair, and the loop information obtained in the detection stage is converted into specific port operation instructions through the "identification message" to close the target port to remove the loop.

[0044] The identification message is an instruction sent by the FTTR master device to the FTTR slave device in the loop. Its content generally includes: the loop device identification of the FTTR slave device; and an operation instruction: instructing the FTTR slave device to query the target port according to the identification message and close it.

[0045] For example, there are three FTTR slave devices in the FTTR network, forming a loop: GE1 port of FTTR slave device A—GE2 port of FTTR slave device B, GE3 port of FTTR slave device B—GE4 port of FTTR slave device C, and GE5 port of FTTR slave device C—GE6 port of FTTR slave device A.

[0046] The identification message sent by the FTTR master device to FTTR slave device A is: close the port connected to FTTR slave device B (MAC: 00:11:22:33:44:55), close the port connected to FTTR slave device C (MAC: 66:77:88:99:AA:BB); the identification message sent to FTTR slave device B is: close the port connected to FTTR slave device A (MAC: CC:DD:EE:FF:11:22), close the port connected to FTTR slave device C (MAC: 66:77:88:99:AA:BB); the identification message sent to FTTR slave device C is: close the port connected to FTTR slave device B (MAC: 00:11:22:33:44:55), close the port connected to FTTR slave device A (MAC: CC:DD:EE:FF:11:22).

[0047] FTTR slave device A finds out from the list of downstream devices that the target interface of FTTR slave device B (MAC: 00:11:22:33:44:55) is GE1, and the target port of FTTR slave device C (MAC: 66:77:88:99:AA:BB) is GE6. It then shuts down ports GE1 and GE6. FTTR slave device B finds out from the list of downstream devices that the target port of FTTR slave device A (MAC: CC:DD:EE:FF:11:22) is GE6. E2, FTTR slave device C (MAC: 66:77:88:99:AA:BB) targets port GE3 and shuts down ports GE2 and GE3. FTTR slave device C then searches its list of connected devices and finds that FTTR slave device B (MAC: 00:11:22:33:44:55) targets port GE4, and FTTR slave device A (MAC: CC:DD:EE:FF:11:22) targets port GE5. It then shuts down ports GE4 and GE5. This resolves the loop, while the other devices connected to each FTTR slave device continue to operate normally.

[0048] The PON network repair method detects the connection status of at least two FTTR slave devices. When a loop is detected between the at least two FTTR slave devices, the method records the unique identifier of the device connected to each FTTR slave device's connection port in the loop as the loop device identifier. An identification message carrying the corresponding loop device identifier is sent to each FTTR slave device in the loop. The identification message instructs each FTTR slave device to query a list of downstream devices for the corresponding target port and close the target port to break the loop. This method solves the problem in the prior art where breaking a FTTR slave device loop can affect the operation of downstream devices. The present invention can be applied to fiber-to-the-room (FTTR), enterprise-level fiber-to-the-room (FTTR-B), and broadband converged terminal products. In the present invention, the target port in the closed loop is the downstream port corresponding to the downstream device, not the upstream port. Therefore, only the loop link is disconnected, without affecting normal communication with other downstream devices. This method solves the problem in the prior art where breaking a FTTR slave device loop can affect the operation of downstream devices.

[0049] Optionally, the unique identifier includes at least one of a MAC address, a device serial number, and an IP address.

[0050] The unique identifier is key information for locating the opposite-end device connected to the FTTR slave device.

[0051] The MAC address is the physical address that is embedded in the network card of a network device (such as an FTTR slave device) when it leaves the factory. It consists of a 48-bit binary number (usually represented as six groups of hexadecimal numbers, such as 00:1B:44:11:3A:B7) and is globally unique.

[0052] The device serial number is a unique string (such as a combination of letters and numbers) assigned by the manufacturer to each device. It is printed on the device body or stored in the device system (can be queried through management commands). It is globally unique (all devices produced by the same manufacturer have unique serial numbers) and is permanently fixed (bound to the hardware and cannot be modified).

[0053] An IP address is a logical address at the network layer (such as 192.168.1.100 in IPv4 or 2001:db8::1 in IPv6), which is configured by the network administrator or automatically assigned and is unique within the network.

[0054] Generally speaking, accurate positioning can be achieved by relying on only one of the MAC address, device serial number, and IP address. In some special cases, such as when a certain identification fails, two or three of them can be combined to jointly locate the device.

[0055] Optionally, when a loop is detected between the at least two FTTR slave devices, the method includes: generating a loop alarm event in response to detecting that a loop is formed between the at least two FTTR slave devices; and sending the loop alarm event to a management system.

[0056] When a loop is detected between the at least two FTTR slave devices, the loop can be resolved by automatically closing the target port, but the physical connection between the FTTR slave devices in the loop still exists. A loop alarm event is generated and sent to the management system, prompting operation and maintenance personnel to promptly address the physical connection between the loops on site.

[0057] A loop alarm event typically includes the following information: loop occurrence time, involved devices, loop path, loop status, and impact area. For example, loop occurrence time: July 15, 2023, 14:30:22; involved devices: FTTR slave device A, FTTR slave device B, and FTTR slave device C; loop path: FTTR slave device A's GE1 port to FTTR slave device B's GE2 port, FTTR slave device B's GE3 port to FTTR slave device C's GE4 port, FTTR slave device C's GE5 port to FTTR slave device A's GE6 port; loop status: the system automatically shut down port A's GE1 port, alleviating network congestion; impact area: users in Unit 2, Building 3, experienced internet access issues (which have since been restored). After viewing the loop alarm event on the management system, operations and maintenance personnel promptly addressed the physical connections between the loops.

[0058] See also Figure 2 As shown, Figure 2 Another flowchart of a PON network repair method provided in an embodiment of the present invention, which is applied to an FTTR slave device, includes the following steps: S21: Receive an identification message carrying the corresponding loop device identifier sent by the FTTR master device. The identification message is generated and sent by the FTTR master device when it detects that a loop is formed between at least two FTTR slave devices. For each FTTR slave device in the loop, the FTTR master device records the unique identifier of the opposite device connected to it as the loop device identifier.

[0059] For example, for FTTR slave device A, the opposite ends connected to it are FTTR slave devices B and C. Therefore, the identification message received by FTTR slave device A will include the unique identifications of B and C.

[0060] S22: Query the target port corresponding to the identification information in the downstream device list, and close the target port to eliminate the loop.

[0061] Each FTTR slave device maintains a local record, i.e. a list of hanging devices, storing the device identifiers (which can be MAC addresses, unique device IDs, etc.) connected to all its physical ports (such as network ports, optical ports).

[0062] FTTR slave device A first extracts the "loop device identifier" in the identification message to determine the opposite device forming a loop with itself. For example: FTTR slave device A learns from the identification information that the loop device identifier is "slave device B's ID", and then queries the target port connected to slave device B from the hanging device list and closes it, thereby breaking the loop.

[0063] Optionally, the network repair method further comprises: when the target port accesses a new device, opening the target port; and sending a loop breaking message to the FTTR master device.

[0064] After closing the target port (breaking the loop), the FTTR slave device does not permanently disable the port, but continuously monitors the port state. When detecting that the target port accesses a new device (not the original loop device), the port is automatically opened to achieve dynamic self-healing and resource reuse of the network.

[0065] For example, when the target port detects an access signal, the FTTR slave device reads the identification information (such as MAC address, device ID) of the access device, and compares it with the "original loop device identifier". If they are consistent (still the original loop device), the target port remains closed to avoid forming a loop again. If they are inconsistent (new device), it is determined as "legal access", the target port is opened, and a loop breaking message is sent to the FTTR master device.

[0066] In an embodiment, a PON network repair device is provided. As shown in Figure 3 The network repair device is applied to an FTTR master device, and includes a detection module 31, a recording module 32, and a sending module 33. The functions of each module are described in detail as follows: The detection module is configured to start loop detection and detect the connection state of at least two FTTR slave devices in real time. The recording module is configured to, when detecting that a loop is formed between the at least two FTTR slave devices, record the unique identifier of the opposite device connected to each FTTR slave device in the loop as a loop device identifier. The sending module is configured to send a message carrying the corresponding loop device identifier to each FTTR slave device in the loop, so that each FTTR slave device queries the port matching the loop device identifier in the hanging device list based on the received loop device identifier, and closes the matching port to break the loop.

[0067] In another embodiment, a PON network repair device is also provided. As shown in Figure 4 As shown, the network repair device is applied to the FTTR slave device, including a receiving module 41 and a closing module 42. The functional modules are described in detail as follows: a receiving module, configured to receive an identification message carrying a corresponding loop device identifier sent by an FTTR master device, wherein the identification message is generated and sent by the FTTR master device upon detecting that a loop is formed between at least two FTTR slave devices, by recording, for each FTTR slave device in the loop, a unique identifier of the opposite end device connected thereto as the loop device identifier; The closing module is used to query the target port corresponding to the identification information in the downstream device list, and close the target port to eliminate the loop.

[0068] An embodiment of the present invention further provides an electronic device comprising a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the aforementioned PON network repair method, which will not be described in detail here to avoid repetition. Alternatively, the electronic device can implement the functions of each module in the aforementioned PON network repair device embodiment, which will not be described in detail here.

[0069] An embodiment of the present invention further provides a readable storage medium storing a program, characterized in that when executed by a processor, the program implements the aforementioned PON network repair method, which is not described here in detail to avoid repetition. Alternatively, when executed by a processor, the program implements the functions of the various modules in the aforementioned PON network repair device embodiment, which is not described here in detail.

[0070] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should all be included in the scope of protection of the present invention.

[0071] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to memory, storage, database or other medium used in each embodiment provided by the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0072] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above-mentioned division of functional units and modules is exemplified, and in actual application, the above-mentioned functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above.

Claims

1. A PON network repair method, applied to FTTR main equipment, characterized in that: include: Detecting the connection status of at least two FTTR slave devices; When a loop is detected between the at least two FTTR slave devices, for each FTTR slave device in the loop, recording a unique identifier of a peer device connected thereto as a loop device identifier; An identification message carrying the corresponding loop device identification is sent to each FTTR slave device in the loop, wherein the identification message is used to instruct each FTTR slave device to query the corresponding target port in the downstream device list and close the target port to release the loop.

2. The network repair method according to claim 1, characterized in that: The unique identifier includes at least one of a MAC address, a device serial number, and an IP address.

3. The network repair method according to claim 1, characterized in that: When a loop is detected between the at least two FTTR slave devices, the method includes: generating a loop alarm event in response to detecting that a loop is formed between the at least two FTTR slave devices; The loop alarm event is sent to a management system.

4. The network repair method according to claim 1, characterized in that: Also includes: In response to receiving a loop release message sent by the FTTR slave device, generating a loop alarm release event; The loop alarm release event is sent to the management system.

5. A PON network repair method, applied to FTTR slave equipment, characterized in that: include: receiving an identification message carrying a corresponding loop device identifier sent by the FTTR master device, wherein the identification message is generated and sent by the FTTR master device when a loop is detected between at least two FTTR slave devices, by recording, for each FTTR slave device in the loop, a unique identifier of the opposite device connected thereto as the loop device identifier; The target port corresponding to the identification information is searched in the downstream device list, and the target port is closed to eliminate the loop.

6. The network repair method according to claim 4, characterized in that: Also includes: When a new device is connected to the target port, opening the target port; Send a loop release message to the FTTR master device.

7. A PON network repair device, applied to FTTR main equipment, characterized in that: include: A detection module is used to enable loop detection and detect the connection status of at least two FTTR slave devices in real time; a recording module configured to, when detecting that a loop is formed between the at least two FTTR slave devices, record, for each FTTR slave device in the loop, a unique identifier of a peer device connected thereto as a loop device identifier; The sending module is used to send a message carrying the corresponding loop device identifier to each FTTR slave device in the loop, so that each FTTR slave device searches for a port matching the loop device identifier in the downstream device list based on the received loop device identifier, and closes the matching port to release the loop.

8. A PON network repair device, applied to FTTR slave equipment, characterized in that: include: a receiving module, configured to receive an identification message carrying a corresponding loop device identifier sent by an FTTR master device, wherein the identification message is generated and sent by the FTTR master device upon detecting that a loop is formed between at least two FTTR slave devices, by recording, for each FTTR slave device in the loop, a unique identifier of the opposite end device connected thereto as the loop device identifier; The closing module is used to query the target port corresponding to the identification information in the downstream device list, and close the target port to eliminate the loop.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the PON network repair method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the PON network repair method according to any one of claims 1 to 6 are implemented.

Images