TEKTELIC STORK Asset Tracker

Document Information

Product Names and T-Codes:

Release Date: June 3, 2024

Document Revision History

Product Description

1.1 Overview

This document provides a user manual for the STORK Asset Trackers developed by TEKTELIC Communications Inc. This document includes descriptions of both STORK variants and instructions regarding the HW capabilities. For the functional operation and SW behaviour, please refer to the TRM document.

The STORK is a low-power LoRaWAN IoT sensor run on a single C-cell LTC battery and packed into a compact IP67 polycarbonate casing. Its primary purpose is to track assets indoors and outdoors using a combination of location-tracking technologies:

• Low-Power GNSS: Outdoor tracking using satellite geolocation.
• Wi-Fi Sniffing: Outdoor and/or indoor tracking using Wi-Fi access point geolocation.
• BLE Tracking: Indoor tracking using BLE beacon network localization.

The STORK is meant to be a component in an end-to-end asset tracking solution as shown in Figure 1-1.

Figure 1-1: Diagram showing the STORK Asset Tracking End-to-End Architecture. It illustrates the flow from Geolocation Signal Sources (GNSS, Wi-Fi, BLE) to STORK End-Devices, then to LoRaWAN GateWays, a LoRaWAN Network Server, Application Server(s), and finally to Cloud IoT Location Services such as LoRa Cloud, Wi-Fi Resolver, BLE Resolver, and TEKTELIC Resolver.

LoRaWAN is the LoRa wireless communications standard protocol. This technology provides a low-bandwidth, low-power, and long-range means of transmitting small amounts of data. It has been developed with wireless sensing in mind, and to enable new means of gathering telemetry in numerous environments. The STORK supports LoRa and (G)FSK modulations according to the LoRaWAN L2 1.0.4 Specification [1]. The 150 MHz-960 MHz ISM bands are utilized to meet different application requirements from the standards and proprietary protocols of the given region.

NOTE: Only raw scan data is present in the LoRaWAN payloads, not sensor location information. In order to track and visualize a STORK's location, an application server must be set up, integrated with the NS, and enabled to use the proper cloud location services. The information in this document is for the STORK sensor only; for information about setting up the rest of the end-to-end solution shown in Figure 1-1, refer to the TEKTELIC support portal Knowledge Base [1].

Up to 2 km NLoS and more than 22 km LoS.

1.2 Summary of HW Information, Streams, and Default Behaviour

Table 1-1 presents the currently available sensor HW variants, and Figure 1-2 shows the enclosures. The information streams supported by the SW are shown in Table 1-2 and the default configuration for reporting data has been shown in Table 1-3.

Figure 1-2: Images of the STORK enclosures. The top image shows the STORK Base Enclosure, and the bottom image shows the STORK External Power Enclosure.

1.3 External Appearance and Interfacing

The appearances and external interfacing are shown in Figure 1-3. These are the same for both the base and external power variants.

Figure 1-3: Diagram of the STORK enclosure's external appearance and interfacing. It shows the back view with Humidity Vents and the front view with RED LED, GREEN LED, Magnet Symbol, and Magnetic Activation Site.

1.4 Specifications and Sensing Functions

The STORK specifications are listed in Table 1-4. The main sensing functions are described in the following subsections.

1.4.1 Tracking with Geolocation

The primary purpose of the STORK is to track assets indoors and outdoors using a combination of location-tracking technologies: low-power GNSS, Wi-Fi sniffing, and BLE scanning.

One or more geolocation scans are conducted during a geolocation cycle. A new geolocation cycle occurs at a regular period called the geolocation update period, as shown in Figure 1-4. By default, the geolocation update period is shorter when the sensor is in motion and longer when the sensor is still.

Figure 1-4: Diagram illustrating Periodic Geolocation Cycles and Uplinks (ULs). It depicts a timeline where Geolocation Cycles occur within Geolocation Update Periods, with Scan Results reported after each scan finishes.

During a geolocation cycle, up to 3 scans can be defined and occur in sequence. After each scan concludes, if successful, the raw results are reported in a LoRaWAN UL before the next scan begins.

