EURÓPAI SZABADALOM SZÖVEGÉNEK FORDÍTÁSA. (51) Int. Cl.: H04L 12/24 ( )

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "EURÓPAI SZABADALOM SZÖVEGÉNEK FORDÍTÁSA. (51) Int. Cl.: H04L 12/24 (2006.01)"

Transcription

1 *HU T2* HU T2 (19) HU (11) Lajstromszám: E (13) T2 MAGYARORSZÁG Szellemi Tulajdon Nemzeti Hivatala EURÓPAI SZABADALOM SZÖVEGÉNEK FORDÍTÁSA (21) Magyar ügyszám: E (22) A bejelentés napja: (51) Int. Cl.: H04L 12/24 ( ) (96) Az európai bejelentés bejelentési száma: EP (97) Az európai bejelentés közzétételi adatai: EP A (97) Az európai szabadalom megadásának meghirdetési adatai: EP B (30) Elsőbbségi adatok: P US (72) Feltaláló(k): Saltsidis, Panagiotis, , Stockholm (SE) Ding, Zhemin, , Solna (SE) Nolish, Kevin, Pittsburgh, PA (US) (73) Jogosult(ak): Telefonaktiebolaget L M Ericsson (publ), Stockholm (SE) (74) Képviselő: dr. Antalffy-Zsíros András, DANUBIA Szabadalmi és Jogi Iroda Kft., Budapest (54) Összekapcsolhatósági hibakezelési forgalomjelző kiterjesztés Az európai szabadalom ellen, megadásának az Európai Szabadalmi Közlönyben való meghirdetésétől számított kilenc hónapon belül, felszólalást lehet benyújtani az Európai Szabadalmi Hivatalnál. (Európai Szabadalmi Egyezmény 99. cikk(1)) A fordítást a szabadalmas az évi XXXIII. törvény 84/H. -a szerint nyújtotta be. A fordítás tartalmi helyességét a Szellemi Tulajdon Nemzeti Hivatala nem vizsgálta.

2 (19) (11) EP B1 (12) EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention of the grant of the patent: Bulletin 2011/23 (51) Int Cl.: H04L 12/24 ( ) (21) Application number: (22) Date of filing: (54) Connectivity fault management traffic indication extension Erweiterung von Verkehrserkennung für Konnektivitätsfehlerverwaltung Extension d indication de trafic de gestion de défaillance de connectivité (84) Designated Contracting States: 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 TR (30) Priority: US P (43) Date of publication of application: Bulletin 2009/43 (60) Divisional application: (73) Proprietor: Telefonaktiebolaget L M Ericsson (publ) Stockholm (SE) (72) Inventors: Saltsidis, Panagiotis , Stockholm (SE) Ding, Zhemin , Solna (SE) Nolish, Kevin Pittsburgh, PA (US) (74) Representative: Sjöberg, Mats Hakan Ericsson AB Patent Unit IP Networks Box Älvsjö (SE) (56) References cited: US-A US-B SIEMENS: "METRO ETHERNET DEPLOYMENT WITH SIEMENS PBB-TE - SURPASS HID 6600" INTERNET CITATION, [Online] no. VERSION 1.0, pages 1-14, XP Retrieved from the Internet: URL: carrier ethernet/downloads/metro%20ethe rnet%20deployment%20with%20siemens%20p BB-T E.pdf> [retrieved on ] "IEEE Standard for Local and metropolitan area networks - Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault Management; IEEE Std 802.1ag (Amendment to IEEE Std 802.1Q as amended by IEEE Std 802.1ad and IEEE Std 802.1ak )" IEEE STANDARD; [IEEE STANDARD], IEEE, PISCATAWAY, NJ, USA, 17 December 2007 ( ), pages 1-260, XP ISBN: EP B1 Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). Printed by Jouve, PARIS (FR)

3 1 EP B1 2 Description TECHNICAL FIELD [0001] The present invention relates to communication networks. More specifically, and without limitation, the invention is directed to a Traffic field indicator for use in Connectivity Fault Management (CFM) messages to provide enhanced control of Ethernet Switched Paths (ESPs). BACKGROUND [0002] Connectivity Fault Management (CFM), as described in IEEE 802.1ag, is a key component of operation, administration, and maintenance for carrier Ethernet. IEEE 802.1ag specifies protocols, procedures, and managed objects for end-to-end fault detection, verification, and isolation. IEEE ag establishes managed objects, called Maintenance Associations (MAs), to verify the integrity of a single service instance by exchanging CFM messages. The scope of an MA is determined by its Management Domain (MD), which describes a network region where connectivity and performance is managed. Each MA associates two or more Maintenance Association Endpoints (MEPs) and enables Maintenance Association Intermediate Points (MIPs) to support fault detection and isolation. [0003] A continuity check protocol is used for fault detection. Each MEP periodically transmits Connectivity Check Messages (CCMs) and tracks CCMs received from other MEPs in the same maintenance association. [0004] FIG. 1 illustrates the format of an existing CFM Protocol Data Unit (PDU). A common CFM Header consists of a Management Domain (MD) level field 11, Version field 12, OpCode field 13, Flags field 14, and First Time, Length, and Value (TLV) Offset field 15. The Flags field 14 of the Common CFM Header is currently split into three parts: 1. RDI field (one bit, the most significant bit); 2. Reserved field (4 bits); and 3. CCM Interval field (the least significant three bits). [0005] Provider Backbone Bridging - Traffic Engineering (PBB-TE), as described in IEEE Qay, was designed to provide full traffic engineering of paths in a bridged network. PBB-TE eliminates the need for backbone devices to perform learning and flooding. Instead of using Multiple Spanning Tree Protocol/Rapid Spanning Tree Protocol (MSTP/RSTP) for loop avoidance, PBB-TE uses a management plane or an external control plane to create static filtering table entries in the component bridges. [0006] PBB-TE is a connection-oriented Ethernet technology that uses a statically configured tuple consisting of the Backbone Destination Address (B-DA), Backbone Source Address (B-SA), and Backbone VLAN ID (B-VID) to create a PBB-TE path. The provisioned path is called an Ethernet Switched Path (ESP). Two co-routed pointto-point ESPs with the same Customer Backbone Port (CBP) MAC addresses form a bidirectional MAC service, which is called a point-to-point Traffic Engineering Service Instance (TESI). [0007] PBB-TE supports 1:1 bidirectional path-protection switching. Two point-to-point TESIs are provisioned. One TESI is configured as a "working" TESI and the other as a "protection" TESI. In normal conditions, traffic is transmitted over the working TESI. In the event of either a failure of the working TESI or a specific administrative request, traffic is switched to the protection TESI. Optionally, PBB-TE 1:1 protected paths may be configured to allow for load sharing. In this case, customer services denoted by an I-TAGed frame flow may be present on both TESIs in a protection group. [0008] FIG. 2 illustrates a conventional PBB-TE protection group 20. The protection group includes a working TESI 21, a protection TESI 22, a near end (East B-Component) 23, and a far end (West B-Component) 24. The near end (East B-Component) includes Provider Network Ports (PNPs) 25a and 25b and Customer Backbone Port (CBP) 26. The far end (West B-Component) includes PNPs 27a and 27b and CBP 28. Each TESI is monitored by an independent MA, and each MA has two MEPs. One is located in the CBP 26 of the near end; the other is located in the CBP 28 of the far end. When the near end MEP detects the loss of CCMs, it notifies the far end MEP by sending a CCM with a Remote Defect Indicator (RDI) flag. Both ends are aware of the failure (either by loss of CCMs or receiving the CCM with the RDI flag), so protection switching to the protection TESI is executed on both ends. When the failure is cleared, traffic may be switched back to the working TESI 21 or may stay in the protection TESI 22 according to the configured mode (revertive or non-revertive). [0009] ITU-T G.8031 defines the Automatic Protection Switching (APS) protocol and linear protection switching mechanisms for point-to-point VLAN-based Ethernet Subnetwork connections in Ethernet transport networks. Linear 1+1 and 1:1 protection switching architectures with unidirectional and bidirectional switching are supported. [00] The current PBB-TE draft (2.0) supports 1:1 bidirectional path protection switching based upon the ITU- T G.8031 model. The differences between PBB-TE protection functionality and ITU-T G.8031 protection functionality are: ITU-T G.8031 defines the APS protocol as the signaling Protocol Data Unit (PDU) while PBB-TE reuses/extends the CCM PDU to avoid the unnecessary complexity of an additional signaling PDU. In PBB-TE, an "out-of-band" management system is assumed to coordinate the two ends of the protected service belonging to a single domain. In PBB-TE, a protected flow is identified by a TESI 2

