WO2022267737A1 - 故障定位检测方法、根节点、通信系统拓扑和存储介质 - Google Patents

故障定位检测方法、根节点、通信系统拓扑和存储介质 Download PDF

Info

Publication number
WO2022267737A1
WO2022267737A1 PCT/CN2022/092745 CN2022092745W WO2022267737A1 WO 2022267737 A1 WO2022267737 A1 WO 2022267737A1 CN 2022092745 W CN2022092745 W CN 2022092745W WO 2022267737 A1 WO2022267737 A1 WO 2022267737A1
Authority
WO
WIPO (PCT)
Prior art keywords
leaf node
node
uplink
target
onu
Prior art date
Application number
PCT/CN2022/092745
Other languages
English (en)
French (fr)
Inventor
余辰东
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022267737A1 publication Critical patent/WO2022267737A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/44—Star or tree networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements

Definitions

  • the embodiments of the present application relate to but are not limited to the technical field of communication, and in particular, relate to a fault location detection method, a root node, a communication system topology, and a computer-readable storage medium.
  • the root node For the PToMP (Point To MultiPoint, Point to Multipoint) communication architecture system, there is a root node and multiple leaf nodes.
  • the above-mentioned PToMP communication architecture system adopts the TDMA (Time Division Multiple Access) mechanism
  • the root node will assign different uplink logical channel identifiers to different leaf nodes, and the root node will assign different uplink logical channel identifiers to different leaf nodes, and the root node will The channel ID allocates different uplink bandwidth time slots for leaf nodes to upload data.
  • the uplink logical channel ID adopts a dynamic allocation mechanism, the root node may repeatedly allocate an uplink logical channel ID to other leaf nodes when the previously assigned leaf node fails, such as being offline.
  • the leaf node that previously allocated the uplink logical channel ID may not normally release the uplink logical channel ID in case of failure, the problem of duplication of uplink logical channel IDs may occur.
  • a leaf node fails to release the uplink logical channel ID as required by the root node due to an abnormality, if the root node assigns the uplink logical channel ID to other leaf nodes again, it will cause the uplink logical channel ID of the leaf node to conflict In this case, abnormal leaf nodes will interfere with the uplink data of normal leaf nodes.
  • Embodiments of the present application provide a fault location detection method, a root node, a communication system topology, and a computer-readable storage medium.
  • the embodiment of the present application provides a method for fault location and detection, which is applied to a root node in a communication system topology, and the communication system topology further includes a plurality of leaf nodes communicating with the root node, and the method includes : Obtain the first communication quality parameter of the target leaf node, wherein the target leaf node is one of the plurality of leaf nodes; when the first communication quality parameter does not meet the requirements of the first preset communication quality parameter, obtain historical characteristic information of a plurality of leaf nodes; determine a first leaf node suspected of interfering with the target leaf node among the plurality of leaf nodes according to the historical characteristic information; control the first leaf node in the target Stop uploading data in the first uplink time slot of the leaf node, and obtain a second communication quality parameter of the target leaf node in the first uplink time slot; when the second communication quality parameter satisfies the second preset communication
  • the quality parameter requirement determines that the first leaf node is a second leaf node that interferes with the target
  • the embodiment of the present application also provides a root node, including: a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor executes the computer program
  • the program implements the fault location and detection method described in the first aspect above.
  • the embodiment of the present application further provides a communication system topology, including a plurality of leaf nodes and the root node as described in the second aspect above, where the root node communicates with the plurality of leaf nodes.
  • the embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, and the computer-executable instructions are used to execute the method for fault location and detection as described in the first aspect above.
  • FIG. 1 is a schematic diagram of a PToMP communication system topology provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of an xPON network provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a system architecture platform for performing a fault location detection method provided by an embodiment of the present application
  • FIG. 4 is a flowchart of a fault location and detection method provided by an embodiment of the present application.
  • FIG. 5 is a specific flow chart of determining the first leaf node in the fault location detection method provided by one embodiment of the present application.
  • FIG. 6 is a specific flow chart of determining the first leaf node in the fault location detection method provided by another embodiment of the present application.
  • Fig. 7 is a specific flowchart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by an embodiment of the present application;
  • Fig. 8 is a specific flow chart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by another embodiment of the present application;
  • 9 is a specific flowchart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by another embodiment of the present application;
  • FIG. 10 is a specific flow chart of subsequent uploading of the characteristic parameters of the second leaf node in the fault location detection method provided by an embodiment of the present application;
  • FIG. 11 is a flowchart of xPON network topology authorization provided by an embodiment of the present application.
  • Fig. 12 is a specific flowchart of a fault location and detection method in an xPON network provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a topology of a PToMP communication system provided by an embodiment of the present application.
  • the PToMP communication architecture system in FIG. 1 it includes a root node 110 and multiple leaf nodes 120 communicating with the root node 110 .
  • the root node 110 will dynamically assign different uplink logical channel IDs to different leaf nodes 120, and the root node 110 will assign different uplink logical channel IDs according to the uplink logical channel ID.
  • the uplink bandwidth time slots are used for leaf nodes 120 to upload data.
  • the root node may repeatedly allocate an uplink logical channel ID to other leaf nodes when the previously assigned leaf node fails, such as being offline. Since the leaf node that previously allocated the uplink logical channel ID may not normally release the uplink logical channel ID in case of failure, the problem of duplication of uplink logical channel IDs may occur.
  • the topology of the PToMP communication system using the TDMA mechanism may be a PON (Passive Optical Network, Passive Optical Network) communication system using the TDMA mechanism in the access network.
  • the root node 110 may correspond to a PON The OLT (Optical Line Terminal, optical line terminal) in the communication system
  • the leaf node 120 can correspond to the ONU (Optical Network Unit, optical network unit) or ONT (Optical Network Termination, optical network terminal) in the PON communication system.
  • the communication system topology using the TDMA mechanism may also be other network architectures using the TDMA mechanism or multiple terminal devices using the TDMA mechanism, which is not limited in this embodiment of the present application.
  • the embodiment of the present application takes the PON communication system using the TDMA mechanism in the access network as an example, Describe in detail.
  • passive optical network equipment based on the TDMA mechanism can be divided into EPON (Ethernet Passive Optical Network, Ethernet-based passive optical network equipment), G-PON (Gigabit-capable Passive Optical Network, thousand Mega passive optical network equipment) and passive optical network equipment with other working mechanisms; the above-mentioned passive optical network equipment has the same system structure, and all include OLT and ONU.
  • the above-mentioned PON technologies are collectively referred to as xPON.
  • FIG. 2 is a schematic diagram of an xPON network provided by an embodiment of the present application.
  • the xPON network in Fig. 2 comprise EMS (Element Management Server, network management server) 210, OLT220, ODN (Optical Distribution Network, optical distribution network) 230 and a plurality of ONU240.
  • the OLT220 serves as a central office device and connects multiple ONU240 through the ODN230 network; the ONU240 is used to realize the access of user services, so as to realize functions such as data services and configuration management.
  • the transmission direction from the OLT220 to the ONU240 is the downlink direction, and the downlink direction adopts broadcast mode to send data, and finally the ONU240 judges whether the data is valid and decides to receive or discard according to the data identification;
  • the transmission direction from the ONU240 to the OLT220 is In the uplink direction, TDMA is used to send data in the uplink direction.
  • ONU240 sends data based on the logical channel identifier according to the uplink authorization of the OLT, and the OLT judges whether the data is valid and decides to receive or discard it.
  • bandwidth authorization will be periodically performed between OLT220 and ONU240. Specifically, OLT220 will send a general authorization to each ONU240 based on the ONU ID. Only the IDs match The ONU240 can respond and send a report according to the authorization requirement, then the OLT220 allocates new bandwidth for the ONU240 through the authorization frame in the next cycle according to the report frame reported by the ONU240, and then the ONU whose upstream logical channel ID matches sends data within the time specified by the authorization frame .
  • the uplink logical channel ID of the deleted ONU240 will be reassigned by the OLT to other newly accessed ONU240s, that is, the uplink logical channel ID of the ONU240 adopts a dynamic allocation mechanism.
  • the OLT 220 sends the general authorization to each ONU 240 based on the ONU identification, which may be, but not limited to, the MPCP GATE frame in the EPON system, or the GTC/BWmap frame in the GPON system.
  • the report about the above-mentioned ONU response and sent according to the authorization requirement may be, but not limited to, the MPCP report frame in the EPON system, or the PLOAMu/DBRu frame in the GPON system.
  • each ONU240 upstream logical channel identifier is uniformly allocated by the OLT220 when the ONU240 registers, and after the ONU240 successfully registers, the OLT220 allocates different upstream bandwidth time slots according to the ONU240 upstream logical channel identifier.
  • each ONU240 is assigned one or more unique logical channel identifiers on the PON port as the uplink channel time slot identifier of the ONU240 according to its service configuration in the unit of the PON port, which is used for ONU240 only Data is forwarded in the uplink time slot allocated by OLT220.
  • the uplink channel time slot identifier corresponds to LIID (Logical Link Identifier, Logical Link Identifier); in the GPON system, the uplink channel time slot identifier corresponds to AllocID (Allocate Identifier, allocation identifier).
  • the registration process will be started periodically, and only the unregistered new access ONU240 can respond to the registration authorization frame sent by the OLT220 in the registration period, and The OLT220 assigns it a unique ONU identifier, and finally the ONU240 sends a registration complete frame through interaction to complete the entire registration process. That is, in the bandwidth allocation of ONU240 registration and normal operation in the above-mentioned xPON network, ONU240 only turns on the upstream light of the optical module within the authorized time of OLT220, and responds to various messages of OLT220. When the authorized time slice is not up or after it is closed, the ONU240 must turn off the upstream light of the optical module, and can only monitor the downstream message of the OLT220, and accept or discard it according to the ONU identification in the downstream message header.
  • the above-mentioned registration authorization frame can be, but not limited to, the MPCP discovery GATE frame in the EPON system, or the DS Frame with valid Psync frame in the GPON system.
  • the above-mentioned ONU identification it can be, but not limited to, the LLID in the EPON system, or the ONU ID in the GPON system.
  • the above-mentioned registration completion frame it can be, but not limited to, the MPCP register ack frame sent by the ONU240 in the EPON system, or the Serial_Number_ONU or Password frame sent by the ONU240 in the GPON system.
  • the uplink logical channel ID adopts a dynamic allocation mechanism
  • the OLT220 reclaims the uplink logical channel ID of an ONU240, and the ONU240 is abnormal, the ONU240 has not correctly released the uplink logical channel ID originally assigned to it by the OLT220 due to some abnormality. channel ID, and the OLT220 redistributes the upstream logical channel ID to other normal ONU240 on the same link.
  • the abnormal ONU240 that has not correctly released the upstream logical channel ID is opposite to the normal ONU240 assigned the upstream logical channel ID by the OLT220
  • the uplink data interferes, that is, the uplink logical channel is occupied.
  • the abnormal ONU240 When the abnormal ONU240 illegally occupies the upstream logical channel ID allocated by the OLT220 device, it will directly affect the interaction between the ONU240 and the OLT220 equipment that the OLT220 normally allocates the upstream logical channel ID, and cause the upstream business of the ONU240 that is normally assigned the upstream logical channel ID to occur. Packet loss and disconnection in severe cases will seriously affect the business, including the following two aspects.
  • the first aspect due to different ONU240 state differences, such as signal strength differences or bandwidth differences, the manifestations are different in the case of upstream logical channel occupation, and due to the unsteady characteristics of the ONU240 itself, it is difficult to detect the occupation of the upstream logical channel.
  • the second aspect in the dynamic allocation mechanism of the logical channel ID, the occupation of the logical channel ID exists implicitly, so it is difficult to locate the abnormal ONU 240 occupied by the upstream logical channel ID.
  • the above-mentioned problem occurs because the software and hardware of the abnormal ONU240 work abnormally and cause the OLT220 in the xPON network that adopts the TDMA working mode to use an abnormality in the allocation and management of the upstream logical channel identification, and cause the ONU240 that OLT220 normally allocates this upstream logical channel identification. interference.
  • an embodiment of the present application provides a fault location detection method, a root node, a communication system topology, and a computer-readable storage medium, wherein the fault location detection method includes but is not limited to the following steps: the root node in the communication system topology The first communication quality parameter of the target leaf node will be obtained, wherein the target leaf node is one of the plurality of leaf nodes in the communication system topology; when the first communication quality parameter does not meet the first preset communication quality parameter requirements, the root The node will obtain the historical characteristic information of multiple leaf nodes, and determine the first leaf node that is suspected of interfering with the target leaf node among the multiple leaf nodes according to the historical characteristic information; then, the root node will control the first leaf node in the target leaf node Stop uploading data in the first uplink time slot, and obtain the second communication quality parameter of the target leaf node in the first uplink time slot; when the second communication quality parameter meets the second preset communication quality parameter requirements, the root node will determine the first A leaf node
  • the root node of the embodiment of the present application can screen out the second leaf node that interferes with the target leaf node, that is, the abnormal leaf node, from multiple leaf nodes, which solves the problem of leaf nodes in the topology of the PToMP communication system.
  • the problem that the uplink logical channel of the node is occupied realizes the positioning of abnormal leaf nodes.
  • FIG. 3 is a schematic diagram of a system architecture platform 300 for implementing a fault location and detection method provided by an embodiment of the present application.
  • the system architecture platform 300 is provided with a processor 310 and a memory 320 , wherein the processor 310 and the memory 320 may be connected via a bus or in other ways, and in FIG. 3 the connection via a bus is taken as an example.
  • the memory 320 can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory 320 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices.
  • the memory 320 may include memory located remotely relative to the processor 310, and these remote memories may be connected to the system architecture platform through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • system architecture platform can be applied to 3G communication network systems, LTE communication network systems, 5G communication network systems and subsequent evolved mobile communication network systems, etc., which is not specifically limited in this embodiment.
  • system architecture platform shown in FIG. 3 does not constitute a limitation to the embodiment of the present application, and may include more or less components than those shown in the illustration, or combine certain components, or have different Part placement.
  • the processor 310 can call the fault location detection program stored in the memory 320 to execute the fault location detection method.
  • Figure 4 is a flowchart of a fault location and detection method provided by an embodiment of the present application.
  • the fault location and detection method is applied to the root node in the communication system topology, wherein the communication system topology also includes communication with the root node Multiple leaf nodes, the fault location detection method includes but not limited to step S100, step S200, step S300, step S400 and step S500.
  • Step S100 Obtain a first communication quality parameter of a target leaf node, where the target leaf node is one of multiple leaf nodes.
  • Step S200 when the first communication quality parameter does not meet the requirement of the first preset communication quality parameter, acquire historical feature information of multiple leaf nodes.
  • Step S300 Determine the first leaf node suspected of interfering with the target leaf node among the plurality of leaf nodes according to historical feature information.
  • Step S400 controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node, and acquiring a second communication quality parameter of the target leaf node in the first uplink time slot.
  • Step S500 when the second communication quality parameter satisfies the second preset communication quality parameter requirement, determine that the first leaf node is the second leaf node of the interference target leaf node.
  • the root node will obtain the first communication quality parameter of the target leaf node, and compare the first communication quality parameter with the first preset communication quality parameter requirement, when the first If the communication quality parameter does not meet the requirement of the first preset communication quality parameter, it means that the target leaf node has received interference from other leaf nodes, and the target leaf node is the interfered leaf node. Then the root node will obtain the historical feature information of multiple leaf nodes, and based on the analysis of the historical feature information of multiple leaf nodes, it will determine the first node that is suspected of interfering with the target leaf node among the multiple leaf nodes except the target leaf node.
  • the leaf node that is, the first leaf node is a suspicious leaf node.
  • the root node will control the first leaf node to stop uploading data in the first uplink time slot of the target leaf node, and obtain the second communication quality parameter of the target leaf node in the first uplink time slot , in other words, during the period of trying to shut down the first leaf node, observe whether the communication quality of the target leaf node will be restored.
  • the second communication quality parameter meets the requirements of the second preset communication quality parameter, that is, if the communication quality of the target leaf node is restored during the shutdown of the first leaf node, it indicates that the first leaf node that stops uploading data is the target leaf node.
  • the node causes interference to the interfering leaf node, so the root node will determine that the first leaf node is the second leaf node of the interfering target leaf node, that is, the first leaf node is the interfering leaf node.
  • the second communication quality parameter does not meet the second preset communication quality parameter requirements, that is, if the communication quality of the target leaf node is not restored during the shutdown of the first leaf node, it indicates that the first leaf node that stopped uploading data It is not an interfering leaf node that interferes with the target leaf node.
  • the root node of the embodiment of the present application can screen out the second leaf node that interferes with the target leaf node, that is, the abnormal leaf node, from multiple leaf nodes, which solves the problem of leaf nodes in the topology of the PToMP communication system.
  • the problem that the uplink logical channel of the node is occupied realizes the positioning of abnormal leaf nodes.
  • the fault location and detection method of the embodiment of the present application can solve the problem that the uplink logical channel of the leaf node in the topology of the PToMP communication architecture using the TDMA mechanism is occupied without relying on the cooperation with the leaf node, and detect abnormal leaf nodes. position.
  • the embodiment of the present application adopts a software method based on the existing hardware to realize the dynamic monitoring of the uplink logical channel occupation problem, it is simpler and more flexible, and the cost is also lower.
  • first communication quality parameter it may be, but not limited to, the number of online and offline times of the target leaf node within the preset period, the number of uplink bit errors of the target leaf node within the preset period, the The change value of the number of times of going online and offline within the preset period, or the change value of the number of uplink bit errors of the target leaf node within the preset period.
  • the above-mentioned second communication quality parameter may be, but not limited to, the number of online and offline times of the target leaf node within a preset period, the number of uplink bit errors of the target leaf node within a preset period, the target leaf node The change value of the number of times the node goes online and offline within the preset period, or the change value of the number of uplink bit errors of the target leaf node within the preset period.
  • first preset communication quality parameter requirement and the second preset communication quality parameter requirement include but are not limited to the following four situations.
  • the first case when the first communication quality parameter and the second communication quality parameter are the number of online and offline times within the preset period, then the first preset communication quality parameter requirement and the second preset communication quality parameter requirement correspond to the online and offline times times threshold.
  • the second case when the first communication quality parameter and the second communication quality parameter are the number of uplink bit errors within the preset period, then the first preset communication quality parameter requirement and the second preset communication quality parameter requirement correspond to the uplink Bit Error Threshold.
  • the third case when the first communication quality parameter and the second communication quality parameter are the change values of the number of times of going online and offline within the preset period, then the first preset communication quality parameter requirement and the second preset communication quality parameter requirement correspond to The threshold for changing the number of online and offline times.
  • the fourth case when the first communication quality parameter and the second communication quality parameter are the change value of the number of uplink error codes within the preset period, then the first preset communication quality parameter requirement corresponds to the second preset communication quality parameter requirement is the change threshold of the number of uplink bit errors.
  • the first preset communication quality parameter requirement and the second preset communication quality parameter requirement may be the same, for example, when the first preset communication quality parameter requirement and the second preset communication quality parameter requirement are the number of times threshold, then the first preset communication quality parameter requirement and the second preset communication quality parameter requirement correspond to the same online and offline times threshold. Or, the first preset communication quality parameter requirement is lower than the second preset communication quality parameter requirement. For example, when the first preset communication quality parameter requirement and the second preset communication quality parameter requirement are the online and offline times threshold, then The online and offline times threshold corresponding to the first preset communication quality parameter requirement is lower than the online and offline times threshold corresponding to the second preset communication quality parameter requirement.
  • the first uplink time slot of the target leaf node is allocated by the root node according to the uplink logical channel identifier allocated by the target leaf node. Specifically, when the target leaf node is registering, the root node will assign an uplink logical channel ID to the target leaf node. Allocating the first uplink time slot, so that the target leaf node can upload data in the first uplink time slot.
  • the above-mentioned historical feature information of multiple leaf nodes includes, but is not limited to, registration feature information of multiple leaf nodes, or service feature information historically used by leaf nodes.
  • step S300 can be specifically divided into two implementation manners as shown in FIG. 5 or FIG. 6 .
  • FIG. 5 is a specific flow chart of determining the first leaf node in the fault location detection method provided by one embodiment of the present application
  • FIG. 6 is a specific flow chart of determining the first leaf node in the fault location detection method provided by another embodiment of the present application. flow chart.
  • FIG. 5 is a specific flow chart of determining the first leaf node in the fault location detection method provided by an embodiment of the present application.
  • the above step S300 includes but not limited to step S610, step S620, step S630 and step S640.
  • Step S610 controlling the target leaf node to stop uploading data in the second uplink time slot.
  • Step S620 when the uplink data is acquired in the second uplink time slot and the uplink data cannot be parsed, acquire a logical channel identifier corresponding to the target leaf node.
  • Step S630 determine the leaf node matching the logical channel ID as the first leaf node among the multiple leaf nodes, wherein the historical feature information includes the logical channel IDs of the multiple leaf nodes.
  • Step S640 controlling the target leaf node to resume uploading data.
  • the root node determines that the target leaf node is the interfered leaf node, in order to filter out the suspicious leaf nodes that are suspected of interfering with the target leaf node from other leaf nodes except the target leaf node .
  • the embodiment of the present application will disable the data upload function of the target leaf node, that is, control the target leaf node to stop uploading data in the second uplink time slot.
  • the root node will judge whether it has received the uplink data from the leaf node in the second uplink time slot. If no uplink data from the leaf node is received in the second uplink time slot, it means that the target leaf node does not have uplink logic. The problem that the channel ID is occupied; if the uplink data from the leaf node is received in the second uplink time slot, it indicates that the target leaf node has the problem that the uplink logical channel ID is occupied.
  • the root node After receiving the uplink data from the leaf node, the root node will analyze the uplink data. If the uplink data cannot be parsed, it means that the only way to find out the suspected Suspicious leaf nodes that interfere with the target leaf node. Specifically, the embodiment of the present application will obtain the logical channel ID allocated by the target leaf node, and the logical channel ID is the ID of the interfered logical channel, where the ID of the interfered logical channel can be one or more, and then the root node will use The interfered logical channel is identified as an index, and the historical feature information of multiple leaf nodes is searched, so that the first leaf node corresponding to the logical channel ID identical to the interfered logical channel ID is found in the historical feature information, wherein, The first leaf node does not include the target leaf node, and the first leaf node is a suspicious leaf node suspected of interfering with the target leaf node.
  • the above-mentioned first uplink time slot can be allocated according to preset rules, wherein the preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, target leaf node One of the bandwidth allocation rules of multiple leaf nodes before uploading data.
  • preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, target leaf node One of the bandwidth allocation rules of multiple leaf nodes before uploading data.
  • the above-mentioned second uplink time slot can also be allocated according to the above-mentioned preset rules, wherein the preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, One of the bandwidth allocation rules of multiple leaf nodes before the target leaf node stops uploading data.
  • the preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, One of the bandwidth allocation rules of multiple leaf nodes before the target leaf node stops uploading data.
  • first uplink time slot and the above-mentioned second uplink time slot may be uplink time slots with the same bandwidth, or uplink time slots with different bandwidths.
  • first uplink time slot and the second uplink time slot may be the same uplink time slot, or may be two different uplink time slots.
  • FIG. 6 is a specific flow chart of determining the first leaf node in the fault location detection method provided by another embodiment of the present application.
  • the above step S300 includes but not limited to step S710, step S720, step S730 and step S740.
  • Step S710 controlling the target leaf node to stop uploading data in the second uplink time slot.
  • Step S720 when the uplink data is acquired in the second uplink time slot and the uplink data is successfully analyzed, the characteristic parameters obtained by analyzing the uplink data are acquired.
  • Step S730 according to the characteristic parameters and historical characteristic information, determine a leaf node matching the characteristic parameters as the first leaf node among the plurality of leaf nodes, wherein the historical characteristic information includes the characteristic parameters of the plurality of leaf nodes.
  • Step S740 controlling the target leaf node to resume uploading data.
  • the root node determines that the target leaf node is the interfered leaf node, in order to filter out the suspicious leaf nodes that are suspected of interfering with the target leaf node from other leaf nodes except the target leaf node .
  • the embodiment of the present application will disable the data upload function of the target leaf node, that is, control the target leaf node to stop uploading data in the second uplink time slot.
  • the root node will judge whether it has received the uplink data from the leaf node in the second uplink time slot. If no uplink data from the leaf node is received in the second uplink time slot, it means that the target leaf node does not have uplink logic. The problem that the channel ID is occupied; if the uplink data from the leaf node is received in the second uplink time slot, it indicates that the target leaf node has the problem that the uplink logical channel ID is occupied.
  • the root node will analyze the uplink data. If the uplink data is successfully parsed, it means that the uplink data can be used as an entry point to find suspicious leaves that are suspected of interfering with the target leaf node. node.
  • the embodiment of the present application will obtain the characteristic parameters obtained by analyzing the uplink data, and then, the root node will use the analyzed characteristic parameters as an index to search in the historical characteristic information of multiple leaf nodes, so that in the historical characteristic information Find out the first leaf node corresponding to the same characteristic parameter as the characteristic parameter obtained by analysis, wherein the first leaf node does not include the target leaf node, and the first leaf node is a suspicious leaf node that is suspected of interfering with the target leaf node.
  • the determination of the leaf node matching the characteristic parameters as the first leaf node among the plurality of leaf nodes according to the characteristic parameters and historical characteristic information can be divided into the following two cases.
  • the first case when the characteristic parameter obtained by analysis is the same as the characteristic parameter currently configured for the leaf node, the leaf node is regarded as the first leaf node, that is, the suspicious leaf node.
  • the second case when the characteristic parameters obtained by analysis cannot be the same as the characteristic parameters currently configured for the leaf node, then use the characteristic parameters obtained by analysis as an index to search for matching from the characteristic parameters used by the leaf node in the past, and find the matching leaf node as the first leaf node, that is, the suspicious leaf node.
  • the historical feature information mentioned in the embodiment of the present application may include the feature information of the current configuration of the leaf node, or the feature information of the previous configuration of the leaf node.
  • the currently configured characteristic information and the previously configured characteristic information may be registered characteristic information or service characteristic information.
  • feature parameters similarly, it may also be registration feature information or service feature information.
  • the above-mentioned first uplink time slot can be allocated according to preset rules, wherein the preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, target leaf node One of the bandwidth allocation rules of multiple leaf nodes before uploading data.
  • preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, target leaf node One of the bandwidth allocation rules of multiple leaf nodes before uploading data.
  • the above-mentioned second uplink time slot can also be allocated according to the above-mentioned preset rules, wherein the preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, One of the bandwidth allocation rules of multiple leaf nodes before the target leaf node stops uploading data.
  • the preset rules include bandwidth allocation rules corresponding to the priorities of leaf nodes, fixed bandwidth allocation rules, One of the bandwidth allocation rules of multiple leaf nodes before the target leaf node stops uploading data.
  • first uplink time slot and the above-mentioned second uplink time slot may be uplink time slots with the same bandwidth, or uplink time slots with different bandwidths.
  • step S400 of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node it can be specifically divided into three implementation manners as shown in FIG. 7 to FIG. 9 .
  • Fig. 7 is a specific flow chart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by one embodiment of the present application
  • Fig. 8 is another embodiment of the present application
  • FIG. 7 is a specific flow chart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by an embodiment of the present application.
  • step S400 of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node it includes but not limited to step S810.
  • Step S810 obtain the current state of the first leaf node, and when the current state is unregistered, send registration information to the first leaf node to switch the first leaf node from the unregistered state to the registered online state, and control the first leaf node Stop uploading data within the first uplink time slot of the target leaf node.
  • FIG. 8 is a specific flow chart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by another embodiment of the present application.
  • step S400 of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node it includes but not limited to step S820.
  • Step S820 acquiring the current state of the first leaf node, and when the current state is the registered online state, controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node.
  • FIG. 9 is a specific flow chart of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node in the fault location detection method provided by another embodiment of the present application.
  • step S400 of controlling the first leaf node to stop uploading data in the first uplink time slot of the target leaf node it includes but not limited to step S830.
  • Step S830 obtaining the current state of the first leaf node, and when the current state is offline, control the first leaf node to stop uploading data in the first uplink time slot of the target leaf node.
  • an embodiment of the present application also provides a specific process for screening out the second leaf node from the first leaf node.
  • the process is specifically as follows: after screening the first leaf node in the unregistered state and the first leaf node in the registered state, if the second leaf node that interferes with the target leaf node cannot be screened out, the embodiment of the present application will filter the leaf node in the offline state The first leaf node serves as the second leaf node of the interference target leaf node.
  • FIG. 10 is a specific flow chart of subsequent uploading of characteristic parameters of the second leaf node in the method for fault location and detection provided by an embodiment of the present application.
  • the method further includes but not limited to step S910 and step S920.
  • Step S910 acquiring characteristic parameters of the second leaf node.
  • Step S920 sending the characteristic parameters of the second leaf node to the fault handling platform.
  • the root node obtains the characteristic parameters of the second leaf node, and sends the characteristic parameters of the second leaf node to the fault handling platform.
  • fault handling platform includes but not limited to network management or other operation and maintenance platforms.
  • the above characteristic parameters include but not limited to registration characteristic parameters or service characteristic parameters.
  • the embodiment of the present application is specifically described based on the xPON network in FIG. 2 .
  • the leaf nodes mentioned in the fault location detection method in Figure 4 to Figure 10 above can correspond to the ONU in the xPON network in Figure 2
  • the root node can correspond to the ONU in the xPON network in Figure 2 The OLT.
  • FIG. 11 is a flow chart of xPON network topology authorization provided by an embodiment of the present application.
  • GPON is taken as an example, and other systems are similar.
  • the GPON GTC Gigabit Pon Transmission Convergence, Gigabit Pon Transmission Convergence
  • the downstream frame indicates the permission of the upstream flow in the upstream frame through BWMAP (BandWidthmap, bandwidth mapping) Position, uplink frame and downlink frame synchronization.
  • BWMAP BandWidthmap, bandwidth mapping
  • the OLT sends pointers in PCBd, which indicate the start and end times of each ONU's upstream transmission. In this way, only one ONU can access the medium at any time, and no collision will occur under normal working conditions.
  • the pointer is in bytes, allowing the OLT to effectively control the medium statically with a bandwidth granularity of 64kbit/s. However, some OLT applications can choose a larger pointer granularity to achieve better dynamic bandwidth scheduling control.
  • the pointers in the example in Figure 11 are sent in ascending order.
  • the pointers sent by OLT to each ONU are required to be arranged in ascending order of start time, and it is recommended that all pointers be sent in ascending order of start time.
  • BWMAP is a vector array of 8-byte allocation structures, and each entry in the array represents a bandwidth allocated to a specific T-CONT.
  • the Allocation ID field is 12 bits and is used to indicate the specific T-CONT corresponding to the PON upstream authorization time.
  • the Start field is 16 bits long and is used to indicate the start time of the allocated time slot.
  • the time is in bytes, starting from 0 in the uplink frame, and the size of the uplink frame is limited to no more than 65536 bytes, which can meet the uplink rate requirement of 2.488Gb/s.
  • the End field is 16 bits long and is used to indicate the end time of the allocated time slot.
  • the time is in units of bytes, starting from 0 in the uplink frame, indicating the last valid data byte allocated this time.
  • FIG. 12 is a specific flowchart of a fault location detection method in an xPON network provided by an embodiment of the present application, including but not limited to steps S1010, step S1020, step S1030, step S1040, step S1050, step S1060, step S1070, step S1080 and step S1090.
  • step S1010 the OLT maintains the ONU historical feature information list based on the PON port, and initializes the suspicious ONU record table and the disturbing ONU record table.
  • the OLT central office equipment in the xPON network maintains the ONU historical feature information list based on the PON port.
  • the feature value in the ONU historical feature information list means that an ONU can be uniquely represented on the optical link.
  • the registration feature value includes but not limited to ONU registration MAC (Media Access Control, media access control) address, SN (Series number, serial number), LOID (Logical ONU Identifier, logical ONU identification), registration Status; service characteristic value includes but not limited to the LLID that ONU is distributed in EPON network, the AllocID that ONU is distributed in GPON network, ONU bears the weight of business MAC address, ONU bears the weight of business VLAN (Virtual LocalArea Network, dedicated virtual local area network).
  • ONU registration MAC Media Access Control, media access control
  • SN Series number, serial number
  • LOID Logical ONU Identifier, logical ONU identification
  • service characteristic value includes but not limited to the LLID that ONU is distributed in EPON network
  • the ONU historical feature information list under the PON port uses the PON port as a unit to record the registered and authenticated ONU information based on the ONU registration identifier, and record the ONU historical feature value within a certain period: the OLT updates the ONU historical feature value according to a certain strategy.
  • the OLT updates the ONU historical feature value according to a certain strategy.
  • the above-mentioned certain period includes but is not limited to artificial designation or configuration according to a certain policy.
  • the above-mentioned ONU-related characteristic values include but not limited to the logical channel identifier assigned to the ONU by the OLT.
  • the above-mentioned ONU service characteristic values include but not limited to the logical channel identifier and VLAN.
  • changes in the above-mentioned ONU service characteristic values include but are not limited to new configurations, configuration changes, and the like.
  • the ONU goes online for the first time on the OLT or the configuration data on the OLT is deleted and rebuilt, which may cause the ONU logical channel identification.
  • the ONU registration identifier mentioned above includes but not limited to MAC address, SN and so on.
  • the root node also maintains the suspicious ONU record table and the disturbing ONU record table, and records the registration and authentication information of the relevant ONU according to a certain policy; the suspicious ONU record table and the disturbing ONU record table are initialized after the OLT is powered on.
  • the above-mentioned ONU registration authentication information includes but not limited to ONU index, ONU registration information, and ONU service configuration information.
  • the ONU registration information includes but not limited to MAC, SN, LOID and so on.
  • ONU service configuration information includes, but is not limited to, explicitly or implicitly configured logical channel identifiers, service VLANs, and the like.
  • the ONU historical feature information list mentioned in FIG. 12 may correspond to the historical feature information mentioned in FIG. 4 to FIG. 10, and the feature value may correspond to feature information.
  • Step S1020 the OLT maintains the first behavior characteristic threshold and the second behavior characteristic threshold of the corresponding ONU based on the PON port.
  • the behavior characteristic of the ONU exceeds the first behavior characteristic threshold, the ONU is set as the disturbed ONU.
  • the OLT in the xPON network maintains the first behavior characteristic threshold and the second behavior characteristic threshold corresponding to the ONU based on the PON port as a unit.
  • the first behavior characteristic threshold and the second behavior characteristic threshold are set according to relevant parameters.
  • the first behavior characteristic threshold is a detection trigger threshold, and when the characteristic behavior exceeds the first behavior characteristic threshold, it is considered that a fault occurs, and the ONU is regarded as a disturbed ONU, thereby performing step S1030.
  • the second behavioral characteristic threshold is a failure recovery threshold, and when the characteristic behavior is lower than the second behavioral characteristic threshold, it is considered that the failure is recovered.
  • the relevant parameters mentioned above include but are not limited to the absolute number of online and offline times for a specific reason within a certain period of the ONU, the absolute number of upstream code errors within a certain period of the ONU, and changes in the number of online and offline times for a specific reason based on historical statistics. , Changes in the relative number of uplink bit errors based on historical statistics.
  • the above-mentioned characteristic behavior of the ONU can be queried and counted on the OLT, including but not limited to the number of online and offline times, and uplink error codes.
  • the above-mentioned behavior characteristics correspond to the above-mentioned communication quality parameters; the above-mentioned first behavior characteristic thresholds and second behavior characteristic thresholds are respectively equivalent to the above-mentioned first communication quality parameter requirements and second communication quality parameters. parameter requirements.
  • step S1030 the OLT sets a T1 timer, and controls the interfered ONU to forbid upstream light emission before T1 times out.
  • the OLT in the xPON network sets a timer T1 for the specific disturbed ONU, and prohibits the disturbed ONU from emitting light upstream before T1 times out.
  • the prohibition of the disturbed ONU’s upstream light emission before the timeout of T1 includes but is not limited to the ONU in the EPON network.
  • the OLT downstream direction shuts down the ONU upstream laser within the specified time T1 through the extended OAM protocol or requires the ONU through the MPCP protocol. Keep silent: For example, for the ONU in the GPON network, the OLT downstream direction turns off the ONU upstream laser within the specified time T1 through the PLOAM protocol.
  • Step S1040 the OLT continues to authorize the disturbed ONU, detects the authorization window signal, and judges whether the data is received. When the data is received but cannot be parsed, then step S1050 is executed; when the data is received and successfully parsed, then step S1060 is executed; If no data is received, execute step S1090.
  • the OLT in the xPON network will continue to allocate uplink time slot authorization windows according to a certain DBA rule according to the logical channel identifier configured for the disturbed ONU.
  • the OLT detects whether there is uplink data in the uplink time slot authorization window corresponding to the disturbed ONU; if T1 does not time out, it continues to allocate the uplink time slot authorization window for the specified logical channel ID according to certain DBA rules, and continues to detect until T1 times out.
  • step S1050 When a signal is detected in the above-mentioned uplink time slot grant window, but the signal data cannot be parsed, there may be an uplink logical channel interference problem, and the process goes to step S1050.
  • step S1060 When a signal is detected in the above-mentioned uplink time slot authorization window, and the signal data can be effectively analyzed, there is an uplink logic channel interference problem, then record and compare the data obtained by multiple rounds of allocation authorization windows within the T1 timeout, and analyze the data in these data ONU characteristic value, record all different characteristic values; and jump to step S1060.
  • the DBA rule refers to the allocation of the bandwidth of each ONU under the PON port according to its high priority, or according to the fixed bandwidth, or according to the last bandwidth before the disturbed ONU is powered off before T1 timeout. Stay empowered.
  • the OLT reopens the uplink laser for the disturbed ONU and authorizes it normally.
  • the above-mentioned grant window during T1 is equivalent to the above-mentioned second uplink time slot.
  • Step S1050 retrieving the historical characteristic value of the ONU, finding all the ONUs using the same logical channel identifier as the interfered ONU, as suspicious ONUs.
  • all ONUs in the ONU historical characteristic information list under the PON port that have used the upstream logical channel identifier of the interfered ONU are listed as suspicious ONUs and recorded in the suspicious ONU list.
  • the logical channel identifier of the interfered ONU is obtained, and the logical channel identifier is set as the interfered logical channel identifier. If the interfered ONU has multiple logical channel identifiers, all these logical channel identifiers are set as the interfered logical channel identifiers. Then, according to the index identified by the disturbed logical channel, the ONU historical characteristic information list is searched. Next, set all the ONUs in the ONU historical feature information list with the same logical channel IDs as the interfered logical channel IDs, and whose ONU registration information is different from the interfered ONU, as suspicious ONUs. Finally, put all suspicious ONUs into the list of suspicious ONUs.
  • Step S1060 retrieve the current characteristic value of the ONU, and find all the ONUs using the same logical channel identifier as the interfered ONU, as suspicious ONUs.
  • the embodiment of the present application will analyze the registration characteristic value or service characteristic value in the uplink data. According to the registration characteristic value or service characteristic value index, retrieve the ONU information in the ONU historical characteristic value list, find the ONU that is currently using the record with the information characteristic value, and record it into the suspicious ONU list. Or, compare the information carried in the uplink message with the ONU historical characteristic value list maintained by the OLT, and if there is an entry with matching information, record the ONU into the suspicious ONU list.
  • valid data is parsed from uplink data. Then, when the registration feature value or service feature value parsed from the valid data is the same as the registration feature value or service feature value of the ONU currently configured by the OLT, set the ONU as a suspicious ONU; When the characteristic value cannot match the ONU data currently configured by the OLT, then use the registration characteristic value or service characteristic value to index the ONU historical characteristic information list, find the corresponding matching item, and set the relevant ONU as a suspicious ONU. Finally, put all suspicious ONUs into the list of suspicious ONUs.
  • Step S1070 set the T2 timer, shut down the suspicious ONU, and observe whether the fault of the disturbed ONU disappears, and screen out the disturbing ONU that interferes with the disturbed ONU from the suspicious ONUs according to the fault condition of the disturbed ONU.
  • the OLT turns on the laser to the disturbed ONU, that is, the disturbed ONU can allocate a normal authorization for its bandwidth according to the OLT, and complete the ONU online and the transmission of uplink data.
  • the T2 timer is set according to a certain strategy, and the suspicious ONUs in the suspicious ONU list are processed, respectively as follows.
  • the suspicious ONU If the status of the suspicious ONU is unregistered, after registering the suspicious ONU, start the timer T2, turn off the upstream light of the suspicious ONU, and observe the status of the disturbed ONU, such as the registration status or upstream bit error, when its behavior characteristics
  • the suspicious ONU is an interfering ONU, which is removed from the suspicious ONU list and included in the interfering ONU list; otherwise, the suspicious ONU is deregistered again, And remove it from the suspicious ONU list.
  • the suspicious ONU is an interfering ONU, removed from the suspicious ONU list and included in the interfering ONU list, otherwise, re-open the upstream light for the suspicious ONU, and authorize normally, And remove it from the suspicious ONU list.
  • the suspicious ONU in the offline state will be removed from the list of suspicious ONUs and included in the disturbing ONU list; otherwise, remove the offline suspicious ONU from the suspicious ONU list.
  • the above-mentioned grant window during T2 is equivalent to the above-mentioned first uplink time slot.
  • Step S1080 report the interfering ONUs in the interfering ONU list to the fault handling platform, and troubleshoot.
  • the root node in the embodiment of the present application will report the interfering ONU in the above interfering ONU list to the network management or other operation and maintenance platform through an alarm message or notification message, and carry its ONU history registration authentication information table under the PON port. information, and combined with user account information for processing.
  • the OLT of the embodiment of the present application can filter out the interfering ONU that interferes with the interfered ONU from multiple ONUs, that is, the abnormal ONU, which solves the problem that the upstream logical channel of the ONU in the xPON network topology is occupied
  • the problem is realized to locate the abnormal ONU.
  • the fault location and detection method of the embodiment of the present application can solve the problem that the uplink logic channel of the ONU in the xPON network topology using the TDMA mechanism is occupied without relying on the cooperation with the ONU, and can locate the abnormal ONU.
  • the embodiment of the present application adopts a software method based on the existing hardware to realize the dynamic monitoring of the uplink logical channel occupation problem, it is simpler and more flexible, and the cost is also lower.
  • an embodiment of the present application provides a root node, where the root node includes: a memory, a processor, and a computer program stored in the memory and operable on the processor.
  • the processor and memory can be connected by a bus or other means.
  • root node in this embodiment may correspond to include the memory and the processor in the embodiment shown in Figure 3, which can constitute a part of the system architecture platform in the embodiment shown in Figure 3, and both belong to The same inventive concept, so both have the same realization principle and beneficial effect, which will not be described in detail here.
  • the non-transitory software programs and instructions required to realize the fault location and detection method of the above-mentioned embodiments are stored in the memory, and when executed by the processor, the fault location and detection method of the above-mentioned embodiment is executed, for example, executing the above-described FIG. 4 Method steps S100 to S500, method steps S610 to S640 in Fig. 5, method steps S710 to S740 in Fig. 6, method steps S810 in Fig. 7, method steps S820 in Fig. 8, method steps S830 in Fig. 9 , method steps S910 to S920 in FIG. 10 , and method steps S1010 to S1090 in FIG. 12 .
  • an embodiment of the present application provides a topology of a communication system, which includes multiple leaf nodes and the aforementioned root node, and the root node communicates with the multiple leaf nodes.
  • an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are used to execute the above-mentioned method for fault location and detection, for example, execute Method steps S100 to S500 in Fig. 4 described above, method steps S610 to S640 in Fig. 5, method steps S710 to S740 in Fig. 6, method steps S810 in Fig. 7, method steps S820 in Fig. 8, Fig. Method step S830 in 9, method steps S910 to S920 in FIG. 10 , method steps S1010 to S1090 in FIG. 12 .
  • the embodiment of the present application includes: the root node in the communication system topology obtains the first communication quality parameter of the target leaf node, wherein the above-mentioned target leaf node is one of the multiple leaf nodes in the communication system topology; when the first If the communication quality parameter does not meet the requirements of the first preset communication quality parameter, the root node will obtain the historical feature information of a plurality of the leaf nodes, and determine the suspected interference with the target in the plurality of leaf nodes according to the historical feature information The first leaf node of the leaf node; then, the root node will control the first leaf node to stop uploading data in the first uplink time slot of the target leaf node, and obtain the first uplink time slot of the target leaf node The second communication quality parameter in the time slot; when the second communication quality parameter meets the second preset communication quality parameter requirement, the root node will determine that the first leaf node is the second leaf node that interferes with the target leaf node .
  • the root node of the embodiment of the present application can filter out the second leaf node that causes interference to the target leaf node, that is, the abnormal leaf node, and solve the PToMP communication using the TDMA mechanism.
  • the problem that the uplink logic channel of the leaf node in the system topology is occupied has realized the location of the abnormal leaf node.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种故障定位检测方法、根节点、通信系统拓扑和存储介质，根节点获取目标叶子节点的第一通信质量参数(S100)，当第一通信质量参数不满足第一预设通信质量参数要求，获取多个叶子节点的历史特征信息(S200)，并根据历史特征信息在多个叶子节点中确定疑似干扰目标叶子节点的第一叶子节点(S300)；然后控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，获取目标叶子节点在第一上行时隙内的第二通信质量参数(S400)；当第二通信质量参数满足第二预设通信质量参数要求，确定第一叶子节点为干扰目标叶子节点的第二叶子节点(S500)。

