[go: up one dir, main page]

WO2010095268A1 - Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau - Google Patents

Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau Download PDF

Info

Publication number
WO2010095268A1
WO2010095268A1 PCT/JP2009/053214 JP2009053214W WO2010095268A1 WO 2010095268 A1 WO2010095268 A1 WO 2010095268A1 JP 2009053214 W JP2009053214 W JP 2009053214W WO 2010095268 A1 WO2010095268 A1 WO 2010095268A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
port
control frame
blocked
master node
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2009/053214
Other languages
English (en)
Japanese (ja)
Inventor
美里 亀井
和海 小口
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
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 Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Priority to PCT/JP2009/053214 priority Critical patent/WO2010095268A1/fr
Publication of WO2010095268A1 publication Critical patent/WO2010095268A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/42—Loop networks
    • H04L12/437—Ring fault isolation or reconfiguration

Definitions

  • the present invention relates to a control method in a ring network.
  • ring networks that achieve high reliability by providing communication path redundancy in the network configuration have been widely used.
  • broadcast frames continue to flow when a loop occurs, so normally a single port on the ring network is blocked to prevent the occurrence of a loop.
  • a method has been proposed in which when a failure occurs on the ring network, the failure is automatically detected and the communication path is switched without causing a loop.
  • STP Sesing Tree Protocol
  • BPDU Binary Protocol Data Unit
  • Patent Document 1 a control frame with a device identification string is bidirectionally transmitted / received between the devices constituting the ring, the failure detection and the occurrence location are specified, and the device that blocks the port when the failure is detected A technique for avoiding a loop by releasing the blockade after waiting for the blockage release command is disclosed.
  • one port of the master node on the ring network is normally closed to avoid the occurrence of a loop.
  • the node that detected the failure closes the link or the node-side port that detected the failure, and sends a control frame that notifies the release of the block to the master node.
  • the master node can switch to the normal communication path by releasing the blocked port. Even when a failure is recovered, it is possible to switch the communication path by avoiding the occurrence of a loop by closing the port of the master node and then releasing the blocked port at the time of failure.
  • Patent Document 2 when a loop has occurred, since the port transition of the address learning entry in the address learning table frequently occurs, the bridge device detects the loop by monitoring the occurrence frequency for each port, A technique for recovering from a loop state by closing a port that has detected a loop is disclosed.
  • the above-described conventional technique has a problem that when a blocked port is erroneously released due to a malfunction of the device, a state (loop) in which there is no blocked port on the ring network occurs.
  • a state (loop) in which there is no blocked port on the ring network occurs.
  • an erroneous setting that sets a plurality of blocked ports on the ring network occurs, there is a problem that the communication path is divided and normal communication cannot be maintained.
  • the present invention has been made in view of the above, and an object of the present invention is to obtain a ring network control method capable of detecting and recovering from an abnormality in a blocked port setting.
  • the present invention is configured so that a plurality of nodes having two or more ports for performing communication are connected in a ring shape, and at least one node is connected to a network state.
  • a ring network control method in a ring network in which a master node to be monitored and a slave node in accordance with an instruction from the master node are used, wherein the master node has a control frame having a block number field indicating the block port number.
  • the control frame transmission step for transmitting to the adjacent slave node, and when the slave node that received the control frame has a blocked port, rewrite the field of the number of blocked locations of the control frame, and then rewrite the control frame
  • Control frame transfer step for transferring to a node other than the source node
  • the master node checks the field of the number of blocked points in the received control frame and detects whether the blocked port setting is normal or abnormal
  • the ring network control method according to the present invention has an effect that it is possible to detect and restore an abnormality in the blocked port setting.
  • FIG. 1 is a diagram illustrating a configuration example of a ring network.
  • FIG. 2 is a diagram illustrating a ring network in which two ports are blocked.
  • FIG. 3 is a diagram illustrating a configuration example of a block number monitoring control frame.
  • FIG. 4 is a flowchart showing the block port confirmation process.
  • FIG. 5 is a diagram illustrating the transition of each field of the block number monitoring control frame.
  • FIG. 6 is a diagram illustrating the transition of each field of the block number monitoring control frame.
  • FIG. 7 is a diagram illustrating a ring network in which a loop has occurred.
  • FIG. 8 is a diagram showing the transition of each field of the block number monitoring control frame.
  • FIG. 9 is a diagram illustrating a ring network in which two ports are blocked.
  • FIG. 10 is a diagram illustrating the transition of each field of the block number monitoring control frame.
  • FIG. 11 is a diagram illustrating a recovery process after abnormality detection.
  • FIG. 12 is a diagram illustrating a ring network in which a link break has occurred.
  • FIG. 13 is a diagram illustrating the flow of the blockage number monitoring control frame.
  • FIG. 14 is a diagram illustrating transition of each field of the block number monitoring control frame.
  • FIG. 15 is a diagram illustrating a ring network that blocks a plurality of ports.
  • FIG. 16 is a diagram illustrating the transition of each field of the block number monitoring control frame.
  • FIG. 17 is a diagram illustrating a configuration example of a block number monitoring control frame.
  • FIG. 18 is a diagram illustrating a state in which the master node has failed.
  • FIG. 19 is a diagram showing transmission / reception of a control frame between the master node and the spare master node.
  • FIG. 20 is a diagram illustrating a state in
  • FIG. 1 is a diagram illustrating a configuration example of a ring network.
  • the ring network includes a master node 11, slave nodes 21 to 25, and links 41 to 46. Each node has two ports for the ring network, which are represented by ports 31 to 3C, respectively.
  • the master node 11 is a node that monitors the state of the ring network.
  • the slave nodes 21 to 25 are nodes that follow the instruction of the master node 11.
  • Ports 31 to 3C are interfaces for inputting / outputting data to / from adjacent nodes.
  • the links 41 to 46 are transmission lines that constitute a ring.
  • the master node and the slave node are arranged at the illustrated positions, but any node on the ring network may be the master node, and any node may be the slave node.
  • one port of the master node 11 is blocked (port 31 or port 3C, for example, port 31 is a blocked port), and a user frame is blocked to avoid a loop state.
  • the slave node that detects the failure closes the port, and the master node 11 releases the port 31 from being blocked.
  • the master node 11 again closes one port (port 31), and the slave node that has blocked the port releases the port blocking.
  • a loop may occur when the master node 11 releases the block of the port 31 while the port of another slave node to be blocked is not blocked due to a device (node) failure or the like.
  • the port is blocked at a plurality of locations because the master node 11 blocks the port 31 while the slave node that should release the block does not release the port when the failure is recovered.
  • the master node 11 confirms that the blocked port in the ring network has been canceled by mistake (blocked port erroneous release) and that multiple blocked ports have been set (blocked port error).
  • a monitoring control frame (blocking location number monitoring control frame) having a field indicating the number of blocking locations (blocking location number field) is transmitted from the ports 31 and 3C on both sides to block on the ring network. Monitor the number of locations.
  • Ethernet In Ethernet (registered trademark), in order to send and receive the block location monitoring control frame, a control VLAN (Virtual Local Area Network) that makes one round of the ring from the master node 11 is set, and the block location monitoring control frame is set. May use a VSM (Vendor Specific Message) frame, which is a type of Ethernet (registered trademark) OAM (Operations, Administration, Maintenance) frame.
  • VSM Vehicle Specific Message
  • FIG. 2 is a diagram illustrating a state in which two ports at both ends of the link are blocked in the ring network.
  • the master node 11 In the ring network, it is possible for the master node 11 to secure a normal communication path (link 42 ⁇ link 41 ⁇ link 46 ⁇ link 45 ⁇ link 44) by releasing the blocking of the port 31.
  • the state in FIG. 2 is not an abnormality in the number of blocked locations (incorrect setting of a blocked port, erroneous release of a blocked port). In such a case, since the number of blocked locations is not set to “2”, a field (set flag field) for distinguishing the state of FIG. 2 from erroneous setting of the blocked ports is provided in the blocked location number monitoring control frame.
  • FIG. 3 is a diagram illustrating a configuration example of a block number monitoring control frame.
  • the block number monitoring control frame is a control frame having a destination address, a transmission source address, a block number field, and a set flag field.
  • the transmission source address is the address of the master node 11.
  • the port 31 is transmitted in the clockwise direction (the direction of the link 41) and the port 3C is transmitted in the counterclockwise direction (the direction of the link 46).
  • the block number monitoring control frame is transmitted to only one of them. Even in this case, an abnormality in the blocked port setting can be detected by making one round of the ring network. However, in consideration of the case where a one-way communication failure occurs, it is desirable to transmit in both directions.
  • the master node 11 and the slave nodes 21 to 25 define a field indicating that the received frame is a blocked part number monitoring control frame in the frame so that the received frame is recognized as a blocked part number monitoring control frame. Also good.
  • FIG. 4 is a flowchart showing the block port confirmation process in the slave node.
  • the slave node 25 When the slave node 25 receives the block number monitoring control frame (step S1), it confirms whether or not the reception port (port 3B) constituting the ring is blocked (step S2). When the reception port is blocked (step S2: Yes), the set flag field of the block number monitoring control frame is confirmed (step S3). When the set flag field is “0” (step S3: Yes), 1 is added to the value of the blockage number field (+1) (step S4), and the set flag field is set to “0” (step S5). When the reception port is not blocked (step S2: No) and when the set flag field is not “0” (step S3: No), the set flag field is set to “0” (step S5).
  • the slave node 25 checks whether or not the transmission port (port 3A) constituting the ring is blocked (step S6).
  • the transmission port is blocked (step S6: Yes)
  • 1 is added to the value of the block number field (+1) (step S7)
  • the set flag field is set to “1” (step S8).
  • the slave node 25 transmits a block location monitoring control frame in which the values of the block location number field and the set flag field are rewritten to the adjacent slave node 24 (step S9).
  • the slave node 25 transmits a block number monitoring control frame to the adjacent slave node 24 (step S9).
  • the slave node 24 that has received the block number monitoring control frame performs the processing of steps S1 to S9 and relays the block number monitoring control frame. In this case, the slave node 24 transfers to the adjacent slave node 23. Similarly, transfer of the blockage number monitoring control frame transmitted from the port 31 to the slave node 21 by the master node 11 is repeated between the slave nodes.
  • the master node 11 receives the block number monitoring control frame and confirms the block number field of the block number monitoring control frame.
  • the number of blocked locations field is “2 or more”
  • the master node 11 detects an abnormality in the blocked port setting as an erroneous setting of the blocked port.
  • the block location number field is “0” and the transmission source address is the address of the own device (master node 11)
  • a block port setting error is detected as an erroneous release of the block port.
  • the master node 11 discards the block number monitoring control frame after confirming the block number field.
  • FIG. 5 shows the transition of the block number field and the set flag field when the block number monitoring control frame is transmitted and received counterclockwise from the master node 11.
  • FIG. 5 is a diagram showing the transition of each field of the block number monitoring control frame in each node.
  • This is a diagram showing the transition of the block number field and the set flag field when the block number monitoring control frame passes through each node.
  • the master node 11 recognizes that the blocked port setting is normal because the number of blocked locations field is “1” when returning around the ring network. Actually, only the port 31 of the master node 11 is blocked, and a normal communication path can be secured in the entire ring network.
  • FIG. 6 shows the transition of the block number field and the set flag field when the block number monitoring control frame is transmitted and received counterclockwise from the master node 11 in the ring network of FIG.
  • FIG. 6 is a diagram illustrating the transition of each field of the block number monitoring control frame in each node.
  • the port 36 and the port 35 are blocked, but the blocked port of the port 35 is not counted by using the set flag field (step S3: No process in the flowchart of FIG. 4). Therefore, the master node 11 recognizes that the blocked port setting is normal because the number of blocked locations field is “1” when returning around the ring network.
  • the number of blocked ports is two, but the number of blocked ports is one, and a normal communication path can be secured in the entire ring network.
  • FIG. 8 shows transitions of the block number field and the set flag field when the block number monitoring control frame is transmitted and received counterclockwise from the master node 11.
  • FIG. 7 is a diagram illustrating a ring network in which a loop has occurred.
  • FIG. 8 is a diagram showing transition of each field of the blockage number monitoring control frame in each node.
  • the master node 11 is able to detect erroneous release of the blocked port because the number of blocked locations field is “0” when returning around the ring network. Actually, a loop occurs and a broadcast frame continues to flow and normal communication cannot be performed.
  • FIG. 10 shows the transition of the block number field and the set flag field when the block number monitoring control frame is transmitted and received counterclockwise from the master node 11 in the ring network of FIG.
  • FIG. 9 is a diagram illustrating a ring network in which two ports are blocked.
  • FIG. 10 is a diagram showing transition of each field of the blockage number monitoring control frame in each node.
  • the master node 11 is able to detect erroneous release of the blocked port because the number of blocked locations field is “2” when returning around the ring network.
  • the route is divided due to blockage at a plurality of locations, and a route between nodes that cannot communicate user data is generated.
  • FIG. 11 is a diagram illustrating a recovery process after abnormality detection.
  • the master node 11 blocks one port (for example, the port 31) of the master node.
  • the master node 11 transmits a blocking release instruction control frame for instructing the release of the blocking port to the slave nodes 21 and 25. Since it is confirmed that the block number monitoring control frame has made one round of the ring network, transmission in one direction may be performed, but transmission in both directions is desirable.
  • the slave nodes 21 and 25 When the slave nodes 21 and 25 receive the blocking release instruction control frame, the slave nodes 21 and 25 transfer the blocking release instruction control frame to the nodes (slave nodes 22 and 24) adjacent to the direction opposite to the direction in which the slave release instruction control frame is received, and the ports blocked by the own device. If there is, release the block. In FIG. 11, the slave node 25 releases the blocking of the port 3A.
  • the slave nodes 22 and 24 that have received the block release instruction control frame receive the above 3.
  • the same process is performed. In FIG. 11, in this process, the slave node 22 releases the block of the port 34. Thereafter, each slave node that has received the block release instruction control frame receives the above 3. By repeating this process, the blockage release instruction control frame goes around the ring network and returns to the master node 11. The master node 11 discards the received block release instruction control frame.
  • the slave nodes 21 to 25 are not blocked. In the ring network, only the master node 11 blocks one port (port 31).
  • the slave node 11 can detect an abnormality in the blocked port setting using the block number monitoring control frame, and can recover the abnormality detected using the block release instruction control frame. did. As a result, a communication failure can be quickly recovered and a normal communication path can be secured, so that the reliability of the ring network can be improved.
  • Embodiment 2 the communication path is secured even in one direction, and the master node 11 detects an abnormality in the blocked port setting when the transmitted block number monitoring control frame returns around the link network. it can. However, if the block location monitoring control frame does not return, the master node 11 can detect that there is some failure on the ring network, but cannot detect an abnormal block port setting.
  • a method for detecting an abnormality in the blocked port setting even when a failure has occurred on the ring network will be described.
  • FIG. 12 is a diagram showing a ring network in which a link break has occurred in the link 43.
  • the master node 11 can detect a failure such as a link disconnection by not returning the transmitted blockage number monitoring control frame.
  • the slave nodes 22 and 23 connected to the link 43 can detect that a failure has occurred in the link 43.
  • the slave nodes 22 and 23 that have detected the failure block the ports (ports 35 and 36) that have suffered the failure.
  • the slave nodes 22 and 23 that have detected the failure transmit the block number monitoring control frame with the block number field set to “1” from the normal port (ports 34 and 37).
  • the transmission source address of the block number monitoring control frame is the address of the own node (slave node 22 or 23).
  • the master node 11 When the master node 11 receives the block number monitoring control frame, if the transmission source address is not its own node (master node 11) and the block number field is “2 or more”, the blocked port setting error Can be detected. The received block number monitoring control frame is discarded as in the first embodiment.
  • FIG. 13 is a diagram showing the flow of the blockage number monitoring control frame. The correspondence of the above processing ((1) to (4)) in each node is shown.
  • FIG. 14 shows the transition of the block number field and the set flag field of the block number monitoring control frame transmitted in the clockwise direction by the slave node 23 detecting the failure in the ring network of FIG.
  • FIG. 14 is a diagram illustrating the transition of each field of the block number monitoring control frame in each node. In this case, the master node 11 recognizes that the blocked port setting is normal because the blocked location number field is “1”.
  • FIG. 15 is a diagram illustrating a state where a plurality of ports are blocked in the ring network.
  • FIG. 16 is a diagram showing transition of each field of the blockage number monitoring control frame in each node.
  • the master node 11 can detect an abnormality in the blocked port setting (incorrect setting of the blocked port) because the number of blocked locations field is “2”.
  • the nodes on both sides (for example, the slave nodes 22 and 23 in FIG. It is desirable to periodically transmit the blockage number monitoring control frame.
  • the master node 11 has not received the block location monitoring control frame transmitted by its own node (master node 11), or has received a block location monitoring control frame whose source address is not its own node (master node 11). Thus, it is possible to detect that there is some failure on the ring network.
  • FIG. 17 is a diagram illustrating a configuration example of a block number monitoring control frame. A field that is blocked due to a failure has been added. The slave node that has detected the failure sets “1” to “blocking” due to the occurrence of the failure at the time of transmission, and the slave node that relays does not change the value.
  • the master node 11 sees the blockage due to failure occurrence and the blockage location number field in the received blockage number monitoring control frame received, the blockage due to failure occurrence is “1”, and the blockage location number field is “2 or more. ", It is possible to detect an abnormality in the blocked port setting during the occurrence of a failure.
  • the master node 11 that has detected an abnormality in the blocked port setting during the occurrence of a failure does not detect a failure in its own node but blocks the port (for example, the port 31 is blocked). If so, the port 31 is unblocked).
  • the master node 11 transmits the blocking release instruction control frame in both directions of the slave node 21 (clockwise) and the slave node 25 (counterclockwise).
  • the slave nodes 21 and 25 When the slave nodes 21 and 25 receive the block release instruction control frame, the slave nodes 21 and 25 transfer the block to the node adjacent to the direction opposite to the received direction, and release the block if there is a port blocked by the own device.
  • the nodes on both sides (for example, slave nodes 22 and 23) that detected the failure do not release the block of the ports (ports 35 and 36) that detected the failure, but discard the block release instruction control frame.
  • the master node does not need to be specified as one on the ring network, and a sub-master node that performs the same processing as the master node may be set.
  • all nodes can perform the same process as the master node, and all nodes can detect a blocked port setting error.
  • Embodiment 3 In the first and second embodiments, only one master node is set on the ring network, the master node is not broken, and it is possible to detect transmission / reception of control frames and abnormalities in blocked port settings. It is a premise. However, when only one master node is set on the ring network, if the master node fails and the links on both sides of the master node are disconnected and communication is not possible, an abnormality in the blocked port setting on the ring network cannot be detected. . In this embodiment, a case where a spare master node is set will be described.
  • FIG. 18 is a diagram showing a state in which the master node 11 has failed in the ring network. In such a case, the links on both sides of the master node 11 are disconnected, making communication impossible, and it is impossible to detect an abnormality in the blocked port setting on the ring network.
  • At least one of the slave nodes is set as a spare master node (slave node 23 as an example), and the block number monitoring control frame It is possible to detect errors in transmission and blocked port settings.
  • a spare master node for example, control frames are periodically transmitted and received between the spare master node (slave node 23) and the master node 11.
  • the spare master node (slave node 23) monitors the normality of the master node 11 by a method such as assuming that the master node 11 has failed when the control frame from the master node 11 does not reach.
  • FIG. 19 is a diagram illustrating transmission and reception of control frames between the master node 11 and a spare master node (slave node 23).
  • FIG. 20 is a diagram illustrating a state in which a spare master node (slave node 23) is operating as a master node. Only when the master node 11 is out of order, the spare master node (slave node 23) is the master node and performs the processing described in the first and second embodiments.
  • the Ethernet may use a CC (Continuity Check) function that is a function of the Ethernet (registered trademark) OAM.
  • any node may transmit the blocked point number monitoring control frame. For example, when a plurality of spare master notes are set, all the spare master nodes are transmitted. Even when operating as a master node, each node can detect an abnormality by checking whether there is an abnormality in the blocked port setting if the transmission source address is the address of its own device. However, it is necessary to recover from a blocked port setting abnormality, and in the second embodiment, only one node on the ring network needs to terminate the control frame as a master node and block at the time of recovery. Therefore, when multiple spare master nodes are set, priorities are assigned to the spare master nodes, and a master node with a lower priority is assigned to the master node only when all other master nodes with higher priorities have failed. Works.
  • the present embodiment it is possible to detect a blocked port setting error and recover the detected error even when the master node fails. As a result, a communication failure can be quickly recovered and a normal communication path can be secured, so that the reliability of the ring network can be improved.
  • the ring network control method according to the present invention is useful for a ring network that achieves high reliability, and is particularly suitable as a ring network that enables detection and recovery of an abnormality in a blocked port setting.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

