Skip to main content

Base station (BS) attributes

The following table describes the main attributes associated with base stations in ThingPark.

NameFriendly name of your base station.
- It is given during the initial declaration of the base station on ThingPark, but can be changed any time from the base station's detailed dashboard.
- You may search base stations by their name on ThingPark's user interface.
- The base station name is reported to third party applications in the LoRaWAN packet metadata, alongside the LRR-ID.
LRR-UUIDUniversally-unique ThingPark identifier of your base station, in the form of <LRR-OUI>-<LRR-GID>:
- <LRR-OUI> is the IEEE OUI (Organizationally Unique Identifier) of the base station manufacturer, it consists of 6 hexadecimal characters. For BS using Semtech's Basics Station packet forwarder, the LRR-OUI is 0016C0.
- <LRR-GID> is the base station’s unique identifier relatively to the manufacturer. Allowed characters are [0-9][a-z]-_, max 256 characters. For BS using Semtech's Basics Station packet forwarder, the LRR-GID is the gateway-ID, often built based on a hardware reference like the MAC address.

The LRR-UUID is set by the base station manager during the provisioning step (see Adding base stations to ThingPark), it cannot be changed later on.
LRR-IDA short (32 bits) identifier of the base station, allocated by the ThingPark system at the end of the base station provisioning step.
- Unlike LRR-UUID, LRR-ID is not globally-unique but is unique within each ThingPark platform.
- The LRR-ID of each base station remains unchanged until the BS is deleted from the system, hence it is the main identifier throughout the BS lifetime.
ManufacturerThe BS manufacturer set by the base station manager during its declaration in the system.
- If the manufacturer is unknown, it may be set to Generic. This is typically the case for base stations using Semtech's Basics Station packet forwarder in absence of a branded ThingPark profile. To learn more about which manufacturers have branded ThingPark profiles, see Supported brands of base stations.
- Once the base station is added to the system, its manufacturer cannot be changed later on.
ModelThe BS model set by the base station manager during its declaration in the system.
- Thanks to ThingPark's base station catalog, each model is implicitly associated with a set of technical attributes such as the maximum number of antennas supported by the hardware, the packet forwarder type, etc.
- For base stations using Semtech's Basics Station packet forwarder, if there is no branded ThingPark profile, the manufacturer must be set to Generic and the model set to Basics Station packet forwarder.
- Once the base station is added to the system, its model cannot be changed later on.
Packet forwarderType of packet forwarder used by the base station to connect to ThingPark, among the following options:
- LRR (Long Range Relay): in this case, the field Packet Forwarder displayed in the base station's detailed page shows LRR XXX where XXX corresponds to the LRR version.
Note Clicking the button (displayed beside this field) shows detailed version of each software component of the base station (firmware, FPGA...).
- Basics Station.
Software versionLRR software version used by the base station.
This field is empty for BS using Basics Station packet forwarder.
RF RegionThe LoRaWAN® Regional Parameters document defines several RF profiles depending on the regional RF regulatory context. For each, ISM Band, these regional parameters are grouped into RF Regions which determine the radio frequency allocation plan for devices and base stations, together with a set of radio parameters used by the LoRaWAN® MAC layer.

For more information about the RF Regions supported by ThingPark catalog, see RF Regions.

Note Only RF Regions matching the ISM Bands associated with your deployment are proposed by the user interface.
TagsEach base station may be associated with one or several tags.

