METHOD FOR SECURE TRANSFER OF MULTIPLE SMALL MESSAGES

• US 20120023158A1
• Filed: 04/14/2009
• Published: 01/26/2012
• Est. Priority Date: 04/14/2009
• Status: Abandoned Application

• Current Assignee: Thomson Licensing (Vantiva SA)
• Original Assignee: Thomson Licensing (Vantiva SA)
• Inventors: Kashyap, Ashwin, Li, Dekai, Mathur, Saurabh, Schmid, Jonas, Prigent, Nicolas F.E.
• Application Number:
  US13/138,758
• Publication Number:
  US 20120023158A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A method and system for securely transferring a multiplicity of short messages using an unsecure connection begins by loading a secure domain component on a client device using a secure connection and then loading an unsecure domain component on the client device. Encrypted messages are sent from an unsecure server to the unsecure domain component. The client device transfers the received encrypted message from the unsecure domain to the secure domain, where the secure domain component decrypts the received encrypted messages. This method works repeatedly without reloading either the secure domain component or the unsecure domain component and by using the unsecure connection to transfer the encrypted messages.

Claims

1. A method performed by a client device operating on a network, the method comprising:

(a) receiving a first software component transmitted using a secure connection on the network;

(b) receiving a second software component transmitted using an unsecure connection on the network;

(c) requesting a content object using the unsecure connection;

(d) receiving, via the unsecure connection, an encrypted version of the requested content object;

(e) transferring the encrypted version of the requested content object from an unsecure domain containing the second software component to a secure domain containing the first software component;

(f) decrypting the encrypted content object using the first component to obtain the requested content object; and

(g) rendering the requested content object on the client device.

2. The method of claim 1, wherein step (a) comprises receiving the first software component comprising a shared secret, a decode routine, and a routine to communicate with the second software component.

3. The method of claim 2, wherein the first software component is transmitted securely using a secure hyper text transfer protocol.

4. The method of claim 1, wherein step (b) comprises receiving the second software component comprising a routine to request objects via the unsecure connection and a routine to communicate with the first software component.

5. The method of claim 1, wherein step (d) is performed using hyper text transfer protocol.

6. The method of claim 1, wherein step (e) comprises transferring the encrypted version of the content object using a cross domain message transfer mechanism.

7. The method of claim 6, wherein the cross domain message transfer mechanism comprises one of a windows.location.hash routine, a cookie, or a window.postMessage routine.

8. The method of claim 1, further comprising:

performing steps (c) through (f) a plurality of times for a plurality of other objects wherein steps (a) and (b) are not repeated.

9. A client device comprising:

a network interface that connects the client device to an unsecure server and a secure server;

a processor having access to memory;

a first component stored in a first domain, the first component transferred into the memory by a secure connection to the secure server;

a second component stored in a second domain, the second component transferred into the memory by an unsecure connection to the unsecure server; and

a cross domain message transfer mechanism;

wherein an encrypted object transferred by the unsecure connection into the second component is decrypted by the first component after the processor invokes the cross domain message transfer mechanism to transfer the encrypted object from the unsecure domain to the secure domain.

10. The device of claim 9, further comprising a rendering mechanism for rendering decrypted objects.

11. The device of claim 9, wherein the first component comprises a shared secret, a decode routine, and a routine to communicate with the second component.

12. The device of claim 9, wherein the second component comprises a routine to request objects via the unsecure connection and a routine to communicate with the first component.

13. The device of claim 9, wherein the first component is securely transferred into the first domain using secure hyper text transfer protocol.

14. The device of claim 13, wherein the cross domain message transfer mechanism comprises one of a windows.location.hash routine, a cookie, or a window.postMessage routine.

15. The device of claim 9, wherein a plurality of encrypted objects are transferred to the second component using an unsecure connection and decrypted by the first component.