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

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

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

Transcription

1 (19) TEPZZ 48786B_T (11) EP B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: Bulletin 16/12 (21) Application number: (22) Date of filing: (1) Int Cl.: H04L 29/06 (06.01) H04L 12/26 (06.01) H04M 3/22 (06.01) H04M 7/00 (06.01) (86) International application number: PCT/CN/07468 (87) International publication number: WO 11/08 ( Gazette 11/06) (4) VOICE LOOPBACK METHOD, GATEWAY AND VOIP NETWORK SPRACHPRÜFSCHLEIFENVERFAHREN, GATEWAY UND VOIP-NETZWERK PROCÉDÉ DE BOUCLAGE DE VOIX, PASSERELLE ET RÉSEAU VOIP EP B1 (84) Designated Contracting States: 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 () Priority: CN (43) Date of publication of application:.0.12 Bulletin 12/22 (73) Proprietor: Huawei Technologies Co., Ltd. Longgang District Shenzhen, Guangdong (CN) (72) Inventor: MENG, Bin Shenzhen (CN) (74) Representative: Kreuz, Georg Maria Huawei Technologies Duesseldorf GmbH Riesstrasse München (DE) (6) References cited: CN-A US-A US-A US-A US-A US-A US-A US-B US-B US-B CARÔT, ALEXANDER ET AL: "Audible ICMP Echo Responses for Monitoring Ultra Low Delayed Audio Streams", AES CONVENTION 124; MAY 08, AES, 60 EAST 42ND STREET, ROOM 2 NEW YORK 16-2, USA, 1 May 08 ( ), XP00836, POSTEL ISI J: "DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION INTERNET CONTROL MESSAGE PROTOCOL; rfc792.txt", , 1 September 1981 ( ), XP , ISSN: REYNOLDS R J B ET AL: "QUALITY VOIP - AN ENGINEERING CHALLENGE", BT TECHNOLOGY JOURNAL, SPRINGER, DORDRECHT, NL, vol. 19, no. 2, 1 April 01 ( ), pages 23-32, XP00348, ISSN: , DOI:.23/A: HEDAYAT BRIX NETWORKS N VENNA BRIX NETWORKS P JONES CISCO SYSTEMS K ET AL: "An Extension to the Session Description Protocol (SDP) for Media Loopback; draft-ietf-mmusic-media-loopback-.txt", AN EXTENSION TO THE SESSION DESCRIPTION PROTOCOL (SDP) FOR MEDIA LOOPBACK; DRAFT-IETF-MMUSIC-MEDIA-LOOPBACK-.T XT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- GENEVA, SWITZERLAND, vol. mmusic, no., 18 February 09 ( ), XP0067, 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, 7001 PARIS (FR)

2 1 EP B1 2 Description FIELD OF THE INVENTION [0001] The present invention relates to the field of communications technologies, and in particular, to a voice loopback method, a gateway and a loopback node in a Voice over Internet Protocol VoIP network and the VoIP network. BACKGROUND OF THE INVENTION [0002] In a time division multiplexing (Time Division Multiplexing, TDM) network, the network tracks user calls to determine switches that the user calls pass. In the TDM network, voice information is transmitted in pulsecode modulation (Pulse-code modulation, PCM) stream mode after being encoded and decoded. Service personnel determine a loopback node of a user call, log in to a platform of a switch serving as the loopback node, search for a time slot used by the call at the switch, and then set that PCM streams received at the time slot from a gateway are directly output through a local loopback. That is, the PCM streams are output through an input port where the PCM streams are received. In this way, the PCM streams sent from the gateway are directly sent back to the gateway after being transmitted to the loopback node, thereby achieving voice loopback. [0003] The disadvantage of the existing technology is as follows: A voice loopback technology in the TDM network is provided in the prior art, but in the VoIP network, no voice loopback solution is provided. [0004] CAROT, ALEXANDER ET AL: "Audible ICMP Echo Responses for Monitoring Ultra Low Delayed Audio Streams", AES CONVENTION 124; MAY 08, AES, 60 EAST 42ND STREET, ROOM 2 NEW YORK 16-2,USA, 1 May 08, discusses how to generate an audible impression of the jitter problem for each hop on a route between sender and destination. [000] US646648B1 relates to a hop by hop quality of service measurement system. [0006] Postel, J., ISI: DARPA INTERNET PROGRAM PROTOCOL SPECFICATION INTERNET CONTROL MESSAGE PROTOCOL; rfc792.txt", , discusses, in relation to ICMP messages, that data received in an echo message must be returned in the echo reply message. [0007] REYNOLDS R J B ET AL: "QUALITY VOIP - AN ENGINEERING CHALLENGE", BT TECHNOLOGY JOURNAL, SPRINGER, DORDRECHT, NL, vol. 19, no. 2, 1 April 01 pages 23-32, discusses measuring and testing of VoIP network quality. [0008] US 07/28700 A1 relates to delay profiling in a communication system. [0009] US 7848 A relates to an enhanced ISDN DP transmission device of the present invention allows for testing of ISDN-protocol communication paths using an existing DDS-protocol test infrastructure. [00] US 06/021 A1 relates to a method for performing loopback tests. [0011] US 06/1706 relates to a method to test end to end relations between gateways MGW1, MGW2 in an IP network IPNW. [0012] HEDAYAT BRIX NETWORKS N VENNA BRIX NETWORKS P JONES CISCO SYSTEMS K ET AL: "An Extension to the Session Description Protocol (SDP) for Media Loopback; draft-itself-music-media-loopback-.txt", AN EXTENSION TO THE SESSION DESCRIP- TION PROTOCOL (SDP) FOR MEDIA LOOPBACK; DRAFT-IETF-MUSIC-MEDIA LOOPBACK-.TXT, IN- TERNET ENGINEERING TASK FORCE, IETF; 18 February 09, discusses media loopback for VoIP services. SUMMARY OF THE INVENTION [0013] The present invention provides a voice loopback method, a gateway and a loopback node in a VoIP network and the VoIP network, so as to achieve voice loopback in the VoIP network. [0014] According to the first aspect of the present invention a voice loopback method in a VoIP network includes: sending (1; 3), by a gateway, an internet control message protocol,icmp, message, wherein a destination address of the ICMP message is an address of a loopback node, and the ICMP message comprises a voice packet to be detected; and receiving (2; 4), by the gateway, a response message of the ICMP message sent by the loopback node, wherein the response message comprises a loopback voice packet, and the loopback voice packet is the voice packet to be detected that is comprised in the ICMP message received by the loopback node; wherein, a length of the ICMP message is the same as a length of a voice message, the voice message is a user datagram protocol, UDP, packet, and payload of the UDP packet is a realtime transport protocol, RTP, packet that bears a user s voice packet; and a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message. [00] According to the second aspect of the present invention a gateway includes: a sending unit (01), configured to send an internet control message protocol,icmp, message, wherein a destination address of the ICMP message is an address of a loopback node, and the ICMP message 2

