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

Size: px
Start display at page:

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

Transcription

1 (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP B1 (4) Date of publication and mention of the grant of the patent: Bulletin 12/11 (21) Application number: (22) Date of filing: (1) Int Cl.: H04W 4/14 (09.01) (86) International application number: PCT/CN08/07112 (87) International publication number: WO 09/0171 ( Gazette 09/06) (4) METHOD, APPARATUS AND SYSTEM FOR REPORTING TRANSMISSION STATE VERFAHREN, VORRICHTUNG UND SYSTEM ZUM MELDEN DES ÜBERTRAGUNGSZUSTANDS PROCÉDÉ, APPAREIL ET SYSTÈME POUR RAPPORTER L ÉTAT DE TRANSMISSION (84) Designated Contracting States: AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR () Priority: CN (43) Date of publication of application: Bulletin /19 (73) Proprietor: Huawei Technologies Co., Ltd. Longgang District, Shenzhen Guangdong (CN) (72) Inventors: LI, Xinjie Guangdong (CN) ZHU, Xiaoying Guangdong (CN) (74) Representative: Pfenning, Meinig & Partner GbR Patent- und Rechtsanwälte Theresienhöhe München (DE) (6) References cited: EP-A WO-A1-04/04963 CN-A US-A US-A US-A SMPP DEVELOPERS FORUM: "Short Message Peer to Peer Protocol Specification v3.4" , vol. 3.4, 12 October 1999 ( ), pages 1-169, XP "ISDN user part supplementary services; Q.7 (12/99)" ITU-T STANDARD IN FORCE (I), INTERNATIONAL TELECOMMUNICATION UNION, GENEVA, CH, no. Q.7 (12/99), 1 December 1999 ( ), XP01743 EP B1 Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). Printed by Jouve, 7001 PARIS (FR)

2 1 EP B1 2 Description FIELD OF THE INVENTION the short message ID in the received status report. SUMMARY [0001] The present invention relates to the mobile communication field, and more specifically to a method, an apparatus, and a system for sending a status report from a Short Message Service Center (SMSC) to a Service Provider (SP). BACKGROUND [0002] There are some prior arts relating to the communication between a short message sender and Short Message Service Center. U.S, patent No relates to a method of handling SMS messages in a radio telecommunications network when an originating mobile station-based Short Message Entity (MS-SME) sends a SMS origination message while operating in a first Mobile Switching Center (MSC) and then moves into a second MSC before the MS-SME receives a SMS acknowledgement message. European patent publication No A1 is directed to a method for routing short messages using a router in a mobile telecommunications network. The method comprises: receiving a short message from a short message element; attempting to deliver a short message without passing through a store and forward function; and if said attempted delivery fails, directing said short message using a mobile originated procedure to a short message service center having a store and forward function. A publication entitled "Short Message Peer to Peer Protocol Specification v3.4" by SMPP Developers Forum relates to a technical standard, in particular to short message peer to peer protocol specification version 3,4. [0003] According to statistics, in a short message network architecture, about 60% of the short messages can be delivered successfully at one time, and more and more short messages need to be stored and forwarded by the SMSC. This causes that the forwarding efficiency is decreased gradually. Based on this situation, a Short Message Service Router (SMS Router) is introduced for a first time delivery. The short messages are submitted to the SMS Router by the SP. The SMS Router delivers the short messages to cell phones. For the short messages that are not delivered successfully for the first time, which are about % of the submitted short messages, the SMS Router may forward these short messages to the SMSC for delivering again. [0004] In practicing the present invention, it is discovered that the short message ID received when the SP submits the short message is assigned by the SMS Router. The short message ID in a status report sent to the SP, however, is assigned by the SMSC after the SMS Router forwards the submitted short message and the SMSC resends the short message. Therefore, the SP may discover that the short message ID received when the SP submits the short message does not match with [000] A method, an apparatus, and a system for sending a status report are provided in order to address the ID matching issue occurred when the SMSC sends a status report via the SMS Router. [0006] A method for sending a status report is provided according to an embodiment of the present invention. The method includes: receiving, by a short message service router, SMS router, a short message sent by a sender; assigning a first ID to the short message and incorporating the first ID in the short message, wherein the first ID is used by the SMS router for identifying the short message; sending, by the SMS router, to the sender an acknowledgement whose message ID field carries the first ID; sending (S11), by the SMS router, the short message carrying the first ID to a short message service center; returning (S1), by the short message service center, to the SMS router, a first status report carrying a second ID and the first ID, wherein the second ID is assigned by the short message service center for identifying the short message; extracting (S21), by the SMS router, the first ID in the first status report; generating (S21) a second status report by replacing the second ID with the first ID in the first status report; and sending (S31), by the SMS Router, the second status report to the sender. [0007] Another method for sending a status report is provided according to an embodiment of the present invention. The method includes: receiving, by a short message service router, SMS router, a short message sent by a sender; assigning, by the SMS router, a first ID to the short message and incorporating the first ID in the short message, wherein the first ID is used by the SMS router for identifying the short message; sending (S11), by the SMS router, the short message to a short message service center; receiving, by the SMS router, an acknowledgement carrying a second ID from the short message service center, wherein the second ID is assigned by the short message service center for identifying the short message; storing (S13), by the SMS router, the relationship between the first ID and the second ID; receiving (S23), by the SMS router, a first status report carrying the second ID; 2

