Samsung SAMI is a Data-driven Development (D3) platform for receiving, storing and sending data to/from IoT devices. Any device can send data in various formats which is then normalized into a JSON format and stored in the cloud. Data can then be requested by other devices.
SAMI operates with the following concepts:
- Device – any source of data - sensors, appliances, applications, services, etc.
- Device Type – a category of devices, such as Samsung Galaxy Gear Fit
- Device ID – the unique ID associated to a device instance
- Message – a piece of data and its associated metadata sent by a device to SAMI or other devices
- Authorization – SAMI uses OAuth2 to authenticate users
- Manifest – a data interpreter, one for each device type, used for data normalization. There is a simple manifest and an advanced manifest. The simple one is created with a web form and it is used to interpret JSON data sent to SAMI, while the advanced one is a script written in Groovy. The latter needs to be approved by Samsung which can reject a manifest if it attempts something malicious, it leaks memory, etc.
Data can be later requested using REST or WebSocket API calls (API specification). There are currently some limitations on the number of such calls per device, per user or per application.
The SAMI platform provides a number of tools for developers: Developer Portal - a web-based interface for creating and managing device types and applications, User Portal – a tool enabling users to register devices and visualize their data, API Console – an online tool for executing API calls, and the Device Simulator - a command-line tool to send simulated messages to SAMI.
Samsung has published a number of sample applications for Android, iOS, Node.js, Arduino, and the browser (JavaScript) that show how to use SAMI. There are also a number of SDKs that help with the creation of applications in Java/Android, Objective-C/iOS, PHP, Python and Ruby.