EP2238717B1 - Datenkommunikationsverfahren zwischen endgeräten über mehrere ethernet-basierende netzwerke eines redundanz-systems - Google Patents

Datenkommunikationsverfahren zwischen endgeräten über mehrere ethernet-basierende netzwerke eines redundanz-systems Download PDF

Info

Publication number
EP2238717B1
EP2238717B1 EP08858285.3A EP08858285A EP2238717B1 EP 2238717 B1 EP2238717 B1 EP 2238717B1 EP 08858285 A EP08858285 A EP 08858285A EP 2238717 B1 EP2238717 B1 EP 2238717B1
Authority
EP
European Patent Office
Prior art keywords
ethernet
management module
operational
network
physical link
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.)
Active
Application number
EP08858285.3A
Other languages
English (en)
French (fr)
Other versions
EP2238717A1 (de
Inventor
Gilles Colas
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.)
Safran Electronics and Defense SAS
Original Assignee
Safran Electronics and Defense SAS
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 Safran Electronics and Defense SAS filed Critical Safran Electronics and Defense SAS
Publication of EP2238717A1 publication Critical patent/EP2238717A1/de
Application granted granted Critical
Publication of EP2238717B1 publication Critical patent/EP2238717B1/de
Active 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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors
    • H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections

Definitions

  • the present invention relates to a redundancy system of an Ethernet type network.
  • One of these constraints is to ensure that in the event of a network failure, for example following the break of a link between two terminal equipments of the network, the communications between these two terminal equipments can be re-established after a interruption bounded in time and whose duration is known a priori.
  • the application will not allow the loss of service, that is, will require that all data lost during this interruption be reissued. This is called a high criticality network.
  • the loss of service will be tolerated, that is to say, it will be tolerated that some data is lost, it is called lower criticality network. In this case, data loss is usually handled by high-level protocol layers.
  • Ethernet technology is widely used for this type of application because the corresponding components, widely used in commerce, are inexpensive.
  • a routing protocol is generally used on this technology because it makes it possible to solve connection problems by varying the paths taken by the routed data, paths qualified as paths ( US2002 / 152320 , US2007 / 076590 ).
  • the Fig. 1 schematically represents an example of Ethernet network according to the state of the art.
  • the Ethernet network ETH comprises a plurality of terminal equipments Ti, in this case four, and a plurality of routers RTj, in this case four.
  • the communication between two terminal equipments Ti and T i + 1 is performed via a plurality of routers.
  • Each terminal equipment is connected to a router by a physical Ethernet link and the routers are also connected to each other so as to multiply the possibilities of paths between the different terminal equipments.
  • each terminal equipment Ti comprises a link management module MGLi, also called Ethernet interface, the purpose of which is to allow the interface between a physical Ethernet link, such as for example a cable, and protocol layers of higher level of terminal equipment Ti which are usually organized in the form of an IP protocol stack ( Internet Protocol ).
  • MGLi link management module
  • Ethernet interface the purpose of which is to allow the interface between a physical Ethernet link, such as for example a cable, and protocol layers of higher level of terminal equipment Ti which are usually organized in the form of an IP protocol stack ( Internet Protocol ).
  • the Fig. 2 schematically represents the architecture of a MGLi link management module according to the state of the art.
  • the MGLi link management module has an RX receive port and a TX transmit port connected to a physical Ethernet link (not shown), a PHY link physical management module, which implements a low-level protocol that is the physical layer of the OSI model, a Media Access Control (MAC) management module that implements, among other things, the Ethernet protocol and allows bi-directional communication between the physical layer and the level protocol layers higher HP, and a BU data bus that provides two-way data transmission between PHY and MAC modules.
  • the BU bus complying with the IEEE MII standard ( Media Independant Interface in English) is generally used.
  • the physical PHY link management module is responsible for generating and analyzing the physical signals that pass through the physical Ethernet link.
  • the MAC media management module handles the analysis and assembly of packets as well as as communication with HP's top-level protocol layers.
  • the signals transiting the Ethernet link are analyzed and converted into digital data by the PHY module.
  • This digital data is then transmitted to the MAC module, which analyzes it in the form of Ethernet packets or frames. These packets are then forwarded to the HP top-level protocol layers.
  • the media management module MAC receives the data to be transmitted from the higher level protocol layers HP, typically the IP protocol stack in the form of IP packets. It assembles the Ethernet packets or frames carrying the IP data and transmits them to the PHY link physical management module for transmission in the form of signals on the physical Ethernet link.
  • each router RTi includes a routing table TABi which indicates to which port should be directed an incoming data and according to the destination address of this data.
  • This TABi routing table is previously auto-configured automatically by the router RTi.
  • each RTi router can communicate with each other.
  • the terminal equipment can communicate with each other.
  • the data transmitted by the terminal equipment T1 and to the terminal equipment T3 are routed by the router RT1, then RT3 (arrow referenced C1 to the Fig. 1 ).
  • the communication between the two terminal equipments is then interrupted and each router RTi must then be re-configured, one speaks convergence of the routing protocol so that a new path can be defined between the two end devices.
  • the data transmitted by the terminal equipment T1 now go through the router RT1, RT4 and RT3 before being received by the terminal equipment T3 (arrow referenced C2).
  • the routing protocol of an Ethernet network thus makes it possible to solve the problem of breaking a link between routers of this network.
  • the convergence of such a protocol which is at the level of the network layer of the OSI model, that is to say at a higher level than that of the physical layer, is complex to implement particularly when the number of routers is high.
  • the Conventional routing protocols are not necessarily deterministic, that is to say that their convergence is not assured in all cases.
  • the patent application EP1,394,985 describes a method for testing each possible path between a host device and a destination device, regardless of the Ethernet network used for sending / receiving a test message between this host device and a single destination device. For this purpose, in the case where a test message is not received during a selected period of time, another test message is sent by the host equipment to a device on another path. The method therefore consists in considering that another network is inoperative when all its paths are no longer valid and the host equipment then uses another network.
  • AFDX network (Avionics Full DupleX) developed and standardized by the European avionics industry to equip the Airbus A380. It is a network intended to support the internal communications of an aircraft (ARINC 664 (Part 7)).
  • the AFDX network implements the redundancy of an Ethernet network by another equivalent Ethernet network.
  • Each frame transiting on the AFDX network is sent at the same time on the two redundant networks of each other and a complex frame numbering system allows the receiver to associate the two redundant frames received.
  • the AFDX network is reliable, deterministic, does not cause loss of service in case of failure of one of the two networks.
  • the implementation of the AFDX network is very complicated and therefore very expensive because it involves, in particular, the protocols of the network layer and a protocol for managing transmission / reception of the frames on these two networks. .
  • Ethernet technology is used, technology that makes it possible to reduce the costs associated with hardware components such as routers, the cost of implementing the AFDX network remains high.
  • the Ethernet technology has a major disadvantage in the context of its use for the deployment of such a redundant system of an Ethernet network.
  • the present invention aims to overcome these disadvantages by proposing a simple and inexpensive solution in terms of implementation and hardware that is applicable to a redundant system of a low-critical Ethernet star network.
  • the present invention consists in implementing at the level of the closest layer physically of the link, that is to say at the level of the link management module, a communication method whose purpose is to determine a first network. the redundancy system which will be used for the communication between them of the terminal equipment, to monitor the operation of this network throughout these communications and to determine a new network of redundancy system in case of failure of the network used until then.
  • this method is transparent and non-intrusive at the level of higher level protocol layers thus avoiding any modification of the protocols of these different upper layers.
  • the routers can then be replaced by switches which are much less expensive because all reliability intelligence is reported at the level of the physical layer.
  • the present invention relates to a method of data communication between at least two terminal devices from a plurality of Ethernet type networks independent of each other and each allowing the communication of data between said at least two terminal equipment.
  • the method is characterized in that it comprises a step of determining a first Ethernet network, said operational, among a set of potentially operational networks obtained from said plurality of Ethernet networks, a step of controlling the operation of said Ethernet network and a step of determining a new Ethernet network among said set of potentially operational networks.
  • the determination of said operational Ethernet network is based on the communication between said dedicated Ethernet frame terminal equipment.
  • each terminal equipment comprises a physical link management module Ethernet network
  • the link physical management modules relating to the Ethernet networks of said set of potentially operational networks are scanned as long as a dedicated frame is not received via one of said physical link management modules and, on the other hand, dedicated frames are transmitted successively via the physical link management modules relating to the Ethernet networks of said set of potentially operational networks, in the case where a dedicated frame is received via one of the said physical management modules of link, the Ethernet network relating to said physical link management module is considered to be operational.
  • each dedicated frame is transmitted via a physical link management module after a random time value chosen from a range values whose lower limit is at least twice the transmission time of a frame between two of said terminal equipment.
  • the physical link management module that is relative to said operational network is scanned, for a previously defined time value which is at least equal to twice the transmission time of a frame between two of said terminal equipments, pending the reception of a dedicated frame transmitted by a terminal equipment, and, secondly, dedicated frames are transmitted successively via the physical link management module relating to the operational network, and as long as the terminal equipment is connected, in the case where a dedicated frame is received during said previously defined time value, the operational Ethernet network is considered to work properly, and in the case where no dedicated frame is received during said previously defined time value, the Ethernet network previously operated there ational is considered to be inoperative, said set of potentially operational networks being then updated by deleting the Ethernet network that has become inoperative.
  • each dedicated frame is transmitted via the physical link management module relative to said operational network after a time value corresponding to the time during which it is acceptable to have a loss of service on said operational network.
  • the method is particularly advantageous because it does not require complex treatments at the low level that are resource consumers.
  • the present invention relates to a device implementing this method as well as a terminal equipment and a redundancy system of an Ethernet type network.
  • the Fig. 3 schematically represents an example of a redundancy system of an Ethernet network according to the present invention.
  • the system of redundancy SYST comprises an ETH1 initial network of etched Ethernet type that is to say that the communication between terminal equipments via this network, in this case between four equipments T1 to T4, is carried out via their management module. link and that each terminal equipment Ti is connected to a single switch SW1.
  • the SW1 switch has the function of connecting one of its input ports with one of its output ports and this non-scalable over time. Indeed, although the SW1 switch has a table that defines the relationships between its different ports, these relationships can not be modified by a protocol as is possible in the case of a router.
  • the switch table SW1 is defined, for example, according to the connection of the terminal equipment on each of its ports.
  • the SYST system also includes two other ethernet Ethernet networks ETH2 and ETH3.
  • the ETH2 network respectively ETH3 uses a switch SW2 respectively SW3.
  • the three networks ETH1, ETH2 and ETH3 are said to be independent of each other because they do not use the same switches. It may be noted, however, that each of them makes it possible to establish communications between the different terminal equipments Ti. They are said to be redundant from each other hence the name of the SYST system.
  • each terminal equipment Ti comprises a particular link management module described in relation to the Fig. 4 .
  • the Fig. 4 schematically represents the architecture of a link management module according to the present invention.
  • the MGLi link management module comprises a MAC media management module and a DISP device which implements the communication method described in connection with the Fig. 5 .
  • the management module MAC and each PHYj physical link management module are connected to the device DISP by a bus BU which provides two-way data transmission between the MAC and PHYj modules and the device.
  • the BU bus complying with the IEEE MII standard ( Media Independant Interface in English) can for example be used.
  • the MGLi link management module also includes a DLV monitoring unit which will be of further use and an ID interface for HP higher-level protocol layers to communicate with the DISP.
  • the Fig. 5 represents a diagram of the steps of a method of data communication between end devices of an SYST redundancy system of an Ethernet type network according to the present invention.
  • the SYST redundancy system comprises a plurality of terminal equipments Ti and a plurality of Ethernet networks independent of each other and accessible from each of the terminal equipments Ti.
  • Each terminal equipment Ti comprises as many PHI physical link management modules i, j as Ethernet networks of the SYST system as has been described in connection with the Fig. 4 .
  • the method is based on the determination of an Ethernet network, among the plurality of Ethernet networks of the SYST system, used for the communication of data between a terminal equipment Ti and at least one other terminal equipment of the SYST system.
  • This determination is scalable during the communication of the terminal equipment Ti with this or these other terminal equipment.
  • the method makes it possible to determine another of the Ethernet networks among the plurality of Ethernet networks.
  • the Ethernet network used for the communication between the terminal equipments of the SYST system is said to be operational, that is to say that it is used by each terminal equipment Ti to transmit data originating from the higher-level protocol layers towards at least one other terminal equipment via the physical link management module relating to this Ethernet network and receiving data transmitted by other terminal equipment via this terminal link physical management module Ti which is noted later P H I i , j V , the index i designating the terminal equipment considered, the index j identifying one of the physical link management modules that includes the terminal equipment considered and the exponent V designating that this module is relative to the Ethernet network considered operational by the terminal equipment considered.
  • an Ethernet network of the SYST system is subsequently said to be inoperative when a terminal equipment Ti has detected a failure on this network.
  • the character of a physical link management module is that of the Ethernet network with which it is in relation.
  • each terminal equipment Ti differentiate from each other according to their character that may be inoperative, operational or indeterminate (neither inoperative nor operational).
  • a set Ei specific to each terminal equipment Ti, is formed of information that identifies the Ethernet networks of the plurality of Ethernet networks of the SYST system that are not considered by this equipment. terminal Ti as inoperative. This prevents networks of the SYST system that have been considered by the terminal equipment Ti as being out of order to be considered as potentially operational.
  • the set Ei is formed of all the Ethernet networks of the plurality of Ethernet networks when no indication makes it possible to specify the character of each Ethernet network of the SYST system. This is the case, for example, when starting the link management module of a terminal device Ti when the character of the physical link management modules has not been previously stored. It may also be noted, as will be seen later, that this set Ei can be updated by deleting an Ethernet network that becomes inoperative and by adding a previously inoperative Ethernet network that would be put back into service once the failure on this repaired network.
  • the determination of the operational Ethernet network is made by all the terminal devices of the SYST system. For this purpose, it is based, according to the present invention, on the communication between these terminal equipments of Ethernet frames denoted TRE that are dedicated, that is to say that each of them includes information that allows a management module link physics to differentiate it from other Ethernet frames likely to pass through this module. This information is for example the MAC identifier of the TRE frame which is an identifier dedicated to this type of frame.
  • communication of dedicated frames TRE between terminal equipment it is meant the transmission of each of these frames by a terminal equipment and the reception of this frame by each of these other terminal equipment.
  • the method intended to be implemented by each terminal equipment T1 of the system SYST, comprises a step 100 of determining a first operational Ethernet network among the set Ei. This step is executed at the start of the MGLi link management module of a terminal equipment Ti, that is to say when no previously memorized indication makes it possible to specify among the plurality of Ethernet networks of the SYST system which one is operational.
  • step 100 the PHI link physical management modules i, j relating to the Ethernet networks of the set Ei specific to a terminal equipment Ti are scanned as long as a TRE frame is not received via the one of these modules.
  • the TRE frames are successively transmitted via the PHI link physical management modules i, j relating to the Ethernet networks of the set Ei.
  • Step 100 is essential because it allows a terminal equipment Ti newly connected to the SYST system to synchronize on the terminal equipment already connected to the system SYST and this through the scanning of each of its physical management modules PHI link i, j to determine which Ethernet network is considered operational by the other connected end devices.
  • step 100 makes it possible to propose an operational Ethernet network to any other terminal equipment that would connect to the SYST system, this avoiding to any newly connected terminal equipment to consider in isolation that an Ethernet network is operational while the other connected end devices consider this Ethernet network as inoperative.
  • a first PHI physical management module i, j is considered.
  • a first TRE frame is then sent via this physical management module PHI link i, j .
  • a random time value TEMP1 chosen from a range of RTEMP values whose lower limit is at least twice the transmission time of a frame between two terminal equipments of the SYST system, that is to say at minus the sum between the time for a terminal equipment connected to the Ethernet network relating to the physical management module PHI link i, j being scanned can receive the TRE frame issued by a terminal equipment Ti and time for the terminal equipment Ti may receive the TRE frame transmitted by another terminal equipment of the SYST system, a second TRE frame is transmitted and so on until a time value TEMP2 has elapsed since the transmission of said first frame TRE on said physical link management module PHI i, j .
  • Another PHI physical management module i, j +1 is then considered and TRE frames are then transmitted as explained above.
  • This embodiment of the method is particularly advantageous in case of simultaneous start of the link management module of several terminal equipments.
  • the randomness of the time value TEMP1 makes it possible to greatly reduce the probability of simultaneous start-up of these terminal equipments and consequently to increase by the same the probability that these terminal equipments can determine the same operational Ethernet network by the TRE frame exchange.
  • step 100 is followed by a step 200 of controlling operation of the operational Ethernet network.
  • each terminal equipment Ti scans its physical link management module P H I i , j V during a previously defined time value TEMP3 which is at least twice the transmission time of a frame between two terminal equipments of the SYST system, while awaiting the reception of a TRE frame transmitted by another terminal equipment.
  • step 200 TRE frames are successively transmitted via the physical link management module P H I i , j V relating to this operational network as long as the terminal equipment is connected to the redundancy system.
  • a first TRE frame is transmitted via the physical link management module P H I i , j V .
  • a second TRE frame is then transmitted and so on.
  • the previously operational Ethernet network is considered inoperative, that is to say that it is considered that a failure has occurred on this network .
  • the set Ei is then updated by deleting the information that identifies the Ethernet network that has become inoperative.
  • the information identifying the Ethernet network that has become inoperative is recorded.
  • the identifier for example the MAC address, of the terminal equipment which considered that the previously operational Ethernet network has become inoperative is recorded.
  • step 200 is followed by a step 300 of determining a new operational Ethernet network of the set Ei.
  • step 300 the physical link management modules PHI i, j of the set Ei specific to the terminal equipment Ti are scanned as long as a TRE frame is not received via one of these modules as explained in the description of step 100.
  • TRE frames are transmitted successively via the physical management modules PHI i, j of the set Ei as explained in the description of step 100.
  • Step 300 is then followed by step 200.
  • a first PHI physical management module i, j of the set Ei is considered.
  • a first TRE frame is then sent via this physical management module PHI link i, j .
  • a second TRE frame is then transmitted and so on until a time value TEMP6 has elapsed since the transmission of said first TRE frame on said physical management module PHI link i, j .
  • Another PHI physical management module i, j +1 is then considered and TRE frames are then transmitted as explained above.
  • the set Ei specific to each terminal equipment Ti is an ordered list of information identifying each Ethernet network such as their number for example.
  • This list is ordered in order to privilege the connection with particular Ethernet networks of the redundancy system and for purposes, for example, maintenance of these Ethernet networks. Indeed, by defining such an ordered list, it is possible to verify, from the method, whether the Ethernet network relating to a physical link management module is working properly. This list can obviously evolve over time depending, in particular, the frequency of use of different Ethernet networks. Thus, for example, Ethernet networks that are used very little are positioned in the first elements of the list. This will check that these Ethernet networks are working properly and thus ensure the proper functioning of all Ethernet networks in the redundancy system.
  • the method also includes a monitoring step 400.
  • This step is intended to provide a diagnostic concerning the evolution of the character of each Ethernet network of the redundancy system.
  • information identifying the operational Ethernet network and the information recorded during the step 200 that identify the inoperative networks are obtained. It is recalled that this information is kept up to date during step 200, that is to say as long as the terminal equipment Ti is connected to the redundancy system SYST or when an Ethernet network considered inoperative has been reset. functioning during a maintenance phase.
  • This information and / or statistics and / or history are possibly sent to the upper level protocol layers HP for example to be analyzed by an administrator of the redundancy system or to be stored.
  • the monitoring step 400 may be implemented, for example, following a request sent from the higher-level protocol layers HP such as a command from the administrator or be implemented periodically.
  • SNMP Simple Network Management Protocol
  • alarms can also be generated. These alarms are sent, for example, to the higher-level HP protocol layers to inform an administrator or to trigger a troubleshooting process.
  • the Fig. 6 schematically represents an embodiment of the device DISP implementing the method described in connection with the Fig. 5 .
  • the device DISP is intended to be implemented at the level of the link management module of each terminal equipment Ti of a redundancy system SYST as described above.
  • the DISP device includes MDRO means for determining an operational Ethernet network among a set of potentially operational networks obtained from the plurality of Ethernet networks of the SYST system, and MCRO means for controlling the operation of the operational Ethernet network.
  • the device DISP comprises MGTD means for generating a dedicated Ethernet frame TRE, METD means for sending a dedicated frame TRE via one of the physical management modules of the link of the terminal equipment Ti, means MRTD for receiving an Ethernet frame via one of the physical link management modules and MITR means for identifying that an Ethernet frame received via one of the link physical management modules is a dedicated TAR frame.
  • the device DISP also comprises means MCRE for choosing one of the physical management modules, means MTEMP1 for selecting a random time value from a range of values whose lower limit is at least twice the transmission time of a frame between two of said terminal equipments, MTEMP3 means for obtaining a previously defined time value which is at least twice the transmission time of a frame between two of said terminal equipments, means MTEMP4 for obtaining a value of time corresponding to the time during which it is acceptable to have a loss of service on said operational network, MSCRT means for scanning a physical link management module pending receipt of a dedicated frame transmitted by a terminal equipment . All of these means are used by the MDRO means to implement step 100 and 300 of the communication method described above and by MCRO means to implement step 200.
  • the MDRO means also use MRO means to designate as operational the Ethernet network relating to a physical link management module via which a dedicated frame TRE has been received and means MRIO to designate as inoperative the operational Ethernet network when no frame Dedicated has been received during a previously defined time value which is at least twice the transmission time of a frame between two of said terminal equipments.
  • the device DISP also comprises means MODI for obtaining information identifying the operational Ethernet network and information identifying the inoperative network (s) and means for computing statistics and / or generating alarms and / or obtaining a history of the evolution of the operation of each of the Ethernet networks.
  • the device comprises a DLV monitoring unit whose purpose is to implement the process monitoring step 400 and an ID interface enabling the upper level protocol layers HP to communicate with the device DISP in particular to obtain identifying information.
  • the device DISP finally comprises a central processing unit CPU intended to receive instructions necessary for the implementation of the communication method and data stored on a data carrier DA which can then for example be materialized by a hard disk, said instructions defining the steps of determining an operational Ethernet network among the plurality of Ethernet networks and controlling the operation of the operational Ethernet network, the execution of which by the central processing unit CPU will allow the communication of data between at least two terminal equipments from of the plurality of Ethernet networks of the redundancy system, the DA data here including in particular information identifying the operational Ethernet network and information identifying the inoperative network or networks.
  • These instructions can be easily modified if necessary, and can form software that can be downloaded to the data carrier if it is rewritable, as is the case for example for a hard disk, a CD-ROM RW, a DVD-RAM or a magneto-optical disc. It can also be programmed on a microprocessor.
  • a data medium including these instructions and DA data may alternatively be removable and consist for example of a CD-ROM or DVD-ROM type read-only disk provided to the system user by a program supply service provider. .