La présente invention porte sur un procédé de commande de réseau en anneau qui comprend : une étape de transmission de trame de commande dans laquelle un noeud maître transmet une trame de commande ; une étape de transfert de trame de commande dans laquelle un noeud esclave réécrit un champ de quantité de partie fermée de la trame de commande si un quelconque port fermé existe et transfère ensuite la trame de commande ; une étape de détection dans laquelle le noeud maître vérifie le champ de qualité de partie fermée si la trame de commande est renvoyée au noeud maître de sorte à détecter si le réglage du port fermé est normal ; une étape de fermeture du port dans laquelle le noeud maître ferme au moins un port si un défaut du réglage du port fermé est détecté et si le noeud maître n'a pas fermé le port ; une étape de transmission de libération de fermeture dans laquelle le noeud maître transmet la trame de commande de libération de fermeture ; et une étape de transfert de libération de fermeture dans laquelle le noeud esclave libère un port fermé s'il y en a dans le noeud esclave et transfère la trame de commande de libération de fermeture.
PCT/JP2009/053214 2009-02-23 2009-02-23 Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau Ceased WO2010095268A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/053214 WO2010095268A1 (fr) 2009-02-23 2009-02-23 Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/053214 WO2010095268A1 (fr) 2009-02-23 2009-02-23 Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau

