IP Library Granted Patent US 11,700,252
Granted Patent B2
US 11,700,252 · App. 17/843,583 · Granted Jul 11, 2023

Trust broker system for managing and sharing trust levels

Inventor: Robert Koeten (Half Moon Bay, CA)
Assignee: Pulse Secure, LLC
H04L63/0884H04L9/0637H04L9/3218H04L63/0807H04L63/0892
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,700,252
App. No.
17/843,583
Granted
Jul 11, 2023
Kind
B2
Abstract

This disclosure is related to devices, systems, and techniques for controlling access to network services based on a trust ledger. In some examples, a trust broker system enables a relying party to control network service access of client device, where the trust broker system comprises one or more computing devices configured to maintain a trust ledger including a trust account balance (TAB) associated with each user of a set of users, where the TAB associated with each user of the set of users represents a value used to determine whether the respective user is permitted to access a resource.

Claims (80)

1. A trust broker system which enables a relying party to control network service access of a client device, the trust broker system comprising:

one or more computing devices configured to maintain a trust ledger including a trust account balance (TAB) associated with each user of a set of users, wherein:

the TAB associated with each user of the set of users represents a value used to determine whether a respective user is permitted to access a resource, and

by maintaining the trust ledger, the one or more computing devices enable each device of a set of devices having access to the trust broker system to:

receive, by a respective device of the set of devices, a request for a TAB associated with a user of the set of users;

determine, based on the trust ledger, the TAB associated with the user of the set of users; and

output, by the respective device of the set of devices, information indicative of the TAB associated with the user of the set of users; and

a trust assessor configured to:

receive, from the one or more computing devices, an indication that the TAB associated with the user of the set of users is updated;

reassess the TAB associated with the user by comparing the TAB with a TAB threshold; and

in response to the TAB being less than the TAB threshold, execute a smart contract to initiate a host check to increase the TAB associated with the user of the set of users.

2. The trust broker system of claim 1 , wherein by maintaining the trust ledger, the one or more computing devices enable the client device to:

receive a request from a user of the set of users to authenticate the user with a blockchain client of the client device, wherein the client device is included in the set of devices having access to the trust broker system; and

determine a TAB associated with the user, wherein the TAB associated with the user is recorded in the trust ledger.

3. The trust broker system of claim 2 , wherein:

by maintaining the trust ledger, the one or more computing devices enable the client device to:

receive, by a client application of the client device, an application resource request from the user of the set of users; and

output, from the client application, the application resource request, and

by maintaining the trust ledger, the one or more computing devices enable the relying party to:

receive the application resource request;

determine, based on the trust ledger, the TAB associated with the user of the set of users; and

in response to the TAB associated with the user being greater than or equal to a TAB threshold, process the application resource request.

4. The trust broker system of claim 3 , wherein by maintaining the trust ledger, the one or more computing devices enable the relying party to:

maintain a list that includes a number of application resource requests associated with each user of the set of users received by the relying party;

in response to the number of application resource requests associated with the user exceeding a threshold number of application resource requests, determine that a trust reassessment is required for the user; and

execute a smart contract to decrease the TAB associated with the user; and

distribute a TAB decrease transaction to each device of the set of devices having access to the trust broker system.

5. The trust broker system of claim 1 , wherein:

the TAB corresponding to each user of the set of users may be within a range from 0 to 1000; and

the TAB associated with each user of the set of users is modified at a TAB change rate.

6. The trust broker system of claim 1 , wherein the one or more computing devices comprise one or more blockchain miner devices.

7. The trust broker system of claim 1 , wherein by maintaining the trust ledger, the one or more computing devices enable the client device to:

execute a first smart contract with an identity provider (IdP) blockchain client of an identity broker device to authenticate the user with an IdP service of the identity broker device;

based on authentication of the user by the IdP service, execute a second smart contract to initiate a TAB update transaction to change a TAB associated with the user; and

distribute the TAB update transaction to each device of the set of devices having access to the trust broker system.

8. The trust broker system of claim 7 , wherein the IdP service is included in the set of devices having access to the trust broker system.

9. The trust broker system of claim 7 , wherein the one or more computing devices are further configured to:

receive the TAB update transaction;

execute, in response to receiving the TAB update transaction, consensus algorithms to update the TAB associated with the user in the trust ledger, wherein the execution creates an updated trust ledger; and

distribute the updated trust ledger to each device of the set of devices having access to the trust broker system.

