EP1768319B1 - Verfahren zur Redundanzbereitstellung in Brücken zwischen RPR-Ringen - Google Patents

Verfahren zur Redundanzbereitstellung in Brücken zwischen RPR-Ringen Download PDF

Info

Publication number
EP1768319B1
EP1768319B1 EP06019929A EP06019929A EP1768319B1 EP 1768319 B1 EP1768319 B1 EP 1768319B1 EP 06019929 A EP06019929 A EP 06019929A EP 06019929 A EP06019929 A EP 06019929A EP 1768319 B1 EP1768319 B1 EP 1768319B1
Authority
EP
European Patent Office
Prior art keywords
inter
ring
bridge
ring bridge
rpr
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.)
Not-in-force
Application number
EP06019929A
Other languages
English (en)
French (fr)
Other versions
EP1768319A1 (de
Inventor
Jian Li
Yilong Zhang
Zhifeng He
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP1768319A1 publication Critical patent/EP1768319A1/de
Application granted granted Critical
Publication of EP1768319B1 publication Critical patent/EP1768319B1/de
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

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/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
    • 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
    • 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/4637—Interconnected ring systems
    • 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

Definitions

  • the present invention relates to Resilient Packet Ring (RPR) techniques, and more particularly, to a method of inter-RPR ring bridge redundancy.
  • RPR Resilient Packet Ring
  • the RPR As the fast development of diversified Metropolitan Area Network (MAN) techniques, the RPR is used by more and more MANs for its advanced technique, effective investment, ascendant performance and diversity of services supported.
  • the RPR of which the architecture and technique are newly designed to satisfy the requirements of the packet MAN, is a ring network composed of packet switch devices.
  • the network adopting the RPR technique is called an RPR ring network and can be called an RPR ring for short.
  • the packet switch device on the RPR ring is called an RPR device.
  • the RPR ring can also be called a bridge mode RPR.
  • the device on the RPR ring can also be called an RPR bridge and the MAC address of the RPR bridge can be called an RPR MAC address.
  • Figure 1 the architecture of two RPR rings interconnecting at two RPR bridges is illustrated.
  • RPR inter-ring bridge is an RPR bridge which is on at least two RPR rings at the same time and it is in charge of forwarding a data packet between the at least two RPR rings.
  • the RPR inter-ring bridge will be called an inter-ring bridge for short; the RPR bridge will be called a bridge for short hereinafter.
  • a loop would be brought between the two RPR inter-ring bridges interconnecting the two RPR rings. That is, there would be a broadcast storm phenomenon between the RPR inter-ring bridge 1 and the RPR inter-ring bridge 2 shown in Figure 1 .
  • a minimum spanning tree without the loop is generated by prune branches through the Spanning Tree Protocol (STP) or Rapid Spanning Tree protocol (RSTP).
  • STP Spanning Tree Protocol
  • RSTP Rapid Spanning Tree protocol
  • the layer-two Ethernet packets are forwarded along the minimum spanning tree to avoid a loop in the layer-two communication.
  • European Patent EP 0 349 099 A2 addresses a method for improving communications in a bridge network between end nodes involving sensing thunking configurations and executing binding schemes to make certain daughter bridges involved in the trunking conditions behave as a plurality of bridges and forward messages in the correct time sequence.
  • This document discloses a designated bridge and daughter bridges corresponding to the primary inter-ring bridge and the secondary inter-ring bridges of the present invention.
  • the present invention provides a method of inter-RPR-ring bridge redundancy, by which the RPR ring may recover rapidly after a failure in the RPR ring, and the normal use of services on the RPR ring may be ensured.
  • the inter-RPR-ring bridge redundancy method includes: configuring a priority for each inter-ring bridge; constituting a redundancy group by more than one inter-ring bridge, which interconnects two RPR rings; configuring one inter-ring bridge in the redundancy group as a primary inter-ring bridge which is in charge of forwarding packets; configuring the other(s) as secondary inter-ring bridge(s); and electing an inter-ring bridge with the highest priority and having an inter-ring communication ability to be the primary inter-ring bridge, when the redundancy group changes.
  • the change of the redundancy group includes the change of the topology of the RPR rings consisting the redundancy group.
  • the method further includes each inter-ring bridge configures a node information table to store redundancy group information of each inter-ring bridge in the redundancy group.
  • the change of the redundancy group includes the change of the redundancy group information of an inter-ring bridge in the redundancy group.
  • the method further includes that configuring a control message; when the redundancy group information of an inter-ring bridge in the redundancy group changes, the inter-ring bridge broadcasting the control message carrying the redundancy group information of itself in the redundancy group; and when other inter-ring bridge(s) receives (receive) the control message, electing an inter-ring bridge with the highest priority and having the inter-ring communication ability to be the primary inter-ring bridge.
  • the step of electing an inter-ring bridge with the highest priority and having the inter-ring communication ability to be the primary inter-ring bridge includes when the primary inter-ring bridge has no inter-ring communication ability or there is an inter-ring bridge with a higher priority and having the inter-ring communication ability in the redundancy group, the primary inter-ring bridge exiting the primary state; and when a secondary inter-ring bridge has the inter-ring communication ability and there is (are) no other inter-ring bridge(s) with a higher priority and having the inter-ring communication ability in the redundancy group, the secondary inter-ring bridge upgrading to be the primary inter-ring bridge.
  • the step of the primary inter-ring bridge exiting the primary state includes the primary inter-ring bridge judging whether it has the inter-ring communication ability, if it has no such ability, exiting the primary state; otherwise, the primary inter-ring bridge judging whether there is an inter-ring bridge with a higher priority and having the inter-ring communication ability; when there is such an inter-ring bridge, the primary inter-ring bridge exiting the primary state.
  • the step of the secondary inter-ring bridge upgrading to be the primary inter-ring bridge includes the secondary inter-ring bridge judging whether it has the inter-ring communication ability, if it has the inter-ring communication ability, the secondary inter-ring bridge judging whether there is an inter-ring bridge with a higher priority and having the inter-ring communication ability; when there is no such an inter-ring bridge, the secondary inter-ring bridge upgrading to be the primary inter-ring bridge.
  • the step of judging whether it has the inter-ring communication ability includes judging whether both its two RPR bridge interfaces work normally, if they work normally, it has the inter-ring communication ability; otherwise, it has no inter-ring communication ability.
  • the step of the primary inter-ring bridge judging whether there is an inter-ring bridge with a higher priority and having the inter-ring communication ability includes judging whether there is an inter-ring bridge with a higher priority in the protection group; if there is such an inter-ring bridge in the protection group, judging whether the inter-ring bridge with a higher priority in the protection group has the inter-ring communication ability; and if the inter-ring bridge with a higher priority in the protection group has the inter-ring communication ability, the primary inter-ring bridge exiting the primary state.
  • the step of the secondary inter-ring bridge judging whether there is an inter-ring bridge with a higher priority and having the inter-ring communication ability includes judging whether there is an inter-ring bridge with a higher priority in the redundancy group, if there is no such an inter-ring bridge the secondary inter-ring bridge upgrading to be the primary inter-ring bridge; if there is such an inter-ring bridge, judging whether the inter-ring bridge with a higher priority in the redundancy group has the inter-ring communication ability; and if the inter-ring bridge with a higher priority in the redundancy group has no such inter-ring communication ability, the secondary inter-ring bridge upgrading to be the primary inter-ring bridge.
  • Each inter-ring bridge configures a node information table storing at least priority information of each inter-ring bridge in the redundancy group; and the step of judging whether there is an inter-ring bridge with a higher priority includes looking up the node information table configured by itself; and judging whether there is an inter-ring bridge with a higher priority in the redundancy group according to the records in the node information table.
  • the step of judging whether the inter-ring bridge with a higher priority in the redundancy group has the inter-ring communication ability includes: judging whether the two RPR bridge interfaces of the inter-ring bridge with a higher priority can communicate with the two RPR bridge interfaces on the two RPR rings respectively; if they can communicate with the two RPR bridge interfaces , the inter-ring bridge has the inter-ring communication ability; otherwise, the inter-ring bridge has no inter-ring communication ability.
  • the method further includes each inter-ring bridge refreshing its own topology structure table; wherein the step of judging whether the two RPR bridge interfaces of the inter-ring bridge with a higher priority can communicate with the two RPR bridge interfaces on the two RPR rings respectively includes: judging whether the two RPR bridge interfaces of the inter-ring bridge with a higher priority respectively exist in the corresponding topology structure tables of the two RPR rings where the inter-ring bridge belongs; if the two RPR bridge interfaces exists in the tables, the two RPR bridge interfaces of the inter-ring bridge with a higher priority can communicate with the two RPR bridge interfaces of itself on the two RPR rings respectively; otherwise, the two RPR bridge interfaces of the inter-ring bridge with a higher priority can not communicate with the two RPR bridge interfaces of itself on the two RPR rings respectively.
  • the redundancy group information comprises at least priority information of the inter-ring bridge and the primary/secondary state.
  • the primary inter-ring bridge is in charge of forwarding all packets or packets with the same characteristics.
  • inter-RPR-ring bridge redundancy makes inter-ring bridges constitute a redundancy group, elects one inter-ring bridge as a primary inter-ring bridge in the redundancy group which is in charge of forwarding packets and configuring the priority of every inter-ring bridge.
  • the redundancy group changes, the inter-ring bridge with the highest priority and having the ability of packet forwarding is elected to be the primary inter-ring bridge.
  • an RPR ring may recover rapidly after the RPR ring changes. As a result, the services on the RPR ring may be ensured to be normal and the network communication delay and the burden of the network communication may be reduced.
  • more than one inter-ring bridge which is the interconnection of the two RPR rings, is set to constitute a redundancy group.
  • One inter-ring bridge in the redundancy group is configured as a primary inter-ring bridge, while the other(s) is (are) secondary inter-ring bridge(s).
  • the primary inter-ring bridge is in charge of forwarding data packets between the two RPR rings.
  • a secondary inter-ring bridge upgrades to be the primary inter-ring bridge continuing to forward data packets between the two RPR rings.
  • the step of transmitting the data packets between the two RPR rings can be implemented by that the primary inter-ring bridge takes charge of forwarding all packets or packets with the same characteristics according to specific configurations. And the secondary inter-ring bridge(s) is (are) not in charge of forwarding these data packets.
  • the primary inter-ring bridge is invalid or whether a new primary inter-ring bridge needs to be elected can be reflected through the change of the topology of the RPR ring.
  • the topology detection and the topology convergence of the RPR ring only need 50 ms, after a change of the RPR ring topology, the time for electing a new primary inter-ring bridge through a special topology detection of the RPR ring will be less than 100 ms.
  • both the primary inter-ring bridge and the secondary inter-ring bridge(s) in the present embodiment can use the special topology detection function of the RPR ring to obtain the topology information of other inter-ring bridge(s) in the redundancy group.
  • a primary inter-ring bridge in the redundancy group can be elected in time when a change of the topology in the group takes place.
  • a node information table can be configured in each inter-ring bridge in the redundancy group, the node information including at least a bridge ID, a bridge priority, a current state of the bridge and RPR MAC information of the current two interfaces of the inter-ring bridge.
  • the reason that there are two interfaces in the inter-ring bridge is that the inter-ring bridge connects two RPR rings and the two interfaces of the inter-ring bridge are used to connect the two RPR rings respectively.
  • the bridge priority can be configured according to actual needs, for example, the smaller value the higher priority, or the larger value the higher priority.
  • the priority of the bridge can be determined according to value of the bridge ID.
  • Step 201 the primary inter-ring bridge recalculates the current topology structure after receiving the topology message, and refresh a topology structure table stored in the primary inter-ring bridge after the topology is convergent.
  • the primary inter-ring bridge since the primary inter-ring bridge is on both the two RPR rings at the same time, there are two topology structure tables stored in the primary inter-ring bridge corresponding to the two RPR rings respectively.
  • the primary inter-ring bridge if a topology message is received from the RPR ring 1, the primary inter-ring bridge will refresh the topology structure table of the RPR ring 1 stored in it. While, if a topology message is received from the RPR ring 2, the primary inter-ring bridge will refresh the topology structure table of the RPR ring 2 stored in it.
  • Step 202 the primary inter-ring bridge judges whether both its two RPR bridge interfaces have inter-ring communication ability, if both the two interfaces have the ability, proceeds to Step 203; and otherwise, proceeds to Step 206.
  • the step of judging whether both the two RPR bridge interfaces have the inter-ring communication ability can be implemented by that the primary inter-ring bridge judges whether the two RPR bridge interfaces of itself can forward packets normally, if they can forward packets normally, it means that they have the inter-ring communication ability; and otherwise, it means that they do not have the inter-ring communication ability.
  • Step 203 the primary inter-ring bridge looks up the node information table stored in it and judges whether there is an inter-ring bridge with a higher priority in the redundancy group, if there is such an inter-ring bridge, proceeds to Step 204; and otherwise, proceeds to Step 205.
  • the judging in Step 203 should be implemented in all the nodes in the redundancy group, no matter whether the previous state of the inter-ring bridge is invalid or not. In this way, it is ensured that none of the inter-ring bridge with a high priority will be neglected. Some inter-ring bridges on an RPR ring are invalid due to a link failure or other reasons. However, if the link is recovered, the inter-ring bridge with a higher priority will reappear on the RPR ring and it is eligible to be a primary inter-ring bridge.
  • Step 204 the primary inter-ring bridge judges whether the inter-ring bridge with a higher priority has the inter-ring communication ability. If the inter-ring bridge has the inter-ring communication ability, proceeds to Step 206; otherwise, proceeds to Step 205.
  • Step 206 will be performed as long as there is one inter-ring bridge with a higher priority and having the inter-ring communication ability.
  • the step of the primary inter-ring bridge judging whether the inter-ring bridge with a higher priority has the inter-ring communication ability can be performed as follows: first, assume that the inter-ring bridge with a higher priority is bridge A, the two RPR bridge interfaces of bridge A on each of the two RPR rings are RPR bridge interface A1 and RPR bridge interface A2 respectively, the current primary inter-ring bridge is bridge B, and the two RPR bridge interfaces of bridge B on each of the two RPR rings are RPR bridge interface B1 and RPR bridge interface B2.
  • the step of the primary inter-ring bridge judging whether the inter-ring bridge with a higher priority has the inter-ring communication ability includes that judging whether the RPR bridge interface A 1 of the bridge A can communicate with the RPR bridge interface B 1 of the bridge B on the RPR ring 1 and whether the RPR bridge interface A2 of the bridge A can communicate with the RPR bridge interface B2 of the bridge B on the RPR bridge 2. If the RPR bridge interface A 1 of the bridge A can communicate with the RPR bridge interface B1 of the bridge B and the RPR bridge interface A2 of the bridge A can communicate with the RPR bridge interface B2 of the bridge B, the bridge A has the inter-ring communication ability.
  • the step of judging whether the RPR bridge interface A1 of the bridge A can communicate with the RPR bridge interface B 1 of the bridge B on the RPR ring 1 includes that the bridge B looks up the topology information table of the RPR ring 1 stored in it and determines whether there is the RPR bridge interface A1. If there is the RPR bridge interface A1, the RPR bridge interface A1 of the bridge A can communicate with the RPR bridge interface B 1 of the bridge B on the RPR ring 1. Otherwise, the RPR bridge interface A 1 of the bridge A can not communicate with the RPR bridge interface B 1 of the bridge B on the RPR ring 1. A same method can be adopted to judge whether the RPR bridge interface A2 of the bridge A can communicate with the RPR bridge interface B2 of the bridge B or not. Hence, no more description will be given.
  • Step 205 the primary inter-ring bridge terminates the current process.
  • This step shows that the current primary inter-ring bridge still works well and there is no inter-ring bridge with a higher priority and having the inter-ring communication ability.
  • Step 206 the primary inter-ring bridge exits the primary state.
  • each secondary inter-ring bridge in the redundancy group receives and processes the topology message as well.
  • the specific processing procedure of each secondary inter-ring bridge is shown in Figure 3 .
  • Step 301 the secondary inter-ring bridge recalculates the current topology structure after receiving the topology message and refresh the topology structure table stored in it after the topology is convergent.
  • the specific refreshing method is the same as the refreshing method performed by the primary inter-ring bridge shown in Step 201. Thus no more description will be given.
  • Step 302 the secondary inter-ring bridge judges whether both its two RPR bridge interfaces have the inter-ring communication ability. If both the two interfaces have the inter-ring communication ability, proceeds to Step 303; and otherwise, proceeds to step 306.
  • Step 202 the method of judging is the same as that shown in Step 202. Thus no more description will be given.
  • Step 303 the secondary inter-ring bridge looks up the node information table stored in it and judges whether there is an inter-ring bridge with a higher priority in the redundancy group. If there is such an inter-ring bridge, proceeds to Step 304; and otherwise, proceeds to Step 305.
  • the judging in Step 303 should be implemented in all the nodes in the redundancy group, no matter whether the state of the inter-ring bridge is invalid or not.
  • Step 304 the secondary inter-ring bridge judges whether the inter-ring bridge with a higher priority has the inter-ring communication ability. If the inter-ring bridge has the inter-ring communication ability, proceeds to Step 306; and otherwise, proceeds to Step 305.
  • Step 306 will be performed as long as there is one inter-ring bridge with a higher priority and having the inter-ring communication ability.
  • the step of the secondary inter-ring bridge judging whether the inter-ring bridge with a higher priority has the inter-ring communication ability can adopt the same method as that in Step 204.
  • Step 305 the secondary inter-ring bridge upgrades to the primary state.
  • Step 306 the secondary inter-ring bridge terminates the current process.
  • Step 306 shows that in the redundancy group, there is an inter-ring bridge with a higher priority and having the inter-ring communication ability. So the secondary inter-ring bridge is not eligible to be a primary inter-ring bridge.
  • the flows shown in Figure 2 and Figure 3 can both ensure that when the topologies of the two RPR rings where the redundancy group belongs change, the current primary inter-ring bridge in the redundancy group is the one with the highest priority and having the inter-ring communication ability.
  • a waiting time can be further configured in the primary inter-ring bridge and the secondary inter-ring bridge(s) in accordance with the present embodiment.
  • the primary inter-ring bridge will wait the configured time when it is ready to exit the primary state, that is, between Step 204 and 206.
  • the secondary inter-ring bridge which is ready to upgrade to the primary state will also wait the configured time before upgrading to the primary state, that is, between Step 304 and 305.
  • the corresponding Step 206 and Step 305 will be performed respectively. Otherwise, the corresponding Step 205 and Step 306 will be performed respectively.
  • a parameter of the number of topology messages to be waited can also be configured in the primary inter-ring bridge and the secondary inter-ring bridge(s), that is, the primary inter-ring bridge which is ready to exit the primary state and the secondary inter-ring bridge which is ready to upgrade to the primary state will first wait the configured number of topology messages. And then if the state of the inter-ring bridge with the highest priority and having the ability to forward is steady, corresponding implementations will be performed.
  • Each inter-ring bridge in the redundancy group can discover whether there is a new inter-ring bridge being added or deleted through the topology message received. However, the inter-ring bridge in the redundancy group can not discover the change of the priorities of other inter-ring bridges in the redundancy group. Therefore, a new control message can be added to the redundancy group to transmit the state of each inter-ring bridge.
  • the control message carries at least a bridge ID of the inter-ring bridge, a bridge priority of the inter-ring bridge, the current state of the inter-ring bridge, RPR MAC information of the current two interfaces of the inter-ring bridge.
  • the information carried in the control message is called redundancy group information of the inter-ring bridge.
  • the inter-ring bridge When the protection information of an inter-ring bridge changes, the inter-ring bridge will broadcast a control message to other bridge(s) in the redundancy group informing the change of its state.
  • the node information table of each inter-ring bridge in the redundancy group will be refreshed according to its current state and the received control message from other inter-ring bridge(s). Specifically, the redundancy group information of other inter-ring bridge(s) stored in this inter-ring bridge is refreshed according to the received control message.
  • the redundancy group information of this inter-ring bridge is refreshed according to its own configurations and its state which is calculated by the current RPR ring topology.
  • the priority of one inter-ring bridge in the redundancy group is degraded due to such reasons as a manual configuration.
  • the priority of the inter-ring bridge After the priority of the inter-ring bridge is degraded, it will broadcast a control message carrying the changed redundancy group information to other inter-ring bridge(s) in the redundancy group.
  • Other bridge(s) in the redundancy group will refresh its (their) own node information table(s) according to the received redundancy group information and perform corresponding processes.
  • the specific processing procedure of the primary inter-ring bridge is the same as that shown in Figure 2 .
  • the specific processing procedure of the secondary inter-ring bridge(s) is (are) the same as that shown in Figure 3 . So no more description will be given.
  • the control message may be broadcasted to other inter-ring bridge(s) in the redundancy group not only when the priority of the inter-ring bridge changes, but also when the state of the inter-ring bridge changes.
  • the change of the state may be a result from the change of the topology or the change caused by a manual configuration or other reasons.
  • control message may be sent to other bridge(s) in the redundancy group not only when the redundancy group information changes, but also periodically.
  • the primary inter-ring bridge will implement the flow showed in Figure 2 .
  • the secondary inter-ring bridge(s) will implement the flow showed in Figure 3 .
  • a parameter of the number of control messages to be waited can be configured.
  • the primary inter-ring bridge which is ready to exit the primary state and the secondary inter-ring bridge which is ready to upgrade to the primary state, will wait the configured number of control messages first. After that, if the state of the inter-ring bridge with the highest priority and having the inter-ring communication ability is still steady, corresponding implementations will be performed.
  • the above embodiments introduce only the situation that a redundancy group is formed by two RPR rings.
  • the general situation is that one inter-ring bridge belongs to multiple redundancy groups.
  • one entry should be added to the node information table of each inter-ring bridge.
  • the entry is call group ID, which is used to illustrate which redundancy group formed by which two RPR rings that the inter-ring bridge belongs to.
  • the group ID entry should be added to the control message correspondingly.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Solid-Sorbent Or Filter-Aiding Compositions (AREA)
  • Fats And Perfumes (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (16)

  1. Verfahren für eine Resilient Packet Ring-Zwischenringbrückenredundanz (RPR-Zwischenringbrückenredundanz), das umfasst, dass
    eine Priorität für jede Zwischenringbrücke konfiguriert wird;
    eine Redundanzgruppe durch mehr als eine Zwischenringbrücke an zwei RPR-Ringen gebildet wird;
    eine Zwischenringbrücke in der Redundanzgruppe als eine primäre Zwischenringbrücke konfiguriert wird, die für ein Weiterleiten von Paketen verantwortlich ist;
    eine andere Zwischenringbrücke/andere Zwischenringbrücken als sekundäre Zwischenringbrücke(n) konfiguriert wird/werden; und
    eine Zwischenringbrücke mit der höchsten Priorität und mit einer Zwischenringkommunikationsfähigkeit gewählt wird, um die primäre Zwischenringbrücke zu sein, wenn sich die Redundanzgruppe ändert (202, 203, 204, 206, 302, 303, 304, 305).
  2. Verfahren nach Anspruch 1, wobei die Änderung der Redundanzgruppe die Änderung der Topologie der RPR-Ringe umfasst, die die Redundanzgruppe bilden.
  3. Verfahren nach Anspruch 1, das ferner umfasst, dass
    jede Zwischenringbrücke eine Knoteninformationstabelle konfiguriert, um eine Redundanzgruppeninformation jeder Zwischenringbrücke in der Redundanzgruppe zu speichern.
  4. Verfahren nach Anspruch 3, wobei die Änderung der Redundanzgruppe die Änderung der Redundanzgruppeninformation einer Zwischenringbrücke in der Redundanzgruppe umfasst.
  5. Verfahren nach Anspruch 4, das ferner umfasst, dass
    eine Steuernachricht konfiguriert wird;
    wenn sich die Redundanzgruppeninformation einer Zwischenringbrücke in der Redundanzgruppe ändert, die Zwischenringbrücke die Steuernachricht, die die Redundanzgruppeninformation über sie selbst trägt, in der Redundanzgruppe aussendet; und
    wenn eine andere Zwischenringbrücke/andere Zwischenringbrücken die Steuernachricht empfängt/empfangen, eine Zwischenringbrücke mit der höchsten Priorität und mit der Zwischenringkommunikationsfähigkeit gewählt wird, um die primäre Zwischenringbrücke zu sein.
  6. Verfahren nach Anspruch 1, wobei der Schritt des Wählens einer Zwischenringbrücke mit der höchsten Priorität und mit der Zwischenringkommunikationsfähigkeit, um die primäre Zwischenringbrücke zu sein, umfasst, dass
    wenn die primäre Zwischenringbrücke keine Zwischenringkommunikationsfähigkeit hat oder es eine Zwischenringbrücke mit einer
    höheren Priorität und mit der Zwischenringkommunikationsfähigkeit in der Redundanzgruppe gibt, die primäre Zwischenringbrücke den Primärzustand verlässt (202, 203, 204, 206); und
    wenn eine sekundäre Zwischenringbrücke die Zwischenringkommunikationsfähigkeit hat und es keine andere(n) Zwischenringbrücke(n) mit einer höheren Priorität und mit der Zwischenringkommunikationsfähigkeit in der Redundanzgruppe gibt, die sekundäre Zwischenringbrücke hochgestuft wird, um die primäre Zwischenringbrücke zu sein (302, 303, 304, 305).
  7. Verfahren nach Anspruch 6, wobei der Schritt, dass die primäre Zwischenringbrücke den Primärzustand verlässt, umfasst, dass
    die primäre Zwischenringbrücke beurteilt, ob sie die Zwischenringkommunikationsfähigkeit hat (202), und wenn sie keine solche Fähigkeit hat, den Primärzustand verlässt (206); andernfalls die primäre Zwischenringbrücke beurteilt, ob es eine Zwischenringbrücke mit einer höheren Priorität und mit der Zwischenringkommunikationsfähigkeit gibt (203, 204); wenn es solch eine Zwischenringbrücke gibt, die primäre Zwischenringbrücke den Primärzustand verlässt (206).
  8. Verfahren nach Anspruch 6, wobei der Schritt des Hochstufens der sekundären Zwischenringbrücke, um die primäre Zwischenringbrücke zu sein, umfasst, dass
    die sekundäre Zwischenringbrücke beurteilt, ob sie die Zwischenringkommunikationsfähigkeit hat (302), und wenn sie die Zwischenringkommunikationsfähigkeit hat, die sekundäre Zwischenringbrücke beurteilt, ob es eine Zwischenringbrücke mit einer höheren Priorität und mit der Zwischenringkommunikationsfähigkeit gibt (303, 304); wenn es keine solche Zwischenringbrücke gibt, die sekundäre Zwischenringbrücke hochgestuft wird, um die primäre Zwischenringbrücke zu sein (305).
  9. Verfahren nach Anspruch 7 oder 8, wobei der Schritt des Beurteilens, ob sie die Zwischenringkommunikationsfähigkeit hat, umfasst, dass
    beurteilt wird, ob ihre beiden RPR-Brückenschnittstellen normal arbeiten, und wenn sie normal arbeiten, sie die Zwischenringkommunikationsfähigkeit hat; andernfalls hat sie keine Zwischenringkommunikationsfähigkeit.
  10. Verfahren nach Anspruch 7, wobei der Schritt, dass die primäre Zwischenringbrücke beurteilt, ob eine Zwischenringbrücke mit einer
    höheren Priorität und mit der Zwischenringkommunikationsfähigkeit vorhanden ist, umfasst, dass
    beurteilt wird, ob es eine Zwischenringbrücke mit einer höheren Priorität in der Schutzgruppe gibt (203);
    wenn es solch eine Zwischenringbrücke in der Schutzgruppe gibt, beurteilt wird, ob die Zwischenringbrücke mit einer höheren Priorität in der Schutzgruppe die Zwischenringkommunikationsfähigkeit hat (204); und
    wenn die Zwischenringbrücke mit einer höheren Priorität in der Schutzgruppe die Zwischenringkommunikationsfähigkeit hat, die primäre Zwischenringbrücke den Primärzustand verlässt (206).
  11. Verfahren nach Anspruch 8, wobei der Schritt, dass die sekundäre Zwischenringbrücke beurteilt, ob es eine Zwischenringbrücke mit
    einer höheren Priorität und mit der Zwischenringkommunikationsfähigkeit gibt, umfasst, dass
    beurteilt wird, ob es eine Zwischenringbrücke mit einer höheren Priorität in der Redundanzgruppe gibt (303),
    wenn es keine solche Zwischenringbrücke gibt, die sekundäre Zwischenringbrücke hochgestuft wird, um die primäre Zwischenringbrücke zu sein (305);
    wenn es solch eine Zwischenringbrücke gibt, beurteilt wird, ob die Zwischenringbrücke mit einer höheren Priorität in der Redundanzgruppe die Zwischenringkommunikationsfähigkeit hat (304); und
    wenn die Zwischenringbrücke mit einer höheren Priorität in der Redundanzgruppe keine solche Zwischenringkommunikationsfähigkeit hat, die sekundäre Zwischenringbrücke hochgestuft wird, um die primäre Zwischenringbrücke zu sein (305).
  12. Verfahren nach Anspruch 10 oder 11, wobei jede Zwischenringbrücke eine Knoteninformationstabelle konfiguriert, die zumindest eine Prioritätsinformation jeder Zwischenringbrücke in der Redundanzgruppe speichert; und
    wobei der Schritt des Beurteilens, ob es eine Zwischenringbrücke mit einer höheren Priorität gibt, umfasst, dass
    in der durch sie selbst konfigurierten Knoteninformationstabelle nachgeschlagen wird; und
    entsprechend den Aufzeichnungen in der Knoteninformationstabelle beurteilt wird, ob es eine Zwischenringbrücke mit einer höheren Priorität in der Redundanzgruppe gibt.
  13. Verfahren nach Anspruch 10 oder 11, wobei der Schritt des Beurteilens, ob die Zwischenringbrücke mit einer höheren Priorität in der Redundanzgruppe die Zwischenringkommunikationsfähigkeit hat, umfasst, dass
    beurteilt wird, ob die beiden RPR-Brückenschnittstellen der Zwischenringbrücke mit einer höheren Priorität jeweils mit den beiden RPR-Brückenschnittstellen an den beiden RPR-Ringen kommunizieren können;
    wenn sie mit den beiden RPR-Brückenschnittstellen kommunizieren können, die Zwischenringbrücke die Zwischenringkommunikationsfähigkeit hat; die Zwischenringbrücke ansonsten keine Zwischenringkommunikationsfähigkeit hat.
  14. Verfahren nach Anspruch 13, das ferner umfasst, dass
    jede Zwischenringbrücke ihre eigene Topologiestrukturtabelle aktualisiert (201, 301);
    wobei der Schritt des Beurteilens, ob die beiden RPR-Brückenschnittstellen der Zwischenringbrücke mit einer höheren Priorität jeweils mit den beiden RPR-Brückenschnittstellen an den beiden RPR-Ringen kommunizieren können, umfasst, dass
    beurteilt wird, ob die beiden RPR-Brückenschnittstellen der Zwischenringbrücke mit einer höheren Priorität jeweils in den entsprechenden Topologiestrukturtabellen der beiden RPR-Ringe vorhanden sind, zu denen die Zwischenringbrücke gehört;
    wenn die beiden RPR-Brückenschnittstellen in den Tabellen vorhanden sind, die beiden RPR-Brückenschnittstellen der Zwischenringbrücke mit einer höheren Priorität jeweils mit den eigenen beiden RPR-Brückenschnittstellen an den beiden RPR-Ringen kommunizieren können; andernfalls die beiden RPR-Brückenschnittstellen der Zwischenringbrücke mit einer höheren Priorität jeweils nicht mit den eigenen beiden RPR-Brückenschnittstellen an den beiden RPR-Ringen kommunizieren können.
  15. Verfahren nach Anspruch 3, 4 oder 5, wobei die Redundanzgruppeninformation zumindest eine Prioritätsinformation der Zwischenringbrücke und den Primär-/ Sekundärzustand umfasst.
  16. Verfahren nach Anspruch 1, 2, 3, 4, 5, 6, 7, 8, 10 oder 11, wobei die primäre Zwischenringbrücke für ein Weiterleiten aller Pakete oder von Paketen mit denselben Eigenschaften verantwortlich ist.
EP06019929A 2005-09-26 2006-09-22 Verfahren zur Redundanzbereitstellung in Brücken zwischen RPR-Ringen Not-in-force EP1768319B1 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNA2005101050259A CN1941730A (zh) 2005-09-26 2005-09-26 实现rpr桥冗余保护的方法

Publications (2)

Publication Number Publication Date
EP1768319A1 EP1768319A1 (de) 2007-03-28
EP1768319B1 true EP1768319B1 (de) 2008-05-21

Family

ID=37188938

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06019929A Not-in-force EP1768319B1 (de) 2005-09-26 2006-09-22 Verfahren zur Redundanzbereitstellung in Brücken zwischen RPR-Ringen

Country Status (7)

Country Link
US (1) US20070104093A1 (de)
EP (1) EP1768319B1 (de)
CN (2) CN1941730A (de)
AT (1) ATE396565T1 (de)
CA (1) CA2622131A1 (de)
DE (1) DE602006001282D1 (de)
WO (1) WO2007033563A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105915426A (zh) * 2016-06-20 2016-08-31 普联技术有限公司 环形网络的故障恢复方法及装置

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7898942B2 (en) * 2005-03-31 2011-03-01 Nec Corporation Ring network system, failure recovery method, failure detection method, node and program for node
CN101128041B (zh) * 2006-08-15 2010-05-12 华为技术有限公司 接入网和核心网间下行数据隧道失效后的处理方法和系统
CN101136830B (zh) * 2006-09-01 2011-01-12 华为技术有限公司 Rpr桥故障恢复后的环路避免方法
JP4848254B2 (ja) * 2006-11-29 2011-12-28 アラクサラネットワークス株式会社 リングネットワークを構成する装置
CN101262400A (zh) * 2007-03-09 2008-09-10 华为技术有限公司 一种桥模式弹性分组环冗余保护的方法和系统
CN100461739C (zh) * 2007-03-13 2009-02-11 华为技术有限公司 Rpr桥冗余保护方法及rpr桥环设备
DE102007015539B4 (de) 2007-03-30 2012-01-05 Siemens Ag Verfahren zum Rekonfigurieren eines Kommunikationsnetzwerks
DE102007021922B4 (de) * 2007-05-10 2012-11-22 Siemens Ag Paketvermitteltes Kommunikationsnetzwerk und Verfahren zum Rekonfigurieren des Kommunikationsnetzwerks
JP2009016905A (ja) * 2007-06-29 2009-01-22 Fujitsu Ltd パケットネットワークシステム
CN101534232B (zh) * 2008-03-10 2012-12-19 中兴通讯股份有限公司 一种防止以太多环网络中出现网络风暴的方法
CN101252500B (zh) * 2008-04-16 2012-08-08 杭州华三通信技术有限公司 任意拓扑相交环网的实现方法、节点和相交环网
IL199146A0 (en) * 2009-06-04 2010-04-29 Eci Telecom Ltd Method and network for combined protection of ethernet traffic
CN101582848A (zh) * 2009-06-18 2009-11-18 中兴通讯股份有限公司 一种弹性分组环跨环保护方法和系统
CN101815315B (zh) * 2010-03-12 2015-05-13 中兴通讯股份有限公司 一种冗余备份倒换方法、装置和系统
US20120314565A1 (en) * 2010-03-30 2012-12-13 Telefonaktiebolaget L M Ericsson (Publ) Method for protection against superloops in an ethernet ring
KR101720347B1 (ko) * 2011-01-20 2017-03-27 엘에스산전 주식회사 적응성의 다중 링 네트워크 시스템 및 우회경로 설정방법
CN102546345A (zh) * 2011-12-30 2012-07-04 Ut斯达康通讯有限公司 利用生成树协议实现弹性分组环跨环保护的方法
CN102724065B (zh) * 2012-05-22 2016-02-17 长沙中联消防机械有限公司 一种网络通信系统及包括该系统的工程机械设备
CN103229456B (zh) * 2012-12-28 2016-06-15 华为技术有限公司 传输组播业务的系统、装置和方法
EP2887593B1 (de) * 2013-12-20 2019-10-09 ABB Schweiz AG Netzwerkschnittstelle zur übertragung von schutzdaten eines stromnetzes
JP2016134130A (ja) * 2015-01-22 2016-07-25 三菱電機株式会社 マルチリングネットワーク
US10412012B2 (en) * 2015-09-22 2019-09-10 Arris Enterprises Llc Intelligent, load adaptive, and self optimizing master node selection in an extended bridge
CN108600097B (zh) * 2018-04-20 2020-09-22 闫晓峰 可多路径传输数据的通讯设备、数据通讯网络系统及数据通讯方法
CN109600290A (zh) * 2018-12-27 2019-04-09 苏州拓康自动化技术有限公司 一种环形网络中多主共存的方法
CN114745352B (zh) * 2022-03-31 2024-02-09 新华三技术有限公司合肥分公司 一种报文转发方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US1547362A (en) * 1922-07-19 1925-07-28 Casale Ammonia Company Apparatus for the electrolysis of water
DE68921373T2 (de) * 1988-06-27 1995-10-19 Digital Equipment Corp Transparente Lastteilung für parallele Netzwerke.
EP1324543A1 (de) * 2001-12-26 2003-07-02 Alcatel Verfahren zum Schutz von RPR Netzen mit erweiterter Topologie, insbesondere RPR Ring zu Ring und vermaschte Hauptnetze
EP1328090A1 (de) * 2002-01-09 2003-07-16 Alcatel Verfahren zur Topologiebestimmung, System und Knoten
US7383354B2 (en) * 2002-02-12 2008-06-03 Fujitsu Limited Spatial reuse and multi-point interconnection in bridge-interconnected ring networks
CN100337453C (zh) * 2004-03-19 2007-09-12 华为技术有限公司 在弹性分组环之间实现报文转发的方法及弹性分组环网络
JP4459018B2 (ja) * 2004-10-28 2010-04-28 富士通株式会社 ノード装置
JP4526423B2 (ja) * 2005-03-17 2010-08-18 富士通株式会社 リング間接続方法及び装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105915426A (zh) * 2016-06-20 2016-08-31 普联技术有限公司 环形网络的故障恢复方法及装置
CN105915426B (zh) * 2016-06-20 2019-06-04 普联技术有限公司 环形网络的故障恢复方法及装置

Also Published As

Publication number Publication date
US20070104093A1 (en) 2007-05-10
EP1768319A1 (de) 2007-03-28
ATE396565T1 (de) 2008-06-15
CN101160836B (zh) 2010-10-06
CA2622131A1 (en) 2007-03-29
WO2007033563A1 (fr) 2007-03-29
CN1941730A (zh) 2007-04-04
DE602006001282D1 (de) 2008-07-03
CN101160836A (zh) 2008-04-09

Similar Documents

Publication Publication Date Title
EP1768319B1 (de) Verfahren zur Redundanzbereitstellung in Brücken zwischen RPR-Ringen
EP2104994B1 (de) Auf hash basierendes multi-homing
CN101047601B (zh) 基于vpls的双归属网络的实现方法及系统
EP2304904B1 (de) Verfahren und System zur Streckenaggregation
EP2533475A1 (de) Verfahren und system für host-routenerreichbarkeit in einem zugangsring eines pakettransportnetzwerkes
EP2161880B1 (de) Verfahren zum verarbeiten einer ethernet ring nachricht und das verfahren verwendendes ethernet ring schutzsystem
CA2439865A1 (en) Method and apparatus for priority-based load balancing for use in an extended local area network
WO2005020022A2 (en) Self-healing tree network
KR20100103459A (ko) 멀티포인트 및 루트형 멀티포인트 보호 스위칭
WO2008107883A2 (en) Prevention of frame duplication in interconnected ring networks
JP4705492B2 (ja) リングノード装置及びリングノード冗長方法
US7342877B1 (en) Method and system for providing a loop-free ring topology
US10489236B2 (en) Method and system for managing a communication network
Huynh et al. RRR: Rapid ring recovery submillisecond decentralized recovery for ethernet ring
JP2010141845A (ja) 複数のサーバを有する通信装置及び通信方法
JPWO2006075402A1 (ja) オープンループネットワークノード装置及びオープンループネットワーク制御方法
Cisco Configuring Spanning Tree
Cisco Configuring Spanning Tree
CN112866143A (zh) 一种实现802.1cb协议的装置及芯片
EP2429129A1 (de) Verfahren zum netzwerkschutz und architektur zum netzwerkschutz
KR102665282B1 (ko) 다중 링 네트워크에서 패킷 루핑을 방지하는 방법
KR102708585B1 (ko) 링 네트워크에서의 통신 라인 절체 방법
JP2010171468A (ja) スイッチングハブ
CN111510364A (zh) 一种报文转发方法和系统
CN113875196A (zh) 通信装置

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

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 HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REF Corresponds to:

Ref document number: 602006001282

Country of ref document: DE

Date of ref document: 20080703

Kind code of ref document: P

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080901

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080921

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080821

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20081021

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20090224

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080821

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20081122

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080521

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080822

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602006001282

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20210812

Year of fee payment: 16

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20210811

Year of fee payment: 16

Ref country code: DE

Payment date: 20210810

Year of fee payment: 16

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602006001282

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20220922

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230401

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220922