# US 11,030,297 B2 · Systems and methods for device and user authorization > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,030,297 B2 - Document ID: US11030297B2 - Status: Granted - Kind: B2 - Application number: 16/240,526 - Filed: 2019-01-04 - Published: 2020-07-09 - Granted: 2021-06-08 - Earliest claimed: 2019-01-04 - Assignees: Comcast Cable Communications, LLC - Applicants: Comcast Cable Communications, LLC - Inventors: Andrew Antar; Asad Haque - Web page: https://patentgrep.com/patent/US11030297B2 ## CPC - G06F 21/44: Program or device authentication - G06F 16/1824: {implemented using Network-attached Storage [NAS] architecture (distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097)} - G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures - G06Q 20/0655: {e-cash managed centrally} - G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights} - G06Q 20/3823: {combining multiple encryption tools for a transaction} - G06Q 20/4014: {Identity check for transactions} - G06Q 20/4093: {Monitoring of device authentication} - G06Q 20/425: {using two different networks, one for transaction and one for security confirmation} - H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC} - H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3247: {involving digital signatures} - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - H04L 63/102: {Entity profiles} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems and methods are described for authorizing users and/or devices. An example method may comprise receiving, from a user device, a request to access a function associated with a service account. The request may comprise an identifier of the user device. The example method may comprise determining, based on the identifier, a primary authority holder of the service account. The example method may comprise determining that a first record on a first distributed ledger associated with the primary authority holder indicates that the user device is associated with the primary authority holder. The example method may comprise determining that a second record on a second distributed ledger associated with the user device indicates that the user device is associated with the primary authority holder. The example method may comprise granting, based on the request, the first record, and the second record, the user device access to the function. ## Claims ### Claim 1 A method comprising: receiving, from a first user device associated with an account holder of a service account, a first request to grant a user one or more permissions associated with the service account; causing, based on the first request, a first record to be created on a first distributed ledger associated with the account holder, wherein the first record comprises an indication of a second user device associated with the user; causing, based on the first request, a second record to be created on a second distributed ledger associated with the user and different than the first distributed ledger, wherein the second record comprises an indication of the one or more permissions; receiving, from the second user device, a second request to access a function associated with the one or more permissions; and accessing, based on the second request, the first record and the second record; and granting, based on the accessing the first record and the second record, the second user device access to the function. ### Claim 2 (depends on 1) The method of claim 1, wherein the method comprises causing, based on the first request and prior to the causing the second record to be created on the second distributed ledger, the second distributed ledger to be generated, wherein the second distributed ledger comprises an initial record comprising an indication of the second user device. ### Claim 3 (depends on 1) The method of claim 1, comprising: receiving, from the second user device, a third request to grant another user a permission of the one or more permissions; and causing, based on the third request, the first record, and the second record, a third record to be created on a third distributed ledger associated with the second user device, wherein the third record comprises an indication of a third user device associated with the another user. ### Claim 4 (depends on 3) The method of claim 3, comprising causing, based on the third request, the first record, and the second record, a fourth record to be created on the first distributed ledger, wherein the fourth record comprises an indication of the third user device. ### Claim 5 (depends on 4) The method of claim 4, comprising causing, based on the third request, the first record, and the second record, a fifth record to be created on a fourth distributed ledger associated with the another user, wherein the fifth record comprises an indication of the permission. ### Claim 6 (depends on 1) The method of claim 1, wherein the first record comprises an indication of the one or more permissions. ### Claim 7 (depends on 1) The method of claim 1, wherein the first distributed ledger comprises a blockchain and the first record comprises a block of the blockchain; and wherein blocks of the blockchain each comprise no more than one transaction. ### Claim 8 (depends on 7) The method of claim 7, wherein the blocks of the blockchain each comprise an indication of a single device. ### Claim 9 (depends on 1) The method of claim 1, wherein the method comprises generating, prior to the receiving the first request and based on an activation of a platform on the first user device, the first distributed ledger; wherein the receiving the first request comprises receiving, via the platform, the first request. ### Claim 10 A method comprising: receiving, from a user device, a request to access a function associated with a service account, wherein the request comprises an identifier of the user device; determining, based on the identifier, a primary authority holder of the service account; determining that a first record on a first distributed ledger of permissions associated with the primary authority holder indicates that the user device is associated with the primary authority holder; determining that a second record on a second distributed ledger of permissions associated with the user device indicates that the user device is associated with the primary authority holder; and granting, based on the request, the first record, and the second record, the user device access to the function. ### Claim 11 (depends on 10) The method of claim 10, wherein the function comprises control, by the user device, of another user device associated with the primary authority holder. ### Claim 12 (depends on 10) The method of claim 10, wherein the identifier comprises a digital certificate. ### Claim 13 (depends on 10) The method of claim 10, wherein the first record and the second record each comprise an indication that the user device is authorized to access the function. ### Claim 14 (depends on 10) The method of claim 10, wherein the function comprises at least one of control of a third user device associated with the service account, access to data associated with the service account, purchase with a payment form associated with the service account, submission of a claim associated with the service account, or amendment of a service associated with the service account. ### Claim 15 A method comprising: causing, based on activation of a platform on a first user device associated with a primary authority holder of a service account, a first unique identifier to be stored on the first user device and a first distributed ledger associated with the first user device to be generated, wherein the first distributed ledger comprises a first record comprising an indication of the first unique identifier; receiving, via the platform, an indication of a second user device associated with the service account and an indication of a unique identifier; causing, based on the indication of the second user device and the unique identifier matching the first unique identifier in the first record, a second unique identifier to be stored on the second user device, a second record indicating the second unique identifier to be created on the first distributed ledger, and a second distributed ledger to be generated, wherein the second distributed ledger comprises a third record comprising an indication of the first user device and an indication of the second unique identifier; and authorizing, based on the second record and the third record, the second user device to access a function associated with the service account. ### Claim 16 (depends on 15) The method of claim 15, comprising authorizing, based on the first record and the second record, the first user device to access a function associated with the second user device. ### Claim 17 (depends on 15) The method of claim 15, wherein the method comprises sending, to the second user device and based on the indication of the second user device, a prompt to install the platform on the second user device. ### Claim 18 (depends on 15) The method of claim 15, wherein the first distributed ledger comprises a blockchain; and wherein blocks of the blockchain indicate devices owned by the primary authority holder. ### Claim 19 (depends on 15) The method of claim 15, wherein the authorizing the second user device is based on: receiving a request to access the function associated with the service account, wherein the request comprises the second unique identifier; and determining, based on the second unique identifier, the second record and the third record. ### Claim 20 (depends on 15) The method of claim 15, wherein the first unique identifier comprises a first token and the second unique identifier comprises a second token; and wherein the causing the first unique identifier to be stored on the first user device comprises causing a digital certificate comprising the first token to be stored on the first user device.