10. The trust broker system of claim 9 , wherein the consensus algorithms include a proof-of-work algorithm, a proof-of-stake algorithm, or a proof-of-time algorithm.

11. A method to enable a relying party to control network service access of a client device, the method comprising:

maintaining, using one or more computing devices, a trust ledger including a trust account balance (TAB) associated with each user of a set of users, wherein the TAB associated with each user of the set of users represents a value used to determine whether a respective user is permitted to access a resource, and

by maintaining the trust ledger, enabling each device of a set of devices having access to a trust broker system to perform:

receiving, by a respective device of the set of devices, a request for a TAB associated with a user of the set of users;

determining, based on the trust ledger, the TAB associated with the user of the set of users;

outputting, by the respective device of the set of devices, information indicative of the TAB associated with the user of the set of users;

receiving, from the one or more computing devices, an indication that the TAB associated with the user of the set of users is updated;

reassessing the TAB associated with the user by comparing the TAB with a TAB threshold; and

in response to the TAB being less than the TAB threshold, executing a smart contract to initiate a host check to increase the TAB associated with the user of the set of users.

12. The method of claim 11 , wherein by maintaining the trust ledger using the one or more computing devices, enabling the client device to perform:

receiving a request from a user of the set of users to authenticate the user with a blockchain client of the client device, wherein the client device is included in the set of devices having access to the trust broker system; and

determining a TAB associated with the user, wherein the TAB associated with the user is recorded in the trust ledger.

13. The method of claim 12 , wherein:

by maintaining the trust ledger using the one or more computing devices, enabling the client device to:

receiving, by a client application of the client device, an application resource request from the user of the set of users; and

outputting, from the client application, the application resource request, and

by maintaining the trust ledger using the one or more computing devices, enabling the relying party to:

receiving the application resource request;

determining, based on the trust ledger, the TAB associated with the user of the set of users; and

in response to the TAB associated with the user being greater than or equal to a TAB threshold, processing the application resource request.

14. The method of claim 13 , wherein by maintaining the trust ledger using the one or more computing devices, enabling the relying party to:

maintaining a list that includes a number of application resource requests associated with each user of the set of users received by the relying party;

in response to the number of application resource requests associated with the user exceeding a threshold number of application resource requests, determining that a trust reassessment is required for the user; and

executing a smart contract to decrease the TAB associated with the user; and

distribute a TAB decrease transaction to each device of the set of devices having access to the trust broker system.

15. The method of claim 11 , wherein:

the TAB corresponding to each user of the set of users may be within a range from 0 to 1000; and

the TAB associated with each user of the set of users is modified at a TAB change rate.

16. The method of claim 11 , wherein the one or more computing devices comprise one or more blockchain miner devices.

17. The method of claim 11 , further comprising:

executing a first smart contract with an identity provider (IdP) blockchain client of an identity broker device to authenticate the user with an IdP service of the identity broker device;

based on authentication of the user by the IdP service, executing a second smart contract to initiate a TAB update transaction to change a TAB associated with the user; and

distributing the TAB update transaction to each device of the set of devices having access to the trust broker system.

18. The method of claim 17 , wherein the IdP service is included in the set of devices having access to the trust broker system.

19. The method of claim 17 , further comprising:

receiving the TAB update transaction;

executing, in response to receiving the TAB update transaction, consensus algorithms to update the TAB associated with the user in the trust ledger, wherein the execution creates an updated trust ledger; and

distributing the updated trust ledger to each device of the set of devices having access to the trust broker system.

20. The method of claim 19 , wherein the consensus algorithms include a proof-of-work algorithm, a proof-of-stake algorithm, or a proof-of-time algorithm.

Assignments (6)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 3, 2025
From: PULSE SECURE LLC
To: ALTER DOMUS (US) LLC
Reel/Frame 071165/0027 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 067457/0497 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071124/0331 →
FIRST LIEN INTELLECTUAL PROPERTY AGREEMENT SUPPLEMENT Recorded May 19, 2024
From: IVANTI, INC.; PULSE SECURE, LLC; MOBILEIRON, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 067457/0472 →
SECOND LIEN INTELLECTUAL PROPERTY AGREEMENT SUPPLEMENT Recorded May 19, 2024
From: IVANTI, INC.; PULSE SECURE, LLC; MOBILEIRON, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 067457/0497 →
Continuity (2)
Continuation 16668785 · Oct 30, 2019
Related Publication 20220329592A1 · Oct 13, 2022
Cited By (1)
US 12,719,851