Scenarios for oneM2M and OIC Interworking

Slides:

Advertisements

Similar presentations

OneM2M Technical Requirements - Driven by EU BUTLER and IEEE PAC - Group Name: WG1 (REQ) Source: Friedbert Berens, FBConsulting Sarl,

Advertisements

oneM2M and AllJoyn Interworking

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

A Proposal of “Common Information Model” for HEMS domain Group Name: MAS WG Source: Yoshihisa Ito, Takefumi Yamazaki,

A Proposal of “Common Information Model” for HEMS domain

TC100 1 Energy saving system for home appliances and home network devices - Part 1 : Architecture and requirements Korea Electronics Technology Institute.

Conflict Management Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:

Electrical Energy.  Electrical energy is the energy transferred to an electrical device by moving electrical charges. The energy used at home is measured.

Bellringer What happens when you turn the lights on? What allows lights to be turned on and off? Write your answer or draw an explanatory picture for later.

IOT5_ GISFI # 05, June 20 – 22, 2011, Hyderabad, India 1 Internet of Things Work Group Coordination Plan WG Chair.

oneM2M-OIC Interworking Technical Comparison

Proposal for OID-based M2M Node ID Group Name: WG2 Architecture at TP#8 (Miyazaki, December 2013) Source: Yong-Suk Park, KETI, Meeting.

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

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

JEMMA: an open platform for a connected Smart Grid Gateway GRUPPO TELECOM ITALIA MAS2TERING Smart Grid Workshop Brussels, September Strategy &

ETRI-KPU ISO/IEC JTC1 SC25 WG1, Oct A Home-oriented IPTV Service Platform on Residential Gateway for Interworking between Home Network and IPTV.

Considerations on M2M URIs Group Name: WG2(ARC) Source: Yong-Suk Park, Sung-Chan Choi, Jaeho Kim, KETI, Meeting Date:

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

IoT and Telecom Infrastructure GISFI # 07, Dec 19-22, 2011, New Delhi Author: Niranth Organization: Huawei Doc No: GISFI_IoT_

Fuctional Procedure for oiC interworking

Proposal for WG3 & WG5 work area split

Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

Introduction of HERIT September, Company Introduction HERIT Overview Our IoT Business HUBISS IoT solution Our References LGU+, Samsung, KT oneM2M.

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.

Intelligent Home Scenario Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

Discussion for the next oneM2M release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

IoT SDOs and Alliances Landscape (Technology and Marketing Dimensions)

OIC device management interworking procedure

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

OIC INTERWORKING Resource mapping

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date:

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

Way Forward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG2 Source: Heedong LG Electronics.

Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016

Home Device Caching & Replacement Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

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

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

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

Jeju, 13 – 16 May 2013Standards for Shared ICT TTA M2M Activities & Proposal of revised resolution Peter J. Kim, Principal Specialist, TTA Document No:

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jinhyeock Choi, Samsung Electronics,

Overview of oneM2M Home Appliances Information Model

Internet Of Things (IoT)

Provisional Architecture for oneM2M

Proximal IoT Interworking discussion

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Modbus interworking Group Name: ARC

WPM ad-hoc group report TP#24

WPM ad-hoc group report TP#25

oneM2M Work on IoT Semantic and Data Model Interoperability

Considering issues regarding handling token

ETSI Standardization Activities on M2M Communications

Presented by: Veena talapaneni

TTA M2M Activities & Proposal of revised resolution

البيئة السياسية للإدارة الدولية

Energy Consumption at Home

ETSI Standardization Activities on M2M Communications

ITU-T Study Group 20: Brief overview

Home Network Architectures

SMART HOME Expectation IN STANDARDS

Presentation transcript:

Scenarios for oneM2M and OIC Interworking Group Name: Architecture WG Source: Kiran Vedula, kiran.vedula@samsung.com Jieun Keum, Samsung Electronics, je.keum@samsung.com Sung Chan Choi, KETI, csc@keti.re.kr Seonhyang Kim, DT&C, shkim@dtnc.net Bahareh Sadeghi, Intel, bahareh.sadeghi@intel.com Lionel Florit, Cisco, lflorit@cisco.com Meeting Date: <2015-09-07> Agenda Item: <WI 44: oneM2M-OIC interworking >

Interworking overview OIC Industrial Field Domain oneM2M SmartHome OIC Healthcare No.4 No.1 No.3 oneM2M Infrastructure Domain oneM2M SmartCar Field Domain No.2 OIC SmartHome Field Domian The case for OIC device controls oneM2M devices is considered to be the scope of OIC spec . Requires to define how to present non-OIC device to OIC device

Interworking Scenario 1 OIC devices in the field domain connect to oneM2M infra domain and get controlled by oneM2M system Field Domain Infrastructure Domain Infrastructure domain of oneM2M Service Provider oneM2M Service Controller OIC Devices in the field domain

Interworking Scenario 1 - Usecase Connecting a new OIC device to oneM2M infra domain to be controlled by oneM2M service provider or controller User buys a new Samsung Washer(OIC) and connect to Gateway(IPE) subsidized by oneM2M service provider platform in order to receive their oneM2M based IoT service.

Interworking Scenario 2 Interworking between OIC field domain and oneM2M field domains through oneM2M infrastructure domain Infrastructure Domain Field Domain Infrastructure domain of oneM2M Service Provider oneM2M Devices in the field domain OIC Devices in the field domain

Interworking Scenario 2 - Usecase More than two different field domains(oneM2M, OIC) can connect to each other by using oneM2M infrastructure domain. SmartHome (OIC field domain) devices can get the energy consumption data from SmartEnergy (oneM2M field domain) through oneM2M service and control the appliance based on the received data. Ex) Air conditioning could get the price data from the SmartEnergy and if the electricity price is high, it will turn the energy-saving mode.

Interworking Scenario 3 Interworking between OIC field domains through oneM2M infrastructure domain Infrastructure Domain Field Domain Infrastructure domain of oneM2M Service Provider OIC Devices in the field domain OIC Devices in the field domain

Interworking Scenario 3 - Usecase OIC field domains can connect to each other by using oneM2M infrastructure domain. SmartHome (OIC field domain) and Healthcare system (OIC field domain) is connected with oneM2M service provider. By using oneM2M infrastructure network, devices in both OIC domains can transfer information between them.

Interworking Scenario 4 Interworking between OIC field domains and oneM2M field domains locally Field Domain Infrastructure Domain oneM2M Devices in the field domain Infrastructure domain of oneM2M Service Provider OIC Devices in the field domain

Interworking Scenario 4 - Usecase Connecting a new OIC device to oneM2M devices(oneM2M field domain) in local network User installs new smart bulb (OIC device) in home. This new bulb could connect to oneM2M devices in home and could be controlled by a OneM2M switch.