Search

US-12627670-B2 - Blockchain folding

US12627670B2US 12627670 B2US12627670 B2US 12627670B2US-12627670-B2

Abstract

An active distributed ledger may comprise an indication of an inactive permission associated with a user device. An entry comprising such indication added to another distributed ledger that is supplemental to the active distributed ledger. An updated active distributed ledger may be generated that does not comprise the indication of the inactive permission. The updated active distributed ledger may comprise an indication of a new permission associated with the user device. The updated active distributed ledger may be stored on the user device or any other device on a network.

Inventors

  • Asad Haque
  • Nancy Davoust

Assignees

  • COMCAST CABLE COMMUNICATIONS, LLC

Dates

Publication Date
20260512
Application Date
20240729

Claims (20)

  1. 1 . A method comprising: determining, by a computing device, a first distributed ledger record on a primary distributed ledger, wherein the first distributed ledger record comprises an active permission associated with a user device, and wherein the first distributed ledger record comprises an identifier that indicates a position of the first distributed ledger record on the primary distributed ledger; receiving, by the computing device and from the user device, a second distributed ledger record comprising an updated active permission associated with the user device; causing removal, from the primary distributed ledger and based on receiving the second distributed ledger record, of the first distributed ledger record; and storing, on a secondary distributed ledger located on a storage device, the first distributed ledger record as an inactive record, wherein the identifier that indicates the position of the first distributed ledger record on the primary distributed ledger is preserved in the inactive record on the secondary distributed ledger.
  2. 2 . The method of claim 1 , wherein the primary distributed ledger is stored on one or more of the computing device or the user device.
  3. 3 . The method of claim 1 , wherein the determining the first distributed ledger record on the primary distributed ledger comprises at least one of storing the first distributed ledger record on the primary distributed ledger, accessing the first distributed ledger record on the primary distributed ledger, or receiving an indication of the first distributed ledger record.
  4. 4 . The method of claim 1 , wherein the storage device comprises at least one of the computing device, a database associated with the computing device, a server associated with the computing device, a network computing device, or a cloud storage device.
  5. 5 . The method of claim 1 , further comprising storing the second distributed ledger record on the primary distributed ledger.
  6. 6 . The method of claim 1 , wherein the user device comprises at least one of a lighting device, a sensor device, an alarm device, a temperature control device, a lighting control device, a lock device, a communication device, a camera device, or a home appliance device.
  7. 7 . The method of claim 1 , wherein the inactive record comprises at least one of an expired permission, a revoked permission, or a permission associated with a security compromise.
  8. 8 . A device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the device to: determine a first distributed ledger record on a primary distributed ledger, wherein the first distributed ledger record comprises an active permission associated with a user device, and wherein the first distributed ledger record comprises an identifier that indicates a position of the first distributed ledger record on the primary distributed ledger; receive, from the user device, a second distributed ledger record comprising an updated active permission associated with the user device; cause removal, from the primary distributed ledger and based on receiving the second distributed ledger record, of the first distributed ledger record; and store, on a secondary distributed ledger located on a storage device, the first distributed ledger record as an inactive record, wherein the identifier that indicates the position of the first distributed ledger record on the primary distributed ledger is preserved in the inactive record on the secondary distributed ledger.
  9. 9 . The device of claim 8 , wherein the primary distributed ledger is stored on one or more of the device or the user device.
  10. 10 . The device of claim 8 , wherein causing the device to determine the first distributed ledger record on the primary distributed ledger comprises at least one of causing the device to store the first distributed ledger record on the primary distributed ledger, access the first distributed ledger record on the primary distributed ledger, or receive an indication of the first distributed ledger record.
  11. 11 . The device of claim 8 , wherein the storage device comprises at least one of the device, a database associated with the device, a server associated with the device, a network computing device, or a cloud storage device.
  12. 12 . The device of claim 8 , further comprising storing the second distributed ledger record on the primary distributed ledger.
  13. 13 . The device of claim 8 , wherein the user device comprises at least one of a lighting device, a sensor device, an alarm device, a temperature control device, a lighting control device, a lock device, a communication device, a camera device, or a home appliance device.
  14. 14 . The device of claim 8 , wherein the inactive record comprises at least one of an expired permission, a revoked permission, or a permission associated with a security compromise.
  15. 15 . A system comprising: a user device; a storage device; and a computing device configured to: determine a first distributed ledger record on a primary distributed ledger, wherein the first distributed ledger record comprises an active permission associated with the user device, and wherein the first distributed ledger record comprises an identifier that indicates a position of the first distributed ledger record on the primary distributed ledger; receive, from the user device, a second distributed ledger record comprising an updated active permission associated with the user device; cause removal, from the primary distributed ledger and based on receiving the second distributed ledger record, of the first distributed ledger record; and store, on a secondary distributed ledger located on the storage device, the first distributed ledger record as an inactive record, wherein the identifier that indicates the position of the first distributed ledger record on the primary distributed ledger is preserved in the inactive record on the secondary distributed ledger.
  16. 16 . The system of claim 15 , wherein the primary distributed ledger is stored on one or more of the computing device or the user device.
  17. 17 . The system of claim 15 , wherein the computing device is configured to determine the first distributed ledger record on the primary distributed ledger, and wherein the computing device is further configured to at least one of cause the device to store the first distributed ledger record on the primary distributed ledger, access the first distributed ledger record on the primary distributed ledger, or receive an indication of the first distributed ledger record.
  18. 18 . The system of claim 15 , wherein the storage device comprises at least one of the computing device, a database associated with the computing device, a server associated with the computing device, a network computing device, or a cloud storage device.
  19. 19 . The system of claim 15 , further comprising storing the second distributed ledger record on the primary distributed ledger.
  20. 20 . The system of claim 15 , wherein the user device comprises at least one of a lighting device, a sensor device, an alarm device, a temperature control device, a lighting control device, a lock device, a communication device, a camera device, or a home appliance device.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. patent application Ser. No. 18/356,934, filed Jul. 21, 2023, now U.S. Pat. No. 12,052,259, issued Jul. 30, 2024, which is a continuation of U.S. patent application Ser. No. 16/395,003, filed Apr. 25, 2019, now U.S. Pat. No. 11,729,175, issued Aug. 15, 2023, which are hereby incorporated by reference in their entirety. BACKGROUND Distributed ledgers may be implemented for use with various technologies. For example, distributed ledgers may have applications to Internet of Things (IoT) devices. IoT devices may be constrained by storage and/or processing capabilities. Developers for distributed ledgers may face issues, such as issues with size and/or growth of the distributed ledger, cost associated with storage of the distributed ledger, increased network transmission time, increased central processing unit (cpu) time for validation of the distributed ledger, as examples. SUMMARY Indications of permissions associated with a user device may be stored on distributed ledgers. The distributed ledgers may comprise a primary distributed ledger stored on the user device. The primary distributed ledger may comprise records indicating active permissions. The distributed ledgers may comprise a secondary distributed ledger stored external to the user device, such as on a network computing system. The secondary distributed ledger may comprise entries indicating inactive permissions, such as expired, invalid, and/or revoked permissions. Based on determining that a permission recorded on the primary distributed ledger is no longer active, an indication of the inactive permission may be recorded on the secondary distributed ledger. An updated primary distributed ledger may be generated that does not comprise the inactive permission. The updated primary distributed ledger may be stored to the user device. Storing and/or processing the updated primary distributed ledger, rather than a distributed ledger comprising entries indicating both active and inactive permissions, may result in reduced consumption of and/or requirement for storage and/or computing resources. BRIEF DESCRIPTION OF THE DRAWINGS The following drawings show generally, by way of example, but not by way of limitation, various examples discussed in the present disclosure. In the drawings: FIG. 1 shows an example distributed system architecture. FIG. 2 shows an example blockchain architecture. FIG. 3 shows an example distributed ledger architecture. FIG. 4 show an example method for managing device association. FIG. 5 shows an example system for managing device association. FIG. 6 shows an example method for managing device association. FIG. 7 shows an example system environment. FIG. 8 shows an example block of a blockchain. FIG. 9 shows an example blockchain. FIG. 10 shows an example secondary blockchain. FIG. 11 shows an example sequence diagram. FIG. 12 shows an example method. FIG. 13 shows an example method. FIG. 14 shows an example method. FIG. 15 shows example method. FIG. 16 shows an example method. FIG. 17 shows an example computing environment. DETAILED DESCRIPTION A distributed ledger (e.g., blockchain) may comprise blocks. The blocks may indicate device associations. For example, the blocks may indicate devices associated with a common entity. The common entity may comprise a common user, a common group of users, a common account, and/or a common premises, as examples. The distributed ledger may be split, such as into an active branch (e.g., primary branch) branch and a secondary branch (e.g., folded branch). The active branch may comprise blocks comprising live (e.g., active, valuable, valid, etc.) transactions. The secondary branch may comprise blocks comprising inactive (e.g., not valuable, invalid, expired, no longer useful or needed, etc.) transactions. Blocks comprising inactive transactions may be removed from the active branch. The blocks comprising inactive transactions may be added to the secondary branch. Blocks in the secondary branch may comprise a new block number. The new block number may indicate a position in the secondary branch. The blocks in the secondary branch may comprise an original block number. The blocks in the secondary branch may comprise a reference to the original block number. Blocks in the active branch may comprise a new block number. The new block number may indicate a position in the active branch. The blocks in the active branch may comprise an original block number. The blocks in the active branch may comprise a reference to the original block number. The original distributed ledger may be reconstituted by merging the active branch and the secondary branch using original block numbers. The secondary branch may be stored in a network computing environment, such as a cloud computing environment. The active branch may be transmitted to one or more user devices. The one or more user devices may use the received active branch to determi