User Tools
wiki:introduction
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wiki:introduction [2017/10/30 10:04] tda |
wiki:introduction [2020/08/03 16:59] (current) mbi |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| - | A Kerlink IoT network is based on a park of Base Stations (Wirnet family) and a network platform (Wanesy RAN). | + | A Kerlink IoT network is based on a set of base Stations (Wirnet, iBTS or iFemtocell product family) and a network platform (Wanesy RAN). |
| - | The different RAN sub-systems are: | ||
| - | * Unordered List ItemBase Stations Controller (BSC) for stations management | + | {{:wiki:lpwa_network.png|}} |
| - | * Radio Network Controller (RNC) for radio aspects management | + | |
| - | * LoRaWAN™ Network Server (LNS) for endpoints data decoding and routing | + | |
| - | * Location Based Services (LBS) for geolocation of endpoints | + | |
| - | Interfaces for customer and user access: | ||
| - | * Dashboard | + | The Wanesy RAN (Radio Access Network) platform includes 3 sub-systems : |
| - | * OSS RESTful APIs | + | |
| - | * OSS PUSH APIs | + | |
| + | * Base Stations Controller (BSC) for stations management | ||
| + | * Radio Network Controller (RNC) for radio aspects management | ||
| + | * LoRaWAN™ Network Server (LNS) for end-devices data decoding and routing | ||
| + | The following component is optional : | ||
| + | * Location Based Services (LBS) for geolocation of end-devices | ||
| + | The platform provides interfaces for customer and user access : | ||
| - | ===== Glossary ===== | + | * Dashboard (GUI) |
| - | + | * OSS RESTful APIs | |
| - | ==== Cluster ==== | + | * OSS PUSH APIs |
| - | + | ||
| - | A cluster is a logical way to group endpoints.\\ | + | |
| - | An endpoint can only be present in one cluster. | + | |
| - | + | ||
| - | This is also where is defined how the LoRa data is pushed to your server. This is a per-cluster setting. | + | |
| - | ==== Fleet ==== | + | |
| - | + | ||
| - | A fleet is a logical way to group stations.\\ | + | |
| - | A station can only be present in one fleet. | + | |
| - | + | ||
| - | ==== Station ==== | + | |
| - | + | ||
| - | A station is identified by its EUI.\\ | + | |
| - | A station can only be present in one fleet. | + | |
| - | + | ||
| - | ==== Endpoints ==== | + | |
| - | + | ||
| - | Sensor associated to a cluster and a region (868, 915, 923).\\ | + | |
| - | Can be activated by OTAA or ABP. | + | |
| - | + | ||
| - | ==== Customer ==== | + | |
| - | + | ||
| - | A customer is a group of fleets and clusters. | + | |
| - | + | ||
| - | ===== Users and roles ===== | + | |
| - | + | ||
| - | ==== Super Admin ==== | + | |
| - | + | ||
| - | Super Admin has a global view of the whole platform – whatever the customer. | + | |
| - | + | ||
| - | ==== Admin ==== | + | |
| - | + | ||
| - | Admin is dedicated to a customer – can perform all the operation limited to a specific customer | + | |
| - | + | ||
| - | ==== User ==== | + | |
| - | User is dedicated to a customer – can perform all the operation on fleets, stations, clusters and end points limited to a specific customer | + | The platform proposes a set of services for operations and device management : |
| + | * Base stations monitoring& maintenance | ||
| + | * Endpoints monitoring & maintenance | ||
| + | * RF spectrum monitoring | ||
| + | * RESTful API for OSS integration | ||
| + | * Web graphical dashboard | ||
| + | * LoRaWan Network server | ||
| + | * LoRaWan Application server | ||
| + | * Multi-protocol data router | ||
| + | * Network controller | ||
| + | * Endpoint localization service (LBS) | ||
| - | ==== Reader ==== | ||
| - | Same as USER but read only. | ||
wiki/introduction.1509354280.txt.gz · Last modified: 2017/10/30 10:04 by tda
Page Tools