3 3 EP B1 4 retrieving (S2), by the SMS router, the relationship between the first ID and the second ID; replacing (S2), by the SMS router, the second ID in a message ID field in the first status report with the first ID to generate a second status report; and sending the second status report to the sender. [0008] Yet another method for sending a status report is provided according to an embodiment of the present invention. The method includes: receiving (S11), by a short message service center, a short message carrying a first ID, wherein the first ID is used by a short message service router for identifying the short message; assigning, by the short message service center, a second ID to the short message, wherein the second ID is used by the short message service center for identifying the short message; storing (S13), by the short message service center, the relationship between the first ID and the second ID; generating (S23), by the short message service center, a first status report carrying the second ID; retrieving (24), by the short message service center, the relationship between the first ID and the second ID; replacing (S24), by the short message service center, the second ID in a message ID field in the first status report with the first ID to generate a second status report; sending the second status report to the sender. [0009] An SMS Router is provided according to an embodiment of the present invention. The SMS Router includes: an assigning unit (1), configured to assign a first ID to a short message sent by a sender; a delivering unit (2), configured to incorporate the first ID in the short message and send the short message; a replacing unit (3), configured to replace a second ID in a first status report with the first ID to generate a second status report, wherein the first status report is sent from a short message service center, the first status report containing the second ID assigned by the short message service center, the second ID being used by the short message service center for identifying the short message; and a transmitting unit (4), configured to send the second status report to the sender. [00] Another SMS Router is provided according to an embodiment of the present invention. The SMS Router includes: an assigning unit (01), configured to assign a first ID to a short message sent by a sender, wherein the first ID is carried in the short message; a delivering unit (02), configured to send the short message; a receiving unit (03), configured to receive an acknowledgement carrying a second ID and a first status report from a short message service center, wherein the second ID being used by the short message service center for identifying the short message; a storing unit (04), configured to store the relationship between the first ID and the second ID of the short message; a replacing unit (0), configured to replace the second ID in the first status report with the first ID to generate a second status report according to the relationship between the first ID and the second ID of the short message; and a transmitting unit (06), configured to send the second status report to the sender. [0011] A short message service center is provided according to an embodiment of the present invention. The short message service center includes: an assigning unit (601, 701), configured to assign a second ID to a short message sent by a sender, the short message carrying a first ID; a delivering unit (602,702), configured to send the short message to a receiver; a storing unit (603,703), configured to store the relationship between the first ID and the second ID of the short message; a first status subunit (7041), configured to generate a first status report based on a response message returned from the receiver; and a replacement subunit (7042), configured to replace the second ID in the first generated status report with the first ID to generate the second status report; and a transmitting unit (60,70), configured to send the second status report. [0012] According to the above technical solutions, for the short message which has not been delivered successfully by the SMS Router for the first time, the SMS Router may replace the second ID in the first status report with the first ID based on the relationship between the first ID and the second ID to obtain a second status report and finally send the second status report to a sender. Thus, the ID in the second status report is the first ID which is assigned by the SMS Router. The short message ID received when the sender initially submits the short message to the SMS Router is also assigned by the SMS Router. Therefore, the ID matching issue occurred when the SMSC sends the status report via the SMS Router can be addressed. Consequently, the sender may perform a series of operations such as charging, service accounting and service upgrade based on the second 3

4 EP B1 6 status report. BRIEF DESCRIPTION OF THE DRAWINGS [0013] FIG. 1 is a flowchart of a method for sending a status report according to an embodiment of the present invention; FIG. 2 is a flowchart of a method for sending a status report according to another embodiment of the present invention; FIG. 3 is a flowchart of a method for sending a status report according to another embodiment of the present invention; FIG. 4 is a block diagram of an SMS Router according to an embodiment of the present invention; FIG. is a block diagram of an SMS Router according to another embodiment of the present invention; FIG. 6 is a block diagram of an SMSC according to an embodiment of the present invention; and FIG. 7 is a block diagram of an SMSC according to another embodiment of the present invention. DETAILED DESCRIPTION [0014] Detailed description is provided for the present invention in connection with the annexed drawings and specific embodiments. In the below embodiments, a first ID indicates an ID of a short message assigned by the SMS Router. A second ID indicates an ID of the same short message assigned by the SMSC. The SMS Router needs to send a second status report whose message ID field carries the first ID. [001] The relationship between the first ID and the second ID may be conveyed to the SMS Router by incorporating the first ID and the second ID in a first status report sent from the SMSC to the SMS Router. A message ID field in the first status report carries the second ID assigned by the SMSC. An extension filed in the first status report carries the first ID. The SMS Router may extract the first ID from the extension field in the first status report and replace the second ID in the message ID field in the first status report with the first ID to generate a second status report. [0016] The relationship between the first ID and the second ID may be stored in the SMS Router. When the SMS Router receives the first status report from the SM- SC, the message ID field in the first status report carries the second ID assigned by the SMSC. The SMS Router then replaces the second ID carried in the message ID field in the first status report with the first ID based on the relationship between the first ID and the second ID. The second status report is thereby obtained. [0017] The relationship between the first ID and the second ID may also be stored in the SMSC. When the SMSC receives a response message from the receiver, the message ID in the response message carries the second ID. The SMSC may directly generate a second status report based on the relationship between the first ID and the second ID. In the second status report, the message ID field carries the first ID. Alternatively, a first status report may be generated first. In the first status report, the message ID field carries the second ID. Then, a second status report is generated by replacing the second ID carried in the message ID field with the first ID based on the relationship between the first ID and the second ID. [0018] Thus, the first ID carried in the message ID field in the second status report is assigned by the SMS Router. The short message ID received when the sender initially submits the short message to the SMS Router is also assigned by the SMS Router. Therefore, the ID matching issue occurred when the SMSC sends the status report via the SMS Router can be addressed. Consequently, the sender may perform a series of operations such as charging, service accounting and service upgrade based on the second status report. [0019] Referring to FIG. 1, a method for sending a status report according to an embodiment of the present invention includes the following steps. [00] The SMS Router receives a short message from a sender. The SMS Router assigns a first ID to the short message. [0021] The SMS Router sends the sender an acknowledgement whose message ID field carries the first ID. [0022] In this embodiment, the sender may be the SP. [0023] S11: The SMS Router forwards a short message to the SMSC. The short message carries a first ID. [0024] Here, an extension field may be used for carrying the first ID in the short message. For example, an extension TLV field may be used for carrying the first ID. [002] The SMSC assigns a second ID to the short message. [0026] After the SMSC receives the short message carrying the first ID, the SMSC assigns the second ID to the short message and stores the first ID. The first ID can be stored by storing the extension field as a property of the short message. [0027] S12: The SMSC sends a forward acknowledgement to the SMS Router. [0028] Here, a message ID field in the forward acknowledgement carries the second ID. S13: The SM- SC delivers the short message to a receiver. [0029] In the present embodiment, the receiver may be a mobile terminal, a stationary terminal, a multimedia terminal, etc. The mobile terminal may be a cell phone, a PDA, etc. [00] S14: The receiver sends a short message acknowledgement to the SMSC. [0031] S1: The SMSC sends a first status report to the SMS Router. The first status report carries the first ID and the second ID. [0032] Here, the message ID field in the first status report carries the second ID assigned by the SMSC, while the extension field in the first status report carries the first 4