4 3 EP B1 4 while in G.8031 the protected flow is identified by a VLAN ID (VID). [0011] In a related publication by Siemens, "Metro Ethernet Deployment with Siemens PBB-TE, SURPASS hid 6600", dated 13 March 2007, fault detection is described in a PBB-TE protection group comprising a working TESI and a protection TESI. CCMs are sent between endpoints to monitor the status of the working TESI. The group switches over to the protection TESI if a fault is detected. However, the Siemens publication does not address a mismatch between the endpoints. [0012] Likewise, U.S. Patent Application Publication No. 2007/ discusses fault detection in primary and backup sub-domains within a broadcast domain. Primary and backup maintenance associations are monitored, and when a fault is detected within the primary sub-domain maintenance association, a switch to the backup sub-domain maintenance association occurs. However, like the Siemens publication, the application does not address a mismatch between the endpoints. [0013] Additionally, U.S. Patent No. 7,093,027 discloses a fast protection mechanism for VLAN-only connections and for connections that are based partially on VLAN technology and partially on MPLS technology. The mechanism provides for switchover from a main VLAN to an alternative VLAN in the event of a link failure. Once again, the patent does not address a mismatch between the endpoints. [0014] In 1:1 bidirectional protection switching, a mismatch between the bridge/selector positions of the near end 23 and the far end 24 can occur. To maintain the proper operation of the network, this mismatch should be detected and reported to the network operator. Then the network operator can clear the defect. There are two types of mismatch in 1:1 bidirectional protection switching: Protection switching incomplete mismatch; and Working/protection configuration mismatch [0015] Still referring to FIG. 2, a scenario is depicted in which a protection switching incomplete mismatch occurs. In this example, due to a hardware malfunction, the near end (East B-Component) 23 fails to switch over, but it sends an RDI to the far end (West B-Component) 24. The far end switches to the protection TESI 22 while the near end is still in the working TESI 21. Similarly, a mismatch can also occur when the near end switches to the protection TESI, but the far end fails to switch when it receives the RDI. [0016] A mismatch can also occur because of a wrong configuration. For example, one end may be configured to send traffic on the working TESI 21 while the other end is configured to send traffic on the protection TESI 22. Similarly, one end may be configured in the revertive mode while the other end is configured in the non-revertive mode. In this case, the mismatch occurs when a failure is cleared. [0017] Based on the existing mechanisms, there are two ways to address the mismatch problem, but both are undesirable in a PBB-TE environment. [0018] First, the APS protocol can be utilized to detect the mismatch (as in G.8031), but this approach is too complicated. In G.8031, the APS protocol is designed for Linear 1+1 and 1:1 protection switching architectures with unidirectional and bidirectional switching. Since PBB-TE only focuses on 1:1 bidirectional protection switching, and PBB-TE already assumes an "out-ofband" management system to coordinate both ends in a single domain, the APS protocol brings a great many duplicated and unnecessary functionalities. In addition, adding the APS protocol to a bridge creates major architecture changes. [0019] FIG. 3 illustrates an example of how a mismatch in 1:1 bidirectional protection switching may be detected by an "out-of-band" Operations Support System/Network Management System (OSS/NMS) 31. Although the mismatch can be detected by using the APS protocol, without APS, the OSS/NMS can be utilized. In step 32, the OSS/NMS requests the selector/bridge position from both the near end (East B-Component) 23 and the far end (West B-Component) 24. At step 33, the near end and far end report their selector/bridge positions to the OSS/NMS. At step 34, the OSS/NMS compares the reported positions to detect a mismatch. For the PBB-TE environment, this process is too slow, and it has the additional disadvantage of having to be initiated proactively by an operator. SUMMARY [0020] It is desirable to have a simple mechanism based on the existing bridge architecture to constantly monitor the working/protection entities and to immediately and automatically report to an operator if a mismatch occurs. The present invention provides a CCM enhancement based on the existing bridge architecture to solve the mismatch problem. It is fully compliant with the existing standard. In addition, the present invention can be used to adjust the CCM interval to save bandwidth. In certain scenarios, it is also possible to use the invention to provide in-band signaling support for operator requests. [0021] In one embodiment, the present invention utilizes one of the four reserved bits in the Flags field of a CCM to indicate traffic status. For example, the bit may indicate whether the traffic is transmitted in the TESI monitored by these CCMs. This bit is referred to herein as the "Traffic field". [0022] The mismatch is detected by the corresponding MEP when the Traffic field of transmitted CCMs and received CCMs does not match for a predefined period of time (for example, 50 ms or longer). The mismatch defect is cleared when the corresponding MEP receives the first CCM that indicates the same Traffic field as its transmit- 3

5 5 EP B1 6 ted CCMs. [0023] Thus, in one embodiment, the present invention is directed to a method of controlling traffic between a first network element and a second network element connected by a working network path and a protection network path. The method includes the steps of setting a Traffic field in a configuration message sent between the first and second network elements, the Traffic field indicating which network path is being utilized to transport the traffic; receiving the configuration message in one of the network elements; and taking action to control the traffic based upon a value of the Traffic field in the received configuration message. The step of taking action may include comparing the value of the Traffic field in the received configuration message with a value of a Traffic field in configuration messages sent from the receiving network element, and when the Traffic field value in the received configuration message does not match the Traffic field value in configuration messages sent from the receiving network element, moving the traffic from its current path to the other network path. In one embodiment, the traffic is moved only when the Traffic field value in the received configuration message has not matched the Traffic field value in configuration messages sent from the receiving network element for a predefined period of time. [0024] In a particular embodiment, the working network path and the protection network path are bidirectional point-to-point Traffic Engineering Service Instances (TESIs), and the step of setting a Traffic field in a configuration message includes setting a Traffic field in a Connectivity Check Message (CCM) by utilizing a reserved bit within a Flags field as the Traffic field. [0025] By utilizing the Traffic field in CCMs, a MEP may determine the traffic load on the different TESIs. When there is no traffic on a given TESI, the MEP may increase a CCM interval on the given TESI in response. Likewise, if the Traffic field subsequently indicates that traffic has been switched to the given TESI, the MEP may dynamically reduce the CCM interval on the given TESI in response. The MEP may also respond to changes of the value of the Traffic field in received CCMs to move traffic from one TESI to the other in order to balance the traffic between the TESIs. Likewise, the MEP may set the Traffic field in response to an operator request to move traffic from one TESI to another. [0026] In another embodiment, the present invention is directed to a MEP associated with a first Customer Backbone Port for controlling traffic between the first Customer Backbone Port and a second Customer Backbone Port, wherein the Customer Backbone Ports are connected by a working TESI and a protection TESI. The MEP includes means for setting a Traffic field in a first CCM sent from the first Customer Backbone Port to the second Customer Backbone Port, the Traffic field indicating which TESI is being utilized to transport the traffic. The MEP also includes means for receiving a second CCM sent from the second Customer Backbone Port; means for determining whether the Traffic field in the second CCM matches the Traffic field in the first CCM; and means for taking action to control the traffic based upon a result obtained from the determining means. The actions taken may include moving traffic from one TESI to another when the Traffic fields do not match. This may be done to balance the traffic load or in response to an operator request. The MEP may also dynamically increase or reduce the CCM interval on the given TESI in response to the traffic load. BRIEF DESCRIPTION OF THE DRAWINGS [0027] In the following, the essential features of the invention will be described in detail by showing preferred embodiments, with reference to the attached figures in which: FIG. 1 (Prior Art) illustrates the format of an existing CFM Protocol Data Unit (PDU); FIG. 2 (Prior Art) illustrates an existing PBB-TE protection group; FIG. 3 (Prior Art) illustrates an example of how a mismatch in 1:1 bidirectional protection switching may be detected by an "out-of-band" Operations Support System/Network Management System (OSS/NMS); FIG. 4 illustrates the format of a Flags field modified in accordance with one embodiment of the present invention; FIG. 5 is a flow chart illustrating the steps of an embodiment of the method of the present invention when CCMs are sent by the MEP; FIG. 6 is a flow chart illustrating the steps of an embodiment of the method of the present invention when CCMs are received by the MEP; FIG. 7 is a flow chart illustrating the steps of an embodiment of the method of the present invention for providing an adaptive CCM interval; FIG. 8 (Prior Art) illustrates an existing scenario in which an operator request can only be sent to the NE/EMS at one end of a protected PBB-TE service instance; and FIG. 9 illustrates an embodiment of the method of the present invention for providing in-band signaling support for an administrative command; FIG. is a flow chart illustrating the steps of an embodiment of the method of the present invention for supporting load sharing; and FIG. 11 is a simplified block diagram of a MEP in an embodiment of the present invention. DETAILED DESCRIPTION [0028] FIG. 4 illustrates the format of a Flags field 14 modified in accordance with one embodiment of the present invention. In this embodiment, one of the reserved bits is utilized to indicate traffic status of the mon- 4

