Connectivity Management

This page describes the basic functionality and principles of akenza's connectivity management

On akenza, two options are possible to make use of LPWAN network providers for device connectivity:

1. Connectivity-as-a-Service

2. Integrations

1. Connectivity-as-a-Service

With Connectivity-as-a-Service (CaaS), akenza offers a selected number of network providers which can be used out of the box on Data Flow level as device connector.

CaaS allows one to quickly get started with an IoT project without the need of setting up an individual account for a network provider.

Akenza currently offers CaaS for the following integration providers:

• Swisscom LoRaWAN

• Loriot

• The Things Network

• Everynet (soon)

• EWZ (soon)

CaaS provider on Data Flow

2. Integrations

Akenza seamlessly integrates with various connectivity providers. These integrations can be used to connect, synchronize and manage Assets of a connectivity provider account.

Integrations

The below list consists of all supported connectivity providers and their feature sets.

Integration provider	Type	Coverage	Asset Sync	Data Routes
Swisscom LoRaWAN	LoRaWAN	Switzerland	Yes	Yes
EWZ LoRaWAN	LoRaWAN	Zurich	Yes	Yes
Loriot	LoRaWAN	global	Yes	Yes
Actility's ThingPark Wireless	LoRaWAN	global	Yes	Yes
The Things Network	LoRaWAN	global	Yes	No

Integrations allow the management of Devices and Sim Cards of connectivity providers. This enables the integration of already existing assets into akenza and manages all Assets from a single point.

Depending on the connectivity provider, multiple options for authorizing the process are available. These are described in the individual documentation.

Synchronizing an Integration

By clicking on the synchronize action on the Integration list, the synchronization process starts. On the first setup, the Integration synchronizes automatically. All changes will be applied from the connectivity provider to the Inventory list of akenza. New devices will be created, updates will be reflected and deleted devices will also be deleted on akenza.

If a device gets created or updated in akenza, and is linked to integration, these changes will also be reflected on the platform of the connectivity provider. Deleting devices will be reflected as well. Therefore no double-handling on the integration account is required.

By adding an Integration, an appropriate device connector will be created simultaneously. This new Device Connector can be used in Data Flows to receive and process data from IoT devices in akenza.

Data Routes

Data Routes reflect the data output of the connectivity provider platform. This can either be akenza or any other third-party provider. Depending on the connectivity provider, Data routes can be created and managed through akenza.

In order to create a new Data Route, the button in the top right corner needs to be clicked. The Integration to create the data route has to be selected, as well as all properties for the data route specified.

Existing data routes can be deleted by selecting the + (plus) icon on the Integration list and clicking the delete action in the appropriate data route entry.

It is not possible to create Data Routes or synchronize Devices or Sim Cards using out-of-the-box connectivities. Their Device Connectors however can be used in Data Flows which allows creating Devices and receiving and processing their data in akenza.

Deleting an Organization which contains Assets managed through CaaS will also be irreversibly deleted on the connectivity provider platform.

Device Connectors

When creating an integration, a device connector will be created. It can be used to receive and process data from your IoT assets in akenza.