5 7 EP B1 8 ID. The message ID field is a field for identifying the ID of the message. [0033] S16: The SMS Router sends a status report acknowledgement to the SMSC. [0034] S21: The SMS Router extracts the first ID in the extension field in the first status report and replaces the second ID in the message ID field in the first status report with the first ID to generate a second status report. [003] S31: The SMS Router sends a second status report to the sender. [0036] S32: The sender sends a status report acknowledgement to the SMS Router. [0037] In the present embodiment, the first status report carries the relationship between the first ID and the second ID. Thus, the storage function does not need to be provided for the SMS Router which saves the storage cost for the SMS Router. [0038] Referring to FIG. 2, a method for sending a status report according to an embodiment of the present invention includes the following steps. [0039] The SMS Router assigns a first ID to a short message. [00] The first ID is used by the SMS Router for identifying the short message. [0041] S11: The SMS Router forwards the short message to the SMSC. The SMS Router stores the first ID. [0042] The SMSC assigns a second ID to the short message. [0043] The second ID is used by the SMSC for identifying the short message. [0044] S12: The SMSC sends a forward acknowledgement to the SMS Router. The forward acknowledgement carries the second ID. [004] Here, an extension field may be used for carrying the second ID in the forward acknowledgement. For example, an extension TLV field in the forward acknowledgement may be used for carrying the second ID. [0046] S13: The SMS Router stores the relationship between the first ID and the second ID. S21: The SM- SC delivers the short message to a receiver. [0047] S22: The receiver sends a short message acknowledgement to the SMSC. [0048] S23: The SMSC sends a first status report to the SMS Router. [0049] Here, the message ID field in the first status report carries the second ID. [000] S24: The SMS Router sends a status report acknowledgement to the SMSC. [001] S2: The SMS Router retrieves the relationship between the first ID and the second ID and replaces the second ID in the message ID field in the first status report with the first ID to generate a second status report. [002] S31: The SMS Router sends the second status report to the sender. [003] S32: The sender sends a status report acknowledgement to the SMS Router. [004] In the present embodiment, the SMS Router is provided with a caching function for storing the relationship between the first ID and the second ID. [00] In the present embodiment, since the SMS Router needs to store the relationship between the first ID and the second ID for a mass of short messages, in practice, the present embodiment may also include a step for deleting the relationship between the first ID and the second ID. As a result, the cache shortage problem that is caused by the case the SMS Router has to constantly store the relationship can be addressed. [006] If the SMS Router still has not received the first status report from the SMSC when the short message times out, the relationship between the first ID and the second ID may be deleted. [007] Alternatively, the relationship between the first ID and the second ID may be deleted after the SMS Router replaces, based on the relationship, the first ID in the message ID field in the first status report generated by the SMSC with the second ID to generate a second status report. [008] Referring to FIG. 3, a method for sending a status report according to an embodiment of the present invention includes the following steps. [009] The SMS Router assigns a first ID to a short message. [0060] The first ID is used by the SMS Router for identifying the short message. [0061] S11: The SMS Router forwards the short message to the SMSC. The short message carries the first ID. [0062] Here, an extension field may be used for carrying the first ID in the short message. For example, an extension TLV field may be used for carrying the first ID. [0063] The SMSC assigns a second ID to the short message. [0064] The second ID is used by the SMSC for identifying the short message. [006] S12: The SMSC sends a forward acknowledgement to the SMS Router. [0066] S13: The SMSC stores the relationship between the first ID and the second ID. S21: The SMSC delivers the short message to a receiver. [0067] S22: The receiver sends a short message acknowledgement to the SMSC. [0068] S23: The SMSC generates a first status report. The message ID field in the first status report carries the second ID. [0069] S24: The SMSC retrieves the relationship between the first ID and the second ID and replaces the second ID in the message ID field in the first status report with the first ID to generate a second status report. [0070] In S23 and S24, the second status report can also be generated directly based on the relationship between the first ID and the second ID after the SMSC receives the short message acknowledgement. The message ID field in the second status report carries the first ID. [0071] S2: The SMSC sends a second status re-

6 9 EP B1 port to the SMS Router. [0072] S26: The SMS Router sends a status report acknowledgement to the SMSC. [0073] S31: The SMS Router sends the second status report to the SP. [0074] S32: The SP sends a status report acknowledgement to the SMS Router. [007] In the present embodiment, the relationship between the first ID and the second ID is stored in the SM- SC. The SMS Router does not have to be provided with the caching function, which saves the storage cost for the SMS Router. Moreover, after the SMSC replaces the ID in the first status report, the SMS Router may transparently sends the second status report to the SP. [0076] Referring to FIG. 4, an SMS Router includes: an assigning unit 1, configured to assign a first ID to a short message sent by a sender; a delivering unit 2, configured to incorporate the first ID in the short message and send the short message; a replacing unit 3, configured to replace a second ID in a first status report with the first ID to generate a second status report; a transmitting unit 4, configured to send the second status report to the sender. [0077] In this embodiment, the SMS Router receives the first status report generated by the SMSC, replaces the second ID in the first status report with the first ID based on the relationship between the first ID and the second ID to generate the second status report, and sends the second status report to the SP. Thus, the message ID received when the SP submits the short message to the SMS Router is the first ID. If the SMS Router fails to deliver the short message for the first time, the SMS Router may submit the short message to the SMSC for delivering again. Ultimately, the short message ID in the second status report returned to the SP is also the first ID. Thus, the ID matching issue occurred when the SMSC sends the status report to the SP via the SMS Router can be addressed. The SP may perform a series of operations such as charging, service accounting and service upgrade based on the second status report. [0078] Referring to FIG., an SMS Router includes: an assigning unit 01, configured to assign a first ID to a short message sent by a sender; a delivering unit 02, configured to send a short message; a receiving unit 03, configured to receive an acknowledgement carrying a second ID and a first status report; a storing unit 04, configured to store the relationship between the first ID and the second ID for the short message; a replacing unit 0, configured to replace the second ID in the first status report with the first ID to generate a second status report; a transmitting unit 06, configured to send the second status report to the sender. [0079] In the present embodiment, the storing unit for storing the relationship between the first ID and the second ID of the short message is provided in the SMS Router, which means that storage function is added to the SMS Router. [0080] Referring to FIG. 6, an SMSC includes: an assigning unit 601, configured to assign a second ID to a short message carrying a first ID; a delivering unit 602, configured to send the short message to a receiver; a storing unit 603, configured to store the relationship between the first ID and the second ID of the short message; a reporting unit 604, configured to generate a second status report according to a response message returned from the receiver and the relationship. a transmitting unit 60, configured to send the second status report. [0081] A storing unit for storing the relationship between the first ID and the second ID of the short message is provided in the SMSC. The SMSC generates the second status report based on the response message and the relationship. Thus, the SMS Router only needs to perform the transparent transmission and does not need to extent the storage function, which saves the storage cost for the SMS Router. Consequently, the issue that the ID does not match when the SMSC sends the status report to the SP via the SMS Router can be addressed. The SP may perform a series of operations such as charging, service accounting and service upgrade based on the second status report. [0082] The second status report may be directly generated by the SMSC with the first ID as its ID, or may be generated by generating a first status report with the second ID first and then replacing the ID in the first status report with the first ID. [0083] Referring to FIG. 7, an SMSC includes a assigning unit 701, a delivering unit 702, a storing unit 703, a reporting unit 704 and a transmitting unit 70. The reporting unit 704 includes a first status subunit 7041 and a replacement subunit [0084] The assigning unit 701 is configured to assign a second ID to a short message carrying a first ID. [008] The delivering unit 702 is configured to deliver the short message to a receiver. [0086] The storing unit 703 is configured to store the relationship between the first ID and the second ID for the short message. [0087] The first status subunit 7041 is configured to generate a first status report based on a response message returned by the receiver. [0088] The replacement subunit 7042 is configured to 6

