KPN Things Developer Manual
↩ All Documentation
  • Welcome to the Things Developer Manual
  • Concepts
    • Overview
    • Uplink communication
    • Downlink communication
    • SenML
      • Upcoming Changes in KPN SenML
    • Management data model
    • Location data
    • API access ✨
  • Devices
    • Introduction to Devices
    • Supported developer kits
    • Supported device types
    • KPN Things devices
    • Device SDK
  • Connectivity
    • Introduction to Connectivity
    • KPN Things LoRa
    • KPN Things M2M
      • Firmware over the air 💎
    • Internet ✨
  • Processing
    • Introduction to Processing
    • ThingsML
    • Common measurements list
    • DIY Decoder 🔜
    • Merger 💎
    • Built-in decoders
  • Destinations
    • Introduction to Destinations
    • Azure Event Hub
    • Azure IoT Hub
    • Cumulocity environment
    • HTTPS endpoint
    • MQTT broker
  • 📗Additional resources
    • Things Portal Manual
    • Getting started
    • Contact Support
Powered by GitBook
On this page
  • Device integration
  • Application integration
  • Configuration / Management
  1. Concepts

Overview

PreviousWelcome to the Things Developer ManualNextUplink communication

Last updated 4 years ago

This is a technical overview of the KPN Things platform. If your are more interested in the overview of features, you can check out the .

The KPN Things Platform is the bridge between IoT Devices and IoT Applications. It offers a unified way of connecting Devices at the one side, and applications at the other side, making Devices and applications completely interchangeable in every IoT solution that uses KPN Things.

Device integration

When you use one of our networks to get your data in KPN Things, you will be able to do connectivity management in KPN Things.

Application integration

Configuration / Management

Devices can communicate with the platform using one of our networks, or , or a Device using another network can get its data to and from KPN Things over the .

Communication from your Device is called . When data or commands are sent to your Device, it is called . In the basis all communication with the KPN Things Platform should use the data protocol, but are available to translate data from and to Devices that do not support SenML.

KPN Things will connect to your application through a dedicated connection layer. To connect your application to KPN Things you can use one of the available . We have for instance support to connect plain to KPN Things, but if you are developing in Microsoft Azure, you can connect directly to the if you like.

The destination types that connect on a platform level can also provide the integration of certain configuration and management of objects in the platform. The for instance will create Device objects in the Cumulocity tenant for each Device that KPN Things sends data of.

The Configuration/Management component in KPN Things holds that enables successful data processing. Also it contains all information needed to correctly manage and monitor solution built in KPN Things.

The is the website through which you can manage and monitor almost all parts of the KPN Things solutions. Soon, you will also be able to use KPN Things API's directly to manage your IoT solutions.

LoRa
M2M (2G/3G/4G/LTE-M)
Internet
Destination types
HTTPS endpoints
Azure IoT Hub
Cumulocity connection
all data in its model
KPN Things Portal
overview page in the Portal documentation
uplink communication
downlink communication
SenML
data decoders
Solid line = IoT data. Dashed line = configuration/metadata.