1. oneM2M based IoT Platform Development of SK Telecom
Group Name: TP
Source: Hongbeom Ahn, SK Telecom,
Meeting Date:
Agenda Item: Technical Plenary Interim

2. Messages What SK Telecom has done? What’s Next? Lesson Learned
oneM2M-based Infrastructure Node
How to Support oneM2M Developers
How to Build Eco-System
What’s Next?
Interworking with other Technologies
Big-Data Support
Lesson Learned

3. oneM2M-based Infrastructure
What SK Telecom has done?
oneM2M-based Infrastructure
The First, oneM2M-based IoT Platform
Compliant with oneM2M release 1, announced in Jan 2015
Major Features
Device and Application Registration
Data Management
Device Management
Location Management
Group Management
Notification System
Security

4. How to Support oneM2M Developers
What SK Telecom has done?
How to Support oneM2M Developers
oneM2M Protocol is not complicated, but easy!
Starter Kit (open to everyone through Github ,
Node.js-based Simulators : Easily understandable how oneM2M system is working
Simple explanation (only Korean ) with selected features
SK Telecom
Server
Node.js
Node.js
Device
(ASN-CSE)
(IN-CSE)
Application
(ADN-AE)
Mca
(HTTP | MQTT)
Mca
(HTTP)
Registration
Data Upload
Device Management Configuration
Data Retrieve
Device Management Execution

5. How to Support oneM2M Developers
What SK Telecom has done?
How to Support oneM2M Developers
Collaboration with Open Source Hardware(s) and Web-based Application Builder (no-coding for application)
PC / Laptop
Mobile
Application Side
(North-bound)
ThingPlugTM
BBB
Raspberry
Edison
mBed
Arduino
(South-bound)
Device Side
* Under development

6. How to Build Eco-System
What SK Telecom has done?
How to Build Eco-System
Lower the Barrier to Entry for Developers and Vendors
Materials - Book
Events - Hackathon
Let the Developers and vendors understand SKT’s ThingPlug plus oneM2M Specifications
IoT Services development competition (not oneM2M-based yet)

7. Interworking with other Technologies
What’s Next?
Interworking with other Technologies
Seeking technologies to complement ’ThingPlug’
LoRaWAN covers L1, L2 and ThingPlug as an oneM2M API Gateway to exposure API(s) for Data and Device management feature(s)
Network Layer

8. Interworking with other Technologies
What’s Next?
Interworking with other Technologies
Seeking technologies to complement ’ThingPlug’
Since oneM2M does not specify the interface between device(s) OIC (manufacturer-driven platform) can cover the local area network efficiently
Not standard-based, the standard is being specified
Platform Layer

9. What’s Next?
Big-Data Support
Support our platform users to easily search the hidden and worthwhile meaning from stored data in <container>
1) Easy Drag-Drop Data Picker
2) Display Chart and Transform the data to discover valuable meaning

10. Lesson Learned
Lesson Learned
oneM2M is appropriate as a core API-engine (Do not be afraid )
Application and Device Enablement are strongly required for easy access
An Official Certification Program is required
Cause oneM2M is standard …. Do not lose our core
More Developers, More Improvement
Developers Support materials from oneM2M TP
Complements to complicated specifications
Define the Strong Points and Specify it more quickly
Strong Cloud-oriented Solutions : Google Brillo , AWS-IoT, …
What are our strong points compared to the solutions?
Interworking with Network-Side (3GPP, 3GPP2, LPWAN, … more) also Platform-Side