7 11 EP B1 12 replace the second ID in the first generated status report with the first ID to generate a second status report. [0089] The transmitting unit 70 is configured to send the second status report. [0090] A storing unit for storing the relationship between the first ID and the second ID for the short message is provided in the SMSC. The SMSC replaces the ID in the first status report and generates a second status report. Thus, the SMS Router only needs to perform the transparent transmission and does not need to extent the storage function, which saves the storage cost for the SMS Router. Consequently, the issue that the ID does not match when the SMSC sends the status report to the SP via the SMS Router can be addressed. The SP may perform a series of operations such as charging, service accounting and service upgrade based on the second status report. [0091] A system for sending a status report is also provided according to an embodiment of the present invention. The system includes: an SMSC, configured to assign a second ID to a short message, deliver the short message to a receiver and generate a first status report, wherein the message ID field in the first status report is the second ID; an SMS Router, configured to assign a first ID to the short message, replace the second ID in the first status report with the first ID based on the relationship between the first ID and the second ID to generate a second status report and send the second status report to a sender. [0092] It is appreciated by those skilled in the art that the entire or partial steps described in the above embodiments can be implemented by associated hardware when instructed by program. The program may be stored in a computer readable storage medium. For instance, the program, when executed, performs the following steps: receiving a short message sent by the sender, assigning a first ID to the short message; incorporating the first ID in the short message and sending the short message, receiving a first status report carrying a second ID and the first ID, generating a second status report based on the first ID, and sending the second status report to the sender. The storage medium may be ROM/RAM, magnetic disc, optic disc, etc. [0093] The foregoing embodiments are merely exemplary embodiments of the present invention. It should be noted that several modifications and variations can be made by those skilled in the art without departing from the principle of the present invention. These modifications and variations shall be construed as falling within the scope of the present invention, as defined by the claims Claims 1. A method for sending a status report, comprising: receiving, by a short message service router, SMS router, a short message sent by a sender; assigning a first ID to the short message and incorporating the first ID in the short message, wherein the first ID is used by the SMS router for identifying the short message; sending, by the SMS router, to the sender an acknowledgement whose message ID field carries the first ID; sending (S11), by the SMS router, the short message carrying the first ID to a short message service center; returning (S1), by the short message service center, to the SMS router, a first status report carrying a second ID and the first ID, wherein the second ID is assigned by the short message service center for identifying the short message; extracting (S21), by the SMS router, the first ID in the first status report; generating (S21) a second status report by replacing the second ID with the first ID in the first status report; and sending (S 31), by the SMS Router, the second status report to the sender. 2. The method of claim 1, further comprising: storing, by the short message service center, the first ID after receiving the short message; assigning the second ID to the short message, and carrying the second ID in a message ID field of the first status report; delivering the short message to the receiver. 3. A method for sending a status report, comprising: receiving, by a short message service router, SMS router, a short message sent by a sender; assigning, by the SMS router, a first ID to the short message and incorporating the first ID in the short message, wherein the first ID is used by the SMS router for identifying the short message; sending (S11), by the SMS router, the short message to a short message service center; receiving, by the SMS router, an acknowledgement carrying a second ID from the short message service center, wherein the second ID is assigned by the short message service center for identifying the short message; storing (S13), by the SMS router, the relationship between the first ID and the second ID, receiving (S23), by the SMS router, a first status report carrying the second ID; 7

