ns.dev-addr-prefixes: Device address prefixes of this Network Server
ns.net-id: NetID of this Network Server
ns.cooldown-window: Time window starting right after deduplication window, during which, duplicate messages are discarded
ns.deduplication-window: Time window during which, duplicate messages are collected for metadata
ns.downlink-priorities options configure priorities Network Server assigns downlinks when scheduling them on Gateway Server. In case when several downlinks are available for scheduling, Gateway Server will schedule higher priority downlink first.
ns.downlink-priorities.join-accept: Priority for join-accept messages (lowest, low, below_normal, normal, above_normal, high, highest)
ns.downlink-priorities.mac-commands: Priority for messages carrying MAC commands (lowest, low, below_normal, normal, above_normal, high, highest)
ns.downlink-priorities.max-application-downlink: Maximum priority for application downlink messages (lowest, low, below_normal, normal, above_normal, high, highest)
ns.default-mac-settings options configure default device MAC configuration parameters Network Server uses if not configured in device’s MAC settings.
ns.default-mac-settings.adr-margin: The default margin Network Server should add in ADR requests
ns.default-mac-settings.class-b-timeout: Deadline for a device in class B mode to respond to requests from the Network Server
ns.default-mac-settings.class-c-timeout: Deadline for a device in class C mode to respond to requests from the Network Server
ns.default-mac-settings.desired-rx1-delay: Desired Rx1Delay value Network Server should use
ns.default-mac-settings.status-count-periodicity: Number of uplink messages after which a DevStatusReq MACCommand shall be sent by Network Server
ns.default-mac-settings.status-time-periodicity: The interval after which a DevStatusReq MACCommand shall be sent by Network Server
ns.interop options configure how Network Server performs interoperability with other LoRaWAN Backend Interfaces-compliant servers.
ns.interop.config-source: Source of the interoperability client configuration (directory, url, blob)
ns.interop.blob.bucket: Blob bucket, which contains interoperability client configuration
ns.interop.blob.path: Blob path, which contains interoperability client configuration
ns.interop.directory: OS filesystem directory, which contains interoperability client configuration
ns.interop.url: URL, which contains interoperability client configuration
In multi-tenant deployments, the Network Server maintains strict isolation of traffic for different tenants. When it also has peering configured, the Packet Broker is typically configured with the correct tenant ID for the DevAddr ranges of each tenant. It is also possible to accept traffic from the Packet Broker without a tenant ID, and let the Network Server match devices without strict tenant isolation.
ns.switch-peering-tenant-context: Switch tenant context in peering