0% found this document useful (0 votes)

104 views

TP-Wireless-5.2.2-Network Manager User Guide-Rev2

Actility Network Manager User Guide-rev2

Uploaded by

Ofer Kraus

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

104 views

TP-Wireless-5.2.2-Network Manager User Guide-Rev2

Actility Network Manager User Guide-rev2

Uploaded by

Ofer Kraus

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 80

ThingPark Wireless

Network Manager User Guide

Under NDA
NOTICE

This document contains proprietary and confidential material of ACTILITY SA. This document
is provided under and governed by either a license or confidentiality agreement. Any
unauthorized reproduction, use, or disclosure of this material, or any part thereof, is strictly
prohibited.
The material provided in this document is believed to be accurate and reliable. However, no
responsibility is assumed by Actility SA for the use of this material. Actility SA reserves the
right to make changes to the material at any time and without notice. This document is
intended for information and operational purposes only. No part of this document shall
constitute any contractual commitment by Actility SA.

© 2019 ACTILITY SA. All rights reserved.

Portions of this documentation and of the software herein described are used by permission
of their copyright owners.
Actility, ThingPark, are registered trademarks of Actility SA or its subsidiaries may also be
registered in other countries.
Other denoted product names of Actility SA or other companies may be trademarks or
registered trademarks of Actility SA or its subsidiaries, or their respective owners.

Headquarters
Actility Lannion,
Actility S.A 4 rue Ampère BP 30225
22300 Lannion France
www.actility.com

Under Non-Disclosure Agreement

Version Date Author Details

4.1 2017/09/29 ML Ancelle Initial version
- Content moved from the Supplier User
Guide to the Network Manager User
Guide.
- BS alarms have been implemented.
5.0 2018/03/27 M. Tasmagam- Version
betova - NFRs included for 4.2, 4.3 and 5.0.
5.0- 2018/03/31 M. Tasmagam- Version: 5.0
rev2 betova - Base Station provisioning verified
according to the NFR 684.
ML Ancelle - Using the Base Stations GUI updated
visually and textually.
5.0- 2018/04/03 M. Tasmagam- Version: 5.0
rev3 betova - Base Stations alarms section
interpretation and guidelines.
- General Settings part added.
5.0.1 2018/08/16 ML Ancelle Version. 5.0.1
- LRR Watchog capability
5.1 2018/06/25 ML Ancelle Version: 5.1
- Multicast Group Tagging
- Update RF Region
- Recue SSH Terminal
- ISM Bands
5.2 2018/08/16 ML Ancelle Version 5.2
- IPv6 support on Base Stations
- TLS support on Base Stations
5.2.2 2019/05/16 R. Soss - Major editorial changes
- Updates for version 5.2.2 (see What’s
New section)

Under Non-Disclosure Agreement

REFERENCE DOCUMENTS

Documents Author
01 ThingPark Wireless Supplier User Guide Actility
02 ThingPark Wireless Device Manager User Guide Actility
03 ref-tpw5.2-alarms-base-stations Actility
04 ThingPark Wireless BS-Commissioning User Guide Actility
05 ThingPark Wireless Radio Parameters User Guide Actility
06 ThingPark Wireless Operator User Guide Actility
07 ThingPark Wireless Spectrum Analysis User Guide Actility

WHAT’S NEW

New/Enhanced Functionalities For More Information, See… Release

RDTP-12998: Alarm history 7 Working with Base Station Alarms 5.2.2-3

Under Non-Disclosure Agreement

NOTICE ............................................................................................................. 2
VERSIONS.......................................................................................................... 3
REFERENCE DOCUMENTS ....................................................................................... 4
WHAT’S NEW .................................................................................................... 4
TABLE OF CONTENTS ............................................................................................ 5
ACRONYMS AND DEFINITIONS ................................................................................ 7
SCOPE.......................................................................................................10
THINGPARK SOLUTION OVERVIEW ...................................................................11
LOGGING INTO THE NETWORK MANAGER ..........................................................12
3.1 Prerequisites .............................................................................................................. 12
3.2 Supplier Access .......................................................................................................... 12
3.3 Subscriber access ....................................................................................................... 13
USING THE GRAPHICAL USER INTERFACE ............................................................15
4.1 Searching Base Stations ............................................................................................. 15
4.2 Base Stations List ....................................................................................................... 16
CREATING A NEW BASE STATION .....................................................................19
VIEWING/EDITING A BASE STATION .................................................................23
6.1 Main Frame................................................................................................................ 23
6.1.1 Indicators Frame ................................................................................................ 24
6.1.2 Uplink/Downlink Packets Frame ........................................................................ 27
6.1.3 Ownership Frame ............................................................................................... 28
6.1.4 Status Frame....................................................................................................... 28
6.2 Base Station Antennas ............................................................................................... 28
6.3 Base Station System .................................................................................................. 33
6.4 Base Station RF Cell Information ............................................................................... 34
6.5 Base Station WAN Backhaul Information .................................................................. 39
6.5.1 Backhaul statistics between LRR and LRC-cluster .............................................. 39
6.5.2 Per-interface backhaul statistics ........................................................................ 41
6.5.3 IEC uplink Queue ................................................................................................ 43
6.5.4 Other WAN indicators ........................................................................................ 43
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 5
6.6 Administering Base Station ....................................................................................... 43
6.6.1 Settings ............................................................................................................... 44
6.6.2 Maintenance ...................................................................................................... 45
6.6.3 Configuration ...................................................................................................... 47
6.6.4 Advanced Maintenance ..................................................................................... 49
6.6.5 Backup Configuration ......................................................................................... 55
6.7 Base Stations Tagging ................................................................................................ 55
6.7.1 Prerequisites....................................................................................................... 56
6.7.2 Tagging a Base Station........................................................................................ 56
6.7.3 Tagging Multiple Base Stations .......................................................................... 57
6.7.4 Searching for Base Stations with a Tag .............................................................. 58
6.7.5 Deleting Tags from Base Stations....................................................................... 58
6.8 Modifying a Base Station ........................................................................................... 58
6.9 Deleting Base Station................................................................................................. 58
WORKING WITH BASE STATION ALARMS ...........................................................59
7.1 Searching Alarms ....................................................................................................... 60
7.2 Troubleshooting Base Stations .................................................................................. 62
7.2.1 System Alarms .................................................................................................... 62
7.2.2 RF Cell Alarms ..................................................................................................... 65
7.3 Acknowledging Alarms .............................................................................................. 70
7.4 Configuring Alarms .................................................................................................... 71
7.4.1 Configuring an Inactivity Alarm .......................................................................... 71
7.4.2 Receiving Alarm Notification Email .................................................................... 72
USING SETTINGS ..........................................................................................73
8.1 Accessing the Settings panel and Viewing Account Details ...................................... 73
8.2 Setting Alarm notification e-mails ............................................................................. 74
8.2.1 Setting Alarm Notifications Emails in Basic Mode ............................................. 74
8.2.2 Setting Alarm Notifications Emails in Advanced Mode ..................................... 75
8.3 Setting ISM Bands ...................................................................................................... 76
MORE ABOUT LORAWAN™ RADIO STATISTICS ..................................................77
WHAT’S NEW HISTORY .................................................................................78
ABOUT ACTILITY ..........................................................................................80

Under Non-Disclosure Agreement

Acronyms Definitions
ABP Activation By Personalization
ADR Adaptive Data Rate
AES Advanced Encryption Standard
AS Application Server
ATM Asynchronous Transfer Mode
BPM Business Process Management
BSS Billing Support Systems
CRC Cyclic Redundancy Check
CSP Communication Service Provider
DC Duty Cycle
End Device A sensor or actuator
ESP Estimated Signal Power
ETSI European Telecommunications Standards Institute
HAN Home Area Network
HSM Hardware Security Module
IaaS Infrastructure As A Service
IEC International Electrotechnical Commission
IoT Internet of Things
ISM Industrial Scientific Medical
GSCL Gateway Service Capability Layer
GTM Go To Market
KPI Key Performance Indicator
LC Logical Channel
LoRaWAN™ Long Range Wide Area NW
LPWAN Low Power Wide Area Network
LRC Long Range Controller

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 7
Acronyms Definitions
LRR Long Range Relay
MAC Media Access Control
M2M Machine-2-Machine
MTBF Mean Time Before Failure
NAT Network Address Translation
NW Network
NSCL Network Service Capability Layer. Also called RMS.
OBIX Open Building Information Exchange
OSS Operations Support Systems
OTA Over The Air
PER Packet Error Rate
PKI Public Key Infrastructure
POC Proof Of Concept
REST Representational State Transfer
RF Radio Frequency
RIT Receiver Initiated Transmit
RSSI Received Signal Strength Indicator
SaaS Software as a Service
SF Spreading Factor
SLRC Secured LRC (VPN Concentrator)
SMP System Management Platform
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SNR Signal to Noise Ratio
SSH Secure SHell
SSO Single Sign On
TLS Transport Layer Security
TWA ThingPark Wireless Application

Under Non-Disclosure Agreement

The purpose of the Network Manager application is to manage the LoRaWAN™ Radio Access
Network (RAN) by creating and administrating LoRa gateways (also known as Long-Range
Relays – LRR).
This guide provides ThingPark’s network providers with all the information needed to use the
Network Manager application that could be subscribed by the network provider. A network
provider could either refer to the roll-out teams within the Operator’s organization, the
system integrator of the Operator or the subscriber that also manages his own gateways
(typically the case of Managed Customer Networks).

Under Non-Disclosure Agreement

The ThingPark set consists of four main key components:

▪ ThingPark Wireless – Core network and OSS
▪ ThingPark OS

▪ ThingPark X

▪ ThingPark Enterprise
The ThingPark platform is a modular solution enabling Network Operators to:
▪ Deploy LPWANs based on LoRaWAN™ or LTE with ThingPark Wireless.
▪ Manage, activate and monetize IoT bundles (Device, connectivity and application)
with ThingPark OS.

▪ Provide value-added data layer services, such as protocol drivers and storage with
ThingPark X.
ThingPark OSS acts as the central System Management Platform (SMP), enabling all other
ThingPark platform modules with base capabilities such as subscriber management,
centralized authentication and access rights, and workflow management.
ThingPark Enterprise is an Internet of Things (IoT) platform that manages private LoRa®
Networks. The ThingPark Enterprise edition is used by companies to support their specific
business.

Operator & Enterprise Application Servers

On-Line Shops
OSS & BSS Management

API Layer

ThingPark OS ThingPark Wireless Core NW & OSS ThingPark X

ThingPark Enterprise

User Portal Store (E-Shop) Operator Connectivity Address Usage Record Supervision, System OCP Edition SaaS Edition RMC
Manager Manager Manager Manager (UDR) Monitoring, Management
Alarms Platform (SMP)
BPM Engine Market
Drivers Connectors

Wireless Device Network

Logger Manager Manager LTE Security Geo-Location
Vendor Supplier Billing & EPC Server Server
Manager Charging ETSI M2M ETSI M2M
Manager Connectors
Net GSCL NSCL

Spectrum Network LoRaWANTM LoRaWANTM

Analysis Tool Survey Network Join Server ²
Local GW (GSCL)
Server

LoRaWANTM LRR (Gateway)

Any Device
Radio Network TPW Air Interface Message Broker Cluster Computing
Planning Tool Dimensioning Tool (Kafka) (Spark) LoRaWANTM /LTE Devices

Figure 1 – ThingPark Solution Architecture Description High Level Product Illustration

Please note that the modules above may be representing a physical server, a function, a service or a business support layer as part of the
overall ThingPark solution and not necessarily a physical HW server

Under Non-Disclosure Agreement

This section shows you login tasks that are specific to the Network Manager, especially when
logging in for the first time.
To perform other authentication operations as password creation and reset, forgotten
password, account authentication and reset, and so forth follow the guidelines provided by
the interface messages when prompted or contact your Vendor.
Refer to the Administrator for further information regarding logging policy.

3.1 Prerequisites

To login to Network Manager Application, you should have a Network Partner role. ThingPark
Wireless supports two Network Partner types:
1. Supplier type (also known as Network Provider): this is the conventional mode dealing
with Network Manager application. The Operator’s Network Provider administrates
and maintains the LoRa gateways provisioned on the Operator’s public network.
2. Subscriber type: addresses the use case of subscribers having access to the Network
Manager application to administrate their own gateways. A typical use case of this type
is the Managed Customer Networks, where the LoRa gateways are hosted on customer
premises but are provisioned/backhauled on the Operator’s LoRaWAN network.

3.2 Supplier Access

Supplier/Network Providers can access Network Manager application using the following URL:
https://<operator-domain.name>/admin/

The following window appears:

Under Non-Disclosure Agreement

Then the following window appears; you are now logged in to Network Manager application.

3.3 Subscriber access

If you have a subscriber account, you can connect to Network Manager application using one
of the following URLs:
▪ Via ThingPark Portal (if the option is enabled by the Operator): https://<operator-
domain.name>/portal/