8 13 EP B1 14 retrieving (S2), by the SMS router, the relationship between the first ID and the second ID; replacing (S2), by the SMS router, the second ID in a message ID field in the first status report with the first ID to generate a second status report; and sending the second status report to the sender. 4. The method of claim 3, further comprising: deleting the relationship between the first ID and the second ID if the first status report has not been received when the short message times out; or, deleting the relationship between the first ID and the second ID after the second status report is generated.. A method for sending a status report, comprising: receiving (S11), by a short message service center, a short message carrying a first ID, wherein the first ID is used by a short message service router for identifying the short message; Assigning, by the short message service center, a second ID to the short message, wherein the second ID is used by the short message service center for identifying the short message; storing (S13), by the short message service center, the relationship between the first ID and the second ID; generating (S23), by the short message service center, a first status report carrying the second ID; retrieving (S24), by the short message service center, the relationship between the first ID and the second ID; replacing (S24), by the short message service center, the second ID in a message ID field in the first status report with the first ID to generate a second status report; sending the second status report to the sender. 6. The method of claim, wherein sending the second status report to the sender comprises: transparently sending, by a short message service center, the second status report to the sender via a short message service router. 7. A short message service router, comprising: an assigning unit (1), configured to assign a first ID to a short message sent by a sender; a delivering unit (2), configured to incorporate the first ID in the short message and send the short message; a replacing unit (3), configured to replace a second ID in a first status report with the first ID to generate a second status report, wherein the first status report is sent from a short message service center, the first status report containing the second ID assigned by the short message service center, the second ID being used by the short message service center for identifying the short message; and a transmitting unit (4), configured to send the second status report to the sender. 8. A short message service router, comprising: an assigning unit (01), configured to assign a first ID to a short message sent by a sender, wherein the first ID is carried in the short message; a delivering unit (02), configured to send the short message; a receiving unit (03), configured to receive an acknowledgement carrying a second ID and a first status report from a short message service center, wherein the second ID being used by the short message service center for identifying the short message; a storing unit (04), configured to store the relationship between the first ID and the second ID of the short message; a replacing unit (0), configured to replace the second ID in the first status report with the first ID to generate a second status report according to the relationship between the first ID and the second ID of the short message; and a transmitting unit (06), configured to send the second status report to the sender. 9. A short message service center, comprising: an assigning unit (601, 701), configured to assign a second ID to a short message sent by a sender, the short message carrying a first ID; a delivering unit (602,702), configured to send the short message to a receiver; a storing unit (603,703), configured to store the relationship between the first ID and the second ID of the short message; a first status subunit (7041), configured to generate a first status report based on a response message returned from the receiver; and a replacement subunit (7042), configured to replace the second ID in the first generated status report with the first ID to generate the second status report; and a transmitting unit (60,70), configured to send the second status report. 8

9 1 EP B1 16 Patentansprüche 1. Verfahren zum Senden einer Statusmeldung, das Folgendes umfasst: Empfangen einer durch einen Sender gesendeten Kurznachricht durch einen Kurznachrichtendienst-Router, SMS-Router; Zuweisen einer ersten ID zu der Kurznachricht und Aufnehmen der ersten ID in die Kurznachricht, wobei die erste ID durch den SMS-Router verwendet wird, um die Kurznachricht zu identifizieren; Senden einer Quittung, deren Nachrichten-ID- Feld die erste ID führt, durch den SMS-Router an den Sender; Senden (S11) der Kurznachricht, die die erste ID führt, durch den SMS-Router an ein Kurznachrichtendienst-Zentrum; Zurückschicken (S 1) einer ersten Statusmeldung, die eine zweite ID und die erste ID führt, durch das Kurznachrichtendienst-Zentrum an den SMS-Router, wobei die zweite ID durch das Kurznachrichtendienst-Zentrum zum Identifizieren der Kurznachricht zugewiesen wird; Extrahieren (S21) der ersten ID in der ersten Statusmeldung durch den SMS-Router; Erzeugen (S21) einer zweiten Statusmeldung durch Ersetzen der zweiten ID durch die erste ID in der ersten Statusmeldung; und Senden (S31) der zweiten Statusmeldung durch den SMS-Router an den Sender. 2. Verfahren nach Anspruch 1, das ferner Folgendes umfasst: Speichern, durch das Kurznachrichtendienst- Zentrum, der ersten ID nach dem Empfangen der Kurznachricht; Zuweisen der zweiten ID zu der Kurznachricht und Führen der zweiten ID in einem Nachrichten-ID-Feld der ersten Statusmeldung; Zustellen der Kurznachricht an den Empfänger. 3. Verfahren zum Senden einer Statusmeldung, das Folgendes umfasst: Empfangen einer durch einen Sender gesendeten Kurznachricht durch einen Kurznachrichtendienst-Router, SMS-Router; Zuweisen einer ersten ID zu der Kurznachricht und Aufnehmen der ersten ID in die Kurznachricht durch den SMS-Router, wobei die erste ID durch den SMS-Router verwendet wird, um die Kurznachricht zu identifizieren; Senden (S11) der Kurznachricht durch den SMS-Router an das Kurznachrichtendienst Zentrum; Empfangen einer Quittung, die eine zweite ID führt, von dem Kurznachrichtendienst-Zentrum durch den SMS-Router, wobei die zweite ID durch das Kurznachrichtendienst-Zentrum zum Identifizieren der Kurznachricht zugewiesen wird; Speichern (S13) der Beziehung zwischen der ersten ID und der zweiten ID durch den SMS- Router; Empfangen (S23) einer ersten Statusmeldung, die die zweite ID führt, durch den SMS- Router; Wiedergewinnen (S2) der Beziehung zwischen der ersten ID und der zweiten ID durch den SMS-Router; Ersetzen (2) der zweiten ID in einem Nachrichten-ID-Feld in der ersten Statusmeldung durch die erste ID, um eine zweite Statusmeldung zu erzeugen, durch den SMS-Router; und Senden der zweiten Statusmeldung an den Sender. 4. Verfahren nach Anspruch 3, das ferner Folgendes umfasst: Löschen der Beziehung zwischen der ersten ID und der zweiten ID, falls die erste Statusmeldung nicht empfangen worden ist, wenn die Kurznachricht abläuft; oder Löschen der Beziehung zwischen der ersten ID und der zweiten ID, nachdem die zweite Statusmeldung erzeugt worden ist.. Verfahren zum Senden einer Statusmeldung, das Folgendes umfasst: Empfangen (S11) einer Kurznachricht, die eine erste ID führt, durch ein Kurznachrichtendienst-Zentrum, wobei die erste ID durch einen Kurznachrichtendienst-Router zum Identifizieren der Kurznachricht verwendet wird; Zuweisen einer zweiten ID zu der Kurznachricht durch das Kurznachrichtendienst-Zentrum, wobei die zweite ID durch das Kurznachrichtendienst-Zentrum zum Identifizieren der Kurznachricht verwendet wird; Speichern (S13) der Beziehung zwischen der ersten ID und der zweiten ID durch das Kurznachrichtendienst-Zentrum; Erzeugen (S23) einer ersten Statusmeldung, die die zweite ID führt, durch das Kurznachrichtendienst-Zentrum; Wiedergewinnen (S24) der Beziehung zwischen der ersten ID und der zweiten ID durch das Kurznachrichtendienst-Zentrum; Ersetzen (S24) der zweiten ID in einem Nach- 9