The duration of each geolocation cycle may vary from 10s of seconds to a few minutes, depending on several factors (e.g.: satellite signal strength, user configurable BLE scan duration, regional duty cycle limitations, etc.). It is important to configure the geolocation update period to be greater than the expected geolocation cycle duration, otherwise scans may not complete, and data may be lost. If GNSS scanning is enabled, it is not recommended to set the geolocation update period to less than 3.5 min. If BLE scanning is enabled, it is not recommended to set the geolocation update to less than 20 s.

The supported scan type options and behaviours are summarized in Table 1-5.

The scan order logic within the geolocation cycle is also configurable to allow the cycle to end upon a successful scan before the other defined scans occur. Doing so can save battery life in use-cases where the scan types can be prioritized by how likely they are to succeed, e.g.: if it is known that GNSS will be the available geolocation signal source 90% of the time. The supported scan order logic options are shown in Table 1-6.

1.4.1.1 Geolocation Strategies

The ability to define up to 3 scan types and choose 1 of 4 scan order logic options results in 12 possible configurational combinations. This combination is called the geolocation strategy. Of the 12 geolocation strategies, only 7 result in unique device behaviour, as shown by the green shaded boxes in Table 1-7.

The geolocation strategy used should be tailored to the use case of the STORK deployment. Some example use-cases and strategies are:

• Delivery vehicle tracking: FALLBACK with (1) GNSS, (2) Wi-Fi, (3) BLE
  Likely to be outside for most of the time, so GNSS is likely to succeed most of the time. Wi-Fi is next most likely, then BLE.
• Pallet tracking in a multi-building site: 2 BACKUP with (1) BLE, (2) Wi-Fi, (3) GNSS
  Likely to be in an indoor BLE Beacon network most of the time, so BLE is likely to succeed most of the time. If BLE fails, try both other methods to get a position estimate.

The default geolocation strategy is fallback (scan order logic A) with all 3 scans defined in priority order GNSS, Wi-Fi, BLE. The operational flow of this strategy is depicted in Figure 1-5. All other strategy flow depictions are shown in Appendix 3.

Figure 1-5: Flowchart for the Default Geolocation Strategy (Fallback, All Scans Defined). It shows the Normal Operation, Geolocation Cycle START, sequential 1st Priority Scan (GNSS), 2nd Priority Scan (Wi-Fi), and 3rd Priority Scan (BLE). Each scan can result in Scan Success (sending Scan Results via LoRaWAN UL) or Scan Failure. If all scans fail, a Geolocation Cycle Failed message is sent.

1.4.1.2 GNSS and Wi-Fi Operation with LoRa Cloud Resolvers

The GNSS and Wi-Fi scan results are formatted in such a way that the edge based LoRa Cloud service can resolve the sensor's position. Both UL and DL communications are exchanged between the STORK and LoRa Cloud server to transfer all the information needed for the positions to be resolvable.

For GNSS scan results to be valid and resolvable, the following are needed:

• Valid clock synchronization: The internal time of the sensor must be synchronized periodically. The sync interval, sync expiration timeout, and sync service option are all configurable.
• Valid almanac: The almanac in the sensor must be kept up-to-date. The update check period and update request UL interval are configurable.
• Assist coordinates: These help the resolver with an initial estimate of the sensor's location. These can be configured specifically by the user if desired, but the SW will automatically communicate with LoRa cloud to obtain assist coordinates upon startup if none are defined.

Other user-configurable options for GNSS scanning include the choice of satellite constellation (GPS, BeiDou, or both) and mobile or static scanning. The Wi-Fi scanning has no configurable options.

1.4.1.3 BLE Operation with LOCUS and the GRB

The BLE scan results are formatted in such a way that the TEKTELIC LOCUS application can resolve and display the sensor's position. Indoor BLE beacon networks can be built virtually in LOCUS to match the physical setup. When LOCUS receives a sensor UL with raw BLE scan data, it forwards it to the Geolocation Resolver Backend (GRB) cloud service, which computes and returns the position estimate within the beacon network.

For information about setting up LOCUS, refer to the TEKTELIC support portal Knowledge Base articles [2]. For a description of BLE scan behaviour, see the TRM.

1.4.2 Temperature and Relative Humidity Transducer

The STORK is equipped with a temperature and relative humidity (RH) transducer. Note that because the transducer element is located inside the sensor housing, sense response time will not be immediate. Vents in the front, bottom, and back of the enclosure are designed to allow ambient air to contact the transducer. Response time can be reduced by forcing air to move over the sensor in the region of the transducer opening.

