EP2594051B1 - Systèmes et procédés de reprise après la défaillance d'un équilibreur de charge de serveur - Google Patents

Systèmes et procédés de reprise après la défaillance d'un équilibreur de charge de serveur Download PDF

Info

Publication number
EP2594051B1
EP2594051B1 EP10740368.5A EP10740368A EP2594051B1 EP 2594051 B1 EP2594051 B1 EP 2594051B1 EP 10740368 A EP10740368 A EP 10740368A EP 2594051 B1 EP2594051 B1 EP 2594051B1
Authority
EP
European Patent Office
Prior art keywords
slb
target processing
session
processing unit
stand
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
EP10740368.5A
Other languages
German (de)
English (en)
Other versions
EP2594051A1 (fr
Inventor
Tarik Hammam
Anders Franzen
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP2594051A1 publication Critical patent/EP2594051A1/fr
Application granted granted Critical
Publication of EP2594051B1 publication Critical patent/EP2594051B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2002—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
    • G06F11/2005—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers

Definitions

  • the invention relates the field of server load balancing.
  • a server load balancer is device (hardware and/or software) for balancing session traffic across a set of applications (e.g., server applications), each of which runs on a processing unit (e.g., a server computer, a blade server, etc.).
  • applications e.g., server applications
  • a processing unit e.g., a server computer, a blade server, etc.
  • the stand-by SLB can either be a "hot” stand-by or a "cold” stand-by.
  • connection data e.g., a connection table
  • this replication is accomplished by updating connection data accessible to the hot stand-by SLB each time the connection data maintained by the primary SLB is updated.
  • An advantage of using a hot stand-by SLB is that, in case a failure of the primary SLB (or "active" SLB) occurs, a switchover to the stand-by SLB occurs and this stand-by SLB would have connection data that is identical to the connection data that was maintained by the primary SLB, thereby enabling the stand-by SLB to takeover as primary SLB and continue balance traffic for the already established sessions as well as new session.
  • a problem with using the hot stand-by method is that if the hot stand-by fails, then the connection data will be lost. Moreover, the hot stand-by method requires that the hot stand-by SLB work in tandem with the primary SLB so that the primary SLB's connection data can be replicated. Another problem with the hot stand-by method occurs when some event (e.g., power failure, operating system crash, hardware fault) causes the primary SLB and a target processing unit (e.g., a processing unit on which a server application runs) to fail at more less the same time. When such a situation arises, the replicated connection data that is used by the stand-by SLB may include invalid information (e.g., information mapping a session to the failed target processing unit).
  • some event e.g., power failure, operating system crash, hardware fault
  • Prior art document US 2007/0174660 describes a hierarchical model of load balancing using a global load balancer to enable failover.
  • a problem with using a cold stand-by SLB is that there is no replication of the primary SLB's connection data, and this means that the cold stand-by SLB can not route traffic corresponding to a session that was established before the primary SLB failed.
  • the invention provides an SLB recovery method that replicates the primary SLB's connection data after the primary SLB experiences a failure, as opposed to before it experiences a failure as is currently done in the known hot stand-by recovery method.
  • this is made possible by (1) employing a replication agent on each target processing unit (e.g., each processing unit on which a server application runs) and (2) transmitting, from the primary SLB, connection data information (i.e., information comprising a session identifier) to the replication agent running on the target processing unit to which the session is mapped, which replication agent will store the connection data information until it is required to transmit the data to a cold stand-by SLB.
  • connection data information i.e., information comprising a session identifier
  • the replication agent can provide the connection data information to the cold stand-by SLB in the event the primary SLB experiences a failure.
  • This provides the advantage of enabling a system design solution that can capitalize on the flexibility of cold stand-by methods yet is still able to protect established sessions because the cold stand-by SLB can receive from one or more replication agents connection data information that maps an established session to a particular target processing unit. This is particularly useful in server farms and clustered system designs.
  • the above described embodiment provides protection against multiple SLB failures because, in the event of a primary SLB failure and a cold stand-by failure, a second cold stand-by SLB can easily replicate the necessary connection data by merely receiving the necessary information from the replication agents.
  • connection data e.g., a connection table
  • invalid connection data information e.g., a records that maps a session to the failed target processing unit.
  • the replicated connection data used by the stand-by SLB will not contain any such invalid connection data information.
  • the stand-by SLB receives its connection data information from the target processing unit themselves after the primary SLB fails.
  • the stand-by SLB will not receive any connection data information from the failed target.
  • the stand-by SLB will not have connection data that includes connection data information that maps a session to the failed target.
  • One aspect of the invention provides a method, performed by a stand-by SLB.
  • this method includes: replicating, by the stand-by SLB, at least a portion of connection data maintained by the primary SLB such that the replicated connection data is accessible to the stand-by SLB, characterized in that the replicating step occurs in response to a detection of the failure of the primary SLB.
  • the stand-by SLB may: (a) receive traffic corresponding to a session; (b) access the replicated connection data to determine a target processing unit to which the session is mapped; and (c) forward the traffic to the determined target processing unit (i.e., the stand-by SLB become the primary SLB).
  • the stand-by SLB (which is now a primary SLB) may further: receive traffic corresponding to a second session and access the replicated connection data to determine whether the accessed data comprises information mapping the second session to any of a plurality of target processing units.
  • the stand-by SLB is configured to: (a) select a particular target processing unit; (b) update the replicated connection data so that the replicated connection data will comprise information mapping the second session with the selected target processing unit; and (c) transmit to a replication agent running on the selected target processing unit a connection data update message comprising a session identifier identifying the second session.
  • the step of replicating the connection data comprises: receiving, at the stand-by SLB, a replication message transmitted from a target processing unit, wherein the replication message contains a session identifier identifying a session; and in response to receiving the replication message, storing information that maps the session with the target processing unit.
  • the replication message may contain a plurality of session identifiers, each identifying a different session, and, in response to receiving the replication message, the stand-by SLB stores information mapping each of the plurality of session identifiers with the target processing unit.
  • the method further includes: transmitting, in response to the failure of the primary SLB, a connection data synchronization message to each of a first and a second target processing unit, wherein each of the first and second target processing units is configured to transmit one or more replication messages to the stand-by SLB in response to receiving the connection data synchronization message.
  • the connection data maintained by the primary SLB comprises first information mapping a first session to the first target processing unit and second information mapping a second session to the second target processing unit, wherein the first information consists of a first record comprising a first field storing a session identifier identifying the first session and a second field storing a target processing unit identifier identifying the first target processing unit, and the second information consists of a second record comprising a second field storing a session identifier identifying the second session and a second field storing a target processing unit identifier identifying the second target processing unit.
  • the step of receiving, at the stand-by SLB, traffic corresponding to a session consists of receiving, at the stand-by SLB, a network packet comprising information identifying the session, wherein the network packet is an Internet Protocol (IP) packet that contains an IP header and a payload, wherein the payload contains a transport layer segment having a transport layer header and payload, and data from the IP header and transport layer header identifies the network packet as corresponding to the session.
  • IP Internet Protocol
  • the primary SLB may execute on one of the target processing units.
  • the replicated connection data may not contain information that maps any session to the target processing unit on which the primary SLB was running when it failed. This, as described above, is advantageous because it is undesirable for the stand-by SLB to attempt to forward traffic to a failed target, which could happen if the connection table used by the stand-by SLB contains a record that maps a session to a failed target processing unit.
  • the invention provides an improved stand-by server load balancer (SLB).
  • the improved stand-by SLB is configured to recover from the failure of a primary SLB, which is operable to use stored connection data to balance traffic across a plurality of target processing units using.
  • the stored connection data comprises information mapping sessions with target processing units.
  • the stand-by SLB is configured such that, in response to a detection of the failure of the primary SLB, the stand-by SLB replicates the connection data (or most of the connection data) to create replicated connection data.
  • the replicated connection data is accessible to the stand-by SLB so that the stand-by SLB can use the replicated connection data to balance traffic across the plurality of target processing units.
  • the stand-by SLB is configured to replicate the connection data by receiving one or more replication messages from one or more of the target processing units, each of the one or more replication message comprising a session identifier and a target processing unit identifier. In some embodiments, the stand-by SLB is further configured such that, in response to the failure of the primary SLB, the stand-by SLB transmits a connection data synchronization message to at least one of the plurality of target processing units.
  • connection data comprises a record comprising a first field storing a session identifier identifying a session and a second field storing a target processing unit identifier identifying a target processing unit
  • replicated connection data comprises a record comprising a first field storing the session identifier identifying the session and a second field storing the target processing unit identifier identifying the target processing unit
  • the stand-by SLB may be further operable to: receive a network packet corresponding to a session; use the replicated connection data to determine the target processing unit to which the session is mapped; and forward the network packet to the determined target processing unit.
  • the network packet may be an Internet Protocol (IP) packet that contains an IP header and a payload, wherein the payload contains a transport layer segment having a transport layer header and payload, and data from the IP header and transport layer header identifies the network packet as corresponding to the session.
  • IP Internet Protocol
  • the invention provides a computer program product comprising a computer usable medium having a computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method comprising: replicating connection data used by a primary server load balancer (SLB) immediately in response to a detection that the primary SLB has failed; and using the replicated connection data to balance traffic across a plurality of target processing units.
  • SLB server load balancer
  • the invention provides, a target processing unit, wherein the target processing includes a replication agent.
  • the replication agent is operable to: receive from a primary server load balancer (SLB) a connection data update message comprising a session identifier identifying a session; and store the session identifier in response to receiving the connection data update message, characterized in that: the replication agent is configured to transmit the session identifier to a stand-by SLB in response to receiving a synchronization message.
  • SLB primary server load balancer
  • the replication agent in some embodiments, is further operable to: receive from the primary SLB a second connection data update message comprising a second session identifier identifying a second session; and store the second session identifier in response to receiving the second connection data update message, characterized in that: the replication agent is configured such that, in response to receiving the synchronization message, the replication agent transmits to the stand-by SLB a replication message containing the first and second session identifiers.
  • the replication message may further contain an identifier identifying the target processing unit.
  • FIG. 1 illustrates a system 100 according to an embodiment of the invention.
  • System 100 includes a primary SLB 114 that is operable to balance session traffic across, among other things, a set of server applications 104, each of which runs on a processing unit 102. Also running on each processing unit 102a to 102n, is a replication agent 106.
  • FIG. 2 is a flow chart illustrating a process 200, according to some embodiments, that is performed by primary SLB 114.
  • Process 200 may begin in step 202, where primary SLB 114 receives session traffic (e.g., a packet), via network 120, transmitted from some device (not shown) connected to network 120, which may be an Internet Protocol (IP) network, such as the Internet, other network.
  • session traffic e.g., a packet
  • IP Internet Protocol
  • the received traffic is an IP packet, which, as is well known in the art, includes a header and payload.
  • SLB 114 received an IP packet.
  • SLB 114 extracts data from the received packet to generate a session identifier (e.g., a data structure, such as a string of bits or other structure, containing data from certain fields of the packet that together identify a session).
  • a session identifier e.g., a data structure, such as a string of bits or other structure, containing data from certain fields of the packet that together identify a session.
  • SLB 114 may form a data structure containing: (a) the following items from the IP header of the packet: source address, destination address, version (e.g. IPv4 or IPv6), and protocol (e.g., TCP or UDP) and (b) the following items from the TCP/UDP header: source port and destination port.
  • SLB 114 determines whether the packet corresponds to a new session. In the case where the packet is a TCP/IP packet, in some embodiments, SLB 114 determines whether the packet corresponds to a new session by determining if the packet contains a TCP packet that indicates that the TCP packet is a TCP connection request (i.e., the SYN bit of the TCP packet is set).
  • connection table 117 stores connection data that includes information mapping sessions to target processing units 102.
  • the connection data may include a plurality of records, where each record comprises a first field for storing a session identifier identifying a session and a second field for storing a processing unit identifier (e.g., an IP address) associated with a target processing unit 102.
  • the records may include additional fields.
  • step 212 If the traffic corresponds to a new session, then the process proceeds to step 212, otherwise it proceeds to step 222.
  • SLB 114 selects a target processing unit.
  • a table 121 of targeting processing unit identifiers may be stored in storage unit 115, and SLB 114 selects a target processing unit in step 212 by, for example, randomly selecting from the table 121 an identifier that identifies a target processing unit.
  • step 214 SLB 114 forwards the packet received in step 202 to the selected target processing unit 102.
  • the packet is then received and processed by protocol stack 108 and, if the packet contains application data, then the application data contained in the packet is provided to server application 104.
  • SLB 114 updates connection table 117. For example, in step 216, SLB 114 may add a record to table 117, which record contains in one field the session identifier generated in step 204 and in another field a target processing unit identifier that identifies the target processing unit selected in step 212.
  • SLB 114 sends to the selected target processing unit a connection data update message that includes the generated session identifier.
  • This message is received by a protocol stack 108 running on the target processing unit 102 and the message is then provided to the replication agent 106 running on the target processing unit 102.
  • Replication agent 106 in response to receiving the message, stores in storage unit 109 the session identifier included in the connection update message (step 220). Accordingly, a portion of connection table 117 is duplicated in storage unit 109.
  • This provides the distinct advantage of enabling replication agent 106 to inform stand-by SLB 116 of the active sessions that were handled by primary SLB 114, as well as the target processing units associated with those active sessions, in the event primary SLB 114 experiences a failure. This information regarding the active sessions enables the cold stand-by SLB 114 to take over the handling of these active sessions.
  • replication agent 106 is shown as being separate and apart from protocol stack 108 (i.e., replication agent 106 is a user application), this was done solely for the sake of illustration. In some other embodiments, replication agent 106 may be part of protocol stack 108 or some other part of the operating system. In the case where, replication agent 108 is a part of protocol stack 108, step 218 may be unnecessary because (a) the replication agent 106 may obtain from the protocol stack 108 a copy of the packet (or a copy of some portion of the packet) that was forwarded in step 214 and (b) replication agent 106 can be configured to use this information to generate the session identifier in the same manner that SLB 114 generates the session identifier as described above. After replication agent 106 generates the session identifier, agent 106 can store it in storage unit 109.
  • SLB 114 determines the target processing unit that is associated with the generated session identifier. SLB 114, in some embodiments, makes this determination by selecting the record in connection table 117 that includes a session identifier that matches the session identifier generated in step 204. This selected record will contain a target processing unit identifier that identifies the target processing unit associated with the generated session identifier.
  • step 224 SLB 114 forwards the packet received in step 202 to the determined target processing unit 102.
  • step 226 SLB 114 determines whether the packet indicates the end of the session. For example, in the case where the packet is a TCP/IP packet, SLB 114 determines that the packet indicates the end of the session when the FIN bit of the TCP packet is set. If the packet does not indicate the end of the session, the process may proceed back to step 202, where SLB 114 receives a new packet. If the packet indicates the end of the session, then SLB 114 updates its connection table by removing the record in the table that contains a session identifier that matches the session identifier generated in step 204 (step 228).
  • step 230 SLB 114 sends to the replication agent on the determined target processing unit a connection data update message that includes the generated session identifier (the message may also include an end-of-session indication).
  • the replication agent 106 removes from storage unit 109 the session identifier that matches the session identifier included in the message (step 232).
  • FIG. 3 is a flow chart illustrating a process 300 that shows steps that are preformed in the event primary SLB 114 experiences a failure.
  • Process 300 may begin in step 302, where SLB monitor 112 determines whether SLB 114 has experienced a failure. If SLB 114 has not experienced a failure, SLB monitor 112 continues monitoring SLB 114. In the event of a failure, process 300 proceeds to step 304.
  • a control message (a.k.a., a connection data synchronization message) is transmitted to each target processing unit 102a to 102n (or each target processing unit identified in table 121).
  • Each control message may be addressed to the replication agent 106 running on the target processing unit to which the control message was sent, thus, the control message is provided to the replication agent.
  • the control message may be sent by SLB monitor 112 in response to it determining that SLB 114 has failed. While SLB monitor 112 is shown as being separate and apart from stand-by SLB 116, this is not a requirement as monitor 112 may be a module of SLB 116.
  • the replication agent 106 transmits to stand-by SLB 116 each of the session identifiers it stored in storage unit 109 if it hasn't earlier removed the session identifier from the storage unit (step 306).
  • replication agent 106 may transmit to SLB 116 a replication message comprising the set of session identifiers.
  • Replication agent 106 may obtain the network address of stand-by SLB 116 from a configuration file stored in storage unit 109 or it may be included in the control message.
  • connection table 123 is replicated connection data. For example, for each session identifier that SLB 116 receives from a particular replication agent 106, SLB 116 may add to table 123 a record comprising a first field that stores the session identifier and a second field that stores a target processing unit identifier that identifies the target processing unit on which the replication agent is running, thereby storing information that maps the session identified by the session identifier with the target processing unit identified by the target processing unit identifier. This target processing unit identifier may be included in the replication message sent by the replication agent in step 306.
  • SLB 116 receives session traffic (e.g., a packet), via network 120, transmitted from some device (not shown) connected to network 120, and uses the information mapping sessions to target processing units (e.g., connection table 123) to forward the packet to the appropriate target processing unit as described above in connection with FIG. 2 .
  • session traffic e.g., a packet
  • target processing units e.g., connection table 123
  • connection table 123 will not be an exact duplicate of connection table 117.
  • connection table 123 will contain all of the records from connection table 117 that map a session to a target processing unit other than the failed target processing unit, which means that stand-by SLB will be able to route all of the active sessions that were not mapped to the failed target processing unit 102.
  • FIG. 4 illustrates a block diagram of an SLB apparatus 400, according to some embodiments, configured to perform SLB functions described above.
  • SLB 400 may include: a data processor 402, which may include one or more microprocessors and/or one or more circuits, such as an application specific integrated circuit (ASIC), Field-programmable gate arrays (FPGAs), etc; a network interface 404 for interfacing with network 110; a network interface 405 for interfacing with network 120; a storage system 406, which may include one or more non-volatile storage devices and/or one or more volatile storage devices (e.g., random access memory (RAM)).
  • ASIC application specific integrated circuit
  • FPGAs Field-programmable gate arrays
  • computer instructions 408 may be stored in storage system 406.
  • the computer instructions 408 may be embodied in a computer program stored using a computer readable means, such as, but not limited, to magnetic media (e.g., a hard disk), optical media (e.g., a DVD), memory devices (e.g., random access memory), etc.
  • computer instructions 408 is configured such that when computer instructions 408 are executed, SLB 400 is operable to perform steps described above (e.g., steps describe above with reference to the flow charts shown in FIGs. 2 and 3 ).
  • SLB 400 is configured to perform steps described above without the need for software 408. That is, for example, data processor 402 may consist merely of one or more ASICs.
  • the features of the present invention described above may be implemented in hardware and/or software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)