10 17 EP B1 18 richten-id-feld in der ersten Statusmeldung durch die erste ID, um eine zweite Statusmeldung zu erzeugen, durch das Kurznachrichtendienst-Zentrum; und Senden der zweiten Statusmeldung an den Sender. 6. Verfahren nach Anspruch, wobei das Senden der zweiten Statusmeldung an den Sender Folgendes umfasst: der zweiten ID der Kurznachricht zu speichern; eine Ersetzungseinheit (0), die konfiguriert ist, um in Übereinstimmung mit der Beziehung zwischen der ersten ID und der zweiten ID der Kurznachricht die zweite ID in der ersten Statusmeldung durch die erste ID zu ersetzen, um eine zweite Statusmeldung zu erzeugen; und eine Übertragungseinheit (06), die konfiguriert ist, um die zweite Statusmeldung an den Sender zu senden. transparentes Senden der zweiten Statusmeldung über einen Kurznachrichtendienst-Router durch ein Kurznachrichtendienst-Zentrum an den Sender. 7. Kurznachrichtendienst-Router, der Folgendes umfasst: eine Zuweisungseinheit (1), die konfiguriert ist, um einer durch einen Sender gesendeten Kurznachricht eine erste ID zuzuweisen; eine Zustelleinheit (2), die konfiguriert ist, um die erste ID in die Kurznachricht aufzunehmen und die Kurznachricht zu senden; eine Ersetzungseinheit (3), die konfiguriert ist, um eine zweite ID in einer ersten Statusmeldung durch die erste ID zu ersetzen, um eine zweite Statusmeldung zu erzeugen, wobei die erste Statusmeldung von einem Kurznachrichtendienst-Zentrum gesendet wird, die erste Statusmeldung die zweite ID enthält, die durch das Kurznachrichtendienst-Zentrum zugewiesen wird, und die zweite ID durch das Kurznachrichtendienst-Zentrum zum Identifizieren der Kurznachricht verwendet wird; und eine Übertragungseinheit (4), die konfiguriert ist, um die zweite Statusmeldung an den Sender zu senden. 8. Kurznachrichtendienst-Router, der Folgendes umfasst: Kurznachrichtendienst-Zentrum, das Folgendes umfasst: eine Zuweisungseinheit (601, 701), die konfiguriert ist, um eine zweite ID einer durch einen Sender gesendeten Kurznachricht zuzuweisen, wobei die Kurznachricht eine erste ID führt; eine Zustelleinheit (602, 702), die konfiguriert ist, um die Kurznachricht an einen Empfänger zu senden; eine Speichereinheit (603, 703), die konfiguriert ist, um die Beziehung zwischen der ersten ID und der zweiten ID der Kurznachricht zu speichern; eine erste Statusuntereinheit (7041), die konfiguriert ist, um basierend auf einer von dem Empfänger zurückgeschickten Antwortnachricht eine erste Statusmeldung zu erzeugen; eine Ersetzungsuntereinheit (7042), die konfiguriert ist, um die zweite ID in der ersten erzeugten Statusmeldung durch die erste ID zu ersetzen, um die zweite Statusmeldung zu erzeugen; und eine Übertragungseinheit (60, 70), die konfiguriert ist, um die zweite Statusmeldung zu senden. Revendications 1. Procédé d envoi d un rapport d état, comprenant : eine Zuweisungseinheit (01), die konfiguriert ist, um einer durch einen Sender gesendeten Kurznachricht eine erste ID zuzuweisen, wobei die erste ID in der Kurznachricht geführt wird; eine Zustelleinheit (02), die konfiguriert ist, um die Kurznachricht zu senden; eine Empfangseinheit (03), die konfiguriert ist, um eine Quittung, die eine zweite ID führt, und eine erste Statusmeldung von einem Kurznachrichtendienst-Zentrum zu empfangen, wobei die zweite ID durch das Kurznachrichtendienst- Zentrum zum Identifizieren der Kurznachricht verwendet wird; eine Speichereinheit (04), die konfiguriert ist, um die Beziehung zwischen der ersten ID und 4 0 la réception, par un routeur de services de messages courts, routeur SMS, d un message court envoyé par un expéditeur ; l attribution d une première ID au message court et l incorporation de la première ID dans le message court, la première ID étant utilisée par le routeur SMS pour identifier le message court ; l envoi, par le routeur SMS, à l expéditeur d un acquittement dont le champ d ID de message achemine la première ID ; l envoi (S11), par le routeur SMS, du message court acheminant la première ID à un centre de services de messages courts ; le renvoi (S1), par le centre de services de messages courts, au routeur SMS, d un premier

11 19 EP B1 rapport d état acheminant une seconde ID et la première ID, la seconde ID étant attribuée par le centre de services de messages courts pour identifier le message court ; l extraction (S21), par le routeur SMS, de la première ID dans le premier rapport d état ; la génération (S21) d un second rapport d état en remplaçant la seconde ID par la première ID dans le premier rapport d état ; et l envoi (S31), par le routeur SMS, du second rapport d état à l expéditeur. 2. Procédé selon la revendication 1, comprenant en outre : la mémorisation, par le centre de services de messages courts, de la première ID après avoir reçu le message court ; l attribution de la seconde ID au message court, et l acheminement de la seconde ID dans un champ d ID de message du premier rapport d état ; la délivrance du message court au récepteur. 3. Procédé d envoi d un rapport d état, comprenant : la réception, par un routeur de services de messages courts, routeur SMS, d un message court envoyé par un expéditeur ; l attribution, par le routeur SMS, d une première ID au message court et l incorporation de la première ID dans le message court, la première ID étant utilisée par le routeur SMS pour identifier le message court ; l envoi (S11), par le routeur SMS, du message court à un centre de services de messages courts ; la réception, par le routeur SMS, d un acquittement acheminant une seconde ID depuis le centre de services de messages courts, la seconde ID étant attribuée par le centre de services de messages courts pour identifier le message court ; la mémorisation (S13), par le routeur SMS, de la relation entre la première ID et la seconde ID, la réception (S23), par le routeur SMS, d un premier rapport d état acheminant la seconde ID ; l extraction (S2), par le routeur SMS, de la relation entre la première ID et la seconde ID ; le remplacement (S2), par le routeur SMS, de la seconde ID dans un champ d ID de message dans le premier rapport d état par la première ID afin de générer un second rapport d état ; et l envoi du second rapport d état à l expéditeur Procédé selon la revendication 3, comprenant en outre : la suppression de la relation entre la première ID et la seconde ID si le premier rapport d état n a pas été reçu quand le message court arrive à expiration ; ou la suppression de la relation entre la première ID et la seconde ID après que le second rapport d état est généré.. Procédé d envoi d un rapport d état, comprenant : la réception (S11), par un centre de services de messages courts, d un message court acheminant une première ID, la première ID étant utilisée par un routeur de services de messages courts pour identifier le message court ; l attribution, par le centre de services de messages courts, d une seconde ID au message court, la seconde ID étant utilisée par le centre de services de messages courts pour identifier le message court ; la mémorisation (S13), par le centre de services de messages courts, de la relation entre la première ID et la seconde ID ; la génération (S23), par le centre de services de messages courts, d un premier rapport d état acheminant la seconde ID ; l extraction (S24), par le centre de services de messages courts, de la relation entre la première ID et la seconde ID ; le remplacement (S24), par le centre de services de messages courts, de la seconde ID dans un champ d ID de message dans le premier rapport d état par la première ID afin de générer un second rapport d état ; l envoi du second rapport d état à l expéditeur. 6. Procédé selon la revendication, dans lequel l envoi du second rapport d état à l expéditeur comprend : l envoi par transparence, par un centre de services de messages courts, du second rapport d état à l expéditeur par l intermédiaire d un routeur de services de messages courts. 7. Routeur de services de messages courts, comprenant : une unité d attribution (1), configurée pour attribuer une première ID à un message court envoyé par un expéditeur ; une unité de délivrance (2), configurée pour incorporer la première ID dans le message court et envoyer le message court ; une unité de remplacement (3), configurée 11

