Secure data orchestrator for IoT networks

A system, comprising:

• one or more computer processors;
• and
• a non-transitory memory containing computer program code that, when executed by operation of the one or more computer processors, performs an operation comprising:
• receiving, at a data orchestrator, from an endpoint device, a plurality of data values collected by the endpoint device;
• determining an identifier that uniquely identifies the endpoint device;
• accessing one or more routing tables using the determined identifier and device type data corresponding to the plurality of data values to determine one or more data consumers to route the plurality of data values to, wherein the one or more routing tables were dynamically generated based on at least one of (i) device claim information relating to the endpoint device, (ii) license data relating to the one or more data consumers, and (iii) user information associated with the one or more data consumers;
• and
• transmitting, by the data orchestrator, at least a portion of the plurality of data values from the endpoint device to the determined one or more data consumers for consumption,
• wherein the endpoint device comprises one of a plurality of Internet of Things (IoT) devices within an IoT network, and different layers of IoT stack are decoupled from each other within a tenancy context to allow sharing of data between tenancy stovepipes.

A non-transitory computer-readable medium containing computer program code that, when executed by operation of one or more computer processors, performs an operation comprising:

• receiving, at a data orchestrator, from an endpoint device, a plurality of data values collected by the endpoint device;
• determining an identifier that uniquely identifies the endpoint device;
• accessing one or more routing tables using the determined identifier and device type data corresponding to the plurality of data values to determine one or more data consumers to route the plurality of data values to, wherein the one or more routing tables were dynamically generated based on at least one of (i) device claim information relating to the endpoint device, (ii) license data relating to the one or more data consumers, and (iii) user information associated with the one or more data consumers;
• and
• transmitting, by the data orchestrator, at least a portion of the plurality of data values from the endpoint device to the determined one or more data consumers for consumption,
• wherein the endpoint device comprises one of a plurality of Internet of Things (IoT) devices within an IoT network, and different layers of IoT stack are decoupled from each other within a tenancy context to allow sharing of data between tenancy stovepipes.