How To Create An Internet Of Things (Iot) Platform For A Smartwatch And Other Devices

Transcription

1 Jong-Tae Park Center for U- Convergence Network, Kyungpook National University, Korea

2 IoT Devices IoT Devices Fitbit Smart Watch (Pebble, Samsung, Apple) Smart Slipper (24eight) Hapifork (Hapilabs) Smart Glass/Lens (Google) Fiix (Conventis) Smart Pills (Proteus) GlowCaps (Vitality) Smart Seating/Bed/ 2

3 (Million) Global Forecast of Wearable Computing Devices 3

4 IoT Platforms Apple HealthKit (2014.6) Health data sharing platform for ios8 Partnership with Mayo Clinic and Epic Systems HealthKit data is limited to Apple specified types Google Fit (2014.6) Cloud-based fitness data sharing platform Provide cross-platform APIs for developer to keep track of customers fitness goals Samsung SAMI (2014.5) Cloud-based healthcare platform to store and analyzing healthcare data Simband: platform for collecting and analyzing biophysical data for preventative health 4

5 IoT Situation: Lack of Standardized Data in Platform! IoT Service Most platforms are using proprietary data format and network infrastructure, as a consequence, service interoperability is a serious problem. IoT Platform Standard!! ISO/IEEE PHD Model Standard Wins! 5

6 Current IoT Industry Consortium Members Intel, Samsung, CISCO, GE Software, 71 others. Qualcomm, LG, Microsoft, Sony, Panasonic, 151 others. Nest(Google), Frees cale, ARM, Samsung, Silicon Labs, 134 others. ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC, 222 others. Application HTTP, CoAP Bus Attachment, AllJoyn Message, Routing Node, AllJoyn Transport HTTP, CoAP, MQTT Transport TCP/UDP TCP/UDP TDP/UDP TCP/UDP Network IPv4/IPv6 IPv4/IPv6 6LoWPAN(IPv6) IPv4/IPv6(6LoWPAN) Data Link Physical (Bluetooth, WiFi, Zigbee, Z-Wave, ANT, 3G/4G, etc.) 6

7 onem2m Standard Network Configuration 6LoWPAN, ZigBee IP, CoAP / DTLS Cellular Web Applications HTTP / TLS Lightweight M2M CoAP / DTLS AAA, Admin Billing M2M Devices Backend Private or Public Cloud 7

8 IoT Service Framework Context Awareness Open Device API Open Service API Provider Application Wearable Device Management M2M Area Network M2M Gateway M2M Core M2M SC Diet & Wellness Monitoring Home Device Management Server Platform Family Care Application Device Domain Network Domain Application Domain 8

9 IoT-based Network Extension for Continua Alliance Personal Health Device Thermometer Aggregation Manager IoT Platform Health Records Pulse Oximeter Pulse/ Blood Pressure IoT Wearable Device Smart Band (Fitbit) Smart Watch (Apple Watch, Galaxy Gear) Smart Patch (CGM-Dexcom) Personal Area Network (PAN) Interface Which standard PAN Interface?? IEEE CoAP App Wide Area Network (WAN) Interface Which standard WAN Interface?? IEEE CoAP Which standard interface: IHE + onem2m Health Record Network (HRN) Interface Web Service (WS) Interface EHR PHR Web Client 9

10 Strategy of Supporting Data, Service, Communication Interoperability Data Interoperability Support ISO PHD Data Model Service Interoperability Support ISO Object Access, Event-Report Service Communication Interoperability Support onem2m Transport with Extension CoAP, HTTP/S, MQTT/AMQP, Others Interoperability with Legacy HIS Support IEEE DIM and HL7 RIM Conversion Support Conversion between ISO Object Access Service and IHE-PCD01 Object Service Seamless Transport Integration with WS and CoAP 10

11 IoT Convergence Architecture XML HTTP TLS TCP IPv6 Internet Constrained Environment Secure Efficient Reliable Extensible Simple Platform Independent DIM* CoAP/SOAP** DTLS/TLS UDP/TCP 6LoWPAN IoT Network * DIM: Domain Information Model **CoAP: Constrained Application Protocol SOAP: Simple Object Access Protocol 11

12 Standard-based IoT Convergence Architecture Application CoAP/HTTP ISO/IEEE DIM ISO/IEEE DIM ISO/IEEE Service Model DTLS/TLS UDP/TCP ISO/IEEE (ROSE/ACSE) CoAP/HTTP/SOAP DTLS/TLS UDP/TCP IPv4/IPv6 (IETF 6LoWPAN) 3G/4G, IEEE IEEE Bluetooth/Zigbee (No IP) IEEE IEEE IPv4/IPv6 (IETF 6LoWPAN) 3G/4G, IEEE IEEE

13 Open Platform : Introduction OHP-M2M Platform is an open source implementation of the in ternational healthcare standards to develop IoT healthcare service. It is based on onem2m and ISO/IEEE DIM standard. The platform provides a basic templates for nine medical devices that are implemented so far. These are medication monitor, stren gth fitness equipment, cardiovascular monitor, blood pressure mo nitor, pulse oximeter monitor, body composition monitor, therm ometer, weighing scale and glucose meter. The main objective of the project is to provide a platform for the users to manage and use medical devices in the IoT environment conveniently. 13

14 Features of IoT-based Open Platform Security: It can be benefited from strong security of HTTPS, TLS, and IPSec Simplicity: It is using CoAP instead of complex OSI ACSE(Association Control Service Element). So it is light, fast and simple. Seamless Application Development on Data: New healthcare services and applications can be seamlessly built without dependence on data format. Lossless Service Integration: Since it is using CoAP, it can be seamlessly and easily integrated with HTTP-based healthcare App. Mobility Support: It can effectively support device mobility, including healthcare apps of smart phone. 14

15 OHP-M2M Service Configuration ISO/IEEE DIM CoAP Application ISO/IEEE DIM CoAP FHIR/ PCD-01 HTTP Application FHIR/ PCD-01 HTTP UDP Transport UDP TCP Transport TCP 6LowPAN BLE IP PHY/MAC 6LowPAN BLE IPv4 WiFi, 3G/4G IP PHY/MAC IPv4 WiFi, 3G/4G Device Gateway Server 15

16 OHP-M2M Project Open Source (GitHub) Community Web Potal Installation Guideline(Youtube) 16

17 OHP-M2M Open Source Supports IEEE xx specializations based on OM2M platform: medication monitor, strength fitness equipment, cardiovascular monitor, blood pressure monitor, pulse oximeter monitor, body composition monitor, thermometer, weighing scale and glucose meter. Supports IEEE Service Model between healthcare devices and OHP-M2M platform based on CoAP. Supports IEEE XX DIM(Domain Information Model) using XML representation. Provide android-based and Raspberry Pi-based application communicated with OM2M platform. 17

18 Contact Point Jong-Tae Park Center for U- Convergence Network (CUCN) Kyungpook National University, Korea 18

19

20 Requirements for Open IoT Platform System Development Separation of Back-end Services and Front-End Application Flexible Composition of System Components Incremental Deployment of Platform Service Avoid Vendor Lock-in Support of Standard Communication Interface Maintainability of Bug Fixes and New Releases Reacting to Users Complaints, Applying Changes Simple and Precise Service Interface Seamless Integration with Other Systems 20