Introduction ofPRO WG activities

Group Name: TPSource: Shingo Fujimoto, FUJITSU, shingo_fujimoto@jp.fujitsu.comMeeting Date: 2015-03-25Agenda 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 CollaborationWG1

Requirement WG

WG2Architecture WG

WG3Protocol WG

WG4Security WG

WG5Management, 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 BindingsTS-0009:HTTP Protocol BindingsTS-0010:MQTT Protocol Bindings

Stage1Requirements

Stage2Architecture

Stage3Protocol

Release-1

3

RESTful API• M2M Platform can perform CRUD+N operations

without protocol dependency

CoreProtocol

Part

ProtocolBindings

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 Class Codeclass InterpretationInformational 1xxx The request is successfully received, but the

request is still on process.Success 2xxx The request is successfully received, understood,

and accepted.Redirection 3xxx (Not used in present release)Originator Error 4xxx The request was malformed by the Originator

and, is rejected.Receiver Error 5xxx The requested operation cannot be performed

due to an error condition at the Receiver CSE.Network Service Error

6xxx The requested operation cannot be performed due to an error condition at the Network Serivce Entity.

StatusReport

ErrorReport

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 name Type Name Examples Descriptionm2m:timestamp Time stamp string 20141003T112032 DateTime 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 sameIN-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