LoRaWAN® export file
The following table gives the packets information available in the LoRaWAN® export file. Most of the fields described are also accessible via ThingPark Tunnel Interface. To learn more, see LRC-AS Tunnel Interface Developer Guide.
From the export file, you can do several analysis such as:
-
Percentage of lost packets
-
Traffic per Logical Channel (LC)
-
Spreading Factor distribution per LRR base station
For more information about how to generate the export file, see Exporting packets.
| Metadata | Description |
|---|---|
| Direction |
|
| Timestamp | UTC timestamp in friendly format (YYYY-MM-DD hh:mm:ss.s). Example: 2021-01-30 05:06:07.0 |
| Timestamp(ISO) | UTC timestamp in ISO 8601 format (YYYY-MM-DDThh:mm:ss.sZ). Example: 2021-01-30T05:06:07.0Z |
| DevEUI | Device EUI (8 bytes) is a global end-device ID in IEEE EUI64 address
space that uniquely identifies the end-device.
If the network server acts as a forwarding network server (fNS) and the message type is data, the DevEUI is only available if LoRaWAN® Backend Interfaces version > 1.0. |
| DevAddr | Device address (4 bytes) on the network . |
| FPort | Application port of the packet. |
| FCnt | Frame counter of the packet. Can be Counter Up or Counter Down depending on the packet direction. |
| LRR RSSI | Received Signal Strength Indicator of the received packet on the best LRR side. Relevant only for uplink packets. |
| LRR SNR | Signal-to-Noise ratio of the received packet on the best LRR side. Relevant only for uplink packets. |
| LRR ESP | Estimated Signal Power of the received packet on the best LRR side. Relevant only for uplink packets. |
| SpFact | Spreading Factor of the uplink/downlink packet. |
| Sub Band | Radio frequency sub band corresponding to the logical channel used to transmit the uplink packet by the device. |
| Channel | Logical Channel used to transmit the uplink packet by the device. |
| LRC Id | Identifier of the LRC network server. |
| Relay Id | Identifier (DevEUI) of the LoRaWAN relay forwarding the end-device's packets. |
| LRR Id | Best LRR (LoRa base station) identifier. |
| LRR Lat | Latitude of the best-LRR. |
| LRR Long | Longitude of the best-LRR. |
| LRR Count | Number of LRRs receiving the uplink packet. The system performs a 250ms buffering upon receiving an uplink packet to check if the same packet arrives through other LRRs, in which case the LRR Count is incremented. |
| Device Lat | Device latitude. |
| Device Long | Device longitude. |
| LoS Distance (m) | Distance between the device and the best-LRR. |
| Device Loc radius | Defines a horizontal circle inside which the position of the device is estimated. |
| Device Loc Time | Device location time, indicating the time when the device location was estimated by the LocSolver engine. |
| Device Alt | Device estimated altitude based on LoRa® location. |
| Device Alt radius | Device altitude location defines a vertical circle inside of which the altitude of the device is estimated. |
| Device Acc | Device location accuracy. |
| LRR[1] Id | ID of the uplink best-LRR (that is, LRR Id). |
| LRR[1] RSSI | RSSI at the uplink best-LRR (that is, LRR RSSI). |
| LRR[1] SNR | SNR at the uplink best-LRR (that is, LRR SNR). |
| LRR[1] ESP | Estimated Signal Power at the uplink best-LRR. |
| LRR[1] CHAINS | Antenna chain used to receive the uplink packet on the uplink best-LRR. |
| LRR[1] ISM Band | ISM band of the base station. |
| LRR[1] RF Region | RF region of the base station. |
| LRR[1] GWID | Gateway ID reported by the fNS. Only applicable when the base station does not belong to the serving network (roaming scenario). |
| LRR[1] GWToken | Gateway token reported by the fNS. Only applicable when the base station does not belong to the serving network (roaming scenario). |
| LRR[1] DLAllowed | Downlink Allowed flag reported by the fNS. Only applicable when the base station does not belong to the serving network (roaming scenario). Reported for the first best base station ranked by SNR. |
| LRR[1] ForeignOperatorNetID | The NetID of the forwarding operator. |
| LRR[1] ForeignOperatorNSID | Forwarding operator's Network Server ID reported by the base station.
|
| LRR[x] Id | ID of the xth best-LRR that has received the same packet (data present only if LRR Count ≥ 2). 2 ≤ x ≤ 10. |
| LRR[x] RSSI | Uplink RSSI at the xth best-LRR (data present only if LRR Count ≥ 2). 2 ≤ x ≤ 10. |
| LRR[x] SNR | Uplink SNR at the xth best-LRR (data present only if LRR Count ≥ 2). 2 ≤ x ≤ 10. |
| LRR[x] ESP | Uplink ESP at the xth best-LRR (data present only if LRR Count ≥ 2). 2 ≤ x ≤ 10. |
| LRR[x] CHAINS | Antenna chain used to receive the uplink packet on the xth best-LRR. 2 ≤ x ≤ 10. |
| LRR[x] ISM Band | ISM band of the base station. |
| LRR[x] RF Region | RF region of the base station. |
| LRR[x] GWID | Gateway ID reported by the fNS for the xth best-LRR. Only applicable when the base station does not belong to the serving network (roaming scenario). 2 ≤ x ≤ 10. |
| LRR[x] GWToken | Gateway token reported by the fNS for the xth best-LRR. Only applicable when the base station does not belong to the serving network (roaming scenario). 2 ≤ x ≤ 10. |
| LRR[x] DLAllowed | Downlink Allowed flag reported by the fNS for the xth best-LRR. Only applicable when the base station does not belong to the serving network (roaming scenario). 2 ≤ x ≤ 10. |
| LRR[x] ForeignOperatorNetID | The NetID of the forwarding operator. If the network server acts as a serving network server (sNS), the Foreign Operator NetID is only available if the base station does not belong to the serving network. 2 ≤ x ≤ 10. |
| LRR[x] ForeignOperatorNSID | Forwarding operator's network server identifier reported by the base station.
|
| MAC(hex) | Hexadecimal ASCII dump of the LoRaWAN® MAC option or LoRaWAN® MAC payload (port=0). |
| MType | LoRaWAN® MType of the packet. |
| ADR | Adaptive Data Rate, 1 if enabled, otherwise 0. |
| ADRACkReq | ADR Acknowledgement Request. |
| Ack | Acknowledgement. |
| FPending(downlink) | Frame pending in downlink, indicates if downlink packet is fragmented. |
| AirTime | Duration of the packet in seconds. |
| MIC | Message integrity checksum calculated using Network Session Key. |
| Payload(hex) | Application payload in hexadecimal format. |
| FCntUp | Frame counter up. |
| FCntDn | Frame counter down. |
| DownlinkStatus | Specifies if the downlink packet has been successfully transmitted over the air. |
| DownlinkFailedCauseOnRX1 | Downlink failure cause on RX1. |
| DownlinkFailedCauseOnRX2 | Downlink failure cause on RX2. |
| DownlinkFailedCauseOnPingSlot | Downlink failure cause on ping slot. |
| Late | Indicates that this is a late reporting of an uplink packet from the LRR. When it is set to 1, the uplink packet was queued on the LRR due to temporary loss of the backhaul link with the LRC. |
| SolvLAT | Device location latitude using LoRa® TDoA/RSSI network geolocation. |
| SolvLON | Device location longitude using LoRa® TDoA/RSSI network geolocation. |
| PayloadSize | Payload size in bytes. |
| BestGWID | Gateway ID of the best base station when the best base station belongs to a forwarding network (roaming scenario). |
| BestGWToken | Gateway token of the best base station when the best base station belongs to a forwarding network (roaming scenario). |
| ForeignOperatorNetID | The NetID of the forwarding operator. If the network server acts as a serving network server (sNS), the Foreign Operator NetID is only available if the best or selected base station does not belong to the serving network. |
| RoamingType | 0: Forwarding Passive Roaming (fNS). 1: Serving Passive Roaming (sNS). |
| RoamingResult | The PRStartAns result code, as defined in the LoRaWAN® backend interfaces specification, generated by the sNS. |
| ISMBand | ISM band in use by the best or selected base station (BestLRR or BestGWID). |
| Modulation | Type of modulation: 0 for "LoRa", 1 for "LoRa-E". |
| DataRate | Data Rate when LoRa-E modulation is used. |
| SubID | Subscriber ID. |
| Device North velocity | Velocity (NORTH axis) expressed in m/s. |
| Device East velocity | Velocity (EAST axis) expressed in m/s. |
| ASID | List of application server routing profiles that received the uplink packet. |
| Multicast class | Class of the multicast group: B or C. Only set when the downlink is sent to a multicast group. |
| Transmission status | Multicast downlink transmission status: PARTIAL, SUCCESS or ABORTED. Only applicable to multicast summary report. |
| LRRs count | Number of LRRs associated with the multicast group. Only applicable to multicast summary report. |
| LRRs successfully transmitted | Number of LRRs having successfully transmitted the downlink packet over the air. Only applicable to multicast summary report. |
| LRRs failed transmitted | Number of LRRs that failed in transmitting the downlink packet over the air. Only applicable to multicast summary report. |
| Delivery Failed Cause/Number of occurrences | Distribution of LRR delivery failed causes. Only applicable to multicast summary report. |
| AF count down | LoRaWAN® 1.1 AFCntDown. |
| NF count down | LoRaWAN® 1.1 NFCntDown. |
| Conf AF count down | LoRaWAN® 1.1 AFCntDown confirmed by the device (retrieved by the LRC after MIC check procedure). |
| Conf NF count down | LoRaWAN® 1.1 NFCntDown confirmed by the device (retrieved by the LRC after MIC check procedure). |
| Conf F count up | LoRaWAN® 1.1 FCntUp confirmed by the LRC (ACK sent by the LRC). |
| Transmission slot | Downlink transmission slot used to send the downlink packet:
Note TransmissionSlot = 0 means unknown. |
| Repeated UL | This flag determines if the downlink unicast packet is sent in response to a repeated uplink packet. |
| Frequency | Physical frequency (in MHz) used to send the uplink/downlink packet. |
| Class | Current LoRaWAN® class of the device: A/B/C. |
| Ping-slot period | Current pingslot periodicity reported by the class B device. |
| Type of notification | Reset notification, valid for the following cases:
|
| Type of device reset |
|
| Device location method used | Type of algorithm (TDoA or RSSI) used by the Location Solver engine (LocSolver) to compute the position reported in each Location Report.
|
| Payload encryption | The payload encryption status (encrypted vs. not encrypted). |
| Tags | List of administrative tags associated with the device in question, if applicable. |
| ForeignOperatorNSID | Forwarding operator's network server identifier reported by the best or selected base station.
|
| RF Region | RF region of the best or selected base station (BestLRR or BestGWID). |
| asDeliveryStatus | Aggregated Application Server delivery status. Values are Ok or Error. This information is only relevant for "Basic HTTP" type of connections towards Application Servers. |
| asRecipients[x] ID | ID of the xth Application Server. The number of AS recipients is limited to 5 per export file. |
| asRecipients[x] status | Transmission status of the report to the xth Application Server. Values are Ok or Error. This information is only relevant for "Basic HTTP" type of connections towards Application Servers. |
| asRecipients[x] destinations | Index, URLs and errorMessage of the xth Application Server when status is Error. This information is only relevant for "Basic HTTP" type of connections towards Application Servers. |
| Decoded payload | Decoded payload, by IoT Flow engine. This field is only relevant when the decoder type is set to Automatic in Wireless Logger application. |
| Driver ID | ThingPark ID of the payload driver used to decode the application payload, using IoT Flow engine.This field is only relevant when the decoder type is set to Automatic in Wireless Logger application. |
| Driver model | Metadata associated with the device profile corresponding to the device in question. This metadata consists of two parts: Model-ID and Application-ID; allows Wireless Logger application to automatically map the device to the right payload decoder from the list of IoT Flow drivers. This field represents the model ID, it is only relevant when the decoder type is set to Automatic in Wireless Logger application. |
| Driver application | Metadata associated with the device profile corresponding to the device in question. This metadata consists of two parts: Model-ID and Application-ID; allows Wireless Logger application to automatically map the device to the right payload decoder from the list of IoT Flow drivers. This field represents the application ID, it is only relevant when the decoder type is set to Automatic in Wireless Logger application. |
| Decoding error | Indicates whether there is a decoding error generated by IoT Flow drivers, it is only relevant when the decoder type is set to Automatic in Wireless Logger application. |