6 7 EP B1 8 itored path. This bit is referred to herein as the "Traffic field" 41. [0029] FIG. 5 is a flow chart illustrating the steps of an embodiment of the method of the present invention when CCMs are sent by the MEP. At step 51, the MEP compares its own destination address and Backbone VLAN ID (B-VID) against the Backbone Destination Address (B-DA) and B-VID entries in the backbone service instance table. At step 52, it is determined whether the MEP s destination address and B-VID are in the backbone service instance table. If not, the method moves to step 53 where the MEP sets the Traffic field of outgoing CCMs to "0". However, if the MEP s destination address and B-VID are in the backbone service instance table, the method moves instead to step 54 where the MEP sets the Traffic field of outgoing CCMs to "1". [0030] FIG. 6 is a flow chart illustrating the steps of an embodiment of the method of the present invention when CCMs are received by the MEP. At step 61, the MEP inspects the Traffic field 41 of the received CCMs. At step 62, it is determined whether the received Traffic field is different from the Traffic field of CCMs sent by this MEP for at least a predefined period of time (for example, 50 ms). If not, the method moves to step 63 where no mismatch is detected. However, if the received Traffic field is different from the Traffic field of CCMs sent by this MEP for at least the predefined period of time, the method moves instead to step 64 where a mismatch defect is declared. [0031] There are additional applications of the Traffic field 41 in CCM messaging. For example, the Traffic field may be utilized to provide an adaptive CCM interval. Ethernet OAM provides a mechanism for checking connectivity in a provider network by transmission of CCM frames at a specified interval. A smaller interval reduces the time to detect a connectivity failure but does so at the expense of a greater fraction of overhead CCM traffic. By using the new Traffic field 41, MEPs on either the working TESI 21 or the protection TESI 22 are kept informed of the traffic status. [0032] FIG. 7 is a flow chart illustrating the steps of an embodiment of the method of the present invention for providing an adaptive CCM interval. At step 71, there is no traffic on the TESI monitored by the CCMs. Therefore, at step 72, the CCM interval is increased to save bandwidth. At step 73, the traffic is switched to the monitored TESI. At step 74, the corresponding MEPs are informed of the traffic change by the Traffic field 41. At step 75, the MEPs dynamically reduce the CCM interval. [0033] The Traffic field 41 can also be used for in-band signaling of administrative commands. The protection switching mechanism must allow for manual operation by the network operator regardless of the network state. Similar to mismatch detection, there are two choices for disseminating administrative commands from network operators. First, the APS protocol can be used, but as discussed above, APS is complicated and redundant for PBB-TE. Second, a management system can be utilized (e.g., OMS/NMS) to notify both ends of a PBB-TE service instance. In certain scenarios, however, operator requests may originate from a single end such as a Network Element (NE) or Element Management System (EMS). The present invention provides a convenient way to propagate operator requests to the other end. [0034] FIG. 8 illustrates an existing scenario in which an operator request can only be sent to the NE/EMS at one end of a protected PBB-TE service instance. An NMS 81 controls EMS 82 in access network 1, EMS 83 in the core network, and EMS 84 in access network 2. An operator request 85 may be received in EMS 82 in access network 1. EMS 82 controls NE 86 to forward the operator request toward the core NEs 87 and 88. In order to coordinate the switching of the other end, the operator request must be communicated in-band over the PBB-TE service instance, thus decreasing available bandwidth. [0035] FIG. 9 illustrates an embodiment of the method of the present invention for providing in-band signaling support for an administrative command. In this embodiment, the new Traffic field 41 is utilized for in-band signaling of the operator request over the PBB-TE protection group. In this example, the command is for manual switching from the working TESI to the protection TESI. [0036] At step 91, an operator request called "manual switching from working to protection" is sent to the far end of the protected PBB-TE service instance (West B- Component) 24. At step 92, the far end West B-Component switches traffic from the working TESI 21 to the protection TESI 22 and changes the Traffic field 41. At step 93, the far end reports its state to the NMS. At step 94, the near end (East B-Component) 23 detects a mismatch in the Traffic field 41 of received CCMs. At step 95, the near end (East B-Component) reports the defect of mismatch to the NMS and at step 96, the NMS notifies the near end (East B-Component) 23 of its state. The near end then switches traffic from the working TESI 21 to the protection TESI 22. Note in this example that the near end cannot tell whether the mismatch was due to an operator s request for a manual switch, a forced switch, or a mismatch defect. So the near end has to get its state information from the NMS. [0037] FIG. is a flow chart illustrating the steps of an embodiment of the method of the present invention for supporting load sharing. At step 1, the Traffic field bit 41 is set on every CCM TESI that is carrying customer traffic. At step 2 an operator determines that traffic should be moved off of a given TESI. At step 3, the operator moves the traffic off of the given TESI simply by clearing the Traffic field bit. [0038] FIG. 11 is a simplified block diagram of a MEP 1 in an embodiment of the present invention. The MEP is associated with a Customer Backbone Port (CBP) such as CBP 26 or CBP 28 in FIG. 1. The MEP monitors traffic between its associated CBP and another CBP connected by a working TESI 21 and a protection TESI 22. The MEP includes a Traffic field setter 111 for setting the Traffic field in CCMs to be sent by a CCM transmitter 112. The 5

7 9 EP B1 Traffic field may be set by setting the reserved bit 41 (FIG. 4) in the Flags field of the CCM. A CCM receiver 113 receives CCMs sent from the other CBP, and a Traffic field comparison unit 114 compares the Traffic field in sent CCMs with the Traffic field in received CCMs to determine whether the Traffic fields match. [0039] When the Traffic field in received CCMs matches the Traffic field in sent CCMs, the MEP continues to send the traffic on its current TESI. When the Traffic field in received CCMs does not match the Traffic field in sent CCMs, the MEP may declare a mismatch defect and move the traffic accordingly. In one embodiment, the MEP includes a timer 115, and the traffic is moved only when the timer indicates that the Traffic field in received CCMs has not matched the Traffic field value in sent CC- Ms for a predefined period of time. [0040] The MEP may also include a load determining unit 116 for determining the traffic load on each TESI 21 and 22. If a given TESI has no traffic, a CCM interval controller 117 may increase the CCM interval on the given TESI in response. Subsequently, the load determining unit may detect from the Traffic field in received CCMs that traffic has been switched to the given TESI. In response, the CCM interval controller may dynamically reduce the CCM interval on the given TESI. [0041] In another embodiment, the load determining unit 116 may report the traffic load on each TESI 21 and 22 to a TESI load balancer 118. The TESI load balancer moves traffic from one TESI to the other in order to balance the traffic between the TESIs. [0042] The MEP 1 may also receive operator requests to control the traffic. The requests are sent to the Traffic field setter 111, which changes the Traffic field in outgoing CCMs to a value corresponding to the operator request. The other CBP receives the CCMs and responds to the Traffic field. [0043] Note also that the Traffic field bit 41 may be used on CCM messages at the Service ID (I-SID) level to allow for cross-checking and switching at a per-customer service level. [0044] The operations of the MEP may be controlled by a processor 119 running computer program instructions stored on a memory 120. [0045] Although preferred embodiments of the present invention have been illustrated in the accompanying drawings and described in the foregoing Detailed Description, it is understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the scope of the invention as defined by the following claims Ports are connected by a working Traffic Engineering Service Instance, TESI, (21) and a protection TESI (22), characterized by said method comprising the steps of: setting a Traffic field (41) in a first Continuity Check Message, CCM, sent from the first Customer Backbone Port to the second Customer Backbone Port on the working or protection TE- SI, said Traffic field indicating a current TESI being utilized to transport the traffic from the first Customer Backbone Port; receiving by the first Customer Backbone Port, a second CCM sent from the second Customer Backbone Port, wherein the second Customer Backbone Port indicates in the second CCM, which TESI is being utilized to transport the traffic from the second Customer Backbone Port; determining whether the Traffic field in the second CCM matches the Traffic field in the first CCM; and detecting a mismatch when the Traffic field in the second CCM does not match the Traffic field in the first CCM. 2. The method as recited in claim 1, further comprising the steps of: when the Traffic field in the second CCM matches the Traffic field in the first CCM, continuing to send the traffic from the first Customer Backbone Port on the current TESI; and when the Traffic field in the second CCM does not match the Traffic field in the first CCM, moving the traffic by the first Customer Backbone Port from the current TESI to the other TESI. 3. The method as recited in claim 2, wherein the step of moving the traffic to the other TESI includes moving the traffic only when the Traffic field value in the second CCM has not matched the Traffic field value in a plurality of CCMs sent from the first Customer Backbone Port for a predefined period of time. 4. The method as recited in claim 1, wherein the step of setting the Traffic field in the first CCM includes utilizing a reserved bit within a Flags field as the Traffic field. 5. The method as recited in claim 1, further comprising the steps of: Claims 1. A method of detecting a mismatch between a first Customer Backbone Port and a second Customer Backbone Port, wherein the Customer Backbone 55 determining from the mismatch there is no traffic on an identified one of the TESIs; and increasing a CCM interval on the identified TESI, wherein the CCM interval is a specified interval for periodic transmission of CCMs. 6

8 11 EP B The method as recited in claim 5, further comprising the steps of: subsequently detecting from the Traffic field that traffic has been subsequently switched to the identified TESI; and dynamically reducing the CCM interval on the identified TESI in response to detecting that traffic has been switched to the identified TESI. 7. The method as recited in claim 4, further comprising responding to changes of the value of the Traffic field in received CCMs to move traffic from one TESI to the other in order to balance the traffic between the TESIs. 8. The method as recited in claim 1, wherein the step of setting the Traffic field includes setting the Traffic field in response to receiving an operator request at the first or second Customer Backbone Port. 9. A Maintenance Association Endpoint, MEP, (1) associated with a first Customer Backbone Port for detecting a mismatch between the first Customer Backbone Port and a second Customer Backbone Port, wherein the Customer Backbone Ports are connected by a working Traffic Engineering Service Instance, TESI, (21) and a protection TESI (22), characterized by said MEP comprising: means (111) for setting a Traffic field (41) in a first Continuity Check Message, CCM, sent from the first Customer Backbone Port to the second Customer Backbone Port on the working or protection TESI, said Traffic field indicating a current TESI being utilized to transport the traffic from the first Customer Backbone Port; means (113) for receiving by the first Customer Backbone Port, a second CCM sent from the second Customer Backbone Port, wherein the second Customer Backbone Port indicates in the second CCM, which TESI is being utilized to transport the traffic from the second Customer Backbone Port; means (114) for determining whether the Traffic field in the second CCM matches the Traffic field in the first CCM; and means (118) for detecting a mismatch when the Traffic field in the second CCM does not match the Traffic field in the first CCM means for continuing to send the traffic from the first Customer Backbone Port on the current TE- SI when the Traffic field in the second CCM matches the Traffic field in the first CCM; and means for moving the traffic by the first Customer Backbone Port from the current TESI to the other TESI when the Traffic field in the second CCM does not match the Traffic field in the first CCM. 11. The MEP as recited in claim, further comprising a timer, wherein the means for moving the traffic moves the traffic only when the timer indicates that the Traffic field has not matched the Traffic field value in a plurality of sent CCMs for a predefined period of time. 12. The MEP as recited in claim 9, wherein the means for setting a Traffic field in the first CCM is adapted to utilize a reserved bit within a Flags field as the Traffic field. 13. The MEP as recited in claim 9, further comprising: means for determining from the mismatch there is no traffic on an identified one of the TESIs; and means for increasing a CCM interval on the identified TESI, wherein the CCM interval is a specified interval for periodic transmission of CCMs. 14. The MEP as recited in claim 13, further comprising: means for subsequently detecting from the Traffic field in the second CCM that traffic has been subsequently switched to the identified TESI; and means for dynamically reducing the CCM interval on the identified TESI in response to detecting that traffic has been switched to the identified TESI. 15. The MEP as recited in claim 9, further comprising means responsive to changes of the Traffic field in the second CCM to move traffic from one TESI to the other in order to balance the traffic between the TESIs. 16. The MEP as recited in claim 9, further comprising: means for receiving an operator request to control the traffic; and means for changing the Traffic field in the first CCM message to a value corresponding to the operator request.. The MEP as recited in claim 9, further comprising: 55 Patentansprüche 1. Verfahren zum Detektieren einer Fehlanpassung zwischen einem ersten Kunden-Backbone-Port und einem zweiten Kunden-Backbone-Port, worin die Kunden-Backbone-Ports durch eine Betriebs-TESI (Traffic Engineering Service Instance, Verkehrtech- 7

9 13 EP B1 14 nik-dienstinstanz) (21) und eine Schutz-TESI (22) verbunden sind, dadurch gekennzeichnet, dass das Verfahren folgende Schritte umfasst: Setzen eines Verkehrsfelds (41) in eine erste Kontinuitätsprüfungsnachricht, CCM, die vom ersten Kunden-Backbone-Port an den zweiten Kunden-Backbone-Port auf der Betriebs- oder Schutz-TESI gesendet wird, wobei das Verkehrsfeld anzeigt, dass eine gegenwärtige TESI genutzt wird, um den Verkehr vom ersten Kunden-Backbone-Port zu transportieren; Empfangen einer vom zweiten Kunden-Backbone-Port gesendeten zweiten CCM durch den ersten Kunden-Backbone-Port, worin der zweite Kunden-Backbone-Port in der zweiten CCM anzeigt, welche TESI genutzt wird, um den Verkehr vom zweiten Kunden-Backbone-Port zu transportieren; Bestimmen, ob das Verkehrsfeld in der zweiten CCM auf das Verkehrsfeld in der ersten CCM angepasst ist; und Detektieren einer Fehlanpassung, wenn das Verkehrsfeld in der zweiten CCM nicht auf das Verkehrsfeld in der ersten CCM angepasst ist. 2. Verfahren nach Anspruch 1, außerdem folgende Schritte umfassend: wenn das Verkehrsfeld in der zweiten CCM auf das Verkehrsfeld in der ersten CCM angepasst ist, das Senden des Verkehrs vom ersten Kunden-Backbone-Port auf der gegenwärtigen TE- SI fortsetzen; und wenn das Verkehrsfeld in der zweiten CCM nicht auf das Verkehrsfeld in der ersten CCM angepasst ist, den Verkehr durch den ersten Kunden- Backbone-Port von der gegenwärtigen TESI zur anderen TESI verlegen. 3. Verfahren nach Anspruch 2, worin der Schritt des Verlegens des Verkehrs zur anderen TESI einschließt, dass der Verkehr nur dann verlegt wird, wenn der Verkehrsfeldwert in der zweiten CCM auf den Verkehrsfeldwert in einer Vielzahl von CCMs nicht angepasst ist, die vom ersten Kunden-Backbone-Port für eine vordefinierte Zeitperiode gesendet wurden. 4. Verfahren nach Anspruch 1, worin der Schritt des Setzens des Verkehrsfelds in die erste CCM einschließt, ein reserviertes Bit innerhalb eines Flag- Felds als das Verkehrsfeld zu nutzen. 5. Verfahren nach Anspruch 1, außerdem folgende Schritte umfassend: aus der Fehlanpassung bestimmen, dass auf einer der TESIs, die identifiziert ist, kein Verkehr stattfindet; und Vergrößern eines CCM-Intervalls auf der identifizierten TESI, worin das CCM-Intervall ein spezifiziertes Intervall für periodische Übertragung von CCMs ist. 6. Verfahren nach Anspruch 5, außerdem folgende Schritte umfassend: nachfolgendes Detektieren aus dem Verkehrsfeld, dass Verkehr nachfolgend auf die identifizierte TESI umgeschaltet wurde; und dynamisches Reduzieren des CCM-Intervalls auf der identifizierten TESI als Reaktion auf das Detektieren, dass Verkehr auf die identifizierte TESI umgeschaltet wurde. 7. Verfahren nach Anspruch 4, außerdem das Reagieren auf Änderungen des Werts des Verkehrsfelds in empfangenen CCMs umfassend, um zwecks Ausgleich des Verkehrs zwischen den TESIs Verkehr von einer TESI zur anderen zu verlegen. 8. Verfahren nach Anspruch 1, worin der Schritt des Setzens des Verkehrsfelds das Setzen des Verkehrsfelds als Reaktion auf den Empfang einer Operatoranforderung am ersten oder zweiten Kunden- Backbone-Port einschließt. 9. Maintenance-Association-Endpoint, MEP, (1), mit einem ersten Kunden-Backbone-Port assoziiert, um eine Fehlanpassung zwischen dem ersten Kunden- Backbone-Port und einem zweiten Kunden-Backbone-Port zu detektieren, worin die Kunden-Backbone- Ports durch eine Betriebs-TESI(Traffic Engineering Service Instance, Verkehrtechnik-Dienstinstanz) (21) und eine Schutz-TESI (22) verbunden sind, dadurch gekennzeichnet, dass der MEP Folgendes umfasst: Mittel (111) zum Setzen eines Verkehrsfelds (41) in eine erste Kontinuitätsprüfungsnachricht, CCM, die vom ersten Kunden-Backbone- Port an den zweiten Kunden-Backbone-Port auf der Betriebs- oder Schutz-TESI gesendet wird, wobei das Verkehrsfeld anzeigt, dass eine gegenwärtige TESI genutzt wird, um den Verkehr vom ersten Kunden-Backbone-Port zu transportieren; Mittel (113) zum Empfangen einer vom zweiten Kunden-Backbone-Port gesendeten zweiten CCM durch den ersten Kunden-Backbone-Port, worin der zweite Kunden-Backbone-Port in der zweiten CCM anzeigt, welche TESI genutzt wird, um den Verkehr vom zweiten Kunden- Backbone-Port zu transportieren; Mittel (114) zum Bestimmen, ob das Verkehrs- 8

10 15 EP B1 16 feld in der zweiten CCM auf das Verkehrsfeld in der ersten CCM angepasst ist; und Mittel (118) zum Detektieren einer Fehlanpassung, wenn das Verkehrsfeld in der zweiten CCM nicht auf das Verkehrsfeld in der ersten CCM angepasst ist.. MEP nach Anspruch 9, außerdem umfassend: MEP nach Anspruch 9, außerdem umfassend: Mittel zum Empfangen einer Operatoranforderung, den Verkehr zu steuern; und Mittel zum Ändern des Verkehrsfelds in der ersten CCM-Nachricht auf einen Wert, der der Operatoranforderung entspricht. Mittel, um das Senden des Verkehrs vom ersten Kunden-Backbone-Port auf der gegenwärtigen TESI fortzusetzen, wenn das Verkehrsfeld in der zweiten CCM auf das Verkehrsfeld in der ersten CCM angepasst ist; und Mittel, um den Verkehr durch den ersten Kunden-Backbone-Port von der gegenwärtigen TE- SI zur anderen TESI zu verlegen, wenn das Verkehrsfeld in der zweiten CCM nicht auf das Verkehrsfeld in der ersten CCM angepasst ist. 11. MEP nach Anspruch, außerdem einen Timer umfassend, worin das Mittel zum Verlegen des Verkehrs den Verkehr nur dann verlegt, wenn der Timer anzeigt, dass das Verkehrsfeld auf den Verkehrsfeldwert in einer Vielzahl von gesendeten CCMs für eine vordefinierte Zeitperiode nicht angepasst war. 12. MEP nach Anspruch 9, worin das Mittel zum Setzen eines Verkehrsfelds in die erste CCM angepasst ist, ein reserviertes Bit innerhalb eines Flag-Felds als Verkehrsfeld zu nutzen. 13. MEP nach Anspruch 9, außerdem umfassend: Mittel, um aus der Fehlanpassung zu bestimmen, dass auf einer der TESIs, die identifiziert ist, kein Verkehr stattfindet; und Mittel zum Vergrößern eines CCM-Intervalls auf der identifizierten TESI, worin das CCM-Intervall ein spezifiziertes Intervall für periodische Übertragung von CCMs ist. 14. MEP nach Anspruch 13, außerdem umfassend: Mittel zum nachfolgenden Detektieren aus dem Verkehrsfeld in der zweiten CCM, dass Verkehr nachfolgend auf die identifizierte TESI umgeschaltet wurde; und Mittel zum dynamischen Reduzieren des CCM- Intervalls auf der identifizierten TESI als Reaktion auf das Detektieren, dass Verkehr auf die identifizierte TESI umgeschaltet wurde. 15. MEP nach Anspruch 9, außerdem Mittel umfassend, die auf Änderungen des Verkehrsfelds in der zweiten CCM reagieren, um zwecks Ausgleich des Verkehrs zwischen den TESIs Verkehr von einer TESI zur anderen zu verlegen Revendications 1. Procédé destiné à détecter une discordance entre un premier port de réseau fédérateur de client et un second port de réseau fédérateur de client, dans lequel les ports de réseau fédérateur de client sont connectés par une instance de service d ingénierie de trafic, TESI, opérationnelle (21) et une instance TESI de protection (22), caractérisé en ce que ledit procédé comporte les étapes ci-dessous consistant à: définir un champ de trafic (41) dans un premier message de contrôle de continuité, CCM, envoyé du premier port de réseau fédérateur de client au second port de réseau fédérateur de client sur l instance TESI de protection ou opérationnelle, ledit champ de trafic indiquant une instance TESI en cours, laquelle est utilisée en vue d acheminer le trafic en provenance du premier port de réseau fédérateur de client ; recevoir, par le biais du premier port de réseau fédérateur de client, un second message CCM envoyé par le second port de réseau fédérateur de client, dans lequel le second port de réseau fédérateur de client indique, dans le second message CCM, quelle instance TESI est à ce moment utilisée en vue d acheminer le trafic à partir du second port de réseau fédérateur de client ; déterminer si le champ de trafic dans le second message CCM correspond au champ de trafic dans le premier message CCM ; et détecter une discordance lorsque le champ de trafic dans le second message CCM ne correspond pas au champ de trafic dans le premier message CCM. 2. Procédé selon la revendication 1, comportant en outre les étapes ci-dessous consistant à : lorsque le champ de trafic dans le second message CCM correspond au champ de trafic dans le premier message CCM, continuer à envoyer le trafic en provenance du premier port de réseau fédérateur de client sur l instance TESI en cours ; et lorsque le champ de trafic dans le second message CCM ne correspond pas au champ de tra- 9

11 17 EP B1 18 fic dans le premier message CCM, déplacer le trafic par le biais du premier port de réseau fédérateur de client de l instance TESI en cours à l autre instance TESI. 3. Procédé selon la revendication 2, dans lequel l étape consistant à déplacer le trafic vers l autre instance TESI inclut l étape consistant à déplacer le trafic uniquement lorsque la valeur de champ de trafic dans le second message CCM n a pas présenté de correspondance avec la valeur de champ de trafic dans une pluralité de messages CCM envoyés à partir du premier port de réseau fédérateur de client au cours d une période de temps prédéfinie. 4. Procédé selon la revendication 1, dans lequel l étape consistant à définir le champ de trafic dans le premier message CCM comporte l étape consistant à utiliser un bit réservé au sein d un champ de fanions en tant que champ de trafic. 5. Procédé selon la revendication 1, comportant en outre les étapes ci-dessous consistant à : déterminer à partir de la discordance qu il n y a pas de trafic sur une instance identifiée parmi les instances TESI ; et augmenter un intervalle de message CCM sur l instance TESI identifiée ; dans lequel l intervalle de message CCM est un intervalle spécifié pour une transmission périodique de messages CCM. 6. Procédé selon la revendication 5, comportant en outre les étapes ci-dessous consistant à : détecter subséquemment à partir du champ de trafic que le trafic a été subséquemment commuté vers l instance TESI identifiée ; et réduire de manière dynamique l intervalle de message CCM sur l instance TESI identifiée en réponse à la détection de la commutation du trafic vers l instance TESI identifiée. 7. Procédé selon la revendication 4, comportant en outre répondre à une modification de la valeur du champ de trafic dans des messages CCM reçus en vue de déplacer le trafic d une instance TESI à l autre afin d équilibrer le trafic entre les instances TESI. 8. Procédé selon la revendication 1, dans lequel l étape consistant à définir le champ de trafic inclut l étape consistant à définir le champ de trafic en réponse à la réception d une demande d opérateur au niveau du premier ou second port de réseau fédérateur de client. 9. Point d extrémité d association de maintenance, MEP, (1) associé à un premier port de réseau fédérateur de client pour détecter une discordance entre le premier port de réseau fédérateur de client et un second port de réseau fédérateur de client, dans lequel les ports de réseau fédérateur de client sont connectés par une instance de service d ingénierie de trafic, TESI, opérationnelle (21) et une instance TESI de protection (22), caractérisé en ce que ledit point d extrémité MEP comporte : un moyen (111) pour définir un champ de trafic (41) dans un premier message de contrôle de continuité, CCM, envoyé du premier port de réseau fédérateur de client au second port de réseau fédérateur de client sur l instance TESI de protection ou opérationnelle, ledit champ de trafic indiquant une instance TESI en cours laquelle est utilisée en vue d acheminer le trafic en provenance du premier port de réseau fédérateur de client ; un moyen (113) pour recevoir par le biais du premier port de réseau fédérateur de client, un second message CCM envoyé par le second port de réseau fédérateur de client, dans lequel le second port de réseau fédérateur de client indique dans le second message CCM, quelle instance TESI est à ce moment utilisée en vue d acheminer le trafic à partir du second port de réseau fédérateur de client ; un moyen (114) pour déterminer si le champ de trafic dans le second message CCM correspond au champ de trafic dans le premier message CCM ; et un moyen (118) pour détecter une discordance lorsque le champ de trafic dans le second message CCM ne correspond pas au champ de trafic dans le premier message CCM.. MEP selon la revendication 9, comportant en outre : un moyen pour continuer à envoyer le trafic en provenance du premier port de réseau fédérateur de client sur l instance TESI en cours lorsque le champ de trafic dans le second message CCM correspond au champ de trafic dans le premier message CCM ; et un moyen pour déplacer le trafic par le biais du premier port de réseau fédérateur de client de l instance TESI en cours à l autre instance TESI lorsque le champ de trafic dans le second message CCM ne correspond pas au champ de trafic dans le premier message CCM. 11. MEP selon la revendication, comportant en outre un temporisateur, dans lequel le moyen pour déplacer le trafic déplace le trafic uniquement lorsque le temporisateur indique que le champ de trafic n a pas présenté de correspondance avec la valeur de

12 19 EP B1 20 champ de trafic dans une pluralité de messages CCM envoyés au cours d une période de temps prédéfinie. 12. MEP selon la revendication 9, dans lequel le moyen pour définir un champ de trafic dans le premier message CCM est apte à utiliser un bit réservé au sein d un champ de fanions en tant que champ de trafic MEP selon la revendication 9, comportant en outre : un moyen pour déterminer à partir de la discordance qu il n y a pas de trafic sur une instance identifiée parmi les instances TESI ; et un moyen pour augmenter un intervalle de message CCM sur l instance TESI identifiée, dans lequel l intervalle de message CCM est un intervalle spécifié pour une transmission périodique de messages CCM. 14. MEP selon la revendication 13, comportant en outre : un moyen pour détecter subséquemment à partir du champ de trafic dans le second message CCM que le trafic a été subséquemment commuté vers l instance TESI identifiée ; et un moyen pour réduire de manière dynamique l intervalle de message CCM sur l instance TESI identifiée en réponse à la détection de la commutation du trafic vers l instance TESI identifiée MEP selon la revendication 9, comportant en outre un moyen répondant aux modifications du champ de trafic dans le second message CCM en vue de déplacer le trafic d une instance TESI à l autre afin d équilibrer le trafic entre les instances TESI MEP selon la revendication 9, comportant en outre : un moyen pour recevoir une demande d opérateur en vue de commander le trafic ; et un moyen pour modifier le champ de trafic dans le premier message CCM en une valeur correspondant à la demande d opérateur

13 EP B1 12

14 EP B1 13

15 EP B1 14

16 EP B1 15

17 EP B1 16

18 EP B1 17

19 EP B1 REFERENCES CITED IN THE DESCRIPTION This list of references cited by the applicant is for the reader s convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard. Patent documents cited in the description US A [0012] US B [0013] 18

20

TEPZZ_768 7_B_T EP 1 768 371 B1 (19) (11) EP 1 768 371 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04M 19/04 (2006.01)

TEPZZ_768 7_B_T EP 1 768 371 B1 (19) (11) EP 1 768 371 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04M 19/04 (2006.01) (19) TEPZZ_768 7_B_T (11) EP 1 768 371 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.01.2014 Bulletin 2014/03 (1) Int Cl.: H04M 19/04 (2006.01)

More information

(51) Int Cl.: B29C 41/20 (2006.01) F21S 4/00 (2006.01) H05K 3/28 (2006.01)

(51) Int Cl.: B29C 41/20 (2006.01) F21S 4/00 (2006.01) H05K 3/28 (2006.01) (19) TEPZZ 68698B_T (11) EP 2 68 698 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.11.201 Bulletin 201/47 (21) Application number: 11808612.3

More information

*EP001173363B1* EP 1 173 363 B1 (19) (11) EP 1 173 363 B1 (12) EUROPEAN PATENT SPECIFICATION

*EP001173363B1* EP 1 173 363 B1 (19) (11) EP 1 173 363 B1 (12) EUROPEAN PATENT SPECIFICATION (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001173363B1* (11) EP 1 173 363 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

(51) Int Cl.: H04W 4/14 (2009.01)

(51) Int Cl.: H04W 4/14 (2009.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 2 184 897 B1 (4) Date of publication and mention of the grant of the patent: 14.03.12 Bulletin 12/11 (21) Application number: 087774.3 (22) Date of filing:

More information

(51) Int Cl.: G10L 15/26 (2006.01)

(51) Int Cl.: G10L 15/26 (2006.01) (19) TEPZZ Z 8B_T (11) EP 2 023 338 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 28.0.14 Bulletin 14/22 (1) Int Cl.: GL /26 (06.01) (21) Application

More information

(51) Int Cl.: G06F 13/38 (2006.01) G06F 1/16 (2006.01)

(51) Int Cl.: G06F 13/38 (2006.01) G06F 1/16 (2006.01) (19) TEPZZ 9777B_T (11) EP 2 97 77 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.07.1 Bulletin 1/29 (1) Int Cl.: G06F 13/38 (06.01) G06F 1/16 (06.01)

More information

(51) Int Cl.: H04N 7/16 (2011.01)

(51) Int Cl.: H04N 7/16 (2011.01) (19) TEPZZ_796 89B_T (11) EP 1 796 389 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.03.1 Bulletin 1/ (1) Int Cl.: H04N 7/16 (11.01) (21) Application

More information

(51) Int Cl.: G05F 3/26 (2006.01) G05F 3/24 (2006.01)

(51) Int Cl.: G05F 3/26 (2006.01) G05F 3/24 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 280 033 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 31.0.2006

More information

(51) Int Cl.: H04L 29/06 (2006.01) G06F 9/445 (2006.01) G06F 13/00 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) G06F 9/445 (2006.01) G06F 13/00 (2006.01) (19) TEPZZ_7486_6B_T (11) EP 1 748 616 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.09.2014 Bulletin 2014/36 (1) Int Cl.: H04L 29/06 (2006.01)

More information

TEPZZ 87_546A T EP 2 871 546 A2 (19) (11) EP 2 871 546 A2 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G05B 19/05 (2006.01)

TEPZZ 87_546A T EP 2 871 546 A2 (19) (11) EP 2 871 546 A2 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G05B 19/05 (2006.01) (19) TEPZZ 87_46A T (11) EP 2 871 46 A2 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 13.0.1 Bulletin 1/ (1) Int Cl.: G0B 19/0 (06.01) (21) Application number: 14188238.1 (22) Date of filing:

More information

TEPZZ 57_ A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: H04L 29/06 ( )

TEPZZ 57_ A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: H04L 29/06 ( ) (19) TEPZZ 57_ A_T (11) EP 2 571 223 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 20.03.2013 Bulletin 2013/12 (51) Int Cl.: H04L 29/06 (2006.01) (21) Application number: 11181229.3 (22)

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) (11) EP 2 07 816 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.0.11 Bulletin 11/18 (21) Application number: 07804833.7 (22) Date of filing:

More information

(51) Int Cl.: G06F 21/00 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: G06F 21/00 (2006.01) H04L 29/06 (2006.01) (19) TEPZZ_8Z_7 _B_T (11) EP 1 801 721 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.06. Bulletin /24 (1) Int Cl.: G06F 21/00 (06.01) H04L 29/06

More information

(51) Int Cl.: G06F 11/20 (2006.01)

(51) Int Cl.: G06F 11/20 (2006.01) (19) TEPZZ 66_ B_T (11) EP 2 366 13 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.0.201 Bulletin 201/20 (21) Application number: 08878183.6 (22)

More information

(51) Int Cl.: H04Q 3/00 (2006.01) H04M 1/72 (2006.01)

(51) Int Cl.: H04Q 3/00 (2006.01) H04M 1/72 (2006.01) (19) TEPZZ Z B_T (11) EP 2 0 113 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.09.1 Bulletin 1/38 (21) Application number: 07809477.8 (22) Date

More information

EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC

EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (19) (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (11) EP 2 124 357 A1 (43) Date of publication: 25.11.2009 Bulletin 2009/48 (21) Application number: 08849815.9 (22) Date

More information

(51) Int Cl.: H04M 3/50 (2006.01)

(51) Int Cl.: H04M 3/50 (2006.01) (19) TEPZZ_Z48_64B_T (11) EP 1 048 164 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.01.1 Bulletin 1/02 (21) Application number: 9893133.0 (22)

More information

(51) Int Cl.: G06F 1/00 (2006.01)

(51) Int Cl.: G06F 1/00 (2006.01) (19) (11) EP 0 972 234 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.09.07 Bulletin 07/36 (21) Application number: 98913219.6 (22) Date of filing:

More information

(56) References cited:

(56) References cited: (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 04 B1 (4) Date of publication and mention of the grant of the patent: 26.12.07 Bulletin 07/2 (21) Application number: 03742391.0 (22) Date of filing: 02.07.03

More information

EP 2 455 926 A1 (19) (11) EP 2 455 926 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 23.05.2012 Bulletin 2012/21

EP 2 455 926 A1 (19) (11) EP 2 455 926 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 23.05.2012 Bulletin 2012/21 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 4 926 A1 (43) Date of publication: 23.0.2012 Bulletin 2012/21 (21) Application number: 11190024.7 (1) Int Cl.: G08B 2/14 (2006.01) G08B 2/00 (2006.01) G0B

More information

(51) Int Cl.: H04L 12/56 (2006.01)

(51) Int Cl.: H04L 12/56 (2006.01) (19) (11) EP 1 779 90 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 28.12.11 Bulletin 11/2 (21) Application number: 0783482.2 (22) Date of filing:

More information

(51) Int Cl.: H04B 3/23 (2006.01)

(51) Int Cl.: H04B 3/23 (2006.01) (19) (11) EP 0 983 638 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.03.12 Bulletin 12/12 (21) Application number: 989232.7 (22) Date of filing:

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04M 15/00 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04M 15/00 (2006.01) (19) TEPZZ 7Z 74 B_T (11) EP 2 702 742 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.04. Bulletin /16 (21) Application number: 1171674.6 (22) Date

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04M 3/56 (2006.01) H04M 3/44 (2006.01) H04L 12/18 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04M 3/56 (2006.01) H04M 3/44 (2006.01) H04L 12/18 (2006.01) (19) TEPZZ Z9 79B_T (11) EP 2 091 179 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.12.14 Bulletin 14/1 (21) Application number: 07817029.7 (22)

More information

(51) Int Cl.: G06F 1/00 (2006.01)

(51) Int Cl.: G06F 1/00 (2006.01) (19) TEPZZ_4 Z4ZB_T (11) EP 1 433 040 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 11.11.201 Bulletin 201/46 (21) Application number: 0277267.9

More information

(51) Int Cl.: H04L 12/10 (2006.01) H04L 12/40 (2006.01)

(51) Int Cl.: H04L 12/10 (2006.01) H04L 12/40 (2006.01) (19) TEPZZ 4799 B_T (11) EP 2 479 92 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 14.0.14 Bulletin 14/ (1) Int Cl.: H04L 12/ (06.01) H04L 12/ (06.01)

More information

(51) Int Cl.: H04L 12/24 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) (19) TEPZZ_8_9Z96B_T (11) EP 1 819 096 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 24..12 Bulletin 12/43 (21) Application number: 0818628.9 (22)

More information

(51) Int Cl.: G06F 9/455 (2006.01) G06F 9/50 (2006.01)

(51) Int Cl.: G06F 9/455 (2006.01) G06F 9/50 (2006.01) (19) TEPZZ 6987 B_T (11) EP 2 698 711 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.08.1 Bulletin 1/32 (21) Application number: 118777.8 (22) Date

More information

TEPZZ 9 Z5A_T EP 2 922 305 A1 (19) (11) EP 2 922 305 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 9 Z5A_T EP 2 922 305 A1 (19) (11) EP 2 922 305 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 9 ZA_T (11) EP 2 922 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 13(4) EPC (43) Date of publication: 23.09.1 Bulletin 1/39 (21) Application number: 1386446.2 (22) Date

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04L 12/26 (2006.01) H04M 3/22 (2006.01) H04M 7/00 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04L 12/26 (2006.01) H04M 3/22 (2006.01) H04M 7/00 (2006.01) (19) TEPZZ 48786B_T (11) EP 2 48 786 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 23.03.16 Bulletin 16/12 (21) Application number: 806012.0 (22)

More information

(51) Int Cl.: H04L 12/26 (2006.01)

(51) Int Cl.: H04L 12/26 (2006.01) (19) TEPZZ 84 8B_T (11) EP 2 84 338 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 23.09.1 Bulletin 1/39 (1) Int Cl.: H04L 12/26 (06.01) (21) Application

More information

(51) Int Cl.: G06F 11/14 (2006.01) G06F 12/08 (2006.01)

(51) Int Cl.: G06F 11/14 (2006.01) G06F 12/08 (2006.01) (19) TEPZZ 488949B_T (11) EP 2 488 949 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.0.14 Bulletin 14/19 (21) Application number: 76367.4 (22)

More information

(51) Int Cl.: H04L 12/24 (2006.01) H04L 12/26 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) H04L 12/26 (2006.01) (19) (11) EP 1 3 219 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.01.07 Bulletin 07/01 (1) Int Cl.: H04L 12/24 (06.01) H04L 12/26 (06.01) (21)

More information

(51) Int Cl.: H04L 12/26 (2006.01) H04L 12/24 (2006.01)

(51) Int Cl.: H04L 12/26 (2006.01) H04L 12/24 (2006.01) (19) TEPZZ 4 686 B_T (11) EP 2 426 862 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.08.1 Bulletin 1/33 (21) Application number: 769368.1 (22)

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04L 29/12 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04L 29/12 (2006.01) (19) TEPZZ_8 Z _9B_T (11) EP 1 8 319 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.06.1 Bulletin 1/2 (21) Application number: 08163. (22) Date

More information

(51) Int Cl.: H04L 12/46 (2006.01) H04L 29/14 (2006.01) H04L 29/12 (2006.01)

(51) Int Cl.: H04L 12/46 (2006.01) H04L 29/14 (2006.01) H04L 29/12 (2006.01) (19) (11) EP 1 342 344 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.06.09 Bulletin 09/23 (21) Application number: 019639.0 (22) Date of filing:.08.01

More information

(51) Int Cl.: C08K 5/523 (2006.01) C08K 5/521 (2006.01) C08K 5/52 (2006.01) C08G 64/00 (2006.01)

(51) Int Cl.: C08K 5/523 (2006.01) C08K 5/521 (2006.01) C08K 5/52 (2006.01) C08G 64/00 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 0 78 966 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 01.03.06

More information

(51) Int Cl.: H04L 12/58 (2006.01)

(51) Int Cl.: H04L 12/58 (2006.01) (19) (11) EP 1 628 448 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.11.07 Bulletin 07/47 (1) Int Cl.: H04L 12/8 (06.01) (21) Application number:

More information

TEPZZ 6_Z76 A_T EP 2 610 763 A1 (19) (11) EP 2 610 763 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.:

TEPZZ 6_Z76 A_T EP 2 610 763 A1 (19) (11) EP 2 610 763 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: (19) TEPZZ 6_Z76 A_T (11) EP 2 6 763 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 03.07.2013 Bulletin 2013/27 (51) Int Cl.: G06F 17/30 (2006.01) (21) Application number: 12192220.7 (22)

More information

TEPZZ A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION

TEPZZ A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION (19) TEPZZ 89949A_T (11) EP 2 899 49 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 29.07.201 Bulletin 201/31 (21) Application number: 111986. (1) Int Cl.: G01R 1/08 (2006.01) G01R 19/27

More information

TEPZZ 84 587A_T EP 2 843 587 A1 (19) (11) EP 2 843 587 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06F 21/64 (2013.01)

TEPZZ 84 587A_T EP 2 843 587 A1 (19) (11) EP 2 843 587 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06F 21/64 (2013.01) (19) TEPZZ 84 87A_T (11) EP 2 843 87 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 04.03.201 Bulletin 201/ (1) Int Cl.: G06F 21/64 (2013.01) (21) Application number: 13181902.1 (22) Date

More information

(51) Int Cl. 7 : G03G 15/00

(51) Int Cl. 7 : G03G 15/00 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001179B1* (11) EP 1 17 9 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the

More information

TEPZZ_9 6Z46B_T EP 1 926 046 B1 (19) (11) EP 1 926 046 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.:

TEPZZ_9 6Z46B_T EP 1 926 046 B1 (19) (11) EP 1 926 046 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: (19) TEPZZ_9 6Z46B_T (11) EP 1 926 046 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.08.13 Bulletin 13/34 (1) Int Cl.: G06F 19/00 (11.01) (21)

More information

Carrier Grade Ethernet. Ethernet in service provider networks, MAN/WAN

Carrier Grade Ethernet. Ethernet in service provider networks, MAN/WAN Carrier Grade Ethernet Ethernet in service provider networks, MAN/WAN Carrier grade The term Carrier Ethernet implies that Ethernet services are carrier grade. Carrier grade is a system that is extremely

More information

(51) Int Cl.: H05K 1/02 (2006.01)

(51) Int Cl.: H05K 1/02 (2006.01) (19) (11) EP 1 229 767 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 20.01.2010 Bulletin 2010/03 (1) Int Cl.: H0K 1/02 (2006.01) (21) Application

More information

(51) Int Cl.: H04L 29/12 (2006.01)

(51) Int Cl.: H04L 29/12 (2006.01) (19) (11) EP 1 4 260 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.09.08 Bulletin 08/37 (1) Int Cl.: H04L 29/12 (06.01) (21) Application number:

More information

(51) Int Cl.: H04L 12/00 (2006.01)

(51) Int Cl.: H04L 12/00 (2006.01) (19) (11) EP 2 119 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 14.12.11 Bulletin 11/0 (21) Application number: 0789037.9 (22) Date of filing: 14.12.07

More information

TEPZZ 69 49A_T EP 2 693 349 A1 (19) (11) EP 2 693 349 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06F 17/30 (2006.01)

TEPZZ 69 49A_T EP 2 693 349 A1 (19) (11) EP 2 693 349 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06F 17/30 (2006.01) (19) TEPZZ 69 49A_T (11) EP 2 693 349 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 0.02.2014 Bulletin 2014/06 (1) Int Cl.: G06F 17/30 (2006.01) (21) Application number: 13160696.4 (22)

More information

(51) Int Cl.: G06F 13/42 (2006.01)

(51) Int Cl.: G06F 13/42 (2006.01) (19) TEPZZ 67487_B_T (11) EP 2 674 871 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.03.201 Bulletin 201/ (1) Int Cl.: G06F 13/42 (2006.01) (21)

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) TEPZZ Z9 96 B_T (11) EP 2 093 962 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 19.12.12 Bulletin 12/1 (21) Application number: 08800984.0 (22)

More information

(51) Int Cl.: H04L 12/24 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 487 11 B1 (4) Date of publication and mention of the grant of the patent: 01.07.09 Bulletin 09/27 (1) Int Cl.: H04L 12/24 (06.01) (21) Application number:

More information

(51) Int Cl.: H04L 9/32 (2006.01) G09C 1/00 (2006.01) G06F 21/33 (2013.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04L 9/32 (2006.01) G09C 1/00 (2006.01) G06F 21/33 (2013.01) H04L 29/06 (2006.01) (19) TEPZZ Z48B_T (11) EP 2 2 048 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.0. Bulletin / (21) Application number: 1179238.6 (22) Date of

More information

APPLICATION NOTE 210 PROVIDER BACKBONE BRIDGE WITH TRAFFIC ENGINEERING: A CARRIER ETHERNET TECHNOLOGY OVERVIEW

APPLICATION NOTE 210 PROVIDER BACKBONE BRIDGE WITH TRAFFIC ENGINEERING: A CARRIER ETHERNET TECHNOLOGY OVERVIEW PROVIDER BACKBONE BRIDGE WITH TRAFFIC ENGINEERING: A CARRIER ETHERNET TECHNOLOGY OVERVIEW By Thierno Diallo, Product Specialist Originally designed as a local-area network (LAN) communication protocol,

More information

TEPZZ_ 8_69B_T EP 1 338 169 B1 (19) (11) EP 1 338 169 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ_ 8_69B_T EP 1 338 169 B1 (19) (11) EP 1 338 169 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ_ 8_69B_T (11) EP 1 338 169 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 27.03.13 Bulletin 13/13 (21) Application number: 01997179. (22)

More information

(51) Int Cl.: H04L 29/06 (2006.01) H04Q 7/24 (2006.01) H04L 12/66 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) H04Q 7/24 (2006.01) H04L 12/66 (2006.01) (19) (11) EP 1 314 291 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:..07 Bulletin 07/41 (21) Application number: 0194907.2 (22) Date of filing: 06.07.01

More information

(51) Int Cl.: H04L 9/24 (2006.01) G06Q 10/00 (2012.01)

(51) Int Cl.: H04L 9/24 (2006.01) G06Q 10/00 (2012.01) (19) TEPZZ_4Z 68ZB_T (11) EP 1 2 680 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 01.04.1 Bulletin 1/14 (21) Application number: 02741722.9 (22)

More information

TEPZZ _Z9458A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: F02P 19/02 ( )

TEPZZ _Z9458A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: F02P 19/02 ( ) (19) TEPZZ _Z948A_T (11) EP 3 9 48 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 28.12.16 Bulletin 16/2 (1) Int Cl.: F02P 19/02 (06.01) (21) Application number: 161666.1 (22) Date of filing:.04.16

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 146 711 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.09.06

More information

(51) Int Cl.: G01C 21/36 (2006.01)

(51) Int Cl.: G01C 21/36 (2006.01) (19) TEPZZ_ 678B_T (11) EP 1 26 78 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.09.14 Bulletin 14/37 (1) Int Cl.: G01C 21/36 (06.01) (21) Application

More information

EUROPEAN PATENT SPECIFICATION

EUROPEAN PATENT SPECIFICATION Patentamt JEuropâisches European Patent Office Publication number: 0 1 47 5 9 7 Office européen des brevets R1 B1 EUROPEAN PATENT SPECIFICATION ( ) Date of publication of patent spécification: 05.08.87

More information

(51) Int Cl.: H04L 9/32 (2006.01) H04B 7/00 (2006.01) A61N 1/37 (2006.01)

(51) Int Cl.: H04L 9/32 (2006.01) H04B 7/00 (2006.01) A61N 1/37 (2006.01) (19) TEPZZ_4977B_T (11) EP 1 49 77 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.12.14 Bulletin 14/0 (21) Application number: 03723989.4 (22) Date

More information

(51) Int Cl.: H04L 12/58 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04L 12/58 (2006.01) H04L 29/06 (2006.01) (19) TEPZZ_986 8 B_T (11) EP 1 986 382 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 19.02.14 Bulletin 14/08 (1) Int Cl.: H04L 12/8 (06.01) H04L

More information

(51) Int Cl.: G04B 19/08 (2006.01)

(51) Int Cl.: G04B 19/08 (2006.01) (19) (11) EP 1 988 432 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.10.2011 Bulletin 2011/40 (21) Application number: 0771278.9 (22) Date of filing:

More information

(56) References cited:

