Granted Patent B2

US 12,361,015 · App. 18/150,363 · Granted Jul 15, 2025

Inventors: Ahmed A. Khan (Plano, TX); Khaliq Raza (Wesley Chapel, FL); Donna L. Rodela (Colorado Springs, CO); Nityanand Sharma (Tampa, FL); Syed R. Noor (Chantilly, VA); Abubakar Syed (Tampa, FL); Jeaha Yang (Darien, CT); Andrew Buford (Columbus, OH); Rangesh Sripathi (Chennai, IN)

Assignee: Verizon Patent and Licensing Inc.

G06F16/27G06F8/63H04L63/101

Abstract

Claims (54)

1. A device, comprising:

one or more processors configured to:

receive a distributed ledger creation request, wherein the distributed ledger creation request specifies a quantity of nodes;

provision a plurality of sets of hardware resources to implement a plurality of nodes, wherein the plurality of nodes includes the requested quantity of nodes, wherein

provisioning the plurality of sets of hardware resources includes generating communication information associated with each node of the plurality of nodes;

instruct at least one node, of the plurality of nodes, to establish a distributed ledger, wherein the at least one node uses the communication information, associated with each node of the plurality of nodes, to communicate with one or more other nodes of the plurality of nodes to establish the distributed ledger;

generate particular communication information associated with the established distributed ledger;

output, in response to the distributed ledger creation request, the particular communication information associated with the established distributed ledger;

receive a request to access the established distributed ledger, wherein the request is associated with the particular communication information; and

forward, based on the particular communication information associated with the request, the request to one or more nodes of the plurality of nodes.

2. The device of claim 1 , wherein the request is received from a particular User Equipment (“UE”), and wherein outputting the particular communication information associated with the established distributed ledger includes outputting the particular communication information to the particular UE.

3. The device of claim 2 , wherein the UE communicates with the device to interact with the distributed ledger.

4. The device of claim 3 , wherein interacting with the distributed ledger includes at least one of:

providing information to be recorded to the distributed ledger, or

accessing information previously recorded to the distributed ledger.

5. The device of claim 1 , wherein the distributed ledger creation request includes an access list that specifies a set of entities that are authorized to access the distributed ledger, wherein the distributed ledger is a permissioned distributed ledger for which access is restricted to the entities specified in the access list.

6. The device of claim 1 , wherein the distributed ledger creation request specifies a particular distributed ledger framework, wherein provisioning the plurality of sets of hardware resources to implement the plurality of nodes includes:

selecting one or more images, associated with the particular distributed ledger framework, from a plurality of images that are associated with a plurality of different distributed ledger frameworks; and

installing the one or more images at the plurality of sets of hardware resources.

7. The device of claim 1 , wherein the plurality of sets of hardware resources each implement a virtual machine, wherein each node of the plurality of nodes is associated with a respective virtual machine implemented by a particular set of hardware resources.

8. A non-transitory computer-readable medium, storing a plurality of processor-executable instructions to:

receive a distributed ledger creation request, wherein the distributed ledger creation request specifies a quantity of nodes;

provision a plurality of sets of hardware resources to implement a plurality of nodes, wherein the plurality of nodes includes the requested quantity of nodes, wherein provisioning the plurality of sets of hardware resources includes generating communication information associated with each node of the plurality of nodes;

instruct at least one node, of the plurality of nodes, to establish a distributed ledger, wherein the at least one node uses the communication information, associated with each node of the plurality of nodes, to communicate with one or more other nodes of the plurality of nodes to establish the distributed ledger; generate particular communication information associated with the established distributed ledger;

output, in response to the distributed ledger creation request, the particular communication information associated with the established distributed ledger;

receive a request to access the established distributed ledger, wherein the request is associated with the particular communication information; and

forward, based on the particular communication information associated with the request, the request to one or more nodes of the plurality of nodes.

9. The non-transitory computer-readable medium of claim 8 , wherein the request is received from a particular User Equipment (“UE”), and wherein outputting the particular communication information associated with the established distributed ledger includes outputting the particular communication information to the particular UE.

10. The non-transitory computer-readable medium of claim 9 , wherein the UE uses the particular communication information to interact with the distributed ledger.

11. The non-transitory computer-readable medium of claim 10 , wherein interacting with the distributed ledger includes at least one of:

providing information to be recorded to the distributed ledger, or

accessing information previously recorded to the distributed ledger.

12. The non-transitory computer-readable medium of claim 8 , wherein the distributed ledger creation request includes an access list that specifies a set of entities that are authorized to access the distributed ledger, wherein the distributed ledger is a permissioned distributed ledger for which access is restricted to the entities specified in the access list.

13. The non-transitory computer-readable medium of claim 8 , wherein the distributed ledger creation request specifies a particular distributed ledger framework, wherein provisioning the plurality of sets of hardware resources to implement the plurality of nodes includes:

selecting one or more images, associated with the particular distributed ledger framework, from a plurality of images that are associated with a plurality of different distributed ledger frameworks; and

installing the one or more images at the plurality of sets of hardware resources.

14. The non-transitory computer-readable medium of claim 8 , wherein the plurality of sets of hardware resources each implement a virtual machine, wherein each node of the plurality of nodes is associated with a respective virtual machine implemented by a particular set of hardware resources.

15. A method, comprising:

receiving a distributed ledger creation request, wherein the distributed ledger creation request specifies a quantity of nodes;

provisioning a plurality of sets of hardware resources to implement a plurality of nodes, wherein the plurality of nodes includes the requested quantity of nodes, wherein provisioning the plurality of sets of hardware resources includes generating communication information associated with each node of the plurality of nodes;

instructing at least one node, of the plurality of nodes, to establish a distributed ledger, wherein the at least one node uses the communication information, associated with each node of the plurality of nodes, to communicate with one or more other nodes of the plurality of nodes to establish the distributed ledger;

generating particular communication information associated with the established distributed ledger;

outputting, in response to the distributed ledger creation request, the particular communication information associated with the distributed ledger;

receiving a request to access the established distributed ledger, wherein the request is associated with the particular communication information; and

forwarding, based on the particular communication information associated with the request, the request to one or more nodes of the plurality of nodes.

16. The method of claim 15 , wherein the request is received from a particular User Equipment (“UE”), and wherein outputting the particular communication information associated with the established distributed ledger includes outputting the particular communication information to the particular UE.

17. The method of claim 16 , wherein the UE uses the particular communication information to interact with the distributed ledger, wherein interacting with the distributed ledger includes at least one of:

providing information to be recorded to the distributed ledger, or

accessing information previously recorded to the distributed ledger.

18. The method of claim 15 , wherein the distributed ledger creation request includes an access list that specifies a set of entities that are authorized to access the distributed ledger, wherein the distributed ledger is a permissioned distributed ledger for which access is restricted to the entities specified in the access list.

19. The method of claim 15 , wherein the distributed ledger creation request specifies a particular distributed ledger framework, wherein provisioning the plurality of sets of hardware resources to implement the plurality of nodes includes:

selecting one or more images, associated with the particular distributed ledger framework, from a plurality of images that are associated with a plurality of different distributed ledger frameworks; and

installing the one or more images at the plurality of sets of hardware resources.

20. The method of claim 15 , wherein the plurality of sets of hardware resources each implement a virtual machine, wherein each node of the plurality of nodes is associated with a respective virtual machine implemented by a particular set of hardware resources.

Assignments (1)

Continuity (1)

References Cited (33)