Claims (17)

  1. Datenkommunikationsverfahren zwischen mindestens zwei Endgeräten über mehrere Netzwerke des Typs des Ethernet-Netzwerks, die voneinander unabhängig sind und jeweils die Kommunikation von Daten zwischen den mindestens zwei Endgeräten ermöglichen, wobei jedes Endgerät mehrere physikalische Verbindungsverwaltungsmodule (PHYj) aufweist, wobei jedes physikalische Verbindungsverwaltungsmodul (PHYj) einem der Ethernet-Netzwerke zugeordnet wird, wobei jedes Endgerät ein Medienverwaltungsmodul (MAC) aufweist, das unter anderem das Ethernet-Protokoll implementiert, wobei das Verfahren von einem Gerät (DISP) ausgeführt wird, das mit dem Medienverwaltungsmodul (MAC) eines Endgeräts und mit jedem physikalischen Verwaltungsmodul (PHYj) des Endgeräts verbunden ist, und dadurch gekennzeichnet ist, dass es aufweist:
    - einen Schritt (100) des Bestimmens eines sogenannten betriebsbereiten Ethernet-Netzwerks aus den mehreren Ethernet-Netzwerken, während dem mindestens eines der physikalischen Verbindungsverwaltungsmodule während eines zuvor gewählten Wertes einer Zeitdauer (TEMP) bis zum Empfangen eines dedizierten Frames (TRE), der von einem Endgerät gesendet wird, gescannt wird,
    - in dem Fall, in dem kein dedizierter Frame (TRE) während des gewählten Wertes der Zeitdauer (TEMP) empfangen wird, wird ein anderes physikalisches Verbindungsverwaltungsmodul gescannt, und
    - in dem Fall, in dem ein dedizierter Frame (TRE) während des gewählten Wertes der Zeitdauer (TEMP) empfangen wird, wird das Ethernet-Netzwerk in Bezug auf das physikalische Verbindungsverwaltungsmodul, das gerade gescannt wird, als betriebsbereit angesehen, und
    - einen Schritt (200) der Funktionskontrolle des betriebsbereiten Ethernet-Netzwerks.
  2. Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass bei dem Schritt (200) der Funktionskontrolle des betriebsbereiten Ethernet-Netzwerks das physikalische Verbindungsverwaltungsmodul, das sich auf das betriebsbereite Ethernet-Netzwerk bezieht, während eines zuvor gewählten Wertes einer Zeitdauer (TEMP) bis zum Empfangen eines dedizierten Frames, der von einem Endgerät gesendet wird, gescannt wird,
    - in dem Fall, in dem ein dedizierter Frame (TRE) während des gewählten Wertes der Zeitdauer (TEMP) empfangen wird, ein dedizierter Frame (TRE) über das physikalische Verbindungsverwaltungsmodul in Bezug auf das betriebsbereite gesendet wird, und
    - in dem Fall, in dem kein dedizierter Frame (TRE) während des gewählten Wertes der Zeitdauer (TEMP) empfangen wird, das Ethernet-Netzwerk, das bis dahin betriebsbereit ist, als nicht betriebsbereit angesehen wird, und auf den Schritt der Funktionskontrolle des betriebsbereiten Ethernet-Netzwerks dann der Schritt (100) des Bestimmens eines betriebsbereiten Ethernet-Netzwerks folgt.
  3. Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass bei dem Schritt (100) des Bestimmens eines betriebsbereiten Ethernet-Netzwerks mindestens eines der physikalischen Verbindungsverwaltungsmodule während eines zuvor gewählten Wertes einer Zeitdauer (TEMP) bis zum Empfangen von einer Anzahl an Frames, die gleich der Anzahl an Endgeräten ist, die geeignet sind, einen dedizierten Frame (TRE) zu senden, gescannt wird,
    - in dem Fall, in dem ein dedizierter Frame (TRE), der geeignet ist, von einem Endgerät gesendet zu werden, nicht als während des gewählten Wertes der Zeitdauer (TEMP) empfangen worden identifiziert worden ist, ein anderes physikalisches Verbindungsverwaltungsmodul gescannt wird, und
    - in dem Fall, in dem ein dedizierter Frame (TRE), der von jedem Endgerät gesendet wird, als während des gewählten Wertes der Zeitdauer (TEMP) empfangen worden identifiziert worden ist, das Ethernet-Netzwerk in Bezug auf das physikalische Verbindungsverwaltungsmodul, das gerade gescannt wird, als betriebsbereit angesehen wird.
  4. Verfahren nach Anspruch 1 oder 3, dadurch gekennzeichnet, dass bei dem Schritt (200) der Funktionskontrolle des betriebsbereiten Ethernet-Netzwerks das physikalische Verbindungsverwaltungsmodul, das sich auf das betriebsbereite Ethernet-Netzwerk bezieht, während eines zuvor gewählten Wertes einer Zeitdauer (TEMP) bis zum Empfangen von so vielen dedizierten Frames (TRE) wie Endgeräte, die geeignet sind, dedizierte Frames (TRE) zu senden, gescannt wird,
    - in dem Fall, in dem ein dedizierter Frame (TRE), der von jedem Endgerät gesendet wird, als während des gewählten Wertes der Zeitdauer (TEMP) empfangen worden identifiziert worden ist, ein dedizierter Frame (TRE) über das physikalische Verbindungsverwaltungsmodul in Bezug auf das betriebsbereite Netz gesendet wird, und
    - in dem Fall, in dem ein dedizierter Frame (TRE), der wahrscheinlich von einem Endgerät gesendet worden ist, nicht als während des gewählten Wertes der Zeitdauer (TEMP) empfangen worden identifiziert worden ist, das Ethernet-Netzwerk, das bis dahin betriebsbereit ist, als nicht betriebsbereit angesehen wird, und auf den Schritt der Funktionskontrolle des betriebsbereiten Ethernet-Netzwerks dann der Schritt (100) des Bestimmens eines betriebsbereiten Ethernet-Netzwerks folgt.
  5. Verfahren nach Anspruch 2 oder 4, dadurch gekennzeichnet, dass jedes physikalische Verbindungsverwaltungsmodul, das zu scannen ist, aus einer Gruppe (E) ausgewählt wird, die jedem Endgerät eigen ist und die durch Zusammenfassen von Informationen definiert wird, die jeweils ein physikalisches Verbindungsverwaltungsmodul in Bezug auf ein Ethernet-Netzwerk identifizieren, das nicht betriebsbereit ist.
  6. Verfahren nach Anspruch 5, dadurch gekennzeichnet, dass die Gruppe eine Liste ist, die nach der Benutzungshäufigkeit der Ethernet-Netzwerke des Systems geordnet wird.
  7. Verfahren nach Anspruch 5 oder 6, dadurch gekennzeichnet, dass bei der Funktionskontrolle des betriebsbereiten Ethernet-Netzwerks in dem Fall, bei dem ein dedizierter Frame (TRE), der geeignet ist, empfangen zu werden, während des gewählten Wertes der Zeitdauer (TEMP) nicht empfangen wird, die Information, die das physikalische Verbindungsverwaltungsmodul in Bezug auf das nicht betriebsbereite Netzwerk identifiziert, von der Gruppe gelöscht wird.
  8. Verfahren nach einem der Ansprüche 1 bis 7, dadurch gekennzeichnet, dass jeder Wert der Zeitdauer (TEMP) in einem Wertebereich zufällig definiert wird, dessen untere Grenzen mindestens gleich dem Zweifachen der maximalen Sendedauer des dedizierten Frames zwischen zwei Endgeräten des Systems ist.
  9. Verfahren nach Anspruch 2 oder nach einem der Ansprüche 4 bis 8, dadurch gekennzeichnet, dass es einen Schritt (300) des Überwachens der mehreren unabhängigen Ethernet-Netzwerke durch eine Einheit aufweist, während dem eine Information, die das betriebsbereite Ethernet-Netzwerk bezeichnet, und Informationen, die das oder die nicht betriebsbereiten Netzwerke bezeichnen, erhalten werden, um Statistiken zu berechnen und/oder Alarme zu erzeugen und/oder eine Historie der Entwicklung des Betriebs jedes der Ethernet-Netzwerke zu erhalten.
  10. Vorrichtung, die dazu bestimmt ist, in einem Endgerät eingesetzt zu werden, das an mehrere Ethernet-Netzwerke angeschlossen ist, die voneinander unabhängig sind und jeweils die Kommunikation von Daten zwischen dem Endgerät und mindestens einem anderen Endgerät ermöglichen, wobei jedes Endgerät mehrere physikalische Verbindungsverwaltungsmodule aufweist, wobei jedes physikalische Verbindungsverwaltungsmodul einem der Ethernet-Netzwerke zugeordnet ist, wobei jedes Endgerät ein Medienverwaltungsmodul (MAC) aufweist, das unter anderem das Ethernet-Protokoll implementiert, wobei die Vorrichtung mit einem Medienverwaltungsmodul (MAC) eines Endgeräts und mit jedem physikalischen Verwaltungsmodul des Endgeräts verbunden ist, wobei die Vorrichtung Mittel (MDRO), um ein betriebsbereites Ethernet-Netzwerk zu bestimmen, und Mittel (MCRO) aufweist, um das Funktionieren des betriebsbereiten Ethernet-Netzwerks zu kontrollieren, wobei die Vorrichtung dadurch gekennzeichnet ist, dass die Mittel (MDRO, MCRO) verwenden:
    - Mittel (MITR), um zu identifizieren, dass ein Frame, der über eines der physikalischen Verbindungsverwaltungsmodule empfangen wird, ein dedizierter Frame ist,
    - Mittel (MCRE), um eines der physikalischen Verbindungsverwaltungsmodule auszuwählen,
    - Mittel (MTEMP), um einen Wert einer Zeitdauer zu definieren,
    - Mittel (MSCRT), um ein physikalisches Verbindungsverwaltungsmodul zu scannen, das während des Wertes der Zeitdauer bis zum Empfangen eines dedizierten Frames, der von einem Endgerät gesendet wird, ausgewählt ist,
    - Mittel (MRO), um das Ethernet-Netzwerk in Bezug auf ein physikalisches Verbindungsverwaltungsmodul zu bezeichnen, über das ein dedizierter Frame während des gewählten Wertes der Zeitdauer empfangen worden ist, und
    - Mittel (MRIO), um das betriebsbereite Ethernet-Netzwerk als nicht betriebsbereit zu bezeichnen, wenn kein dedizierter Frame während des gewählten Wertes der Zeitdauer empfangen worden ist.
  11. Vorrichtung nach Anspruch 10, dadurch gekennzeichnet, dass die Mittel (MCRE), um eines der physikalischen Verbindungsverwaltungsmodule auszuwählen, ein physikalisches Verbindungsverwaltungsmodul aus einer Gruppe (E) auswählen, das jedem Endgerät eigen ist und das durch das Zusammenfassen von Informationen definiert ist, die jeweils ein physikalisches Verbindungsverwaltungsmodul in Bezug auf ein Ethernet-Netzwerk identifizieren, das nicht betriebsbereit ist.
  12. Vorrichtung nach Anspruch 11, dadurch gekennzeichnet, dass die Gruppe eine Liste ist, die nach der Benutzungshäufigkeit der Ethernet-Netzwerke des Systems geordnet ist.
  13. Vorrichtung nach Anspruch 11 oder 12, dadurch gekennzeichnet, dass die Mittel (MCRO), um das Funktionieren des betriebsbereiten Ethernet-Netzwerks zu kontrollieren, Mittel aufweisen, um von der Gruppe die Information zu löschen, die das physikalische Verbindungsverwaltungsmodul in Bezug auf ein nicht betriebsbereites Ethernet-Netzwerk identifiziert.
  14. Vorrichtung nach einem der Ansprüche 10 bis 13, dadurch gekennzeichnet, dass jeder Wert der Zeitdauer in einem Wertebereich zufällig definiert ist, dessen untere Grenze mindestens gleich dem Zweifachen der maximalen Sendedauer des Frames des Typs zwischen zwei Endgeräten des Systems ist.
  15. Vorrichtung nach einem der Ansprüche 10 bis 14, dadurch gekennzeichnet, dass sie Mittel (MODI) zum Erhalten von einer Information, die das nicht betriebsbereite Ethernet-Netzwerk bezeichnet, und von Informationen, die das oder die nicht betriebsbereiten Netzwerke bezeichnen, und Mittel aufweist, um Statistiken zu berechnen und/oder Alarme zu erzeugen und/oder eine Historie der Entwicklung des Funktionierens jedes der Ethernet-Netzwerke zu erhalten.
  16. Endgerät eines Netzwerks des Typs des Ethernet-Netzwerks, dadurch gekennzeichnet, dass es eine Vorrichtung gemäß einem der Ansprüche 10 bis 15 aufweist.
  17. Redundanzsystem eines Netzwerks des Typs des Ethernet-Netzwerks, das zur Datenkommunikation zwischen mindestens zwei Endgeräten bestimmt ist, dadurch gekennzeichnet, dass es aufweist:
    - mindestens ein anderes Netzwerk des Typs des Ethernet-Netzwerks, das unabhängig ist und das die Kommunikation von Daten zwischen den mindestens zwei Endgeräten ermöglicht,
    - und dadurch, dass jedes Endgerät gemäß dem Anspruch 16 ist.