3 3 EP B1 4 comprises a voice packet to be detected; and a receiving unit (02), configured to receive a response message of the ICMP message sent by the loopback node, wherein the response message comprises a loopback voice packet, and the loopback voice packet is the voice packet to be detected that is comprised in the ICMP message received by the loopback node; wherein, a length of the ICMP message is the same as a length of a voice message, the voice message is a user datagram protocol, UDP, packet, and payload of the UDP packet is a realtime transport protocol, RTP, packet that bears a user s voice packet; and a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message [0016] According to the fourth aspect of the present invention a VoIP network includes a gateway and a loopback node, where the gateway is configured to send an internet control message protocol ICMP message, wherein a destination address of the ICMP message is an address of a loopback node, and the ICMP message comprises a voice packet to be detected; the loopback node is configured to receive the ICMP message, serve the voice packet to be detected that is comprised in the ICMP message as a loopback voice packet;, and send a response message of the ICMP message, wherein the response message comprises the loopback voice packet; and the gateway is further configured to receive the response message of the ICMP message sent by the loopback node; wherein, a length of the ICMP message is the same as a length of a voice message, the voice message is a user datagram protocol, UDP, packet, and payload of the UDP packet is a realtime transport protocol, RTP, packet that bears a user s voice packet; and a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message. [0017] According to the present invention, the internet control message protocol (Internet Control Message Protocol, ICMP) message sent by a gateway to a loopback node includes a voice packet to a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message. [0018] According to the present invention, the internet control message protocol (Internet Control Message Protocol, ICMP) message sent by a gateway to a loopback node includes a voice packet to be detected. Because of the ICMP message, the loopback node knows that the voice packet included in the ICMP message needs to be sent back to the gateway. Therefore, the response message that is of the ICMP message and is received by the gateway includes a loopback voice packet. In this way, voice loopback is achieved in the VoIP network. BRIEF DESCRIPTION OF THE DRAWINGS [0019] To illustrate the technical solutions according to the embodiments of the present invention more clearly, the accompanying drawings for describing the embodiments are provided below. Apparently, the accompanying drawings in the following description are only some embodiments of the present invention. FIG 1 is a flowchart of a voice loopback method in a VoIP network according to Embodiment 1 of the present invention; FIG. 2 is a flowchart of a voice loopback method in a VoIP network according to Embodiment 2 of the present invention; FIG. 3 is a schematic diagram of a voice loopback in a VoIP network according to Embodiment 2 of the present invention; FIG. 4 is a flowchart of a method for obtaining the path of a call according to an embodiment of the present invention; FIG. is a structural diagram of a gateway according to Embodiment 3 of the present invention; and FIG. 6 is a structural diagram of a loopback node according to Embodiment 4 of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS Embodiment 1 [00] Referring to FIG. 1, Embodiment 1 of the present invention provides a voice loopback method in a VoIP network, where the method includes the following steps: 1: A gateway sends an internet control message protocol ICMP message, where a destination address of the ICMP message is an address of a loopback node; the ICMP message includes a voice packet to be detected. [0021] The ICMP message is a protocol message in the prior art. After receiving the ICMP message, a destination node knows that information included in the payload of the ICMP message needs to be sent back to the gateway. The embodiment of the present invention utilizes the characteristic of an ICMP message in the prior art to achieve voice loopback. [0022] 2: The gateway receives a response message of the ICMP message sent by the loopback node, where the response message includes a loopback voice packet, and the loopback voice packet is obtained by the loopback node according to the voice packet to be detected that is included in the received ICMP message. 3

4 EP B1 6 [0023] In Embodiment 1 of the present invention, the ICMP message sent by the gateway to the loopback node includes a voice packet to be detected. Because of the ICMP message, the loopback node knows that the voice packet included in the ICMP message needs to be sent back to the gateway. Therefore, the response message that is of the ICMP message and is received by the gateway includes a loopback voice packet. In this way, voice loopback is achieved in the VoIP network. Embodiment 2 [0024] Referring to FIG. 2, Embodiment 2 of the present invention provides a voice loopback method in a VoIP network. In this embodiment, voice loopback is performed after it is determined that the quality of a call is poor. A loopback voice packet can be used to locate a fault on the path of a call. The method includes the following steps: 1: A media gateway determines that the path of a call needs to be detected. [002] In this step, when it is detected that the voice quality of a call is poor, the media gateway determines that the path of the call needs to be detected to locate a fault. [0026] 2: The media gateway searches for the path of the call in a local forwarding path information base and selects a loopback node. [0027] In this step, the media gateway searches for the path of the call in the local forwarding path information base according to an IP address pair of the call, where the forwarding path information base saves path information of multiple calls. The IP address pair includes a source gateway address and a destination gateway address of the call. [0028] The selecting of the loopback node may adopt the following method: first, selecting an intermediate node on the path of a call as the loopback node, and if subsequent detection shows that voice quality looped back from the loopback node is good, selecting a node at a position after the intermediate node on the path of the call as the loopback node; and if subsequent detection shows that voice quality looped back from the loopback node is not good, selecting a node at a position before the intermediate node on the path of the call as the loopback node, where the nodes in the embodiment of the present invention refer to routers. [0029] 3: The media gateway encodes a voice stream to be detected to obtain a voice packet to be detected and generates an ICMP message and sends the ICMP message, where a destination address of the ICMP message is an address of the loopback node, and the payload of the ICMP message is a realtime transport protocol (RealTime Transport Protocol, RTP) message that bears the voice packet to be detected. [00] The voice stream to be detected in this step may be user s voice stream of the call. [0031] It should be noted that, the length of the ICMP message needs to be the same as that of a normal voice message, and the differentiated service codepoint (Differentiated Service Codepoint, DSCP) in an IP header of the ICMP message needs to be the same as that of a voice message. The voice message refers to a voice message formed by encoding the user s voice stream by the media gateway, and is transmitted from a source gateway to a destination gateway. The voice message may be a user datagram protocol (User Datagram Protocol, UDP) packet, where the payload of the UDP packet is an RTP packet that bears a user s voice packet. [0032] The reason why it is required that the differentiated service codepoint of the ICMP message is the same as the differentiated service codepoint of the voice message lies in that nodes on a loopback path (a path between the media gateway and the loopback node) use different processing policies for received messages according to different differentiated service codepoints. For example, according to different differentiated service codepoints, different processing priorities may be adopted and different bandwidth may be allocated for the received messages. To accurately locate a fault on the path of the call, it is required that the differentiated service codepoint of the ICMP message is the same as the differentiated service codepoint of the voice message, and it is also required that the length of the ICMP message is the same as the length of the voice message. In this way, the nodes (routers) on the loopback path may use the same processing policy, the same priority, and allocate the same bandwidth for the ICMP message as those of the voice message, so as to accurately simulate the transmission environment of the voice message. The loopback path refers to the path between the media gateway and the loopback node. [0033] 4: After a node on the loopback path receives the ICMP message, the node forwards the ICMP message to a next node. When the loopback node receives the ICMP message, the loopback node does not forward the ICMP message to a next node, but sends a response message of the ICMP message from a port where the ICMP message is received, where the response message includes a voice packet in the ICMP message received locally, and the voice packet in the ICMP message received locally serves as a loopback voice packet. The response message is forwarded to the media gateway in sequence by nodes on the loopback path until the media gateway receives the response message. The response message includes the loopback voice packet. [0034] It should be noted that, an ID field in the ICMP message is used to transmit a message identification identifier. The message identification identifier is used to identify a different ICMP message. When the loopback node generates a response message of the ICMP message, the response message includes the message identification identifier in the ICMP message, so that the media gateway can identify to which ICMP message the 4