Tags may serve various purposes:
- Administrative tags, to easily group objects and filter them accordingly.
- Multicast tags, to allocate base stations to multicast groups. Multicast type of tags allow grouping all the base stations contributing to the transmission of downlink multicast packets of a multicast group. To learn more about multicast, see multicast groups.
DomainsIf the segregation based on domains has been enabled by an administrator, the Domains attribute contains the list of domains associated with the BS.
If your user account has domain restrictions, the domains you associate with your BS must match your domain restrictions without any domain prefix (only full domains can be assigned to resources). See About domains for more details.
CertificateX.509 certificate specific to each base station to secure its connection to the core network either in IPSec or TLS mode.
- This certificate is generated by ThingPark's Public Key Infrastructure (namely the Key Installer) and can be downloaded only once by the BS.
- Each certificate is associated with an expiration date, that is displayed in the Certificate column of the base station list, as well as in the Security widget under the Advanced tab of the base station's detailed page.
- Certificates are automatically renewed by the system and downloaded by the BS few days before they expire (true for LRR versions 2.4.73 onwards).
- If, for any reason, the BS needs to re-download its X.509 certificate, the base station manager must manually regenerate it from the user interface, under the Advanced tab of the base station's detailed page.
- Regenerating the BS certificate automatically revokes the current certificate to issue a new one. This action could be used in case the current certificate has been compromised.
Public KeyFor SaaS deployments, base stations using LRR packet forwarder rely on a pair of public and private keys to authenticate with ThingPark's PKI server (also known as the Key Installer).
- The key pair is generated by the LRR through the SUPLOG interface, as described in Generating and retrieving the base station’s Public Key.
- Setting a wrong Public Key in ThingPark shall prevent the base station from downloading its X.509 security certificate, hence it cannot connect to the network server.
- The Public Key authentication is not supported by Basics Station packet forwarder. Additionally, in the current release, the use of public key is not supported in self-hosted ThingPark Enterprise deployments.
Location modeTechnique used to locate the base station:
- Onboard Global Navigation Satellite System (GNSS) position: the location is automatically reported by a GPS receiver embedded in the base station. This mode is not supported for base stations using Semtech's Basics Station packet forwarder.
- Manual: the base station location (latitude and longitude) is manually set by the base station manager.

Manual location can be set using one of the following options:
- Either via the Search box on the top of the map,
- or by directly placing the marker on the map,
- or by setting the latitude and longitude in text input below the map. The compass button allows switching between decimal and degree/minute/second formats.

If the base station, supports LRR software, has a GPS receiver and can receive a stable GPS signal, the "Onboard GNSS position" mode should be used. Otherwise, the "Manual" mode should be used.
RF coverage typeThis attribute specifies if the BS provides permanent RF coverage or it only offers temporary coverage for recovery purposes.

- Permanent (default setting): the BS provides permanent RF coverage to surrounding devices. Accordingly, the uplink packets received through this BS are counted in ADR decisions. Additionally, this BS may be used to route downlink packets for all device classes A/B/C.

- Temporary and mobile: the base station does not have a fixed location, it provides temporary RF coverage to surrounding devices. This is typically used for the walk-by or drive-by use cases.
Accordingly, if the same uplink packet is received through both permanent and temporary base stations, the reception through the temporary BS does not impact ADR decisions and this temporary BS is not eligible for routing of DL traffic.
Otherwise, if the uplink packet is received only through the temporary BS, the device is assumed to be out-of-coverage of the permanent base stations; hence, the network triggers the RF recovery mode for this device, to boost its SF/TxPower and number of repetitions. This BS may be used to route downlink packets for class A devices only, since there is no guarantee that this moving BS will remain within the device's vicinity in class B/C modes.

- Temporary and stationary: the base station has a static location for a period of several days, up to a few weeks, but it does not provide permanent RF coverage. This is typically the case of seasonal gateways deployed to temporarily boost the RF coverage/capacity during specific events. The same UL/DL processing described in "temporary and mobile" mode applies for this "temporary and stationary" mode, with the only difference that this BS may be used to route downlink packets for class B/C devices besides class A. Note that this BS must be switched to "temporary and moving" once it leaves its temporary location, to avoid losing DL class B/C packets.
Station EUI or Gateway IDThis attribute is specific to Basics Station packet forwarder. It is used to build the corresponding ThingPark universally-unique identifier (also called LRR-UUID).
- The Station EUI / Gateway ID is provided by the manufacturer, it is often built based on a hardware reference like the MAC address.
- ThingPark's user interface provides a utility to compute the LRR-UUID from the Station EUI or Gateway ID, as described in Adding base stations to ThingPark.

You may retrieve the station EUI from the Basics Station logs, this is an ID6 (see LoRaWAN® Glossary. Example:

Station EUI: 8:ff:fe4a:bc32
4 groups of 16 bit blocks: 0008:00ff:fe4a:bc32
Gateway ID: 000800FFFE4ABC32
LRR-UUID: 0016C0-000800FFFE4ABC32
Additional informationAny useful administrative information related to the base station (free text).