邊緣與云物聯(lián)網(wǎng)平臺(tái)集成方案

1、Integration of Edge and Cloud IoT Platforms邊緣與云物聯(lián)網(wǎng)平臺(tái)集成方案Mainflux Project/mainflux/mainfluxOpen-Sorce, Apache-2.0 licensed, patent-freeOver 30 contributorsWritten in GoDocker & KubernetesUsed in productionMainflux Labs/Professional services around Mainflux IoT PlatformClients are big companies in the

2、 domain of Oil&Gas, Retail, Telecom, Semiconductor.MFX-1 IoT gateway with EdgeX Foundry SWEdgeflux gateway management SaaSDocker & KubernetesUsed in productionCloudMainflux - OverviewMicroservice ArchitectureGolang wherever possible - Go KitNATS Message BusNginXTLS/DTLS TerminationReverse Proxy for

3、UISQL database for structured dataNoSQL database for Telemetry:InfluxDBMongoDBCassandraMainflux Scales from PRi class devices to multi datacenter with Kubernetes and Cassandra DBDeployment:NativeDocker containers (compose provided)Kubernetes scriptsMainflux - ArchitectureMainflux - ArchitectureMainf

4、lux - ArchitectureUsersUser represents a human user of the system and is basic entity in the Mainflux IoT Platform. User is authenticated by email and password.Once authenticated user receives JWT to use for further actions.Each user is Admin within his domainThingsConnected devices and applications

5、 are the same entity. We call them Things.Internal representation of every device is saved to databaseChannelsChannel connects Things (devices and/or applications)Only Things connected to the same Channel can communicate with each other.Mainflux - SecurityAuthentication with Mainflux keysMainflux ke

6、y is a secret key thats generated at the Thing creationMutual TLS Authentication with X.509 CertificatesClient-to-server authentication using client-side X.509This is called two-way or mutual authenticationMainflux supports mTLS over HTTP, WS, and MQTT protocols (no CoAP at the moment)Thing key will

7、 be used to create x.509 certificateHTTPS Authorization header does not have to be presentMQTTS Password filed in CONNECT message must match the key from the certificateWSS Authorization header or authorization query parameter must match cert keyMainflux - DevOpsEventsEvents are published to Redis S

8、tream. This is useful for integration with 3rd party systemsLogsFluentdElastic SearchKibanaMetricsPrometheusGrafanaEdgeEdgeXAn open source, vendor neutral project (and ecosystem)A microservice, loosely coupled software framework for IoT edge computing Hardware and OS agnosticLinux Foundation, Apache

9、 2 licensed projectGoal:enable and encourage growth in IoT solutionsThe community builds and maintains common building blocks and APIsPlenty of room for adding value and getting a return on investmentAllowing best-of-breed solutionsEdgeXA collection of a 10+ microservicesWritten in multiple language

10、s (Java, Go, C, we are polyglot believers!)EdgeX data flow:Sensor data is collected by a Device Service from a thingData is passed to the Core Services for local persistenceData is then passed to Export Services for transformation, formatting, filtering and can then be sent “north” to enterprise/clo

11、ud systemsData is then available for edge analysis and can trigger device actuation through Command serviceMany others services provide the supporting capability that drives this flowREST communications between the serviceSome services exchange data via message bus (core data to export services and

12、rules engine)Micro services are deployed via Docker and DockerComposeEdgeX - How it WorksIntegrationEdge-CloudMainflux on the EdgeUnified IoT Platform - same code in the cloud and on the gatewayStrong security - X.509 certificates and device tokensSmall footprint - Docker images 5MBEdged - IoT agent on the gatewayElm-based UI for administrationEdgeX on the EdgePlethora of Device ServicesLinux Foundation LF Edge projectMFX-1 distribution