Device Connectivity & Murano IoT-Connectors (Aka Products)
Murano Connectivity functionality provides a centralized control for devices configuration and provisioning. A single connectivity sub-domain is provided per instance of Murano IoT-Connector which usually pairs with a firmware version and a hardware model.
Table of Contents
- Get Started
- Useful Links
As is discussed in the Data Flow article, Murano internally represents real-world IoT components as the IoT-Connectors, Applications, and Integrations.
In general, most Murano users want to simply connect a Device to the cloud and start interacting with that Device remotely to create something valuable for end users or for a business process. However, there are many different types of Devices. Each type has a different level of processing/communication/storage capabilities and represents/controls different real-world parameters.
To make “connecting/interacting to a remote Device” a scalable effort for businesses, Murano uses the idea of a Device type (or Device model)—known as a Product—to define how Devices belonging to the IoT-Connector interact. IoT-Connectors, therefore, have multiple Devices associated with them (one IoT-Connector, many Devices). Once the behavior of the general IoT-Connector is defined, it is easy to start “stamping out” thousands of Devices that will interact as required by the IoT-Connector to which they belong. The representation and capabilities in Murano of a given Device are often referred to by the industry as a “Digital Twin,” a “Device Shadow,” or a “Virtual Device.”
Because there are so many different possible IoT-Connectors variants (i.e. ranging from a simple sensor to a very capable gateway - each having varieties of processing, communications, storage, data representation, and control capabilities), each Murano IoT-Connector allows the configuration of its capabilities. Every Device interacts with Murano as defined its IoT-Connector’s configuration of these areas:
- Communications authentication method
- Communications protocol
- Device identities/whitelist pool
- Expected communications behavior
- Expected data schema
- Data & State persistence
- Cloud-assisted processing
- User/Value-Added-Reseller access/control permissions
- Automated external Integrations
It is also often the case that an IoT-Connector will be used to power a variety of End User applications (Applications). For example, a Connected Pump Product may have some specific Pumps that are used in a container truck filling/dispensing application, while other Pumps (belonging to the same IoT-Connector) are used in a maintenance facility fluid transfer application. In Murano, an IoT-Connector is able to be used in a variety of Applications without changes to the underlying Devices – even when the Applications are created and maintained by business partners or customers.
Now what do you want to do?
Our supported hardware examples.