> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/getting-started/tutorials/technical-overview/uplink-communication.md).
# Uplink communication
When data is sent from device to KPN Things
KPN Things Data Management is a data processing platform that enables you to connect all your KPN Things devices to all supported destinations through one standard way of data processing. This principle is visualized in the diagram below:
## Device support
Read more on device support:
{% content-ref url="/pages/Of3VVQZTjDcx0jEELZoy" %}
[Supported devices and KPN Devices](/kpn-things/getting-started/tutorials/connect-devices/supported-devices-and-kpn-devices.md)
{% endcontent-ref %}
## Network support
KPN Things Data Management supports multiple forms of connectivity to receive data from devices. When you have a KPN Things device it is already configured to work with KPN Things Data Management.
Read more on connectivity support here:
{% content-ref url="/pages/sxmxLfIEOcEF8bZmLii6" %}
[LoRa connectivity configuration](/kpn-things/the-portal-explained/things-manager/connectivity/lora-connectivity-configuration.md)
{% endcontent-ref %}
## Processing
### Decode
During the optional decoding phase the device specific data protocol is transformed to the universal language of [SenML](/kpn-things/building-blocks/data-processing/thingsml-and-senml/senml.md). This is called decoding. Decoding for KPN Things devices and custom devices that use the KPN Things client libraries is taken care of automatically. Therefor there is automatic compatibility with the enrichment phase.
{% content-ref url="/pages/BKtmldnRctkCgXew35rl" %}
[Decoders and encoders](/kpn-things/building-blocks/data-processing/decoders-and-encoders.md)
{% endcontent-ref %}
### Enrich
In future releases KPN will introduce data enrichment functionality in KPN Things Data Management.
## Destination support
After processing your data will be forwarded to one or more Destinations you have configured.
{% content-ref url="/pages/MTpJNwuPcGVb6qjQqjPq" %}
[Destinations](/kpn-things/the-portal-explained/things-manager/destinations.md)
{% endcontent-ref %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kpnthings.com/kpn-things/getting-started/tutorials/technical-overview/uplink-communication.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