5 7 EP B1 8 response message responds according to the ID in the response message when the media gateway receives the response message from a router side. In this way, the media gateway can determine the voice packet to be detected to which the loopback voice packet included in the response message corresponds. [003] In this step, the loopback node receives an IC- MP message, and a destination address of the ICMP message is the address of the loopback node, so the loopback node generates a response message of the ICMP message and sends the response message to the media gateway, where the response message includes the voice packet in the ICMP message, and in this case, the voice packet is called a loopback voice packet. As shown in FIG. 3, assume that the source gateway and the destination gateway of the call are a media gateway 1 and a media gateway 2 respectively, the path of the call is R1 - R2 - R3 - R4, and the loopback node is a router R3. An ICMP message sent by the media gateway 1 is forwarded to the router R3 through the routers R1 and R2. Because the destination address included in the ICMP message is the address of the R3, the R3 generates a response message of the ICMP message and sends the ICMP message to the media gateway 1, where the response message includes the voice packet in the ICMP message, and in this case, the voice packet is called a loopback voice packet. The response message is forwarded to the media gateway 1 through the routers R2 and R1. [0036] In the process of transmitting the ICMP message and the response message in the loopback path, if the path between two nodes is faulty, a part of its included voice packet content may be lost. If a certain node is faulty, the voice packet content may also be influenced. For example, the voice packet content may be modified. Therefore, if a loopback path is faulty, the content of the voice packet to be detected that is included in an ICMP message sent by the media gateway may be different from the content of the loopback voice packet included in the response message received by the media gateway. [0037] : The media gateway parses the response message to obtain the loopback voice packet, decodes the loopback voice packet to obtain the voice stream, and plays the voice stream to determine whether the loopback path is faulty. [0038] Specifically, if the quality of the voice stream looped back from the loopback node is different from the quality of the voice stream to be detected, it indicates that the loopback path is faulty; otherwise, it indicates that the loopback path is not faulty. [0039] In this step, the media gateway may also compare the content of the voice packet to be detected with the content of the loopback voice packet, and determine whether the path between the media gateway and the loopback node is faulty according to a comparison result. Whether the media gateway compares the content or not does not influence the implementation of the present invention [00] The voice technical solution described in the foregoing embodiment is for easily locating a fault on the path of a call. The voice loopback technology may also be used for other purposes, which are not limited in the present invention. [0041] In Embodiment 2 of the present invention, the ICMP message sent by the media gateway to the loopback node includes the voice packet to be detected. Because of the ICMP message, the loopback node knows that the voice packet included in the ICMP message needs to be sent back to the media gateway. Therefore, the media gateway receives the response message of the ICMP message, and the response message includes the loopback voice packet. In this way, voice loopback is achieved in the VoIP network. Further, the media gateway decodes the loopback voice packet to obtain a voice stream and directly plays the voice stream to determine whether the loopback path is faulty, thereby conveniently locating the fault on the path of the call. For example, operating personnel may remotely log in to a platform of the media gateway, set a loopback node, and then make a call to the media gateway to directly listen to the played voice effect, so as to determine whether the loopback path is faulty. Further, the voice loopback method according to the embodiment of the present invention is performed on a specific call path in implementation, and does not interfere with any other calls. Further, because the maximum traffic of one voice stream is 0 pps, 0 ICMP messages need to be sent per second at the most, not resulting in performance impacts on routers that receive the ICMP messages. Further, all routers at the IP bearer plane support ICMP messages, so the voice loopback technology can be easily promoted. [0042] Referring to FIG. 4, how to obtain the path of a call is described as follows: 1: After a call is established, a media gateway obtains an IP address pair of the call, where the IP address pair includes a source gateway address and a destination gateway address. [0043] The media gateway in this step is assumed to be the source gateway of the call. [0044] 2: The source gateway judges whether a path corresponding to the IP address pair exists in a forwarding path information base according to the IP address pair of the call. If a path corresponding to the IP address pair exists in the forwarding path information base, the process is complete; if a path corresponding to the IP address pair does not exist in the forwarding path information base, 3 is performed. [004] 3: The source gateway initiates router tracking (Tracert) detection to a destination gateway according to the IP address pair. Specifically, the source gateway sends a detection message to the destination gateway, receives response messages of the detection message sent by multiple nodes, and determines whether the nodes that send the response messages are located

6 9 EP B1 in the path of the call according to the received response messages. [0046] 4: The source gateway records path information of the call in a local forwarding path information base. [0047] It should be noted that, even if the media gateway supports a dynamic routing protocol, the Tracert detection needs to be initiated. The dynamic routing protocol refers to that a network is divided into multiple regions, and information of each region is shared by members within each region. Therefore, the media gateway merely knows routing information of the region where the media gateway is located, and cannot know routing information of other regions, so the Tracert detection needs to be initiated. [0048] A media gateway may periodically initiate Tracert detection to the destination gateway of a call, so as to ensure that the detected path is the most accurate; or, the media gateway may also initiate Tracert detection after a call is established for the first time. If the path does not transfer any other calls within a preset time period, path information of the call recorded locally is deleted, and Tracert detection is initiated again for new calls; or, the media gateway may initiate Tracert detection after determining that a path of a call needs to be detected because of poor voice quality. Embodiment 3 [0049] Referring to FIG., Embodiment 3 of the present invention provides a gateway, where the gateway includes: a sending unit 01, configured to send an internet control message protocol ICMP message, where a destination address of the ICMP message is an address of a loopback node; the ICMP message includes a voice packet to be detected; and a receiving unit 02, configured to receive a response message of the ICMP message sent by the loopback node, where the response message includes a loopback voice packet; the loopback voice packet is obtained by the loopback node according to the voice packet to be detected that is included in the ICMP message. [000] The sending unit 01 and the receiving unit 02 implement relatively independent functions. The functions of the two units are implemented in sequence. The dashed line in the FIG. represents the logical connection of the two units. [001] The gateway further includes: a fault judgment unit 03, configured to determine whether the path between the gateway and the loopback node is faulty according to the loopback voice packet. Specifically, the fault determination unit 03 decodes the loopback voice packet to obtain a voice stream and play the voice stream to determine whether the loopback path is faulty; or, the fault determination unit 03 compares content of the voice packet to be detected with content of the loopback voice packet to determine whether the path between the gateway and the loopback node is faulty. [002] The length of the ICMP message is the same as that of a voice message, and the differentiated service codepoint of the ICMP message is the same as the differentiated service codepoint of the voice message. The reason why the DSCP of the ICMP message needs to be the same as the differentiated service codepoint of the voice message lies in that nodes on the loopback path (a path between the gateway and the loopback node) use different processing policies for received messages according to different differentiated service codepoints. For example, according to different differentiated service codepoints, different processing priorities may be adopted and different bandwidth may be allocated for the received messages. To accurately locate a fault on the path of the call, it is required that the differentiated service codepoint of the ICMP message is the same as the differentiated service codepoint of the voice message, and it is also required that the length of the ICMP message is the same as the length of the voice message. In this way, the nodes (routers) on the loopback path may use the same processing policy, the same priority, and allocate the same bandwidth for the ICMP message as those of the voice message, so as to accurately simulate the transmission environment of the voice message. [003] Specifically, the gateway is the source gateway of the call. In this case, the sending unit 01 is further configured to send a detection message to the destination gateway of the call when the source gateway determines that the path of the call needs to be detected; the receiving unit 02 is further configured to receive response messages of the detection message sent by intermediate nodes between the source gateway and the destination gateway; and the gateway further includes: a loopback node selection unit, configured to select a node from the intermediate nodes that send the response messages as the loopback node. [004] Or, the sending unit 01 sends a detection message to the destination gateway of the call after the call is established; the receiving unit 02 receives response messages of the detection message sent by intermediate nodes between the source gateway and the destination gateway. In this case, the gateway further includes: a path determination unit 04, configured to obtain the path of the call according to the received response messages of the detection message, and save path information of the call in a forwarding path information base, where nodes on the path of the call are nodes that send the response messages; and a loopback node selection unit 0, configured to obtain the path information of the call from the forwarding path information base and select a node on the path of the call as the loopback node. [00] In Embodiment 3 of the present invention, the ICMP message sent by the gateway to the loopback node includes a voice packet to be detected. Because of the ICMP message, the loopback node knows that the voice 6

