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
  • Client
  • Project
  • Flow
  • Device
  • Destination
  1. Concepts

Management data model

Explaining the data model of the platform.

PreviousUpcoming Changes in KPN SenMLNextLocation data

Last updated 4 years ago

  • Green bordered blocks are objects provided to you.

  • Green filled blocks are objects you can create and manage.

  • Grey bordered blocks are objects globally managed by the system.

Client

If you have an account on KPN Things Data Management, it belongs to a client. All main objects in the KPN Things Data Management belong to a client: projects, devices, plugs and network subscriptions.

Project

Each Project defines a solution you buy or build in KPN Things.

Flow

With a Flow - previously known as (device) group - you link one or more devices to one or more plugs. So, if data is received from a device in a device group, it's data will be forwarded to the plugs that are in the same device group.

A project has one or multiple activated decoders and encoders. These decoders prescribe which decoders should be used when data is received by a device that is in a device group that belongs to this project.

Device

A Device represents a single physical device that can send data to the platform. When creating a device you tell the system the device specification it belongs to.

For a device, you can create a Network info for each supported network type of the given device specification.

Destination

A Network subscription contains information for network types for a specific client. .

A Device specification has one or multiple supported network types. For all our supported device types, go to the .

A Destination - previously known as plug - allows you to forward the data from your devices to an external system. For detailed information please read the .

Learn more about connectivity types
supported devices page
introduction to Destinations page