Method for transmitting short messages over the internet

• US 20040029598A1
• Filed: 08/08/2003
• Published: 02/12/2004
• Est. Priority Date: 10/20/2000
• Status: Active Grant

• Current Assignee: Azzurro Investment AG
• Original Assignee: Azzurro Investment AG
• Inventors: Guggisberg, Karl
• Granted Patent: US 7,243,152 B2
• Time in Patent Office: Days
• US Class Current: 455/466
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 61/2596 Translation of addresses of the same type other than IP, e.g. translation from MAC to MAC addresses
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 92/24 between backbone network devices

Abstract

To provide a method for transmitting short messages (SMS) between computers (3, 8, 9) in the Internet (4), wherein the short message (SMS) is converted into a data format comprised of a header part (10) and a useful part (32), with at least one data field (11) for determining the data format, at least one data field (16) for identifying the sender, and at least one data field (19) for identifying the recipient being inserted into the header part (10), it is provided that before, during and, optionally, after the transmission of the short message (SMS), character strings (.LOGIN, .SELECT-CHANNEL) are exchanged between computers (3, 8, 9). By using the data format described in combination with the character strings which are exchanged between the computers (3, 8, 9), a protocol (ISMTP, Internet Short Message Transfer Protocol) that is suitable for such a data transfer and variable can be created which is based on a computer network, e.g. a TCP-IP-based network. By using this data format, a protocol suitable for such a data transmission (ISMTP Internet Short Message Transfer Protocol) can be created which is based on a computer network, e.g. a TCP-IP based network.

Claims

1. A method for transmitting short messages (SMS) between computers (3, 8, 9) in the Internet (4), wherein the short message (SMS) is converted into a data format comprised of a header part (10) and a useful part (32), with at least one data field (11) for determining the data format, at least one data field (16) (Sender Address) for identifying the sender, and at least one data field (19) (Recipient Address) for identifying the recipient being inserted into the header part (10), characterized in that before, during and, optionally, after the transmission of the short message (SMS), character strings (.LOGIN, .SELECT-CHANNEL) are exchanged between computers (3, 8, 9).

2. A method according to claim 1, characterized in that before the transmission of the short message (SMS) at least one character string (.SELECT-CHANNEL) is exchanged between computers (3, 8, 9) of the Internet (4) for selecting the channel.

3. A method according to claim 2, characterized in that before the transmission of the short message (SMS), at least one character string (.LOGIN) is exchanged between computers (3, 8, 9) of the Internet (4) for authenticating the sender of the short message (SMS) and that this character string (.LOGIN) contains at least a user identification.

4. A method according to any one of claims 1 to 3, characterized in that the MIME (Multipurpose Internet Mail Extension) version is entered in data field (11) for determining the data format.

5. A method according to any one of claims 1 to 4, characterized in that a data field (12, MIME type) for defining the type of short message (SMS) is inserted in the header part (10).

6. A method according to any one of claims 1 to 5, characterized in that a data field (13, message Id) is inserted in the header part (10) to indicate a unique identification for the short message (SMS).

7. A method according to any one of claims 1 to 6, characterized in that a data field (14, Sender Ton) is inserted in the header part (10) to indicate the type of network of the sender of the short message (SMS).

8. A method according to any one of claims 1 to 7, characterized in that a data field (15, Sender Npi) is inserted in the header part (10) to determine the numbering plan of the network of the sender.

9. A method according to any one of claims 1 to 8, characterized in that a data field (17, Recipient Ton) is inserted in the header part (10) to determine the type of network of the recipient.

10. A method according to any one of claims 1 to 9, characterized in that a data field (18, Recipient Npi) is inserted in the header part (10) to define the numbering plan of the network of the recipient.

11. A method according to any one of claims 1 to 10, characterized in that a data field (20, Protocol Id) is inserted in the header part (10) to identify the contents transported with the short message (SMS).

12. A method according to any one of claims 1 to 11, characterized in that a data field (21, Is-Compressed) is inserted in the header part (10) to indicate a compression of the useful data.

13. A method according to any one of claims 1 to 12, characterized in that a data field (22, Message Class) is inserted in the header part (10) to distinguish the class of the short message (SMS).

14. A method according to any one of claims 1 to 13, characterized in that a data field (23, Alphabet) is inserted in the header part (10) to determine the code of the useful data.

15. A method according to any one of claims 1 to 14, characterized in that a data field (24, Priority) is inserted in the header part (10) to determine the priority of the short message (SMS).

16. A method according to any one of claims 1 to 15, characterized in that a data field (25, Validity-Period) is inserted in the header part (10) to input the expiration date of the short message (SMS).

17. A method according to any one of claims 1 to 16, characterized in that a data field (26, Cod) is inserted in the header part (10) to determine whether or not a confirmation of the receipt of the short message (SMS) is required.

18. A method according to any one of claims 1 to 17, characterized in that a data field (27, Replace-If-Present) is inserted in the header part (10) to determine whether or not a previously created short message (SMS) is to be replaced by the new short message (SMS).

19. A method according to any one of claims 1 to 18, characterized in that a data field (28, Reply Path) is inserted in the header part (10) to determine the number of repetitions of the sending attempts for the short message (SMS).

20. A method according to any one of claims 1 to 19, characterized in that a data field (29, Send-On) is inserted in the header part (10) to determine a desired point of time of sending the short message (SMS).

21. A method according to any one of claims 1 to 20, characterized in that a data field (30, Created-On) is inserted in the header part (10) to enter the point of time of creating the short message (SMS).

22. A method according to any one of claims 1 to 21, characterized in that a data field (31, Sender-Ip-Address) is inserted in the header part (10) to transmit the Internet addresses (IP numbers) of the computers involved in the transmission.

23. A method according to any one of claims 1 to 22, characterized in that the recipient of the short message (SMS) upon transmission of a character string (.LOGIN) for authenticating the sender of the short message (SMS) transmits a character string to the sender which contains at least a status code regarding the success of the authentication.

24. A method according to any one of claims 1 to 23, characterized in that after a successful log-in, a character string (.SELECT-CHANNEL) is transmitted from the sender to the recipient of the short message (SMS) which contains data regarding the selection of an output channel of the receiving computer.

25. A method according to claim 24, characterized in that the recipient answers the sender of the short message (SMS) with a character string which contains data on the success of the selection of the output channel.

26. A method according to any one of claims 1 to 25, characterized in that a character string (.QUIT) is transmitted from the sender of the short message (SMS) which contains a quitting order to terminate the transmission of the short message (SMS).

27. A method according to claim 26, characterized in that a character string is transmitted to the sender of the short message as a response of the recipient of the short message (SMS) which contains data regarding the success of the quitting order.