Secure messaging systems

• US 4,866,707 A
• Filed: 03/01/1988
• Issued: 09/12/1989
• Est. Priority Date: 03/03/1987
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Company (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Proudler, Graeme J., Marshall, Alan D., Mitchell, Christopher J.
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): Scutch, III, Frank M.
• Application Number:
  US07/162,724
• Time in Patent Office: 560 Days
• Field of Search: 370/60, 370/94, 370/94 U, 340/825.5, 371/32, 371/33
• US Class Current: 714/749
• CPC Class Codes: H04L 1/1874 Buffer management
• CPC Class Codes: H04L 2001/0093 Point-to-multipoint
• CPC Class Codes: H04L 9/0836 using tree structure or hierarchical structure
• CPC Class Codes: H04L 9/0897 involving additional devices, e.g. trusted platform module [TPM], smartcard or USB
• CPC Class Codes: H04L 9/3242 involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC
• CPC Class Codes: H04N 21/6377 directed to server one-way streaming services wherein the source is controlled by the destination H04L65/613
• CPC Class Codes: H04N 21/658 Transmission by the client directed to the server

Abstract

A secure messaging system with several terminals and many system (control) messages transmitted between the various terminals. These messages can deliberate, accidentally change sequence, or be deleted or duplicated. To protect the system against this, an acknowledgement is sent for every message received (except a simple acknowledgement), and each station stores copies of the messages it has sent, deleting them only when acknowledged. When a new message is to be sent or a non-receipt of acknowledgement time-out occurs, a packet is sent with all previous messages in store prefixed to the new message, so the receiving station cannot act on the new message before receiving and acting on the previous messages. There are known means for ignoring duplicated messages. Preferably there is chained serial authentication of the messages in the packet so that even if one is garbled, they can be acted on up to that point. For security and other reasons, user messages are in general not treated similarly but sent only once; with these, error control is a user responsibility.

Claims

1. A messaging system in which messages are sent and acknowledged, the system comprising a plurality of terminals and means for interconnecting said terminals, each terminal including:

means for sending a message to another terminal;

means for storing any messages which have been sent to another terminal;

means for detecting any stored message upon receipt of an acknowledgment of said message from the terminal to which the message was sent; and

means for bundling a new message with any stored messages,

whereby when it is desired to send a new message from a first terminal to a second terminal the new message is bundled with any other messages which were previously sent from the first terminal to the second terminal but no acknowledgment of which was received by the first terminal and the bundle is thereupon sent from the first terminal to the second terminal.

2. The messaging system of claim 1 wherein the means for bundling comprises means for concatenating the stored messages in the order in which said messages were originally sent and adding the new message to the end of the concatenated messages to form the bundle.

3. The messaging system of claim 2 wherein the means for bundling messages bundles the messages in such a form that if a message in a bundle is damaged messages preceding the damaged message can be acted on by the receiving terminal.

4. The messaging system of claim 2 wherein each terminal includes means for calculating a message authentication code for each message in a bundle according to the contents of the message and any message authentication code of a preceding message in a bundle.

5. The messaging system of claim 1 wherein each terminal includes means for deleting any stored message which has become redundant as a result of a subsequent event.

6. The messaging system of claim 1, wherein a user message is sent only once by a terminal.

7. The messaging system of claim 1, wherein a user message can be sent to request an acknowledgment message.

8. The messaging system of claim 1, further comprising means located in each of the plurality of terminals for logging received user messages.

9. The messaging system of claim 1, further comprising means located in each of the plurality of terminals for logging acknowledged user messages.

10. A method of sending messages from a first terminal to a second terminal, the method comprising:

storing in the first terminal any messages which have been sent to the second terminal;

deleting any stored message upon receipt of an acknowledgment of said message from the second terminal;

bundling a new message to be sent to the second terminal with any stored messages; and

sending the bundle to the second terminal,

whereby the new message is sent together with any other messages which were previously sent from the first terminal to the second terminal but no acknowledgment of which was received by the first terminal.

11. A method according to claim 10 wherein the bundling step comprises concatenating the stored messages in the order in which said messages were originally sent and adding the new message to the end of the concatenated messages to form the bundle.

12. A method according to claim 11 wherein the bundling step comprises concatenating the messages in such a form that if a message in a bundle is damaged messages preceding the damaged message can be acted on by the second terminal.

13. A method according to claim 11 wherein the bundling step comprises calculating a message authentication code for each message in a bundle according to the contents of the message and any message authentication code of a preceding message in the bundle.

14. A method according to claim 10 and further comprising the step of deleting any stored message which has become redundant as a result of a subsequent message.

15. A method of sending messages from a first terminal to a second terminal, the method comprising:

identifying any message to be sent as a user message or a system message;

storing in the first terminal any system messages which have been sent to the second terminal;

deleting any stored message upon receipt of an acknowledgment of said message form the second terminal;

bundling a new system message to be sent to the second terminal with any stored messages; and

sending the bundle to the second terminal,

whereby the new message is sent together with any other system messages which were previously sent from the first terminal to the second terminal but no acknowledgment of which was received by the first terminal.

16. A method according to claim 15 wherein the bundling step comprises concatenating the stored messages in the order in which said messages were originally sent and adding the new message to the end of the concatenated messages to form the bundle.

17. A method according to claim 16 wherein the bundling step comprises concatenating the messages in such a form that if a message in a bundle is damaged messages preceding the damaged message can be acted on by the second terminal.

18. A method according to claim 16 wherein the bundling step comprises calculating a message authentication code for each message in a bundle according to the contents of the message and any message authentication code of a preceding message in the bundle.

19. A method according to claim 15 and further comprising the step of deleting any stored message which has become redundant as a result of a subsequent message.

20. A method according to claim 15 and further comprising the steps of logging received user messages in the second terminal and logging acknowledged user messages in the first terminal.