Temperature and RH values can be reported on a threshold basis; a window of "good operational range" can be user-defined. High and low alarm points can be set individually for ambient temperature and RH. The sample rate for checking the transducers is user configurable with different sample rates settable if the measured value is inside or outside the normal operating window.

1.4.3 Accelerometer Transducer

The STORK supports motion sensing through an integrated 3-axis accelerometer which can optionally be disabled. The main role of the accelerometer in the is to detect motion that can indicate a change of the sensor's status from stillness to mobility, or vice versa.

The accelerometer generates an acceleration alarm when a motion event is detected that can be reported OTA. An acceleration event report is based on exceeding a defined acceleration alarm threshold count in a defined alarm threshold period. These thresholds can be customized such that there will not be multiple reports for a single event, depending on the definition of an event in a particular use case. An alarm event can only be registered after a configurable grace period elapses since the last registered alarm event. Carefully setting the grace period is important and prevents from repeatedly registering an accelerometer event.

In addition to alarms, detected motion can trigger the transitions between geolocation update periods. That is, when the Accelerometer Assist function is enabled,

• When new motion is detected:
  • A new geolocation cycle begins immediately.
  • New geolocation cycles occur periodically according to the MOBILE geolocation update period.
• When the motion has ended:
  • A new geolocation cycle begins immediately.
  • New geolocation cycles occur periodically according to the STILL geolocation update period.

The geolocation update periods are both configurable.

For asset tracking, Accelerometer Assisted geolocation scans help to get location updates at appropriate rates: faster when the asset is moving and slower when still. Accelerometer Assist also helps to update the location at 2 critical times; when assets leave old locations and settle in new ones. Accelerometer Assist is enabled by default.

The accelerometer can also be polled periodically for its output acceleration vector for applications in which the sensor's orientation is of interest.

1.4.4 BLE Beacon Mode

The STORK supports a beacon mode function as an alternative to geolocation tracker mode. The default mode of the sensor is tracker mode, so it must be switched into beacon mode.

When in beacon mode, no geolocation scans occur and the BLE operates in Tx only. It sends out periodic advertisements which are small packets of data. These packets are discoverable by other STORKs operating in tracker mode, as well as any other device capable of BLE scanning.

When in beacon mode, the sensor is still LoRaWAN-backhauled. That is, it can still send sensor data in LoRaWAN ULs and be reconfigured through LoRaWAN DLs. Furthermore, all other transducer functions are accessible in either beacon or tracker mode.

After a beacon joins the LoRaWAN network, it begins broadcasting BLE advertisements. This continues throughout normal operation as a background process.

The advertising interval is the time between the beginnings of consecutive advertisement transmissions as shown in Figure 1-6. It is user-configurable in units of [ms].

Figure 1-6: Diagram illustrating the BLE Advertisement Scheme. It shows a timeline with consecutive BLE Advertisements separated by Advertising Intervals. Each advertisement consists of multiple packet transmissions on different channels (37, 38, 39).

In addition to the advertising interval, the advertisement Tx power level is also a configurable operational parameter.

The BLE advertisement and LoRa radio transmission are mutually exclusive and never overlap. If any reporting becomes due, the BLE advertisements are paused while the LoRa activity is occurring.

The BLE advertising packet formatting supports 3 major BLE standards: iBeacon, Eddystone UID, and Eddystone TLM. By default, only iBeacon is enabled.

1.4.5 Magnetic Sensor

The STORK is equipped with a magnetic hall-effect sensor. Since the enclosures are fully sealed, there is no ability to have a battery pull-tab or reset button pinhole. The magnetic sensor therefore is included to address these purposes:

1. To wake the device from sleep (the sensors are shipped in a state of DEEP SLEEP).
2. To put the device to sleep.
3. To reset the device.
4. To force a LoRaWAN UL.

The position on the exterior of the enclosure on which the magnet must be placed to activate the reed switch is shown in Figure 1-3.

For more information on how to wake the device from sleep, refer to Section 2.4. For more information on how to use the magnetic sensor for the other purposes, refer to the TRM.

A magnet is not included with the STORK.

Installation

2.1 Included Product and Installation Material

The following items are shipped with each sensor:

• 1x sensor with 3.6 V C-cell LTC battery installed.
• 1x Quick Start Guide.
• 1x mounting bracket.

