TWTG Documentation
Service Desk
Starting Guide
Starting Guide
  • Introduction
  • LoRa & LoRaWAN
    • LoRa
      • LoRa vs WirelessHART
      • LoRa vs BLE
    • LoRaWAN
      • Infrastructure
  • Installation & Provisioning
    • Box Content
    • Installation
      • Pressure Gauge (PG)
      • Pressure Sensor (PS)
      • Temperature Sensor (TS)
      • Temperature Transmitter (TT)
      • Vibration Sensor (VB)
      • Contact Sensor (VS-CS)
      • Valve Sensor - Multiturn (VS-MT)
      • Valve Sensor - Quarter Turn (VS-QT)
    • Provisioning
      • 📄Step 1: Product manual
      • 🔑Step 2: Identify the keys
      • 💻Step 3: Add the device to the LNS
      • ⚙️Step 4: Encoder & Decoder in the LNS
      • 🟩Step 5: Activating the device
  • Data & Communication
    • Communication Protocol
    • Measurements & Messages
    • Schedules
    • Data Visualization
  • Configuration
    • Online Configurator
    • Configure a Device
  • How-to
    • General
      • How to troubleshoot a NEON device not connecting to the network
      • How to fix a bad connection
      • How to replace a battery
    • Pressure Gauge (PG)
      • How to configure event triggers
    • Pressure Sensor (PS)
      • How to configure event triggers
    • Temperature Sensor (TS)
      • How to configure event triggers
      • How to change the configuration of the device from using FSB1 to FSB2 in US915
      • How to configure the frequency of measurements and messages
    • Temperature Transmitter (TT)
      • How to configure event triggers
      • How to use a temperature element different from type K
      • How to use a PT100/RTD
      • How to configure the frequency of measurements and messages
    • Vibration Sensor (VB)
      • Communication Protocol v2 & v3
        • How to obtain the FFT data
        • How to have an FFT for threshold values without periodic messages
        • How to configure event triggers
      • Communication Protocol v4
        • How to Get Started with the New Features of the NEON Vibration Sensor v4
      • How to configure the frequency of measurements and messages
      • How to replace the sensor or probe
      • How to debug a not connected sensor
      • How to debug a not paired sensor
      • How to enable Hanning Window
  • General Information
    • Available Regions
    • LoRaWAN Region
    • Hazardous Locations
    • Device Maintenance
    • Support & Troubleshooting
    • FAQs
Powered by GitBook
On this page
  • LoRa Network Server
  • Application Server
  • Join Server
  1. LoRa & LoRaWAN
  2. LoRaWAN

Infrastructure

PreviousLoRaWANNextBox Content

Last updated 1 year ago

The NEON devices communicate using LoRaWAN; these are the "end devices" or "sensors" in a LoRaWAN infrastructure. They send data over LoRa which is forwarded by a gateway to the LoRa Network Server for processing. TWTG's NEON devices are specially designed for Industrial Internet of Things (I-IoT) infrastructures using LoRaWAN.

For more information on LoRaWAN please visit the .

LoRa Network Server

A LoRa Network Server (LNS) is a crucial component in a LoRaWAN architecture. It serves as the central point of control and management for LoRa devices within a LoRa network. The primary functions of a LoRa Network Server include:

  1. Communication Handling: The LNS facilitates communication between LoRa devices and the application servers. It receives data from devices, processes it, and forwards it to the appropriate application server for further processing or storage.

  2. Network Control: The LNS monitors the network health and controls various parameters to optimize network performance, such as data rate, frequency channels, and transmission power.

  3. Security: The LNS ensures the security of communication between LoRa devices and the network by implementing encryption and authentication mechanisms.

  4. Integration with Application Servers: The LNS interfaces with application servers, which are responsible for processing and analyzing data received from LoRa devices. It forwards data from devices to the appropriate application server based on predefined rules and protocols.

Application Server

The application server manages the LoRaWAN application layer, which involves tasks like decrypting and decoding uplink data, queuing downlink messages, and encoding downlink data with encryption.

The application server is capable of decoding and encoding binary payloads transmitted to and from end devices. This facilitates the handling of structured streaming data, such as JSON objects via MQTT and HTTP webhooks, while efficiently utilizing compact binary data for transmission over the air.

Join Server

The join server within a LoRaWAN network oversees the over-the-air activation (OTAA) procedure employed for incorporating end devices into the network. It holds the essential data for handling uplink join request frames and downlink join accept frames. Moreover, it serves as the crucial network element responsible for deriving both network and application session encryption keys.

LoRa Alliance website
Example of an I-IoT infrastructure