12 21 EP B1 22 pour remplacer une seconde ID dans un premier rapport d état par la première ID afin de générer un second rapport d état, le premier rapport d état étant envoyé par un centre de services de messages courts, le premier rapport d état contenant la seconde ID attribuée par le centre de services de messages courts, la seconde ID étant utilisée par le centre de services de messages courts pour identifier le message court ; et une unité de transmission (4), configurée pour envoyer le second rapport d état à l expéditeur. destinataire ; et une sous-unité de remplacement (7042), configurée pour remplacer la seconde ID dans le premier rapport d état généré par la première ID afin de générer le second rapport d état ; et une unité de transmission (60, 70), configurée pour envoyer le second rapport d état. 8. Routeur de services de messages courts, comprenant : 1 une unité d attribution (01), configurée pour attribuer une première ID à un message court envoyé par un expéditeur, la première ID étant acheminée dans le message court ; une unité de délivrance (02), configurée pour envoyer le message court ; une unité de réception (03), configurée pour recevoir un acquittement acheminant une seconde ID et un premier rapport d état depuis un centre de services de messages courts, la seconde ID étant utilisée par le centre de services de messages courts pour identifier le message court ; une unité de mémorisation (04), configurée pour mémoriser la relation entre la première ID et la seconde ID du message court ; une unité de remplacement (0), configurée pour remplacer la seconde ID dans le premier rapport d état par la première ID afin de générer un second rapport d état, en fonction de la relation entre la première ID et la seconde ID du message court ; et une unité de transmission (06), configurée pour envoyer le second rapport d état à l expéditeur Centre de services de messages courts, comprenant : une unité d attribution (601, 701), configurée pour attribuer une seconde ID à un message court envoyé par un expéditeur, le message court acheminant une première ID ; une unité de délivrance (602, 702), configurée pour envoyer le message court à un destinataire ; une unité de mémorisation (603, 703), configurée pour mémoriser la relation entre la première ID et la seconde ID du message court ; une première sous-unité d état (7041), configurée pour générer un premier rapport d état en fonction du message de réponse renvoyé par le

13 EP B1 13

14 EP B1 14

15 EP B1 1

16 EP B1 16

17 EP B1 17

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

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

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

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

More information

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

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

More information

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

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

More information

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

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

More information

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

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

More information

(51) Int Cl.: 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 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

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

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

More information

(51) Int Cl.: 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

(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

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.: H04N 7/16 (2011.01)

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

More information

(51) Int Cl.: 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) 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

The Advantialer and Its Advantages

The Advantialer and Its Advantages (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

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) H04L 12/26 (2006.01) H04M 3/22 (2006.01) H04M 7/00 (2006.01)

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

More information

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

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

More information

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

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

More information

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

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

More information

(51) Int Cl.: 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.: 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 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.: 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

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

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

More information

(51) Int Cl.: 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 29/08 (2006.01) H04L 29/06 (2006.01)