2.2 Safety Precautions

The following safety precautions should be observed for all STORK variants:

• All installation practices must be in accordance with the local and national electrical codes.
• Replace battery only with approved type (see §2.6).
• The sensor contains a single LTC C-cell battery. When used correctly, lithium batteries provide a safe and dependable source of power. However, if they are misused or abused, leakage, venting, explosion, and/or fire can occur. The following are recommended safety precautions for battery usage [4].

• Keep batteries out of the reach of children.
• Do not allow children to replace batteries without adult supervision.
• Do not insert batteries in reverse.
• Do not short-circuit batteries.
• Do not charge batteries.
• Do not force discharge batteries.
• Do not mix batteries.
• Do not leave discharged batteries in equipment.
• Do not overheat batteries.
• Do not weld or solder directly to batteries.
• Do not open batteries.
• Do not deform batteries.
• Do not dispose of batteries in fire.
• Do not expose contents to water.
• Do not encapsulate and/or modify batteries.
• Store unused batteries in their original packaging away from metal objects.
• Do not mix or jumble batteries.

2.3 Unpacking and Inspection

The following should be considered during the unpacking of a new sensor.

1. Inspect the shipping carton and report any significant damage to TEKTELIC.
2. Unpacking should be conducted in a clean and dry location.
3. Do not discard the shipping box or inserts as they will be required if a unit is returned for repair or reprogramming.

2.4 Commissioning and Activation

Each sensor has a set of commissioning information that must be entered into the network server for the sensor to be able to join the network and begin normal operation once activated. For instructions on how to do this please refer to the Network Server Quick Start Guide (available online in the Knowledge Base) [5]. The commissioning info should be included on the package labels.

The sensor is shipped in a secured enclosure with the battery preinstalled in a state of DEEP SLEEP. The magnetic activation/reset pattern is illustrated in Figure 2-1. A "magnet presence" is achieved by placing a sufficiently strong magnet against the enclosure at the magnetic activation site as shown in Figure 1-3. A "magnet absence" is achieved by taking the magnet away from the enclosure. Figure 2-1 shows that the pattern involves sustaining a "magnet presence" continuously for at least 3 s but less than 10 s.

Figure 2-1: Graph illustrating the Magnetic Activation/Reset Pattern. It shows the 'Magnet Present' state sustained for 3 to 10 seconds, leading to Module Reset and activation if in DEEP SLEEP.

When the STORK is activated, it will display an LED indication (described in §3.3) to show that it is beginning to join the network. It may take up to 10 seconds between the time of activation and the beginning of the LED join attempt pattern.

Once activated, the sensor will automatically begin the join process. To turn the sensor off, the battery must be removed. To reset the device, the magnetic activation/reset pattern can be applied again.

2.5 Mounting Procedure

1. The mounting bracket needs to be secured to a wall or another solid surface by using an adhesive or mounting screws. The mounting bracket can be seen in the back view in Figure 1-3.

1. For use cases that require releasable mounting, ensure that the “SOFT LOCK” indication is installed with the arrows pointing up.
2. For use cases that require permanent mounting, ensure that the “HARD LOCK” indication is installed with the arrow pointing up.
3. After the bracket has been secured, the sensor can be mounted by sliding the enclosure into the bracket ridges until a click is heard, indicating it is fully inserted.

2.6 Battery Replacement

The battery cover is marked with a battery symbol and uses Phillips Head H1 screws. This cover needs to be removed to replace the battery.

1. Remove the battery cover by unscrewing the 4x Phillips head screws using a size #1 Phillips head screwdriver (see Figure 2-2).

Figure 2-2: Image showing the underside of the STORK enclosure with four Phillips head screws, indicating the battery cover removal process.

2. Remove the depleted battery and replace it with a new 3.6V Lithium Thionyl Chloride C-size battery ONLY. When inserting the new battery, insert the negative terminal side first. The battery contact on the battery cover is the positive contact and is marked with a plus-sign (+) as shown in Figure 2-3.

Figure 2-3: Images showing the internal components for battery insertion. One image displays the front and back edges of the sensor chassis with polarity markers, and another shows the battery cover with its gasket and contact points.

3. Check that the gasket is undamaged and remains properly seated and adhered to the battery cover.

