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

Slides:

Advertisements

Similar presentations

SOAP Quang Vinh Pham Simon De Baets Université Libre de Bruxelles1.

Advertisements

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

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.

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

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.

TST WG Progress Report at TP 17 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Sapporo, Japan Agenda.

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

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:

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

WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.

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

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

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

WG 3 Progress Report at TP14 Group Name: oneM2M TP14 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

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

Proposal for WG3 & WG5 work area split

Architectural Principles for Services Group Name: WG2- ARC Source: Tim Carey, ALU, Meeting Date: Agenda Item:

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

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.

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

An introduction to oneM2M

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

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

Discussion on XSD implementation conventions (document number PRO R01) Group Name: PRO Source: Wolfgang Granzow, Meeting.

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

PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

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

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.

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

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

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

WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

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

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

Possible Solution of Interworking between oneM2M and OSGi

Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.

Discussion about Interoperability (&versioning) Group Name: PRO & ARC Source: FUJITSU Meeting Date: Agenda Item: TS-0004.

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.

Eclipse Vorto Alexander Edelmann.

oneM2M interop 3 issues and optimizations

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

MIME Type Definition Group Name: PRO WG

Group multicast fanOut Procedure

2nd Interoperability testing issues

Possible options of using DDS in oneM2M

NIDD Discussion Points

WPM ad-hoc group report TP#24

oneM2M Service Layer Protocol Version Handling

MAF&MEF Interface Specification discussion of the next steps

Discussion to clarify online/offline behavior

Considering issues regarding handling token

An introduction to oneM2M

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

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

Scope of Protocol WG (WG3) Protocol WG is working on: Service Layer Protocol – RESTful API to use/control Common Service Functions – Synchronous / Asynchronous communication handling and possible error cases Data Models – Common data types: reusable typed information – oneM2M resource definition Protocol Bindings – Protocol specific mapping for CRUD operations 2

WG Collaboration WG1 Requirement WG WG2 Architecture WG WG3 Protocol WG WG4 Security WG WG5 Management, Abstraction and Semantics WG TS-0001(partial): Security Architecture TS-0001(partial): Device Management Architecture TS-0002: Functional Requirements TS-0003: Security Solutions TS-0004(partial): Common Operations & Resource Def. TS-0005: Management Enablement(OMA-DM) TS-0006: Management Enablement(BBF TR069) TS-0001: Functional Architecture TS-0004: Core Protocol TS-0008: CoAP Protocol Bindings TS-0009: HTTP Protocol Bindings TS-0010: MQTT Protocol Bindings Stage1 Requirements Stage2 Architecture Stage3 Protocol Release-1 3

RESTful API M2M Platform can perform CRUD+N operations without protocol dependency Core Protocol Part Protocol Bindings 4

Communication Handling Minimized Documentation with combination of ‘Generic Procedures’ and ‘Common Procedures’ Generic Procedure for Originator Branch for applicable conditions Common Procedure (reuse / refer within TS) 5

Response Status Codes Errors/Status are categorized to indicate whether Originator is required to take further action Status ClassCodeclassInterpretation Informational1xxxThe request is successfully received, but the request is still on process. Success2xxxThe request is successfully received, understood, and accepted. Redirection3xxx(Not used in present release) Originator Error4xxxThe request was malformed by the Originator and, is rejected. Receiver Error5xxxThe requested operation cannot be performed due to an error condition at the Receiver CSE. Network Service Error 6xxxThe requested operation cannot be performed due to an error condition at the Network Serivce Entity. Status Report Error Report 6

Common Data Types Strict typing in information representation using XSD (XML Schema Definition) – Simple data type: type of value – Enumeration type: numeric indication to save space – Complex data type: structured info. messages Only if XSD definition is not enough, further “restriction” is documented for implementer XSD type nameType NameExamplesDescription m2m:timestampTime stamp string T112032DateTime string of ‘Basic Format’ specified in ISO8601 [27]. Time zone shall be interpreted as UTC timezone. Example of common data definition 7

oneM2M Resource Defs Inheritance information model definition referring TS-0001, adding data types and optionality of attributes on Create Retrieved resource data can be checked using XML validator against XSD definitions 8

Protocol Binding Describes how CRUD+N operation can be requested using specific transport protocol No matter which protocol binding was chosen, operation result is always same IN-CSE(Cloud) MN-CSE(GW) ADN(Sensor) CoAP HTTP Configuration A: Protocol Gateway IN-CSE(Cloud) ADN(Sensor) CoAP MQTT Configuration B: Multi-Protocol Support ADN(Monitor App) 9

Future Work (TBD) Additional Protocol Binding Communication Level Optimization … (more to discuss !) 10

Thanks ! Any Question & Comments ? 11