Claims (16)

  1. Procédé de secours à froid pour une reprise après une défaillance d'un équilibreur SLB principal (114), le procédé de secours à froid étant mis en oeuvre par un équilibreur SLB auxiliaire (116) dans un environnement comprenant une pluralité d'unités de traitement cibles (102a) ... (102n), incluant une première unité de traitement cible et une seconde unité de traitement cible, et un équilibreur de charge de serveur principal (SLB) (114) destiné à équilibrer le trafic à travers la pluralité d'unités de traitement cibles (102a) ... (102n), dans lequel des données de connexion pour mettre en concordance des sessions sur des unités de traitement cibles (102a) ... (102n) sont stockées dans un magasin de stockage de données (115) accessible par l'équilibreur SLB principal (114), et les données de connexion comportent des premières informations mettant en concordance une première session sur la première unité de traitement cible et des secondes informations mettant en concordance une deuxième session sur la seconde unité de traitement cible, le procédé consistant à :
    répliquer, par le biais de l'équilibreur SLB auxiliaire (116), au moins une partie des données de connexion, de sorte que les données de connexion répliquées sont accessibles par l'équilibreur SLB auxiliaire (116), et les données de connexion répliquées comprenant au moins les premières informations, caractérisé en ce que l'étape de réplication est mise en oeuvre en réponse à une détection de la défaillance de l'équilibreur SLB principal (114); et
    suite à la réplication des données de connexion :
    (a) recevoir, au niveau de l'équilibreur SLB auxiliaire (116), le trafic correspondant à la première session ;
    (b) accéder, par le biais de l'équilibreur SLB auxiliaire (116), aux données de connexion répliquées, en vue de déterminer l'unité de traitement cible sur laquelle la première session est mise en concordance ; et
    (c) acheminer, par le biais de l'équilibreur SLB auxiliaire (116), le trafic vers l'unité de traitement cible déterminée.
  2. Procédé selon la revendication 1, consistant en outre à :
    recevoir, au niveau de l'équilibreur SLB auxiliaire (116), le trafic correspondant à une troisième session ;
    accéder aux données de connexion répliquées en vue de déterminer si les données accédées comportent des informations mettant en concordance la troisième session sur l'une quelconque de la pluralité d'unités de traitement cibles (102a) ... (102n) ; et
    en réponse à la détermination que les données accédées ne comportent pas d'informations mettant en concordance la troisième session sur l'une quelconque de la pluralité d'unités de traitement cibles (102a) ... (102n) :
    (a) sélectionner une unité de traitement cible spécifique ;
    (b) mettre à jour les données de connexion répliquées de sorte que les données de connexion répliquées comprendront des informations mettant en concordance la troisième session sur l'unité de traitement cible sélectionnée ; et
    (c) transmettre, à un agent de réplication exécuté sur l'unité de traitement cible sélectionnée, un message de mise à jour de données de connexion comprenant un identifiant de session identifiant la troisième session.
  3. Procédé selon la revendication 1 ou 2, dans lequel l'étape de réplication des données de connexion consiste à :
    recevoir, au niveau de l'équilibreur SLB auxiliaire (116), un premier message de réplication transmis à partir de la première unité de traitement cible, dans lequel le premier message de réplication contient un identifiant de session identifiant la première session ; et
    en réponse à la réception du premier message de réplication, stocker des informations qui mettent en concordance la première session sur la première unité de traitement cible.
  4. Procédé selon l'une quelconque des revendications 1 à 3, consistant en outre à :
    transmettre, en réponse à la défaillance de l'équilibreur SLB principal (114), un message de synchronisation de données de connexion à chacune des première et seconde unités de traitement cibles, dans lequel
    chacune des première et seconde unités de traitement cibles est configurée de manière à transmettre un ou plusieurs messages de réplication à l'équilibreur SLB auxiliaire (116) en réponse à la réception du message de synchronisation de données de connexion.
  5. Procédé selon l'une quelconque des revendications 1 à 4, dans lequel
    les premières informations se composent d'un premier enregistrement comprenant un premier champ stockant un identifiant de session identifiant la première session et un second champ stockant un identifiant d'unité de traitement cible identifiant la première unité de traitement cible ; et
    les secondes informations se composent d'un second enregistrement comprenant un second champ stockant un identifiant de session identifiant la deuxième session et un second champ stockant un identifiant d'unité de traitement cible identifiant la seconde unité de traitement cible.
  6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel l'étape de réception, au niveau de l'équilibreur SLB auxiliaire (116), du trafic correspondant à la première session consiste à recevoir, au niveau de l'équilibreur SLB auxiliaire (116), un paquet de réseau comprenant des informations identifiant la première session, dans lequel
    le paquet de réseau est un paquet de protocole Internet (IP) qui contient un en-tête IP et une charge utile, dans lequel la charge utile contient un segment de couche de transport présentant un en-tête et une charge utile de couche de transport, et
    les données de l'en-tête IP et de l'en-tête de couche de transport identifient le paquet de réseau comme correspondant à la première session.
  7. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel l'équilibreur SLB principal (114) s'exécute sur la seconde unité de traitement cible et les données de connexion répliquées ne contiendront pas les secondes informations qui mettent en concordance la deuxième session sur la seconde unité de traitement cible.
  8. Procédé selon la revendication 3, dans lequel
    les données de connexion comportent en outre des troisièmes informations mettant en concordance une troisième session sur la première unité de traitement cible ; et
    le premier message de réplication transmis à partir de la première unité de traitement cible contient non seulement l'identifiant de session identifiant la première session, mais également un identifiant de session identifiant la troisième session.
  9. Équilibreur de charge de serveur auxiliaire (SLB) (116) pour une reprise après la défaillance d'un équilibreur SLB principal (114) qui est exploitable de manière à équilibrer le trafic à travers une pluralité d'unités de traitement cibles (102a) ... (102n) en utilisant des données de connexion qui comportent des informations mettant en concordance des sessions sur des unités de traitement cibles, caractérisé en ce que : l'équilibreur SLB auxiliaire (116) est configuré de sorte que, en réponse à une détection de la défaillance de l'équilibreur SLB principal (114), l'équilibreur SLB auxiliaire réplique au moins une partie des données de connexion en vue de créer des informations de données de connexion répliquées mettant en concordance des sessions établies sur des unités de traitement cibles, accessibles par l'équilibreur SLB auxiliaire (116), l'équilibreur SLB auxiliaire (116) utilise les données de connexion répliquées en vue de déterminer l'unité de traitement cible sur laquelle une session est mise en concordance et d'acheminer le trafic vers l'unité de traitement cible déterminée.
  10. Équilibreur SLB auxiliaire (116) selon la revendication 9, dans lequel l'équilibreur SLB auxiliaire (116) est configuré de manière à répliquer les données de connexion en recevant un ou plusieurs messages de réplication à partir d'une ou plusieurs des unités de traitement cibles (102a) ... (102n), chacun dudit un ou desdits plusieurs messages de réplication comprenant un identifiant de session et un identifiant d'unité de traitement cible.
  11. Équilibreur SLB auxiliaire (116) selon l'une quelconque des revendications 9 à 10, dans lequel l'équilibreur SLB auxiliaire (116) est en outre configuré de sorte que l'équilibreur SLB auxiliaire (116), en réponse à la défaillance de l'équilibreur SLB principal (114), transmet un message de synchronisation de données de connexion à au moins l'une de la pluralité d'unités de traitement cibles.
  12. Équilibreur SLB auxiliaire (116) selon l'une quelconque des revendications 9 à 11, dans lequel
    les données de connexion comportent un enregistrement comprenant un premier champ stockant un identifiant de session identifiant une session et un second champ stockant un identifiant d'unité de traitement cible identifiant une unité de traitement cible ; et
    les données de connexion répliquées comportent un enregistrement comprenant un premier champ stockant l'identifiant de session identifiant la session et un second champ stockant l'identifiant d'unité de traitement cible identifiant l'unité de traitement cible.
  13. Équilibreur SLB auxiliaire (116) selon l'une quelconque des revendications 9 à 12, dans lequel l'équilibreur SLB auxiliaire (116) est exploitable de manière à :
    recevoir un paquet de réseau correspondant à la première session ;
    utiliser les données de connexion répliquées en vue de déterminer l'unité de traitement cible sur laquelle la première session est mise en concordance ; et
    acheminer le paquet de réseau vers l'unité de traitement cible déterminée, dans lequel
    le paquet de réseau est un paquet de protocole Internet (IP) qui contient un en-tête IP et une charge utile, dans lequel la charge utile contient un segment de couche de transport présentant une charge utile et un en-tête de couche de transport ; et
    les données de l'en-tête IP et de l'en-tête de couche de transport identifient le paquet de réseau comme correspondant à la première session.
  14. Produit-programme informatique comprenant un support utilisable par ordinateur dans lequel est intégré un code de programme lisible par ordinateur, ledit code de programme lisible par ordinateur étant apte à être exécuté en vue de mettre en oeuvre un procédé comprenant les étapes ci-dessous consistant à :
    répliquer, par le biais d'un équilibreur SLB auxiliaire (116), des informations de données de connexion mettant en concordance des sessions sur des unités de traitement cibles utilisées par un équilibreur de charge de serveur principal (SLB) immédiatement en réponse à une détection selon laquelle l'équilibreur SLB principal est défaillant, dans lequel les données de connexion répliquées sont accessibles par l'équilibreur SLB auxiliaire (116) ; et
    dans lequel l'équilibreur SLB auxiliaire (116) utilise les données de connexion répliquées en vue de déterminer l'unité de traitement cible sur laquelle une session est mise en concordance et d'acheminer le trafic vers l'unité de traitement cible déterminée.
  15. Unité de traitement cible, dans laquelle le traitement cible inclut un agent de réplication, l'agent de réplication étant exploitable de manière à :
    recevoir, en provenance d'un équilibreur de charge de serveur principal (SLB) (114), un message de mise à jour de données de connexion comprenant un identifiant de session identifiant une session mise en concordance sur l'unité de traitement cible ; et
    stocker l'identifiant de session en réponse à la réception du message de mise à jour de données de connexion, caractérisée en ce que :
    l'agent de réplication est configuré de manière à transmettre l'identifiant de session à un équilibreur SLB auxiliaire (116), en réponse à la réception d'un message de synchronisation à la suite d'une défaillance de l'équilibreur SLB principal (114).
  16. Unité de traitement cible selon la revendication 15, dans laquelle l'agent de réplication est en outre exploitable de manière à :
    recevoir, en provenance de l'équilibreur SLB principal (114), un second message de mise à jour de données de connexion comprenant un second identifiant de session identifiant une deuxième session mise en concordance sur l'unité de traitement cible ; et
    stocker le second identifiant de session en réponse à la réception du second message de mise à jour de données de connexion, caractérisée en ce que :
    l'agent de réplication est configuré de sorte que, en réponse à la réception du message de synchronisation, à la suite d'une défaillance de l'équilibreur SLB principal (114), l'agent de réplication transmet, à l'équilibreur SLB auxiliaire (116), un message de réplication contenant les premier et second identifiants de session.