EP08858285.3A 2007-12-04 2008-12-02 Datenkommunikationsverfahren zwischen endgeräten über mehrere ethernet-basierende netzwerke eines redundanz-systems Active EP2238717B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FR0708432A FR2924554B1 (fr) 2007-12-04 2007-12-04 Procede de communication de donnees entre equipements terminaux a partir d'une pluralite de reseaux de type ethernet d'un systeme de redondance
PCT/EP2008/066576 WO2009071522A1 (fr) 2007-12-04 2008-12-02 Procédé de communication de données entre équipements terminaux à partir d'une pluralité de réseaux de type ethernet d'un système de redondance

Publications (2)

Publication Number Publication Date
EP2238717A1 EP2238717A1 (de) 2010-10-13
EP2238717B1 true EP2238717B1 (de) 2018-08-08

Family

ID=39745081

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08858285.3A Active EP2238717B1 (de) 2007-12-04 2008-12-02 Datenkommunikationsverfahren zwischen endgeräten über mehrere ethernet-basierende netzwerke eines redundanz-systems

Country Status (5)

Country Link
EP (1) EP2238717B1 (de)
CN (1) CN101939956B (de)
BR (1) BRPI0820106A2 (de)
FR (1) FR2924554B1 (de)
WO (1) WO2009071522A1 (de)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR3057342B1 (fr) 2016-10-10 2019-05-10 Bull Sas Protocole de communication entre plusieurs modules de refroidissement liquide de serveurs informatiques
FR3071118B1 (fr) * 2017-09-12 2020-09-04 Thales Sa Dispositif electronique et procede de reception de donnees via un reseau de communication rebonde, systeme de communication et programme d'ordinateur associes
CN110166316B (zh) * 2019-05-09 2022-05-17 中国航空工业集团公司西安航空计算技术研究所 一种afdx网络选择模块的测试方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020152320A1 (en) * 2001-02-14 2002-10-17 Lau Pui Lun System and method for rapidly switching between redundant networks
EP1394985A1 (de) * 2002-08-28 2004-03-03 Siemens Aktiengesellschaft Testverfahren für Nachrichtenpfade in Kommunikationsnetzen sowie Netzelement
US7688712B2 (en) * 2005-10-04 2010-03-30 Invensys Systems, Inc. Selecting one of multiple redundant network access points on a node within an industrial process control network
CN100558111C (zh) * 2007-02-05 2009-11-04 华为技术有限公司 城域以太网提供多业务组网下的可靠性处理方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
FR2924554A1 (fr) 2009-06-05
CN101939956A (zh) 2011-01-05
BRPI0820106A2 (pt) 2015-05-05
CN101939956B (zh) 2013-09-25
WO2009071522A1 (fr) 2009-06-11
FR2924554B1 (fr) 2010-02-19
EP2238717A1 (de) 2010-10-13