Enter your e-mail and password.

Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 13
▪ Or directly via the URL: https://<operator-domain.name>/networkManager/

1. Click Sign in.

2. In the pop-up window that appears, enter your e-mail and your password.
Then you are now logged in to Network Manager application, the following screen is
displayed:

Under Non-Disclosure Agreement

When you log into the Network Manager application, the following screen is displayed:

The interface is based on a left sidebar menu and a main application frame showing:

▪ A “Create” button, to add new base stations

▪ A search bar to find base stations based on specific criteria

▪ A Map/List space to show the base station details:

o The “Map” view displays the base station locations on the map, the user can
click on a base station to view its details: connection status, stats, etc.
According to the choice of your operator, the map supports Google Maps,
OpenStreetMap or Baidu Maps.
o The “List” view displays the base station details, it is organized in pages of 100
base stations. To switch pages, please use the arrows available at the bottom
of the page:

4.1 Searching Base Stations

The Search bar looks like this:

▪ Location: inserting a location (for instance, a city name) zooms at the map on the
desired location. This search option is only valid for “Map” view.
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 15
For “List” view, the checkbox “Restrict search to visible map area” allows filtering the
base station list to only base stations located on the corresponding map view.

▪ Identifier: This field determines the base station of interest based on its name, LRR-ID
or LRR-UUID. Note: This field is case sensitive.

▪ Tag: Allows searching for all base stations associated with a given tag. For more details
about base station tagging, please refer to 6.7.2 Tagging a Base Station.
Other search options include:

▪ Version: search for all base stations having a specific LRR software version.

▪ Software restart: search for all base stations that have restarted since a specific
date/time.

▪ Min. remaining DC: displays only the base stations whose remaining Duty Cycle is
higher than or equal to a specific threshold. This option allows a quick monitoring of
congested base stations.

▪ Alarm: shows only base stations associated with a given alarm state (only active alarms
are considered). For more information about base station alarms and their severity,
please refer to Section 7 Working with Base Station Alarms.

Note that the list view of the Search section is updated only when the user clicks the Search
button.

4.2 Base Stations List

The Base Stations list displays all the base stations issued from the filtering criteria defined in
the Search bar. The following figure shows an example screenshot of the List view:

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 16
The displayed fields are the following:
▪ Name (LRR ID) / model: base station name, followed by the LRR-ID (or LRR-UUID)
between parenthesis then the base station model on the following line.

▪ Version: LRR software version of the base station

▪ Software restart: date/time of the last LRR software restart

▪ Power source: Power supply configuration if it is provisioned for the base station
(inherited from the BS profile). It could be either “mains”, “power over ethernet”,
“wind + battery” or “solar + battery”.

▪ Min remaining cap up/down: not supported in the current release.

▪ Average packets up/down: average number of packets per hour in uplink (from device
to base station) or downlink (from base station to device) directions, estimated over
the last hour preceding the reception of the last uplink frame.
Note: for uplink frames received by several base stations at the same time (thanks to
macro diversity), the frame is counted only for the uplink best-serving gateway (that is
to say, the gateway having the highest reception signal to noise ratio (uplink SNR)).

▪ Alarm: Number of active alarms currently raised on this LRR but not yet acknowledged.

▪ Locate: when the user clicks the “Locate” icon, the Network Manager application
opens a new window and locates the base station on the map. The position of each
base station is either based on the GPS coordinates reported by the LRR or on the
coordinates manually provisioned. To configure the location mode, please refer to
Section 6.6.3.2 Update Location and Altitude.
When clicking on a Base Station, a pop-up window displays the base station details, as
per the following screenshot:

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 17
From this pop-up it is possible to go to the alarms list, view the Base Station’s details
or edit the Base Station’s information.
The icon on the map indicates a Base Station with uncleared alarms.
To exit the “Locate” view, please press the Escape key of your keyboard.

On the Base Station list, the user can sort columns by ascending or descending order; by
clicking the arrow button on the right of each column as per the following screenshot:

Note: The sorting function applies to the current page only, it doesn’t sort the list elements
across several pages.
The “Columns” menu allows the user to customize its column view by removing some columns
not relevant for his day-to-day activities.

For each base station displayed in the list, the following actions are supported:

▪ View : use this option to consult the base station details in read only mode

▪ Edit : use this option to edit the base station details.

▪ Tag : Opens the base station tag manager to associate a tag to this base station.
For more details about tag management, please refer to section 6.7.

▪ Delete : use this option to delete a base station, a pop-up window with a
confirmation message will be display to make sure users don’t accidentally delete base
stations.

Under Non-Disclosure Agreement

The base station provisioning process allows the Network Partner to add new base stations to
the network.
To create a new base station, go the “Base stations” panel and click the “Create” button:

There are two different modes to identify a base station during provisioning phase:
1. Either using the LRR-UUID (recommended mode): this ID refers to the Universal
Unique Identifier of the LRR. The advantage of this mode is that, unlike the LRR-ID
whose unicity is not guaranteed across the different gateway manufacturers, the LRR-
UUID is always unique. The UUID consists of a manufacturer-specific prefix (the IEEE
OUI of the base station vendor) followed by the vendor-related base station identifier.
In this mode, the LRR-UUID is provisioned during base station creation whereas the
LRR-ID is assigned by ThingPark.
2. Or using the LRR-ID: This mode is only kept for backward compatibility purpose. In this
mode, the LRR-ID is statically associated with the base station by the vendor;
therefore, collision may occur!
The information required to create a new Base Station is the following:

▪ Base station ID: LRR-UUID OR LRR-ID (depending on the “Identification mode”)

o LRR UUID: has the format <LRR-OUI>-<LRR-GID>, where:
▪ <LRR-OUI> is the IEEE OUI of the Base Station vendor (6 hexadecimal
characters)
▪ <LRR-GID> is the Base Station identifier relatively to the vendor. The
allowed characters are [0-9][a-z]-_ and maximum length is 256
characters.
Note that if the Base Station has been provisioned with an LRR UUID, it means
the LRR UUID field could not be updated any longer.
Note that the LRR UUID and SMN are written on the sticker on the Base Station.

▪ Serial Marketing Number (SMN) (optional): the format is 0000-XX-0000-0000

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 19
▪ Manufacturer: defines the base station manufacturer: for instance, Cisco, Kerlink,
Ufispace, Multitech, Tektelic…)

▪ Model: defines the base station profile, the drop-down list is filtered based on the
selected Manufacturer

▪ Name (optional): Base station given name.

▪ VPN & authentication (only valid for LRR-UUID identification mode): enables the
automatic generation of the Base Station certificate for IPSec or TLS VPN security
modes on the backhaul interface between LRR and the LoRaWAN core network. This
field is greyed if the option is not activated at operator level.
Note that for LRR-ID identification, IPSec/TLS modes are also supported by ThingPark,
but the Base Station certificate is not automatically generated by TWA upon Base
Station created (needs to be generated manually by the Network Partner).
The following figure illustrates an example for a base station creation window using LRR-UUID
mode:

New in release 5.2.2: Enhanced Security Access to Key Installer (RDTP-7582).

In order to retrieve its security configuration (for instance, the Base Station certificate), each
Base Station needs to connect to ThingPark Key Installer Server.
▪ Before release 5.2.2, the access to the Key Installer is secured by IP
filtering/whitelisting.
▪ Starting release 5.2.2, a new approach is supported as an alternative to IP filtering: the
Public Key Authentication mode. In this mode, each base station generates a random
public RSA key and derives an associated private key. While the public key can be

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 20
shared with the network (i.e. provisioned in TWA Network Manager and exchanged
with Key Installer), the private key is a secret key that never goes out of the base
station. Based on this public/private key pair, the Key Installer exchanges a challenge
with the base station to fully authenticate its identity. After successful authentication,
the base station is granted secure access to its personalized configuration archive; each
base station can only retrieve its own tarball (i.e. cannot download tarballs of other
base stations). Hence, even if the security of one base station is compromised due to
theft (for instance), the security of other base stations is not compromised.

NOTE: This feature is only compatible with LRR-UUID identification mode.

To use this feature, the following steps are required:

1. For each base station, login to SUPLOG (LRR local administration GUI) to retrieve the
public key of the Base Station. For more details on this step, please refer to Section
6.6.4.1 Remote Access via Reverse SSH. NOTE: The base station image should be
configured to use the Public Key Authentication mode.
2. In Network Manager application, provision this public key retrieved from SUPLOG. This
can be either done at base station creation or updated for an existing base station, it
is only available if BS security (TWA parameter “defaultBsSecurity”) is configured to
"IPsec or TLS (X.509 certificates)".

Public key provisioning during base station creation:

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 21
“Disable public key authentication” flag is displayed if the operator configuration
allows this mode as an option. If this checkbox is ticked, the legacy mode (based on IP
filtering and shared passwords) remains usable.

Note: Do not forget to press the “Create” button when you are done provisioning the required
fields.
 A message displaying that the Base Station is successfully created is displayed in
the bottom left corner of your screen, then the base station becomes visible in the
list.
 You should see something like the following capture in the List tab.

Note that after a new Base Station has been created, it stays in status VALIDATING until your
Operator Manager has validated the Base Station in the network, unless the Operator has
delegated this BS validation action to the Network Partner.
Note that if the Base Station has been provisioned with the LRR ID, the LRR UUID field can be
later updated to enable future LRR migration to the LRR SW version superior to 2.2.20.

Under Non-Disclosure Agreement

To view all the details of a base station in read-only mode, click the button in the “List”
view. If the user wants to edit the base station configuration or perform administrative actions
(for instance launch the RF scan functionality, reset the radio board…etc.), then he should click
the button.
Once a base station is selected for view/edit, it appears in the sidebar menu under the “Base
station” root node as illustrated by the following figure:

6.1 Main Frame

This frame displays the basic information of the Base Station such as the model (referring to
the base station profile), name, LRR ID, LRR UUID and SMN (Serial Number).
The “Administrative info” space is a free-text field that can be used by the administrator to fill
additional information about the gateway. This is field is also used by the BS-Commissioning
tool to provision specific installation details during on-site commissioning (for instance, MAC
address…). For more information about this tool, please refer to [4].

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 23
Based on the base station characteristics inherited from the BS model/profile, the ThingPark
Wireless OSS displays the installation information such as:

▪ Power source: if the power supply configuration is defined for the corresponding
model, it can take one of the following values: Mains, Power Over Ethernet (PoE), Wind
+ Battery, Solar + Battery. Note that, if the base station model is equipped with several
power sources, only the primary source is referenced in this field.

▪ GPS receiver: indicates whether the gateway is equipped with an embedded GPS
receiver.

▪ Antennas: this configuration indicates how many antennas are available for this
model. Note: pico/nano gateways are equipped with a single antenna whereas macro
v2 gateways may be equipped with up to 3 antennas depending on their model.

▪ WAN backhaul: indicates which backhaul options are supported by the base station
model. Ethernet and Cellular are the most common modes, but satellite backhaul is
also possible. For Cellular mode, the administrator can enter the SIM card details by
clicking the “Details” button then filling the fields related to the SIM card and
equipment identity (IMEI).

▪ Software version: indicates the LRR software version used by the base station. More
details on the software version (including operating system version, firmware, HAL,
FPGA…) can be found by clicking the “Custom versions” button.

▪ VPN and Authentication: enable/disabled. Enabled means that the Base Station
certificate is automatically generated by TWA upon Base Station creation
Note that “VPN and Authentication” flag does not show the dynamic status of the Base
Station backhaul security mode, it only determines whether automatic generation of
the BS certificate is enabled or not.
Note: to provision the Public Key for existing base station (RDTP-7582):

▪ In base station dashboard, click “Manage Public Key” button, then fill the Public Key.

The location of the Base Station on the map can be provided in two different ways:
1. Either based on the GPS position reported by the LRR (using the GPS receiver)
2. Or manually set by the administrator in Network Manager GUI / web-services. For
more details about manually provisioning the base station coordinates, please
refer to Section 6.6.3.2 Update Location and Altitude.

6.1.1 Indicators Frame

A summary view of indicators for System, RF Cell indicators and WAN backhaul indicators is
available for the LRR as shown in the following screen.
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 24
Note that you can reload all indicators by clicking the reload button in the top-right
corner.

6.1.1.1 System Indicators

While the “Installation” information essentially reflects the static system characteristics
inherited from the BS profile, the Network Manager application also displays the dynamic
system indicators reported by the LRR. Available system indicators include the following:
o Power status: when the status is “UP”, Network Manager displays “Mains”
whereas when the status is “DOWN”, Network Manager displays “Battery”.
o CPU load measured over the last reporting LRR period to ThingPark OSS (5
minutes by default). The measured metric corresponds to the average +
standard deviation of the CPU load.
o RAM usage: ratio of used memory with respect to total available RAM,
averaged over the last 5 minutes (default LRR reporting periodicity).
o Mass Storage Usage: file system, providing the current disk usage per disk
partition.
o GPS receiver status, three different states are possible: Not present,
Locking/No signal (i.e. GPS is present but down), Locked (i.e. GPS is up and
running).
o Time synchronization status, three different states are possible: GPS, NTP and
Local.
o Software restart date
o Class B support, three different states are possible: Not supported, Supported
but not operational, Supported and operational. Please note that Class B
support is enable/disabled by the Network Partner on each Base Station from
the Administration panel (for more information, please refer to Section 6.6.1.1
Advanced Settings).