EP10740368.5A 2010-07-13 2010-07-13 Systèmes et procédés de reprise après la défaillance d'un équilibreur de charge de serveur Not-in-force EP2594051B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2010/053207 WO2012007793A1 (fr) 2010-07-13 2010-07-13 Systèmes et procédés de reprise après la défaillance d'un équilibreur de charge de serveur

Publications (2)

Publication Number Publication Date
EP2594051A1 EP2594051A1 (fr) 2013-05-22
EP2594051B1 true EP2594051B1 (fr) 2014-05-21

Family

ID=43853293

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10740368.5A Not-in-force EP2594051B1 (fr) 2010-07-13 2010-07-13 Systèmes et procédés de reprise après la défaillance d'un équilibreur de charge de serveur

Country Status (3)

Country Link
US (2) US20130086414A1 (fr)
EP (1) EP2594051B1 (fr)
WO (1) WO2012007793A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9893997B2 (en) * 2016-04-07 2018-02-13 Nxp Usa,Inc. System and method for creating session entry
CN107919971B (zh) * 2016-10-09 2019-06-28 腾讯科技（深圳）有限公司 用于音视频通讯连接容灾的方法、装置及系统

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5774660A (en) * 1996-08-05 1998-06-30 Resonate, Inc. World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network
WO2001059999A1 (fr) * 2000-02-11 2001-08-16 Convergent Networks, Inc. Environnent executable au niveau des services pour rtpc integres et reseaux ip, et langage de traitement des appels a cet effet
US6731598B1 (en) 2000-09-28 2004-05-04 Telefonaktiebolaget L M Ericsson (Publ) Virtual IP framework and interfacing method
US20020073211A1 (en) 2000-12-12 2002-06-13 Raymond Lin System and method for securely communicating between application servers and webservers
US7383329B2 (en) 2001-02-13 2008-06-03 Aventail, Llc Distributed cache for state transfer operations
US7512702B1 (en) 2002-03-19 2009-03-31 Cisco Technology, Inc. Method and apparatus providing highly scalable server load balancing
US7139926B1 (en) 2002-08-30 2006-11-21 Lucent Technologies Inc. Stateful failover protection among routers that provide load sharing using network address translation (LSNAT)
US8572249B2 (en) * 2003-12-10 2013-10-29 Aventail Llc Network appliance for balancing load and platform services
US8155117B2 (en) * 2004-06-29 2012-04-10 Qualcomm Incorporated Filtering and routing of fragmented datagrams in a data network
WO2006107883A2 (fr) * 2005-04-01 2006-10-12 Arroyo Video Solutions, Inc. Basculement du controle d'un flux distribue en continu
US8788640B1 (en) 2005-08-16 2014-07-22 F5 Networks, Inc. Employing rate shaping class capacities and metrics to balance connections
US7702947B2 (en) * 2005-11-29 2010-04-20 Bea Systems, Inc. System and method for enabling site failover in an application server environment
US20070150600A1 (en) 2005-12-22 2007-06-28 International Business Machines Corporation Method and apparatus for collecting data for characterizing HTTP session workloads
US20070220302A1 (en) * 2006-02-28 2007-09-20 Cline Brian G Session failover management in a high-availability server cluster environment
US7987266B2 (en) * 2008-07-29 2011-07-26 International Business Machines Corporation Failover in proxy server networks
US8166100B2 (en) * 2008-08-28 2012-04-24 Avg Technologies Cz, S.R.O. Cross site, cross domain session sharing without database replication
JP5458688B2 (ja) * 2009-03-19 2014-04-02 富士通株式会社 一意性保証支援プログラム、サービス提供システム、及び一意性保証実現方法
US8824362B2 (en) 2009-03-24 2014-09-02 Optis Wireless Technology, Llc Systems and methods for transmitting serving grants to a serving base station
US9032398B2 (en) * 2010-07-12 2015-05-12 Vmware, Inc. Online classification of memory pages based on activity level represented by one or more bits
EP2803178B1 (fr) 2012-01-12 2018-04-11 Telefonaktiebolaget LM Ericsson (publ) Systèmes et procédés pour l'équilibrage de charge extensible et élastique

