Typical Workflow for Connecting Non-IP Devices
Non-IP devices indirectly connect to Oracle Internet of Things Cloud Service through a third-party cloud service. Oracle Internet of Things Cloud Service uses connectors to receive and process the data from such devices.
Use case: Orange offers LoRa network connectivity and exposes cloud service APIs for HTTP and MQTT connectivity. These APIs can be used to obtain the devices' telemetry data
Typical workflow for connecting non-IP devices in a LoRa network with Oracle Internet of Things Cloud Service
Task | More Information | Description |
---|---|---|
Subscribe to an Oracle Internet of Things Cloud Service instance. |
Purchase a subscription to Oracle Cloud, set up an Oracle Internet of Things Cloud Service instance, and then access it. |
Get Started with Oracle Internet of Things Cloud Service Applications |
Review the built-in connectors and identify the type that's required for your devices and their network. |
Built-in connectors includes generic, OrangeLora, and ProximusLora. | |
Create a connector, select its type, and configure it. |
Based on the type of connector, enter appropriate credentials, grammar, URL, API-Key, and other details. |
|
Verify that the connector has started. |
Oracle Internet of Things Cloud Service automatically starts the connector and displays its status on the Connectors screen. |
|
Upload the required device models for all the device types. |
A device model is an interface that helps the connector to identify the structure and the meaning of the device data content. |
|
Create an interpreter or create an interpreter at runtime when the connector receives a device notification . |
When you configure an interpreter, you specify its selection criteria, a device model, and the payload processing information. For each device type, you create an interpreter. |
|
Review the device registration. |
The connector obtains telemetry information by subscribing (MQTT) or periodically polling (HTTP). It registers a device and converts the payload data into device messages based on the envelope and payload processing information that you provide. |