Under Non-Disclosure Agreement

6.1.1.2 RF Cell Indicators

RF Cell indicators include Uplink and Downlink traffic indicators on the RF interface. Available
indicators include the following:

▪ Uplink/downlink average packets: hourly average number of packets, estimated over

the last hour.

▪ Last packets: date and time of the last packet

▪ Most busy channel: indicates the RF channel having the highest uplink/downlink duty
cycle over the last 10 minutes. The duty cycle statistics are provided for each antenna
(in case the base station has several antennas). The antenna having the highest duty
cycle is indicated as Ax (for instance, A1, A2, A3…).
o Duty cycle: utilization of the duty cycle on the busiest channel
o Rem. capacity: remaining capacity of the duty cycle (not yet supported in the
current release).

Note: Uplink corresponds to packets sent from the device to the network, whereas downlink
corresponds to packets sent from the network to the device.

6.1.1.3 WAN Backhaul Indicators

The supported LRRs may have multiple backhauling options; it could be Ethernet or Cellular
or others.
The WAN indicators summary provides the following information:

▪ Connection status to each LRC in the LRC-cluster. Please note that LRC-1 is the primary
LRC while LRC-2 is the hot standby / secondary LRC used in case of switchover to
support High Availability.

▪ For each network interface (eth = Ethernet, wwan = Wireless WAN (typically cellular,
but could also be WiFi backhaul)):
o Connection status to LRC cluster
o Activity: Time duration with this interface in “Up and Used” state, since the
start of the WAN stats’ recording. Note that the start date/time of WAN stats -
for each network interface - is logged by Network Manager in WAN Backhaul
panel. It is also possible to reset statistics to initialize the aggregation period.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 26
o Average round trip latency estimated over the last reporting interval (5 minutes
by default).
o Dev. round trip latency: standard deviation of the network round trip delay
between the LRR and the LRC over this interface, estimated over the last
reporting interval (5 minutes by default).
o Total traffic volume (in bytes) for both transmission (TX) and reception (RX)
flowing through this interface, aggregated since the start of the stat
aggregation period for this WAN backhaul interface.
o Avg. Bitrate for both TX and RX, averaged over the last reporting interval (5
minutes by default).

6.1.2 Uplink/Downlink Packets Frame

The uplink/downlink packets and payload frame present the number of packets or payload
size transmitted uplink and downlink by an LRR with multiple time aggregation options (Daily,
Hourly, Last 7 days, Last 15 days).

Note that all charts can be exported or printed by clicking on the top right menu icon in
the chart as shown in the following screen.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 27
6.1.3 Ownership Frame
This section presents potential site information regarding the hosting of an LRR. This allows
networks managers to access the contact information for a specific high point or roof-top site.

6.1.4 Status Frame

This section presents the last modification history date and time, as well as the Admin user
name responsible of this last modification.

6.2 Base Station Antennas

You can access the Antennas list along with their properties by clicking “Antennas” in the left
sidebar.

Under Non-Disclosure Agreement

▪ ID

▪ Type:
o Omnidirectional: the horizontal antenna pattern covers 360°, typical case for
LoRaWAN deployments.
o Directional: the antenna has a directional pattern on the horizontal plane to
maximize the radiated energy on a given direction. Directional antennas are
typically used in tri-sector antenna deployments where the Base Station has
three different antennas, each one covers around 120° on the horizontal plane.
o Undefined: the antenna type is not provisioned by the administrator.

▪ Antenna gain: measured in dBi units (decibels-isotropic)

▪ Azimuth: the rotation of the whole antenna around a vertical axis, measured in
degrees. Azimuth is only relevant for directional antennas (not applicable for
omnidirectional antenna types).

▪ Used: Yes/No. The activation state of each antenna depends on the number of
antennas configured in the “RF hardware configuration in use” field.

The “RF hardware configuration in use” field determines the effective antenna configuration
mode. Please note that the maximum configuration supported by the Base Station hardware
is defined in the Base Station profile, but the effective hardware configuration in use could be
downgraded for each Base Station with respect to the maximum hardware capability, using
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 29
the “RF hardware configuration in use” parameter in Network Manager, under the Antennas
panel, as shown by the following figure:

For example, for a Kerlink iBTS gateway with 2 radio boards and 2 antennas physically cabled
to the gateway, the Base Station Profile shall be configured to “1 sector, 2 antennas, 2 boards”,
then each Base Station can be individually configured to one of the following configurations:
▪ 1 sector, 1 antenna, 1 board
▪ 1 sector, 2 antenna, 1 board
▪ 1 sector, 2 antenna, 2 board
Note that the hardware configuration options proposed in the drop-down list are limited by
the maximum hardware capability defined in the Base Station profile associated with this BS.
The following hardware configurations are fully supported by ThingPark in the current release:

▪ For V1 gateways (based on Semtech’s V1 reference design):

▪ 1 sector, 1 antenna, 1 board (mono-sector 1*8): s1_a1_b1

▪ For V2/V3 gateways (based on Semtech’s V2 reference design):

▪ 1 sector, 1 antenna, 1 board (mono-sector 18 or 116): s1_a1_b1

▪ 1 sector, 2 antennas, 1 board (mono-sector 2*8): s1_a2_b1 → Antenna

Diversity enabled

▪ 1 sector, 2 antennas, 2 boards (mono-sector 2*16): s1_a2_b2 → Antenna

Diversity enabled

▪ 1 sector, 1 antenna, 4 boards (mono-sector 1*64): s1_a1_b4

▪ 3 sectors, 3 antennas, 3 boards (tri-sectors 18 or 116): s3_a3_b3

To view the detailed Antenna description, please click . To update the antenna details,
please use the icon.
Clicking either icon given above transfers you to the page containing a full description of
the concerned Antenna divided into the following sections:

▪ Antenna: showing the Antenna ID, its type, horizontal half power beamwidth (HPBW,
only relevant for directional antennas), azimuth (only for directional antennas) and
additional administrative information (free text fields).

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 30
Note: the antenna gain is in read-only mode in this screen, to change the antenna gain
or RF cable losses, the user should go to the Administration panel. For more details,
please refer to Section 6.6.3.3 Update Antenna Gain and Cable Loss.
Note that precise setting of the antenna gain and cable loss is very important to adjust
the transmission power of downlink frames by the base station without violating the
local regulations.

▪ Location: in this section, the user can view/edit the location of each RF antenna as well
as its height above the ground and sea levels (the latter reflects the absolute antenna
height).
Note that the information provided in this section is necessary for network geolocation
(using sophisticated triangulation algorithms) where it is crucial to precisely provision
the antenna location if it is different from the Base Station GPS location; this could be
the case when the RF antennas are installed several meters away from the LoRa Base
Station on a building rooftop, for instance.

▪ Cable: showing the RF cable loss (in dB) and delay (in nanoseconds). The RF cable loss,
together with the RF antenna gain, are mandatory information required by the Base
Station to use the correct downlink transmission power in compliance with the local
regulations. This information could be either derived from field measurements or
directly estimated from the cable’s electrical specification provided in its datasheet.
Note that precisely setting the RF cable delay is very important for geolocation use
cases, this information is reported to the location solver to precisely estimate the
device location using TDoA algorithms.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 31
▪ Environment: optional information but very useful for troubleshooting of any
potential radio/coverage issues. This section provides details about the main
propagation environment covered by the antenna (dense urban, urban, suburban,
rural…etc.), as well as the installation mode (indoor, outdoor rooftop, outdoor on
tower). It also allows setting the antenna clearance in each direction to highlight the
presence of any major obstacles in the direction of the antenna coverage.

▪ TX Power: this section reports the maximum and effective radiated transmission
power (EIRP) used by the LRR for RX1 and RX2 slots. The maximum EIRP is based on
the RF Region configuration setting (reflecting the maximum allowed radiated power
set by the regulatory limits) whereas the effective EIRP reflects the real radiated power
estimated by the LRR based on the RF gain / cable loss configured by this antenna and
the calibrated TX power levels supported by this Base Station.

▪ Images: to upload any relevant photos taken during BS installation.

Note: do not forget to click at the top-right corner once you complete editing the
antenna details. If you close this screen without saving the last configuration, the new changes
will not be considered.
Besides the RF antenna, Network Manager application allows the user to provision the details
of the GPS antenna; this is available directly in the “Antennas” tab. The most important
information about GPS antenna is the cable delay (in nanoseconds) since it directly impacts
the geolocation precision for TDoA algorithms.

Under Non-Disclosure Agreement

By clicking the System menu in the left sidebar (as shown by the following figure), the user
can access the detailed statistics about the LRR system: CPU, RAM and partition usage.

For each metric, the following display options are supported:

▪ Daily Average for the last 7 days
▪ Daily Average for the last 15 days
▪ Hourly average for the last 7 days
▪ Hourly average for the last 15 days
Depending on the selected aggregation period and history length, Network Manager tool
displays the average, average + standard deviation and the maximum value of each metric.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 33
Additionally, Network Manager records and displays the minimum/ maximum levels reported
for each metric since the last time the statistics were reset. This allows the Network Partner
to keep the historical minimum/maximum values beyond the 15-days timeline display limit.

Note that it is possible to reset the statistics by clicking Reset Statistics. This action resets only
the min/max values; the chart data remains stored.

6.4 Base Station RF Cell Information

As described in Section 6.1 Main Frame, the summary overview for an LRR presents
information on the busiest logical channel depending on duty cycle information. However, you
can drill down into the data of each specific logical channel in the RF Cell menu. This allows
you to identify potential noise issues on specific frequencies.

▪ Duty Cycle per logical channel: You can access uplink and downlink Duty Cycle
(channel utilization) per Logical Channel.
o Uplink duty cycle reflects the aggregated reception time of physically-valid
LoRaWAN frames over the logical channel. This stat can be correlated with the
average uplink packet loss rate to establish a relation between the target
packet error rate for a given network deployment (considering the gateway
macro diversity) and the maximum tolerable uplink channel occupancy rate. If
radio congestion is identified, it can be mitigated by network densification.
o Downlink duty cycle reflects the aggregated transmission time of downlink
LoRaWAN frames over the logical channel, using RX1 transmission slot. In
countries where transmission duty cycle is limited by the local regulation, it is
mandatory to keep this metric below the maximum allowed duty cycle (set in
RF Region configuration). Even if TX duty cycle is not constrained by the local
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 34
regulation, it is recommended to keep the average Tx duty cycle, aggregated
over all the downlink channels, below 10% to avoid excessive packet loss with
half-duplex gateways.
Note: downlink duty cycle for RX2 transmission slot is displayed separately in
the “RX2” tab.

Duty cycle statistics displayed by Network Manager with either daily or hourly
aggregation. For each aggregation period, the statistics can be displayed for 7 or 15
days. Note that hourly duty cycles are aggregated over full hours, not over sliding
3600s windows.
The maximum uplink/downlink hourly duty cycles are recorded and displayed by
Network Manager, allowing the Network Partner to keep the historical maximum
values beyond the 15-days timeline display limit.
Note that it is possible to reset the statistics by clicking Reset Statistics. This action resets only
the min/max values; the chart data remains stored.

▪ Spreading Factor distribution per logical channel: For a given logical channel, you can
also access the uplink/downlink spreading factor distribution of the various
LoRaWAN™ packets. The distribution can be aggregated over the last 10 minutes or
over the last day. The following picture shows a sensor transmitting only at SF10
throughout the previous day.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 35
▪ RSSI and SNR per logical channel: You can display 2 types of charts:
o Received Signal Strength (RSSI):
o Signal to Noise Ratio (SNR)
For more information about the definition of RSSI and SNR statistics, please refer to
Section 9 More About LoRaWAN™ Radio Statistics.
These 2 charts are available over the last 10 minutes or over the last day.

▪ Downlink delivery status: This tab illustrates the split of downlink transmission status
between those successfully transmitted by the Base Station and those where
transmission failed. For failed transmissions, Network Manager provides a distribution
of the different failure causes (aggregated over the last 7 or 15 days).

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 36
Failure causes are categorized as follows:
o Ax: Transmission slot busy.
o Bx: Downlink frame received too late by the LRR.
o Cx: LRC selects another transmission slot.
o Dx: Duty Cycle or gateway constraint.
o Ex: Transmission timeout on LRR (relevant for class C only).
▪ Beacon delivery status: This section reports the beacon transmission status on the
Base Station, it is only relevant if Beacon transmission is activated on the LRR. For more
information on how to activate Beacon transmissions, please refer to Section 6.6.1
Settings.
o Beacon transmissions requested by LRC: number of beacon transmission
requested by the LRC since LRR startup.
o Beacon frames sent towards RF interface: number of beacon frames
successfully sent by the Base Station since LRR startup. The beacon
transmission success rate represents the number of successful transmissions
over the number of transmissions requested by the LRC.
o Last beacon delivery cause: success or failure.
o Last beacon delivery failed cause: reason of the last failure.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 37
▪ Other RF cell indicators:
The RF interface provides some indicators about the downlink/uplink frames and the RF
modem status. Those statistics are cumulated since the start of the recording period which is
displayed at the bottom of the page (see figure below). The user can click “Reset statistics” to
initialize all these statistics and start recording from the current time.