4. Before reattaching the battery cover, ensure the proper orientation of the cover with respect to the front and back of the sensor chassis. The front of the sensor has rounder corners, and the back of the sensor has sharper corners, as seen in Figure 2-3.

5. Reassemble the cover to the chassis by using the 4x Phillips head screws, using a #1 size screwdriver and up to 0.23 Nm of torque.

2.7 Cable Connection

The STORK, External Power variants (T0008396 and T0008952) may be powered from an external DC power source through the M5 connector located on the bottom of the sensor. The pinout is illustrated in Figure 2-4 and summarized in Table 2-1.

Use care when mating this connection as the pins are small and can be damaged with misalignment or excessive force. The connector is fully protected from misconnection and no damage can occur but the sensor may not operate as expected if the required connection is not followed. A 5 A maximum rated fuse is required in the external feed if the sourced power can exceed 100 W.

The sensor internal battery may remain in place when powering from external power. In the absence of valid input power, the sensor will continue to operate from its internal battery.

The supported input voltage range is 9 - 16 V DC.

Figure 2-4: Close-up image of the M5 connector on the STORK, with pins labeled 1, 3, and 4.

The external cable is not supplied with STORK. The recommended mating cable is listed in Table 2-2 [6].

Operation, Alarms, and Management

3.1 Configuration

The STORK supports a full range of OTA configuration options. Specific technical details are available in the corresponding TRM documents. All configuration commands need to be sent OTA during the sensor's DL Rx windows.

3.2 Default Configuration

Table 3-1 lists the default reporting behaviour of the STORK. Reporting behaviour can be changed from default through OTA DL commands.

3.3 RF LED Behaviour

The LED behaviour is not user configurable.

The LEDs are normally off. Their blinking patterns reflect different actions and states of the sensor. At a high-level, the main patterns are summarized in Table 3-2. The detailed sequence and timings for each are described in the following subsections.

3.3.1 Power-On and Network Join Patterns

When the sensor is activated or reset:

1. Both GREEN and RED are OFF for approximately 0.5 s after any reset occurs.
2. Upon startup, the SW conducts its POST. Both GREEN and RED are turned on when the POST begins.
3. When the POST ends (about 2 s), both GREEN and RED are turned off. Immediately following, the sensor will do 1 of 2 things, depending on the POST result:
   1. If the POST passes, GREEN is toggled ON and OFF 3 times: every 100 ms for 0.6 s, as shown in Figure 3-1. In this case, the LED pattern proceeds to step 4.
   2. If the POST fails, RED is toggled ON and OFF 3 times: every 100 ms for 0.6 s, as shown in Figure 3-1. In this case, the device restarts and the LED pattern begins again at step 1 after approximately 4 s.

Figure 3-1: Waveforms illustrating LED patterns. The left waveform shows the GREEN POST Pass pattern (three ON/OFF toggles). The right waveform shows the RED POST Failure pattern (three ON/OFF toggles).

4. After a successful POST, both GREEN and RED are turned off. Immediately following this, the sensor will enter JOIN mode and begin attempting to join the network. For the first hour¹¹:

1. GREEN is toggled ON and OFF every 50 ms for the first hour.
2. RED flashes just once:
   1. with a pulse duration of 25 ms right after transmitting a JOIN REQUEST. This occurs at approximately 10 s intervals at the beginning of the join process, but at decreasing regularity the longer the join process continues due to battery saving measures and possible duty-cycle limitations in certain regions [7].
   2. with a pulse duration of 100 ms right after receiving a JOIN ACCEPT. This will occur once, after which, the device will have joined the network and normal operation begins.

If the sensor has been unsuccessfully trying to join for more than an hour, it enters join back-off to conserve power. While the sensor still attempts to join, GREEN stops flashing and RED flashes twice (ON time: 10 ms, OFF time: 10 ms) every 8 s. The JOIN LED pattern is shown in Figure 3-2

Figure 3-2: Diagram showing LED patterns during JOIN mode. It depicts the initial rapid GREEN flashing for joining, followed by RED flashes for JOIN REQUEST and JOIN ACCEPT, and finally a join back-off pattern with RED flashing twice.

3.3.2 Normal Operation Patterns

After the Sensor has joined the network:

1. RED flashes just once with a pulse duration of 25 ms right after transmitting an uplink.
2. GREEN flashes just once with a pulse duration of 100 ms right after receiving a downlink.

