Application Streaming
Application Notifiers allow data from an Application’s entire Device population to be securely forwarded to third parties; typically data-processing platforms that provide tailored aggregation, analysis and visualization services. The Notifier configuration provisions the third party’s end-point communication requirements, enabling the Network Server to establish and maintain the northbound data stream.
Selecting "Add Target" from the button's dropdown menu launches the Notification Target edit dialog. Each Notification Target type has a set of common configuration options and a set of additional options that are unique to that target. Some target types do not support all of the common options, so these options may not always be visible. Additional options to Edit and Delete are made available for existing Notification Targets. Application Providers may only create a single Notfication Target, but may edit or deleted any created for the Application Provider by the Network Operator.
Application Providers with only a single Application are not presented with a tabular view. Instead the Application Details view is presented. Notification Targets may be edited from the gear icon shown in the upper right corner of the side panel as shown here:
Configuration Options
The following options, displayed as checkboxes in the Notfication Target configuration dialog, toggle inclusion of the fields shown below in the data streamed to the Notification Target:
| Option | Description |
|---|---|
| Use Legacy Format | Use an older Notfication Target data format. |
| Batch Notifications | Group Notification messages before forwarding. |
| Duplicate Uplinks | Include all uplinks for Gateways hearing the Device. Note: this may significantly increase the amount of Northbound data. |
| RF Data | Include the RF fields: channel, datarate, freq, rssi and snr. |
| Type | Include the devType field. |
| Tags | Include the tags field. |
| Metadata | Include the metadata field. |
| LoRa Class | Include the devClass field. |
| Ack Flag | Include the ack field. |
| Firmware Version | Include the fwVersion field. |
| Configured Location | Include the cfgLat and cfgLng fields. |
| Estimated Location | Include the estLat and estLng fields. |
| Ack Downlink MsgId | Include the ackDnMsgId field. |
| Profile | Include the defProfile field. |
| Gateway Received Time | Include the gwRxTime field. |
Fields
The following fields are included in the data streamed to the Notification Target if enabled in the Notification Target configuration dialog:
| FieldName | DataType | Description |
|---|---|---|
| devEui | String | 64-bit Extended Unique Identifier of the Device transmitting the message |
| gwEui | String | 64-bit Extended Unique Identifier of the receiving Gateway that processed the message |
| joinId | Number | Incrementing Integer used to Identify the last join |
| pdu | String | Protocol Data Unit or Customer Payload data |
| port | Number | 0 indicates that the FRMPayload contains MAC commands only and 1..223 are Application specific |
| seqno | Number | Incrementing integer used to identify an uplink |
| txtime | String | Time the message was received by the Network Server |
| channel | Number | Frequency Channel of the transmission |
| datarate | Number | Integer that maps to a spreading factor, bandwidth and bitrate |
| freq | Number | Transmit Frequency in MHz |
| rssi | Number | Received Signal Strength Indicator reported by receiving Gateway |
| snr | Number | Average Signal to Noise Ratio reported by receiving gateway |
| ack | Boolean | Flag indicating if the uplink was acknowledging the receipt of a downlink |
| ackDnMsgId | Number | When present, indicates that a Device has acknowledged a specific downlink message ID |
| devClass | String | LoRaWAN Class designation ("A", "B", "C") of the Device |
| devType | String | The type of the Device |
| dup* | Boolean | Flag indicating if the uplink was already forwarded because it was heard by multiple Gateways |
| estLat* | Number | Estimated latitude of the Device in decimal degrees |
| estLng* | Number | Estimated longitude of the Device in decimal degrees |
| cfgLat | Number | Configured latitude of the Device in decimal degrees |
| cfgLng | Number | Configured longitude of the Device in decimal degrees |
| tags | String | A comma separated list of tags configured on the Device |
| metadata | String | The metadata value configured on the Device |
| devProfile | String | The name of the Profile applied to the Device |
| fwVersion | String | The firmware version of the Device |
| gwRxTime | String | Time the message was received by the gateway |
* Requires contractual agreement
Notification Target Types
There are several supported Application Notification Target types:
Each type has unique configuration options.
HTTP
| Field | Description |
|---|---|
| URL | The destination URL where messages will be sent |
| Header Key(s) | Optional HTTP header key to include with sent messages |
| Header Values(s) | Value to include with the associated header key |
Senet Packet
| Field | Description |
|---|---|
| Uplink URL | The destination URL where messages will be sent |
| Downlink URL | URL where Downlink messages will be sent |
| Join URL | URL where Join specific messages will be sent |
| Encoded API Key | An API key used to provide access to the message destination |
| Header Key(s) | Optional HTTP header key to include with sent messages |
| Header Values(s) | Value to include with the associated header key |
MQTT
| Field | Description |
|---|---|
| SSL/TLS | Indicates whether to use secure communication protocols for messages |
| Client ID | A unique ID for the message sender |
| Broker Address | The address where messages will be sent |
| Broker Port | The port number where messages will be sent |
| Publish Topic | A topic ID for filtering sent messages |
| Subscribe Topic | A topic ID for filtering received messages |
| Username | A username used to authenticate with the message server at the Broker Address |
| Password | A password used to authenticate with the message server at the Broker Address |
AWS API Gateway
| Field | Description |
|---|---|
| Server Name | The name of the AWS server where messages will be sent |
| Function Name | The name of the target function that will be executed on received messages |
| API Key | The encoded key used to provide access to the AWS server |
| Token | An optional token to pass to the AWS server API |
TagoIO
TagoIO uses an authentication token to enable data forwarding to its respective services. No additional configuration options are required.