The indicators available are the following:

▪ Downlink:
o Number of frames sent towards the RF interface (downlink applicative payload,
MAC commands, ACKs…etc.): total number of downlink frames sent to the RF
radio board.
o Number of frames waiting for a transmission slot.
o Number of times the modem was busy when a frame was sent: indicates the
number of downlink frames not sent by the radio board due to radio
congestion (modem being already busy transmitting another downlink frame
at the same time). NOTE: the Base Station transmit only one downlink frame at
a time.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 38
o Number of frames which missed the RX1 slot and were postponed to the RX2
receive slot: indicates the number of frames postponed by the LRR from RX1 to
RX2 slot due to backhaul latency. If the ratio of downlink frames postponed by
the LRR to RX2 exceeds 40%, it is recommended to increase the MAC RX1 Delay
setting in the RF Region associated with this Base Station to compensate the
high backhaul latency.
o Number of frames received too late and discarded: If the ratio of discarded
frames (due to late reception) to the total number of downlink frames is higher
than 5%, it is recommended to check the backhaul latency (see WAN statistics
in the following section) and potentially adapt the MAC RX1 Delay setting in
the RF Region associated with tis Base Station to compensate the high backhaul
latency.

▪ RF cell modem (LoRa radio board):

o Number of successful initializations of modem.
o Number of modems with failed initialization.
o Number of modem configuration failures.
o Number of times the link with the modem was lost.

▪ Uplink:
o Number of frames received from the RF interface.
o Number of frames received with a CRC error: physical CRC error means that the
frame is not a valid LoRa frame; so, it may be used as an indication of the radio
pollution perceived by the gateway from other technologies.
o Number of frames received with a wrong length.

6.5 Base Station WAN Backhaul Information

This panel provides the Network Manager user with statistics related to the backhaul between
the Base Station and the ThingPark core network (also known as the LRC cluster), for the
different backhaul interfaces configured in this Base Station. The LRR-LRC interface uses IEC-
104 protocol at the application layer.

6.5.1 Backhaul statistics between LRR and LRC-cluster

The WAN backhaul information presents the traffic indicators between an LRR and the 2 LRCs
forming the LRC-cluster for that LRR. This is displayed in the following screen:
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 39
The information available is as follows:
▪ Last successful uplink/downlink packet to/from the LRC.
▪ Average latency round trip measured at the application layer (IEC-104) between LRR
and LRC, measured over the last LRR reporting period (5 minutes by default).

▪ Deviation of the latency round trip (showing the standard deviation of the round-trip
time between the LRR and LRC), measured over the last LRR reporting period (5
minutes by default).

▪ Max. latency round trip and its timestamp measured at the application layer (IEC-104)
between LRR and LRC.

▪ Number of IEC link disconnections, indicating the number of times the LRR-LRC link
was broken (e.g. due to loss of network connectivity, timeout…) since the recording
time of the current statistics.
Note that the all the statistics presented above are generated for a time period specified by
the “Recorded since:” information.
Note that the user can reset the statistics to restart the recording from the current time.

The following picture shows hourly totals for the number of packets transmitted over backhaul
WAN links over the last 7 days.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 40
Each tab presents WAN backhaul data exchanged with the LRC. Use the LRC tabs to switch
between one LRC and the other.
Note that the traffic volume indicated by these statistics reflects the overall applicative traffic
exchanged between the LRR and the LRC over IEC-104 interface, including LoRaWAN frames,
periodic LRR reports, LRR-LRC signaling and downlink transmission status reports.

6.5.2 Per-interface backhaul statistics

Depending on the Base Station backhaul interfaces that are available on the LRR, the WAN
interface section will present data rate information for available interfaces.
Note that eth0 refers to ethernet interface, whereas ppp0 refers to the cellular (3G/4G)
interface.

6.5.2.1 Recorded statistics

The following screen shows the traffic bit rate indicators for an LRR using ethernet backhaul.
In the example shown below, the statistics are recorded since April 19 th, 2018. The user can
reset statistics to start recording new ones from the time he clicks “Reset statistics” button.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 41
Note that the IP Address can be an IPv4 protocol as shown in the preceding screen or an IPv6
protocol (for instance, *2001:0db8:85a3:0000:0000:8a2e:0370:7334*). Both IP addressing
protocols are supported by ThingPark Wireless in release 5.2.2.
Note that the Tx/Rx traffic refers to the network traffic at IP layer.
Note that the latency measurements reported for each interface represent the network
latency (not the applicative latency).

6.5.2.2 Tx/Rx bitrate

The following section presents the bit rate history over the selected backhaul interface:

Note that all the graphs can be exported in several formats by clicking

6.5.2.3 Latency Round-trip

The following graph provides information about the applicative round-trip time measured
between the LRR and the LRC. It is possible to retrieve these measurements at daily or hourly
levels, up to the last 15 days.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 42
6.5.3 IEC uplink Queue
The statistics provided by the following graph show the evolution of the number of uplink
frames (both average and maximum volume) queued by the LRR during temporary LRR-LRC
backhaul disconnection. Both hourly and daily aggregations are available, up to the last 15
days.

Note that uplink frames buffered/queued by the LRR during temporary backhaul
disconnection are flagged “LATE” when they are reported to the Application Server or
ThingPark back-office applications (TWA).

6.5.4 Other WAN indicators

“Number of packets dropped due to loss of all links to LRCs”: This indicator shows the number
of uplink frames dropped by the LRR during extended backhaul disconnection period with
both LRCs in the LRC-cluster. Although the uplink frames are queued by the LRR when they
cannot be sent to LRC (when backhaul link is broken), they might eventually be dropped by
the LRR when the LRR queue becomes full.

6.6 Administering Base Station

The Administration section is visible only if you have the correct rights to access it. These rights
are given to you by your operator by delegating the Base Station administration to the
Network Partner.
allows you to refresh indicators after having performed administrative actions on the Base
Station.

Under Non-Disclosure Agreement

6.6.1 Settings

6.6.1.1 Advanced Settings

The flags available in this section allow you to switch ON/OFF the parameters given on the
screenshot below by ticking the box.

▪ Activate RX2 optimization: this algorithm allows the LRC Network Server to optimize
the choice between RX1 & RX2 slots used by end-devices to receive downlink frames.
This optimization is based on a combination of several criteria:
o RF link budget: to favor the RX slot having the higher transmission power (in
case of difference) for end-devices located in difficult radio conditions
o Downlink capacity: for devices located in fair/good/excellent radio conditions,
favor the RX slot having the highest data rate to optimize downlink
capacity/airtime.
o Maximum allowed MAC payload size: force the use of RX2 slot if the required
applicative downlink payload size can only be sent over RX2 slot but not RX1
slot.
For more details about the RX2 Optimization algorithm, please refer to [5].
▪ Support for IEEE 802.15.4: technical standard defining Low-Rate Wireless Personal
Area Networks, specific to old Watteco devices. Please contact Actility Support team
before ticking this checkbox.
▪ Activate Class B: Tick this flag if you want the Base Station to support Class B devices
by sending downlink pingslots. To support Class B in the current release, the Base
Station must be equipped with a GPS receiver.
▪ Activate Beacon transmission: If this flag is ticked, the Base Station shall contribute to
the beacon transmission. The beacon transmission periodicity is determined by the
LRC based on the RF Region configuration of the beacon randomization parameter. To
support beacon transmission in the current release, the Base Station must be equipped
with a GPS receiver.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 44
6.6.1.2 Automatic Upgrade of the LRR Software
When this option is activated, the Base Station will be automatically upgraded according to
the ThingPark upgrade policy available for this base station model. This does not imply that
manual upgrades cannot be performed. For manual upgrades, please refer to the following
section.

6.6.2 Maintenance

6.6.2.1 Upgrade LRR software

You can perform a manual LRR software upgrade as shown in the following capture.

The command instructs the Base Station to download and install a new LRR software (using
the FTP protocol). If the command is successful, the LRR process may be automatically
restarted or rebooted. The execution of the command may take several minutes. The Base
Station will be unavailable during this time.
When the user clicks “Upgrade”, the following window appears; it allows setting the target
LRR software version among a drop-down list of available versions.

Note: Starting release 5.2.2, only the LRR software versions compatible with the Base Station’s
current firmware/HAL/FPGA versions is proposed in the drop-down list.

Under Non-Disclosure Agreement

The command either stops the RF Cell uplink/downlink communications (Stop) or only stops
the downlink communications (Downlink stop). When the RF cell is completely stopped, the
Base Station becomes invisible to all LoRaWAN end-devices.
When the RF Cell is Started, the radio interface is up and running; whereas when the RF Cell
is Stopped, the radio interface is unavailable.

6.6.2.3 Reboot Base Station

The command launches a full operating system reboot. The execution of the command may
take several minutes. The Base Station will be unavailable during this time.
The “Base Station uptime” indicates the date/time of the last system reboot action.

6.6.2.4 Restart LRR Process

This command launches a restart of the LRR process only without full system reboot. This
command also reloads the configuration of the radio subsystem and the configuration of the
WAN backhaul interfaces.
The “LRR process uptime” indicates the date/time of the last LRR process restart action.

Under Non-Disclosure Agreement

6.6.3.1 Update RF Region (RDTP-3365)

To ease the definition of the RF channel plan and the optimization of the main ThingPark radio
parameters, ThingPark Wireless supports the RF Region concept:
Indeed, to fully leverage the ThingPark macro diversity gain and efficiently support device
mobility while minimizing the amount of downlink MAC commands, most optimization
parameters should be tuned over a wide geographical area rather than at base station level.
Several RF Regions can be defined in the network, each RF Region typically covering a
continuous geographical area and applies to Base Stations having a common RF channel plan
(e.g. same 8 or 16 channels).
Each Base Station (LRR) is associated with a given RF Region. All Base Stations sharing the same
RF Region shall have the same set of configuration parameters (channel plan, maximum Tx
Power, ADR parameters…etc.).
Actility recommends avoiding as much as possible overlapping between distinct RF Regions,
as well as setting the boundaries of each RF Region in a way that minimizes the border effect.
In Network Manager application, the Network Partner can associate each Base Station with
an RF Region from the Administration panel.

The drop-down list of RF Regions represents the list of RF Regions authorized by the Operator,
either based on Actility’s RF Region catalog or based on a manual Operator-personalized RF

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 47
Region catalog. Additionally, if the Operator has created custom RF Regions in the Operator
Manager, they will be visible in the drop-down list.
For more information about the RF Region concept, please refer to [5].
For more information about the management of RF Region catalog, please refer to [6].

6.6.3.2 Update Location and Altitude

The command allows the user to manually update the location and altitude configuration on
the Base Station.

“Current location status” indicates the location mode used by the Base Station: GPS (position
is automatically reported by the LRR) or Administrative (position set manually). To configure
the location mode, click “Update"; the following window will appear:

▪ When Base Station location mode is set to “GPS”, the absolute altitude (that is to say,
the altitude above sea level) is automatically reported by the LRR. Only the height
above ground level (in meters) can be configured by the Network Partner.
▪ When Base Station location mode is set to “Administrative”, the Network Partner can
determine the location directly on the map, by clicking on the required position then
the marker will be moved to this new position. Additionally, both the absolute altitude
(that is to say, the altitude above sea level) and the height above ground level can be
configured by the Network Partner.
Please don’t forget to click “Update” at the top right of the window to save your changes, or
press cancel to revert to previous configuration.
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 48
6.6.3.3 Update Antenna Gain and Cable Loss

The command updates the gain and cable loss for each antenna on the Base Station. A dialog
window will be opened to configure the gain and cable loss as shown by the following
screenshot:

Note: it is essential to set the correct values for the antenna gain and cable loss, otherwise
the downlink transmission power used by the LRR will be wrongly set. The LRR derives the
conducted TX power from the maximum allowed radiated power (also known as Effective
Isotropic Radiated Power – EIRP) configured in the RF Region associated with the Base Station
as per the following formula: Conducted Tx Power = EIRP – Antenna Gain + Cable Loss.

6.6.3.4 Update Fine-timestamp Decryption Keys

The command updates the fine-timestamp decryption keys for all FPGA boards on the Base
Station. A dialog window will be opened to configure the gain and cable loss for all antennas.

6.6.4 Advanced Maintenance