(51) Int Cl.: H04L 29/08 (2006.01) H04L 29/06 (2006.01) (19) TEPZZ_897 6B_T (11) EP 1 897 336 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.08.1 Bulletin 1/33 (21) Application number: 06779738.1 (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

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

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

More information

(51) Int Cl.: H04L 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.: 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

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

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.: 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 9/32 (2006.01)

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

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.: H04M 3/50 (2006.01)

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

More information

(51) Int Cl.: 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

(51) Int Cl. 7 : H04B 7/185, H04B 1/40. (56) References cited: WO-A-00/03494

(51) Int Cl. 7 : H04B 7/185, H04B 1/40. (56) References cited: WO-A-00/03494 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP001363412B1* (11) EP 1 363 412 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

(51) Int Cl. 7 : G06F 11/22

(51) Int Cl. 7 : G06F 11/22 (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP00084463B1* (11) EP 0 844 63 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

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

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

More information

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

(51) Int Cl.: H04L 12/66 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 73 43 B1 (4) Date of publication and mention of the grant of the patent: 18.01.12 Bulletin 12/03 (21) Application number: 02792. (22) Date of filing: 26.12.02

More information

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

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

More information

(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

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

(51) Int Cl.: H04L 29/06 (2006.01) H04L 12/22 (2006.01) (19) (11) EP 0 998 091 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 31.01.07 Bulletin 07/0 (1) Int Cl.: H04L 29/06 (06.01) H04L 12/22 (06.01) (21)

More information

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

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

More information

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

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

More information

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

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

More information

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

EURÓPAI SZABADALOM SZÖVEGÉNEK FORDÍTÁSA. (51) Int. Cl.: H04L 12/24 (2006.01) *HU000011740T2* HU000011740T2 (19) HU (11) Lajstromszám: E 011 740 (13) T2 MAGYARORSZÁG Szellemi Tulajdon Nemzeti Hivatala EURÓPAI SZABADALOM SZÖVEGÉNEK FORDÍTÁSA (21) Magyar ügyszám: E 09 157877 (22)

More information

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

(51) Int Cl.: G06F 9/46 (2006.01) H04L 12/56 (2006.01) (19) (11) EP 1 611 23 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 21.0.08 Bulletin 08/21 (21) Application number: 0471948.2 (22) Date of filing:

More information

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

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

More information

(51) Int Cl.: H04L 29/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.: H04W 8/16 (2009.01) H04L 29/12 (2006.01) H04W 8/18 (2009.01)

(51) Int Cl.: H04W 8/16 (2009.01) H04L 29/12 (2006.01) H04W 8/18 (2009.01) (19) TEPZZ 474_77B_T (11) EP 2 474 177 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 0.11.14 Bulletin 14/4 (21) Application number: 747648.3 (22)

More information

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

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

More information

TEPZZ 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.: 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.: G06F 17/00 (2006.01) G06F 11/20 (2006.01)

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

More information

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

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

More information

(51) Int Cl.: 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

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 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.: H04L 12/10 (2006.01) H04L 12/40 (2006.01)

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

More information

(51) Int Cl.: H04L 12/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

(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 8_B_T (11) EP 2 3 8 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.04.14 Bulletin 14/16 (1) Int Cl.: G06F 11/14 (06.01) G06F 17/ (06.01)

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

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 858 ZB_T EP 2 858 320 B1 (19) (11) EP 2 858 320 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ 858 ZB_T EP 2 858 320 B1 (19) (11) EP 2 858 320 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ 88 ZB_T (11) EP 2 88 3 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 06.04.16 Bulletin 16/14 (21) Application number: 1287929.9 (22) Date

More information

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

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

More information

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

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

More information

(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

(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

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

(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.: G06F 17/30 (2006.01)

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

More information

(51) Int Cl.: 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 9/32 (2006.01) H04B 7/00 (2006.01) A61N 1/37 (2006.01)

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

More information

(51) Int Cl.: G06Q 10/00 (2006.01)

(51) Int Cl.: G06Q 10/00 (2006.01) (19) (11) EP 1 69 282 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 2.03.09 Bulletin 09/13 (21) Application number: 048.1 (22) Date of filing: 29.11.04

More information

(51) Int Cl.: H04Q 7/22 (2006.01) (56) References cited:

(51) Int Cl.: H04Q 7/22 (2006.01) (56) References cited: (19) Europäisches Patentamt European Patent Office Office européen des brevets (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 2 414 B1 (4) Date of publication and mention of the grant of the patent:.08.06

More information

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

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

More information

(51) Int Cl.: H04N 5/225 (2006.01)

(51) Int Cl.: H04N 5/225 (2006.01) (19) TEPZZ_94 66_B_T (11) EP 1 942 661 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 17.09.2014 Bulletin 2014/38 (1) Int Cl.: H04N /22 (2006.01)

More information

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

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

More information

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

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

More information

(51) Int Cl.: B43M 3/04 (2006.01)

(51) Int Cl.: B43M 3/04 (2006.01) (19) (11) EP 0 899 129 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 13.08.08 Bulletin 08/33 (1) Int Cl.: B43M 3/04 (06.01) (21) Application number:

More information

(51) Int Cl.: H01M 8/04 (2006.01)

(51) Int Cl.: H01M 8/04 (2006.01) (19) (11) EP 1 791 20 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 12.09.2012 Bulletin 2012/37 (1) Int Cl.: H01M 8/04 (2006.01) (21) Application

More information

(56) References cited:

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

More information

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

(51) Int Cl.: H04L 12/56 (2006.01) H04L 12/24 (2006.01) H04L 29/06 (2006.01) H04L 29/08 (2006.01) (19) (11) EP 2 184 89 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: 16.03.11 Bulletin 11/11 (1) Int Cl.: H04L 12/6 (06.01) H04L 12/24 (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.: H04L 12/58 (2006.01) H04L 29/06 (2006.01)

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

More information

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

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

More information

TEPZZ _ 6594B_T EP 2 136 594 B1 (19) (11) EP 2 136 594 B1 (12) EUROPEAN PATENT SPECIFICATION

TEPZZ _ 6594B_T EP 2 136 594 B1 (19) (11) EP 2 136 594 B1 (12) EUROPEAN PATENT SPECIFICATION (19) TEPZZ _ 694B_T (11) EP 2 136 94 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent:.11.13 Bulletin 13/47 (1) Int Cl.: H04W 2/ (09.01) H04W 36/ (09.01)

More information

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

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

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

*EP000961991B1* EP 0 961 991 B1 (19) (11) EP 0 961 991 B1 (12) EUROPEAN PATENT SPECIFICATION

*EP000961991B1* EP 0 961 991 B1 (19) (11) EP 0 961 991 B1 (12) EUROPEAN PATENT SPECIFICATION (19) Europäisches Patentamt European Patent Office Office européen des brevets *EP000961991B1* (11) EP 0 961 991 B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of

More information

(51) Int Cl.: G08G 1/14 (2006.01) G07B 15/02 (2006.01) G10L 15/28 (2006.01)

(51) Int Cl.: G08G 1/14 (2006.01) G07B 15/02 (2006.01) G10L 15/28 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 862 986 B1 (4) Date of publication and mention of the grant of the patent: 14.07. Bulletin /28 (1) Int Cl.: G08G 1/14 (06.01) G07B 1/02 (06.01) GL 1/28

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

(51) Int Cl.: G06F 1/00 (2006.01) H04L 9/32 (2006.01) H04Q 7/32 (2006.01) G07F 7/10 (2006.01)

(51) Int Cl.: G06F 1/00 (2006.01) H04L 9/32 (2006.01) H04Q 7/32 (2006.01) G07F 7/10 (2006.01) (19) (12) EUROPEAN PATENT SPECIFICATION (11) EP 1 14 096 B1 (4) Date of publication and mention of the grant of the patent: 17.01.07 Bulletin 07/03 (21) Application number: 99963714.3 (22) Date of filing:

More information