Proposal for WG3 & WG5 work area split

Slides:

Advertisements

Similar presentations

Gateway Agent Product & Architecture

Advertisements

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Copyright 2009 FUJITSU TECHNOLOGY SOLUTIONS PRIMERGY Servers and Windows Server® 2008 R2 Benefit from an efficient, high performance and flexible platform.

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

CURRENT STANDARDIZATION ACTIVITIES – ONEM2M GSC-18 Meeting, July 2014, Sophia Antipolis, France Document No: GSC(14)18_012 Source: ETSI Contact:

Microsoft Operations Manager Presented by: Alen Plicanic.

OneM2M Draft proposal for slide set. This is not intended to be a oneM2M presentation. It is a collection of source material slides which can be used.

Device Management using mgmtCmd resource

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

On Management, Abstraction & Semantics

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Step by step approach Group Name: WG2

Focus on developing RESTful API Group Name: TP Source: Shingo Fujimoto, FUJITSU (TTC), Meeting Date: Agenda Item:

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

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

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

3GPP Rel-13 Interworking discussions

An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T;

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

Usage Scenarios for CSE Group Name: WG2(ARC-WG) Source: Shingo Meeting Date: Agenda Item: Message.

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

Device Management A unified way of managing devices enabled by different management technologies Group Name: WG2/WG5 Source: Huawei Technologies Co., Ltd.

WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

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

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

An introduction to oneM2M

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

1 HGI MESSAGE TO ONEM2M TECHNICAL PLENARY HANS WERNER BITZER, DEUTSCHE TELEKOM VICE CHAIR, HGI ONEM2M TP#19, SOPHIA ANTIPOLS, FRANCE.

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

3GPP Rel-13 Interworking discussions

Role Based Access Control In oneM2m

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

OneM2M Partnership Project. Contents Introduction Founding Partners Participation Scope & Objectives Structure Deliverables Contacts © 2013 oneM2M Partners.

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.

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

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

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

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, 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:

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

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

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

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

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:

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

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

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

Introducing User’s Role concept Group Name: WG2(ARC) and WG4(SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Provisional Architecture for oneM2M

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Discussion about Use Case and Architecture in Developer Guide

3GPP Rel-13 Interworking discussions

WPM ad-hoc group report TP#25

3GPP Interworking Abstraction

Considering issues regarding handling token

ETSI Standardization Activities on M2M Communications

On Management, Abstraction & Semantics

3GPP V2X Interworking Potential Impact

Current standardization activities – oneM2m

SMART HOME Expectation IN STANDARDS

Presentation transcript:

Proposal for WG3 & WG5 work area split Group Name: WG3(PRO) & WG5(MAS) Source: Shingo Fujimoto, Fujitsu, shingo_fujimoto@jp.fujitsu.com Meeting Date: 2013-09-03 Agenda Item: WG3/WG5 work split

Introduction oneM2M architecture become more stable It seems ready to go for Stage 3 (protocol dev.) Issues WG3(Protocol WG) and WG5(Management, Abstraction and Semantics WG) work may potentially overwrapped. WG3 and WG5 should discuss to split work loads by its speciality.

Potential Issues What is the scope of “Device Management” ? How we can use existing solutions ? How WG3 and WG5 can deliver (integrated or series of) TS ?

Scope of “Device Management” Device Management in M2M Platform is defined as “General Concept”: Device Management (DMG) CSF enables the management of device capabilities including one or more of the following: Application Software installation and settings; Configuration settings and Provisioning; Firmware Updates; Logging, Monitoring, Diagnostics; Topology Management of Area Networks; Devices within an Area Network Management. “Device Management” in M2M is purely administrative, but critical part of the M2M service

oneM2M Architecture Overview

Problem on current DM architecture There are no standardized specifications to fit (interoperability issue is exist)

Proposed DM architecture Intermediate/End Node is controlled using management protocol

Deployment Scenario PAN comm. Proprietary interface API call OMA-DM Server OMA-DM Client (Smartphone) Weight Scale Sending Measured Data ? API call M2M Infrastructure Node M2M Application Server Sending Measured Data ? Proprietary interface LAN comm. BBF TR-069 ACS Air Conditioner BBF TR-069 Compliant GW WG5 [Issues regarding DM] WG3 [Issues in General]

Proposal Consider using management protocols (ex. OMA-DM, TR-069, …) for reference point Y WG5 can focus on how implement CSE on M2M intermediate/end node for its work area. (WG3 will work on generic issues regarding API for reference point X.)