To enable Network Partners to perform troubleshooting tasks on the Base Stations, Network
Manager application supports a remote access functionality to the Base Station.
Click “Open reverse SSH” to launch the remote access to the Base Station (if the status is
already closed). In case the Base Station connection to the LRC-cluster is broken, it is still

Under Non-Disclosure Agreement

6.6.4.1 Remote Access via Reverse SSH

This command opens a reverse SSH session with the Base Station. This may be used for
advanced maintenance and troubleshooting operations. Once the session is open, you may
launch the embedded SSH terminal (see button below) or you may connect the ThingPark
Support server by using the default support account provided by your operator.
To reverse the SSH session:
1. Click Open reverse SSH button.
2. The port value is preconfigured in Network Manager window (but you may choose a
different port of it is also open).

3. Click Open to confirm opening the reverse SSH.

4. Once the reverse SSH session is opened, open the SSH terminal by clicking SSH terminal
as displayed in the following screen.

5. Click Yes to confirm opening the SSH terminal.

Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 50
Once signed into the reverse SSH session, the dashboard proposes a menu for the LRR
Base Station remote supervision, as described in the following section.

LRR Base Station Remote Monitoring Tasks:

This section presents the scope of functionalities available to the Network Partner when they
remotely access the Base Station, once an SSH session gets opened according to the previous
instructions.
The local Base Station GUI console is also known as SUPLOG.
Note that the Tab key on the keyboard allows you to reach the Exit, Back and Ok buttons in
the Reverse SSH session. To move to next screen, press F12 on your keyboard.
The LRR Base Station remote monitoring tasks and action menu is displayed in the following
capture.

▪ Logs:
o Allows the user to visualize log files for the current + historical logs of the last
7 days. To scroll up/down, please use the up/down keys on your keyboard.
o It also allows searching in logfiles (grep functionality) watching activity via tail
functionality.
o The user can also export the Base Station configuration and log files via
FTP/SFTP, by setting the server details, username / password…etc.
▪ LRR configuration:
o Get the current radio configuration: number of antennas, ISM band, LBT
configuration, TX Power look-up tables (LUT), physical channel
configuration…etc.
o Get LRR-UID: useful to provision LRR-UID of the Base Station in Network
Manager in case the information is not available on the Base Station sticker.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 51
o Dump Base Station configuration.
o Set Transmit Power: to set the Base Station radiated power (EIRP) used for
downlink transmission. Note: It is recommended to set the Tx EIRP directly on
RF Region rather than locally from the Base Station console: The EIRP set on
the Base Station console will be lost when a new RF Region having a different
EIRP value is associated with the Base Station.
o Set Power Transmission adjustment: to directly set the antenna gain and cable
loss for each antenna, directly from the Base Station console.
▪ Network:
o View ethernet or cellular networks.
o View the DNS (Domain Name Server) address.
▪ Troubleshooting:
o Ping a configurable IP address to check internet connectivity.
o Ping LRCs to test backhaul connectivity to ThingPark’s core network.
o View Disk usage statistics.
o View system statistics in real-time: CPU, RAM, processes.
o Netstat.
o Show iptables.
o Show versions (LRR, firmware…etc.).
o Uptime: timestamp of last LRR process restart (or system reboot).
o Status of each configured network interface: ethernet, cellular, WiFi,
satellite…etc.
o Network routes.
o Last LRR restart & Base Station reboot causes.

Close Reverse SSH Session:

To close the reverse SSH session, click “Close reverse SSH” button as per the following capture,
then click YES to confirm.
Note that an inactive SSH session is automatically closed after a timeout of 60 minutes.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 52
Rescue SSH Terminal:
If the Open/Close reverse SSH is not working, you still can troubleshoot the faulty Base Station
using the Rescue SSH Terminal Window.
This functionality is always enabled, even if a command is running.
When the Base Station cannot reach ThingPark LRC, it automatically opens a reverse SSH
session. Use the embedded rescue SSH terminal to attempt to access this session.
Clicking the Rescue SSH terminal window opens an SHH Session window.

Analyze the LRR configuration, then exit the SSH session.

6.6.4.2 Spectrum Analysis

RF Spectrum Analysis is used to display noise-scan results generated by the Base Station, and
to determine the noise level seen on each frequency within the defined spectrum.
Noise-Scan statistics are used to derive the average interference level (that is the rise above
thermal noise floor) to be used for the link budget analysis. It is also mandatory for the
appropriate selection of physical frequencies related to LoRaWAN™ logical channels.
To launch a new scan campaign, click “Scan the radio” then “Yes” to confirm.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 53
This command launches a spectrum analysis of the radio. The analysis may take several
minutes.
Note that the result of the RF spectrum scan is directly available in ThingPark Spectrum
Analysis tool. For more information, please refer to [7].
Note that, for old Base Station design (Semtech’s v1.0 reference design), launching the
spectrum scan cannot be done in parallel to normal LoRa transmission/reception (the radio
TX/RX is blocked during scan period). This limitation is lifted for all the Base Station designs
starting v1.5.

6.6.4.3 Update Trace Level

This command updates a trace level of a Base Station. A dialog window will be opened to
configure the trace level.

The following trace levels are supported by the LRR software:

▪ 0 => for error level.
▪ From levels 1…9, the log activity is gradually increased. Warnings are mostly in level 1,
but there is also some INFO in level 1.
Base Station startup logs are always activated, regardless of the trace level.
Note that, in the Network Manager GUI, it is currently only possible to set trace level from 0
to 3. Trace levels > 3 cannot be directly configured from Network Manager in the current
release, this restriction shall be lifted in future ThingPark Wireless releases.
“Current trace level” indicates the current configuration and whether the RAM-disk option is
activated on the Base Station. RAM-disk usage is strongly recommended when the trace level
is > 0 to preserve the flash storage on the Base Station by avoiding frequent write actions on
the flash.

Under Non-Disclosure Agreement

▪ Backup – The command launches a backup of the current configuration. The LRR
software, LRR configuration, RF configuration, WAN backhaul configuration and Base
Station login/password will be saved. This command must be used CAREFULLY: the
backup configuration will be erased and replaced by the current configuration.

▪ Restore – The command launches a restore process of the backup configuration. The
backup LRR software, LRR configuration, RF Cell configuration, WAN backhaul
configuration and Base Station login/password will be restored. The execution of the
command might take several minutes. The Base Station will be rebooted and
unavailable during this time. This command must be used CAREFULLY: the current
configuration will be erased and replaced by the backup configuration.

6.7 Base Stations Tagging

The tagging functionality allows to group Base Stations for Multicast and Managed Customer
Network usage.
A Managed Customer Network is a set of Base Stations deployed by an operator on the
customer premises for its own usage. A billing policy is applied by the Operator to the
LoRaWAN™ traffic routed through the Managed Customer Network. The discrimination is
performed according to the best Base Station for uplink frames and according to the selected
Base Station for downlink frames.
Several sets of Base Stations can be associated within a group and then be tagged. The tag can
be used to localize the Base Station or for other classification.
You can create class B or C Multicast Groups to send simultaneously a same downlink payload
to many target multicast devices in your LoRaWAN™ network. The class of the Multicast Group
must be the same as the class of the target multicast devices working with it.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 55
For instance, to create a Multicast Group for which the devices are in Paris, you need to
associate the Multicast Group to the tag “Paris” for all the Base Stations to transmit their
Multicast downlinks to the device.
You can display on a map or a satellite view all the Base Stations associated with a Multicast
Group that have a known location.
For further information on Multicast, please refer to [5].

6.7.1 Prerequisites
Ensure that the delegation for BS tagging is activated for your Network Partner. Otherwise,
the BS tagging stays in read-only mode. To do this, go to the Operator Manager > Network
partners and activate the Delegate BS Tagging of your supplier. For more information, please
refer to [6].

6.7.2 Tagging a Base Station

Use this procedure if you want to tag a single Base Station. Two different approaches are
possible to create one or several tags:
Approach #1:
1. Go to the Base Stations List Tab.
2. Select a Base Station in the list and click Edit at the end of the line.
 The Base Station panel opens.
3. Below the Administrative information rectangle, click Tags Management.
 The Base Station Tag Manager opens.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 56
4. Click New tag.
a) Check the “I want this tag to be visible for multicast” box, if you want to use the
tag for a specific multicast group.
b) Check the “I want this tag to be visible for managed customer” box, if you want to
use this tag for the Network partners that are included the multicast group.
5. Click Validate.
 The new tag “paris” is displayed in the tags’ list.
 Add new tag, if need be.
6. In the Base Station list, click the tag icon to check that the tag has been added.

Approach #2:

1. Go back to the Base Stations List Tab.

2. Select a Base Station in the list and click the tag icon ( ) at the end of the line.
 The Base Station Tag Manager opens as displayed in the first way.
3. Proceed as described in the first way.

6.7.3 Tagging Multiple Base Stations

Use this procedure if you want to tag a group of Base Stations belonging to one or different
Network Partners.
1. Go back to the Base Stations List Tab.
2. Select a Base Station in the list and click the Multiple Base Station Tagging Manager on
the right side of the list ( ) at the end of the line.
 The Multiple Base Station Tagging Manager opens.

3. Follow the steps indicated on your screen.

4. Select an existing tag, for instance “paris”.
5. Click Add tag.
 A message in the left corner of your screen indicates that all Base Stations have
been tagged “paris”.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 57
6.7.4 Searching for Base Stations with a Tag
After you have tagged all your Base Stations, you can search those in which you are interested
in.
1. Go to the Base Stations panel.
2. In the Search area in the Base Station frame, write “Paris” in the Tag rectangle.
3. Click Search.
 The list of Base Stations that are tagged “paris” is displayed in the table list.
Note that leaving the Search empty results in a complete list of tagged Base Stations.

6.7.5 Deleting Tags from Base Stations

1. Proceed as described in 6.7.2 Tagging a Base Station.
2. In the Base Station Tag Manager that opens, select the tag that you want to remove.
3. Click Delete.
The tag is removed from the list.

6.8 Modifying a Base Station

Modifying a Base Station allows you to update Base Station-related data such as the name,
the address, the manually entered location or the administrative info.
Start by opening a Base Station in Edit view:
a) Select the Base Station to edit in the list.
b) Click Edit to enter in the Edit view.
Finally, to confirm the changes, go back to the Device details by selecting the Device in the
column in the left sidebar, then click Save in the top-right corner of the screen.

6.9 Deleting Base Station

Deleting a Base Station is an action that cannot be undone and should be handled with care.
All Base Station details and status information will be lost.
The steps to delete a Base Station are as follows:
a) Select the Base Station to delete in the list.
b) Click Edit to enter in Edit view.
c) Click Delete and confirm in the pop-up to delete the Base Station.

Tips: All actions Save or Delete displays the result in the status bar at the bottom of the screen.

Under Non-Disclosure Agreement

Use this information if you want to know more about the Base Station alarms that are
displayed by the Network Manager. You can access the Base Station alarms by clicking the
Alarms section in the left menu.

The Alarms panels display all alarms generated for the Base Station and lets you monitor them.
Network Manager application supports two panels to manage BS alarms:
▪ “Alarms” panel shows the active alarms associated with the Base Station. Active alarms
are those currently raised by the system (not yet cleared) regardless of their
acknowledgment status.
▪ “History” sub-panel (located under “Alarms” panel): show historical alarms associated
with this Base Station, historical alarms are those already cleared by the system (i.e.
not active anymore) in the past 15 days.

Notes:
▪ Historical alarms represent the latest known status about the alarm before it was
cleared. In other words, when an alarm is cleared, the alarm before clearance is cloned
in the history.
▪ When an alarm is cleared, it is still displayed in “Alarms” panel under the state
“Cleared” to inform the BS administrator about the last issue. This implementation
allows the user to quickly monitor the latest state of their BS without switching
between active and historical alarms. If the user does not want to see cleared alarms
in active alarm list, they can use the filter State = “not cleared” (see below the
search/filter options).
▪ By default, an alarm in the history expires 15 days after clearance.

▪ Historical alarms are only available starting the upgrade of ThingPark Wireless
platform to release 5.2.2-3.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 59
The Network Manager triggers alarms about a Base Station when:
▪ A Base Station does not work properly: These alarms are triggered automatically and
are defined as follows:
o Beacon transmission failure
o Abnormal log activation
o Base Station connection status
o Downlink frame rate exceeds the RF cell capacity
o Etc.
▪ You have configured an alarm based on an inactivity threshold of the Device. For more
information about the settings related to this alarm, please refer to Section 7.4.1
Configuring an Inactivity Alarm.

▪ The Base Station is exposed to a replay attack threat.

7.1 Searching Alarms

Network Manager application supports several search filters allows you to search alarms using
one of the following criteria:

The same search options are available in “Alarms” panel and “History” sub-panel.

▪ From: only return alarms created after the specified date/time.

▪ To: only return alarms cleared after the specified date/time.

