Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Using IoT Device Manager

Sync for IoT is currently in Developer Preview, which means access is by invite only. If you'd like to try what you see in these docs, sign up for the developer preview and the team at Twilio will get you onboarded as soon as possible.

The IoT Device Manager organizes resources of your device registry according to the domain model that includes: Devices, Deployments, Fleets, Certificates and Keys. The illustration below sketches out an example IoT application that uses Twilio for Deployed Devices following the above model.

Twilio for Deployed Devices - Recycling Application

In our example application above, we are setting up a fleet of connected devices in order to run an optimized waste recycling process. Our devices are comprised of a set of garbage trucks equipped with GPS receivers, and a set of smart containers equipped with sonars, both characterized by specific data access patterns. Since the device datasets and instructions are different, we are configuring the devices to belong to two distinct deployments, each linked to their own Sync service instance. In order to authenticate, establish unique identity, and authorize access to data for depoyed devices, the fleet is instrumented with individual device certificates.

The diagram below illustrates relationships between IoT Device Manager resources in a more formal manner.

Twilio for Deployed Devices - Domain Model

What next?

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.