Description

故障定位检测方法、根节点、通信系统拓扑和存储介质
相关申请的交叉引用
本申请基于申请号为202110685578.5，申请日为2021年06月21日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于通信技术领域，尤其涉及一种故障定位检测方法、根节点、通信系统拓扑和计算机可读存储介质。
背景技术
对于PToMP(Point To MultiPoint，点到多点)通信架构系统，包括有一个根节点和多个叶子节点。当上述的PToMP通信架构系统采用TDMA(Time Division Multiple Access，时分多址)机制时，在正常情况下，根节点会给不同的叶子节点分配不同的上行逻辑通道标识，并且根节点会根据上行逻辑通道标识分配不同的上行带宽时隙供叶子节点上传数据。但是，由于上行逻辑通道标识采用动态分配机制，因此根节点可能将一个上行逻辑通道标识在前次分配叶子节点失效如离线的情况下，会将该上行逻辑通道标识重复分配给其他的叶子节点。由于前次分配该上行逻辑通道标识的叶子节点可能在其失效情况下未正常释放该上行逻辑通道标识，从而会导致出现上行逻辑通道标识重复的问题。换句话说，当某个叶子节点由于异常没有按照根节点要求释放上行逻辑通道标识时，若根节点再次将该上行逻辑通道标识分配给其他叶子节点，就会造成叶子节点的上行逻辑通道标识冲突的情况，进而会使得异常叶子节点对正常叶子节点的上行数据造成干扰。
对此，为了解决干扰问题，需要先对异常叶子节点进行定位。但是，在定位期间往往存在如下两种情况：第一，由于不同叶子节点的状态差异如信号强度差异或带宽差异，在上行逻辑通道占用情况下表现形式不同，且由于叶子节点本身可能存在非稳态特性，因此检测上行逻辑通道标识占用问题存在难度；第二，对于上行逻辑通道标识的动态分配机制，上行逻辑通道标识占用问题是隐性存在的，因此定位出现上行逻辑通道标识占用的叶子节点存在难度。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种故障定位检测方法、根节点、通信系统拓扑和计算机可读存储介质。
第一方面，本申请实施例提供了一种故障定位检测方法，应用于通信系统拓扑中的根节点，所述通信系统拓扑还包括与所述根节点通信的多个叶子节点，所述方法包括：获取目标叶子节点的第一通信质量参数，其中，所述目标叶子节点为多个所述叶子节点中的一个；当所述第一通信质量参数不满足第一预设通信质量参数要求，获取多个所述叶子节点的历史特 征信息；根据所述历史特征信息在多个所述叶子节点中确定疑似干扰所述目标叶子节点的第一叶子节点；控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据，并获取所述目标叶子节点在所述第一上行时隙内的第二通信质量参数；当所述第二通信质量参数满足第二预设通信质量参数要求，确定所述第一叶子节点为干扰所述目标叶子节点的第二叶子节点。
第二方面，本申请实施例还提供了一种根节点，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上述第一方面所述的故障定位检测方法。
第三方面，本申请实施例还提供了一种通信系统拓扑，包括多个叶子节点和如上述第二方面所述的根节点，所述根节点与多个所述叶子节点通信。
第四方面，本申请实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如上述第一方面所述的故障定位检测方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的PToMP通信系统拓扑的示意图；
图2是本申请一个实施例提供的xPON网络的示意图；
图3是本申请一个实施例提供的用于执行故障定位检测方法的系统架构平台的示意图；
图4是本申请一个实施例提供的故障定位检测方法的流程图；
图5是本申请一个实施例提供的故障定位检测方法中确定第一叶子节点的具体流程图；
图6是本申请另一个实施例提供的故障定位检测方法中确定第一叶子节点的具体流程图；
图7是本申请一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图；
图8是本申请另一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图；
图9是本申请又一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图；
图10是本申请一个实施例提供的故障定位检测方法中后续上传第二叶子节点的特征参数的具体流程图；
图11是本申请一个实施例提供的xPON网络拓扑授权流程图；
图12是本申请一个实施例提供的xPON网络中的故障定位检测方法的具体流程图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于 限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书、权利要求书或上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
如图1所示，图1是本申请一个实施例提供的PToMP通信系统拓扑的示意图。对于图1中的PToMP通信架构系统，包括有根节点110和与根节点110通信的多个叶子节点120。当图1中的PToMP通信架构系统采用TDMA机制时，在正常情况下，根节点110会给不同的叶子节点120动态分配不同的上行逻辑通道标识，并且根节点110会根据上行逻辑通道标识分配不同的上行带宽时隙供叶子节点120上传数据。但是，由于上行逻辑通道标识采用动态分配机制，因此根节点可能将一个上行逻辑通道标识在前次分配叶子节点失效如离线的情况下，会将该上行逻辑通道标识重复分配给其他的叶子节点。由于前次分配该上行逻辑通道标识的叶子节点可能在其失效情况下未正常释放该上行逻辑通道标识，从而会导致出现上行逻辑通道标识重复的问题。换句话说，当某个叶子节点由于异常没有按照根节点要求释放上行逻辑通道标识时，若根节点再次将该上行逻辑通道标识分配给其他叶子节点，就会造成叶子节点的上行逻辑通道标识冲突的情况，进而会使得异常叶子节点120对正常叶子节点120的上行数据造成干扰。
需要说明的是，关于上述采用TDMA机制的PToMP通信系统拓扑，可以是接入网中采用TDMA机制的PON(Passive Optical Network，无源光网络)通信系统，具体地，根节点110可以对应为PON通信系统中的OLT(Optical Line Terminal，光线路终端)，叶子节点120可以对应为PON通信系统中的ONU(Optical Network Unit，光网络单元)或者ONT(Optical Network Termination，光网络终端)。此外，上述采用TDMA机制的通信系统拓扑，还可以是采用TDMA机制的其他网络架构或者是采用TDMA机制的多个终端设备，本申请实施例不作任何限定。
具体地，为了能够更加清晰地描述采用TDMA机制的PToMP通信架构拓扑中的上行逻辑通道标识被占用的情况，举例说明，本申请实施例以接入网中采用TDMA机制的PON通信系统为例，进行详细说明。
可以理解的是，基于TDMA机制的无源光网络设备根据工作机制可以分为EPON(Ethernet Passive Optical Network，基于以太网的无源光网络设备)、G-PON(Gigabit-capable Passive Optical Network，千兆无源光网络设备)以及其它工作机制的无源光网络设备；上述这些无源光网络设备系统构架一致，均包含OLT和ONU，本申请实施例将上述PON技术统称为xPON。
如图2所示，图2是本申请一个实施例提供的xPON网络的示意图。对于图2中的xPON网络，包括EMS(Element Management Server，网管服务器)210、OLT220、ODN(Optical Distribution Network，光分配网络)230和多个ONU240。其中，OLT220作为中心局端设备通过ODN230网络连接汇聚多个ONU240；ONU240用于实现用户业务的接入，从而实现数据业务和配置管理等功能。另外，可以理解的是，从OLT220到ONU240的传输方向为下行方向，下行方向采用广播方式发送数据，最后由ONU240根据数据标识判断数据是否有效并决定接收或丢弃；从ONU240到OLT220的传输方向为上行方向，上行方向采用TDMA方式发送数据，ONU240基于逻辑通道标识根据OLT的上行授权发送数据，并由OLT判断数据是否有效并决定 接收或丢弃。
对于图2中的xPON网络的带宽授权机制，具体如下：在ONU240注册完成后，OLT220与ONU240之间会周期性进行带宽授权，具体由OLT220基于ONU标识向每个ONU240发送普通授权，只有标识相符的ONU240可以响应并根据授权要求发送报告，接着OLT220根据ONU240上报的报告帧，在下一周期通过授权帧为ONU240分配新的带宽，接着上行逻辑通道标识相符的ONU在授权帧指定的时间内发送数据。当ON240U删除后，被删除的ONU240的上行逻辑通道标识会被OLT重新分配给其他新接入ONU240，即ONU240上行逻辑通道标识采用动态分配机制。
可以理解的是，关于上述的由OLT220基于ONU标识向每个ONU240发送普通授权，可以但不限于是EPON系统中的MPCP GATE帧，或者GPON系统中的GTC/BWmap帧。另外，关于上述的ONU响应并根据授权要求而发送的报告，可以但不限于是EPON系统中的MPCP report帧，或者GPON系统中的PLOAMu/DBRu帧。
需要说明的是，关于上述的ONU240上行逻辑通道标识，是在ONU240注册时由OLT220统一分配，并在ONU240注册成功后由OLT220按ONU240上行逻辑通道标识分配不同的上行带宽时隙。对于xPON网络，在OLT220控制下以PON口为单位为每个ONU240根据其业务配置为其分配一个或多个在该PON口上唯一的逻辑通道标识作为ONU240的上行通道时隙标识，用于ONU240只在OLT220分配的上行时隙中转发数据。
可以理解的是，关于上述的上行通道时隙标识，在EPON系统中，上行通道时隙标识对应为LIID(Logical Link Identifier，逻辑链接标识符)；在GPON系统中，上行通道时隙标识对应为AllocID(Allocate Identifier，分配标识)。
基于图2的xPON网络，当图2中的xPON网络采用TDMA接入方式时，会周期性启动注册流程，在注册周期中只有未注册的新接入ONU240可以响应OLT220发出的注册授权帧，并由OLT220为其分配唯一的ONU标识，通过交互最终由ONU240发出注册完成帧完成整个注册过程。即在上述xPON网络中的ONU240注册与正常工作的带宽分配中，ONU240只有在OLT220的授权时间内打开光模块的上行发光，并响应OLT220的各种消息。在授权时间片未到或关闭后，ONU240必须关闭光模块的上行发光，只能监听OLT220下行消息，并根据下行消息头中的ONU标识进接受或丢弃。
可以理解的是，关于上述的注册授权帧，可以但不限于是EPON系统中的MPCP发现GATE帧，或者是GPON系统中的DS Frame with valid Psync帧。另外，关于上述的ONU标识，可以但不限于是EPON系统中的LLID，或者是GPON系统中的ONU ID。另外，关于上述的注册完成帧，可以但不限于是EPON系统中ONU240发出的MPCP register ack帧，或者是GPON系统中ONU240发出的Serial_Number_ONU或Password帧。
在上述xPON网络中，由于上行逻辑通道标识采用动态分配机制，当OLT220回收某ONU240的上行逻辑通道标识，而该ONU240即异常ONU240由于某种异常而未正确释放原来由OLT220分配给其的上行逻辑通道标识，且OLT220将该上行逻辑通道标识重新分配给同链路上的其他正常ONU240。这种情况下可能存在两个ONU240在同一个上行逻辑通道标识标记的上行带宽时隙中发送数据，也即未正确释放上行逻辑通道标识的异常ONU240对被OLT220分配该上行逻辑通道标识的正常ONU240的上行数据产生干扰，即上行逻辑通道占用。
当异常ONU240非法占用OLT220设备分配的上行逻辑通道标识后，会直接影响OLT220正 常分配上行逻辑通道标识的ONU240与OLT220设备之间的交互，并导致被正常分配上行逻辑通道标识的ONU240的上行业务产生丢包，严重时掉线，对业务造成严重影响，包括如下两个方面。
第一方面：由于不同ONU240状态差异，如信号强度差异或者带宽差异，在上行逻辑通道占用情况下表现形式不同，且由于ONU240本身的非稳态特性，因此检测上行逻辑通道标识占用问题存在难度。
第二方面：在逻辑通道标识的动态分配机制中，逻辑通道标识占用问题是隐性存在的，因此定位出现上行逻辑通道标识占用的异常ONU240存在难度。
为此，出现上述问题是由于异常ONU240软硬件工作异常并导致采用TDMA工作方式的xPON网络中的OLT220的上行逻辑通道标识分配管理使用出现异常，且对OLT220正常分配此上行逻辑通道标识的ONU240造成干扰。
基于上述情况，本申请实施例提供了一种故障定位检测方法、根节点、通信系统拓扑和计算机可读存储介质，其中，故障定位检测方法包括但不限于如下步骤：通信系统拓扑中的根节点会获取目标叶子节点的第一通信质量参数，其中，上述的目标叶子节点为通信系统拓扑中多个叶子节点中的一个；当第一通信质量参数不满足第一预设通信质量参数要求，根节点会获取多个叶子节点的历史特征信息，并根据历史特征信息在多个叶子节点中确定疑似干扰目标叶子节点的第一叶子节点；接着，根节点会控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，并且获取目标叶子节点在第一上行时隙内的第二通信质量参数；当第二通信质量参数满足第二预设通信质量参数要求，根节点会确定第一叶子节点为干扰目标叶子节点的第二叶子节点。根据本申请实施例的技术方案，本申请实施例的根节点能够从多个叶子节点中筛选出对目标叶子节点造成干扰的第二叶子节点，即异常叶子节点，解决了PToMP通信系统拓扑中叶子节点的上行逻辑通道被占用的问题，实现了对异常叶子节点进行定位。
下面结合附图，对本申请实施例作进一步阐述。
如图3所示，图3是本申请一个实施例提供的用于执行故障定位检测方法的系统架构平台300的示意图。
在图3的示例中，该系统架构平台300设置有处理器310和存储器320，其中，处理器310和存储器320可以通过总线或者其他方式连接，图3中以通过总线连接为例。
存储器320作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外，存储器320可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器320可包括相对于处理器310远程设置的存储器，这些远程存储器可以通过网络连接至该系统架构平台。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本领域技术人员可以理解的是，该系统架构平台可以应用于3G通信网络系统、LTE通信网络系统、5G通信网络系统以及后续演进的移动通信网络系统等，本实施例对此并不作具体限定。
本领域技术人员可以理解的是，图3中示出的系统架构平台并不构成对本申请实施例的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
在图3所示的系统架构平台中，处理器310可以调用储存在存储器320中的故障定位检测程序，从而执行故障定位检测方法。
基于上述系统架构平台，下面提出本申请的故障定位检测方法的各个实施例。
如图4所示，图4是本申请一个实施例提供的故障定位检测方法的流程图，该故障定位检测方法应用于通信系统拓扑中的根节点，其中通信系统拓扑还包括与根节点通信的多个叶子节点，该故障定位检测方法包括但不限于有步骤S100、步骤S200、步骤S300、步骤S400和步骤S500。
步骤S100、获取目标叶子节点的第一通信质量参数，其中，目标叶子节点为多个叶子节点中的一个。
步骤S200、当第一通信质量参数不满足第一预设通信质量参数要求，获取多个叶子节点的历史特征信息。
步骤S300、根据历史特征信息在多个叶子节点中确定疑似干扰目标叶子节点的第一叶子节点。
步骤S400、控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，并获取目标叶子节点在第一上行时隙内的第二通信质量参数。
步骤S500、当第二通信质量参数满足第二预设通信质量参数要求，确定第一叶子节点为干扰目标叶子节点的第二叶子节点。
具体地，在采用TDMA机制的PToMP通信架构拓扑中，根节点会获取目标叶子节点的第一通信质量参数，并将第一通信质量参数和第一预设通信质量参数要求进行比较，当第一通信质量参数不满足第一预设通信质量参数要求，即表明目标叶子节点收到了其他叶子节点的干扰，该目标叶子节点即为被干扰叶子节点。接着根节点会获取多个叶子节点的历史特征信息，并基于对多个叶子节点的历史特征信息的分析，从而在除去目标叶子节点的多个叶子节点中确定到疑似干扰目标叶子节点的第一叶子节点，即第一叶子节点为可疑叶子节点。当筛选出第一叶子节点之后，根节点会控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，并且获取目标叶子节点在第一上行时隙内的第二通信质量参数，换句话说，即在尝试关闭第一叶子节点的期间，观察目标叶子节点的通信质量会不会得到恢复。当第二通信质量参数满足第二预设通信质量参数要求，即若目标叶子节点的通信质量在第一叶子节点的关闭期间得到恢复，则表明所停止上传数据的第一叶子节点就是对目标叶子节点造成干扰的干扰叶子节点，从而根节点会确定第一叶子节点为干扰目标叶子节点的第二叶子节点，即该第一叶子节点为干扰叶子节点。相反，当第二通信质量参数不满足第二预设通信质量参数要求，即若目标叶子节点的通信质量在第一叶子节点的关闭期间没有得到恢复，则表明所停止上传数据的第一叶子节点并不是对目标叶子节点造成干扰的干扰叶子节点。
根据本申请实施例的技术方案，本申请实施例的根节点能够从多个叶子节点中筛选出对目标叶子节点造成干扰的第二叶子节点，即异常叶子节点，解决了PToMP通信系统拓扑中叶子节点的上行逻辑通道被占用的问题，实现了对异常叶子节点进行定位。另外，本申请实施例的故障定位检测方法，能够不依赖与叶子节点的配合，解决了采用TDMA机制的PToMP通信架构拓扑中的叶子节点的上行逻辑通道被占用的问题，并对异常叶子节点进行定位。另外，由于本申请实施例是在现有硬件基础上采取软件方式来实现对上行逻辑通道被占用问题的动态监控，更加简单和灵活，并且成本也较低。
需要说明的是，关于上述的第一通信质量参数，可以但不限于是目标叶子节点在预设周期内的上下线次数、目标叶子节点在预设周期内的上行误码数、目标叶子节点在在预设周期内的上下线次数变化值、或者目标叶子节点在在预设周期内的上行误码数变化值。
另外，需要说明的是，关于上述的第二通信质量参数，可以但不限于是目标叶子节点在预设周期内的上下线次数、目标叶子节点在预设周期内的上行误码数、目标叶子节点在在预设周期内的上下线次数变化值、或者目标叶子节点在在预设周期内的上行误码数变化值。
另外，可以理解的是，关于上述的第一预设通信质量参数要求和第二预设通信质量参数要求，包括但不限于如下四种情况。
第一种情况：当第一通信质量参数和第二通信质量参数为在预设周期内的上下线次数，那么第一预设通信质量参数要求和第二预设通信质量参数要求对应为上下线次数阈值。
第二种情况：当第一通信质量参数和第二通信质量参数为在预设周期内的上行误码数，那么第一预设通信质量参数要求和第二预设通信质量参数要求对应为上行误码数阈值。
第三种情况：当第一通信质量参数和第二通信质量参数为在预设周期内的上下线次数变化值，那么第一预设通信质量参数要求和第二预设通信质量参数要求对应为上下线次数变化阈值。
第四种情况：当第一通信质量参数和第二通信质量参数为在预设周期内的上行误码数变化值，那么第一预设通信质量参数要求和第二预设通信质量参数要求对应为上行误码数变化阈值。
需要说明的是，第一预设通信质量参数要求和第二预设通信质量参数要求可以相同，举例说明，当第一预设通信质量参数要求和第二预设通信质量参数要求为上下线次数阈值，那么第一预设通信质量参数要求和第二预设通信质量参数要求所对应的上下线次数阈值一致。或者，第一预设通信质量参数要求要低于第二预设通信质量参数要求，举例说明，当第一预设通信质量参数要求和第二预设通信质量参数要求为上下线次数阈值，那么第一预设通信质量参数要求对应的上下线次数阈值要低于第二预设通信质量参数要求所对应的上下线次数阈值。
值得注意的是，关于上述目标叶子节点的第一上行时隙，是由根节点根据目标叶子节点所分配的上行逻辑通道标识进行分配的。具体地，目标叶子节点在注册时，根节点会为目标叶子节点分配上行逻辑通道标识，在目标叶子节点完成注册后，根节点还会根据目标叶子节点所分配的上行逻辑通道标识对目标叶子节点分配第一上行时隙，使得目标叶子节点能够在第一上行时隙内上传数据。
另外，需要说明的是，关于上述的多个叶子节点的历史特征信息，包括但不限于是多个叶子节点的注册特征信息，或者是叶子节点历史采用过的业务特征信息。
另外，对于上述步骤S300，可以具体分为图5或者图6两种实施方式。其中，图5是本申请一个实施例提供的故障定位检测方法中确定第一叶子节点的具体流程图；图6是本申请另一个实施例提供的故障定位检测方法中确定第一叶子节点的具体流程图。
如图5所示，图5是本申请一个实施例提供的故障定位检测方法中确定第一叶子节点的具体流程图。对于上述步骤S300，包括但不限于有步骤S610、步骤S620、步骤S630和步骤S640。
步骤S610、控制目标叶子节点在第二上行时隙内停止上传数据。
步骤S620、当在第二上行时隙内获取到上行数据并且无法解析上行数据，获取与目标叶子节点对应的逻辑通道标识。
步骤S630、根据逻辑通道标识和历史特征信息，在多个叶子节点中确定与逻辑通道标识匹配的叶子节点作为第一叶子节点，其中，历史特征信息包括多个叶子节点的逻辑通道标识。
步骤S640、控制目标叶子节点恢复上传数据。
具体地，在采用TDMA机制的PToMP通信架构拓扑中，当根节点确定目标叶子节点为被干扰叶子节点之后，为了在除去目标叶子节点的其他叶子节点中筛选出疑似干扰目标叶子节点的可疑叶子节点。
首先，本申请实施例会关闭目标叶子节点的数据上传功能，即控制目标叶子节点在第二上行时隙内停止上传数据。
接着，根节点会在第二上行时隙内判断是否接收到来自叶子节点的上行数据，若在第二上行时隙内没有接收到来自叶子节点的上行数据，即表明目标叶子节点不存在上行逻辑通道标识被占用的问题；若在第二上行时隙内接收到来自叶子节点的上行数据，即表明目标叶子节点存在上行逻辑通道标识被占用的问题。
然后，当接收到来自叶子节点的上行数据之后，根节点会对上行数据进行解析，若无法解析该上行数据，则表明唯有以目标叶子节点所分配的逻辑通道标识为切入点，查找出疑似干扰目标叶子节点的可疑叶子节点。具体地，本申请实施例会获取目标叶子节点所分配的逻辑通道标识，该逻辑通道标识为被干扰逻辑通道标识，其中，该被干扰逻辑通道标识可以为一个或多个，然后，根节点会以被干扰逻辑通道标识为索引，在多个叶子节点的历史特征信息中进行查找，从而在历史特征信息中查找出与被干扰逻辑通道标识相同的逻辑通道标识所对应的第一叶子节点，其中，该第一叶子节点不包括目标叶子节点，该第一叶子节点即为疑似干扰目标叶子节点的可疑叶子节点。
需要说明的是，关于上述的第一上行时隙，可以按照预设规则进行分配，其中，预设规则包括与叶子节点的优先级对应的带宽分配规则、固定带宽分配规则、目标叶子节点在停止上传数据之前多个叶子节点的带宽分配规则中的一种。
另外，可以理解的是，关于上述的第二上行时隙，也可以按照上述的预设规则进行分配，其中，预设规则包括与叶子节点的优先级对应的带宽分配规则、固定带宽分配规则、目标叶子节点在停止上传数据之前多个叶子节点的带宽分配规则中的一种。
另外，值得注意的是，上述的第一上行时隙和上述的第二上行时隙，可以是带宽相同的上行时隙，也可以是带宽不同的上行时隙。另外，第一上行时隙和第二上行时隙可以是同一个上行时隙，或者，也可以是两个不同的上行时隙。
如图6所示，图6是本申请另一个实施例提供的故障定位检测方法中确定第一叶子节点的具体流程图。对于上述步骤S300，包括但不限于有步骤S710、步骤S720、步骤S730和步骤S740。
步骤S710、控制目标叶子节点在第二上行时隙内停止上传数据。
步骤S720、当在第二上行时隙内获取到上行数据并且成功解析上行数据，获取由上行数据解析得到的特征参数。
步骤S730、根据特征参数和历史特征信息，在多个叶子节点中确定与特征参数匹配的叶子节点作为第一叶子节点，其中，历史特征信息包括多个叶子节点的特征参数。
步骤S740、控制目标叶子节点恢复上传数据。
具体地，在采用TDMA机制的PToMP通信架构拓扑中，当根节点确定目标叶子节点为被干扰叶子节点之后，为了在除去目标叶子节点的其他叶子节点中筛选出疑似干扰目标叶子节点的可疑叶子节点。
首先，本申请实施例会关闭目标叶子节点的数据上传功能，即控制目标叶子节点在第二上行时隙内停止上传数据。
接着，根节点会在第二上行时隙内判断是否接收到来自叶子节点的上行数据，若在第二上行时隙内没有接收到来自叶子节点的上行数据，即表明目标叶子节点不存在上行逻辑通道标识被占用的问题；若在第二上行时隙内接收到来自叶子节点的上行数据，即表明目标叶子节点存在上行逻辑通道标识被占用的问题。
然后，当接收到来自叶子节点的上行数据之后，根节点会对上行数据进行解析，若成功解析该上行数据，则表明能够以该上行数据为切入点，查找出疑似干扰目标叶子节点的可疑叶子节点。具体地，本申请实施例会获取由上行数据解析得到的特征参数，然后，根节点会以解析得到的特征参数为索引，在多个叶子节点的历史特征信息中进行查找，从而在历史特征信息中查找出与解析得到的特征参数相同的特征参数所对应的第一叶子节点，其中，该第一叶子节点不包括目标叶子节点，该第一叶子节点即为疑似干扰目标叶子节点的可疑叶子节点。
需要说明的是，关于上述根据特征参数和历史特征信息，在多个叶子节点中确定与特征参数匹配的叶子节点作为第一叶子节点，可以分为如下两种情况。
第一种情况：当解析得到的特征参数与叶子节点当前配置的特征参数相同，则将该叶子节点作为第一叶子节点，即可疑叶子节点。
第二种情况：当解析得到的特征参数无法与叶子节点当前配置的特征参数相同，则以解析得到的特征参数为索引，从叶子节点以往使用过的特征参数进行匹配查找，找到相匹配的叶子节点作为第一叶子节点，即可疑叶子节点。
值得注意的是，对于上述两种情况，本申请实施例中所提及的历史特征信息，可以包括叶子节点当前配置的特征信息，也可以包括叶子节点以往配置的特征信息。关于当前配置的特征信息和以往配置的特征信息，可以是注册特征信息或者业务特征信息。
另外，关于上述的特征参数，同样地，也可以是注册特征信息或者业务特征信息。
需要说明的是，关于上述的第一上行时隙，可以按照预设规则进行分配，其中，预设规则包括与叶子节点的优先级对应的带宽分配规则、固定带宽分配规则、目标叶子节点在停止上传数据之前多个叶子节点的带宽分配规则中的一种。
另外，可以理解的是，关于上述的第二上行时隙，也可以按照上述的预设规则进行分配，其中，预设规则包括与叶子节点的优先级对应的带宽分配规则、固定带宽分配规则、目标叶子节点在停止上传数据之前多个叶子节点的带宽分配规则中的一种。
另外，值得注意的是，上述的第一上行时隙和上述的第二上行时隙，可以是带宽相同的上行时隙，也可以是带宽不同的上行时隙。
另外，对于上述步骤S400中的控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，可以具体分为图7至图9三种实施方式。其中，图7是本申请一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具 体流程图；图8是本申请另一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图；图9是本申请又一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图。
如图7所示，图7是本申请一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图。对于上述步骤S400中的控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，包括但不限于有步骤S810。
步骤S810、获取第一叶子节点的当前状态，当当前状态为未注册状态，发送注册信息至第一叶子节点以使第一叶子节点由未注册状态切换为注册在线状态，并控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据。
如图8所示，图8是本申请另一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图。对于上述步骤S400中的控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，包括但不限于有步骤S820。
步骤S820、获取第一叶子节点的当前状态，当当前状态为注册在线状态，控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据。
如图9所示，图9是本申请另一个实施例提供的故障定位检测方法中控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据的具体流程图。对于上述步骤S400中的控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据，包括但不限于有步骤S830。
步骤S830、获取第一叶子节点的当前状态，当当前状态为离线状态，控制第一叶子节点在目标叶子节点的第一上行时隙内停止上传数据。
另外，本申请一个实施例还提供了从第一叶子节点中筛选出第二叶子节点的具体流程。该流程具体如下：对未注册状态的第一叶子节点以及注册状态的第一叶子节点进行筛选之后，若仍然无法筛选出干扰目标叶子节点的第二叶子节点，则本申请实施例会将离线状态的第一叶子节点作为干扰目标叶子节点的第二叶子节点。
另外，如图10所示，图10是本申请一个实施例提供的故障定位检测方法中后续上传第二叶子节点的特征参数的具体流程图。在上述步骤S500之后，该方法还包括但不限于有步骤S910和步骤S920。
步骤S910、获取第二叶子节点的特征参数。
步骤S920、将第二叶子节点的特征参数发送至故障处理平台。
具体地，当根节点定位到干扰目标叶子节点的第二叶子节点之后，根节点会获取第二叶子节点的特征参数，并将将第二叶子节点的特征参数发送至故障处理平台。
可以理解的是，关于上述的故障处理平台，包括但不限于网管或其他运维平台。
另外，可以理解的是，关于上述的特征参数，包括但不限于注册特征参数或业务特征参数。
为了能够更加清晰地描述图4至图10中的故障定位检测方法，举例说明，本申请实施例基于图2中的xPON网络进行具体说明。对于图2的xPON网络，上述图4至图10中的故障定位检测方法所提及的叶子节点可以对应为图2的xPON网络中的ONU，其次，根节点可以对应为图2的xPON网络中的OLT。
结合图2和图4至图10，具体地，如图11所示，图11是本申请一个实施例提供的xPON 网络拓扑授权流程图，以GPON为例，其他系统类似。
具体地，GPON GTC(Gigabit Pon Transmission Convergence,千兆无源光网络传输汇聚)系统为上行业务流提供媒质接入控制：下行帧通过BWMAP(BandWidthmap，带宽映射)指示上行流在上行帧中的允许位置，上行帧和下行帧同步。
OLT在PCBd中发送指针，这些指针指示了每个ONU上行发送的开始和结束时间。这样在任意时刻只有一个ONU可以访问媒质，在正常工作状态下不会发生碰撞。指针以字节为单位，允许OLT以带宽粒度为64kbit/s对媒质进行有效的静态控制。然而，一些OLT应用可以选择更大的指针粒度来实现更好的动态带宽调度控制。图11示例中的指针以升序发送。要求OLT向各ONU发送的指针按开始时间的升序排列，建议所有指针都按其开始时间的升序发送。
BWMAP是8字节分配结构的向量数组，数组中的每个入口代表分配给某个特定T-CONT的一个带宽。
Allocation ID域为12比特，用于指示PON上行流授权时间对应的特定T-CONT。
Start域长16bit，用于指示分配时隙的开始时间。该时间以字节为单位，在上行帧中从0开始，并且限制上行帧的大小不超过65536字节，可满足2.488Gb/s的上行速率要求。
End域长16bit，用于指示分配时隙的结束时间。该时间以字节为单位，在上行帧中从0开始，指出此次分配的最后一个有效数据字节。
另外，结合图2、图4至图10和图11，如图12所示，图12是本申请一个实施例提供的xPON网络中的故障定位检测方法的具体流程图，包括但不限于有步骤S1010、步骤S1020、步骤S1030、步骤S1040、步骤S1050、步骤S1060、步骤S1070、步骤S1080和步骤S1090。
步骤S1010、OLT基于PON口为单位维护ONU历史特征信息列表，并初始化可疑ONU记录表以及干扰ONU记录表。
具体地，xPON网络中的OLT局端设备基于PON口为单位维护ONU历史特征信息列表，其中，ONU历史特征信息列表中的特征值是指在光链路上可唯一表征一个ONU与注册或业务相关的特征值，其中，注册特征值包括但不限于ONU注册MAC(Media Access Control，媒体接入控制)地址、SN(Series number，序列号)、LOID(Logical ONU Identifier，逻辑ONU标识)、注册状态；业务特征值包括但不限于在EPON网络中ONU被分配的LLID、在GPON网络中ONU被分配的AllocID、ONU承载业务MAC地址、ONU承载业务VLAN(Virtual LocalArea Network，专用虚拟局域网)。
PON口下ONU历史特征信息列表以PON口为单位基于ONU注册标识记录注册认证的ONU信息，记录一定周期内的ONU历史特征值：OLT根据一定策略更新ONU历史特征值，当ONU第一次上线后，以ONU相关特征值为索引，将相关特征值记入特征信息列表；并在获取ONU业务特征值记录入特征值列表的过程中，当其ONU业务特征值发生变化，则将变更值记录入特征信息列表。
可以理解的是，关于上述所提及的一定周期，包括但不限于人为指定或者根据一定策略配置等。另外，关于上述所提及的ONU相关特征值，包括但不限于OLT分配给ONU的逻辑通道标识，另外，关于上述所提及的ONU业务特征值，包括但不限于逻辑通道标识、VLAN。另外，关于上述所提及的ONU业务特征值发生变化，包括但不限于新增配置、变更配置等。
其中，对于新ONU，包括但不限于基于ONU注册标识的ONU在OLT第一次上线或在OLT上配置数据被删除重建等可能引起ONU逻辑通道标识的情况。
可以理解的是，关于上述所提及的ONU注册标识，包括但不限于MAC地址、SN等。
另外，根节点还会维护可疑ONU记录表与干扰ONU记录表，分别根据一定策略记录相关ONU的注册认证信息；OLT上电后初始化该可疑ONU记录表与干扰ONU记录表。
可以理解的是，关于上述所提及的ONU的注册认证信息，包括但不限于ONU索引、ONU注册信息、ONU业务配置信息。其中，ONU注册信息包括但不限于MAC、SN、LOID等。ONU业务配置信息包括但不限于显式或隐性配置的逻辑通道标识、业务VLAN等。
结合图2和图4至图10，具体地，图12中所提及的ONU历史特征信息列表可以对应于图4至图10中所提及的历史特征信息，特征值可以对应特征信息。
步骤S1020、OLT基于PON口为单位维护对应ONU的第一行为特征阈值和第二行为特征阈值，当ONU的行为特征超过第一行为特征阈值，则将该ONU置为被干扰ONU。
具体地，xPON网络中的OLT基于PON口为单位维护对应ONU的第一行为特征阈值和第二行为特征阈值。第一行为特征阈值和第二行为特征阈值根据相关参数而设定。其中，第一行为特征阈值为检测触发阈值，当特征行为超过第一行为特征阈值，则认为故障出现，将该ONU为被干扰ONU，从而执行步骤S1030。第二行为特征阈值为故障恢复阈值，当特征行为低于第二行为特征阈值，则认为故障恢复。
可以理解的是，关于上述的相关参数，包括但不限于ONU的一定周期内特定原因的绝对上下线次数、ONU的一定周期内绝对上行误码数，基于历史统计的特定原因的上下线次数变化、基于历史统计的相对上行误码数变化。
另外，可以理解的是，关于上述的ONU特征行为，可在OLT上查询和统计，具体包括不限于上下线次数、上行误码。
另外，可以理解的是，关于上述的特定原因，是指在OLT侧ONU光功率指标正常情况下，排除ONU掉电、人为去激活ONU等行为，由于上行链路异常原因导致的ONU上下线。
需要说明的是，关于上述的行为特征，对应于上述的通信质量参数；关于上述的第一行为特征阈值和第二行为特征阈值，分别相当于上述的第一通信质量参数要求和第二通信质量参数要求。
步骤S1030、OLT设定T1定时器，在T1超时之前，控制被干扰ONU禁止上行发光。
具体地，xPON网络中的OLT针对该特定的被干扰ONU设定定时器T1，在T1超时前禁止被干扰ONU上行发光。
可以理解的是，关于在T1超时前禁止被干扰ONU上行发光，包括但不限于针对EPON网络中的ONU，OLT下行方向通过扩展OAM协议在指定时间T1内关闭ONU上行激光器或通过MPCP协议要求ONU保持静默：如针对GPON网络中的ONU，OLT下行方向通过PLOAM协议在指定时间T1内关闭ONU上行激光器。
步骤S1040、OLT为被干扰ONU继续授权，检测授权窗口信号，并判断是否接收到数据，当接收到数据但无法解析，则执行步骤S1050；当接收到数据并且成功解析，则执行步骤S1060；当没有接收到数据，则执行步骤S1090。
具体地，xPON网络中的OLT会根据其为被干扰ONU配置的逻辑通道标识，按一定DBA规则继续分配上行时隙授权窗口。OLT在对应被干扰ONU的上行时隙授权窗口中检测是否存在上行数据；若T1未超时，则继续根据一定DBA规则为指定逻辑通道标识分配上行时隙授权窗口，并继续检测直到T1超时为止。
需要说明的是，通过对被干扰ONU对应的上行逻辑通道标识继续分配带宽，不改变PON口上的数据以及故障情况下的带宽分配，以避免故障态变化导致的误检或误判。
当在上述上行时隙授权窗口中检测到信号，但信号数据无法解析，则在可能存在上行逻辑通道干扰问题，并跳转至步骤S1050。
当在上述上行时隙授权窗口中检测到信号，且信号数据可以有效解析，则存在上行逻辑通道干扰问题，则记录并比对T1超时内多轮分配授权窗口获取的数据，解析这些数据中的ONU特征值，记录所有不同的特征值；并跳转至步骤S1060。
当在上述上行时隙授权窗口中未检测到信号或数据，且T1超时，则认为不存在上行逻辑通道干扰问题，并跳转至步骤S1090。
另外，需要说明的是，DBA规则是指根据PON口下各ONU的配置带宽按其高优先级进行分配，或者按照固定带宽进行分配，或者按照被干扰ONU关电前最后一次带宽在T1超时前保持授权。
另外，在T1超时后，OLT为被干扰ONU重新打开上行激光器，并正常为其授权。
可以理解的是，关于上述的T1期间的授权窗口，相当于上述的第二上行时隙。
步骤S1050、检索ONU历史特征值，找到与被干扰ONU所有使用相同逻辑通道标识的ONU，作为可疑ONU。
具体地，当在上行时隙授权窗口检测到信号，但数据无法解析。本申请实施例会将该PON口下的ONU历史特征信息列表中所有采用过被干扰ONU的上行逻辑通道标识的ONU均列为可疑ONU，并记入可疑ONU列表。
举例说明，首先，获取被干扰ONU的逻辑通道标识，将该逻辑通道标识置为被干扰逻辑通道标识。若被干扰ONU存在多条逻辑通道标识，这将这些逻辑通道标识均置为被干扰逻辑通道标识。然后，根据被干扰逻辑通道标识为索引，查找ONU历史特征信息列表。接着，将ONU历史特征信息列表中所有逻辑通道标识与被干扰逻辑通道标识相同的，且ONU注册信息与被干扰ONU不同的ONU置为可疑ONU。最后，将所有可疑ONU列入可疑ONU列表。
步骤S1060、检索ONU当前特征值，找到与被干扰ONU所有使用相同逻辑通道标识的ONU，作为可疑ONU。
具体地，当在上行时隙授权窗口检测到数据，且数据可有效解析。则本申请实施例会解析上行数据中的注册特征值或业务特征值。根据注册特征值或业务特征值为索引，检索ONU历史特征值列表中的ONU信息，找到当前正在使用信息特征值相符的记录的ONU，并记入可疑ONU列表。或者，将上行报文携带的信息与OLT维护的ONU历史特征值列表进行比对，如果存在信息相符的表项，则将该ONU记入可疑ONU列表。
举例说明，首先，从上行数据中解析出有效的数据。然后，当有效数据中解析出的注册特征值或者业务特征值与OLT当前配置的ONU的注册特征值或业务特征值相同的，则将该ONU置为可疑ONU；当有效数据中解析出的注册特征值无法与OLT当前配置的ONU数据相匹配时，则以注册特征值或业务特征值为索引查询ONU历史特征信息列表，并找到对应匹配项，并将相关ONU置为可疑ONU。最后，将所有可疑ONU列入可疑ONU列表。
步骤S1070、设定T2定时器，关闭可疑ONU，并观察被干扰ONU的故障是否消失，根据被干扰ONU的故障情况，从可疑ONU中筛选出对被干扰ONU造成干扰的干扰ONU。
具体地，在T1超时后，OLT对被干扰ONU打开激光器，即被干扰ONU可根据OLT为其带 宽分配正常授权，完成ONU上线和上行数据的发送。同时根据一定策略设定T2定时器，对可疑ONU列表中的可疑ONU进行处理，分别如下。
若可疑ONU的状态为未注册状态，则将该可疑ONU注册后，启动定时器T2，关闭可疑ONU上行发光，并观察被干扰ONU的状态，如注册状态或上行误码情况，当其行为特征值在T2超时时小于第二行为特征阈值，则认为故障消失，则该可疑ONU为干扰ONU，从可疑ONU列表移除，并列入干扰ONU列表；否则，则将该可疑ONU重新解注册，并从可疑ONU列表移除。
若可疑ONU的状态为注册在线状态，则针对该可疑ONU启动定时器T2，关闭其上行发光，并观察被干扰ONU的状态，如注册状态或上行误码情况，当其行为特征值在T2超时时小于第二行为特征阈值，则认为故障消失，则该可疑ONU为干扰ONU，从可疑ONU列表移除并列入干扰ONU列表，否则，则重新为该可疑ONU打开上行发光，并正常授权，并从可疑ONU列表移除。
若可疑ONU的状态为离线状态，且上述未注册状态、注册在线状态的可疑ONU轮询处理完毕后，故障依然存在，则将离线状态的可疑ONU从可疑ONU列表移除，并列入干扰ONU列表；否则将离线状态的可疑ONU从可疑ONU列表移除。
可以理解的是，关于上述的T2期间的授权窗口，相当于上述的第一上行时隙。
步骤S1080、将干扰ONU列表中的干扰ONU上报至故障处理平台，排查故障。
具体地，本申请实施例的根节点会将上述干扰ONU列表中的干扰ONU通过告警消息或通知消息上报网管或其他运维平台，并携带其在该PON口下ONU历史注册认证信息表中的信息，并结合用户台帐信息进行处理。
步骤S1090、结束。
根据本申请实施例的技术方案，本申请实施例的OLT能够从多个ONU中筛选出对被干扰ONU造成干扰的干扰ONU，即异常ONU，解决了xPON网络拓扑中ONU的上行逻辑通道被占用的问题，实现了对异常ONU进行定位。另外，本申请实施例的故障定位检测方法，能够不依赖与ONU的配合，解决了采用TDMA机制的xPON网络拓扑中的ONU的上行逻辑通道被占用的问题，并对异常ONU进行定位。另外，由于本申请实施例是在现有硬件基础上采取软件方式来实现对上行逻辑通道被占用问题的动态监控，更加简单和灵活，并且成本也较低。
基于上述实施例的故障定位检测方法，下面提出本申请的根节点、通信系统拓扑和计算机可读存储介质的各个实施例。
另外，本申请的一个实施例提供了一种根节点，该根节点包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
需要说明的是，本实施例中的根节点，可以对应为包括有如图3所示实施例中的存储器和处理器，能够构成图3所示实施例中的系统架构平台的一部分，两者属于相同的发明构思，因此两者具有相同的实现原理以及有益效果，此处不再详述。
实现上述实施例的故障定位检测方法所需的非暂态软件程序以及指令存储在存储器中，当被处理器执行时，执行上述实施例的故障定位检测方法，例如，执行以上描述的图4中的方法步骤S100至S500、图5中的方法步骤S610至S640、图6中的方法步骤S710至S740、图7中的方法步骤S810、图8中的方法步骤S820、图9中的方法步骤S830、图10中的方法步骤S910至S920、图12中的方法骤S1010至S1090。
需要说明的是，本申请实施例的根节点具体实施方式和技术效果，可以参照上述实施例的故障定位检测方法的具体实施方式和技术效果。
另外，本申请的一个实施例提供了一种通信系统拓扑，包括多个叶子节点和上述的根节点，根节点与多个叶子节点通信。
需要说明的是，本申请实施例的根节点具体实施方式和技术效果，可以参照上述实施例的故障定位检测方法的具体实施方式和技术效果。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，当计算机可执行指令用于执行上述的故障定位检测方法，例如，执行以上描述的图4中的方法步骤S100至S500、图5中的方法步骤S610至S640、图6中的方法步骤S710至S740、图7中的方法步骤S810、图8中的方法步骤S820、图9中的方法步骤S830、图10中的方法步骤S910至S920、图12中的方法骤S1010至S1090。
本申请实施例包括：通信系统拓扑中的根节点会获取目标叶子节点的第一通信质量参数，其中，上述的目标叶子节点为通信系统拓扑中多个叶子节点中的一个；当所述第一通信质量参数不满足第一预设通信质量参数要求，根节点会获取多个所述叶子节点的历史特征信息，并根据所述历史特征信息在多个所述叶子节点中确定疑似干扰所述目标叶子节点的第一叶子节点；接着，根节点会控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据，并且获取所述目标叶子节点在所述第一上行时隙内的第二通信质量参数；当所述第二通信质量参数满足第二预设通信质量参数要求，根节点会确定所述第一叶子节点为干扰所述目标叶子节点的第二叶子节点。根据本申请实施例的技术方案，本申请实施例的根节点能够从多个叶子节点中筛选出对目标叶子节点造成干扰的第二叶子节点，即异常叶子节点，解决了采用TDMA机制的PToMP通信系统拓扑中叶子节点的上行逻辑通道被占用的问题，实现了对异常叶子节点进行定位。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包括计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的若干实施方式进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请精神的共享条件下还可作出种种等同的变形或替换，这些等同的变形或替换均包括在本申请权利要求所限定的范围内。

