Data communications protocol for facilitating communications between a message entry device and a messaging center

• US 5,966,663 A
• Filed: 01/14/1997
• Issued: 10/12/1999
• Est. Priority Date: 01/14/1997
• Status: Expired due to Term

• Current Assignee: Ericsson Messaging Systems Incorporated (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Ericsson Messaging Systems Incorporated (Telefonaktiebolaget LM Ericsson)
• Inventors: Gleason, Thomas G.
• Primary Examiner(s): Urban, Edward F.
• Application Number:
  US08/783,176
• Time in Patent Office: 1,001 Days
• Field of Search: 455/412, 455/414, 455/418, 455/419, 455/466, 455/517, 395/200.39, 395/200.33
• US Class Current: 455/466
• CPC Class Codes: H04L 51/226 Delivery according to priorities
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 3/5307 for recording messages comprising any combination of audio and non-audio components
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

A data communications protocol facilitates communications between a message entry device and a messaging center. The protocol permits an operator to enter a message and transmit it quickly, efficiently, and with confirmation. In an example application to short text messaging, two-way data communications between a message entry device and a message handling center, a small set of simple transactional commands is used for communicating messages to and from cellular telephones. Both the message entry device and the message handling center may independently initiate and send messages to the other. An input message is encoded by encapsulating the message between first and second delimiters, e.g., "{" and "}", and associating a message tag with the encapsulated message. Both the message tag and the encapsulated message are in human-readable ASCII format. The delimited message and associated message tag are further encapsulated by additional delimiters to form a protocol data unit with an associated protocol data unit tag. The message handling center simply parses the various delimited fields in accordance with the associated tags. No complicated encoding or decoding procedures are necessary.

Claims

1. A method for exchanging data between a message entry device (MED) and a message handling center (MC), comprising:

defining one of the MED and MC which initiates a communications connection between the MED and MC as a client with the other of the MED and MC being a server, where either the MED or the MC may independently initiate a communications connection as the client;

establishing a set of human-readable transactional commands used by the client and server to transmit information over the established communications connection, each transactional command including a transaction request protocol data unit (PDU) sent from the client which initiates the transaction and a transaction confirm protocol data unit (PDU) sent from the server which confirms whether the transaction request is successful;

generating at one of the MED and the MEC a message to be sent to the other of the MED and the MC;

encapsulating the message between first and second delimiters and associating a message tag with the encapsulated message;

encapsulating the delimited message and associated message tag between third and fourth delimiters to form a protocol data unit (PDU) and associating a PDU tag with the encapsulated message, thereby generating an encoded PDU; and

sending the encoded PDU to the other of the MED and the MC.

2. The method in claim 1, wherein the set of transactions includes a bind transaction used by the client to initiate a communications session between the client and server to permit plural transaction request PDUs and transaction confirm PDUs to be exchanged during the communications session.

3. The method in claim 2, wherein the set of transactions includes an unbind transaction used to end the communications session.

4. The method in claim 1, wherein the set of transactions includes a submit transaction initiated by the first device to submit a message to the second device.

5. The method in claim 1, wherein each PDU request and confirm is independent of other PDU requests and confirms to permitting transmission of messages having a varying number of PDUs.

6. The method in claim 1, wherein the set of transactions includes a deliver transaction initiated by the first device to retrieve a message from the second device.

7. The method in claim 1, wherein the set of transactions includes a remove transaction initiated by the MED to delete a message stored in the MC.

8. The method in claim 1, wherein the set of transactions includes an inquire transaction initiated by the client to inquire about the status of an earlier submitted message.

9. The method in claim 1, wherein at least some of the transactions each include one or more parameters with each parameter specifying a particular operation to be performed with respect to a submitted message.

10. The method in claim 9, wherein the one or more parameters include a deferred delivery time when an attempt will be made to transmit the message.

11. The method in claim 10, wherein the parameters include a message expiration time after which no further attempts should be made to transmit the message.

12. The method in claim 10, wherein the parameters include a message delivery status to inform the message submitter whether a message was successfully delivered, and if not, the reason for failed delivery.

13. The method in claim 10, wherein the parameters include a confirmation parameter that indicates whether confirmation PDUs should be suppressed to facilitate transmission of long messages or transmission messages to plural destinations.

14. The method in claim 10, wherein the parameters include a transaction reference which assigned by the originator of the transaction request, the transaction reference is used to match a pending transaction request with a received transaction confirm.

15. The method in claim 10, wherein the parameters include a maximum transaction window that represents the maximum number of outstanding transaction requests pending a confirm transaction.

16. The method in claim 9, wherein the one or more parameters include plural destination addresses for transmitting a PDU to plural different destinations.

17. The method in claim 9, wherein the one or more parameters include a priority associated with a message which controls the order in which the message will be transmitted with higher priority messages being transmitted before lower priority messages.

18. The method in claim 1, wherein the encoded PDU is written in ASCII text, the delimited message in the encoded PDU being humanly readable.

19. The method in claim 18, wherein before the transmitting step the method further comprises:

translating the encoded PDU from ASCII form to binary form.

20. The method in claim 19,further comprising at the second device the steps of:

receiving binary symbols corresponding to the transmitted PDU;

converting the received binary symbols into ASCII format; and

parsing the encoded PDU using the first, second, third, and fourth delimiters and PDU tags to unpack the message.

21. The method in claim 1, wherein additional information is included in the encoded PDU by encapsulating the additional information between fifth and sixth delimiters and attaching an associated tag related to the addition information to the delimited additional information.

22. The method in claim 21, wherein the delimited additional information and associated tag arc nested with the delimited message and message tag between the third and fourth delimiters.

23. The method in claim 21, further comprising the step of:

attaching a sequence tag to the nested additional information and message.

24. The method in claim 1, wherein the encoded PDU has the following format:

PDUtag{message tag{message}},

where the "{"and"}" are delimiters.

25. The method in claim 24, wherein the encoded PDU has the following format:

PDUtag{sequence tag{message tag{message}additional information tag{additional information}}},

where the "{"and"}" are delimiters.

26. The method in claim 1, wherein each tag identifies the content of the delimited information with which the tag is associated.

27. The method in claim 1, wherein each tag identifies the content of the delimited information with which the tag is associated, the PDU including a sequence tag which is associated with a sequence of primitive service elements and primitive service tags.

28. The method in claim 1, wherein the set of transactions includes a replace transaction initiated by the MED to replace a message stored in the MC.

29. The method in claim 1, further comprising:

marking some of the transactions to indicate they include plural PDUs thereby binding the plural PDUs to the same transaction.

30. A messaging system for delivering messages, comprising:

a message handling center providing a plurality of messaging services including storing messages in electronic form and forwarding the messages to destination devices under prescribed conditions;

a mobile radio communications network connected to the message handling center including a radio base station for communicating voice and data call information over radio channels with portable radios;

a message service center including;

a telephone for receiving from a call originator a text message to be delivered to one of the portable radios, the text message including alphanumeric characters and other symbols readable by humans;

a message entry device connected to the message handling center used to enter the text message, the message entry device including a message processor for encoding the text message and control information related to the text message into a format where at least part of the text message is encapsulated between first and second delimiters and is associated with a message tag, and the control information is encapsulated between third and fourth delimiters to form a protocol data unit (PDU) in which the text message and control information are in human readable format, the PDU being transmitted to the message handling center,

wherein the message handling device receives the PDU, parses out the at least part of the text message and control information using the delimiters and message tag, processes the control information and message tag, and delivers the text message to the one portable radio by way of the mobile radio network and the radio base station in accordance with the control information.

31. The messaging system in accordance with claim 30, wherein when the message handling center receives a radio text message generated by the portable radio from the mobile communications network, a processor in the message handling center encodes the radio text message and control information related to the radio text message into a format where at least part of the radio text message is encapsulated between first and second delimiters and associated with a message tag and the control information is encapsulated between third and fourth delimiters to form a protocol data unit (PDU) in which the text message and control information are in human readable format, the PDU being transmitted to the message entry device in accordance with the control information, and wherein the message entry device receives the PDU, parses out the at least part of the text message and control information using the delimiters and message tag, processes the control information and message tag.

32. The messaging system in accordance with claim 30, wherein one of the message entry device and message handling center which initiates a communications connection between the message entry device and message handling center as a client with the other of the message entry device an message handling center being the server, where either the message entry device or the message handling center may independently initiate a communications connection as the client.

33. The messaging system in accordance with claim 30, wherein a set of human-readable transactional commands used by the client and server are employed to transmit PDUs, each transactional command including a transaction request PDU sent from the client which initiates the transaction and a transaction confirm PDU sent from the server which confirms whether the transaction request is successful.

34. The messaging system in accordance with claim 30, wherein some of the transactions are marked to indicate they include plural PDUs to bind those PDUs to the same transaction.