EP2130329A1 - Procédé de reconfiguration d'un réseau de communication - Google Patents
Procédé de reconfiguration d'un réseau de communicationInfo
- Publication number
- EP2130329A1 EP2130329A1 EP08717849A EP08717849A EP2130329A1 EP 2130329 A1 EP2130329 A1 EP 2130329A1 EP 08717849 A EP08717849 A EP 08717849A EP 08717849 A EP08717849 A EP 08717849A EP 2130329 A1 EP2130329 A1 EP 2130329A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- bridge
- slave
- master
- data link
- network
- 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.)
- Withdrawn
Links
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/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
- H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
Definitions
- the invention is in the technical field of packet-switched communication networks and relates to a method for reconfiguring a communication network in which LANs using different network protocols are interconnected.
- LANs Packet-switched Local Area Networks
- office environment Packet-switched Local Area Networks
- LANs In contrast to the office environment, LANs have to work reliably in everyday industrial environments under extreme conditions such as electromagnetic interference fields, high operating temperatures and mechanical stresses. Since the failure of a production plant and the associated downtimes are usually associated with high costs, it is added that in industrial applications, the requirements for reliability are higher than in office environment.
- a ring topology is usually chosen for the network, as it enables a fast reconfiguration time of less than 500 ms in the event of a data link or bridge failure.
- Network protocols typically use Ethernet standard based or proprietary network protocols for industrial LANs.
- LANs in the office environment are usually constructed in a star or mesh topology and as a network protocol these days typically use RSTP (Rapid Spanning Tree Protocol) in accordance with IEEE standard 802. Iw.
- RSTP Rapid Spanning Tree Protocol
- ring-shaped industrial LANs are connected to one another via meshed Office LANs via data links.
- the disadvantage here is the fact that the switching process for activating the blocked second data link takes comparatively much time and takes about 30 seconds when using the standardized routines of RSTP in the office LAN.
- a method for reconfiguring a packet-switched communication network which comprises a (geswitchtes by bridges) first network and a (geswitchtes by bridges) second network, which are connected to each other via at least three redundant data links, respectively only one is activated for the user data exchange.
- redundant data links only connecting the two networks of the communication network data links.
- the at least three redundant data links are a master data link which can be presettable activated or activated and used for the user data exchange and at least two presettable inactivatable or inactivated slave data links which can be used for the user data exchange in the event of failure of the master data link ,
- the redundant data links each connect a bridge of the first network and a bridge of the second network data-technically together.
- Each bridge of the second network can in each case be connected to a separate bridge of the first network.
- the bridge of the second network connected to the master data link is referred to here and below as the master bridge.
- the respective bridges of the second network connected to a slave data link are referred to here and below as slave bridges.
- Master and slave bridges of the second network may each be assigned individual path costs, with the master bridge being assigned the lowest path cost of all bridges connected to a redundant data link of the second network.
- the path costs assigned to the master and slave bridges of the second network can be stored in the master bridge in a corresponding data storage device.
- the path costs allocated to the master and slave bridges of the second network can in particular be transmitted by means of signals from the slave bridges to the master bridge, in particular based on the second network protocol.
- the first network of the communication network can msbeson- be installed as office LAN in a office environment.
- a first network protocol has been set up for data exchange.
- the first network protocol used in the first network is preferably RSTP according to IEEE standard 802. Iw, which forms a logical topology in the form of a spanning tree on the physical topology of the first network.
- the first network preferably has a meshed or star-shaped physical topology.
- the second network of the communication network can be installed, in particular, as an industrial LAN in an industrial environment and uses a second network protocol based in particular on the Ethernet standard for data exchange, which can be a standard or proprietary network protocol.
- the Network is different from the first network protocol, especially RSTP.
- the second network preferably has an annular topology.
- the inventive method for reconfiguring the communication network comprises the following steps:
- the master bridge Detecting a failure of the (default) activated master data link by the master bridge of the second network connected to the master data link.
- the failure of the master data link can be detected, for example, by a lack of reception of a signal transmitted by the bridge of the first network connected to the master data link by the master bridge ("loss-of-signal").
- the master bridge is provided for this purpose with a device for detecting a signal failure (hardware detector) of the data link. In this way, in particular a so-called hardware alarm of the master bridge can be triggered.
- Master bridge Generation of a first data packet (N1) by the master bridge and transmission of the first data packet (N1) to a slave bridge of the slave bridge connected to a slave data link second network.
- the master bridge selects the slave bridge of the second network for transmission of the first data packet in accordance with a preselected selection rule.
- the first data packet (N1) is transmitted from the master bridge of the second network to the slave bridge of the second network by means of the second network protocol.
- the master bridge After transmission of the first data packet by the master bridge: receiving and processing of the first data packet by the slave bridge, wherein the first data packet contains logical information by which the at least partial execution of the first network protocol, in particular RSTP, on one with the slave Data link connected port of the slave bridge is triggered.
- the first network protocol in particular RSTP
- Activation of the slave link by the first network protocol executed on the port of the slave link is preferably carried out by exporting a handshake mechanism defined in RSTP between the RSTP port of the slave bridge of the second network connected to the inactivated slave data link and a bridge of the first link connected to the inactivated slave data link network.
- Activation of the inactivated slave data link takes place here by means of routines standardized in RSTP.
- the method according to the invention advantageously comprises the further steps:
- the failure of the activated slave data link can, for example, based on a lack of receiving a signal sent from the connected to the slave data link bridge of the first network signal through the
- Slave bridge of the second network can be detected.
- the slave bridge is equipped for this purpose with a device for detecting a missing signal reception (hardware detector). As a result, in particular, a hardware alarm of the slave bridge can be triggered.
- the slave bridge After transmission of the second data packet by the slave bridge: receiving and processing of the second data packet (N2) by the master bridge, wherein the second data packet contains logical information by which the master bridge is informed about the failure of the slave data link.
- the master bridge Re-generating a first data packet (Nl) by the master bridge and transmitting the first data packet (Nl) to a slave bridge of the second network connected to a slave data link (not failed).
- the master bridge selects the slave bridge of the second network for transmission of the first data packet in accordance with the preselectable selection rule.
- the first data packet (N1) is transferred from the master bridge of the second network to the slave bridge of the second network by means of the second network protocol. factory transfer.
- the selected slave bridge Receiving and processing of the first data packet by the selected slave bridge, wherein the first data packet contains logical information by which the at least partially execution of the first network protocol, in particular RSTP, is triggered on a connected to the slave data link port of the slave bridge.
- the first network protocol in particular RSTP
- the slave data link is preferably activated by executing a handshake mechanism defined in RSTP between the RSTP port of the slave bridge of the second network connected to the inactivated slave data link and a bridge of the first link connected to the inactivated slave data link network. Activation of the inactivated slave data link takes place here by means of routines standardized in RSTP.
- the method for activating a further inactivated slave data link in the event of failure of a slave data link activated after failure of the master data link can be repeated for all slave data links of the communication network.
- a selection of the slave bridges for activating the slave data links connected to the slave bridges is carried out according to the slave bridges in each case allocated path costs.
- the master bridge and the slave bridge of the second network are path costs, in particular RSTP path costs, for example by the Assigned to network protocol.
- Particularly advantageous are the master bridge here assigned the lowest path costs.
- the master bridge for activating a slave data link advantageously selects those slave bridges which are assigned the subsequent path costs with respect to the master bridge.
- the master bridge advantageously selects that slave bridge which has the post-medium path costs with respect to the slave bridge of the failed slave data link. In this way, it can be ensured that the data connection between the two networks always has the lowest possible path costs.
- this comprises the following further steps:
- a third data packet (N3) by the master bridge and transfer of the third data packet to the slave bridge of the activated slave data link.
- the third data packet is transmitted to all slave bridges. This informs the slave bridges of the activated and deactivated slave data links about the restoration of the master data link.
- the slave bridge After transmission of the third data packet: receiving and processing of the third data packet by the slave bridge (s), wherein the third data packet contains logical information, by which termination of the execution of the first network protocol, in particular RSTP, on the slave bridge or a termination of the transmission of RSTP configuration frame by the slave bridge is effected.
- the third data packet contains logical information, by which termination of the execution of the first network protocol, in particular RSTP, on the slave bridge or a termination of the transmission of RSTP configuration frame by the slave bridge is effected.
- the following steps are performed to activate the restored master data link and to deactivate the second slave data link after detecting the restoration of the master data link by the master bridge:
- the master data link is preferably activated by exporting a handshake mechanism implemented in RSTP between the bridges of the first and second network which are directly connected to the master data link.
- a handshake mechanism implemented in RSTP between the bridges of the first and second network which are directly connected to the master data link.
- This can advantageously a particularly rapid reconfiguration of the logical topology in recovery of the master data links, in particular using routines implemented in RSTP.
- the invention further extends to a search as described above sch ⁇ ebenes packet-switched communications network with egg ⁇ nem a first network protocol onset first network and a different from the first network protocol second network protocol onset of the second network, in which the two networks interconnected by at least three redundant data links are, of which only one is activated for user data exchange, wherein a master data link is activated by default and at least two slave data links are disabled by default.
- the bridges in particular associated with a slave data link bridges, each turned so directed ⁇ that a process as described above is ausvigbar.
- the invention extends to a master bridge of a packet-switched communication network as described above.
- the OF INVENTION ⁇ extension extends to a slave bridge a pa ⁇ ketverstofften communication network as described above.
- FIG. 1A-1D are schematic representations to illustrate an exemplary embodiment of the erfmdungsgeschreiben
- Figs. 1A-1D schematically a Ausbowungs- example of the inventive communication network is open ⁇ shows.
- the designated as a whole by reference numeral 1 comprises a communi ⁇ nikationsnetztechnik installed in a Buroum poverty, maschenformiges, office, switched by bridges LAN 2 and an industrial-environment-installed annular bridge-switched industrial LAN 3.
- the physical topology of the office LAN 2 includes four bridges 4-7 which are meshed with each other in a meshed fashion via respective point-to-point links (data links).
- data links are shown by solid lines and not otherwise denoted.
- the IEEE standard 802. Iw standardized network protocol RSTP is executed.
- RSTP network protocol
- a logical topology in the form of a spanning tree is formed on the physical topology of the office LAN 2 given by the bridges and data links, which is used exclusively for the exchange of user data packets.
- the spanning tree is not nearer marked.
- the RSTP network protocol assigns unique identifiers (IDs) and path costs to all RSTP bridges and RSTP ports on the office LAN 2.
- IDs unique identifiers
- the bridges can change the state of their Change ports.
- Each configuration frame contains a series of fields, such as a flag field for indicating or confirming a topology change, a rootbuck ID field for identifying the rootbruck indicating priority and ID, a path cost field for specifying the path cost of the root bridge sending the BPDU , a message age field (MessAge) for specifying the period since the BPDU was sent, a MaxAge field for specifying a time after which the message is to be deleted, a Hello time field for specifying the period between regular configuration messages (Hello signals) the root bridge, and a forward delay field that indicates the wait time after a topology change.
- fields such as a flag field for indicating or confirming a topology change, a rootbuck ID field for identifying the rootbruck indicating priority and ID, a path cost field for specifying the path cost of the root bridge sending the BPDU , a message age field (MessAge) for specifying the period since the BPDU was sent, a MaxAge field for specifying
- RSTP uses four criteria to determine the highest priorities of the bridges or their ports. These are: the smallest Rootbrucken-ID, the lowest path cost to the Rootbrucke, the smallest Sendebrucken-ID and the smallest Port-ID.
- each bridge In order to determine a root bridge, in RSTP all ports of the bridges after initialization (for example, after a restart of the network) first in the state "Blockmg", each bridge assumes that it is itself a root bridge and a corresponding BPDU with their own Send ID as Rootbruck ID to the other bridges. Then the bridge with the lowest Rootbrucken-ID is used as rootbruck. If the rootbruck ID is identical, the lowest MAC address is used as a supplementary criterion.
- the root bridge From the selected root bridge, all network paths of the spanning tree are then determined, via which a data exchange between the bridges in the communication network is to take place. For this purpose, the root bridge first sends BPDUs to the other bridges. Each bridge then determines as root Port a port that has the lowest path cost to Rootbrucke. In the case of equal path costs, the port ID is used as a supplementary criterion. Subsequently, designate ports are determined based on the path cost and the designated bridges of the spanning tree are determined.
- the root bridge tells all bridges in the spanning tree at regular intervals via a corresponding BPDU (hello signal) that it is still there. If such a hello signal fails, for example because of the failure of a link or the root bridge itself, a reconfiguration of the communication network is required to determine a new spanning tree. Since at this time only BPDUs, i. H. Data packets are transmitted to determine a new spanning tree, the communication network for this period for a user data exchange is not usable.
- BPDU i. H.
- RSTP also identifies alternative ports that block BPDUs from other bridges and provide an alternative route to the root bridge if the root port goes down.
- RSTP proposes / agreement handshake mechanism between directly connected bridges.
- Proposal / Agreement handshake mechanism RSTP bridges automatically send BPDUs to the neighboring bridges at predeterminable intervals.
- RSTP specifies that a bridge loses its link to a neighboring bridge if it can not receive BPDUs within a predefined time period. In this way, a failure of a link can be detected quickly.
- the topology of the industry LAN 3 includes six bridges 8-13 which are annularly connected to each other via respective point-to-point data links.
- the data links between the bridges are shown by a solid line and not otherwise denoted.
- the office LAN 2 and the industrial LAN 3 are connected to each other via three redundant data links 14-16 in terms of data technology. These are a default activated for the user data exchange Master lmk 14 and two for the user data exchange preset inactivated slave data links 15, 16.
- FIG. 1A shows an initial situation for carrying out the method according to the invention, in which the master data log 14 is activated and the two slave data links 15, 16 are inactivated.
- the activated master data log 14 is therefore represented by a solid line, while the two inactivated slave data links 15, 16 are shown by broken lines.
- the two slave data links 15, 16 serve as activatable redundant connections (back-up lmks) between the two networks 2, 3rd
- the master data link 14 is connected to an RSTP port of the RSTP bridge 6 of the office LAN 2 and a proprietary port of the proprietary bridge 8 ("master bridge") of the industrial LAN 3 which uses the proprietary network protocol.
- Em first slave data link 15 is connected to an RSTP-executing RSTP port of the RSTP bridge 7 of the office LAN 2 and a proprietary port of the proprietary bridge 9 of the industrial LAN 3.
- the second slave data link 16 is connected to an RSTP port of the RSTP bridge 5 of the office LAN 2 and to a proprietary port of the proprietary bridge 13 of the industrial LAN 3.
- each data link between the two networks 2, 3 connects a bridge of one network to a separate bridge of the other network.
- Both ports connected to the master data interface 14 are activated, in particular the RSTP port of the RSTP bridge 6 of the office LAN 2 being in its "forwardmg" state.
- the RSTP port of the RSTP bridge 7 of the office LAN 2 connected to the first slave data link 15 is set in its "Blockmg” state.
- the RSTP port of the RSTP bridge 5 of the office LAN 2 connected to the second slave data link 16 is set to its "Blockmg" state.
- the RSTP bridges of the office LAN 2 and the bridges 8, 9, 13 of the industrial LAN 3 directly connected to the office LAN 2 via the data links 14-16 are RSTP path costs assigned.
- the master bridge 8 of the industrial LAN 3 connected to the master data link 14 the path costs of all bridges of the industrial LAN 3 directly connected to the office LAN 2 are stored in a data storage device.
- the path costs of the slave bridges of the industrial LAN 3 directly connected to the office LAN 2 can be sent to the master bridge 8 via messages (data packets) generated by the slave bridges, in particular based on the proprietary network protocol of the industrial LAN 3 become.
- FIG. 1B shows a situation in which, starting from the situation illustrated in FIG. 1A, with activated master data memory 14, this has fallen out for the payload data transmission.
- the failed master data file 14 is shown by a broken line.
- the failure of the activated master data link 14 is detected by the two bridges connected by the master data link 14 by a missing signal reception ("loss of signal") by a corresponding device for detecting a missing signal reception (hardware detector).
- this triggers a hardware alarm, as a result of which a first data packet N 1 from the master station Bridge 8 is generated.
- the master bridge 8 among the two slave bridges 9, 13 selects those to which the smaller RSTP path costs are assigned.
- this is the slave bridge 9 of the first slave data link 15.
- the master bridge 8 sends the first data packet N1 via the corresponding data link of the ring-shaped industrial LAN 3 to the slave bridge 9 connected to the first slave data link 15.
- the first data packet N1 contains logical information by which the slave bridge 9 is informed that the master link 14 for the user data exchange has failed.
- a flag "Fallen-Master-Datenlmk" is set in the first data packet N1.
- the slave bridge 9 of the industrial LAN 3 is in this case a highest bridge ID, ie the lowest priority assigned to all RSTP bridges of the office LAN 2, whereby it can be ensured that the slave bridge 9 is in formation a spanning tree of the office LAN 2 is not undesirably chosen as the new root bridge.
- the slave bridge 9 of the industrial LAN 3 which is now provided with an RSTP port, generates a first RSTP signal.
- the RSTP configuration frame RSTP-BPDUl is a suggestion message (pro posal) for activating the link to the first slave data link 15 (blocked) within the framework of the handshake mechanism implemented in RSTP ) RSTP ports of the RSTP bridge 7 of the office LAN 2.
- the RSTP bridge 7 Upon receiving and processing the first RSTP congestion frame through the RSTP bridge 7 of the office LAN 2, the RSTP bridge 7 generates a second RSTP congestion frame
- RSTP-BPDU2 sends the second RSTP-Conflgurationsrahmen to the slave bridge 9 of the Indust ⁇ e-LAN 3.
- the second RSTP-Schwiergurationsrahmen is another suggestion message (Proposal).
- the slave bridge 9 Upon receipt and processing of the second RSTP configuration frame by the slave bridge 9, it generates a third RSTP Conflicting Frame (RSTP-BPDU3) and sends the third RSTP Confluration Frame to the RSTP Bridge 7 of the Industrial LAN 3.
- the third one RSTP Conflict Framework is an agreement (Agreement).
- the RSTP port of the RSTP bridge 7 of the first slave data link 15 is set in its "Forwardmg" state, which places the blocked first slave data link 15 in its active state, which exchanges useful data between the two both networks. This is illustrated in FIG. 1B by a solid line for the first slave data link 15.
- the handshake mechanism for activating the blocked RSTP port connected to the first slave data link 15 corresponds to the routines standardized according to IEEE standard 802. Iw.
- FIG. 1C shows a further situation in which the first slave data link 15 activated for user data transmission has failed.
- the failure of the first slave data link 15 is detected by the slave bridge 9 connected to the first slave data link 15, for example by a hardware detector detecting the lack of reception of configuration BPDUs, which can be transmitted from the bridge 7 of the office LAN 2, can capture.
- this triggers a hardware alarm, as a result of which a second data packet N2 is generated by the slave bridge 9.
- the slave bridge 9 sends the second data packet N2 via the corresponding data link of the ring-shaped industrial LAN 3 to the master bridge 8 connected to the master data link 14.
- the second data packet N2 contains logical information by which the master bridge 8 is informed that the first slave data link 15 has failed for the user data exchange. For this purpose, for example, a flag "Fold-out slave data link" is set in the second data packet N2.
- the detection of the failure of the first slave data link 15 by means of the second data packet triggers a hardware alarm, as a result of which a first data packet N 1 is again generated by the master bridge 8 ,
- the master bridge 8 selects the next slave bridge 13 for transmission of the generated first data packet Nl.
- the master bridge 8 selects such a slave bridge, which are assigned the next lowest RSTP path costs with respect to the slave bridge 9 connected to the failed first slave data link 15, in this case the slave bridge 13.
- the master bridge 8 sends the first data packet N1 via the corresponding data link of the ring-shaped industrial LAN 3 to the slave bridge 13 connected to the second slave data link 16.
- the first data packet N1 ent - Holds logical information by which the slave bridge 13 is informed that the master data link 14 has failed for the user data exchange.
- a flag "Failed" Master data link for example, a flag "Failed" Master data link ".
- the slave bridge 13 of the second slave data link 16 By receiving and processing of the first data packet Nl by the slave bridge 13 of the second slave data link 16, a partial or complete execution of the network protocol RSTP according to IEEE standard 802. Iw is triggered on that port of the slave bridge 13, with the second Slave data link 16 is connected. As a result, the slave bridge 13 of the industrial LAN 3 appears opposite the office LAN 2 as an RSTP bridge.
- RSTP-BPDUl Conflagration frame
- RSTP-BPDU1 a proposal message (pro posal) for activating the (blocked) RSTP port of bridge 5 of the office LAN 2 connected to the second slave data link 16.
- the RSTP bridge 5 Upon receiving and processing the first RSTP congestion frame through the RSTP bridge 5 of the office LAN 2, the RSTP bridge 5 generates a second RSTP congestion frame (RSTP-BPDU2) and sends the second RSTP congestion frame to the slave bridge 13 of the Industrial LAN 3.
- the second RSTP Conflicting Frame is another Proposal Message (Proposal).
- the slave bridge 13 Upon receipt and processing of the second RSTP configuration frame by the slave bridge 13, it generates a third RSTP Conflict Frame (RSTP-BPDU3) and sends the third RSTP Confluration Frame to the bridge 5 of the Industrial LAN 3.
- the third RSTP Conflict frame is an understanding message (Agreement).
- the RSTP port of bridge 5 of the second Slave data links 16 Upon receipt of the acknowledge message, the RSTP port of bridge 5 of the second Slave data links 16 in its "Forwardmg" state, whereby the blocked second slave data link 16 is set to its active state, in which a user data exchange between the two networks is enabled. This is shown in Fig. IC by a solid line for the second
- the handshake mechanism for activating the blocked RSTP port connected to the second slave data link 16 corresponds to the routines standardized according to IEEE standard 802. Iw.
- Fig. ID another situation is shown in which the master lmk 14 is restored after its failure.
- the master bridge 8 of the industrial LAN 3, which is connected to the master data link 14, recognizes via incoming signals which are connected to the master data link 14
- the third data packet N3 is then sent by means of the proprietary network protocol of the Indust ⁇ e LAN 3 via the corresponding data links of the Indust ⁇ e LAN 3 to the slave bridges 9, 13.
- the third data packet N3 informs the slave bridges 9, 13 that the master data memory 14 has been restored.
- a flag "failed master data file" has been deleted.
- the detection of the restored master data link 14 by the master bridge 8 further t ⁇ gggert the partial or complete execution of the network protocol RSTP according to IEEE standard 802. Iw (only) on that port of the master bridge 8, with the blocked master lmk 14 is connected.
- the master bridge 8 appears opposite the office LAN 2 as RSTP bridge.
- RSTP-BPDUl Conflagration Frame
- RSTP-BPDU1 The configuration frame RSTP-BPDU1 is a proposal (proposal) within the framework of the handshake mechanism implemented in RSTP.
- the RSTP bridge 6 Upon receiving and processing the first RSTP congestion frame through the RSTP bridge 6 of the office LAN 2, the RSTP bridge 6 generates a second RSTP congestion frame (RSTP-BPDU2) and sends the second RSTP congestion frame to the master bridge 8. This is also illustrated by an arrow in Fig. ID.
- the second RSTP Conflicting Framework is a proposal to activate the blocked RSTP port of the Office LAN 2 bridge 6 connected to the Master Data Link 14.
- master bridge 8 of industry LAN 3 Upon receipt and processing of the second RSTP configuration frame, master bridge 8 of industry LAN 3 generates a third RSTP congestion frame (RSTP-BPDU3) and transmits the third RSTP congestion frame through its RSTP frame connected to master data library 14. Port to the RSTP bridge 6 of the office LAN 2 connected to the master data interface 14. This is illustrated by an arrow in FIG.
- the third RSTP configuration frame is an agreement to activate the blocked RSTP port of the bridge 6 of the office LAN 2 connected to the master data link 14.
- the blocked RSTP port of the RSTP bridge 6 of the office LAN 2 connected to the master data link 14 is then set to its "forwarding" state.
- the blocked master data link 14 is set to its active state, so that a user data exchange between the two
- Networks 2, 3 on the master data link 14 is enabled.
- the above-mentioned handshake mechanism for activating the blocked RSTP port of the RSTP bridge 6 of the office LAN 2 connected to the master data link 14 is performed by routines standardized in the IEEE 802. Iw standard.
- the second RSTP configuration frame (RSTP-BPDU2) received from master bridge 8 of industrial LAN 3 is forwarded unchanged to slave bridge 13 connected to second slave data link 16. Forwarding takes place here by the proprietary network protocol of the industrial LAN 3.
- the slave bridge 13 connected to the second slave data link 16 forwards the second RSTP configuration frame (RSTP-BPDU2) unchanged to the second slave data link 16 connected RSTP bridge 5 of the office LAN 2 on.
- the RSTP port in the "Forwarding" state of the RSTP bridge 5 of the office LAN 2 connected to the second slave data link 16 is set to its "blocking" state, so that the second slave data link 16 is deactivated.
- Networks are connected to another network in ring topology multi-redundant, with the Rekonflgurations- times for reconfiguring a data link connecting the two networks are very short.
- a restriction to a single redundant backup data is not necessary. In this way, a data connection between the two networks can be maintained even in the event of multiple failures of data links connecting the two networks.
- the complexity for configuring such a communication network is low.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
L'invention concerne un procédé de reconfiguration d'un réseau de communication à commutation par paquets comprenant un premier réseau utilisant un premier protocole de réseau et un deuxième réseau utilisant un deuxième protocole de réseau différent du premier protocole de réseau. Ces deux réseaux sont reliés par au moins trois liaisons de données redondantes, sur lesquelles une seule est activée à la fois pour l'échange de données utiles, une liaison de données maître étant activée par défaut et au moins deux liaisons de données esclaves étant inactivées par défaut. Le procédé selon l'invention est caractérisé par les étapes suivantes : détection d'une défaillance de la liaison de données maître ou d'une défaillance d'une liaison de données esclave par un pont maître du deuxième réseau relié à la liaison de données maître; génération d'un premier paquet de données par le pont maître et transmission de ce premier paquet de données à un pont esclave du deuxième réseau relié à une liaison de données esclave, ce pont esclave étant sélectionné par le pont maître conformément à une règle de sélection prédéterminable; réception et traitement du premier paquet de données par le pont esclave sélectionné, ce premier paquet de données contenant des informations logiques au moyen desquelles l'exécution au moins partielle du premier protocole de réseau est déclenchée sur un port du pont esclave relié à la liaison de données esclave et une activation de la liaison de données esclave est effectuée par l'intermédiaire du premier protocole de réseau exécuté sur le port du pont esclave.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102007015539A DE102007015539B4 (de) | 2007-03-30 | 2007-03-30 | Verfahren zum Rekonfigurieren eines Kommunikationsnetzwerks |
PCT/EP2008/053108 WO2008119649A1 (fr) | 2007-03-30 | 2008-03-14 | Procédé de reconfiguration d'un réseau de communication |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2130329A1 true EP2130329A1 (fr) | 2009-12-09 |
Family
ID=39469348
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP08717849A Withdrawn EP2130329A1 (fr) | 2007-03-30 | 2008-03-14 | Procédé de reconfiguration d'un réseau de communication |
Country Status (6)
Country | Link |
---|---|
US (1) | US8284658B2 (fr) |
EP (1) | EP2130329A1 (fr) |
CN (1) | CN101652963B (fr) |
CA (1) | CA2682425A1 (fr) |
DE (1) | DE102007015539B4 (fr) |
WO (1) | WO2008119649A1 (fr) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8817611B2 (en) * | 2009-03-18 | 2014-08-26 | Hirschmann Automation And Control Gmbh | Parallel operation of RSTP (rapid spanning tree protocol) and MRP (media redundancy protocol) and segmentation/coupling |
ES2656433T3 (es) * | 2010-01-08 | 2018-02-27 | Siemens Aktiengesellschaft | Nodo de red para una red de comunicaciones |
FR2978281B1 (fr) | 2011-07-20 | 2013-09-27 | Airbus Operations Sas | Procede de reconfiguration d'un dispositif de surveillance de l'environnement d'un aeronef |
US9100210B2 (en) * | 2011-11-15 | 2015-08-04 | Rockwell Automation Technologies, Inc. | Redundant gateway system for device level ring networks |
EP2688249B1 (fr) * | 2012-07-20 | 2016-04-27 | Siemens Aktiengesellschaft | Procédé de transmission de nouvelles dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante |
ES2534377T3 (es) | 2012-07-31 | 2015-04-22 | Siemens Aktiengesellschaft | Procedimiento para transmitir mensajes en una red de comunicación industrial que puede hacerse funcionar de forma redundante y aparato de comunicación para una red de comunicación industrial que puede hacerse funcionar de forma redundante |
EP2704370B1 (fr) | 2012-08-31 | 2018-02-07 | Siemens Aktiengesellschaft | Procédé de transmission de nouvelles dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante |
WO2014072374A1 (fr) | 2012-11-09 | 2014-05-15 | Siemens Aktiengesellschaft | Procédé de transmission de messages dans un réseau de communication industriel d'un système d'automatisation industriel et dispositif de communication d'un réseau de communication industriel |
EP2750340A1 (fr) | 2012-12-28 | 2014-07-02 | Siemens Aktiengesellschaft | Procédé de transmission de nouvelles dans un réseau de communication industriel à fonctionnement redondant et appareil d'infrastructure de réseau |
EP2750310A1 (fr) | 2012-12-28 | 2014-07-02 | Siemens Aktiengesellschaft | Procédé de synchronisation d'horloges locales dans un réseau de communication d'un système d'automatisation industriel et appareil d'infrastructure de réseau |
ES2659773T3 (es) * | 2013-03-15 | 2018-03-19 | Vivint, Inc | Uso de un panel de control como un punto de acceso inalámbrico |
DE102019114307A1 (de) * | 2019-05-28 | 2020-12-03 | Beckhoff Automation Gmbh | Automatisierungsnetzwerk, Netzwerkverteiler und Verfahren zur Datenübertragung |
CN111478778B (zh) * | 2020-04-03 | 2021-11-02 | 中电科航空电子有限公司 | 一种降低rstp环网功耗方法及其应用 |
US11496418B1 (en) * | 2020-08-25 | 2022-11-08 | Xilinx, Inc. | Packet-based and time-multiplexed network-on-chip |
CN114162067B (zh) * | 2021-12-16 | 2024-03-15 | 深圳市优必选科技股份有限公司 | 一种四足机器人及其总线模块 |
EP4425875A1 (fr) | 2023-02-28 | 2024-09-04 | Siemens Aktiengesellschaft | Procédé de transmission de données à haute disponibilité dans un système de communication, système de communication et appareil de communication |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6222855B1 (en) * | 1998-02-19 | 2001-04-24 | Lucent Technologies, Inc. | Method and apparatus for converting between differing data and command exchange protocols |
US6262977B1 (en) * | 1998-08-28 | 2001-07-17 | 3Com Corporation | High availability spanning tree with rapid reconfiguration |
US7107358B2 (en) * | 2001-09-12 | 2006-09-12 | Rockwell Automation Technologies, Inc. | Bridge for an industrial control system using data manipulation techniques |
US20030048501A1 (en) * | 2001-09-12 | 2003-03-13 | Michael Guess | Metropolitan area local access service system |
US6917986B2 (en) * | 2002-01-07 | 2005-07-12 | Corrigent Systems Ltd. | Fast failure protection using redundant network edge ports |
KR20050116363A (ko) * | 2002-12-20 | 2005-12-12 | 엔트라시스 네트워크스, 인크. | 스패닝 트리를 결정하는 장치 및 방법 |
JP2005269059A (ja) * | 2004-03-17 | 2005-09-29 | Fujitsu Ltd | データ中継装置、データ中継方法およびデータ中継プログラム |
US7983173B2 (en) * | 2004-05-10 | 2011-07-19 | Cisco Technology, Inc. | System and method for detecting link failures |
US7643409B2 (en) * | 2004-08-25 | 2010-01-05 | Cisco Technology, Inc. | Computer network with point-to-point pseudowire redundancy |
US7916668B2 (en) * | 2004-12-30 | 2011-03-29 | Alcatel Lucent | Spanning tree protocol with burst avoidance |
DE102005017021A1 (de) * | 2005-04-13 | 2006-10-19 | Siemens Ag | Verfahren und Vorrichtung zur Kommunikation zwischen Netzknotenelementen |
US7719957B2 (en) * | 2005-08-29 | 2010-05-18 | Alcatel Lucent | Resiliency in minimum cost tree-based VPLS architecture |
CN1941730A (zh) | 2005-09-26 | 2007-04-04 | 华为技术有限公司 | 实现rpr桥冗余保护的方法 |
-
2007
- 2007-03-30 DE DE102007015539A patent/DE102007015539B4/de not_active Expired - Fee Related
-
2008
- 2008-03-14 CA CA002682425A patent/CA2682425A1/fr not_active Abandoned
- 2008-03-14 WO PCT/EP2008/053108 patent/WO2008119649A1/fr active Application Filing
- 2008-03-14 US US12/593,972 patent/US8284658B2/en not_active Expired - Fee Related
- 2008-03-14 CN CN2008800111666A patent/CN101652963B/zh not_active Expired - Fee Related
- 2008-03-14 EP EP08717849A patent/EP2130329A1/fr not_active Withdrawn
Non-Patent Citations (1)
Title |
---|
See references of WO2008119649A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2008119649A1 (fr) | 2008-10-09 |
DE102007015539B4 (de) | 2012-01-05 |
DE102007015539A1 (de) | 2008-10-09 |
CA2682425A1 (fr) | 2008-10-09 |
CN101652963A (zh) | 2010-02-17 |
US20100110884A1 (en) | 2010-05-06 |
CN101652963B (zh) | 2012-08-08 |
US8284658B2 (en) | 2012-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE102007015539B4 (de) | Verfahren zum Rekonfigurieren eines Kommunikationsnetzwerks | |
EP2070256B1 (fr) | Procédé pour reconfigurer un réseau de communication | |
EP2343857B1 (fr) | Noeud de réseau pour un réseau de communication | |
DE102011114278B4 (de) | Verfahren und Vorrichtung, die eine Ausfallumschaltung für einen Punkt-Punkt-Tunnel für Split-Plane-Umgebungen drahtloser lokaler Netze bereitstellen | |
EP2688249B1 (fr) | Procédé de transmission de nouvelles dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante | |
DE102005032479B4 (de) | Fernsteuerung eines Vermittlungsknotens in einem Stapel von Vermittlungsknoten | |
EP2693700B1 (fr) | Procédé de transmission de messages dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante | |
EP2721784B1 (fr) | Procédé de fonctionnement d' un équipement de réseau et équipement de réseau | |
EP2838220B1 (fr) | Procédé de transmission redondante de messages dans un réseau de communication industriel et appareil de communication | |
EP1532771A1 (fr) | Methode d'essai de chemins de messages dans des reseaux de communication et element de reseau | |
EP2127329B1 (fr) | Filtrage de trames redondantes dans un noeud de réseau | |
DE102011114276B4 (de) | Ausfallsicherheit durch Routed Split Multi-Link Trunking für Split-Plane-Umgebungendrahtloser lokaler Netze | |
EP2130331B1 (fr) | Procédé de reconfiguration d'un réseau de communication | |
EP2127241B1 (fr) | Recherche de port cible dans des réseaux constitués de sous-réseaux reliés | |
EP2704370B1 (fr) | Procédé de transmission de nouvelles dans un réseau de communication industriel pouvant fonctionner de manière redondante et appareil de communication pour un réseau de communication industriel pouvant fonctionner de manière redondante | |
WO2021037466A1 (fr) | Procédé de transmission de données dans un réseau de communication fonctionnant de manière redondante et couplage de dispositif de communication | |
EP2750310A1 (fr) | Procédé de synchronisation d'horloges locales dans un réseau de communication d'un système d'automatisation industriel et appareil d'infrastructure de réseau | |
EP2143241B1 (fr) | Réseau de communication à commutation de paquets, et procédé de reconfiguration du réseau de communication | |
EP2817923B1 (fr) | Réseau de calculateurs avec un bus de liaison de forme annulaire | |
EP4425875A1 (fr) | Procédé de transmission de données à haute disponibilité dans un système de communication, système de communication et appareil de communication | |
EP2182680A1 (fr) | Procédé destiné au fonctionnement d'un réseau de communication et composants de communication | |
DE102022206121A1 (de) | Deadlock-freies lokales umleiten zur behandlung mehrerer lokaler verbindungsausfälle in hierarchischen netztopologien | |
EP2750340A1 (fr) | Procédé de transmission de nouvelles dans un réseau de communication industriel à fonctionnement redondant et appareil d'infrastructure de réseau | |
EP1394995A1 (fr) | La redondance dans l'infrastructure du réseau | |
EP1394987A1 (fr) | La redondance dans une infrastructrure de réseau |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20090813 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR |
|
17Q | First examination report despatched |
Effective date: 20100324 |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: SIEMENS AKTIENGESELLSCHAFT |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20161001 |