Claims (11)

  1. 一种故障定位检测方法，应用于通信系统拓扑中的根节点，所述通信系统拓扑还包括与所述根节点通信的多个叶子节点，其中，所述方法包括：
    获取目标叶子节点的第一通信质量参数，其中，所述目标叶子节点为多个所述叶子节点中的一个；
    当所述第一通信质量参数不满足第一预设通信质量参数要求，获取多个所述叶子节点的历史特征信息；
    根据所述历史特征信息在多个所述叶子节点中确定疑似干扰所述目标叶子节点的第一叶子节点；
    控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据，并获取所述目标叶子节点在所述第一上行时隙内的第二通信质量参数；
    当所述第二通信质量参数满足第二预设通信质量参数要求，确定所述第一叶子节点为干扰所述目标叶子节点的第二叶子节点。
  2. 根据权利要求1所述的方法，其中，所述根据所述历史特征信息在多个所述叶子节点中确定疑似干扰所述目标叶子节点的第一叶子节点，包括：
    控制所述目标叶子节点在第二上行时隙内停止上传数据；
    当在所述第二上行时隙内获取到上行数据并且无法解析所述上行数据，获取与所述目标叶子节点对应的逻辑通道标识；
    根据所述逻辑通道标识和所述历史特征信息，在多个所述叶子节点中确定与所述逻辑通道标识匹配的叶子节点作为第一叶子节点，其中，所述历史特征信息包括多个所述叶子节点的逻辑通道标识；
    控制所述目标叶子节点恢复上传数据。
  3. 根据权利要求1所述的方法，其中，所述根据所述历史特征信息在多个所述叶子节点中确定疑似干扰所述目标叶子节点的第一叶子节点，包括：
    控制所述目标叶子节点在第二上行时隙内停止上传数据；
    当在所述第二上行时隙内获取到上行数据并且成功解析所述上行数据，获取由所述上行数据解析得到的特征参数；
    根据所述特征参数和所述历史特征信息，在多个所述叶子节点中确定与所述特征参数匹配的叶子节点作为第一叶子节点，其中，所述历史特征信息包括多个所述叶子节点的特征参数；
    控制所述目标叶子节点恢复上传数据。
  4. 根据权利要求2或3所述的方法，其中，所述第一上行时隙和/或所述第二上行时隙按照预设规则进行分配，其中，所述预设规则包括与所述叶子节点的优先级对应的带宽分配规则、固定带宽分配规则、所述目标叶子节点在停止上传数据之前多个所述叶子节点的带宽分配规则中的一种。
  5. 根据权利要求1所述的方法，其中，所述控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据，包括如下至少之一：
    获取所述第一叶子节点的当前状态，当所述当前状态为未注册状态，发送注册信息至所 述第一叶子节点以使所述第一叶子节点由所述未注册状态切换为注册在线状态，并控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据；
    或获取所述第一叶子节点的当前状态，当所述当前状态为注册在线状态，控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据；
    或获取所述第一叶子节点的当前状态，当所述当前状态为离线状态，控制所述第一叶子节点在所述目标叶子节点的第一上行时隙内停止上传数据。
  6. 根据权利要求1所述的方法，其中，在所述确定所述第一叶子节点为干扰所述目标叶子节点的第二叶子节点之后，所述方法还包括：
    获取所述第二叶子节点的特征参数；
    将所述第二叶子节点的特征参数发送至故障处理平台。
  7. 根据权利要求1所述的方法，其中，所述通信质量参数包括如下至少之一：
    在预设周期内的上下线次数；
    或在预设周期内的上行误码数；
    或在预设周期内的上下线次数变化值；
    或在预设周期内的上行误码数变化值。
  8. 根据权利要求3或6所述的方法，其中，所述特征参数包括注册特征参数和/或业务特征参数。
  9. 一种根节点，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至8中任意一项所述的故障定位检测方法。
  10. 一种通信系统拓扑，包括多个叶子节点和如权利要求9所述的根节点，其中，所述根节点与多个所述叶子节点通信。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行如权利要求1至8中任意一项所述的故障定位检测方法。