7 11 EP B1 12 packet included in the ICMP message needs to be sent back to the gateway. Therefore, the gateway receives the response message of the ICMP message, and the response message includes the loopback voice packet. In this way, voice loopback is achieved in the VoIP network. Further, the gateway decodes the loopback voice packet to obtain a voice stream and directly plays the voice stream to determine whether the loopback path is faulty, thereby conveniently locating the fault on the path of the call. For example, operating personnel may remotely log in to a platform of a media gateway, set a loopback node, and then make a call to the media gateway to directly listen to the played voice effect, so as to determine whether the loopback path is faulty. Further, the voice loopback solution according to the embodiment of the present invention is performed on a specific call path in implementation, and does not interfere with any other calls. Further, because the maximum traffic of one voice stream is 0 pps, 0 ICMP messages need to be sent per second at the most, not resulting in performance impacts on routers that receive the ICMP messages. Further, all routers at the IP bearer plane support ICMP messages, so the voice loopback technology can be easily promoted. Embodiment 4 [006] Referring to FIG. 6, Embodiment 4 of the present invention provides a loopback node, where the loopback node includes: a receiving unit 601, configured to receive an internet control message protocol ICMP message sent by a gateway, where the ICMP message includes a voice packet to be detected; an obtaining unit 602, configured to obtain a loopback voice packet according to the voice packet to be detected that is included in the received ICMP message; and a sending unit 603, configured to send a response message of the ICMP message to the gateway, where the response message includes the loopback voice packet. [007] The ICMP message includes the voice packet to be detected and a destination address (an address of the loopback node) of the ICMP message. The loopback node determines that the voice packet included in the ICMP message needs to be sent back to the gateway locally according to the destination address. [008] The loopback node provided by Embodiment 4 of the present invention knows that the voice packet included in the ICMP message needs to be sent back to the gateway immediately after receiving the ICMP message from the gateway according to the characteristic of ICMP messages. In this way, voice loopback is achieved in the VoIP network Embodiment [009] Embodiment of the present invention provides a VoIP network, where the VoIP network includes a gateway and a loopback node. [0060] The gateway is configured to send an internet control message protocol ICMP message, where a destination address of the ICMP message is an address of the loopback node, and the ICMP message includes a voice packet to be detected. [0061] The loopback node is configured to receive the ICMP message, obtain a loopback voice packet according to the voice packet to be detected that is included in the ICMP message, and send a response message of the ICMP message, where the response message includes the loopback voice packet. [0062] The gateway is further configured to receive the response message of the ICMP message sent by the loopback node. [0063] To detect whether the path between the gateway and the loopback node is faulty, the gateway is further configured to decode the loopback voice packet to obtain a voice stream, and play the voice stream to determine whether the path between the gateway and the loopback node is faulty; or, compare content of the voice packet to be detected with content of the loopback voice packet to determine whether the path between the gateway and the loopback node is faulty. [0064] The loopback node may specifically be a router. [006] In Embodiment of the present invention, the ICMP message sent by the gateway to the loopback node includes a voice packet to be detected. Because of the ICMP message, the router serving as the loopback node knows that the voice packet included in the ICMP message needs to be sent back to the gateway. Therefore, the gateway receives the response message of the ICMP message, and the response message includes the loopback voice packet. In this way, voice loopback is achieved in the VoIP network. Further, the gateway decodes the loopback voice packet to obtain a voice stream, and plays the voice stream to determine whether the loopback path is faulty. [0066] Persons skilled in the art may understand that all or part of the steps of the method according to the embodiments of the present invention may be implemented by a program instructing relevant hardware. The program may be stored in a computer readable storage medium such as a Read-Only Memory (ROM), a magnetic disk or an optical disk. [0067] The voice loopback method, the gateway and the loopback node in a VoIP network and the network according to the embodiments of the present invention are described in detail above. The principle and implementation of the present invention are described herein through specific examples. The description about the embodiments of the present invention is merely provided for ease of understanding of the method and core ideas of the present invention. Therefore, the specification shall 7

8 13 EP B1 14 not be construed as a limit to the present invention which is defined by the subject-matter of the independent claims. Claims 1. A voice loopback method in a Voice over Internet Protocol, VoIP, network, comprising: sending (1; 3), by a gateway, an internet control message protocol,icmp, message, wherein a destination address of the ICMP message is an address of a loopback node, and the ICMP message comprises a voice packet to be detected; and receiving (2; 4), by the gateway, a response message of the ICMP message sent by the loopback node, wherein the response message comprises a loopback voice packet, and the loopback voice packet is the voice packet to be detected that is comprised in the ICMP message received by the loopback node; wherein, a length of the ICMP message is the same as a length of a voice message, the voice message is a user datagram protocol, UDP, packet, and payload of the UDP packet is a realtime transport protocol, RTP, packet that bears a user s voice packet; and a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message. 2. The method according to claim 1, wherein after the receiving the response message of the ICMP message sent by the loopback node, the method further comprises: decoding (), by the gateway, the loopback voice packet to obtain a voice stream, and playing the voice stream to determine whether a path between the gateway and the loopback node is faulty, if the quality of the voice stream looped back from the loopback node is different from the quality of the voice stream to be detected, it indicates that the loopback path is faulty; otherwise, it indicates that the loopback path is not faulty; or, comparing (), by the gateway, content of the voice packet to be detected with content of the loopback voice packet, and determining a path between the gateway and the loopback node is faulty if the content of the voice packet to be detected is different from the content of the loopback voice packet The method according to claim 1, wherein the gateway is a source gateway of a call; and before the sending, by gateway, the ICMP packet, the method further comprises: sending (3), by the source gateway, a detection message to a destination gateway of the call after determining that a path of the call needs to be detected, receiving response messages of the detection message sent by intermediate nodes between the source gateway and the destination gateway, and selecting a node from the intermediate nodes that send the response messages as the loopback node. 4. The method according to claim 1, wherein the gateway is a source gateway of a call; and before the sending, by the gateway, the ICMP packet, the method further comprises: sending (3), by the source gateway, a detection message to a destination gateway of the call, receiving response messages of the detection message sent by intermediate nodes between the source gateway and the destination gateway, obtaining a path of the call according to the received response messages, and saving (4) path information of the call in a forwarding path information base, wherein nodes on the path of the call are nodes that send the response messages; and obtaining, by the source gateway, the path information of the call from the forwarding path information base after determining that the path of the call needs to be detected, and selecting a node on the path of the call as the loopback node.. The method according to claim 1, wherein an ID field in the ICMP message is used to transmit a message identification identifier, wherein the message identification identifier is used to identify a different ICMP message, and the response message of the ICMP message generated by the loopback node comprises the message identification identifier in the ICMP message. 6. A gateway, comprising: a sending unit (01), configured to send an internet control message protocol,icmp, message, wherein a destination address of the ICMP message is an address of a loopback node, and the ICMP message comprises a voice packet to be detected; and a receiving unit (02), configured to receive a response message of the ICMP message sent by the loopback node, wherein the response 8

9 EP B1 16 message comprises a loopback voice packet, and the loopback voice packet is the voice packet to be detected that is comprised in the ICMP message received by the loopback node; wherein, a length of the ICMP message is the same as a length of a voice message, the voice message is a user datagram protocol, UDP, packet, and payload of the UDP packet is a realtime transport protocol, RTP, packet that bears a user s voice packet; and a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message. 7. The gateway according to claim 6, further comprising: sent by intermediate nodes between the source gateway and the destination gateway; and the gateway further comprises: a path determination unit (04), configured to obtain a path of the call according to the received response messages of the detection message, and save path information of the call to a forwarding path information base, wherein nodes on the path of the call are nodes that send the response messages; and a loopback node selection unit (0), configured to obtain the path information of the call from the forwarding path information base, and select a node on the path of the call as the loopback node. a fault judgment unit (03), configured to decode the loopback voice packet to obtain a voice stream, and play the voice stream to determine whether a path between the gateway and the loopback node is faulty, if the quality of the voice stream looped back from the loopback node is different from the quality of the voice stream to be detected, it indicates that the loopback path is faulty; otherwise, it indicates that the loopback path is not faulty; or, compare content of the voice packet to be detected with content of the loopback voice packet, and determine a path between the gateway and the loopback node is faulty if the content of the voice packet to be detected is different from the content of the loopback voice packet. 8. The gateway according to claim 6, wherein the gateway is a source gateway of a call; the sending unit (01) is further configured to send a detection message to a destination gateway of the call after determining that a path of the call needs to be detected; the receiving unit (02) is further configured to receive response messages of the detection message sent by intermediate nodes between the source gateway and the destination gateway; and the gateway further comprises: A Voice over Internet Protocol, VoIP, network, comprising a gateway and a loopback node, wherein the gateway is configured to send an internet control message protocol ICMP message, wherein a destination address of the ICMP message is an address of a loopback node, and the ICMP message comprises a voice packet to be detected; the loopback node is configured to receive the ICMP message, serve the voice packet to be detected that is comprised in the ICMP message as a loopback voice packet, and send a response message of the ICMP message, wherein the response message comprises the loopback voice packet; and the gateway is further configured to receive the response message of the ICMP message sent by the loopback node; wherein, a length of the ICMP message is the same as a length of a voice message, the voice message is a user datagram protocol, UDP, packet, and payload of the UDP packet is a realtime transport protocol, RTP, packet that bears a user s voice packet; and a differentiated service codepoint of the ICMP message is the same as a differentiated service codepoint of the voice message. Patentansprüche a loopback node selection unit (0), configured to select a node from the intermediate nodes that send the response messages as the loopback node. 9. The gateway according to claim 6, wherein the gateway is a source gateway of a call; the sending unit (01) is further configured to send a detection message to a destination gateway of the call; the receiving unit (02) is further configured to receive response messages of the detection message 0 1. Sprachprüfschleifenverfahren in einem "Voice over Internet Protocol"-, VoIP-, Netz, das Folgendes umfasst: Senden (1; 3), durch ein Gateway, einer Internet-Steuer-Nachricht-Protokoll-, ICMP-, Nachricht, wobei eine Zieladresse der ICMP- Nachricht eine Adresse eines Prüfschleifenknotens ist und die ICMP-Nachricht ein zu detektierendes Sprachpaket enthält; und Empfangen (2; 4), durch das Gateway, einer von dem Prüfschleifenknoten gesendeten 9