▪ Alarm: search for a specific Base Station alarm by its name.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 60
▪ State: the user can search for active alarms (not cleared) or cleared alarms. For
active/not-cleared alarms, the user can search by the alarm severity: Critical, Major,
Minor or Warning. Note that each state has a specific color as depicted by the following
figure.

▪ Acked: the user may search for alarms by their acknowledgment status. For more
information, please refer to Section 7.3 Acknowledging Alarms.
The search result shows the list of Base Station alarms matching the filtering criteria. Each
alarm is associated with a state to define its severity and activity status as well as a color code.
The following screenshot refers to active alarm list:

To acknowledge an alarm, click the desired alarm and click Ack.

To acknowledge all alarms, click Ack all as shown in the preceding picture.
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 61
Note about occurrence management of Event-Driven versus State-Driven alarms:
Event-driven and state-driven alarms manage and display occurrences in a different way:

▪ Event-driven alarms
Each time the event associated with the alarm is detected, the alarm occurrence is
incremented by one.
Example: If a Join Request has been rejected ten times due to repeated DevNonce, the
Alarm 113 - Join request replay detected (DevNonce replay)- displays ten occurrences.
Note: For an event-driven alarm, no email notification is sent for any new occurrence
if the alarm state, related to a severity level of the alarm, stays the same. For more
information, see Section 8.2.2 Error! Reference source not found..
Event-driven Base Station alarms include the replay attack alarms (alarm ID 113…120)
in addition to alarm 101 “LRR software restarted by watchdog”.

▪ State-driven alarms
A state is a stable event that cannot repeat unless stopped. Each time the state
associated with the alarm is detected, the alarm occurrence does not increase and
always displays one. This type is valid for all Base Station alarms except replay attacks
and alarm 101.
Example: If a power failure of the Base Station has been detected with the same alarm
reported ten consecutive times (on ten LRR consecutive LRR reports), the Alarm 110 -
Power failure detected - displays only one occurrence.

7.2 Troubleshooting Base Stations

7.2.1 System Alarms

Alarm Alarm Explanation Possible Root Causes Guidelines
ID name
101 LRR software Base Station The alarm gets triggered once See the sub-chapter Error!
restarted by software gets the watchdog process stops Reference source not found. Error!
watchdog rebooted by the receiving reporting signals Reference source not found. to
system protection from LRR on its working state collect logs, and contact your
algorithm via within a set period of time. support.
execution of the
proper keystrokes

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 62
Alarm Alarm Explanation Possible Root Causes Guidelines
ID name
102 Base Station Informs on Base Six diverse alarm states occur Check the Base Station power for
connection Station’s accordingly to Base Station’s potential power failure.
status connection status administrative state (active,
to ThingPark LRC- validating, suspended) along
Check the Ethernet/Cellular
cluster with Base Station’s
connection state (never connection for potential network
connected, disconnected). failure.
▪ The BS is not yet
validated by the Check if the lrr.x process is running,
administrator (minor restart it if needed.
alarm by default)
▪ The BS has been
Check if LRC-cluster has restarted,
suspended by the
administrator (major causing disconnection of the LRR-
alarm by default) LRC link.
▪ The BS is administratively
active but has never See the sub-chapter Error!
connected to the core Reference source not found. Error!
network (warning alarm Reference source not found. to
by default)
collect logs, and contact your
▪ The BS is administratively
active but is disconnected support.
from the core network
(critical alarm by default)

106 Unusually high CPU usage The alarm gets triggered once See the sub-chapter Error!
CPU usage level reaches an the CPU’s average and Reference source not found. Error!
abnormal level standard deviation cumulated Reference source not found. to
load exceeds 85%: collect logs, and contact your
▪ Warning alarm if average support.
+ standard deviation of
the CPU load > 85%
▪ Major alarm if average +
standard deviation of the
CPU load > 95%

Under Non-Disclosure Agreement

108 Unusually high File-system usage The alarm gets triggered once See the sub-chapter Error!
file system reaches an the file-system average and Reference source not found. Error!
usage level abnormal level standard deviation cumulated Reference source not found. to
load exceeds 95%:
collect logs, and contact your
▪ Warning alarm if average
+ standard deviation of support.
the CPU load > 95%
▪ Major alarm if average +
standard deviation of the
CPU load > 99%

109 Time The Base Station ▪ NTP launched before Connect on the Base station and
synchronization uses the local getting an IP address. restart the NTP: settime restart.
lost time instead of ▪ The Base station
using the NTP restarted but the NTP See the sub-chapter Error!
time reference. was not launched Reference source not found. Error!
correctly Reference source not found. to
collect logs, and contact your
support.

110 Power failure Power supply ▪ Base station disconnected ▪ Check the connection of the
detected defect detected; from the grid Base station to the grid.
the Base Station is ▪ Power grid failure ▪ Check the power of the grid.
running on
battery.

Under Non-Disclosure Agreement

Note: In some cases when a Base

Station makes many insertions into
flash memory, it might damage the
normal usage and behavior of the
Base Station.
121 Backhaul At least one ▪ IP address issue, e.g. due ▪ Use manual IP address allocation
network backhaul link of to DHCP. in case of DHCP issue.
interface status this base station is ▪ For cellular interface: ▪ Check the interface
lost 3G/LTE network failure,
configuration in the LRR and
no SIM card, bad network
coverage. correct configuration issues if
▪ Bad configuration of the needed.
backhaul interface in the ▪ For alarms related to cellular
LRR backhaul: check cellular network
coverage, SIM card status and
subscription with cellular
operator

7.2.2 RF Cell Alarms

Under Non-Disclosure Agreement

If the alarm persists, contact your

Support.

104 Unusually high LoRa frames ▪ Number of packets ▪ If the uplink duty cycle of the
level of invalid received by the generated by devices in Base Station is high, switch off
uplink physical LRR (on the last the cell is too high (frame some Devices.
CRC hour) cannot be collisions). ▪ Check if an RF equipment has
demodulated ▪ Noise generated by been installed next to the Base
properly, or there another LoRa network's Station (causing potential
are many non- gateway nearby. interference).
LoRa frames ▪ Jammer/Non-LoRa ▪ Scan the radio on the Base
received by the equipment is interfering Station to check the noise level.
gateway with (most likely if ratio is very
physical high). If the alarm persists, contact your
preamble similar ▪ LRR RF chain defect. support.
to LoRa.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 66
Alarm Alarm Explanation Possible Root Causes Guidelines
ID name
105 Downlink frame This alarm is Too many LoRaWAN™ ▪ Reduce the acknowledgements
rate exceeds the raised when acknowledgments or requested by your Devices.
RF cell capacity downlink packets reconfigurations attempts ▪ Reduce the downlinks sent by
are dropped by your applications.
the Base Station ▪ Have a better repartition of the
(received by the downlink MAC reconfiguration
LRR but not sent messages (e.g. RF Region
over-the-air) updates) over time to prevent
because the RF temporary saturation of
cell modem was downlink capacity.
busy. Therefore, ▪ Add a new Base Station to your
the LRR was not network.
able to send
these downlink If the alarm persists, contact your
packets (e.g. a support.
downlink packet
of a class 'A'
device for which
the transmission
window is
outdated).
111 Beacon A failure linked to ▪ Radio is stopped. ▪ Check the radio status of the
transmission the transmission ▪ Listen Before Talk (LBT) Base Station.
failure of the last time- procedure did not allow ▪ Check the GPS status of the Base
synchronized the transmission. Station.
beacon from the ▪ GPS synchronization is ▪ Check the duty cycle on Beacon
Base Station to lost. RF sub-band.
the Class B ▪ Beacon is received too ▪ Check if the latency between
Device. late for beacon slot. the Base Station and the
▪ Duty cycle constraint is network server is reasonable.
reached.
If the alarm persists, contact your
support.

Under Non-Disclosure Agreement

114 Wrong MIC A wrong MIC has ▪ The LRR is the target of a If the number of the alarm
detected in Join been detected in join request replay attack. occurrences is high:
request a Join request, ▪ A Device sent a join 1. Check the Device's information
failing to request containing a
and behavior and fix issues.
authenticate the wrong MIC possibly due to
activation wrong Device provisioning 2. The Base Station may be the
request for the (that is, bad Appkey). victim of a join request replay
device in attack. Stop the radio and try to
question. identify the attacker.
If the alarm persists, contact your
support.

115 Join request A wrong MIC If the number of the alarm Stop the radio and try to identify the
replay detected correlation has occurrences is high, the attacker.
(wrong MIC been detected
Base Station may be the
correlation) between a Join
request and the victim of a join request If the alarm persists, contact your
following Uplink replay attack. support.
frame,
invalidating the
last join request
received from
this device.

Under Non-Disclosure Agreement

117 Wrong MIC A wrong MIC has ▪ The LRR is the target of an If the number of the alarm
detected in been detected in uplink frame replay occurrences is high:
Uplink frame an Uplink frame, attack. 1. If the Device has sent an uplink
failing to ▪ A Device sent an uplink
packet containing a wrong MIC,
authenticate the frame containing a wrong
frame. MIC (for instance, bad fix it (check NwkSKey).
NwkSKey provisioned for 2. The Base Station may be the
ABP device). victim of a join request replay
attack. Stop the radio and try to
identify the attacker.
If the alarm persists, contact your
support.

118 Uplink frame A repeated FCnt ▪ The LRR is the target of an If the number of the alarm
replay detected has been uplink frame replay attack occurrences is high:
(repeated FCnt) detected in an 1. Stop the radio and try to identify
Uplink frame. ▪ A Device exceeds its
configured number of the attacker.
transmissions 2. Check the behavior of the device
and fix it if needed.
3. If the replay attack risk is highly
persistent, it is recommended to
reduce the maximum number of
transmissions to 1 in the
Connectivity Plan.

If the alarms persist, contact your

support.

Under Non-Disclosure Agreement

120 Join request A DevNonce If the number of the alarm If a join request replay attack: stop
replay detected attack has been occurrences is high, the Base the radio and try to identify the
(invalid detected in a Join Station may be the victim of a attacker.
DevNonce) request when the join request replay attack.
If the alarms persists, contact your
device is
support.
supposed to use
counter-based
DenNonce.

7.3 Acknowledging Alarms

When you have dealt with an alarm, you can acknowledge it. It will appear as checked in the
alarm list if the search filter is set to “No filter” or “Acked”. It should look like this.

You can acknowledge an alarm, a set of alarms or all alarms.

▪ To acknowledge one alarm, click the alarm you want to acknowledge, then click Ack.

▪ To acknowledge multiple alarms, use the Ctrl Key and click the alarms you want to
acknowledge.

▪ To acknowledge all alarms, click Ack all. If a message is displayed, click Yes to confirm.

Note: If the filter is set to “Acked”, only acknowledged Alarms marked by a green check mark
and corresponding metdata describing the Alarm are displayed. This is shown in the following
screen.

Under Non-Disclosure Agreement

7.4.1 Configuring an Inactivity Alarm

An inactivity alarm is defined by the no-uplink activity of the Base Station.
You can define only one inactivity alarm by Base Station, but you can define one or two
thresholds to trigger the alarm. For example, raising a warning alarm after two days of
inactivity, and raising a major alarm again after five days of inactivity.
You will configure the inactivity alarm in the Node Settings panel of the Base Station you want.
In the Navigation panel:
1) Click Base Stations to display the Base Stations panel.
2) Click the List or the Map tab.
3) Select a Base Station and click Edit.
In the Base Station that appears in the Navigation panel:
1) Click Settings to open the Node settings panel.

In the Alarm settings frame:

1) Select Active threshold1.

From the Trigger list:

1) Select the duration of inactivity (from 1 hour to 15 days) after which you want the
alarm to be triggered.
2) Set this duration per the usage of your Base Station.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 71
From the Action list:
1) Select a critical level you want to associate to the threshold1.
Each critical level corresponds to an alarm state and a color to display to help you
monitor the alarms in the Alarms frame.
Alarm State Definition
Critical The service is affected, and an immediate corrective action is required.

Major The service is partly affected, and an urgent action is required.

Optional: If you want to create another threshold for the alarm, select Active threshold2 and
repeat the sub-steps above.
2) Click Save.
The alarm will be displayed in the Alarms panel of the Base Station when the conditions are
met.

7.4.2 Receiving Alarm Notification Email

If you want to receive a notification email when an alarm is triggered on any Base Station, see
8.2 Setting Alarm notification e-mails.

Under Non-Disclosure Agreement

The Settings panel displays information about the Network partner account and lets you
configure alarm email notifications.

8.1 Accessing the Settings panel and Viewing Account Details

To access the Settings panel:

1) Click Settings in the Navigation panel.

The Settings panel appears:

▪ The Network partner frame gives the activation date and status of the subscription.

▪ The Delegations frame confirms or denies Network partner’s administration and Base
Station validation along with tagging rights.

▪ The Alarm notifications frame lets you configure alarm notification emails and appears
by default with the basic mode.
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 73
▪ The Subscription information frame provides the following
o a roll-out list of available ISM bands per country, being “Undefined” by default;
o Base Station credit;
o used Base Station credit quantity;