PCT/CN2022/092745 2021-06-21 2022-05-13 故障定位检测方法、根节点、通信系统拓扑和存储介质 WO2022267737A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110685578.5 2021-06-21
CN202110685578.5A CN115514626A (zh) 2021-06-21 2021-06-21 故障定位检测方法、根节点、通信系统拓扑和存储介质

Publications (1)

Publication Number Publication Date
WO2022267737A1 true WO2022267737A1 (zh) 2022-12-29

Family

ID=84499717

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/092745 WO2022267737A1 (zh) 2021-06-21 2022-05-13 故障定位检测方法、根节点、通信系统拓扑和存储介质

Country Status (2)

Country Link
CN (1) CN115514626A (zh)
WO (1) WO2022267737A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117408572A (zh) * 2023-12-13 2024-01-16 南通纳科达聚氨酯科技有限公司 力致变色弹性薄膜的制备优化方法及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116017516B (zh) * 2023-03-24 2023-06-27 广州世炬网络科技有限公司 基于链路干扰的节点连接配置方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132234A (zh) * 2006-08-24 2008-02-27 上海贝尔阿尔卡特股份有限公司 光网络中检测光网络单元间时隙冲突的装置及方法
WO2009053390A1 (en) * 2007-10-26 2009-04-30 Nokia Siemens Networks Oy Method to diagnose an optical communication network
CN111107449A (zh) * 2018-10-25 2020-05-05 中兴通讯股份有限公司 一种突发式长发光干扰onu定位的方法及装置
CN112738660A (zh) * 2019-10-28 2021-04-30 华为技术有限公司 无源光网络的检测方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132234A (zh) * 2006-08-24 2008-02-27 上海贝尔阿尔卡特股份有限公司 光网络中检测光网络单元间时隙冲突的装置及方法
WO2009053390A1 (en) * 2007-10-26 2009-04-30 Nokia Siemens Networks Oy Method to diagnose an optical communication network
CN111107449A (zh) * 2018-10-25 2020-05-05 中兴通讯股份有限公司 一种突发式长发光干扰onu定位的方法及装置
CN112738660A (zh) * 2019-10-28 2021-04-30 华为技术有限公司 无源光网络的检测方法、装置及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117408572A (zh) * 2023-12-13 2024-01-16 南通纳科达聚氨酯科技有限公司 力致变色弹性薄膜的制备优化方法及系统
CN117408572B (zh) * 2023-12-13 2024-04-19 南通纳科达聚氨酯科技有限公司 力致变色弹性薄膜的制备优化方法及系统

