Introduction to one M 2 M based Implementations

Introduction to one. M 2 M based Implementations including Open Source Activities Group Name: TP 18 Source: Jae. Seung Song, KETI (jssong@sejong. ac. kr) Meeting Date: 2015 -07 -20

one. M 2 M based Implementations There already multiple one. M 2 M based implementations OCEAN OM 2 M Io. TDM open. MTC one. MPOWER Open source These implementaitons show benefits of one. M 2 M to Io. T/M 2 M market Now these are becoming part of one. M 2 M echo system

OPEN SOURCE http: //open-iot. net/ocean

Introduction to OCEAN • What is OCEAN – – – • Licence policy – – • 3 -Clause BSD license policy OCEAN adapts IPR policy of the standards referred by open sources Current Members – • OCEAN (Open allian. CE for iot st. ANdard) established in Jan. 6 th, 2015 by KETI and Korea Government. The objective of OCEAN is to share open sources based on Io. T standards and to encourage co-working between its members The OCEAN supports early commercialize and vitalized ecosystem for Io. T 158 members (June 1 st, 2015) Open source – – The OCEAN is now providing open sources of one. M 2 Mbased Io. T platform called “Mobius“ and “&Cube“, and relevant documents. For download of the open source, users shoud join to OCEAN web site (http: //open-iot. net/ocean/download/). 4

Introduce OCEAN • Release Plan – – – Jan. 6 th, 2015: open. Mobius, &Cube (one. M 2 M candidate release) Jul. 15 th, 2015: open. Mobius, &Cube (one. M 2 M release 1) Dec. 1 st 2015 (expected): Interworking Proxy 2014 2015 2016 OCEAN (Open alliance for iot standard) IEEE … ~2015 Expand one. M 2 M 1. 0 2017 one. M 2 M 2. 0 IETF 2016~ Interworking Other Alliance 5

OPEN SOURCE Eclipse OM 2 M Open source standard-based Io. T platform eclipse. org/om 2 m-dev@eclipse. org

Eclipse OM 2 M platform • Open source project developed at the Eclipse Foundation. • Horizontal service platform for M 2 M interoperability • Compliant with Smart. M 2 M (April 2014) • Compliant with one. M 2 M (September 2015) • Restful API with generic set of service capabilities • Facilitate deployment of vertical applications • OSGI-based architecture extensible via plugins • Developed by research labs and companies

Eclipse OM 2 M building blocks OSGi framework Java Virtual Machine Operating System Hardware OM 2 M main building blocks Your plugin! Qo. S Additional Services Semantic TLS-PSK Security TLS LWM 2 M 6 Low. PAN KNX ZIGBEE OMA-DM Device Manage. Interworking Proxy MQTT COAP Comm. Binding HTTP CORE Generic Process.

Eclipse OM 2 M Project stats • Downloads : 602 • Contributors : 8

Eclipse OM 2 M roadmap • Eclipse OM 2 M Release 0. 8. 0 (April 2015) – Smart. M 2 M-based platform. • Eclipse OM 2 M Release 1. 0. 0 (September 2015) – – – – – one. M 2 M-based platform. IN, MN, ASN, and MN nodes support. Protocol-independent CORE module. HTTP and Co. AP communication bindings. XML and JSON resource formats. Interworking driver for simulated devices. Web interface for resource browsing and debugging. DAO persistence layer for SQL and NOSQL databases. Semantic capabilities. Android support.

OPEN SOURCE Io. TDM Daylight Open Source Project https: //wiki. opendaylight. org/view/Io. TDM: Main

Io. TDM from Daylight Project • The Io. TDM project is about developing a datacentric middleware • one. M 2 M compliant Io. T Data Broker (IOTDM) • Enable authorized applications to retrieve Io. T data uploaded by any device. • Project Creation Date: December 9 th, 2014 • Contributors: Cisco, ETRI, Echelon • Repository: https: //git. opendaylight. org/gerrit/iotdm

Io. TDM one. M 2 M Features • Implement Io. TDM as closely to the one. M 2 M specifications as possible. • Keep in mind that the specifications are still evolving. • Detailed information about what is supported from the one. M 2 M R 1 is available here (https: //wiki. opendaylight. org/images/5/55/Io. TDM_one. M 2 M_Featu res_Lithium. pdf) • RESTconf is also supported but it is a non-one. M 2 M standard method for accessing the tree. Bundles providing the API: odl-iotdm-onem 2 m • REST API commands include: onem 2 m-request-primitive for CRUDN • Examples of CRUDN calls and JSON formats are available here (https: //wiki. opendaylight. org/images/9/93/API_Calls_Examples. pdf)

www. openmtc. org © Matthias Heyde / Fraunhofer FOKUS Headline (open. MTC) – Release 4 Open Machine-Type Communication Subheadline

Open. MTC – M 2 M Session Control for Smart Cities Comprehensive M 2 M/Io. T platform More Information: www. openmtc. org Application Enablement Data Handling Connectivity Management Device Management Cloud-based Backend Platform Wide Area Network Application Open. MTC Gateway Sensor Actuator Field Domain � Enable the academia and industry to • Develop and validate domain-specific M 2 M/Io. T applications and services • Integrate various machine devices with operator networks � Comprehensive M 2 M/Io. T deployment • Over managed or unmanaged core � Intermediary layer • Between multiple managed domains • Service platforms, the operator network, and devices � Aligned with ETSI, one. M 2 M and OMA spec • Extensible to specific research needs • Configurable & high performance � The Open. MTC is non-open source Application Open. MTC Device © Fraunhofer FOKUS

Open. MTC key features Open. MTC Frontend Open. MTC Backend - Real-time data aggregation and processing - - Device management and discovery - - Open and standardized APIs to apps Support various deployment scenarios Scalable service layer Enable the development of M 2 M and H 2 H applications over a common platform - - - - Heterogeneous wireless access - - HTTP, Co. AP, MQTT pull, push, Pub/Sub, etc. Store & forward - 4 G, 3 G, 2 G and Wi. Fi Qo. S and mobility enforcement through 3 GPP EPC interfaces Android-based and Linux-based Embedded hardware (Arduino and Raspberry Pi) SDK and scenarios as reference implementation Scalable and Flexible M 2 M Communication Support open REST APIs Support different protocols and interaction models FS 20, Zig. Bee, Bluetooth, etc. Integrate multiple sensors Various gateways - - - Optimized for resource constrained devices Support different sensors and actuators - All-in-one complete M 2 M solution Could-enabled deployment Aligned with the standards like ETSI M 2 M and one. M 2 M All functional elements available individually Any functionality combination feasible due to software modularity Source code available

Open. MTC Roadmap Open. MTC Rel. 1 Open. MTC Rel. 3 - Generic communication - Remote management - Integration with Telco - Application Enablement Apr 2012 - Cloud-based Platform with horizontal scalability - Co. AP, Diameter and Web. Socket support - Polyglot platform: Java, Python, Ruby, Java. Script - Initial one. M 2 M support Nov 2013 Open. MTC Rel. 2 - Apr 2014 Integration with core network Reachability extensions Applications Extensions Security and Trust Nov 2014 Open. MTC Rel. 5 - One. M 2 M enhancement Integration with Open. Io. T Application management … … Nov 2015 Open. MTC Rel. 4 - One. M 2 M alignment Co. AP-DTLS IEC 61. 850 support Web. RTC Data Channel support - Android gateway - combined H 2 H & M 2 M services

one. MPOWER SDP Overview: Platform Overview • • • Inter. Digital’s one. MPOWERTM platform is a scalable and secure horizontal M 2 M/Io. T solution. It features a suite of services that span connectivity, device, data, and transaction management resulting in faster time-to-market, reduced complexity, and lower costs It is the most mature one. M 2 MTM standards-based platform in the industry today Note: one. M 2 MTM is a global standard that has defined and published a collection of comprehensive service layer solutions to accelerate the development and reuse of M 2 M/Io. T data and applications across diverse verticals, networks, and devices.

one. MPOWER SDP Overview: Feature Highlights

one. MPOWER SDP Overview: Platform Introduction