Access Official Technical PDF

Share Summary:LinkedInEmail

GPS tracking can help emergency response teams build a clearer picture of a disaster site by linking location information with updates from personnel and injured people. A prototype developed around Nordic Semiconductor’s Thingy:52 explored how GPS, LoRa, Bluetooth Low Energy (BLE) and near-field communication (NFC) could work together in a wearable tracker. Its design also offers a practical lesson for embedded-system developers: the GPS module and NFC reader were the largest power consumers in the device.

Combining location, identification and wireless communication

The proposed use case is a disaster-affected site where an operations leader needs information about the positions and status of rescue personnel and injured people. Responders could carry trackers, while additional units could be assigned to injured people. An NFC scan would associate a person or care assessment with a tracker, and the device could send information such as GPS coordinates, status and sensor readings for remote monitoring.

This approach connects several functions that are often considered separately. GPS provides location and time data. NFC supports close-range identification or the entry of information from a tag. Wireless links then move the resulting data to a nearby device or toward an internet-connected network. In the prototype, a data transfer could be triggered by events including a tag scan, detected movement, a change in orientation, sound above a set threshold or a timer.

Why use both LoRa and Bluetooth Low Energy?

The tracker used two communication paths for different purposes. LoRa, used with the LoRaWAN protocol, was intended to send data over a long-range, low-power wide-area network. A LoRa module forwarded data received from the Thingy:52 to a gateway, which could relay it to an internet-connected service. The prototype used over-the-air activation to join the LoRaWAN network.

BLE provided a separate point-to-point link between the tracker and a nearby central device, such as a phone or computer. In this arrangement, the tracker acts as a peripheral and the phone or computer as the central device. BLE can support local access to tracker data without relying on the same network path used for LoRaWAN.

The two links should not be treated as interchangeable. LoRaWAN is suited to sending small data packages through a gateway over a wider area, while BLE supports communication with a nearby device. The thesis also considered BLE mesh as a possible way to pass messages through other devices, but mesh functionality was identified as future work rather than implemented in the prototype.

NFC tags connect a tracker to a person or assessment

NFC operates over a very short distance, making it suitable for deliberate, close-range scans. In the prototype, a PN532 reader was configured to read Type 2 NFC tags containing information such as an identification number or triage assessment. The tracker then included the scanned information in a data package sent over BLE and LoRa.

For emergency workflows, this illustrates how an NFC tag can act as a simple input point: a responder scans a tag to associate information with the device, rather than entering it through a more complex interface. The prototype’s reader was configured for Type 2 tags, so compatibility with other tag types was not established by this implementation.

Power consumption shapes the tracker design

Power use matters whenever a device is expected to operate away from convenient charging. The project measured consumption across the tracker’s modules and found that the GPS module and NFC reader were the most power-intensive components. This makes them priorities for further energy optimization, rather than assuming that wireless communication alone will dominate the energy budget.

The firmware included several ways to manage activity. For example, the GPS positioning interval was changed from its one-second default to ten seconds, and the NFC reader checked for tags periodically instead of continuously. The microphone was also enabled only for a short listening period at defined intervals. These choices reflect a general embedded-design tradeoff: reducing how often a sensor operates may save energy, but it can also affect how frequently the system can detect events or refresh information.

The reported measurements were taken on a prototype assembled from development hardware. The Thingy:52’s consumption was calculated by subtracting the measured power of the external modules from the measured total. The results identify relative priorities for this design, but they do not establish the power profile of a future, miniaturized device.

From proof of concept to deployable system

The prototype demonstrated an integration path for GPS, NFC, LoRaWAN and BLE, and included a proposed circuit diagram to support future miniaturization. Moving from a development-board proof of concept to a field-ready tracker would require further engineering. In particular, the power draw of the GPS and NFC functions warrants attention, and the hardware proposal would need to be developed and validated as a compact design.

Operational use would also depend on how information is interpreted and acted upon. A tracker can provide location and scanned status data, but the value of that information depends on reliable workflows between responders, operations leaders and receiving facilities. The thesis describes these as potential benefits and a future use case, not as outcomes established through a field deployment.

Practical implications for automation and embedded teams

For engineers and system integrators, the project highlights three useful design considerations:

  • Match communication to the task: use LoRaWAN and BLE for distinct network roles rather than treating them as equivalent links.
  • Design event handling deliberately: sensor triggers, scan intervals and reporting timers influence both responsiveness and energy use.
  • Measure the complete system: component-level measurements can reveal where optimization effort is most relevant, while prototype results should be distinguished from validated production performance.

In short, GPS tracking combined with LoRa, BLE and NFC can form a flexible architecture for sharing location and identification data in a distributed response scenario. The prototype’s clearest engineering finding is that GPS and NFC were its leading power consumers. Any next-stage design should therefore assess their operating schedules and energy requirements alongside the communication architecture, while validating the complete system for its intended operational conditions.

Access Official Technical PDF

About The Author