10 17 EP B1 18 Antwort-Nachricht der ICMP-Nachricht, wobei die Antwort-Nachricht ein Prüfschleifen-Sprachpaket umfasst und das Prüfschleifen-Sprachpaket das zu detektierende Sprachpaket ist, das in der ICMP-Nachricht enthalten ist, die von dem Prüfschleifenknoten empfangen wurde; wobei eine Länge der ICMP-Nachricht dieselbe ist wie die Länge einer Sprach-Nachricht, wobei die Sprach-Nachricht ein Nutzer-Datagramm- Protokoll-, UDP-, Paket ist, und eine Nutzlast des UDP-Pakets ein Echtzeit-Transport-Protokoll-, RTP-, Paket ist, das ein Sprachpaket eines Nutzers trägt; und ein differenzierter Dienst-Codepunkt der ICMP- Nachricht derselbe ist wie ein differenzierter Dienst-Codepunkt der Sprach-Nachricht. 2. Verfahren nach Anspruch 1, wobei das Verfahren nach dem Empfangen der Antwort-Nachricht der ICMP-Nachricht, die von dem Prüfschleifenknoten gesendet wurde, ferner Folgendes umfasst: Decodieren (), durch das Gateway, des Prüfschleifen-Sprachpakets, um einen Sprachstrom zu erhalten und Abspielen des Sprachstroms, um zu bestimmen, ob ein Weg zwischen dem Gateway und dem Prüfschleifenknoten fehlerhaft ist, und, falls die Qualität des Sprachstroms, der von dem Prüfschleifenknoten zurückgeschleift wird, sich von der Qualität des zu detektierenden Sprachstroms unterscheidet, zeigt es an, dass der Prüfschleifenweg fehlerhaft ist; ansonsten zeigt es an, dass der Prüfschleifenweg nicht fehlerhaft ist; oder Vergleichen (), durch das Gateway, des Inhalts des zu detektierenden Sprachpakets mit Inhalt des Prüfschleifen-Sprachpakets, und Bestimmen, dass ein Weg zwischen dem Gateway und dem Prüfschleifenknoten fehlerhaft ist, falls der Inhalt des zu detektierenden Sprachpakets sich von dem Inhalt des Prüfschleifen-Sprachpakets unterscheidet. 3. Verfahren nach Anspruch 1, wobei das Gateway ein Quell-Gateway eines Anrufs ist; und das Verfahren, vor dem Senden des ICMP-Pakets, durch das Gateway, ferner Folgendes umfasst: Senden (3), durch das Quell-Gateway, einer Detektions-Nachricht an ein Ziel-Gateway des Anrufs, nach dem Bestimmen, dass ein Weg des Anrufs detektiert werden muss, Empfangen von Antwort-Nachrichten der Detektions-Nachricht, die von Zwischenknoten zwischen dem Quell- Gateway und dem Ziel-Gateway gesendet wurden, und Auswählen eines Knotens aus den Zwischenknoten, die die Antwort-Nachrichten als der Prüfschleifenknoten senden Verfahren nach Anspruch 1, wobei das Gateway ein Quell-Gateway eines Anrufs ist; und das Verfahren, vor dem Senden des ICMP-Pakets, durch das Gateway, ferner Folgendes umfasst: Senden (3), durch das Quell-Gateway, einer Detektions-Nachricht an ein Ziel-Gateway des Anrufs, Empfangen von Antwort-Nachrichten der Detektions-Nachricht, die von Zwischenknoten zwischen dem Quell-Gateway und dem Ziel-Gateway gesendet wurden, Erhalten eines Weges des Anrufs gemäß den empfangenen Antwort-Nachrichten und Speichern (4) von Weg-Informationen des Anrufs in einer Weiterleitungsweg-Informations-Datenbank, wobei Knoten auf dem Weg des Anrufs Knoten sind, die die Antwort-Nachrichten senden; und Erhalten, durch das Quell-Gateway, der Weg- Informationen des Anrufs aus der Weiterleitungsweg-Informations-Datenbank, nach dem Bestimmen, dass der Weg des Anrufs detektiert werden muss, und Auswählen eines Knotens auf dem Weg des Anrufs als den Prüfschleifenknoten.. Verfahren nach Anspruch 1, wobei ein ID-Feld in der ICMP-Nachricht verwendet wird, eine Nachrichten-Identifikations-Kennung zu übertragen, wobei die Nachrichten-Identifikations-Kennung verwendet wird, eine andere ICMP-Nachricht zu identifizieren, und die Antwort-Nachricht der ICMP-Nachricht, die von dem Prüfschleifenknoten erzeugt wird, die Nachrichten-Identifikations-Kennung in der ICMP-Nachricht enthält. 6. Gateway, das Folgendes umfasst: eine Sendeeinheit (01), die dafür ausgelegt ist, eine Internet-Steuer-Nachricht-Protokoll-, ICMP-, Nachricht zu senden, wobei eine Zieladresse der ICMP-Nachricht eine Adresse eines Prüfschleifenknotens ist und die ICMP- Nachricht ein zu detektierendes Sprachpaket enthält; und eine Emfangseinheit (02), die dafür ausgelegt ist, eine von dem Prüfschleifenknoten gesendete Antwort-Nachricht der ICMP-Nachricht zu empfangen, wobei die Antwort-Nachricht ein Prüfschleifen-Sprachpaket umfasst und das Prüfschleifen-Sprachpaket das zu detektierende Sprachpaket ist, das in der ICMP-Nachricht enthalten ist, die von dem Prüfschleifenknoten empfangen wurde; wobei eine Länge der ICMP-Nachricht dieselbe ist wie die Länge einer Sprach-Nachricht, wobei die Sprach-Nachricht ein Nutzer-Datagramm- Protokoll-, UDP-, Paket ist, und eine Nutzlast des UDP-Pakets ein Echtzeit-Transport-Proto-

