oneM2M-AllJoyn Interworking

Slides:

Advertisements

Similar presentations

Copyright © 2002, Peter Kriens, All Rights Reserved OSGi versus UPnP??? There is no "versus" here. OSGi is fully complimentary to UPnP. No overlap. UPnP.

Advertisements

Gateway Agent Product & Architecture

oneM2M and AllJoyn Interworking

Example for SCL resource usage according to ETSI TC M2M March 2011 Josef Blanz, Qualcomm Inc.

IoT in ODL Lionel Florit, Principal Engineer, ODL ID lflorit

WAWC’05 Enhancing Mobile Peer-To-Peer Environment with Neighborhood Information Arto Hämäläinen -

Adding More Value to Your ERP System Using Service-Oriented Architecture (SOA) Copyright © 2001 iWay Software 1 Information Builders.

Microsoft Ignite /16/2017 3:42 PM

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

请点击以下链接下载 WinHEC 的演讲材料 Download WinHEC presentations here:

Chapter 9: Troubleshooting and Repairing Networking.

22 September 2014 AllSeen Alliance 1 Lighting Service Framework (LSF)

Authors list to be completed.

On Management, Abstraction & Semantics

Authors list to be completed.

oneM2M-OIC Interworking Technical Comparison

Step by step approach Group Name: WG2

An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.

Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Updated:

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Meeting Date:

3GPP Rel-13 Interworking discussions

© 2015 Redbend – Confidential1 Aug 2015 ALLJOYN UPDATE SERVICE UPDATED CONTRIBUTION & DEMO PLAN.

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea Electronics Technology Institute (KETI) Meeting Date: ~24.

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

AllJoyn-Interworking Discussion Group Name: TP WG2 ARC Source: Josef Blanz, Phil Hawkes, Qualcomm Inc., Meeting Date:

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

D-Link Cloud Revolutions

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Connecting to the Network Introduction to Networking Concepts.

An introduction to oneM2M

3GPP Rel-13 Interworking discussions

LWM2M Interworking Group Name: Architecture

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.

3GPP SCEF Interworking Discussions

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

Wireless Mesh Networking or Peer to Peer Technology Andre Lukito – Johnsonsu – Wednesday, 9.

Status of Active Work Items Summary Group Name: TP Source: Roland Hechwartner, WPM Convenor Updated: source: TP_WPM R08-New_Work_Item_Status_Report.

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

Possible Solution of Interworking between oneM2M and OSGi

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:

What is oneM2M? 2 Covers: Requirements Architecture API specifications Security Interoperability Facilitate, implement and promote IoT.

Background Data Transfer

Developing an Implementation Framework for the Future Internet using the Y-Comm Architecture, SDN and NFV Glenford Mapp Associate Professor Middlesex University,

ONEM2M RELEASE 2: SETTING THE STANDARD FOR IOT INTEROPERABILITY

Resource subscription using DDS in oneM2M

Service Enabled AE (SAE)

Users and Administrators

WG2 - ARC TP#29 Status Report

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

oneM2M Service Layer Protocol Version Handling

3GPP Rel-13 Interworking discussions

WPM ad-hoc group report TP#25

WG2 - ARC TP#29 Status Report

Proximal IoT Interworking solution discussion

3GPP Interworking Abstraction

Ieva Juodelytė IT 3 kursas 4 grupė

Status of Active New Work Items

3GPP V2X Interworking Potential Impact

Users and Administrators

Presentation transcript:

oneM2M-AllJoyn Interworking Source: SeungMyeong Jeong (LG Electronics), Josef Blanz (Qualcomm)

Outline What is AllJoyn? oneM2M vs. AllJoyn Interworking Solution (TR)

App-to-app Communication Runs on local network (proximal network) Communicates Peer-to-Peer (Apps talk to Apps with help of AJ Routers) Enables Apps to advertise and discover each other

Service Flow Advertisement and discovery Session establishment/join One or more Interfaces: Methods (RPC) Properties (set, get) Signals Advertisement and discovery Advertisement by producer app and discovery by consumer app Session establishment/join Data Exchange via service objects Consumer calls methods, gets/sets properties provided by Producer Producer sends event notifications to Consumer(s) via signals

Service Types 1a. Base services : AllJoyn service framework pre-defined Examples: Notifications Control Panel Onboarding Configuration 1b. Purpose-specific service frameworks pre-defined in AllJoyn Examples: LSF, HAE 2. App-specific services : service objects that are implementing AllJoyn interfaces

oneM2M vs. AllJoyn oneM2M and AllJoyn are complementing each other This is why the two different system interwork oneM2M AllJoyn Coverage LAN + WAN LAN API RESTful RPC Discovery Passive Proactive

Interworking Example

Gateway Agent Exposes/injects services from/to AllJoyn proximal network Remote access configuration with control app Connector app provides cloud connection oneM2M API between Gateway Agent and Cloud

AllJoyn-to-oneM2M mapping AJ Gateway Agent with oneM2M AE = IPE oneM2M Network Connector App AJ Network Service Exposing App oneM2M Exposure AE 12 oneM2M IN CSE 3 AJ App 1 Rsc 1 oneM2M AE Y AJ App 2 Rsc 2 oneM2M AE Z Consume AJ service Provide AJ service

AllJoyn-to-oneM2M mapping AJ Gateway Agent with oneM2M AE=IPE & CSE oneM2M Network Connector App AJ Network Service Exposing App oneM2M Exposure AE 12 oneM2M CSE 1 oneM2M IN CSE 3 Rsc srv 1 Rsc srv 2 AJ App 1 Annc Rsc 1 oneM2M AE Y AJ App 2 Annc Rsc 2 oneM2M AE Z oneM2M AE Z Consume AJ service Provide AJ service

AllJoyn-to-oneM2M mapping Need to develop resource structure to expose AJ service objects to oneM2M AEs Re-use existing resource types versus new types Resource structure for provider-specific services needs to represent serv. objects Need new resource types Serv. Frameworks different from serv. objects

Way forward Informative work (TR-0014) by TP#18 TR-0014: oneM2M and AllJoyn Interworking Normative work from TP#19 as part of Rel-2 CRs to TS-0001 Resource type specifications, and so on…