Device Profiles
Device Profiles define how the Network Server manages the LoRa operational parameters of one or more Devices, including channel plan, data rate, and transmit power.
Setting Device Profiles
-
Profiles are set as part of Device registration or activation.
-
Device Profiles are enforced continuously. Once assigned they take effect upon successful join and through ongoing evaluation of all uplinks thereafter.
Adding Device Profiles
To add a new Device Profile click the 
button and fill in the required information.
To edit a Profile, highlight the row and click the 
button.
Base Settings
When editing or adding a Profile click on the 
to configure its base settings.
| Field | Description |
|---|---|
| Name | Descriptive name displayed in the Device and Application information associated with the Profile. |
| Application EUI | The EUI of the Application that this Profile is restricted to. |
| LoRa Version | The version of the LoRaWAN stack that the Device supports. |
| Join Device Class | The LoRaWAN Device class that the Device is after joining the network for OTAA Devices, or when it first uplinks the first time for ABP Devices. Default is Class A for LoRaWAN currently. The other options are Class B and Class C. |
| CFList Support | This option identifies the type of CFList allowed for use. The CFList is provisioned only when supported by the region the device is operating in. If Type 0 is selected, the CFList will be used for regions implementing dynamic channel plans (EU868, AS923, IN865, CN779, EU433, KR920 and RU864). The Type 1 CFList is only supported for regions implementing fixed channel plans (US915 and AU915). |
| Mobile | Currently not used |
| ABP Allow FCnt Reset | If enabled, this option allows the network server to still process uplinks for an ABP Devices that re-use a previously used FCnt. This can happen if an ABP Devices does not save its frame counter when it is rebooted. |
| Senet Packet Format | This option is used to tell if the Device sends uplinks with the Application payload in the Senet Packet Format, so it can be parsed into JSON and passed along as JSON. |
| 16 Bit Frame Counter | Enable if the Device only uses a 16 bit counter for its uplink and downlink frame counters and uses that to compute the MIC of uplinks and downlinks, instead of the required 32 bit counter. |
| Disable Downlinks | This option will stop the network server from ever sending a downlink to the Device. This is mainly used for testing how a Device will behave if you starve it of downlinks. |
| Ignore MIC | This option will ignore all uplink MICs and allow the network server to process the Application payload even if the MIC is being formulated incorrectly by the Device. This will NOT fix a corrupt Application session key. |
| Require Inc DevNonce | This option forces that a Device always increments its DevNonce on a join request, instead of using a random key. |
| Use Rx2 Only | This option will force the network server to always respond to the Device on RX2. |
| Set Alternate RX2 Params | This option enables sending alternate parameters in Class B downlinks. |
| Default TX Period(s) | The interval at which the Device is expected to transmit uplinks at. This is used for calculating PSR when packets were lost at the end of the day. |
| Deduplication Delay (% of RX1) | This setting provides a way to change the uplink deduplication resolution time. The default is 250ms (25% of default 1s RX1 delay). This allows the network server to receive from all gateways hearing a Device and elect the one whose RF can best respond to the Device. |
| Max Retransmits | The maximum number of retransmits that a Device can send prior to dropping the uplinks with the same sequence number. |
ADR Settings
When editing or adding a profile, click on the 
to configure its ADR (Adaptive Data Rate) settings.
There are three ADR engine types currently supported:
- Default - a more simplified ADR engine that provides a singular set of rules used factoring in PSR to DR changes.
- Experimental DataSR - an ADR engine implementation that allows a per DR configuration of PSR attributes to factor into changing the DR.
- V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy - an ADR engine that allows controlling Device network behavior by modifying TX Power, DR and NBTrans. The modification is controlled by evaluating SNR, DSR (Data Success Rate), PSR and redundancy.
Selecting an ADR engine determines which ADR configuration options are available. The ADR configuration options are shown in the following table, but may appear in a different position in the user interface based on the ADR engine selected.
| Field | Description | ADR Engine |
|---|---|---|
| ADR | Checkbox to tell if the Devices that use this profile support receiving the LinkAdrReq MAC command from the network server. | All |
| ADR Engine | The selected ADR engine determines the available ADR configuration options and resulting behavior when those options are applied. | All |
| Perform ADR on Channel Change | This flag controls whether the network server should perform an ADR re-evaluation if a Device is detected communicating on a channel outside its configured range. | All |
| Perform ADR on DR Change | This flag controls whether the network server should perform an ADR re-evaluation if the Device is detected communicating at a data rate different from its configured rate. | All |
| Alternate RX2 For ADRAck Response | This flag causes the network server to alternate responses. | All |
| Use NB Trans To Influence PSR | This flag allows the ADR engine to adjust NBTrans up when raising DR to allow for the Device to have a better PSR while still conserving battery. When the Device is at the lowest DR, this is used in conjunction with the "Max NB Trans @ Min DR" option to allow for better PSR. | V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy |
| Use TX Power To Conserve Battery | This flag allows the ADR engine to lower TX Power when the Device is at the highest DR and still behaving above desired expectations. | V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy |
| Use Degradation Recovery | This flag is used to lessen the amount of DR changes forcing a Device to a higher DR when its SNR is fluctuating, causing the Device to go to a higher DR for a short period of time. | V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy |
| TX Power | The maximum transmit power applied to the Device to override the default for the band it is operating in. This is not allowed to be higher than the band's maximum TX power. | All |
| NBTrans | The number of transmits to tell a Device to use to send each uplink to ensure it gets to the network server. | Default Experimental-DataSR |
| Max NBTrans @ Min DR | The maximum NBTrans that the ADR engine is allowed to enforce to a Device with bad PSR at the lowest DR. Enabling this option could have a negative consequence on battery life. | V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy |
| Min DR | The minimum data rate the network server is allowed to command the Device to use. | All |
| Max DR | The maximum data rate the network server is allowed to command the Device to use. | All |
| Allow Missed Before Lower DR | If configured this allows the network server to miss up to N uplinks, in an 11 uplink cycle. Even if the Device has poor SNR values for its uplinks, the Device will NOT be commanded to go to a lower data rate. | Default |
| Allow Missed Before Raise DR | This will stop the network server from raising the data rate if the Device lost more than N uplinks during an 11 uplink cycle. | Default |
| Lower DR if Missed More Than | The number of uplinks that can be missed to force the Device down to a lower data rate. If this is to 0, then if the Device misses any uplinks in its 11 uplink cycle, the Device will be commanded to a lower DR. This setting still obeys Min DR. | Default |
| Delay Channel Mask Uplink Count | The number of uplinks to wait after a Device joins before assigning a channel mask. This allows the SenRa LNS to select the optimal Base Stations hearing a Device to generate a more inclusive channel mask. | All |
| Required Redundancy | Allows for the ADR engine to factor in a desired redundancy when configuring the device's data rate. | V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy. |
| DR Behaviors | These settings allow for unique configuration of: Lower DR if Missed More Than, Allow Missed Before Lower DR, and Allow Missed Before Raise DR per DR the Device is currently at. IE: this is used to direct a Device to stay at a certain DR, unless it has outstanding PSR or stop it from going to a lower data rate unless it has a poor PSR. | Experimental-DataSR V2.0 - PSR, DSR, TX Power, NBTrans and Redundancy |
LoRa Regional Settings
When editing or adding a profile click on the 
to configure its LoRa region specific settings.
| Field | Description |
|---|---|
| ISM Band | This is used for regions where a Device might be heard on multiple bands. When set, the Network Server will only process uplinks on the designated band to ensure optimal ADR configuration. |
| Region | The LoRaWAN radio frequency region - as defined in the LoRaWAN Regional Parameters Specification - where the Device will be operating. |
| Region Parameters Version | Identifies the version of the LoRaWAN Regional Parameters specification that the Device operates in compliance with, according to its regional location. |
| Allow Join Reconfiguration | If enabled, allows the LNS to configure the RX 1 Delay, RX 1 DR Offset, and RX 2 DR in the join request. |
| Allow MAC Command Reconfiguration | If enabled, allows the LNS to use RXTimingSetupReq, RXParamSetupReq, TxParamSetupReq, DutyCycleReq, PingSlotChannelReq, and BeaconFreqReq MAC commands to be used to reconfigure a Device. |
| MAC Commands Prefer FPort 0 | If enabled or the MAC command length exceeds 15 bytes, the Senet LNS sends downlinks that only contain MAC commands in the Application payload and uses FPort=0. If this is not enabled, MAC only commands 15 bytes or less in length are sent to the Device in the fopts portion of the downlink. |
| Default | This column reflects the RF region's default values defined in the LoRaWAN Regional Parameters Specification that Devices are expected to employ when either joining the network via OTAA, or being provisioned onto the network via ABP. |
| Device Defaults | Configuring this column’s values allows the LNS to accommodate manufacturer settings for Devices that do not implement the LoRaWAN-specified regional defaults when either joining the network via OTAA, or being provisioned onto the network via ABP. |
| Override Settings | This column’s values define a target configuration the LNS will command after a Device successfully joins the network. For the duration of the Device Profile assignment, the LNS compares the Device's current state (as reflected by its uplinks) to these settings and will reassert this configuration to the Device via MAC commands accordingly. |
| RX1 Delay | The delay in seconds for the Device to wait after the transmitting a class A uplink to wait for the RX1 window of its Class A downlink. The RX2 delay is this delay plus 1 second. This setting can be set during the join of a Device or via a downlink of an RxTimingSetupReq. |
| RX1 DR Offset | The DR offset to be applied to the formula to figure out the DR to respond to the Device's uplink. This can be used with Asymmetric Link Budget to allow a Device to better hear downlinks. This setting can be set during the join of a Device or via a downlink of an RxParamSetupReq. |
| RX2 DR | The DR the Device should listen on for its RX2 reception window. This is also the DR used by Class C downlinks. This setting can be set during the join of a Device or via a downlink of an RxParamSetupReq. |
| RX2 Frequency | This is the frequency the Device should listen on for its RX2 reception window. This is also the DR used by Class C downlinks. This setting can only be set via a downlink of an RxParamSetupReq. |
| Dwell Time | This is the setting used to configure if the Device needs to obey a 400ms uplink and/or downlink dwell time. This setting is only applicable in some regions, such as AS923 and is only required in some countries within that region. This setting can only be set via a downlink of an TxParamSetupReq. |
| Duty Cycle | This is used to configure the maximum duty cycle that a Device should operate at. This can be used for Device that no longer have service to tune down the number of uplinks. This setting can only be set via a downlink of an DutyCycleReq. |
| Max EIRP | This value is used to configure the maximum EIRP a Device calculates it max transmit power from. The ADR algorithm is Max EIRP - (2 x LinkADRReq->TxPower). This setting can only be set via a downlink of an TxParamSetupReq. |
| Channel Mask | This is used to tell which channels a Device should configured to use. The value is a hexadecimal value where the binary representation of the value has a bit per channel, with channel 0 being the right most bit. For example, 06 would be represented as 00001010 in binary. This has channel 0 disabled, channel 1 enabled, channel 2 disabled, channel 3 enabled, and channels 4, 5, 6, 7 as all disabled. This setting can only be set via a downlink of a LinkADRReq. |
| Beacon Frequency | This is the frequency that a Class B Device should be listening on for acquiring a beacon. If this value is reconfigured, all gateways in the region of that Device needs to also be reconfigured to use that frequency for the beacon as well. This setting can only be set via a downlink of a BeaconFreqReq. |
| Ping Slot Frequency | This is the frequency that a Class B Device should be listening on for receiving a downlink on one of its ping slots. Setting this value in regions that require frequency hopping will cause the Device to only listen on the static frequency. This setting can only be set via a downlink of a PingSlotFreqReq. |
| Ping Slot DR | This is the data rate that a Class B Device should be listening on for receiving a downlink on one of its ping slots. This setting can only be set via a downlink of a PingSlotFreqReq. |
Channel Mask
In this section, the current settings for which channels are enabled or disabled are displayed and controlled, with respect to the following:
- Default: Expected default channel plan for the selected region.
- Device Defaults: Expected default channel plan for the Devices not compliant with the regional default.
- Override Settings: Channel plan to be commanded by LNS after the Device(s) successfully joins the Network.
Editing
For the US915 and AU915 fixed Channel Plan regions, the Device Defaults and Override Settings may be updated using a custom channel mask editor, indicated by the pencil icon to the right of the respective fields:
Clicking the pencil launches the editor, wherein the Channel Mask located at the top will dynamically update in response to changes:
The editor also supports filtering the list, making it easy to find and update specific channels:
For all other regions, the Channel Mask is directly entered as a 2 or 4-character hexadecimal string:
Estimated Location Settings
When editing or adding a profile click on the 
to configure its Estimated Location algorithm settings.
Options to select and configure the algorithms used to determine the estimated location of a Device are set in this section. Configuration options are only available for the Advanced - Signal Quality Influenced algorithm.
Algorithms
| Algorithm | Description |
|---|---|
| Basic - Simple Location Average | Centroid of the Base Stations hearing the Device. |
| Advanced - Signal Quality Influenced | This algorithm uses the Base Station RSSI value to weight an uplink. Base Stations with a better RSSI will be weighted slightly higher and shift the Device location in that direction. Each RSSI weighted location is added to a running total. |
Advanced Algorithm Options
| Option | Description |
|---|---|
| Mobility Type | Fixed - The Device is positioned at a fixed location and is not expected to move. Nomadic - The Device infrequently moves from location to location. Mobile - The Device frequently moves from location to location. |
| Write Location to LoRa Events | Toggle inclusion of the Device location in the LoRa Events. Required to show the Estimated Location view in Device Details. |
| Only Use In-Service and Maintenance Base Stations | Toggle inclusion of Base Stations by Administrative Status |
| Ignore Threshold(miles) | Ignore positional changes in location exceeding this value. |
| Base Stations to Include | Owned - Include owned Base Stations in location calculations. LVN - Include Base Stations that are members of the LVN in location calculations. |
| Reset Triggers | SeqNo - Reset estimated location calculations if the uplink sequence number exceeds this value. Duration- Reset estimated location calculations after this many minutes. Distance(miles) - Reset estimated location calculations if the location changes by this many miles. |