Documente Academic
Documente Profesional
Documente Cultură
AGENDA
Introduction
General overview
Monitoring
Introduction
Functional architecture
System architecture
High availability
Monitoring
Actility helps service providers all the way from connectivity to online distribution of their IoT offers
Gateway of LRR :
Radio basestation for LoRa devices with a dynamic bitrate adaptation saves batteries and airtime whenever
possible.
Symmetrical bidirectional communications
OSS or Backoffice :
Its the network partner portal, applications to manage the End Devices including Billing, Logging and
Monitoring are here implemented.
ThingPark Store :
ThingPark Cloud :
It sets an excellent platform standard, that focus on data analysis and representation (e.g. alarming, charging,
monitoring applications)
On-Line Shops
Supplier
Manager
Marketplace
SNMP Traps,
REST APIs
Ordering APIs
Store APIs
User Portal
Application Servers
REST APIs
Operator
Manager
Connectivity
Manager
Network
Manager
Wireless
Logger
Spectrum
Analysis
Tool
LoRaWAN
Network
Servers LRCs
ThingPark Cloud
ETSI M2M
Net GSCL
ETSI M2M
NSCL
Store (EShop)
Billing &
Charging
Network
Survey
Security
Server
System
Management
Platform (SMP)
Local GW (GSCL)
Any Device
LoRa Device
Optional
Introduction
Functional architecture
System architecture
High availability
Monitoring
DMP Mapping
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
8
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
10
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
12
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
SLRC VPNC
It ends IPSec VPN connections by implementing a StrongSwan server.
Strongswan was choosen by Actility for its capability to terminate more than 1000 VPN tunnels
RCA
RCA is a PKI (Public Key Infrastructure) providing a set of functionalities to trust to a
certificate signed by a certificate authority :
generate, manage and revoke X.509 certificates allocated to base stations and VPNC
publish certificates
generate and publish revocation lists
13
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
14
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
A GUI functionality will be available on the platform and all these steps will be done
automatically on the background
15
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
16
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
18
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
It also enables the decoding of payload data and other application layer messages and
frames for some partner devices.
19
End user
PORTAL
Charging (ogone)
Operator
Vendor
Suppliers
End user
Configuration
STORE
Orders
(sef-activation)
SMP
invoices
BILLING
Operat or/vendor/
suppl ier/subscribers DB
eShop DB
Invoi ce DB
Charging
(UDR)
LoRA device/base
stations DB
End user
Application(s)
End user
TWA
WLOGGER
End user
Statistic DB (monoDB)
Log DB DB
LRC
Application(s)
Table A/B/L/S
(file syst em)
SUPPORT
Reverse SSH
SLRC
IEC link
20
LoRa
device
LRR
PKI
configuration
Operator
RCA
PKI DB DB
22
HSM
23
Sends JOIN_REQUEST
with encrypted AppKey
LRC
Introduction
Functional architecture
System architecture
High availability
Monitoring
DMP Mapping
24
25
26
UPPER-RED
LOWER-RED
ORANGE
MANAGEMENT
27
GREEN
28
Site A / B
AS_RCA
Site A / B
i6: IPsec IK E / MOBI KE
Site A / B
Site A / B
i23: Downlink req
VPN (ipsec)
I8a: Ping (SLRC)
SLRC
LRC
LRR
PROXY_HTTP
Site A / B
OPTIONAL To be evaluated
According to the access network.
PROXY_AS
i9a: Reverse LRR admin
i26: LRR admin
Site A / B
SUPPORT
OPTIONAL
To be evaluated
According to the
access network.
29
SSH term. (Actility
engineers)
AS_WLOGGER
AS_TWA
AS_TWA
Site A / B
PROXY_HTTP
Site A / B
WebApp (Actility
ThingPark Marketplace)
AS_SMP
WebApp (Payment
Service)
a16: Email
SMTP
WebApp (Payment
Service)
WebApp (Partners)
Site A / B
a19: Email
AS_BILL
SMTP
a2: GUI
a21: Rep osito ry resyn c
Site A / B
Browser (Partners)
a3: GUI
a22: Email
AS_STORE
SMTP
Billing
LRC
Site A / B
PROXY_AS
a24: Email
SMTP
a25: SNMP Notification
SNMP
a10: Admin API
AS_TWA
Site A / B
PROXY_AS
LRC
SUPPORT
Site A / B
AS_WLOGGER
Site A / B
30
Site A / B
AS_PORTAL
AS_SMP
AS_BILL
AS_STORE
AS_TWA
AS_WLOGGER
Site A / B
AS_RCA
PROXY_HTTP
Site A / B
AS_SMP
PROXY_HTTP
Site A / B
AS_BILL
PROXY_HTTP
Site A / B
AS_STORE
Site A / B / C
SQL
PROXY_HTTP
PROXY_AS
PROXY_HTTP
Site A / B
AS_WLOGGER
Site A / B
AS_PORTAL
PROXY_HTTP
PROXY_AS
31
Site A / B
AS_TWA
Site A / B / C
MG_CONF
Site A / B (MG_NODE)
Site C (MG_ARB)
MG_NODE /
MG_ARB
d20/d21: Mongo primary election
d19: Mongo data replication (MG_NODE only)
Site A / B
Browser (Actility
engineers)
m4: Email
SMTP
AS_NAGIOS
m5: SNMP Notification
SNMP
m2: Nagios NRPE
Site A / B / C
All ThingPark
servers
AS_NAGIOS (Site A) toward all ThingPark servers (Site A / C)
AS_NAGIOS (Site B) toward all ThingPark servers (Site B / C)
c1: SSH/SCP
SSH term (Actility
engineers)
Site A / B / C
All ThingPark
servers
c1a: ICMP
NTP
c3: NTP request
c5: SSH/SCP
REPO
32
c6: SSH/SCP
33
Introduction
Functional architecture
System architecture
High availability
Monitoring
34
Primary site
LRR
LRC01.ORANGE.COM
Sync link
LRC01.ORANGE.COM
Secondary site
LRC02.ORANGE.COM
LRC02.ORANGE.COM
35
LRR
LRC01.ORANGE.COM
Sync link
LRC01.ORANGE.COM
Secondary site
LRC02.ORANGE.COM
LRC02.ORANGE.COM
36
Replica set : It is a group of mongoDB node (mongod processes) that maintain the same data set. ThingPark replica
sets are composed of a primary node, a secondary node and an arbiter node.
Primary : The primary accepts all write operations from application servers. A replica set can have only one
primary. To support replication, the primary records all changes to its data sets in its oplog.
Secondary : The secondary replicates the primarys oplog and applies the operations to their data sets such that the
secondary data sets reflect the primarys data sets. If the primary is unavailable, the replica set will elect the
secondary to be primary.
Arbiter : The arbiter is also a mongod instance that does not maintain data sets. The purpose of an arbiter is to
maintain a quorum in a replica set by responding to heartbeat and election requests by other replica set members.
38
39
40
Introduction
Functional architecture
System architecture
High availability
Monitoring
41
System alarms
Active monitoring on the platform is done by Nagios
Scripts (plugins) are launched on VMs to check the health of system, databases,
applications.
42
43
44
45
47
Thank You