▪ The Status frame indicates when the Settings section got updated and by whom.

8.2 Setting Alarm notification e-mails

In addition to the alarm notifications appearing in the Alarms panel of a Base Station (For more
information, see Section 7 Working with Base Station Alarms), you can set alarm notifications
by email to monitor all Base Stations of the account when necessary, and independently of
the Base Station the alarm belongs to.

▪ The basic mode lets you send notification emails whatever the alarm state to all
recipients.

▪ The advanced mode lets you send notification emails to the recipients per the alarm
state.
Important

▪ Click Save after you have finished your configuration in any mode.

▪ When shifting from the advanced mode to the basic mode and clicking Save, the
basic mode overwrites what you have set in the advanced mode.

▪ The Setting panel opens with the last saved configuration mode.

8.2.1 Setting Alarm Notifications Emails in Basic Mode

In basic mode, the recipient or recipients receive an email whenever an alarm is triggered,
whatever the alarm state (Critical, Major, Minor, Warning, Indeterminate, Cleared or Acked).
1. Click Settings in the Navigation panel to access the Settings panel.
2. In the Alarm Notifications frame set in the basic mode, click Add.

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 74
3. Click the line that appears, and in the Name box, enter the name of the recipient you want
to add.
4. In the Destination box, enter the recipient email address.
5. If you want to add more recipients, repeat from step 1.
6. Click Save.
 The recipients registered will receive an email whenever an alarm is
triggered on any device.

8.2.2 Setting Alarm Notifications Emails in Advanced Mode

In advanced mode, if an alarm state having a registered recipient is reached, an email for all
devices impacted is send:

▪ Whenever a new alarm is triggered with this alarm state.

▪ Whenever an existing alarm changes to this alarm state.

Note: For an event-driven alarm, no email is sent for any new occurrence if the alarm
state is the same.

▪ Whenever the alarm has been acknowledged and increases to this alarm state.
Note: When an acknowledged alarm increases its alarm state, the acknowledgement
is cancelled by the system.
Each alarm state corresponds to a severity level of the alarm, or a cleared or acknowledged
alarm:
Alarm State Definition
Critical The service is affected, and an immediate corrective action is required.

Major The service is partly affected, and an urgent action is required.

Minor A fault that does not affect the service should be corrected to prevent a
more serious problem.
Warning A potential or impending fault affecting the service should be diagnosed
and corrected if necessary.
Under Non-Disclosure Agreement
Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 75
Indeterminate The severity cannot be determined.

Cleared or The alarm has been cleared by the system or acknowledged by the user
Acknowledged and is kept in an history for one year.

1. Apply all steps described in Error! Reference source not found. Error! Reference source
not found. entering the email addresses of all the recipients you want to notify, whatever
the alarm state of the devices.
2. Click Switch to the advanced mode.
 All the recipients email addresses have been copied in all alarm state areas.
3. In the Alarm state area that you want, select the recipient you do not want to notify, and
click Delete. Repeat as necessary in any other alarm state area.
If necessary, you can add more recipients in the alarm state area you want.
4. Click Save.
 The recipients registered will receive an email when the corresponding
alarm state is reached for any device.
 Next time you open the Settings panel, the Alarm notifications frame will
appear with the advanced mode.

8.3 Setting ISM Bands

ThingPark Wireless supports a various range of ISM bands. When the Network administrator
sets one or several ISM bands in Network Manager, only Base Station Profiles compatible with
these selected ISM bands shall be proposed during Base Station creation.
1. In the Default ISM band table in the Subscription information frame, click Add.

2. Double-click Undefined line in the table.

3. In the combo box that scrolls down select the ISM band you are interested in.

Under Non-Disclosure Agreement

MORE ABOUT LORAWAN™ RADIO STATISTICS

This section provides information on the calculation of radio parameters. This includes

▪ Estimated Signal Power (ESP)

▪ Received Signal Strength Indicator (RSSI)
▪ Signal to Noise Ratio (SNR)

Radio Parameter Definition

Estimated Signal ▪ ESP is the received signal strength of the useful signal.
Power (ESP)
▪ It represents the "S" component in the SNR formula.

▪ Therefore, ESP can be computed as follows:

ESP = Tx EIRP – Path Loss + Rx antenna gain
ESP = RSSI – 10*LOG( 1 + 10(-SNR/10) )
Received Signal ▪ It represents the total received signal power within the
Strength Indicator channel bandwidth including the useful signal +
(RSSI) background noise + interference.

▪ Hence, RSSI represents the sum S + I + N.