Similar Documents

Publication Publication Date Title
Oppenheimer Top-down network design
US7987228B2 (en) Broadband communications
US20030033406A1 (en) Apparatus for and a method of network load testing
EP1672874B1 (de) Verfahren zur sicheren Übertragung und System, Firewall und Router zur Durchführung des Verfahrens
EP3771182B1 (de) Verfahren zum entdecken und identifizieren von über ein modbus-protokoll kommunizierenden geräten, und kommunikations-controller zur umsetzung dieses verfahrens
US20120269068A1 (en) Testing system
EP2238717B1 (de) Datenkommunikationsverfahren zwischen endgeräten über mehrere ethernet-basierende netzwerke eines redundanz-systems
WO2007107674A2 (fr) Procede de communication de donnees entre des systemes de traitement heterogenes connectes en reseau local et systeme de communication mettant en oeuvre ce procede
EP2751959B1 (de) Verfahren zum austausch von daten zwischen knoten in einem server-cluster und servercluster zur durchführung des verfahrens
CN103516631A (zh) 通信装置
EP0676881A1 (de) Prüfung der Echtheit von zwischen zwei Stationen eines Telecommunikationsnetz übertragenen Daten
EP1466442B1 (de) Verfahren und system zur statusüberwachung eines kommunikationsnetzwerks
EP3122005B1 (de) Routing-system, das eine datenfilterung zur integration und überprüfung der betriebsausrüstungen ermöglicht
EP2878086B1 (de) Unidirektionale multicast-systeme
Cisco Catalyst 3900 Token Ring Switch Release 4.1(3) Release Note
Goldman Network Communication
EP3817294B1 (de) Verfahren und module zur konnektivitätsteuerung von verbundenen objekten
EP2366236A2 (de) Konfigurationsverfahren für virtuelle schaltungen
EP2119140B1 (de) Verfahren zur weiterleitung eines datenpakets durch einen router in einem durch ein transportnetzwerk gestützten paketnetzwerk
Lammle et al. CCNP™
CN116633750A (zh) 一种oam lb自动回复的实现方法及系统
US8572235B1 (en) Method and system for monitoring a complex IT infrastructure at the service level
Goldman 22.1 General Principles of Network Analysis and Design
EP2840762A1 (de) Ausrüstung vom Typ produktive Multiserver-Lamelle für modulare Grundplatte, mit Mehrfachzugang über das Grundplatten-Steuernetz
EP1667361A1 (de) Schnittstellenvorrichtung zwischen diagnostischen Mitteln und Analyseeinrichtungen eines Kommunikationsnetzwerks

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

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