Publications (1)

Publication Number Publication Date
WO2010095268A1 true WO2010095268A1 (fr) 2010-08-26

Family

ID=42633568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/053214 Ceased WO2010095268A1 (fr) 2009-02-23 2009-02-23 Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau

Country Status (1)

Country Link
WO (1) WO2010095268A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013153293A (ja) * 2012-01-24 2013-08-08 Nippon Telegr & Teleph Corp <Ntt> ループ検知方法及びループ検知装置
CN107181661A (zh) * 2016-03-11 2017-09-19 西门子公司 实时性故障保护方法、主节点、从节点和环形网络系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006027824A1 (fr) * 2004-09-06 2006-03-16 Mitsubishi Denki Kabushiki Kaisha Système de réseau de communication et appareil de détection de panne
JP2007019698A (ja) * 2005-07-06 2007-01-25 Nippon Telegr & Teleph Corp <Ntt> リング型冗長通信路制御方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006027824A1 (fr) * 2004-09-06 2006-03-16 Mitsubishi Denki Kabushiki Kaisha Système de réseau de communication et appareil de détection de panne
JP2007019698A (ja) * 2005-07-06 2007-01-25 Nippon Telegr & Teleph Corp <Ntt> リング型冗長通信路制御方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013153293A (ja) * 2012-01-24 2013-08-08 Nippon Telegr & Teleph Corp <Ntt> ループ検知方法及びループ検知装置
CN107181661A (zh) * 2016-03-11 2017-09-19 西门子公司 实时性故障保护方法、主节点、从节点和环形网络系统

