# US 2019/0163912 A1 · System and method for recording device lifecycle transactions as versioned blocks in a blockchain network using a transaction connector and broker service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0163912 A1
- Document ID: US20190163912A1
- Status: Published application
- Kind: A1
- Application number: 16/180,200
- Filed: 2018-11-05
- Published: 2019-05-30
- Earliest claimed: 2017-11-30
- Assignees: Mocana Corporation
- Applicants: Mocana Corporation
- Inventors: Srinivas KUMAR; Atul GUPTA; Ruslan ULANOV; Shreya UCHIL
- Web page: https://patentgrep.com/patent/US20190163912A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57)
- G06F 16/1834: {implemented based on peer-to-peer networks, e.g. gnutella (p2p communication protocols H04L67/104)}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 21/575: {Secure boot}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/0877: {using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- 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 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0464: {using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method of building a device historian, across a supply chain of device manufactures and managers, by a plurality of device management services comprising an enrollment service, an update service, a policy service, and an analytics service, a transaction connector, a blockchain broker service participating as a node in a blockchain network, and transaction filters. The method comprises sending, by the plurality of device management services a transaction record over the transaction connector to the blockchain broker service, receiving, by the blockchain broker service, the transaction record, filtering, by the blockchain broker service, information in the transaction record based on the transaction filters, preparing, by the blockchain broker service, a versioned block based on the filtered information from the transaction record, and adding, by the blockchain broker service, the versioned block to the blockchain network.

## Claims

### Claim 1

A method of updating a device, that has been authenticated, using dynamic device attributes discovered by an update client on the device, an update service in a supply chain network of providers and publishers, orchestration rules, a local ledger, and a blockchain broker service the method comprising:
sending, by the update client on the device, a device request for an update package for the device from the update service in the supply chain network, wherein the device request includes the discovered dynamic device attributes;
receiving, by the update service, the device request;
preparing, by the update service, a doubly signed and reencrypted update package based on the orchestration rules established for a network service of the supply chain network;
sending, by the update service, the doubly signed and reencrypted update package to the device; and
recording, by the update service, a request log for the device as an entry in the local ledger, and distributing blocks of transaction records to the blockchain broker service to maintain a distributed ledger to reproduce history of update packages sent to a plurality of devices by a plurality of publishers in the supply chain.

### Claim 2 (depends on 1)

The method of claim 1, wherein the request log for the device is doubly signed and reencrypted and includes at least a request counter, request operation data, a request nonce, a device request signature, a request hash, a device signature, a device certificate identifier, a publisher signature, a publisher certificate identifier, a publisher package identifier, a device identifier based on the discovered dynamic device attributes and a publisher identifier.

### Claim 3 (depends on 2)

The method of claim 2, wherein the distributed ledger in the blockchain broker service has adequate transaction records to reproduce a history of device updates and service transactions for cross domain traceability to the supply chain network of providers and publishers.

### Claim 4

A method of updating a device, that has been authenticated, using dynamic device attributes discovered by an update client on the device, a plurality of providers of update packages, an update service of a plurality of publishers in a supply chain network of providers and publishers, orchestration rules, a local ledger, and a blockchain broker service, the method comprising:
sending, by the update client on the device, a device request for an update package for the device from the update service in the supply chain network, wherein the device request includes the discovered dynamic device attributes;
receiving, by the update service, the device request;
preparing, by the update service, a doubly signed and reencrypted update package based on the orchestration rules established for a network service of the supply chain network;
sending, by the update service, the doubly signed and reencrypted update package to the device; and
recording, by the update service, a request log for the device as an entry in the local ledger, and distributing blocks of transaction records to the blockchain broker service to maintain a distributed ledger to reproduce history of provider packages sent to a plurality of authenticated devices by a plurality of providers and publishers in the supply chain.

### Claim 5 (depends on 4)

The method of claim 4, wherein the request log for the device is doubly signed and reencrypted and includes at least a request counter, request operation data, a request nonce, a device request signature, a request hash, a device signature, a device certificate identifier, a publisher signature, a publisher certificate identifier, a publisher package identifier, a device identifier based on the discovered dynamic device attributes, a publisher identifier, and a provider package identifier.

### Claim 6 (depends on 5)

The method of claim 5, wherein the distributed ledger in the blockchain broker service has adequate transaction records to reproduce a history of device updates and service transactions for cross domain traceability to a supply chain of update package providers.

### Claim 7

A method of updating a device using an update client on the device, an update service in a supply chain network of providers and publishers, orchestration rules, a local ledger, and a blockchain broker service the method comprising:
sending, by the update client, a device request for an update package for the device from the update service in the supply chain network;
receiving, by the update service, the device request and authenticating the device;
preparing, by the update service, a signed and encrypted update package based on the orchestration rules established for a network service of the supply chain network;
sending, by the update service, the signed and encrypted update package to the device; and
recording, by the update service, a request log for the device as an entry in the local ledger, and distributing blocks of transaction records to the blockchain broker service to maintain a distributed ledger to reproduce history of the device, wherein the request log includes a publisher identifier or a provider identifier.

### Claim 8

A method of building a device historian, across a supply chain of device manufactures and managers, by a plurality of device management services comprising an enrollment service, an update service, a policy service, and an analytics service, a transaction connector, a blockchain broker service participating as a node in a blockchain network, and transaction filters, the method comprising:
sending, by the plurality of device management services a transaction record over the transaction connector to the blockchain broker service;
receiving, by the blockchain broker service, the transaction record;
filtering, by the blockchain broker service, information in the transaction record based on the transaction filters;
preparing, by the blockchain broker service, a versioned block based on the filtered information from the transaction record; and
adding, by the blockchain broker service, the versioned block to the blockchain network.

### Claim 9 (depends on 8)

The method of claim 8, wherein the versioned block is configured for a specific industry sector by operation type, and with at least one of a device, application and operator as an entity, wherein the operator comprises at least one of a portal user and service user.

### Claim 10 (depends on 8)

The method of claim 8, wherein the versioned block is configured to track a chain of custody of the device based on a trust chain of a root certificate, a platform certificate, and an owner certificate.

### Claim 11 (depends on 8)

The method of claim 8, wherein the versioned block is configured to track applications on the device based on a trust chain of a root certificate, a platform certificate, an owner certificate, and a service certificate.

### Claim 12 (depends on 8)

The method of claim 8, wherein the versioned block is configured to track supply chain provenance of device update packages based on a trust chain established across a plurality of provider certificates, a publisher signing certificate, and a device encryption certificate.

### Claim 13 (depends on 12)

The method of claim 12, wherein the versioned blocks are in a distributed ledger of the blockchain network and are used to trace a history of device management operations orchestrated across the supply chain from a silicon fabrication plant, an original equipment manufacturer, a device owner, a device management service of the plurality of device management services, and in-field operations.
