Getting Started Devices Gateways The Things Stack Integrations Reference
Get The Things Stack

Reference

    Overview
  • Adaptive Data Rate
  • API
  • Application Packages
  • Billing with Stripe
  • Command-Line Interface
  • Components
    • Application Server
    • Command-line Interface
    • Console
    • Device Claiming Server
    • Device Template Converter
    • Gateway Configuration Server
    • Gateway Server
    • Identity Server
    • Join Server
    • Network Operations Center
    • Network Server
    • Packet Broker Agent
    • Tenant Billing Server
  • Configuration
  • Data Retention and Privacy
  • Device Claiming Configuration
  • Email Templates
  • Federated Authentication
  • Frequency Plans
  • FUOTA
  • Gateway RTT
  • Glossary
  • ID and EUI Constraints
  • Last Activity
  • LoRa Basics Station Implementation Guide
  • LoRaWAN Join Server Configuration
  • Packet Broker Routing
  • Packet Forwarders
  • Rate Limiting
  • Resource Limiting
  • Root Certificates
  • Telemetry
  • The Things Network

Application Server

The Application Server handles the LoRaWAN® application layer, including uplink data decryption and decoding, downlink queuing and downlink data encoding and encryption.

It hosts an MQTT server for streaming application data, supports HTTP webhooks as well as pub/sub integrations.

Connectivity

Applications can connect to Application Server over multiple protocols and mechanisms.

MQTT Protocol

Applications can connect to an Application Server by exchanging JSON messages over MQTT. MQTT is available over TLS, providing confidentiality of messages exchanged between applications and the Application Server.

The upstream messages do not only contain data uplink messages, but also join-accepts and downlink events, on separate topics.

See Application Server MQTT server for more information.

HTTP Webhooks

Applications can get streaming JSON messages via HTTP webhooks, and schedule downlink messages by making an HTTP request to the Application Server.

Like MQTT, all upstream messages can be configured, including uplink messages, join-accepts and downlink events, each to separate URL paths.

See HTTP webhooks for more information.

Pub/Sub Integrations

Applications can also use pub/sub integrations to work with streaming data. This includes connecting to an external MQTT server and NATS server.

Message Processing

The Application Server can decode and encode binary payload sent and received by end devices. This allows for working with structured streaming data, such as JSON objects using MQTT and HTTP webhooks, yet using compact binary data that is transmitted over the air.

Message processors can be well-known formats or custom scripts, and can be set on the device level, or for the entire application.

← Components Command-line Interface →

On this page

  • Connectivity
  • Message Processing

The Things Stack

Getting Started

Devices

Gateways

The Things Stack

Integrations

Reference

Contributing

GitHub

About Us

The Things Industries