1st Introduction

SIM as an Identity

This feature is tailored to customers working with MQTT and want a native and direct connection with the AWS IoT Core without the hassle of provisioning and enrolling their devices.

The SIM-as-an-Identity Solution is part of the 1NCE IoT Connectivity Suite and allows customers a seamless and fully automated device onboarding for the AWS IoT Core (other platforms will follow).

Customers who want to use this solution require an active AWS Account connection to be available in the 1NCE Customer portal. More detailed steps on how to set up and connect an AWS Account can be found here 1NCE Rules Engine.

The Service will set up, create and configure Device in the AWS IoT Core using a default Policy allowing devices to only connect to a device-specific topic using the 1NCE ICCID as ThingName in AWS. A full example of the used Policy can be found below in the References. All Things are onboarding using the AWS Root CA.

The following picture shows a high-level flow of the Onboarding Flow:

Data Broker

This feature is tailored to customers working on LPWAN use cases that are not relying on MQTT as transport protocol, but still want to benefit from all the USPs of the AWS IoT Core. We offer seamless integration via UDP, CoAP, and soon Lightweight M2M as much more optimized alternatives to MQTT.

The core of the 1NCE IoT Connectivity Suite is a highly scalable Data Broker designed to process millions of messages in parallel extended by a range of Device Gateways to support different transport protocols.

Management and configuration of the Data Broker are handled via the Rules Engine in the 1NCE Customer Portal.

The main goal of the Data Broker is to provide a range of Endpoints for different Data Protocols and be able to translate data to be able to forward it to Cloud Platforms like the AWS IoT Core.

More details to be found in the Developer section.

Rules Engine

The Rules Engine as part of the 1NCE IoT Connectivity Suite allows customers seamless management of all settings and flawless configuration in the existing 1NCE Customer Portal.

The Rules Engine combines all administration task which needs to be done one-time or updated. Possible configurations include:

  • Dashboard => Providing a simple overview of the Status of the 1NCE IoT Connectivity Suite and Onboarding Guides
  • Rules Engine => Creating and managing Actions to process data and connect with available Backend Applications
  • Account Connection => Managing Cloud Platform connections and SaaS Applications to deliver data and act as identity providers for the Onboarding Service.
  • Downloads => Overview of 1NCE provided software, SDK, and Device Blueprints for use by the customer.
  • Documentation => Link to the 1NCE Documentation Page on the 1NCE Developer Hub.

More details to be found in the Developer section.

SDKs

1NCE offers different Blueprints and SDKs to allow customers a seamless setup and use of all features as part of the 1NCE IoT Connectivity Suite.

Blueprints

  • PyCom
    The Pycom onboarding blueprint enables a PySense, in combination with GPy, to communicate with the AWS IoT Core. This enables the functionality to subscribe and publish messages on the IoT Core, by making use of the SIM (IoT Device) specific certificates and keys.
  • STM32 with Quectel BG96
    FreeRTOS cellular is an implementation of Amazon FreeRTOS with cellular connectivity using the BG96 modem.

The more generalized FreeRTOS Cellular Library Demo (https://github.com/FreeRTOS/Lab-Project-FreeRTOS-Cellular-Demo) also allows an easy porting to any Microcontroller or Modem combination.

More details to be found in the Developer section.


Did this page help you?