11 19 EP B1 koll-, RTP-, Paket ist, das ein Sprachpaket eines Nutzers trägt; und ein differenzierter Dienst-Codepunkt der ICMP- Nachricht derselbe ist wie ein differenzierter Dienst-Codepunkt der Sprach-Nachricht. 7. Gateway nach Anspruch 6, das ferner Folgendes umfasst: eine Fehlerbewertungseinheit (03), die dafür ausgelegt ist, das Prüfschleifen-Sprachpaket zu decodieren, um einen Sprachstrom zu erhalten und den Sprachstrom abzuspielen, um zu bestimmen, ob ein Weg zwischen dem Gateway und dem Prüfschleifenknoten fehlerhaft ist, und, falls die Qualität des Sprachstroms, der von dem Prüfschleifenknoten zurückgeschleift wird, sich von der Qualität des zu detektierenden Sprachstroms unterscheidet, zeigt es an, dass der Prüfschleifenweg fehlerhaft ist; ansonsten zeigt es an, dass der Prüfschleifenweg nicht fehlerhaft ist; oder den Inhalt des zu detektierenden Sprachpakets mit Inhalt des Prüfschleifen- Sprachpakets zu vergleichen, und zu bestimmen, dass ein Weg zwischen dem Gateway und dem Prüfschleifenknoten fehlerhaft ist, falls der Inhalt des zu detektierenden Sprachpakets sich von dem Inhalt des Prüfschleifen-Sprachpakets unterscheidet. 8. Gateway nach Anspruch 6, wobei das Gateway ein Quell-Gateway eines Anrufs ist; die Sendeeinheit (01) ferner dafür ausgelegt ist, eine Detektions-Nachricht an ein Ziel-Gateway des Anrufs zu senden, nach dem Bestimmen, dass ein Weg des Anrufs detektiert werden muss, die Empfangseinheit (02) ferner dafür ausgelegt ist, Antwort-Nachrichten der Detektions-Nachricht, die von Zwischenknoten zwischen dem Quell-Gateway und dem Ziel-Gateway gesendet wurden, zu empfangen, und das Gateway ferner Folgendes umfasst: eine Prüfschleifenknoten-Auswahleinheit (0), die dafür ausgelegt ist, einen Knoten aus den Zwischenknoten auszuwählen, die die Antwort- Nachrichten als der Prüfschleifenknoten senden. 9. Gateway nach Anspruch 6, wobei das Gateway ein Quell-Gateway eines Anrufs ist; die Sendeeinheit (01) ferner dafür ausgelegt ist, eine Detektions- Nachricht an ein Ziel-Gateway des Anrufs zu senden, die Empfangseinheit (02) ferner dafür ausgelegt ist, Antwort-Nachrichten der Detektions-Nachricht, die von Zwischenknoten zwischen dem Quell-Gateway und dem Ziel-Gateway gesendet wurden, zu empfangen; und das Gateway ferner Folgendes umfasst: eine Wegbestimmungseinheit (04), die dafür ausgelegt ist, einen Weg des Anrufs gemäß den empfangenen Antwort-Nachrichten der Detektions-Nachricht zu erhalten und Weg-Informationen des Anrufs in einer Weiterleitungsweg-Informations-Datenbank zu speichern, wobei Knoten auf dem Weg des Anrufs Knoten sind, die die Antwort-Nachrichten senden; und eine Prüfschleifenknoten-Auswahleinheit (0), die dafür ausgelegt ist, die Weg-Informationen des Anrufs aus der Weiterleitungsweg-Informations-Datenbank zu erhalten, und einen Knoten auf dem Weg des Anrufs als den Prüfschleifenknoten auszuwählen.. "Voice over Internet Protocol"-, VoIP-, Netz, das ein Gateway und einen Prüfschleifenknoten umfasst, wobei das Gateway dafür ausgelegt ist, eine Internet-Steuer-Nachricht-Protokoll-, ICMP-, Nachricht zu senden, wobei eine Zieladresse der ICMP-Nachricht eine Adresse eines Prüfschleifenknotens ist und die ICMP-Nachricht ein zu detektierendes Sprachpaket enthält; der Prüfschleifenknoten dafür ausgelegt ist, die ICMP-Nachricht zu empfangen, das zu detektierende Sprachpaket, das in der ICMP-Nachricht enthalten ist, als ein Prüfschleifen-Sprachpaket anzudienen und eine Antwort-Nachricht der ICMP-Nachricht zu senden, wobei die Antwort-Nachricht das Prüfschleifen-Sprachpaket umfasst; und das Gateway ferner dafür ausgelegt ist, die Antwort- Nachricht der von dem Prüfschleifenknoten gesendeten ICMP-Nachricht zu empfangen; wobei eine Länge der ICMP-Nachricht dieselbe ist wie die Länge einer Sprach-Nachricht, wobei die Sprach-Nachricht ein Nutzer-Datagramm-Protokoll-, UDP-, Paket ist, und eine Nutzlast des UDP- Pakets ein Echtzeit-Transport-Protokoll-, RTP-, Paket ist, das ein Sprachpaket eines Nutzers trägt; und ein differenzierter Dienst-Codepunkt der ICMP- Nachricht derselbe ist wie ein differenzierter Dienst- Codepunkt der Sprach-Nachricht. Revendications 1. Procédé de bouclage de voix dans un réseau à Protocole Voix sur Internet, VoIP, comprenant : l envoi (1; 3), par une passerelle, d un message de protocole de message de commande Internet, ICMP, dans lequel une adresse destinataire du message ICMP est une adresse d un noeud de bouclage, et le message ICMP comprend un paquet vocal à détecter ; et la réception (2; 4), par la passerelle, d un message de réponse au message ICMP envoyé 11

12 21 EP B1 22 par le noeud de bouclage, dans lequel le message de réponse comprend un paquet vocal de bouclage, et le paquet vocal de bouclage est le paquet de voix à détecter qui est compris dans le message ICMP reçu par le noeud de bouclage ; dans lequel une longueur du message ICMP est identique à une longueur d un message vocal, le message vocal étant un paquet de protocole de datagramme d utilisateur, UDP, et la charge utile du paquet UDP est un paquet de protocole de transport en temps réel, RTP, qui porte un paquet vocal d un utilisateur ; et un point de code de service différencié du message ICMP est identique à un point de code de service différencié du message vocal. 2. Procédé selon la revendication 1, comprenant en outre, après la réception du message de réponse au message ICMP envoyé par le noeud de bouclage : le décodage (), par la passerelle, du paquet vocal de bouclage pour obtenir un flux vocal, et la reproduction du flux vocal pour déterminer qu un chemin entre la passerelle et le noeud de bouclage est défaillant ou non, si la qualité du flux vocal renvoyé par le noeud de bouclage est différente de la qualité du flux vocal à détecter, cela indique que le chemin de bouclage est défaillant ; sinon, cela indique que le chemin de bouclage n est pas défaillant; ou, la comparaison (), par la passerelle, du contenu du paquet vocal à détecter au contenu du paquet vocal de bouclage, et la détermination qu un chemin entre la passerelle et le noeud de bouclage est défaillant si le contenu du paquet vocal à détecter est différent du contenu du paquet vocal de bouclage. 3. Procédé selon la revendication 1, dans lequel : la passerelle est une passerelle source d un appel ; et avant l envoi, par la passerelle, du paquet ICMP, le procédé comprend en outre : l envoi (3), par la passerelle source, d un message de détection à une passerelle destinataire de l appel après la détermination qu un chemin de l appel doit être détecté, la réception de messages de réponse au message de détection envoyés par des noeuds intermédiaires entre la passerelle source et la passerelle destinataire, et la sélection d un noeud parmi les noeuds intermédiaires qui envoient les messages de réponse comme noeud de bouclage Procédé selon la revendication 1, dans lequel: la passerelle est une passerelle source d un appel ; et avant l envoi, par la passerelle, du paquet ICMP, le procédé comprend en outre: l envoi (3), par la passerelle source, d un message de détection à une passerelle destinataire de l appel, la réception de messages de réponse au message de détection envoyés par des noeuds intermédiaires entre la passerelle source et la passerelle destinataire, l obtention d un chemin de l appel en fonction des messages de réponse reçus, et la sauvegarde (4) d informations de chemin de l appel dans une base d informations de chemin de renvoi, dans lequel les noeuds sur le chemin de l appel sont des noeuds qui envoient les messages de réponse ; et l obtention, par la passerelle source, des informations de chemin de l appel à partir de la base d informations de chemin de renvoi après la détermination que le chemin de l appel doit être détecté, et la sélection d un noeud sur le chemin de l appel comme noeud de bouclage.. Procédé selon la revendication 1, dans lequel un champ ID dans le message ICMP est utilisé pour transmettre un identifiant d identification de message, l identifiant d identification de message servant à identifier un différent message ICMP, et dans lequel le message de réponse au message ICMP généré par le noeud de bouclage comprend l identifiant d identification de message dans le message ICMP. 6. Passerelle, comprenant: une unité d envoi (01), configurée pour envoyer un message de protocole de message de commande Internet, ICMP, dans laquelle une adresse destinataire du message ICMP est une adresse d un noeud de bouclage, et le message ICMP comprend un paquet vocal à détecter ; et une unité de réception (02), configurée pour recevoir un message de réponse du message ICMP envoyé par le noeud de bouclage, dans laquelle le message de réponse comprend un paquet vocal de bouclage, et le paquet vocal de bouclage est le paquet de voix à détecter qui est compris dans le message ICMP reçu par le noeud de bouclage ; dans lequel une longueur du message ICMP est identique à une longueur d un message vocal, le message vocal étant un paquet de protocole de datagramme d utilisateur, UDP, et la charge 12