Also Published As

Publication number Publication date
CN115514626A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
WO2022267737A1 (zh) 故障定位检测方法、根节点、通信系统拓扑和存储介质
JP7176111B2 (ja) バースト型連続発光干渉ｏｎｕの測位方法および装置
KR100421151B1 (ko) 기가비트 이더넷 수동 광 가입자 망 시스템에서의 동작구현방법 및 그 이더넷 프레임 구조
US8254780B2 (en) Passive optical network system and fault determination method
US9838150B2 (en) Method and apparatus for detecting optical network unit, and passive optical network system
US9130676B2 (en) Transparent protection switching operation in a PON
JP6431184B2 (ja) Ｐｏｎにおける不正なｏｎｕを決定するための方法および装置
US20170279525A1 (en) Method, Apparatus, and System for Detecting Rogue Optical Network Unit
WO2016188196A1 (zh) 一种异常pon终端的检测方法及装置
CN107294595B (zh) 一种长发光光网络单元的检测方法、装置及光线路终端
US11805339B2 (en) Downlink bandwidth transmission method and apparatus for passive optical network
CN112953627A (zh) 一种故障检测方法、装置、设备及存储介质
CN111954101B (zh) Gpon系统中重复alloc id的检测方法与装置
WO2023029805A1 (zh) 通道占用检测与防护方法、光线路终端、网络及存储介质
ES2365306T3 (es) Procedimiento, sistema de comunicación y unidad de comunicación central para detectar una unidad de comunicación periférica defectuosa.
KR100929132B1 (ko) Ｌ3/ｌ2 망으로 운영되는 수동광 네트워크의 가입자 통신장애 처리 장치 및 방법
CN108631864B (zh) 一种burst漂移检测方法及装置
WO2023142469A1 (zh) 告警检测方法、电子设备、计算机可读存储介质
US20220224595A1 (en) Optical communication device and control method
US8244135B2 (en) System and method for increasing upstream optical coding gain in a gigabit passive optical network (GPON)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22827235

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE