Difference between revisions of "AMTech..."
From AMTech WikiDocs
(→=IoT Core services) |
(→IOT Platform Gartner) |
||
| (80 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ==IOT Platform Gartner== | ||
| + | [[File:gartner-iot-arch.png|950px||thumbnail|center|IoT Platform]] | ||
| + | |||
== PaaS == | == PaaS == | ||
| − | Platform as a Service (PaaS) brings the benefits that SaaS | + | Platform as a Service (PaaS) brings the benefits that SaaS brought for applications, but over to the software development world. |
PaaS can be defined as a computing platform that allows the creation of web applications quickly and easily and without the complexity of buying and maintaining the software and infrastructure underneath it. | PaaS can be defined as a computing platform that allows the creation of web applications quickly and easily and without the complexity of buying and maintaining the software and infrastructure underneath it. | ||
PaaS is analogous to SaaS except that, rather than being software delivered over the web, it is a platform for the creation of software, delivered over the web. | PaaS is analogous to SaaS except that, rather than being software delivered over the web, it is a platform for the creation of software, delivered over the web. | ||
| Line 8: | Line 11: | ||
== IoT == | == IoT == | ||
The Internet of Things (IoT) is the network of physical objects (things) with unique identifiers and the ability to communicate and sense, as well as interact with their internal states and/or the external environment, without requiring human-to-human or human-to-computer interaction, by leveraging the Internet. | The Internet of Things (IoT) is the network of physical objects (things) with unique identifiers and the ability to communicate and sense, as well as interact with their internal states and/or the external environment, without requiring human-to-human or human-to-computer interaction, by leveraging the Internet. | ||
| − | [[File:IoTBP.jpg|thumbnail|850px | + | [[File:IoTBP.jpg|thumbnail|850px|center|Internet of Things]] |
| + | |||
== Edge == | == Edge == | ||
| − | + | The edge could be the devices themselves, an on-premise gateway connecting a group of devices, or even a machine in the cloud. The right flavor will be dictated by the use cases, but in every situation there will be value in distributing intelligence to the edge | |
*Greater Responsiveness | *Greater Responsiveness | ||
*Lower Total Cost of Ownership | *Lower Total Cost of Ownership | ||
| Line 28: | Line 32: | ||
===Devices ([[M2M Bridge|M2M]])=== | ===Devices ([[M2M Bridge|M2M]])=== | ||
| − | *Devices [[Functionality|Protocols]] | + | *Devices [[M2MBridge Functionality|Protocols]] |
| − | *Communication [[Functionality|Protocols]] | + | *Communication [[M2MBridge Functionality|Protocols]] |
*[[M2M_Bridge#Cloud Configuration|Centralized management]] | *[[M2M_Bridge#Cloud Configuration|Centralized management]] | ||
*[[AMTech...#Edge|Edge]] [[M2M_Bridge#Intelligence at the Edge|intelligence]] | *[[AMTech...#Edge|Edge]] [[M2M_Bridge#Intelligence at the Edge|intelligence]] | ||
*[[M2M_Bridge#Intelligence at the Edge|Monitoring]] | *[[M2M_Bridge#Intelligence at the Edge|Monitoring]] | ||
| − | ===Cloud based & | + | ===Cloud based & multitenancy === |
| − | * | + | *[[Access_control#Multitenancy|multitenant]] |
| − | *scalable | + | *cluster of [[Big_Data|services]] replicated , monitored and scalable on-demand: |
| + | #Identity management | ||
| + | #Publish subscriber queuing | ||
| + | #Real time streaming | ||
| + | #Rule engine | ||
| + | #Big data speed layer | ||
| + | #Bid data real time data view | ||
| + | #Memory caching | ||
| + | #Scheduled jobs | ||
| + | #Maps | ||
| + | #Location information services | ||
| + | #Orchestration | ||
| + | #Deployment and version control | ||
| + | #Troubleshoot | ||
===Reasoning in real time=== | ===Reasoning in real time=== | ||
| Line 59: | Line 76: | ||
===Reference data=== | ===Reference data=== | ||
| + | [[Big_Data#Real time view|Real time view]] | ||
Example of what developers think | Example of what developers think | ||
[https://www.progress.com/docs/default-source/default-document-library/progress/documents/papers/iot_surveyreport.pdf Stay of IoT] | [https://www.progress.com/docs/default-source/default-document-library/progress/documents/papers/iot_surveyreport.pdf Stay of IoT] | ||
| − | ==IoT | + | ==AMTech IoT services== |
| − | + | ; A service refers to a set of related software functionalities that can be reused for different purposes, together with the policies that should control its usage | |
| − | + | [[File:IoTServicesView.png|1150px|IoT Services]] | |
| − | **Supports | + | === Resources semantic === |
| + | ;[[IoT Semantics|IoT Semantics]] | ||
| + | [[File:Ser-semantic.jpg|30px|semantic]] | ||
| + | *Restful and NOSQL real-time views; for querying and managing resources semantic; structured according to the RDF and represented leveraging linked data and Json-ld. | ||
| + | **Supports resources types version control with publication policies | ||
| + | |||
| + | === Real Time View === | ||
| + | ;[[Big Data|Big Data]] | ||
| + | [[File:Srv-realtimeview.jpg|30px|view]] | ||
| + | *Restful and NOSQL real-time view for querying and managing resources instances; structured according to the RDF and represented leveraging linked data and Json-ld. | ||
| + | **Support instances enrichment, allowing insert new properties and values after semantic been extended. | ||
| + | |||
| + | === Identity access management === | ||
| + | ;[[Access_control|Access_control]] [[File:Srv-identity-management.jpg|30px]] | ||
| + | *Manages the identity and information of users that describes the operations and access control over IoT resources, offering a secure multi-tenancy and protected IoT real time view data hosting. | ||
| + | **actors for grouping access policies | ||
| + | **access control based on resource’s type, tenant and user id | ||
| + | |||
| + | === Sensor Network === | ||
| + | ;[[Sensor's network|Sensor's network]] [[File:Srv-sensornetwork.jpg|30px]] | ||
| + | *Restful publish / subscribe message broker and event processing network that allows subscribers and publishers to exchange observations classified by topics or/and observations types; uses linked data to represent observations semantic and MQTT topics to express the physical organization of sensors network. | ||
| + | |||
| + | === Real Time Intelligence === | ||
| + | ;[[Observers|Observers]] [[File:Realtime-intelligence.jpg|30px]] | ||
| + | *Query engine for discovering new knowledge emerging from associating real time observations with Things real time views, bringing into account time, spatial location and observed properties. | ||
| + | |||
| + | === Location-aware === | ||
| + | [[File:Srv-location-aware.jpg|30px]] | ||
| + | *Set of geometric and mathematical algorithms responsible for the [[Location|location]], organization and spatial relation between Things. It leverages geolocation/GPS or WiFi positioning system and [[Proximity_area|proximity location]] technologies to guarantee that observations and things get enriched with accurate location. | ||
| + | |||
| + | === Rules and Actions Execution === | ||
| + | [[File:Srv-riles-execution.jpg|30px]] | ||
| + | *A distributed computation framework that offers the [[Execution_engine|queuing]] and stream processing capabilities for computing IoT real-time views; by processing observations and executing pre-configured [[Observers|observers]] and [[Actions|actions]]. | ||
| + | |||
| + | === Push notifications === | ||
| + | ;[[Notifications|Notifications]] [[File:Srv-notifications.jpg|30px]] | ||
| + | *A service for sending asynchronous notifications using a private channel, leveraging access control policies, sensor network infrastructure and HTML5 websockets. | ||
| + | |||
| + | === Time-aware === | ||
| + | ;[[IoT_Semantics#Things_and_Observations_semantic|Things type]] [[File:Time-aware.jpg|30px]] | ||
| + | *Maintains a set of copies of observed properties per Thing; control by frequency and amount of copies; allows real time view data size and expiration time configuration. | ||
| + | |||
| + | === Scheduler Fault-tolerant distributed === | ||
| + | ;[[Actions#Send_scheduled_observation|Scheduled observations]] [[File:Srv-Scheduler.jpg|30px]] | ||
| + | *is used to schedule tasks and orchestrate the executions of business rules actions. | ||
| + | |||
| + | === Generating code and data binding === | ||
| + | ;[[Reasoners|Reasoners]] [[File:Srv-binding.jpg|30px]] | ||
| + | *For the creation and consumption of error free resources configuration information. | ||
| + | |||
| + | === Observation Enrichment === | ||
| + | ;[[Observation_enrichment|Enrichment]] [[File:Srv-obsrv-enrichment.jpg|30px]] | ||
| + | *producer, access control topics and things relation can be configured to be enriched with: | ||
| + | **geospatial information like country, city... | ||
| + | **user content, user id, tenant… | ||
| + | **EPC information company prefix, product code.. | ||
| + | **Other M2MBridge plugins placeholders | ||
| + | |||
| + | === Edge intelligence and M2M Bridge === | ||
| + | ;[[M2M Bridge|M2M Bridge]] [[File:Srv-m2mBridge.jpg|30px]] | ||
| + | *Configurable edge intelligence | ||
| + | *Automatic deployment with autodiscovering | ||
| + | *Integrated devices and M2M protocols (data and commands from/to devices) | ||
| + | **SNMP, LLRP, iBeacon, eddystone, PLC, GPIO, EPC, NFC, ODB-II, OPC-UA, Modbus, BLE GATT | ||
| + | *Device-to-device or device-to-cloud communications (Mesh network, aggregation) | ||
| + | **Digi Mesh, wifi, classic Bluetooth, BLE, ZigBee, RFID, Wi-Fi, RS485/232 | ||
| + | *Remote and centralized control of IoT devices and gateways. | ||
| + | *Common functionality and host the execution of the protocols | ||
| + | *Network failure detection and recovery | ||
| + | *Get centralized configuration information at startup and real-time modification | ||
| + | *Access control policies to manager observations production and consumption | ||
| + | |||
| + | === Creator User Experience (PaaS configuration) === | ||
| + | ;[[Access_control#Roles|Creator]] [[File:Srv-followers.jpg|30px]] | ||
| + | *define and manage resources type (semantic) | ||
| + | *configure observation production | ||
| + | *configure activities | ||
| + | *debug & test activities | ||
| + | *deploy activities | ||
| + | |||
| + | === SaaS configuration user experience === | ||
| + | ;[[Access_control#Roles|Followers]] [[File:Srv-followers.jpg|30px]] | ||
| + | *user experience to configure IoT SaaS from Activities defined using AMTech creator experience | ||
| + | *access to things and notifications based on follower roles, tenant and user | ||
| + | *scale when new things, sensors and business rule get deployed | ||
| + | |||
| + | === Cloud App Marketplace === | ||
| + | ;[[Services|Services]] [[File:Srv-Marketplace.jpg|30px]] | ||
| + | *offers the tools for: | ||
| + | **developers to quicker and simpler deliver IoT solutions to market. | ||
| + | **businesses to discover new IoT solutions that extend your business. | ||
| + | |||
| + | === Electronic Product Code === | ||
| + | ;[[Execution_engine#EPC|EPC]] [[File:Srv-epc.jpg|30px]] | ||
| + | *encoding and decoding: | ||
| + | **SGTIN-96, SGTIN-198, SSCC-96, SGLN-96, SGLN-195, GRAI-96, GRAI-170, GSRN-96, GSRNP-96, GDTI-96, GDTI-174, GID-96. | ||
| + | |||
| + | === Connectivity === | ||
| + | ;[[Mesh_network|Mesh network]] [[File:IoTConectivity.png|30px]] | ||
| + | IoT mesh network implementing edge intelligence industrial protocol and connecting edge components from the sensor to the cloud and back including edge logic | ||
| + | *Digi Mesh PTMP 9 miles | ||
| + | *Digi Mesh PTMP 25 miles | ||
| + | *PTMP repeater 100 miles | ||
| + | |||
| + | === Sensors design === | ||
| + | ;[[File:SensorDesign.png|30px]] | ||
| + | *Components to detect/collect requires properties | ||
| + | *Connection and industrial protocol integrated to the platform and IoT semantic. | ||
| + | *Required IP Ratings: (Ingress Protection or International Protection) | ||
| + | *Form factor | ||
| + | *Power supply | ||
Latest revision as of 14:18, 12 October 2017
Contents
- 1 IOT Platform Gartner
- 2 PaaS
- 3 Thing
- 4 IoT
- 5 Edge
- 6 Big Data & Real time
- 7 The Challenge
- 8 AMTech IoT services
- 8.1 Resources semantic
- 8.2 Real Time View
- 8.3 Identity access management
- 8.4 Sensor Network
- 8.5 Real Time Intelligence
- 8.6 Location-aware
- 8.7 Rules and Actions Execution
- 8.8 Push notifications
- 8.9 Time-aware
- 8.10 Scheduler Fault-tolerant distributed
- 8.11 Generating code and data binding
- 8.12 Observation Enrichment
- 8.13 Edge intelligence and M2M Bridge
- 8.14 Creator User Experience (PaaS configuration)
- 8.15 SaaS configuration user experience
- 8.16 Cloud App Marketplace
- 8.17 Electronic Product Code
- 8.18 Connectivity
- 8.19 Sensors design
IOT Platform Gartner
PaaS
Platform as a Service (PaaS) brings the benefits that SaaS brought for applications, but over to the software development world. PaaS can be defined as a computing platform that allows the creation of web applications quickly and easily and without the complexity of buying and maintaining the software and infrastructure underneath it. PaaS is analogous to SaaS except that, rather than being software delivered over the web, it is a platform for the creation of software, delivered over the web.
Thing
A Thing is a physical object or even a piece of data, with a unique identifier and a group of properties like: location, temperature, speed, acceleration, altitude, weight, volume, pressure, value or any other variable that can be measured
IoT
The Internet of Things (IoT) is the network of physical objects (things) with unique identifiers and the ability to communicate and sense, as well as interact with their internal states and/or the external environment, without requiring human-to-human or human-to-computer interaction, by leveraging the Internet.
Edge
The edge could be the devices themselves, an on-premise gateway connecting a group of devices, or even a machine in the cloud. The right flavor will be dictated by the use cases, but in every situation there will be value in distributing intelligence to the edge
- Greater Responsiveness
- Lower Total Cost of Ownership
- Scalability
- Device Interoperability
Big Data & Real time
The Challenge
IT encompasses a set of technologies, concepts and software stacks in order to use it to solve a problem in real time
Access control from the edge to the cloud
- Things, Data and Commands (See Resources)
- Configurable (Actors)
- Business rules
- Actions
- Integration with tenants and existing systems.
Devices (M2M)
- Devices Protocols
- Communication Protocols
- Centralized management
- Edge intelligence
- Monitoring
Cloud based & multitenancy
- multitenant
- cluster of services replicated , monitored and scalable on-demand:
- Identity management
- Publish subscriber queuing
- Real time streaming
- Rule engine
- Big data speed layer
- Bid data real time data view
- Memory caching
- Scheduled jobs
- Maps
- Location information services
- Orchestration
- Deployment and version control
- Troubleshoot
Reasoning in real time
Extensible API
- Things type, Observations type and Commands
- Observation enrichment
- Placeholders
- M2M Bridge
Location Systems
- GIS
- Proximity area
- Positioning systems
Acting in real time
Applications evolution
Reference data
Example of what developers think Stay of IoT
AMTech IoT services
- A service refers to a set of related software functionalities that can be reused for different purposes, together with the policies that should control its usage
Resources semantic
- Restful and NOSQL real-time views; for querying and managing resources semantic; structured according to the RDF and represented leveraging linked data and Json-ld.
- Supports resources types version control with publication policies
Real Time View
- Restful and NOSQL real-time view for querying and managing resources instances; structured according to the RDF and represented leveraging linked data and Json-ld.
- Support instances enrichment, allowing insert new properties and values after semantic been extended.
Identity access management
- Manages the identity and information of users that describes the operations and access control over IoT resources, offering a secure multi-tenancy and protected IoT real time view data hosting.
- actors for grouping access policies
- access control based on resource’s type, tenant and user id
Sensor Network
- Restful publish / subscribe message broker and event processing network that allows subscribers and publishers to exchange observations classified by topics or/and observations types; uses linked data to represent observations semantic and MQTT topics to express the physical organization of sensors network.
Real Time Intelligence
- Query engine for discovering new knowledge emerging from associating real time observations with Things real time views, bringing into account time, spatial location and observed properties.
Location-aware
- Set of geometric and mathematical algorithms responsible for the location, organization and spatial relation between Things. It leverages geolocation/GPS or WiFi positioning system and proximity location technologies to guarantee that observations and things get enriched with accurate location.
Rules and Actions Execution
- A distributed computation framework that offers the queuing and stream processing capabilities for computing IoT real-time views; by processing observations and executing pre-configured observers and actions.
Push notifications
- A service for sending asynchronous notifications using a private channel, leveraging access control policies, sensor network infrastructure and HTML5 websockets.
Time-aware
- Maintains a set of copies of observed properties per Thing; control by frequency and amount of copies; allows real time view data size and expiration time configuration.
Scheduler Fault-tolerant distributed
- is used to schedule tasks and orchestrate the executions of business rules actions.
Generating code and data binding
- For the creation and consumption of error free resources configuration information.
Observation Enrichment
- producer, access control topics and things relation can be configured to be enriched with:
- geospatial information like country, city...
- user content, user id, tenant…
- EPC information company prefix, product code..
- Other M2MBridge plugins placeholders
Edge intelligence and M2M Bridge
- Configurable edge intelligence
- Automatic deployment with autodiscovering
- Integrated devices and M2M protocols (data and commands from/to devices)
- SNMP, LLRP, iBeacon, eddystone, PLC, GPIO, EPC, NFC, ODB-II, OPC-UA, Modbus, BLE GATT
- Device-to-device or device-to-cloud communications (Mesh network, aggregation)
- Digi Mesh, wifi, classic Bluetooth, BLE, ZigBee, RFID, Wi-Fi, RS485/232
- Remote and centralized control of IoT devices and gateways.
- Common functionality and host the execution of the protocols
- Network failure detection and recovery
- Get centralized configuration information at startup and real-time modification
- Access control policies to manager observations production and consumption
Creator User Experience (PaaS configuration)
- define and manage resources type (semantic)
- configure observation production
- configure activities
- debug & test activities
- deploy activities
SaaS configuration user experience
- user experience to configure IoT SaaS from Activities defined using AMTech creator experience
- access to things and notifications based on follower roles, tenant and user
- scale when new things, sensors and business rule get deployed
Cloud App Marketplace
- offers the tools for:
- developers to quicker and simpler deliver IoT solutions to market.
- businesses to discover new IoT solutions that extend your business.
Electronic Product Code
- encoding and decoding:
- SGTIN-96, SGTIN-198, SSCC-96, SGLN-96, SGLN-195, GRAI-96, GRAI-170, GSRN-96, GSRNP-96, GDTI-96, GDTI-174, GID-96.
Connectivity
IoT mesh network implementing edge intelligence industrial protocol and connecting edge components from the sensor to the cloud and back including edge logic
- Digi Mesh PTMP 9 miles
- Digi Mesh PTMP 25 miles
- PTMP repeater 100 miles
Sensors design
- Components to detect/collect requires properties
- Connection and industrial protocol integrated to the platform and IoT semantic.
- Required IP Ratings: (Ingress Protection or International Protection)
- Form factor
- Power supply