13 23 EP B1 24 utile du paquet UDP est un paquet de protocole de transport en temps réel, RTP, qui porte un paquet vocal d un utilisateur ; et un point de code de service différencié du message ICMP est identique à un point de code de service différencié du message vocal. 7. Passerelle selon la revendication 6, comprenant en outre: une unité de jugement de défaillance (03), configurée pour décoder le paquet vocal de bouclage pour obtenir un flux vocal, et reproduire le flux vocal pour déterminer qu un chemin entre la passerelle et le noeud de bouclage est défaillant ou non, si la qualité du flux vocal renvoyé par le noeud de bouclage est différente de la qualité du flux vocal à détecter, cela indique que le chemin de bouclage est défaillant ; sinon, cela indique que le chemin de bouclage n est pas défaillant ; ou comparer le contenu du paquet vocal à détecter au contenu du paquet vocal de bouclage, et déterminer qu un chemin entre la passerelle et le noeud de bouclage est défaillant si le contenu du paquet vocal à détecter est différent du contenu du paquet vocal de bouclage. 8. Passerelle selon la revendication 6, dans laquelle la passerelle est une passerelle source d un appel ; l unité d envoi (01) est configurée en outre pour envoyer un message de détection à une passerelle destinataire de l appel après la détermination qu un chemin de l appel doit être détecté ; l unité de réception (02) est configurée en outre pour recevoir des messages de réponse au message de détection envoyés par des noeuds intermédiaires entre la passerelle source et la passerelle destinataire ; et la passerelle comprend en outre : une unité de sélection de noeud de bouclage (0), configurée pour sélectionner un noeud parmi les noeuds intermédiaires qui envoient les messages de réponse comme noeud de bouclage une unité de détermination de chemin (04), configurée pour obtenir un chemin de l appel en fonction des messages de réponse au message de détection reçus, et sauvegarder des informations de chemin de l appel dans une base d informations de chemin de renvoi, dans laquelle les noeuds sur le chemin de l appel sont des noeuds qui envoient les messages de réponse ; et une unité de sélection de noeud de bouclage (0), configurée pour obtenir les informations de chemin depuis la base d informations de chemin de renvoi, et sélectionner un noeud sur le chemin de l appel comme noeud de bouclage.. Réseau à protocole de voix sur Internet, VoIP, comprenant une passerelle et un noeud de bouclage, dans lequel la passerelle est configurée pour envoyer un message de protocole de message de commande Internet, ICMP, dans lequel une adresse destinataire du message ICMP est une adresse d un noeud de bouclage, et le message ICMP comprend un paquet vocal à détecter ; le noeud de bouclage est configuré pour recevoir le message ICMP, desservir le paquet vocal à détecter qui est compris dans le message ICMP comme paquet vocal de bouclage, et envoyer un message de réponse au message ICMP, le message de réponse comprenant le paquet vocal de bouclage ; et la passerelle est configurée en outre pour recevoir le message de réponse du message ICMP envoyé par le noeud de bouclage ; dans lequel une longueur du message ICMP est identique à une longueur d un message vocal, le message vocal étant un paquet de protocole de datagramme d utilisateur, UDP, et la charge utile du paquet UDP est un paquet de protocole de transport en temps réel, RTP, qui porte un paquet vocal d un utilisateur ; et un point de code de service différencié du message ICMP est identique à un point de code de service différencié du message vocal. 9. Passerelle selon la revendication 6, dans laquelle la passerelle est une passerelle source d un appel ; l unité d envoi (01) est configurée en outre pour envoyer un message de détection à une passerelle destinataire de l appel ; l unité de réception (02) est configurée en outre pour recevoir des messages de réponse au message de détection envoyés par des noeuds intermédiaires entre la passerelle source et la passerelle destinataire ; et la passerelle comprenant en outre : 0 13

14 EP B1 14

15 EP B1

16 EP B1 16

17 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 B1 [000] US A1 [0008] US 7848 A [0009] US A1 [00] US A [0011] Non-patent literature cited in the description CAROT, ALEXANDER et al. Audible ICMP Echo Responses for Monitoring Ultra Low Delayed Audio Streams. AES CONVENTION 124; MAY 08, AES, 60 EAST 42ND STREET, ROOM 2 NEW YORK 16-2,USA, 01 May 08 [0004] POSTEL, J. ISI: DARPA INTERNET PROGRAM PROTOCOL SPECFICATION INTERNET CON- TROL MESSAGE PROTOCOL. ISI: DARPA INTER- NET PROGRAM PROTOCOL SPECFICATION IN- TERNET CONTROL MESSAGE PROTOCOL, 01 September 1981 [0006] QUALITY VOIP - AN ENGINEERING CHALLENGE. REYNOLDS R J B et al. BT TECHNOLOGY JOUR- NAL. SPRINGER, 01 April 01, vol. 19, [0007] An Extension to the Session Description Protocol (SDP) for Media Loopback; draft-itself-music-media-loopback-.txt. AN EXTENSION TO THE SES- SION DESCRIPTION PROTOCOL (SDP) FOR ME- DIA LOOPBACK; DRAFT-IETF-MUSIC-MEDIA LOOPBACK-.TXT, INTERNET ENGINEERING TASK FORCE. IETF, 18 February 09 [0012] 17

