> 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/kpn-lora/technical-information/messaging-capabilities.md).

# Messaging capabilities

The LoRaWAN protocol is capable of transferring sensor data or changing the behavior of an actuator. LoRaWAN can be used for both uplink (device to network) as well as downlink (network to device) messaging. Within LoRaWAN, there are three traffic categories defined:

| **Class**          | **Characteristics**                                                                                                                                                                                                                                 |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **A (all)**        | <p>Battery-powered sensors or actuators.</p><p>No latency constraint.</p><p>Focus on energy efficiency.</p><p>Must be supported by all devices.</p><p>Downlink message is triggered by an uplink message.</p>                                       |
| **B (beacon)\***   | <p>Battery-powered actuators.</p><p>Energy-efficient communication class for latency-controlled downlink.</p><p>Based on slotted communication synchronized with a network beacon.</p><p>Send 'actions' to a device with a few minutes latency.</p> |
| **C (continuous)** | <p>Mains-powered actuators</p><p>Devices that can afford to listen continuously.</p><p>No latency for downlink communication.</p><p>Listens for network «ping» for low-latency actuation.</p>                                                       |

> \*) The KPN LoRa service currently supports LoRaWAN Class A and C


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kpnthings.com/kpn-things/kpn-lora/technical-information/messaging-capabilities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.