Similar Documents

Publication Publication Date Title
US7355965B2 (en) Apparatus and method for rapid detection of unidirectional breaks in a network ring
US7339887B2 (en) Multipoint protected switching ring
CN101822000B (zh) 在网络中运行的方法和网络的装置以及包括这种装置的通信系统
JP5521663B2 (ja) 通信装置、通信システムおよび通信方法
JP5471240B2 (ja) スイッチ装置、リングネットワークシステム、通信制御方法、および装置のプログラム
CN100574241C (zh) 具有冗余特性的局域网及用于这种网络的耦合设备
US8264954B2 (en) Method and device for operating a network and communication system comprising such device
EP2023541B1 (fr) Procédé, appareil et système de communication pour éviter des boucles dans un réseau Ethernet à anneau étant sur un réseau 802.3ad
CN101094190B (zh) 以太环网保护控制报文的传输方法
CN100479411C (zh) 一种分布式系统的节点链路切换的处理方法及其装置
CN101127653B (zh) 设置有备份的以太网环网设备及其主设备备份的实现方法
CN101626335B (zh) 一种双归连接网络的数据保护方法
WO2012079313A1 (fr) Procédé de protection de liaison et système associé
JP5084772B2 (ja) リング型ネットワーク
CN101436975A (zh) 一种在环网中实现快速收敛的方法、装置及系统
JP5012485B2 (ja) 冗長方法及びスイッチ装置
CN102104521B (zh) 以太环网链路故障恢复方法、以太环网及节点设备
CN101764714A (zh) 通道失效倒换方法、节点和信号传输系统
JP5176623B2 (ja) イーサネットの伝送方法、伝送装置およびシステム
WO2010095268A1 (fr) Procédé de commande de réseau en anneau, noeud maître, noeud esclave et réseau en anneau
JP2011223172A (ja) リング型ネットワークシステム、通信装置および障害検出方法
WO2008037781A1 (fr) Procédé de commutation de protection dans topologies en anneau
JP5635029B2 (ja) 通信ネットワーク、中継ノードおよび通信経路切替方法
JP2013157682A (ja) リング接続ノード、マルチリングネットワークおよび経路切替方法
JP7452635B2 (ja) 経路切替方法、転送装置、及び通信システム

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: 09840374

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09840374

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP