Page tree
Skip to end of metadata
Go to start of metadata


This introduction section will introduce you to the deviceWISE IoT Platform. The deviceWISE IoT Platform helps you connect your things (the remote assets that you want to interact with) to your applications (the application services that you want to interface to your assets). The deviceWISE IoT Platform does this in a way that is easy to use and allows you to deploy production-ready solutions in a matter of weeks instead of months.



Platform overview

We begin with the deviceWISE IoT Platform basic design and architecture. This understanding provides a big picture while you are introduced to various features of the platform.

The deviceWISE IoT Platform is composed of three primary components:

  • The deviceWISE Asset Gateway
  • The deviceWISE M2M Service
  • The deviceWISE Enterprise Gateway.

Before you can decide how you want to use the deviceWISE IoT Platform to build an M2M application solution, it is important for you to review your M2M application solution requirements. These are a mix of your business requirements and your environment requirements.
The deviceWISE IoT Platform provides many different options for connectivity from the edge and from the enterprise, and it can be overwhelming trying to decide what option is the best for you when building an application solution.

Following are the key thoughts you need to keep in mind when using the deviceWISE IoT Platform:
(Note: this is just an example list, there will be specific questions that are the most relevant for your business and your application solution.)

  1. What kind of device do I need to use?
    • Am I using a COTS (commercial off-the-shelf) product or building a custom product?
    • Does my device require any kind of special IO or connectivity?
    • Does my device require cellular connectivity?
    • Does my device require dual network adapters?
    • Is my device capable of running the deviceWISE Asset Gateway software?
    • Do I have a C or JAVA environment capable of using the deviceWISE M2M Service API?
    • Do I have one of the Telit family of 910 modules that is capable of interfacing with the M2M Service?
  2. How am I going to get data into the cloud?
    • Am I using cellular connectivity?
      • Do I already have a cellular connectivity provider?
      • Does the deviceWISE IoT Platform have integration with my connectivity provider?
  3. What am I going to do with my data once its in the cloud?
    • Do I want to use simple web-based dashboards to monitor my devices?
    • Do I need to integrate the data with an enterprise application like SAP or Oracle?
    • Do I need to interface the data with a custom application that I created myself?

The following content should assist you with understanding how the deviceWISE IoT Platform provides solutions for the questions raised above.

deviceWISE M2M Service

The deviceWISE M2M Service (M2M Service) is a hosted service that handles all security, messaging, device management, and administration for your application solution. You configure and monitor the M2M Service using the web-based Management Portal. Here are the key features of the M2M Service:

Main Features

  • Connectivity
    • MQTT Interface (TR50 compliant)
      You can simply connect an MQTT client to the M2M Service either unencrypted or with MQTT over SSL (SSLv3 or TLS1+) for improved security. This is the preferred protocol to use for real-time or near-real-time performance. It is the only interface that supports subscribing to live feeds of data coming from devices.
    • HTTP(S) Interface (TR50 compliant)
      A JSON over HTTP interface is supplied that conforms to the TR50 standard. This interface tends to be the preferred interface for web applications.
      Note:  HTTPS requires SSLv3 or TLS1+
    • UDP Receiver (TR50 compliant)
      Send UDP messages to the M2M Service, this is ideal when using a platform that doesn't support TCP or where managing TCP connections will be too burdensome.
    • CloudSMS
      Send and receive SMS messages with ease to automate provisioning or notify your users when alarms occur.
  • Main Services
    • Connection Management
    • Provisioning Interfaces
    • Device Management
    • Alert Notifications
    • Rating Engine
    • Reporting Engine
    • License Management
    • Security Management
    • Management Portal
    • Developer Forum
    • Support Cases
    • Online Help
  • Data-at-Rest
    Built-in data warehouse for storing your device's sensor data, locations, alarms, etc.
  • Data-in-Transit
    Native integration with 3rd party enterprise systems from industry leading vendors such as IBM, Oracle, and SAP.

deviceWISE Asset Gateway

The deviceWISE Asset Gateway (Asset Gateway) is one of the essential components of many deviceWISE IoT Platform solutions. At its core, the Asset Gateway is software that communicates with your company's assets, processes any data, and sends the processed data either to the M2M Service, or to one of your enterprise applications via a deviceWISE Enterprise Gateway. The Asset Gateway is configured using the deviceWISE Workbench which lets you configure it with an innovative logic engine that enables rapid development of applications, eliminating time consuming custom application development and testing that accompanies many custom applications.

Below is a sample trigger:

Another key value proposition for the Asset Gateway is the availability of a robust library of drivers enabling communication with a wide variety of sensors and controllers commonly found in smart factories, buildings, and throughout the energy sector. Details about the available drivers can be found here: Device driver list

  • Asset Gateway software supports many platforms including the following:
    • B+B SmartWorx Spectre V3
    • CalAmp CDM-5030, LMU-5000, Vanguard
    • Cisco 829
    • Cisco IE 4000
    • Cypress CTM-200
    • Dell Edge
    • GateTel EZMoto
    • MultiTech OCG,
    • MultiTech MultiConnect Conduit
    • MultiTech MultiConnect rCell
    • NetComm Wireless Gateway
    • Option CloudGate
    • Red Lion Series 6000, 9000  (Pilot Ready)
    • Systech SL-500
    • USRobotics 3510
    • Vantron VT-M2M-LV
    • xmodus XM1710E  (Pilot Ready)
  • Asset Gateway software runs on the following operating systems to ease integration with your existing solutions:
    • Windows XP SP3, 7, 10
    • Linux 32-bit/64-bit.

deviceWISE Hosted Gateway

The deviceWISE Hosted Gateway uses the same software as the deviceWISE Asset Gateway and lets you connect remote devices that don't support communicating with the M2M Service directly. The Hosted Gateway can be deployed in your own data centers or can be co-resident with the M2M Service enabling rapid development of solutions that can "take over" existing deployments enabling seamless solution development between legacy and new systems.

Telit 910 Module AT Interface

If you are building a solution that uses the Telit 910 family of cellular modules, you can interface with the M2M Service via a set of simple AT commands. The API removes the need for complicated IP stack management from applications that can be run from a simple micro-controller. The agent running in the module manages the cellular connection and the connection to the M2M Service to make it as easy as possible to integrate your device with the M2M Service.

deviceWISE HTTP and MQTT Interface

If you don't want to (or can't) use the Asset Gateway or In-Module API, the M2M Service provides several interfaces to enable robust communication from a variety of programming languages. If you want to use a pre-packaged library, full source clients are available in C and JAVA. If you want to create your own client, the M2M Service Interface documentation describes the request and reply message formats. The M2M Service supports communication via HTTP and MQTT.

deviceWISE Enterprise Gateway

The deviceWISE Enterprise Gateway (Enterprise Gateway) is unique in the industry. Where most platforms only provide you with APIs so that you can write code to interface your enterprise applications, the deviceWISE IoT Platform goes a step further and provides enterprise-grade software that can be installed in your back-office and instantly map data from the deviceWISE IoT Platform to your enterprise applications.

Management and development tools

The deviceWISE IoT Platform has three main tools that you will use to build, manage, and deploy your applications. The following provides a brief introduction to those three tools.

The Workbench

The deviceWISE Workbench is the main tool that you will use to configure the Asset Gateways and the Enterprise Gateways. The Workbench provides full development capabilities and the ability to administer and debug an individual device in the field. It is also the same tool that is used to configure how to interface data to your enterprise applications through its easy to use click-to-configure features.

Following is a list of the most common tasks that you can perform using the Workbench:

  • Build, manage, and monitor triggers and projects
  • Configure and manage connections to devices and sensors
  • Configure network settings (both LAN and cellular)
  • Configure connection of the Asset Gateways and the Enterprise Gateways to the M2M Service
  • View logs and reports
  • Configure connections to enterprise application programs.

Management Portal

The deviceWISE Management Portal is a web-based program that is part of the M2M Service. Using the Management Portal, you can view and manage all of the devices that are connected to the M2M Service. In addition, the Management Portal lets you manage users, update firmware, and all of the other batch type processing you might want to perform on your field of devices.

Following is a list of the most common tasks that you can perform using the Management Portal:

  • Define and manage user accounts
  • Define the things that represent your remote assets
  • View usage reports and logs
  • Manage Asset Gateway and Enterprise Gateway firmware and software versions
  • Interact remotely with Asset Gateways and Enterprise Gateways
  • Connect to tunnel services provided by Asset Gateways and Enterprise Gateways.

Asset Gateway: Web Interface

The deviceWISE Asset Gateway: Web Interface is a specially designed web program that runs on the Asset Gateway. You can think of this tool like the configuration web program that is available on your home router. It is designed to be easy to use and to allow the person who actually installs the Asset Gateway to configure the network settings and the connections to the downstream assets.

Following is a list of the most common tasks that you can perform using the Asset Gateway: Web Interface:

  • Configure network settings (both LAN and cellular)
  • Configure connection of the Asset Gateway to the M2M Service
  • View basic event logs
  • Configure connections to downstream assets.

Common design patterns

Below you will find several of the most common implementation examples to help you further understand how the platform can be used to solve business problems.

The most important distinction between the first two patterns described is whether the Asset Gateway is running at the edge or in the cloud. If you are not running the Asset Gateway software at the edge, then you will be responsible for the edge component firmware management, modem management, sensor connectivity, and so forth.
The third pattern uses the Enterprise Gateway installed in your company's environment and is connected to the sensors or devices.

Asset Gateway at the edge

One of the most common design patterns involves deploying Asset Gateways at the edge, meaning installed at remote locations communicating to the Telit hosted M2M Service over either wired or wireless networks.

You will typically want to use this design pattern if you need to do a lot of edge processing of data prior to sending it to your applications. This pattern leverages the full capabilities of the Asset Gateway software, including:

  • Sensor and device driver library. To review the list of available device drivers, see Device driver list.
  • Edge processing of data
  • Store and forward capabilities
  • Modem management
  • Firmware and application version management.
Example 1: PLC connected to an Asset Gateway and connected to your application via the deviceWISE M2M Service

This first example shows how you could implement a solution requiring a programmable logic controller (PLC) to communicate with your application in your back office.

This example is representative of applications such as:

  • Demand-response power management
  • Industrial machine monitoring
  • Water treatment plant monitoring
  • Remote SCADA integration.

Example 2: Sensors connected directly to an Asset Gateway and connected to your application via the deviceWISE M2M Service

This second example is very similar to the first example. The main difference is that there is no PLC or other intelligent controller at the edge. The sensors are connected directly to the Asset Gateway and they communicate with your enterprise applications via the M2M Service just like the previous example. Most of the asset gateway hardware that Telit supports have 8-16 DI/DO channels, and 2-4 analog input channels for directly attaching I/O devices.

This example is representative of applications such as:

  • Simple power monitoring
  • Environmental monitoring
  • Tank level monitoring.

Asset Gateway In the cloud

You will typically use this design pattern if you have a large number of low-cost assets in the field that need to be monitored. In this model, you will be providing the software and hardware at the remote location that is sending data to the M2M Service. This model also works well for retrofit markets where you already have thousands of assets deployed in the field and you want to use the M2M Service, but not change any of the existing devices in the field.

Example 3: Smart asset talking to an Asset Gateway hosted within the deviceWISE M2M Service

This example is typical for many Telit telematic customers, where a device already exists that is deployed in the millions around the world, and you want to have that device send data to the M2M Service so that it can be processed. You can configure the device to send data to a hosted Asset Gateway, which, in turn, can send that data to an Enterprise Gateway, which will interact with your enterprise application. For example receiving a low fuel warning from a vehicle and sending that alert to an SAP system for dispatch.

This example is representative of applications such as:

  • Vehicle telematics
  • Power equipment monitoring (floor sweepers, riding lawnmowers, and so forth).

Enterprise Gateway communicating directly with sensors or devices within a company's LAN

This design pattern is typical for the industrial customer, where the plant floor device already exists and must be connected to an enterprise application. The Enterprise Gateway is installed in the company's environment and is connected to the sensors or devices. You can configure your Enterprise Gateway application to select data from the device and send it to an enterprise application; for example, PLC collected as-built data and counts can be sent to a relational database, such as Microsoft SQL Server, at every part completion.

Example 4: Devices or sensors connected directly to an Enterprise Gateway

This example is representative of applications that provide:

  • As-built data reporting
  • Production management via recipe download to the equipment
  • Replacement of older data collection system (for example, home grown or OPC systems)

Users for this example would use the Enterprise Gateway product. The Asset Gateway, Management Portal and M2M Service are not required.

That completes this platform introduction

If you have question about purchasing Telit products or services, contact your Telit representative.

If you would like to continue with a step by step instructional guide for application developers that covers many of the deviceWISE IoT Platform features, see Getting Started with deviceWISE IoT Platform.

If you are ready to proceed with your M2M solution development, see:


(C) Copyright Telit IoT Platforms, LLC 2006-2017. All rights reserved.

  • No labels