AX Request for extension of the european patent

Extension state: AL BA MK RS

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SAGEM DEFENSE SECURITE

17Q First examination report despatched

Effective date: 20160129

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SAFRAN ELECTRONICS & DEFENSE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602008056428

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012560000

Ipc: H04L0001220000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 1/22 20060101AFI20180305BHEP

Ipc: H04L 12/931 20130101ALI20180305BHEP

Ipc: H04L 12/939 20130101ALI20180305BHEP

INTG Intention to grant announced

Effective date: 20180323

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1028256

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180815

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: FRENCH

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602008056428

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180808

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1028256

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180808

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

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

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

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

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

Ref country code: NO

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

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

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

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

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

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

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

Ref country code: HR

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602008056428

Country of ref document: DE

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

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

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

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

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

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

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

Ref country code: LU

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

Effective date: 20181202

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181231

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

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

Ref country code: BE

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

Effective date: 20181231

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

Ref country code: CH

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

Effective date: 20181231

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

Ref country code: MT

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

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

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

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

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; INVALID AB INITIO

Effective date: 20081202

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

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

Ref country code: GB

Payment date: 20231121

Year of fee payment: 16

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

Ref country code: FR

Payment date: 20231122

Year of fee payment: 16

Ref country code: DE

Payment date: 20231121

Year of fee payment: 16