3.3.3 DEEP SLEEP and Magnetic Reset Patterns

The sensor displays an LED indication when it is brought out of DEEP SLEEP or reset by applying the magnetic pattern. The following LED pattern is displayed about 3 sec after the pattern is applied:

1. GREEN is turned ON for 75 ms, then turned OFF.

2. After a 100-500 ms pause while the device resets, the normal Power-On and Network Join LED patterns described in §3.3.1 occur.

There is another LED pattern for when the device is put back into DEEP SLEEP. The following LED pattern is displayed about 3 s after the pattern is applied:

1. After a 100-500 ms pause while the device resets, the Power-On POST LED patterns described in steps 1-3 in §3.3.1 occur.
2. Immediately, RED is toggled ON and OFF 3 times: every 100 ms for 0.6 sec as shown in Figure 3-3.

Figure 3-3: Waveform illustrating the RED LED pattern before entering DEEP SLEEP (three ON/OFF toggles).

3.4 Reset Function

The STORK capable of a physically triggered reset. This type of reset powers down the MCU and restarts it, causing the network join procedure to begin again. The reset is triggered by applying the magnetic pattern as shown in Figure 2-1. While this pattern causes the sensor to wake from deep sleep before activation, during normal operation this pattern causes a reset.

NOTE: Shutting down or resetting the sensor will cause all unsaved user configurations to be lost. Save the desired configuration to the sensor flash before powering off or resetting.

Compliance Statements

Federal Communications Commission:

This device complies with Part 15 of the FCC Rules [8]. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and
2. This device must accept any interference received, including interference that may cause undesired operation.

To comply with FCC exposure limits for general population / uncontrolled exposure, this device should be installed at a distance of 20 cm from all persons and must not be co-located or operating in conjunction with any other transmitter.

Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in an industrial installation. This equipment generates uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

Innovation, Science and Economic Development Canada (Industry Canada):

This device contains licence-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canada's licence-exempt RSS(s) [9]. Operation is subject to the following two conditions:

1. This device may not cause interference, and
2. This device must accept any interference, including interference that may cause undesired operation of the device.

This device should be installed and operated with minimum distance 0.2 m from human body.

L'émetteur/récepteur exempt de licence contenu dans le présent appareil est conforme aux CNR d'Innovation, Sciences et Développement économique Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes:

1. L'appareil ne doit pas produire de brouillage.
2. L'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

Cet appareil doit être installé et utilise à une distance minimale de 0.2 m du corps humain.

California Proposition 65:

⚠️ WARNING: This product can expose you to chemicals including lead, nickel, and carbon black, which are known to the State of California to cause cancer, birth defects or other reproductive harm. For more information, go to www.P65Warnings.ca.gov [10].

Appendix 1 - List of Geolocation Strategies

Solid lines: process always done. Dotted lines: process done under certain conditions.

Geolocation Strategy 1: Fallback, All Scans Defined

Diagram illustrating Geolocation Strategy 1, showing the flow of scans and outcomes.

Geolocation Strategy 2: Fallback, 2 Scans Defined

Diagram illustrating Geolocation Strategy 2, showing the flow of scans and outcomes.

Geolocation Strategy 3: 1 Backup, All Scans Defined

Diagram illustrating Geolocation Strategy 3, showing the flow of scans and outcomes.

Geolocation Strategy 4: 2 Backups, All Scans Defined

Diagram illustrating Geolocation Strategy 4, showing the flow of scans and outcomes.

Geolocation Strategy 5: All Scans, All Scans Defined

Diagram illustrating Geolocation Strategy 5, showing the flow of scans and outcomes.

Geolocation Strategy 6: All Scans, 2 Scans Defined

Diagram illustrating Geolocation Strategy 6, showing the flow of scans and outcomes.

Geolocation Strategy 7: All Scans, 1 Scan Defined

Diagram illustrating Geolocation Strategy 7, showing the flow of scans and outcomes.

References

[1] LoRa Alliance, Inc., "TS001-1.0.4 LoRaWAN® L2 1.0.4 Specification," October 2020. [Online]. Available: https://resources.lora-alliance.org/technical-specifications/ts001-1-0-4-lorawan-l2-1-0-4-specification. [Accessed 31 October 2023].

