LoRa Basics Modem and LoRa Edge documentation
Use Case - Basic Asset Tracking¶
A key advantage of the LoRa Edge™ platform is that it can ease the development, deployment, and management of low power and cost-efficient asset tracking devices designed to operate on a LoRaWAN® network.
The Basic Asset Tracking use case described below is suitable for addressing the business needs of tracking the location of vehicles, trailers, pallets, livestock, etc. You can use Semtech’s LoRa Edge Asset Management Evaluation Kit to evaluate this use case based on the three key elements of the LoRa Edge Asset Management Platform:
The LoRa Edge LR1110 transceiver
The embedded LoRa Basics™ Modem-E software, converting an LR1110 transceiver into a LoRa Basics Modem-E device.
The LoRa Edge LR1110 chip with LoRa Basics Modem-E is encapsulated in a sleek, streamlined, and commercial-ready end device that demonstrates the complete set of asset tracking capabilities for IoT applications.
For more information, see:
The LoRa Edge platform was specifically designed for basic asset tracking, and the system works best when all of the LoRa Cloud services are used as intended.
The various platform components required are shown in the following diagram:
Prerequisites / Dependencies¶
This use case assumes the deployment of a functional LoRaWAN network with an appropriate application server and an integration to LoRa Cloud, as illustrated above. The LoRaWAN network should comply with the LoRaWAN L2 specification ( version 1.0.2 or a later, compatible, version).
While timeliness is not mandated by the LoRaWAN standard, it is an assumed behavior of the LoRa Edge system. Therefore, the system will not work correctly if uplink data is delayed by more than 30 seconds.
Prerequisites for LoRa Basics Modem:
The end device must be built on modem version 2.x.x.
Prerequisites for LoRa Basics Modem-E:
The end device must be built on modem version 1.0.7.
The LR1110 device must have been claimed.
The prerequisites for a LoRaWAN network, Semtech’s LoRa Cloud services, and device provisioning must be in place.
The device application commands the Basics Modem to join the network.
Assuming that automatic GNSS almanac updates were enabled during modem initialization, LoRa Basics Modem communicates with the network to update the GNSS almanac.
Assuming that application layer clock synchronization (ALC Sync) was enabled at modem initialization, LoRa Basics Modem communicates with the network to acquire the correct time.
If the previous steps are successful, the device application waits (loops) until the clock synchronization and almanac update are started before initiating GNSS scans. (Wi-Fi signals can be scanned immediately.) The results are then sent to the application server.
To use the lowest power position solving operations of the LoRa Edge platform, the device application must provide an approximate latitude and longitude for the device. This needs to be accurate to within +/- 150km. Often, this can simply be the latitude and longitude of the receiving or beaconing gateway.
At this point, the modem is completely up-to-date and ready for normal operation. To reliably and efficiently transfer the raw positioning data to the LoRa Cloud Device & Application Services (which are used for determining the true latitude and longitude of the device) the device application shall initialize a reliable stream of data.
Having reached the steady state operation for asset tracking, the device application should initiate an asssisted GNSS scan and store the results.
Alternatively (or additionally) the device application can initiate a passive Wi-Fi scan and store the results.
Having collected and processed either or both the GNSS and Wi-Fi scan data, the end-device application tags the data collections and places them into the stream buffer.
The LoRa Basics Modem and LoRa Edge platform stream the data to the LoRaWAN network. The LoRa Cloud integration server parses the data to determine the correct LoRa Cloud API to use to either recover the original data from the stream, or to resolve the raw data into a precise latitude and longitude that can be used by the Application Server.
The LoRa Edge platform is a multifaceted technical solution with the fundamental capabilities required for implementing an asset management solution. Here, we have documented many of the details and best-practices that will lead to success. Nevertheless, problems may arise.
You can find a wealth of information and documents to help you solve any problems you encounter at both www.semtech.com and on the LoRa Developers Portal. Additionally, Semtech maintains a LoRa Developer’s Forum at https://lora-developers.semtech.com/knowledge-base/forum/. In the Forum, you can find community support for technical questions.
If none of these methods are sufficient to resolve a technical issue, Semtech may be able to provide direct support. To for direct support, submit a support request to https://semtech.force.com/ldp/ldp_support
LoRa Basics Modem and LoRa Edge documentation
- Overview - LoRa Edge™ Asset Management Platform
- Use Case - Basic Asset Tracking
- Use Case - IR Image Upload on Detected Motion
- Scenario - GNSS Assisted Scan
- Scenario - GNSS Autonomous Scan
- Scenario - LoRa Basics™ Wi-Fi Passive Scan
- Scenario - LoRa Cloud™ Device Join
- Scenario - GNSS Scan with ROSE
- Scenario - Wi-Fi Scan with ROSE
- Scenario - Claiming a Device
- Scenario - Unclaiming a Device
- Scenario - Modem-E Initialization
- Scenario - LoRa Basics™ Almanac Update
- Scenario - User Loaded Almanac Update
- Scenario - Intermittent Network
- Component - Application Layer Clock Synchronization
- Component - Large File Upload
- Component - Reliable Octet Stream Encoding
- Cryptographic Engine