Download as PDF, PPTX
![the UNCAP example
channel
stream
Timestamp
POSIT’N
Timestamp
MEASURM’S
Timestamp
ALARMS
Payload
"properties": {
"blood_glucose": {
"allOf": [
{
"$ref": "#/definitions/unit_value”
},
{
"properties": {
"unit": {
"enum": [
"mg/dL",
"mmol/L”
]
}
}
}
]
}
i.e. location stream
x,y,z channels](https://image.slidesharecdn.com/20161212wf-iottutorial-lowres-161213034337/75/Tutorial-at-IEEE-WF-IOT-Dec-2016-Five-Years-of-Research-and-Innovation-Experience-in-IoT-42-2048.jpg)
![store significant data…
Payload
"properties": {
"blood_glucose": {
"allOf": [
{
"$ref": "#/definitions/unit_value”
},
{
"properties": {
"unit": {
"enum": [
"mg/dL",
"mmol/L”
]
}
}
}
]
}
“literate”
(relevant plugins / libraries)
Raptorbox IoT
Data Broker
higher processing but…
save storage space
facilitate interpretation
save network use
“all blood glucose levels above a threshold”](https://image.slidesharecdn.com/20161212wf-iottutorial-lowres-161213034337/75/Tutorial-at-IEEE-WF-IOT-Dec-2016-Five-Years-of-Research-and-Innovation-Experience-in-IoT-58-2048.jpg)
![the UNCAP example
channel
stream
Timestamp
POSIT’N
Timestamp
MEASURM’S
Timestamp
ALARMS
Payload
"properties": {
"blood_glucose": {
"allOf": [
{
"$ref": "#/definitions/unit_value”
},
{
"properties": {
"unit": {
"enum": [
"mg/dL",
"mmol/L”
]
}
}
}
]
}
i.e. location stream
x,y,z channels](https://image.slidesharecdn.com/20161212wf-iottutorial-lowres-161213034337/75/Tutorial-at-IEEE-WF-IOT-Dec-2016-Five-Years-of-Research-and-Innovation-Experience-in-IoT-103-2048.jpg)
Uploaded byRaffaele Giaffreda
Tutorial at IEEE WF-IOT Dec. 2016 - Five Years of Research and Innovation Experience in IoT
The document discusses five years of research and innovation in the Internet of Things (IoT), highlighting key challenges and opportunities in turning research into practical solutions for business. It outlines the complexities of IoT integration, the importance of energy-efficient communication protocols, and the significance of platforms for application development in the IoT ecosystem. Additionally, it emphasizes the need for interdisciplinary collaboration between technologists and domain experts to address real-world applications and improve overall IoT functionality.
More Related Content
Similar to Tutorial at IEEE WF-IOT Dec. 2016 - Five Years of Research and Innovation Experience in IoT
Tutorial at IEEE WF-IOT Dec. 2016 - Five Years of Research and Innovation Experience in IoT
- 1.
- 2.
- 3.
- 4. • Chief IoT Scientist - CREATE-NET, Italy •20yrs experience in the telecom domain: BT and Telecom Italia • large projects, patent holder, public speaking • >5mEur funding acquisition • IEEE IoT newsletter editor-in-chief • MSc, Telecoms Engineering, University College London, U. of London • MSc, Electronic Engineering, Optical Telecommunication Systems, Politecnico di Torino 4 About me
- 7.
- 8.
- 9.
- 10.
- 11.
- 13.
- 14.
- 15.
- 16.
- 17. Constrained Nodes (IETF classification) Data (RAM) Code(ROM) Class 0 (Too constrained) << 10 KB << 100 KB Class 1 (Quite constrained) ~ 10 KB ~ 100 KB Class 2 (Not so constrained) ~ 50 KB ~ 250 KB courtesy of Mattia Antonini
- 18. IoCT OSes Features • Real-Time Os •Full IPv6 Stack • Multi-hops support • Multitasking • Power Management • Application-agnostic RTOS Kernel I/O Management Task Management Memory Management Interrupt & Event Handling Timer Management Synchronizati on & Communicatio n courtesy of Mattia Antonini
- 19.
- 20.
- 21.
- 22.
- 23.
- 24. The physics… • Radio signal attenuation proportional to frequency • Longer wavelength, longer range •Sub-1GHz band • robust and reliable communication with low-power budgets • bandwidth limitation • Modulation techniques • (U)NB vs. Spread Spectrum
- 25. wireless technologies for M2M “horses for courses…” LoRa™ Alliance WhitePaper © Mobile Experts, 2015 BLE – Bluetooth Low Energy LPWA – Low Power Wide Area RPMA – Random Phase Multiple Access indoor coverage, low cost, long battery life and large number of devices (>10K per AP)
- 26. trendy comms for IoT: LPWANs • LoRa(non managed) • SIGFOX (managed services) • Vodafone and Huawei (NB-IOT – 3GPP LTE standard)
- 27.
- 28.
- 29.
- 30. LoRa basic features • 868 MHz •125 KHz channel • 250 bps – typical • non-managed • star topology, thousands of nodes / gateway • LoRaWAN L2 protocol for networking (security, duplication etc.)
- 31. SIGFOX • UNB – 100 Hz •12 bytes per message • 140 messages per day max (ISM bands regulation, 1% duty cycle) • 100 bps • 2-way communication • very high power efficiency • 1 Eur / year
- 32. NB-IoT • the telco operators’ bet • 3GPP LTE •announcement • piggybacking existing infrastructure • low-cost to deploy, wide coverage, but • subscription based, quality league • Prototypes exist but no commercial hardware / deployments yet
- 33. 5G anyone? • issue of latency • tactile internet scenarios •bandwidth… • but…not only radio technologies
- 34. • 5G is not just about speed and more flexible networks! •5G is about having a better mobile network that can lead to improved/futuristic application smart scenarios • 5G will in fact leverage on: • Virtualised/programmablehigh speed dynamic access & transport networks • Decreased latency thanks to Mobile Edge/Fog computing (Tactile Internet, Enhanced Virtual Reality, Telerobotics,…) • Secure and interoperable IoT infrastructures for a huge variety of Smart Scenarios (Industry 4.0, Smart Cities, Connected Cars,…) things to remember about 5G… 34
- 35. RESEARCH CHALLENGES? • cheaper • energy efficient •longer range • higher bandwidth • low latency • … • some little extras (positioning)
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. the UNCAP example channel stream Timestamp POSIT’N Timestamp MEASURM’S Timestamp ALARMS Payload "properties": { "blood_glucose": { "allOf":[ { "$ref": "#/definitions/unit_value” }, { "properties": { "unit": { "enum": [ "mg/dL", "mmol/L” ] } } } ] } i.e. location stream x,y,z channels
- 43.
- 44.
- 45. what is a platform? • a comprehensive (software) offer of services that puts together a mix of what presented so far • main purpose for IoTplatforms is to provide more or less automated features that help easily create applications that exploit data for a purpose
- 46.
- 47.
- 48.
- 49.
- 50. Facebook Platform openAPI made it possible for third-party developers to create applications. src: http://www.digitaltrends.com/features/the-history-of-social-networking/ AppleStore Android GooglePlay Software advances (Hardware enablers) touch screens tablets / smartphones mobile computing Rather than offering a comprehensive social networking experience like the now-defunct Myspace and the struggling Google+, they instead specialize in a specific kind of interaction service that involves the sharing of public images (Instagram), the private sharing of images sharing (Snapchat), augmented reality (Foursquare), and location- based matchmaking (Tinder). People essentially use the various services in conjunction with other platforms to build a comprehensive, digital identity. what is the target? ease of use for its intended audience!!! ability to tinker and personalise it!!!! contextual background awareness…
- 51. a more comprehensive picture • IoT and Cloud (infrastructure) •Industrial IoT (specific segment) • Cognitive IoT (data) • Secure IoT SENSORS PLATF’S EMBED’D SYSTEMS COMMS PROTOC’S DATA STRUCT’S IoT & Cloud Secure IoT Industrial IoT Cognitive IoT
- 52.
- 53. Improve IoT through Cloud • constrained devices •limited processing power • limited battery power • limited networking • limited storage • limited support for scalable applications • advances in cloud computing (edge / fog computing, containers, micro- services) constrained to unconstrained offload, separating concerns…
- 54.
- 55. Integration API Raptorbox Problem addressed • Challenges for integration of IoT devices into existing product/service portfolio: •Complexity of integration of heterogeneous IoT devices into an existing infrastructure: • Interaction with IoT devices (device identification, protocol handling) • Security: secure communication, device and data access control • Scalability: • From few devices in trial phase to massive deployment of IoT connected devices • How to perform rapid prototyping to address fast business and tech validation cycles and fast delivery Service Bus Enterprise Systems Device integration and management made eas in a secure, scalable, configurable way courtesy of Fabio Antonelli
- 56. Our solution u Device Virtualization: u Common Device Modeling (“Web of Things” paradigm) uIoT Message Brokering: u Scalability by design u Multiprotocol support (http/https, MQTT, JMS, AMQP) u Data chaching for real-time event processing and querying u Configure your Business Logic for Rapid IoT Application Prototyping (Data and events workflow Editor) u Flexible Access Control & Authorization (ACLs) for devices and users u Secure Communication and Interaction with devices u Easy Integration via APIs exposing all available capabilties courtesy of Fabio Antonelli
- 57. Integration API Raptorbox Service Bus Enterprise Systems the Raptorbox IoTData Broker COMMUNICATIONS SENSING GOOD DATA VALUE GENERATION ROUTING FILTERING the more I understand the data, the better value I can provide… AGGREGATING INTERPRETING VALUE PROCESSING low high low high
- 58. store significant data… Payload "properties": { "blood_glucose": { "allOf":[ { "$ref": "#/definitions/unit_value” }, { "properties": { "unit": { "enum": [ "mg/dL", "mmol/L” ] } } } ] } “literate” (relevant plugins / libraries) Raptorbox IoT Data Broker higher processing but… save storage space facilitate interpretation save network use “all blood glucose levels above a threshold”
- 59. Raptorbox target • system integrators mainly •focus on core service provisioning competences while exploiting interoperable platform for enriching those with interoperable IoT data harvesting • examples: SMEs digitalisation support, smart cities, e-health Integration API Raptorbox Service Bus Enterprise Systems
- 60.
- 61.
- 62. WAZIUP target • African community of developers • focus on core competences while exploiting ready-to-use open-source tools and components to cater for the needs of African businesses •examples: fish farming, precision agriculture, cattle rustling etc. App source code data processing & analytics IoT PF IoT sensors
- 63.
- 64.
- 65.
- 67.
- 68.
- 69. recent news… • software industry • appliance / electronics •“SAP and Bosch team up on Internet of Things” • … The technology, for example, allows a production system to select the torque for each screwdriver's task, increasing efficiency ... • wow...what does it take to tighten a screw? • how much torque to apply when? what about replacing the screw driver? what about ensuring it is the right one for the type of screws? • sensing system and an actuator...plus contextual knowledge about type of screw, screw pitch and size, material (pre- sales)...data collection, interpretation (after-sales) enhance a particular task integration, know-how
- 70.
- 71.
- 72. all well, but… • need reliable technology • sensing and communications •security, dependability, servitization • (pre-sales / after-sales) • need performance • data-processing and edge cloud • need competences (choice, integration, deployment) • infrastructure • choice of technologies • interface between standards • middleware • flexible architectures • interface between standards • services and applications • what knowledge do we want to extract from data? • interface between standards • need technologists + domain experts, working side by side enhance a particular task
- 73. need reliable technology • (sensing) – what to sense, size, durability, etc. •securely getting data out of sensors to the applications • what options for your production plant, assembly line, deployment environment… • 5G is a key enabler • reliable communications / protocols • energy efficiency • short round-trip delays • NB-IoT vs. Sigfox vs. LoRa
- 74.
- 75. need competences • know-how! • infrastructure •choice of technologies • interface between standards • middleware • flexible architectures • interface between standards • services and applications • domain experts + technologists • solution design integration, know-how
- 77. Advantages of 4th industrial revolution • digitalisationof production process • digitalisation of product • monitoring during and after production • azienda manifatturiera acquisirà componente da software house • “just in time” production – with management of stock, stores, production value chain • products personalisation • reduced production and final product costs – competition • new business models tied to servitisation
- 78.
- 79.
- 80.
- 81. TED Talk on AI • https://www.ted.com/talks/sam_harris_can_we_build_ai_without_lo sing_control_over_it • https://www.ted.com/talks/jeremy_howard_the_wonderful_and_ter rifying_implications_of_computers_that_can_learn •dave evans https://youtu.be/UQi9B7yB5dM (beginning of it size of sensing + computing) phone processing power in a blood red-cell… • deep learning: computer can see (10min 30) also they see what we cannot (heartrate from image...), computer can read
- 82.
- 84. Extracting knowledge from data – domain expert modeling… • many bespoke machine-learning applications exist •however, still substantial overhead needed • smart-agriculture example • domain expert models need to assist machine learning experts to help them design algorithms that, based on collected data, can actuate according to model expectations • sometimes models need to be created through observation (lengthy process) • in both cases, a lot of validation data is needed to train and tweak algorithms • no wide applicability, no general purpose machine learning… • experience from iCore EU collaborative project
- 85.
- 86. Illustration by JustinMetz applicable in all scenarios exposing highly structured data the emergence of unsupervised learning… (+ advances in edge cloud computing)
- 87.
- 88.
- 89.
- 90. many levels of security • data encryption at transmission level • data encryption at storage level •policy-based access control • anonymise data • etc. • IoT and blockchains…(enable secure and logged exchange of IoT messages)
- 91. Added Value for IoT • Trust and Reputation of IoT devices: • Non-RepudiableDevice Identity • Security enforcement at the edge • Secure Traceability of Transactions and of Information: • in financial transactions, supply chains, and other processes involving involving IoT devices • transparency, auditability without the need to leverage on 3rd party trusted entities • Make consumer data more private • More Resiliency: • No single point of failure • IoT devices can autonomously interact with humans and other IoT devices: • including capabilities to perform automatic payments/value exchange tracking (digital currencies) courtesy of Fabio Antonelli
- 92.
- 93.
- 94.
- 95.
- 96. Overall architecture ! ! !! ! !! ! ! ! ! ! !UNCAP!BOX! ! ! ! ! ! User’s!clinical!data! ! ! ! ! ! ! ! ! ! ! ! UNCAP!BOX!core! (incl.!seman9c!proxy)! UNCAP!end> user!end!point! UNCAP! caregivers!end! point! Smart!flooring! –!based! localisa9on! Biometric! sensors! Camera!based! localisa9on! ZigBee! localisa9on! Other…! Local!DB! (configura9on)! Wearable! sensors! Other!…! Interoperable!channels!(HL7!/!CDA!/! SensorThings)!over!secure!connec9onx! UNCAP!services! in!the!cloud! Outer&world& Value!added!services! from!3°!par9es! Public!health!IT!services! (based!on!standards)! Proprietary!! data!format! Loca9on! Connectors! Sensor! Connectors! Home&or&& protected&& environment& Loca9on!informa9on!!!(users!&objects)! ! ! ! ! ! ! ! ! ! ! ! Interoperable! channels!! Standardised Interfacing to wearables / monitoring Common services across pilots Applications Monitoring
- 97. The IoT Interoperability Problem • Technical Interoperability •ability to communicate between objects or between objects and apps • Need for a “Multi-protocol IoT hub” • Syntactical Interoperability • about data formats, i.e. xml, html, json • Semantic Interoperability • to do with resource annotation, query and discovery (i.e. semantic-based) • ontologieshelp with common vocabulary and knowledge sharing
- 98. The SMEs real world problem… • “semantic what?” • understand scalability, RESTFUL API exposed services •understand the need to implement access control and safe storage • use of IoT Data Broker cloud-based platform
- 99.
- 100. Secure, Permanent Storage IoT Data Broker (cloud) data sources data sources data sources data sources data sources data sources IoT Data Broker (gateway) IoTdata (direct) IoT data (via gateway) CEP, data processing access control MQTT, STOMP, CoAP, REST, WebSockets OAUTH eHealth scenario integration Open mHealth standard Offline functionality validated for DB integration (CHINO) Node-red based rapid prototyping for business logic deployment on both, large and small scale
- 101. Integration API Raptorbox Problem addressed • Challenges for integration of IoT devices into existing product/service portfolio: •Complexity of integration of heterogeneous IoT devices into an existing infrastructure: • Interaction with IoT devices (device identification, protocol handling) • Security: secure communication, device and data access control • Scalability: • From few devices in trial phase to massive deployment of IoT connected devices • How to perform rapid prototyping to address fast business and tech validation cycles and fast delivery Service Bus Enterprise Systems Device integration and management made easy, in a secure, scalable, configurable way
- 102. applying the results of a project to solve a concrete problemchannel stream Timestamp POSIT’N Timestamp MEASURM’S Timestamp ALARMS i.e. location stream x,y,z channels • Open mHealthcompliance • “payload” to carry JSON structures, but… • Value is in someone else’s hands • Decided to accommodate more detailed structures • parsing, searching, filtering by thresholds etc.
- 103. the UNCAP example channel stream Timestamp POSIT’N Timestamp MEASURM’S Timestamp ALARMS Payload "properties": { "blood_glucose": { "allOf":[ { "$ref": "#/definitions/unit_value” }, { "properties": { "unit": { "enum": [ "mg/dL", "mmol/L” ] } } } ] } i.e. location stream x,y,z channels
- 104. Integration API Raptorbox Service Bus Enterprise Systems the Raptorbox IoTData Broker COMMUNICATIONS SENSING GOOD DATA VALUE GENERATION ROUTING FILTERING the more I understand the data, the better value I can provide… AGGREGATING INTERPRETING VALUE PROCESSING low high low high
- 105.
- 106. Securing access to datastreams IoT Data Brokerdata sources data sources data sources IoTdata upload usr_ID sess_KEY data TYPE, VALUE, etc. User Mgmt sess_KEY LOGIN (usr_ID, pwd) sess_KEY UNCAP Webapp usr_ID, nok_ID, Dr1_ID, Dr2_ID sess_KEY ßà usr_ID ? 1. 2. 3. CREATE (sess_KEY ßà usr_ID) 4. 5. 6. 7. usr_ID nok_ID Dr1_ID Dr2_ID PUB/SUB CHANNELS 8.
- 107.
- 108.
- 109.
- 110. where is the IoT? • no broad set of applications encompassing “one IoT” • with mobile phones and personal computers it was easier •IoT devices very diverse, yet we tend to blur boundaries • losing ability to tackle separately different markets DISCLAIMER: no business expert but have matured insights into the business of IoT that might be useful to share
- 111.
- 112.
- 113. Return on investment (ROI) • EXAMPLE 1 • I spend a $ to buy a bottle of water because I am thirsty •the (immediate) need = I am thirsty • who benefits? = me (private) • willingness to pay for it = I need it badly • when do I benefit = as soon as I get my bottle • I make an (private) investment, the benefit is immediate • VERY SHORT CYCLE, TANGIBLE, UNAMBIGUOUS, CONCRETE B2C • EXAMPLE 1.b • I spend $ to buy an iPhone • the (immediate) need = I need a cool device • who benefits? = me (private) • willingness to pay for it = can do cool things with it • when do I benefit = as soon as I get it • I make an (private) investment, the benefit is immediate • VERY SHORT CYCLE, TANGIBLE, UNAMBIGUOUS, CONCRETE location is key – booth next to a fountain? “coolness” is key – no “cheap look” please… IDENTIFY YOUR POTENTIAL MARKET TARGET…
- 114. Return on investment (ROI) • EXAMPLE 2 • I spend money to make my house energy efficient •the (not so immediate) need = I need to save money on my energy bills • the (good for a common cause) need = I need to make my life more sustainable • who benefits? = me (private), the environment • willingness to pay for it = I need it (not so badly), the environment needs it (not so badly) • TIME DIMENSION • when do I benefit = after I paid the bills for needed equipment with the money I saved • I make an investment, the benefit might be for someone else or not materialise until later • LONG-ISH CYCLE, TANGIBLE, UNAMBIGUOUS, CONCRETE BUT… B2G2CB2C • EXAMPLE 2.b • smart-lighting • the (not so immediate) need = I need to save money on my energy bills • the (good for a common cause) need = I need to make my city more sustainable • who benefits? = the environment • willingness to pay for it = the city balance sheet needs it (in a couple of years, not so badly), the environment needs it (not so badly) • TIME DIMENSION • when do I benefit = after I paid the bills for needed equipment with the money I saved • I make an investment, the benefit might be for someone else or materialise when it is too late • LONG-ISH CYCLE, TANGIBLE, UNAMBIGUOUS, CONCRETE BUT…
- 115. Return on investment (ROI) • EXAMPLE 3 • I have a business and I want to digitiliseit • spend money to make my production process more modern and efficient… • the (not so immediate) need = I need to gain competitive advantage • the (good for a common cause) need = I need to gain insights into my business operations • who benefits? = my biz (private) • willingness to pay for it = I need it (not so badly), long-term gains • TIME DIMENSION • when do I benefit = as soon as I am in a position to transform gathered data into differential advantage that drives more customers to buy what I sell or reduces operating costs etc. • I make an investment, the benefit is not immediate and depends on a proper strategy • LONG CYCLE, UNTANGIBLE B2B2C
- 116. The value (and diversity) of data • the importance of bespoke modeling – multi-disciplinarityand adjacent domain experts interactions • cycles of learning (modeling) before I can be predictive and even longer before I can be prescriptive… • sensing and influence on results... • IS IT WORTH IT? Example: motors manufacturing biz vibration, current, torque MTBF: 60000 hours (!) Raccoltadati Descriptive what happened? Diagnostic why did it happen? Predictive what will happen? Preventive what should I do? Decision Actuation Decision support Decision automation human input requiredanalytics the ROI CYCLE
- 117.
- 118.
- 119. WHO we solve the problems for and WHY • WHO • application developers (rapid prototyping) •system integrators • system admin of eHealth • API framework managers u WHY u rapid development saves costs & time u agility u easy integration u hide complexity, Web-based APIs 9
- 120. key message – who is your target? • Cisco (Jasper), IBM (Bluemix), GE (Predix) … •IoTango, Trilogis etc. • propose a reference framework for validation of how to break-down a complex problem space into more “palatable” “mouth-sized” chunks
- 121.
- 122.
- 123.