(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

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

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

(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.: 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

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) 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

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

*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

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/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

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

(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.: 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

(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

TEPZZ 974846A_T EP 2 974 846 A1 (19) (11) EP 2 974 846 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 974846A_T EP 2 974 846 A1 (19) (11) EP 2 974 846 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 974846A_T (11) EP 2 974 846 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (43) Date of publication: 20.01.2016 Bulletin 2016/03 (21) Application number: 14874187.9

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

(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

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

(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

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

(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

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

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 74Z9 ZA_T EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 74Z9 ZA_T EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 74Z9 ZA_T (11) EP 2 740 930 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (43) Date of publication: 11.06.2014 Bulletin 2014/24 (21) Application number: 12819896.7

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

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

(51) Int Cl.: H04L 29/06 (2006.01) H04L 12/24 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 231 74 B1 (4) Date of publication and mention of the grant of the patent: 16.03.11 Bulletin 11/11 (1) Int Cl.: H04L 29/06 (06.01) H04L 12/24 (06.01) (21)

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

TEPZZ 96 A_T EP 2 961 111 A1 (19) (11) EP 2 961 111 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 96 A_T EP 2 961 111 A1 (19) (11) EP 2 961 111 A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 96 A_T (11) EP 2 961 111 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 13(4) EPC (43) Date of publication:.12.1 Bulletin 1/3 (21) Application number: 147426.7 (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

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

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

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

(51) Int Cl.: H04L 29/12 (2006.01) H04L 12/56 (2006.01) (19) (11) EP 1 993 266 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 04.07.12 Bulletin 12/27 (1) Int Cl.: H04L 29/12 (06.01) H04L 12/6 (06.01) (21)

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

(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 94Z968A_T EP 2 940 968 A1 (19) (11) EP 2 940 968 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: H04L 29/08 (2006.01)

TEPZZ 94Z968A_T EP 2 940 968 A1 (19) (11) EP 2 940 968 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: H04L 29/08 (2006.01) (19) TEPZZ 94Z968A_T (11) EP 2 940 968 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 04.11.20 Bulletin 20/4 (1) Int Cl.: H04L 29/08 (2006.01) (21) Application number: 1430649.7 (22) Date

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.: 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 ZZ7_4 A_T EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ ZZ7_4 A_T EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ ZZ7_4 A_T (11) EP 3 007 142 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 153(4) EPC (43) Date of publication: 13.04.2016 Bulletin 2016/15 (21) Application number: 13886431.9

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

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

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

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

TEPZZ_98 47ZB_T EP 1 982 470 B1 (19) (11) EP 1 982 470 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ_98 47ZB_T EP 1 982 470 B1 (19) (11) EP 1 982 470 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ_98 47ZB_T (11) EP 1 982 470 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.04.14 Bulletin 14/18 (21) Application number: 077168.0 (22)

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

(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 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

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

*EP A1* EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2005/48 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001600303A1* (11) EP 1 600 303 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 30.11.2005 Bulletin 2005/48

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

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

TEPZZ 5699Z7B_T EP 2 569 907 B1 (19) (11) EP 2 569 907 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04L 12/803 (2013.01)

TEPZZ 5699Z7B_T EP 2 569 907 B1 (19) (11) EP 2 569 907 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04L 12/803 (2013.01) (19) TEPZZ 699Z7B_T (11) EP 2 69 907 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 06.0.1 Bulletin 1/19 (21) Application number: 117816.1 (22) Date

More information

TEPZZ_946 57B_T EP 1 946 257 B1 (19) (11) EP 1 946 257 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ_946 57B_T EP 1 946 257 B1 (19) (11) EP 1 946 257 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ_946 7B_T (11) EP 1 946 27 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.01.14 Bulletin 14/03 (21) Application number: 0682689.0 (22) Date

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

(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

(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

*EP001520563A1* EP 1 520 563 A1 (19) (11) EP 1 520 563 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 06.04.2005 Bulletin 2005/14

*EP001520563A1* EP 1 520 563 A1 (19) (11) EP 1 520 563 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 06.04.2005 Bulletin 2005/14 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001520563A1* (11) EP 1 520 563 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 06.04.2005 Bulletin 2005/14

More information

TEPZZ ZZ5974A_T EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ ZZ5974A_T EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ ZZ974A_T (11) EP 3 00 974 A1 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 13(4) EPC (43) Date of publication: 13.04.16 Bulletin 16/1 (21) Application number: 1480372.8

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

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 69 _ZA T EP 2 692 310 A2 (19) (11) EP 2 692 310 A2. (12) EUROPEAN PATENT APPLICATION published in accordance with Art.

TEPZZ 69 _ZA T EP 2 692 310 A2 (19) (11) EP 2 692 310 A2. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. (19) TEPZZ 69 _ZA T (11) EP 2 692 3 A2 (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 13(4) EPC (43) Date of publication: 0.02.14 Bulletin 14/06 (21) Application number: 1276632.0 (22)

More information

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

*EP A1* EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2002/45 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001255200A1* (11) EP 1 255 200 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 06.11.2002 Bulletin 2002/45

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/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

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

EP A1 (19) (11) EP A1. (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 158(3) EPC (19) (12) EUROPEAN PATENT APPLICATION published in accordance with Art. 8(3) EPC (11) EP 1 962 14 A1 (43) Date of publication: 27.08.08 Bulletin 08/3 (21) Application number: 06828244.1 (22) Date of filing:

More information

EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2009/15

EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2009/15 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 044 969 A1 (43) Date of publication: 08.04.2009 Bulletin 2009/15 (51) Int Cl.: A61M 16/04 (2006.01) (21) Application number: 08150076.1 (22) Date of filing:

More information

(51) Int Cl.: A61N 5/06 ( ) A61H 39/06 ( )

(51) Int Cl.: A61N 5/06 ( ) A61H 39/06 ( ) (19) TEPZZ 6 _47B_T (11) EP 2 63 147 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 31.08.2016 Bulletin 2016/3 (21) Application number: 11848121.7

More information

(51) Int Cl.: H04N 1/00 (2006.01) H04N 1/32 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04N 1/00 (2006.01) H04N 1/32 (2006.01) H04L 29/06 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 472 859 B1 (45) Date of publication and mention of the grant of the patent: 23.01.08 Bulletin 08/04 (21) Application number: 03700738.2 (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

(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

EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2006/52

EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2006/52 (19) Europäisches Patentamt European Patent Office Office européen des brevets (12) EUROPEAN PATENT APPLICATION (11) EP 1 736 761 A1 (43) Date of publication: 27.12.2006 Bulletin 2006/52 (51) Int Cl.:

More information

TEPZZ 4_888 B_T EP 2 418 883 B1 (19) (11) EP 2 418 883 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04W 12/00 (2009.01)

TEPZZ 4_888 B_T EP 2 418 883 B1 (19) (11) EP 2 418 883 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04W 12/00 (2009.01) (19) TEPZZ 4_888 B_T (11) EP 2 418 883 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 23.04.14 Bulletin 14/17 (21) Application number: 09842887.3

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

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

TEPZZ 5 6 ZB_T EP 2 536 230 B1 (19) (11) EP 2 536 230 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04W 68/00 (2009.01)

TEPZZ 5 6 ZB_T EP 2 536 230 B1 (19) (11) EP 2 536 230 B1 (12) EUROPEAN PATENT SPECIFICATION. (51) Int Cl.: H04W 68/00 (2009.01) (19) TEPZZ 6 ZB_T (11) EP 2 36 2 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.04. Bulletin /16 (21) Application number: 11741879.8 (22) Date of

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

(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 A2 (19) (11) EP A2 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2009/47

EP A2 (19) (11) EP A2 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2009/47 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 120 010 A2 (43) Date of publication: 18.11.2009 Bulletin 2009/47 (51) Int Cl.: G01C 19/38 (2006.01) F41G 3/04 (2006.01) (21) Application number: 09158994.5

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

EP 1 675 420 A1 (19) (11) EP 1 675 420 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 28.06.2006 Bulletin 2006/26

EP 1 675 420 A1 (19) (11) EP 1 675 420 A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: 28.06.2006 Bulletin 2006/26 (19) Europäisches Patentamt European Patent Office Office européen des brevets (12) EUROPEAN PATENT APPLICATION (11) EP 1 67 4 A1 (43) Date of publication: 28.06.06 Bulletin 06/26 (1) Int Cl.: H04Q 7/34

More information

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

(51) Int Cl.: H04L 12/26 (2006.01) (19) (11) EP 2 169 879 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.09.11 Bulletin 11/38 (1) Int Cl.: H04L 12/26 (06.01) (21) Application number:

More information

EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2011/41

EP A1 (19) (11) EP A1 (12) EUROPEAN PATENT APPLICATION. (43) Date of publication: Bulletin 2011/41 (19) (12) EUROPEAN PATENT APPLICATION (11) EP 2 375 644 A1 (43) Date of publication: 12.10.2011 Bulletin 2011/41 (51) Int Cl.: H04L 12/46 (2006.01) H04L 29/12 (2006.01) (21) Application number: 10186014.6

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

TEPZZ Z_6 9 A_T EP 3 016 293 A1 (19) (11) EP 3 016 293 A1 (12) EUROPEAN PATENT APPLICATION

TEPZZ Z_6 9 A_T EP 3 016 293 A1 (19) (11) EP 3 016 293 A1 (12) EUROPEAN PATENT APPLICATION (19) TEPZZ Z_6 9 A_T (11) EP 3 016 293 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication: 04.0.2016 Bulletin 2016/18 (21) Application number: 1192431.3 (1) Int Cl.: H04B 1/3816 (201.01) H04B

More information

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

(51) Int Cl.: H04M 3/51 (2006.01) (19) TEPZZ_976 B_T (11) EP 1 976 2 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 18.03.1 Bulletin 1/12 (1) Int Cl.: H04M 3/1 (06.01) (21) Application

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. 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_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.: 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 88_898A_T EP 2 881 898 A1 (19) (11) EP 2 881 898 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06N 5/04 (2006.01) G06F 17/30 (2006.

TEPZZ 88_898A_T EP 2 881 898 A1 (19) (11) EP 2 881 898 A1 (12) EUROPEAN PATENT APPLICATION. (51) Int Cl.: G06N 5/04 (2006.01) G06F 17/30 (2006. (19) TEPZZ 88_898A_T (11) EP 2 881 898 A1 (12) EUROPEAN PATENT APPLICATION (43) Date of publication:.06. Bulletin /24 (1) Int Cl.: G06N /04 (06.01) G06F 17/ (06.01) (21) Application number: 136680.3 (22)

More information