Provisioning the base station on ThingPark GUI
ThingPark users must follow those steps to activate base stations on their account, using the ThingPark GUI:
Note You must be assigned either an Administrator or a Base Station Manager role to proceed with base station provisioning tasks. Read-only users (being assigned a "Viewer" role) cannot activate base stations.
Log in to your ThingPark account.
Browse on the left panel to Base Stations, then Create.
Select your base station's Manufacturer.
Note The manufacturer thumbnails are displayed by ordered of
their last usage. If you do not find your manufacturer in those
thumbnails, click "View More Manufacturers".Note For gateways using Basics™ Station packet forwarder, use the Generic manufacturer unless your manufacturer is explicitly listed.
On the following screen, select the desired Model from the drop-down list, which will appear according to the manufacturer selected in the previous step. You may change manufacturer by clicking the "Change manufacturer?" link at the beginning of the page.
Note Only models compliant with the ISM bands you specified are displayed by the drop-down menu. The supported ISM bands are displayed in gray, beside each Model, as shown in the following example.
Tip Start typing in the "Model" field to quickly look-up your target Model, as per the example above.
Note For gateways using Basics™ Station packet forwarder, use the Basics Station packet forwarder model.
Fill the form, guided by the following table:
Note Fields marked by an * are mandatory.
| Field | Description |
|---|---|
| Name | Friendly name given to your base station. You may use this name later-on to look-up your base station on ThingPark UI. You may edit this name at any time after base station creation, from the base station’s detailed dashboard. |
| LRR-UUID | Universally-unique ThingPark identifier of your base station. LRR-UUID is a <LRR-OUI>-<LRR-GID> concatenation: - <LRR-OUI> is the IEEE OUI (Organizationally Unique Identifier) of the base station manufacturer, it consists of 6 hexadecimal characters. - <LRR-GID> is the base station’s unique identifier relatively to the manufacturer. Allowed characters are [0-9][a-z]-_, max 256 characters. In case it is not printed on your base station’s sticker nor enclosed in your base station shipment, you can retrieve the LRR-UUID of your base station from SUPLOG: (1) Login to SUPLOG (see Connecting to SUPLOG for more details). (2) Browse to Identifiers then Get LRR UUID. (3) Copy the UID displayed on the third line. (4) Paste this UID on your base station creation form on ThingPark UI. Note: For Browan’s MiniHub models, the LRR-UUID is directly printed on the BS sticker, it corresponds to the hexadecimal characters following “(92)”, including the dash (e.g. 58A0CB-8007FF). Note: For gateways using LoRa Basics™ Station instead of LRR: The LRR-UUID must have the following format: 0016C0-xxxxxxxxxxxxxxxx (where xxxxxxxxxxxxxxxx being the gateway ID provided by the Manufacturer, often built based on a hardware reference like the MAC address). To retrieve the gateway ID, you may get 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 |
| RF Region | The “LoRaWAN® Regional Parameters” specification 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®’s MAC layer. For more information about the RF Regions supported by ThingPark catalog, see RF Region.) Note: Only RF Regions matching the ISM Bands associated with your deployment are displayed by the drop-down menu. |
| IPsec (X.509) for base station to TPW connection | When enabled by this field, ThingPark will automatically generate the base station’s X.509 security certificate upon its provisioning in the system. Then, once the base station is successfully provisioned, it shall automatically connect to ThingPark’s core network (more precisely the Key Installer server) to retrieve its personalized certificate. Note: This option is only relevant when the base station’s connection to ThingPark core network is secured either by IPSec or TLS. Do not enable this option if PKI is disabled in the base station. Note: This field does not control the effective PKI activation/deactivation on the base station, which remains entirely controlled by the base station image and any further configuration done on SUPLOG. For more details about PKI configuration in SUPLOG, see Configuring PKI. Note: for MiniHub and ST-Nucleo base station models: Since the bootstrapping process of these models is different from conventional linux-based models, users must disable the automatic generation of X.509 certificates during provisioning of these two models. Note: for gateways using BasicsTM Station instead of LRR: IPSec (X509) must be enabled, this will generate certificates that will be provided by the CUPS server to the Basics Station in order to connect to ThingPark core network. |
| Additional Information | Any useful administrative information related to the base station (free text). |
| Disable public key authentication | Tick this checkbox to disable the use of Public Key Authentication for ThingPark SaaS. Using Public Key Authentication is strongly recommended for SaaS platforms. If you disable this feature, a warning pop-up will display at the end of the base station creation process to remind users about this recommendation. Note: for MiniHub and ST-Nucleo base station modelsSince the bootstrapping process of these models is different from conventional linux-based models, users must disable Public Key Authentication for these two models. Note: for ThingPark SaaS This field is not displayed if the platform administrator has enforced the use of Public Key Authentication for all base stations. In this case, you must fill the “Public Key” field in this form. Note: for self-hosted ThingPark Enterprise This field is not displayed, since Public Key Authentication is mandatorily disabled for on-premise deployments (the feature being not yet supported). Note: for gateways using BasicsTM Station instead of LRR: This field is not displayed as it is not relevant for BasicsTM Station packet forwarder. |
| Public Key | Only relevant for TPE-SaaS, when “IPSec (X.509) for base station to ThingPark connection” is enabled. Note: this field is greyed when Public Key Authentication is deactivated by the preceding checkbox. See Generating and retrieving the base station’s Public Key, make sure to copy/paste the entire text including the BEGIN and END lines.  |
| Base station location mode | Technique used to locate the base station, Onboard Global Navigation Satellite System (GNSS) position (default mode): the position of the base station is expressed by its latitude and its longitude, which is automatically reported by a GPS receiver available in the base station. Note: this mode is only supported by gateways using LRR software, it is not supported by BasicsTM Station software. Manual mode: the position of the base station is expressed by its latitude and its longitude that are manually set by the base station administrator. Manual location can be set using one of the following options: Either use the Search box on the top of the map using the geocoding service. Or place the marker on the map. Or set the latitude and longitude in text input above the map. The compass button allows the switch between decimal and degree/minute/second formats. Note: this is the only mode supported by gateways using LoRa Basics™ Station software. 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. |
If the permission segregation based on domains has been enabled by an Administrator user, the Domains field is available to set the list of domains associated with the base station. If your user account has domain restrictions, the associated domains must match your domain restrictions without any domain prefix (only full domains can be assigned to resources). See Domains for more details.
Once the base station is successfully provisioned on ThingPark, the "Initialization" status appears in the user interface, with an orange dot.
Note Whenever the base station comes online (meaning it has a valid network connection), it may take a couple of minutes for the base station to download its IPSec certificate, establish the VPN connection, and the GUI to update the connection status to "Connected" with a green dot.
At any time, if your base station goes offline (for instance, it is switched-off), its status shall show "Connection Error", with a red dot. A gray dot means "Radio Error", which typically highlights an internal RF error (radio may be switched off) while the base station is still connected to ThingPark's core network.
If your base station could not come up online after being configured and provisioned, see some debug tips in Troubleshooting the base station connectivity.