Gateway Settings

Gateway Settings

LoRaWAN Settings

Mode Settings

There are three optional modes for LoRaWAN:

• Packet Forwarder (Data Packet Forwarding Mode)
• Basics Station Mode (Class B devices not supported temporarily)
• Built-in Server Mode

Packet Forwarder (Data Packet Forwarder) Mode

Packet Forwarder provides the most basic LoRa data packet forwarding function and does not process content related to the LoRaWAN protocol itself. It only performs data forwarding. For example: After the gateway receives RF (Radio Frequency) data packets (uplink data) sent by end devices, the Packet Forwarder will forward these data packets, along with metadata added by the gateway (such as gateway ID, signal strength, etc.), to the LoRaWAN Network Server (LNS) through a secure IP link. Conversely, when the network server has data to be sent to end devices (downlink data), the Packet Forwarder will also receive these data packets through the same IP link, convert them into radio frequency signals, and send them to the corresponding end devices.

Basics Station Mode

In addition to basic data forwarding functionality, LoRa Basics Station offers several additional features:

• Comprehensive support for communication modes: It supports two communication modes in LoRaWAN, namely Class A and Class C. Class A enables end devices to perform bidirectional communication with the server on demand; Class C keeps end devices' receive windows open for as long as possible, making it suitable for scenarios requiring timely responses to downlink data.
• Centralized management: It features centralized update and configuration management capabilities. Basics Station regularly contacts a separate Configuration and Update Server (CUPS) to check for configuration or software updates, which can even include updates to the underlying operating system. Furthermore, it supports centralized channel planning management, where channel plans and other network parameters are centrally managed by the network server, and Basics Station reads these parameters when establishing a connection.
• Diverse authentication methods: The LNS (LoRaWAN Network Server) and CUPS authenticate Basics Station using TLS (Transport Layer Security). Meanwhile, Basics Station can also use token-based authentication schemes. For embedded gateways running on resource-constrained hardware, token-based schemes are more advantageous due to their lower resource requirements.
• No reliance on local time: Basics Station obtains time synchronization from the network server and does not require a local UTC (Coordinated Universal Time) clock. In Class B mode, it only needs to route the Pulse Per Second (PPS) signal to the concentrator. Synchronization between PPS pulses and global GPS time is achieved through negotiation with the network server, eliminating the need for a GPS module's NMEA interface or other types of interfaces (if a GPS module is available, its information can be used to enhance device health status information).

Built-in Server Mode

The LoRaWAN gateway integrates a lightweight network server, which is referred to as the Built-in Server Mode. It has the following characteristics:

• Convenient Deployment: There is no need to build an additional independent network server. After the device is powered on, a small-scale LoRaWAN network can be quickly established. This mode is suitable for beginners or users who are not very familiar with network setup, greatly simplifying the configuration process.
• Local Data Processing: In scenarios where data isolation and security requirements are extremely high, or where data only needs to be stored and used locally (such as single-point deployment scenarios like individual factories or greenhouses), the Built-in Server Mode can directly collect and process data locally. There is no need to transmit data to a public network server, which improves the response speed of data processing and enhances data security to a certain extent.

Frequency Band Settings

In the frequency band settings, the following frequency bands can be selected, which are:

• FSB1, channel 0~7, 64
• FSB2, channel 8~15, 65
• FSB3, channel 16~23, 66
• FSB4, channel 24~31, 67
• FSB5, channel 32~39, 68
• FSB6, channel 40~47, 69
• FSB7, channel 48~55, 70
• FSB8, channel 56~63, 71

Please select a suitable frequency band plan according to local regulations for the region of use.

Data Filter

If you have a large number of node devices connected and need to filter the node data of a specific part, you can enable the whitelist mode and add relevant values to the whitelist. The node data of the added nodes can be received.

The whitelist provides two methods: Join EUI and Network ID.

Multi-Gateway Settings

On the Multi-Gateway Settings page, you are allowed to add multiple gateways. Typically, this function is used when adding blind-filling gateways to address poor signal quality.

Among the configuration items, the Gateway EUI is the most important identity verification number and must not be filled in incorrectly.

Data Statistics

On the Data Statistics page, data is statistically analyzed by application quantity, signal quality, data packets, and other metrics.

System Information

On the System Information page, various internal information of the gateway is provided for viewing. You can also modify the gateway's system time here.

Meanwhile, interfaces for functions such as firmware update are reserved. However, the firmware update function is not available at present, and a dedicated update software must be used to update the firmware.