System and method using a blockchain matrix

1. A system controller, comprising:

a processor;

a non-transitory memory comprising a blockchain matrix that comprises a static blockchain, where the static blockchain comprises a matrix genesis block and a plurality of subsystem genesis blocks, where the matrix genesis block comprises a first package of microcode that, when executed by the processor, configures the system controller for building live subsystem blockchains that are founded using the subsystem genesis blocks, where each subsystem genesis block serves as a genesis block of a different live subsystem blockchain and comprises a package of microcode that, when executed by a subsystem, configures the subsystem for operation within a system controlled by the system controller; and

a subsystem management application stored in the non-transitory memory that, when executed by the processor,

receives event blocks from the subsystems,

stores the event blocks to a live subsystem blockchain associated with the subsystem that generated the event blocks in the non-transitory memory, and

processes each of the event blocks of the live subsystem blockchain associated with a subsystem to generate a report on the operations of the subsystem.

2. The system controller of claim 1 , wherein some of the event blocks provide information about a communication session of a subsystem.

3. The system controller of claim 1 , wherein some of the event blocks provide information about execution of licensed software by a subsystem.

4. The system controller of claim 1 , wherein a genesis block of a live subsystem blockchain is associated with metadata that comprises a link to a next block in the static blockchain and a link to an event block on the live subsystem blockchain.

5. The system controller of claim 1 , wherein the subsystem management application further generates a bill for use of communication services by the subsystems associated with the system controller and transmits this bill to a communication service provider.

6. The system controller of claim 5 , wherein the subsystem management application further pays for the bill via a financial payment mechanism associated to the system controller.

7. A method of initializing a subsystem by reading microcode from a block of a static blockchain associated to the subsystem, executing the microcode to configure the subsystem, and building event blocks associated with the subsystem using the block of the static blockchain as a genesis block of a live subsystem blockchain, comprising:

reading a block associated to a subsystem by an application executing on a processor of the subsystem, where the block associated to the subsystem is one of a plurality of blocks in a static blockchain;

executing microcode of the block read by the application;

based on executing the microcode, configuring by the application the subsystem for operation within a system in which the subsystem is embedded;

creating an event block by the application, where the event block stores information about an event generated by the subsystem operating based on the configuration; and

attaching the event block to a live subsystem blockchain associated with the subsystem.

8. The method of claim 7 , wherein the block associated to the subsystem in the static blockchain is a subsystem genesis block and wherein the static blockchain and event blocks associated to the static blockchain establish a blockchain matrix.

9. The method of claim 7 , wherein the subsystem is one of an engine controller, a navigational system, or an entertainment system.

10. The method of claim 9 , wherein the system is one of an automobile or a pickup truck.

11. The method of claim 7 , wherein configuring the subsystem for operation comprises configuring the subsystem to access communication services via the system.

12. The method of claim 11 , wherein configuring the subsystem to access communication services comprises configuring the subsystem to access communication services according to a service level agreement (SLA) defined in the microcode.

13. The method of claim 7 , wherein configuring the subsystem for operation comprises configuring the subsystem to generate a billing report based on reading event blocks on the live subsystem blockchain.

14. The method of claim 13 , further comprising generating a billing report associated with licensed software executed on the subsystem based on event blocks on the live subsystem blockchain that capture events related to use of the licensed software.

15. A subsystem, comprising:

a processor;

a non-transitory memory; and

an application stored in the non-transitory memory that, when executed by the processor:

reads a block associated to the subsystem, wherein the block is one of a plurality of blocks in a static blockchain,

executes microcode read from the block,

based on executing the microcode, configures the subsystem for operation within a system in which the subsystem is embedded,

creates an event block that stores information about an event generated by the subsystem operating based on the configuration, and

attaches the event block to a live subsystem blockchain associated with the subsystem.

16. The subsystem of claim 15 , wherein the subsystem is one of an engine controller, a navigational system, or an entertainment system.

17. The subsystem of claim 15 , wherein configuring the subsystem for operation comprises configuring the subsystem to access communication services via the system.

18. The subsystem of claim 17 , wherein configuring the subsystem to access communication services comprises configuring the subsystem to access communication services according to a service level agreement (SLA) defined in the microcode.

19. The subsystem of claim 18 , wherein configuring the subsystem for operation comprises configuring the subsystem to generate a billing report based on reading event blocks on the live subsystem blockchain.

20. The subsystem of claim 15 , wherein the live subsystem blockchain is stored by the system.