Dynamically Configured Connection to a Trust Broker

• US 20140222955A1
• Filed: 03/11/2013
• Published: 08/07/2014
• Est. Priority Date: 02/01/2013
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Vidder, Inc. (Verizon Communications Inc.)
• Inventors: Islam, Junaid, Bilger, Brent, Schroeder, Ted
• Granted Patent: US 9,398,050 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 63/0281 Proxies
• 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/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

A method for connecting to a trust broker system is disclosed. The method is performed on a client device having one or more processors and memory storing one or more programs for execution by the one or more processors. The client device connects to a trust broker system upon start-up of the device, wherein the device is not enabled to connect to any other system. The client device transmits information identifying the electronic device to the trust broker system. The client device receives, from the trust broker, information that enables the client device to connect to a server system, wherein the trust broker determines the appropriate server system based on the client device. The client device downloads, from the server system, further instructions for performing the one or more tasks associated with the client device; wherein the downloaded instructions are only retained for the current session.

Claims

1. A method for connecting to a trust broker system, comprising:

at a stateless client device having one or more processors and memory storing one or more programs for execution by the one or more processors;

connecting to a trust broker system upon start-up of the device, wherein the device is not enabled to connect to any other system;

transmitting information identifying the electronic device to the trust broker system;

receiving, from the trust broker, information that enables the client device to connect to a server system, wherein the trust broker determines the appropriate server system based on the client device; and

downloading, from the server system, further instructions for performing the one or more tasks associated with the client device;

wherein the downloaded instructions are only retained for the current session.

2. The method of claim 1, wherein the instructions downloaded from the server system are dynamically updated by the server system as needed.

3. The method of claim 1 wherein no critical network access information is stored at the client device.

4. The method of claim 1, wherein the stateless client device operates without user interaction.

5. The method of claim 1, wherein the stateless client device is an embedded electronic system in a consumer device.

6. The method of claim 1, wherein the identifying information transmitted to the trust broker system includes a client device ID number and a device role identifier.

7. The method of claim 6, wherein the downloaded instructions are determined by the role identifier received from the client device.

8. An electronic device for connecting to a trust broker system, comprising:

one or more processors;

memory storing one or more programs to be executed by the one or more processors;

the one or more programs comprising instructions for;

connecting to a trust broker system upon start-up of the device, wherein the device is not enabled to connect to any other system;

transmitting information identifying the electronic device to the trust broker system;

receiving, from the trust broker, information that enables the client device to connect to a server system, wherein the trust broker determines the appropriate server system based on the client device; and

downloading, from the server system, further instructions for performing the one or more tasks associated with the client device;

wherein the downloaded instructions are only retained for the current session.

9. The device of claim 8, wherein the instructions downloaded from the server system are dynamically updated by the server system as needed.

10. The device of claim 8, wherein no critical network access information is stored at the client device.

11. The device of claim 8, wherein the stateless client device operates without user interaction.

12. The device of claim 8, wherein the stateless client device is an embedded electronic system in a consumer device.

13. The device of claim 8, wherein the identifying information transmitted to the trust broker system includes a client device ID number and a device role identifier.

14. The device of claim 13, wherein the downloaded instructions are determined by the role identifier received from the client device.

15. A non-transitory computer readable storage medium storing one or more programs configured for execution by an electronic device with a camera, the one or more programs comprising instructions for:

connecting to a trust broker system upon start-up of the device, wherein the device is not enabled to connect to any other system;

transmitting information identifying the electronic device to the trust broker system;

receiving, from the trust broker, information that enables the client device to connect to a server system, wherein the trust broker determines the appropriate server system based on the client device; and

downloading, from the server system, further instructions for performing the one or more tasks associated with the client device;

wherein the downloaded instructions are only retained for the current session.

16. The non-transitory computer readable storage medium of claim 15, wherein the instructions downloaded from the server system are dynamically updated by the server system as needed.

17. The non-transitory computer readable storage medium of claim 15, wherein no critical network access information is stored at the client device.

18. The non-transitory computer readable storage medium of claim 15, wherein the stateless client device operates without user interaction.

19. The non-transitory computer readable storage medium of claim 15, wherein the identifying information transmitted to the trust broker system includes a client device ID number and a device role identifier.

20. The non-transitory computer readable storage medium of claim 19, wherein the downloaded instructions are determined by the role identifier received from the client device.