diff --git a/doc/content/lorawan/adaptive-data-rate/_index.md b/doc/content/lorawan/adaptive-data-rate/_index.md index 4c0b2abba6..3b8b408240 100644 --- a/doc/content/lorawan/adaptive-data-rate/_index.md +++ b/doc/content/lorawan/adaptive-data-rate/_index.md @@ -24,6 +24,10 @@ Mobile end devices should be able to detect when they are stationary for a longe ## ADR in The Things Stack +{{< info >}} +Check [{{% tts %}} documentation](https://www.thethingsindustries.com/docs/reference/adr/#how-adr-works) for more specifics on how ADR works on the {{% tts %}}. +{{}} + To determine the optimal data rate, the network needs some measurements (uplink messages). Currently The Things Stack takes the 20 most recent uplinks, starting at the moment the ADR bit is set. These measurements contains the frame counter, signal-to-noise ratio (SNR) and number of gateways that received each uplink. When a device unsets the ADR bit (because it knows it is moving or it knows RF conditions are unstable), previous measurements are discarded. As soon as the ADR bit is set again, the network starts measuring again. For each of these measurements, we take the SNR of the best gateway, and we calculate the so-called "margin", which is the measured SNR minus the required SNR to demodulate a message given the data rate. This margin is used to determine how much we can increase the data rate or lower the transmit power. For example, when the network receives a message with data rate `SF12BW125` and SNR `5.0`, that message has a margin of 25 dB. This is a waste of valuable airtime and energy. If we would increase the data rate to `SF7BW125` we would still have a margin of 12.5 dB, but that would be many times more airtime- and energy efficient. We could even lower the transmit power to save even more energy and cause less interference. diff --git a/doc/content/lorawan/end-device-activation/index.md b/doc/content/lorawan/end-device-activation/index.md index 6c32dac9be..d57bbe8980 100644 --- a/doc/content/lorawan/end-device-activation/index.md +++ b/doc/content/lorawan/end-device-activation/index.md @@ -13,6 +13,10 @@ Every end device must be registered with a network before sending and receiving The join procedure for LoRaWAN 1.0.x and 1.1 is slightly different. The following two sections describe the join procedure for LoRaWAN 1.0.x and 1.1 separately. +{{< info >}} +For more information on the differences between OTAA and ABP, check the [{{% tts %}} documentation](https://www.thethingsindustries.com/docs/the-things-stack/concepts/data-formats/). +{{}} + ## Over The Air Activation in LoRaWAN 1.0.x In LoRaWAN 1.0.x, the join procedure requires two MAC messages to be exchanged between the end device and the Network Server: diff --git a/doc/content/lorawan/message-types/index.md b/doc/content/lorawan/message-types/index.md index 79399abbcb..a630185796 100644 --- a/doc/content/lorawan/message-types/index.md +++ b/doc/content/lorawan/message-types/index.md @@ -6,6 +6,10 @@ images: - payload.png --- +{{< info >}} +For information on {{% tts %}} specific data formats, check [{{% tts %}} documentation](https://www.thethingsindustries.com/docs/the-things-stack/concepts/data-formats/). +{{}} + In this chapter, you will learn about different message types used in LoRaWAN 1.0.x and 1.1. These message types are used to transport MAC commands and application data. The Things Fundamentals Certification exam expects you should have basic knowledge on the following topics with regards to the message types: * Uplink and downlink messages. diff --git a/doc/content/lorawan/regional-parameters/_index.md b/doc/content/lorawan/regional-parameters/_index.md index 5030b42a44..146ffd1da6 100644 --- a/doc/content/lorawan/regional-parameters/_index.md +++ b/doc/content/lorawan/regional-parameters/_index.md @@ -4,6 +4,10 @@ section: The Things Fundamentals weight: 40 --- +{{< info >}} +For information on the specific versions of the Regional Parameters check [{{% tts %}} documentation](https://www.thethingsindustries.com/docs/the-things-stack/concepts/spec-regional-parameters/). +{{}} + LoRaWAN operates in unlicensed radio spectrum. This means that anyone can use the radio frequencies without having to pay million dollar fees for transmission rights. It is similar to WiFi, which uses the 2.4GHz and 5GHz ISM bands worldwide. Anyone is allowed to set up WiFi routers and transmit WiFi signals without the need for a license or permit. LoRaWAN uses lower radio frequencies with a longer range. The fact that frequencies have a longer range also comes with more restrictions, that are often country-specific. This poses a challenge for LoRaWAN, as it strives to maintain uniformity across various regions of the world. As a result, LoRaWAN is specified for several bands within these regions. These bands are similar enough to support a region-agnostic protocol but entail various consequences for the implementation of backend systems. diff --git a/doc/layouts/shortcodes/tts.html b/doc/layouts/shortcodes/tts.html new file mode 100644 index 0000000000..59509549dd --- /dev/null +++ b/doc/layouts/shortcodes/tts.html @@ -0,0 +1 @@ +{{- printf "The Things Stack" -}} \ No newline at end of file