Also Published As

Publication number Publication date
US20170322855A1 (en) 2017-11-09
WO2012007793A1 (fr) 2012-01-19
US11119871B2 (en) 2021-09-14
EP2594051A1 (fr) 2013-05-22
US20130086414A1 (en) 2013-04-04

Similar Documents

Publication Publication Date Title
US11606300B2 (en) Network flow management for isolated virtual networks
US9998955B1 (en) Multi-tier stateful network flow management architecture
EP2803178B1 (fr) Systèmes et procédés pour l'équilibrage de charge extensible et élastique
US9424325B2 (en) Recording medium, distribution controlling method, and information processing device
US9438520B2 (en) Synchronizing state among load balancer components
US9934273B1 (en) Metadata synchronization in flow management systems
US8356078B2 (en) Multi-homed data forwarding storage
NO331320B1 (no) Balansering av nettverksbelastning ved bruk av informasjon om vertsmaskin-status
WO2017193966A1 (fr) Procédé de commutation de liaison d'un service dans un système de stockage, et dispositif de stockage
US10097454B1 (en) Flexible packet rewriting framework
US20190123956A1 (en) Server network interface level failover
CN105634832B (zh) 一种服务器的备份方法和装置
CN116530066A (zh) 保护有状态业务功能路径的方法和装置
CN112367257B (zh) 路由通告方法及装置
US11119871B2 (en) Systems and methods recovering from the failure of a server load balancer
JP7230206B2 (ja) プロトコルパケットの処理
US8984619B2 (en) Methods, systems, and computer readable media for adaptive assignment of an active security association instance in a redundant gateway configuration
CN111083160A (zh) 资源信息恢复方法及装置
TW200836525A (en) Selective passive address resolution learning
JP4757670B2 (ja) システム切替方法、その計算機システム及びプログラム
JP2001244977A (ja) データ転送装置、データ転送システム、データ転送方法及び記憶媒体
US20220232071A1 (en) Load balancing systems and methods
CN112104531A (zh) 一种备份实现方法及装置
US8352776B2 (en) Facilitating persistence of routing states
WO2021024377A1 (fr) Commutateur l2, procédé de commande de communication, et programme de commande de communication

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

AK Designated contracting states

Kind code of ref document: A1

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

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20131211

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): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM 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

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 670081

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140615

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010016265

Country of ref document: DE

Effective date: 20140710

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 670081

Country of ref document: AT

Kind code of ref document: T

Effective date: 20140521

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010016265

Country of ref document: DE

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

Ref country code: LU

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20150331

26N No opposition filed

Effective date: 20150224

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

Ref country code: CH

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

Effective date: 20140731

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010016265

Country of ref document: DE

Effective date: 20150224

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

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

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

Ref country code: SM

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

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

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

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

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

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

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

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

Ref country code: MK

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

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

Ref country code: AL

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602010016265

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04L0065000000

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

Ref country code: NL

Payment date: 20220726

Year of fee payment: 13

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

Ref country code: GB

Payment date: 20220727

Year of fee payment: 13

Ref country code: DE

Payment date: 20220629

Year of fee payment: 13

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602010016265

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20230801

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

Effective date: 20230713

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

Ref country code: NL

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

Effective date: 20230801

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

Ref country code: NL

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

Effective date: 20230801

Ref country code: DE

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

Effective date: 20240201

Ref country code: GB

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

Effective date: 20230713