Signal-to-Noise ▪ SNR= S/(I+N
Ratio (SNR)
▪ SNR determines the quality of the reception through the
ratio between the received signal strength of the useful
signal and the signal strength of the background noise and
interference.

Under Non-Disclosure Agreement

This section lists changes implemented in the previous versions of this document.
NFR 472 - Map service
4.2 Base Stations List 4.2
based on OSM
NFR 684 - TWA Redesign
Error! Reference source not found. Error! Reference
LRR ID Format, Length and 4.2
source not found.
Association
NFR 758 - Set LRR trace
level via the Network Error! Reference source not found. Error! Reference 4.2
Manager source not found.

NFR 730 - Join request Error! Reference source not found. Error! Reference 4.3
replay attack by LRC source not found.
NFR 731 - Device UL to
Application Server to Error! Reference source not found. Error! Reference 4.3
prevent replay attacks source not found.

4.1 Searching Base Stations

NFR 1036 - TWA multicast
5.0.1
groups 6.7 Base Stations Tagging

NFR 1043 - DevNonce as a Error! Reference source not found. Error! Reference 5.0.1
counter source not found.
RDTP-1086/NFR698
ThingPark Wireless LRR/No Error! Reference source not found. Error! Reference 5.0.1
Radio Packet Activity source not found.
(Watchdog) Completion

NFR 3365 - rfregion-catalog 6.6.3.1 Update RF Region 5.1

NFR 4030 – SSH

5.1
Connection to BS 0 Rescue SSH Terminal

NFR 2262 – New backhaul Error! Reference source not found. Error! Reference 5.1
link status alarm source not found.
NFR 3755 – Support
5.1
several ISM Bands 8.3 Setting ISM Bands

Under Non-Disclosure Agreement

Actility S.A. au capital de 1 122 916 € - 4 rue Ampère, 22300 Lannion, France
RCS St Brieuc 522 305 473, Siret 522 305 473 00012, TVA FR62522305473
TP_Wireless_5.2.2-rev2_Network_Manager_User_Guide.docx- 78
[ThingPark China] Add the
support of Baidu maps 5.1
4 Using the Graphical User Interface
(RDTP 2243)
RDTP-7582: Enhanced
Security Access to Key 5.2.2
5 Creating a New Base Station
Installer
RDTP-2208: TLS support on
5.2.2
Base Stations 5 Creating a New Base Station

RDTP-2343: IPv6 support Error! Reference source not found. Error! Reference 5.2.2
on Base Stations
source not found.
RDTP-7849: LRR upgrade
depending on 5.2.2
6.6.2.1 Upgrade LRR software
firmware/FPGA versions
An event-driven alarm 7.1 7.1Searching Alarms
increases its occurrence
number, a state-driven
alarm does not (RDTP-
9073) 5.2.2
7.3 Acknowledging Alarms
Clarification on
acknowledged alarms and 8.2.2 Setting Alarm Notifications Emails in Advanced
alarm notification emails. Mode

Under Non-Disclosure Agreement

Actility is an industry leader in LPWAN (Low Power Wide Area) large scale infrastructure with
ThingPark™, the new generation standard-based M2M communication platform. Actility’s
ThingPark Wireless™ network provides long-range coverage for low-power sensors used in
SmartCity, SmartBuilding and SmartFactory applications. Actility also provides the ThingPark
X which provides big data storage for sensor data and exposes sensor function through an
open API allowing developers to provide vertical applications on top of rolled out sensors. To
help vendors transform their sensors, Actility provides the ThingPark IoT platform which
include embedded software solutions and cloud solutions to help Devices connect to
innovative applications. Via the ThingPark Market, an online marketplace engine dedicated to
the IoT sensors, applications and network solutions, Actility enables the roll-out of new
innovative IoT services for sensor vendors and network solution vendors. Actility is a founding
member of the LoRa Alliance™: the largest, most powerful standards-based effort to enable
the Internet of Things (IoT). Visit https://www.actility.com/.

LoRaWAN™, the LoRa Alliance™, and LoRa Alliance Certified™ are trademarks of Semtech
Corporation, used with permission under a sublicense granted to the LoRa Alliance™ and its
members.

Under Non-Disclosure Agreement

Digital Modulations using Matlab
From Everand
Digital Modulations using Matlab
Mathuranathan Viswanathan
4/5 (6)
TP Wireless 6.1 Radio Parameters User Guide Rev2
No ratings yet
TP Wireless 6.1 Radio Parameters User Guide Rev2
121 pages
What Are Operational Support Systems
No ratings yet
What Are Operational Support Systems
15 pages
Indoor Radio Planning: A Practical Guide for 2G, 3G and 4G
From Everand
Indoor Radio Planning: A Practical Guide for 2G, 3G and 4G
Morten Tolstrup
5/5 (1)
TP-Wireless-5.2.2-Wireless Supplier User Guide
No ratings yet
TP-Wireless-5.2.2-Wireless Supplier User Guide
53 pages
TP-Wireless-5.2.2-LRC-OSS Interface Developer Guide (Cellular)
No ratings yet
TP-Wireless-5.2.2-LRC-OSS Interface Developer Guide (Cellular)
16 pages
ThingPark Wireless - Device Mannager GUI User Guide
No ratings yet
ThingPark Wireless - Device Mannager GUI User Guide
31 pages
TP Enterprise 5.2.2 - Rev2 SAAS User Guide
No ratings yet
TP Enterprise 5.2.2 - Rev2 SAAS User Guide
150 pages
TP Wireless 6.1 OSS API User Guide
No ratings yet
TP Wireless 6.1 OSS API User Guide
86 pages
AdvancedThingParkDeveloperGuide V4
No ratings yet
AdvancedThingParkDeveloperGuide V4
43 pages
ThingPark Wireless - Outdoor LRR Physical Installation Guidelines v1.5
No ratings yet
ThingPark Wireless - Outdoor LRR Physical Installation Guidelines v1.5
43 pages
TPE Data Sheet - 12
No ratings yet
TPE Data Sheet - 12
3 pages
ThingPark Wireless - Logger GUI User Guide
No ratings yet
ThingPark Wireless - Logger GUI User Guide
12 pages
Versatile Routing and Services with BGP: Understanding and Implementing BGP in SR-OS
From Everand
Versatile Routing and Services with BGP: Understanding and Implementing BGP in SR-OS
Alcatel-Lucent
No ratings yet
User Guide: TPPLC Utility For Tp-Link Powerline Adapters and Extenders
No ratings yet
User Guide: TPPLC Utility For Tp-Link Powerline Adapters and Extenders
24 pages
Multipair Ethernet over DMT ver.2: ver, #2
From Everand
Multipair Ethernet over DMT ver.2: ver, #2
Ashlan Chidester
No ratings yet
Reconfigurable Radio Systems: Network Architectures and Standards
From Everand
Reconfigurable Radio Systems: Network Architectures and Standards
Maria Stella Iacobucci
No ratings yet
TPNA SMB Examination Outline
No ratings yet
TPNA SMB Examination Outline
4 pages
Mastering FT8 A Comprehensive Guide to the Ultimate Digital Mode
From Everand
Mastering FT8 A Comprehensive Guide to the Ultimate Digital Mode
Duarte Braga
No ratings yet
TR-369a2 - User Services Platform (USP)
No ratings yet
TR-369a2 - User Services Platform (USP)
213 pages
LEARN MPLS FROM SCRATCH PART-B: A Beginners guide to next level of networking
From Everand
LEARN MPLS FROM SCRATCH PART-B: A Beginners guide to next level of networking
POONAM DEVI
No ratings yet
Voice over LTE: VoLTE
From Everand
Voice over LTE: VoLTE
Miikka Poikselkä
4.5/5 (2)
Nternetworking Oncepts Uide: Netcpts - BK: FRONTMTR - FRM Page I Friday, October 3, 1997 11:15 AM
No ratings yet
Nternetworking Oncepts Uide: Netcpts - BK: FRONTMTR - FRM Page I Friday, October 3, 1997 11:15 AM
79 pages
SIMPLE NETWORK MANAGEMENT PROTOCOLE
No ratings yet
SIMPLE NETWORK MANAGEMENT PROTOCOLE
12 pages
MULTICAST IP ROUTING Part-2: IP routing & forwarding
From Everand
MULTICAST IP ROUTING Part-2: IP routing & forwarding
Ummed Singh
No ratings yet
Alcatel-Lucent Network Routing Specialist II (NRS II) Self-Study Guide: Preparing for the NRS II Certification Exams
From Everand
Alcatel-Lucent Network Routing Specialist II (NRS II) Self-Study Guide: Preparing for the NRS II Certification Exams
Glenn Warnock
No ratings yet
Cellular and Hybrid Networ2
No ratings yet
Cellular and Hybrid Networ2
9 pages
TP Link User Guide
No ratings yet
TP Link User Guide
48 pages
First Hop Redundancy Protocol: Network Redundancy Protocol
From Everand
First Hop Redundancy Protocol: Network Redundancy Protocol
Mulayam Singh
No ratings yet
The Almost Complete Guide to Yaesu's VX-6R
From Everand
The Almost Complete Guide to Yaesu's VX-6R
Phillip J. Boucher
No ratings yet
Alcon 2406 Manual
No ratings yet
Alcon 2406 Manual
87 pages
Onem2M Technologies For Lpwa: Lora in The City
No ratings yet
Onem2M Technologies For Lpwa: Lora in The City
15 pages
Actility Enova Presentation REV01
No ratings yet
Actility Enova Presentation REV01
19 pages
Ruckus Smartzone 300 and Virtual Smartzone-High Scale Administrator Guide 6.1.0!6!29-2023
No ratings yet
Ruckus Smartzone 300 and Virtual Smartzone-High Scale Administrator Guide 6.1.0!6!29-2023
857 pages
Isa PPT1
No ratings yet
Isa PPT1
43 pages
Nortel Passport 8000/ Accelar: Supports Management Module SM-NTL1003
No ratings yet
Nortel Passport 8000/ Accelar: Supports Management Module SM-NTL1003
83 pages
CCNA Exam Focus: Study Guide with Practice Tests
From Everand
CCNA Exam Focus: Study Guide with Practice Tests
SUJAN
No ratings yet
Learning Unit 1
No ratings yet
Learning Unit 1
27 pages
0b15b999 Profile - WP WhyYouNeedOut of BandManagement GP EN 01222020a
No ratings yet
0b15b999 Profile - WP WhyYouNeedOut of BandManagement GP EN 01222020a
5 pages
LEARN MPLS FROM SCRATCH PART-A: A Beginner's Guide to Next Level of Networking
From Everand
LEARN MPLS FROM SCRATCH PART-A: A Beginner's Guide to Next Level of Networking
POONAM DEVI
No ratings yet
New Question 1
No ratings yet
New Question 1
8 pages
[FREE PDF sample] Building Modern Networks Create and manage cutting edge networks and services 1st Edition Steven Noble ebooks
100% (3)
[FREE PDF sample] Building Modern Networks Create and manage cutting edge networks and services 1st Edition Steven Noble ebooks
62 pages
Alcatel-Lucent Service Routing Architect (SRA) Self-Study Guide: Preparing for the BGP, VPRN and Multicast Exams
From Everand
Alcatel-Lucent Service Routing Architect (SRA) Self-Study Guide: Preparing for the BGP, VPRN and Multicast Exams
Glenn Warnock
No ratings yet
ZF in Ap 9 8 Ug 800 70601 001 Revc 20141009
No ratings yet
ZF in Ap 9 8 Ug 800 70601 001 Revc 20141009
187 pages
DPS Telecom
No ratings yet
DPS Telecom
28 pages
Orchestrator Overview
No ratings yet
Orchestrator Overview
5 pages
2300 T Shoot
No ratings yet
2300 T Shoot
76 pages
System 800xa Information Management Getting Started
No ratings yet
System 800xa Information Management Getting Started
194 pages
PMW-MAN03E ParkManager Web User Manual
No ratings yet
PMW-MAN03E ParkManager Web User Manual
128 pages
Lecture 2 - Monitoring & Maintenance
100% (1)
Lecture 2 - Monitoring & Maintenance
39 pages
e4cfb78725f4c234e31a337bd04dc170698e837f2caa6de3e3ce4996c0a553e5
No ratings yet
e4cfb78725f4c234e31a337bd04dc170698e837f2caa6de3e3ce4996c0a553e5
9 pages
1756-EN2TSC User Manual
No ratings yet
1756-EN2TSC User Manual
64 pages
Chapter 1 - Introduction To Network Maintenance Objectives
No ratings yet
Chapter 1 - Introduction To Network Maintenance Objectives
25 pages
Ruckus Wireless Zoneflex 7762 Dual Band 802.11N Outdoor Access Point Getting Started Guide
No ratings yet
Ruckus Wireless Zoneflex 7762 Dual Band 802.11N Outdoor Access Point Getting Started Guide
60 pages
3 2 1 4 Lab Configuring EtherChannel PDF
No ratings yet
3 2 1 4 Lab Configuring EtherChannel PDF
1,106 pages
ZF7762 Getting Started Guide
No ratings yet
ZF7762 Getting Started Guide
60 pages
ThingWorx Deployment Architecture Guide
No ratings yet
ThingWorx Deployment Architecture Guide
49 pages
[Ebooks PDF] download Internetworking Troubleshooting Handbook 2nd Edition Inc. Cisco Systems full chapters
100% (5)
[Ebooks PDF] download Internetworking Troubleshooting Handbook 2nd Edition Inc. Cisco Systems full chapters
81 pages
Technical Guide
No ratings yet
Technical Guide
9 pages
TechCorner 03 - Network Security
No ratings yet
TechCorner 03 - Network Security
6 pages
Mohit Report
No ratings yet
Mohit Report
43 pages
Do One of The Following:: Communications Vocational General Conference Skill Level 2 Year of Introduction: 1953
No ratings yet
Do One of The Following:: Communications Vocational General Conference Skill Level 2 Year of Introduction: 1953
11 pages
B Is 100 Information System Description Template
No ratings yet
B Is 100 Information System Description Template
10 pages
Netwrok Organization Concepts
No ratings yet
Netwrok Organization Concepts
25 pages
My - Statement - 01 Oct, 2022 - 16 Oct, 2022 - 9531808598
No ratings yet
My - Statement - 01 Oct, 2022 - 16 Oct, 2022 - 9531808598
9 pages
Final ECA Lab Manual
100% (1)
Final ECA Lab Manual
75 pages
Web Scraping With Python Tutorials From A To Z
100% (1)
Web Scraping With Python Tutorials From A To Z
35 pages
Winter 2015 - Model Answer PaperDiploma
No ratings yet
Winter 2015 - Model Answer PaperDiploma
32 pages
Association of European Automotive and Industrial Battery Manufacturers
No ratings yet
Association of European Automotive and Industrial Battery Manufacturers
40 pages
Functional Testing With Examples
No ratings yet
Functional Testing With Examples
10 pages
Cad Cam Lecture Notes
100% (1)
Cad Cam Lecture Notes
2 pages
External User (Agent) Registration Use Case-Diagram: Create Online Account
No ratings yet
External User (Agent) Registration Use Case-Diagram: Create Online Account
16 pages
NGFW Battle Card
No ratings yet
NGFW Battle Card
3 pages
BGS Project Report Group2
No ratings yet
BGS Project Report Group2
34 pages
Recursion
No ratings yet
Recursion
14 pages
R3 Science and Technology and Nation Building
No ratings yet
R3 Science and Technology and Nation Building
11 pages
Aggregate Functions Grouping - Question
No ratings yet
Aggregate Functions Grouping - Question
3 pages
day-1
No ratings yet
day-1
30 pages
Introduction To Online Auction Systems
No ratings yet
Introduction To Online Auction Systems
11 pages
CC ZG522 Ec-2r First Sem 2023-2024
No ratings yet
CC ZG522 Ec-2r First Sem 2023-2024
12 pages
2-LISTOFCOURSESINDEX3-1
No ratings yet
2-LISTOFCOURSESINDEX3-1
4 pages
Experiment No. 04 Experiment Name-QPSK Modulation & Demodulation Aim Equipments Needed
No ratings yet
Experiment No. 04 Experiment Name-QPSK Modulation & Demodulation Aim Equipments Needed
10 pages
Subjective Evaluation of State of The-Art 2-Channel Audio Codecs
No ratings yet
Subjective Evaluation of State of The-Art 2-Channel Audio Codecs
24 pages
Avpxw05 5dai VPX Imo 10 06 3 tf04
No ratings yet
Avpxw05 5dai VPX Imo 10 06 3 tf04
20 pages
Btu Meter
No ratings yet
Btu Meter
1 page
SevOne Data Insight 3.12 Report Linking URL Specification Guide
No ratings yet
SevOne Data Insight 3.12 Report Linking URL Specification Guide
20 pages
MWB1450Q Updated
No ratings yet
MWB1450Q Updated
26 pages
Presentation (Smart Calculator)
No ratings yet
Presentation (Smart Calculator)
10 pages
Cis Rhel6 Linux RCL
No ratings yet
Cis Rhel6 Linux RCL
17 pages
Blueprint For The Alienvault Certified Security Engineer Exam
No ratings yet
Blueprint For The Alienvault Certified Security Engineer Exam
3 pages

TP-Wireless-5.2.2-Network Manager User Guide-Rev2

Uploaded by

TP-Wireless-5.2.2-Network Manager User Guide-Rev2

Uploaded by

ThingPark Wireless

Network Manager User Guide

© 2019 ACTILITY SA. All rights reserved.

Under Non-Disclosure Agreement

Version Date Author Details

Under Non-Disclosure Agreement

New/Enhanced Functionalities For More Information, See… Release

RDTP-12998: Alarm history 7 Working with Base Station Alarms 5.2.2-3

Under Non-Disclosure Agreement

Under Non-Disclosure Agreement

Under Non-Disclosure Agreement

Under Non-Disclosure Agreement

Under Non-Disclosure Agreement

Under Non-Disclosure Agreement

The ThingPark set consists of four main key components:

Operator & Enterprise Application Servers

ThingPark OS ThingPark Wireless Core NW & OSS ThingPark X

Wireless Device Network

Spectrum Network LoRaWANTM LoRaWANTM

LoRaWANTM LRR (Gateway)

Figure 1 – ThingPark Solution Architecture Description High Level Product Illustration

Under Non-Disclosure Agreement

3.2 Supplier Access

The following window appears:

Under Non-Disclosure Agreement

3.3 Subscriber access

Enter your e-mail and password.

1. Click Sign in.

Under Non-Disclosure Agreement

▪ A “Create” button, to add new base stations

▪ A search bar to find base stations based on specific criteria

▪ A Map/List space to show the base station details:

4.1 Searching Base Stations

The Search bar looks like this:

4.2 Base Stations List

Under Non-Disclosure Agreement

▪ Version: LRR software version of the base station

▪ Software restart: date/time of the last LRR software restart

▪ Min remaining cap up/down: not supported in the current release.

Under Non-Disclosure Agreement

▪ Edit : use this option to edit the base station details.

Under Non-Disclosure Agreement

▪ Base station ID: LRR-UUID OR LRR-ID (depending on the “Identification mode”)

▪ Serial Marketing Number (SMN) (optional): the format is 0000-XX-0000-0000

Under Non-Disclosure Agreement

▪ Name (optional): Base station given name.

New in release 5.2.2: Enhanced Security Access to Key Installer (RDTP-7582).

Under Non-Disclosure Agreement

NOTE: This feature is only compatible with LRR-UUID identification mode.

To use this feature, the following steps are required:

Public key provisioning during base station creation:

Under Non-Disclosure Agreement

Under Non-Disclosure Agreement

6.1 Main Frame

Under Non-Disclosure Agreement

6.1.1 Indicators Frame

6.1.1.1 System Indicators

Under Non-Disclosure Agreement

6.1.1.2 RF Cell Indicators

▪ Uplink/downlink average packets: hourly average number of packets, estimated over

▪ Last packets: date and time of the last packet

6.1.1.3 WAN Backhaul Indicators

Under Non-Disclosure Agreement

6.1.2 Uplink/Downlink Packets Frame

Under Non-Disclosure Agreement

6.1.4 Status Frame

6.2 Base Station Antennas

Under Non-Disclosure Agreement

▪ Antenna gain: measured in dBi units (decibels-isotropic)

▪ For V1 gateways (based on Semtech’s V1 reference design):

▪ 1 sector, 1 antenna, 1 board (mono-sector 1*8): s1_a1_b1

▪ For V2/V3 gateways (based on Semtech’s V2 reference design):

▪ 1 sector, 1 antenna, 1 board (mono-sector 1*8 or 1*16): s1_a1_b1

▪ 1 sector, 2 antennas, 1 board (mono-sector 2*8): s1_a2_b1 → Antenna

▪ 1 sector, 2 antennas, 2 boards (mono-sector 2*16): s1_a2_b2 → Antenna

▪ 1 sector, 1 antenna, 4 boards (mono-sector 1*64): s1_a1_b4

▪ 1 sector, 1 antenna, 1 board (mono-sector 18 or 116): s1_a1_b1

▪ 3 sectors, 3 antennas, 3 boards (tri-sectors 18 or 116): s3_a3_b3