(56) References cited: (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 43 18 B1 (4) Date of publication and mention of the grant of the patent: 02.12.09 Bulletin 09/49 (21) Application number: 02773111.6 (22) Date of filing:

More information

Title (fr) SOURCE IONIQUE INTERNE DOUBLE POUR PRODUCTION DE FAISCEAU DE PARTICULES AVEC UN CYCLOTRON

Title (fr) SOURCE IONIQUE INTERNE DOUBLE POUR PRODUCTION DE FAISCEAU DE PARTICULES AVEC UN CYCLOTRON Title (en) A TWIN INTERNAL ION SOURCE FOR PARTICLE BEAM PRODUCTION WITH A CYCLOTRON Title (de) DOPPELTE INTERNE IONENQUELLE FÜR PARTIKELSTRAHLHERSTELLUNG MIT EINEM ZYKLOTRON Title (fr) SOURCE IONIQUE INTERNE

More information

(51) Int Cl.: G06F 11/14 (2006.01) G06F 17/30 (2006.01)

(51) Int Cl.: G06F 11/14 (2006.01) G06F 17/30 (2006.01) (19) TEPZZ_97799B_T (11) EP 1 97 799 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 06.0. Bulletin /19 (1) Int Cl.: G06F 11/14 (06.01) G06F 17/ (06.01)

More information

ethernet alliance Provider Backbone Transport Overview Version 1.0 December 2007 Authors:

ethernet alliance Provider Backbone Transport Overview Version 1.0 December 2007 Authors: Provider Backbone Transport Overview Version 1.0 December 2007 Authors: David Allen, Nortel Paul Bottorff, Nortel Harpreet Chadha, Extreme Networks Peter Lunk, Extreme Networks David Martin, Nortel ethernet

More information

EP 2 133 666 A1 (19) (11) EP 2 133 666 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 16.12.2009 Bulletin 2009/51

EP 2 133 666 A1 (19) (11) EP 2 133 666 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 16.12.2009 Bulletin 2009/51 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 133 666 A1 (43) Date of publication: 16.12.2009 Bulletin 2009/51 (21) Application number: 08104321.8 (51) Int Cl.: G01F 1/075 (2006.01) G01F 1/115 (2006.01)

More information

TEPZZ 68575_A_T EP 2 685 751 A1 (19) (11) EP 2 685 751 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 68575_A_T EP 2 685 751 A1 (19) (11) EP 2 685 751 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 687_A_T (11) EP 2 68 71 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 3(4) EPC (43) Date of publication:.01.14 Bulletin 14/03 (21) Application number: 1278849.6 (22)

More information

(51) Int Cl.: G10L 19/00 (2006.01) H04L 1/20 (2006.01)

(51) Int Cl.: G10L 19/00 (2006.01) H04L 1/20 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 317 72 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.08.06

More information

TEPZZ 65Z79 A_T EP 2 650 793 A1 (19) (11) EP 2 650 793 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 65Z79 A_T EP 2 650 793 A1 (19) (11) EP 2 650 793 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 65Z79 A_T (11) EP 2 650 793 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (43) Date of publication: 16.10.2013 Bulletin 2013/42 (21) Application number: 12818771.3

More information

TEPZZ Z Z5_A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: F01L 1/356 ( ) F01L 1/047 (2006.

TEPZZ Z Z5_A_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: F01L 1/356 ( ) F01L 1/047 (2006. (19) TEPZZ Z Z5_A_T (11) EP 3 032 051 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 15.06.2016 Bulletin 2016/24 (51) Int Cl.: F01L 1/356 (2006.01) F01L 1/047 (2006.01) (21) Application

More information

(51) Int Cl.: G01S 7/52 (2006.01)

(51) Int Cl.: G01S 7/52 (2006.01) (19) (11) EP 0 92 48 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.08. Bulletin /33 (1) Int Cl.: G01S 7/2 (06.01) (21) Application number: 993172.3

More information

TEPZZ_57 7_9B_T EP 1 573 719 B1 (19) (11) EP 1 573 719 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ_57 7_9B_T EP 1 573 719 B1 (19) (11) EP 1 573 719 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ_7 7_9B_T (11) EP 1 73 719 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.11.13 Bulletin 13/47 (21) Application number: 0277098.3 (22) Date

More information

(51) Int Cl.: H04Q 11/04 (2006.01) H04L 12/64 (2006.01)

(51) Int Cl.: H04Q 11/04 (2006.01) H04L 12/64 (2006.01) (19) (11) EP 1 181 839 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 27.0.09 Bulletin 09/22 (21) Application number: 009391.3 (22) Date of filing:

More information

EP 2 492 881 A2 (19) (11) EP 2 492 881 A2 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 29.08.2012 Bulletin 2012/35

EP 2 492 881 A2 (19) (11) EP 2 492 881 A2 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 29.08.2012 Bulletin 2012/35 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 492 881 A2 (43) Date of publication: 29.08.2012 Bulletin 2012/35 (51) Int Cl.: G08B 13/16 (2006.01) G08B 25/08 (2006.01) (21) Application number: 12386006.6

More information

Connectivity Fault Management. Norman Finn

Connectivity Fault Management. Norman Finn Connectivity Fault Management Norman Finn 1 DISCLAIMER IEEE P802.1ag is a work in progress. Some of the information in this slide deck reflects consensus among IEEE 802.1 and ITU-T Q.3/13 participants.

More information

Europaisches Patentamt European Patent Office Office europeen des brevets (11) EP 0 219 886 B2

Europaisches Patentamt European Patent Office Office europeen des brevets (11) EP 0 219 886 B2 Europaisches Patentamt European Patent Office Office europeen des brevets (11) EP 0 219 886 B2 (12) NEW EUROPEAN PATENT SPECIFICATION (45) Date of publication and mention (51) Int CI.6: G07G 1/12 of the

More information

(51) Int Cl.: G08B 21/02 (2006.01) H04M 11/04 (2006.01)

(51) Int Cl.: G08B 21/02 (2006.01) H04M 11/04 (2006.01) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 224 642 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 1.03.06

More information

TEPZZ 5Z _9_B_T EP 2 502 191 B1 (19) (11) EP 2 502 191 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ 5Z _9_B_T EP 2 502 191 B1 (19) (11) EP 2 502 191 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ Z _9_B_T (11) EP 2 02 191 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.06.1 Bulletin 1/2 (21) Application number: 787872.0 (22) Date

More information

TEPZZ ZZ _5ZA_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: B60L 15/20 ( ) B60W 30/18 (2012.

TEPZZ ZZ _5ZA_T EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: B60L 15/20 ( ) B60W 30/18 (2012. (19) TEPZZ ZZ _ZA_T (11) EP 3 002 0 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 06.04.2016 Bulletin 2016/14 (1) Int Cl.: B60L /20 (2006.01) B60W 30/18 (2012.01) (21) Application number:

More information

(51) Int Cl.: H04N 7/52 (2011.01)

(51) Int Cl.: H04N 7/52 (2011.01) (19) TEPZZ_9776 B_T (11) EP 1 977 611 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.01.13 Bulletin 13/03 (21) Application number: 0683819.1 (22)

More information

EP 1 976 249 B1 (19) (11) EP 1 976 249 B1 (12) EUROPEAN PATENT SPECIFICATION

EP 1 976 249 B1 (19) (11) EP 1 976 249 B1 (12) EUROPEAN PATENT SPECIFICATION (19) (11) EP 1 976 249 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 11.03.09 Bulletin 09/11 (1) Int Cl.: H04M 1/72 (06.01) G06F 9/44 (06.01) H04W

More information

(51) Int Cl.: H04M 3/42 (2006.01) H04Q 3/00 (2006.01)

(51) Int Cl.: H04M 3/42 (2006.01) H04Q 3/00 (2006.01) (19) (11) EP 1 696 646 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 07.03.12 Bulletin 12/ (1) Int Cl.: H04M 3/42 (06.01) H04Q 3/00 (06.01) (21)

More information

TEPZZ 8898 7A_T EP 2 889 827 A1 (19) (11) EP 2 889 827 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06Q 40/04 (2012.01)

TEPZZ 8898 7A_T EP 2 889 827 A1 (19) (11) EP 2 889 827 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06Q 40/04 (2012.01) (19) TEPZZ 8898 7A_T (11) EP 2 889 827 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 01.07.201 Bulletin 201/27 (1) Int Cl.: G06Q 40/04 (2012.01) (21) Application number: 14199864.1 (22)

More information

(51) Int Cl.: H04L 1/18 ( )

(51) Int Cl.: H04L 1/18 ( ) (19) Europäisches Patentamt European Patent Office Office européen des brevets (11) EP 1 161 809 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 11..06

More information

(51) Int Cl.: G06F 11/14 (2006.01)

(51) Int Cl.: G06F 11/14 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 08 414 B1 (4) Date of publication and mention of the grant of the patent: 04.03.09 Bulletin 09/ (1) Int Cl.: G06F 11/14 (06.01) (21) Application number:

More information

(51) Int Cl.: H04L 29/06 (2006.01) (56) References cited:

(51) Int Cl.: H04L 29/06 (2006.01) (56) References cited: (19) (11) EP 1 4 48 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 06.08.08 Bulletin 08/32 (21) Application number: 02776379.6 (22) Date of filing:..02

More information

(51) Int Cl.: H04L 12/24 (2006.01) G06F 9/445 (2006.01)

(51) Int Cl.: H04L 12/24 (2006.01) G06F 9/445 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 978 672 B1 (4) Date of publication and mention of the grant of the patent: 01.09. Bulletin /3 (1) Int Cl.: H04L 12/24 (06.01) G06F 9/44 (06.01) (21) Application

More information

(56) References cited:

(56) References cited: (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 371 26 B1 (4) Date of publication and mention of the grant of the patent: 21.01.09 Bulletin 09/04 (21) Application number: 02711612.8 (22) Date of filing:

More information

EP 2 365 669 A1 (19) (11) EP 2 365 669 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 14.09.2011 Bulletin 2011/37

EP 2 365 669 A1 (19) (11) EP 2 365 669 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 14.09.2011 Bulletin 2011/37 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 36 669 A1 (43) Date of publication: 14.09.11 Bulletin 11/37 (1) Int Cl.: H04L 12/8 (06.01) (21) Application number: 00243.6 (22) Date of filing:.03. (84)

More information

(51) Int Cl.: H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/06 (2006.01) (19) TEPZZ Z4Z 6B_T (11) EP 2 4 036 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.04.13 Bulletin 13/14 (21) Application number: 07822.8 (22) Date

More information

(51) Int Cl.: H04L 12/56 (2006.01) H04L 12/28 (2006.01) H04M 7/00 (2006.01)

(51) Int Cl.: H04L 12/56 (2006.01) H04L 12/28 (2006.01) H04M 7/00 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 129 0 B1 (4) Date of publication and mention of the grant of the patent: 09.04.08 Bulletin 08/1 (21) Application number: 9996836.2 (22) Date of filing:

More information

(51) Int Cl.: G06Q 20/00 (2006.01) G06F 21/00 (2006.01)

(51) Int Cl.: G06Q 20/00 (2006.01) G06F 21/00 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 24 008 B1 (4) Date of publication and mention of the grant of the patent: 29.12. Bulletin /2 (21) Application number: 00992990.2 (22) Date of filing: 31..00

More information

*EP A1* EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2002/20

*EP A1* EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2002/20 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP00120890A1* (11) EP 1 20 890 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 1.0.2002 Bulletin 2002/20 (1)

More information

TEPZZ ZZ 766A_T EP 3 002 766 A1 (19) (11) EP 3 002 766 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: H01F 5/02 (2006.01) H01F 5/04 (2006.

TEPZZ ZZ 766A_T EP 3 002 766 A1 (19) (11) EP 3 002 766 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: H01F 5/02 (2006.01) H01F 5/04 (2006. (19) TEPZZ ZZ 766A_T (11) EP 3 002 766 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 06.04.16 Bulletin 16/14 (1) Int Cl.: H01F /02 (06.01) H01F /04 (06.01) (21) Application number: 1186712.4

More information

(51) Int Cl.: H04L 29/02 (2006.01) H04L 12/801 (2013.01)

(51) Int Cl.: H04L 29/02 (2006.01) H04L 12/801 (2013.01) (19) TEPZZ 7 48ZB_T (11) EP 2 72 480 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 03.12.2014 Bulletin 2014/49 (21) Application number: 11784039.7

More information

(51) Int Cl.: G06F 17/30 (2006.01)

(51) Int Cl.: G06F 17/30 (2006.01) (19) (11) EP 1 6 23 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 2.11.09 Bulletin 09/48 (1) Int Cl.: G06F 17/ (06.01) (21) Application number: 014696.1

More information

(51) Int Cl.: B61K 9/12 (2006.01)

(51) Int Cl.: B61K 9/12 (2006.01) (19) (11) EP 2 001 722 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.12.11 Bulletin 11/1 (21) Application number: 077926.6 (22) Date of filing:

More information

(51) Int Cl.: H04B 7/26 (2006.01)

(51) Int Cl.: H04B 7/26 (2006.01) (19) TEPZZ_698Z76B_T (11) EP 1 698 076 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 02.12. Bulletin /49 (21) Application number: 037821.3 (22) Date

More information