[2] LoRa Alliance, "LoRaWAN™ 1.0.2 Regional Parameters," February 2017. [Online]. Available: https://lora-alliance.org/wp-content/uploads/2020/11/lorawan_regional_parameters_v1.0.2_final_1944_1.pdf. [Accessed 12 April 2021].

[3] Bluetooth SIG, "Core Specification 5.0," 6 Dec 2016. [Online]. Available: https://www.bluetooth.com/specifications/specs/core-specification-5/. [Accessed 15 November 2021].

[4] Tadiran Batteries GmbH, "Tadiran Lithium Batteries: Technical Brochure LTC-Batteries," Tadiran Batteries, Büdingen, Germany, 2020.

[5] TEKTELIC Communications Inc, "Network Server Quickstart Guide - Creating Your first network," 21 August 2019. [Online]. Available: https://support.tektelic.com/support/tektelic/ShowHomePage.do?articlestatus=published#Solutions/dv/274696000014617215/en/History. [Accessed 12 April 2021].

[6] Tensility International Corporation, "10-03011," Tensility, 14 09 2018. [Online]. Available: https://tensility.com/cable-assemblies/10-03011. [Accessed 14 05 2024].

[7] LoRa Alliance, "LoRaWAN Regional Parameters," v1.0.2, rev. B, Feb 2017.

[8] Office of the Federal Register, "Electronic Code of Federal Regulations: Title 47; Part 15 - Radio Frequency Devices," e-CFR, 28 February 2020. [Online]. Available: https://www.ecfr.gov/cgi-bin/text-idx?SID=86ed79fc9447ceff183191690a733ec7&mc=true&node=pt47.1.15&rgn=div5#se47.1.15_11. [Accessed 3 March 2020].

[9] Innovation, Science and Economic Development Canada, "RSS-Gen: General Requirements for Compliance of Radio Apparatus; Issue 5; Amendment 1," March 2019. [Online]. Available: ic.gc.ca/eic/site/smt-gst.nsf/vwapj/RSS-Geni1amend12019-04EN.pdf/$FILE /RSS-Geni1amend12019-04EN.pdf. [Accessed 3 March 2020].

[10] OEHHA, "Proposition 65," California Office of Environmental Health Hazard Assessment, 2020. [Online]. Available: https://oehha.ca.gov/proposition-65. [Accessed 3 March 2020].

[11] Saft, Specialty Battery Group, "Primary lithium battery: LS 14500," Saft, September 2009. [Online]. Available: https://datasheet.octopart.com/LS14500-Saft-datasheet-15505441.pdf. [Accessed 3 March 2020].

[12] Tadiran Batteries, "Model TL-4903 Technical Data," January 2007. [Online]. Available: https://datasheet.octopart.com/TL-4903/S-Tadiran-datasheet-556727.pdf. [Accessed 3 March 2020].

[13] Tadiran Batteries GmbH, "LTC Batteries: SL-360," January 2012. [Online]. Available: https://datasheet.octopart.com/SL-360-S-Tadiran-datasheet-128477996.pdf. [Accessed 21 February 2020].

[14] Tadiran Battery Group, "Model TL-5903 Technical Data," November 2011. [Online]. Available: https://datasheet.octopart.com/TL-5903/S-Tadiran-datasheet-8817806.pdf. [Accessed 3 March 2020].

[15] Xeno Energy Co. Ltd., "XL-060F Specifications," 2010. [Online]. Available: http://www.xenoenergy.com/eng/file/Xeno%20Catalog%20XL-060F_E.pdf. [Accessed 3 March 2020].

[16] TEKTELIC Communications Inc., "BLE Asset Tracker: Technical Reference Manual T0005946_TRM_v0.4," TEKTELIC Communications Inc., Calgary, 2019.

[17] TEKTELIC Communications, Inc., BLE ASSET Tracker Quick Start Guide T0005946_QSG_ver1.0, Calgary, 2020.

[18] Bluetooth SIG, "Bluetooth Core Specifications v 5.0," 6 December 2016. [Online]. Available: https://www.mouser.it/pdfdocs/bluetooth-Core-v50.pdf. [Accessed 12 April 2021].

[19] Semtech, "LoRa Cloud Modem and Geolocation Services," Semtech, 2023. [Online]. Available: https://www.loracloud.com/documentation/modem_services?url=index.html. [Accessed 9 11 2023].