Focus on developing RESTful API

Group Name: TPSource: Shingo Fujimoto, FUJITSU (TTC), shingo_fujimoto@jp.fujitsu.comMeeting Date: 2013-10-18Agenda Item: Release 1 planning

Issues

• There are many candidates on protocol choice• High Level Functional requirements are also a

lot• But, Time is limited !!!

2

Suggested Approach

• Standardize Service Layer API only (=ref-X)• Making choice on RESTful API over HTTP as

ref-X for oneM2M release-1(Later we can add more bindings)

• Prioritize API functionalities by relevant use case– Collecting data from M2M Device– Accessing data by various API users

3

Urgency of reference points• Reference points– X: App - Server– Y: Server (or Gateway)

- Device– Z: Node – Network

• We must have ‘Service Layer API’ to make M2M as telecom infrastructure

LAN/PAN

Other Service Provider

Ref-Y

Ref-Y

Ref-Y

Ref-Z

Ref-Z

Ref-Z

Ref-Z

M2M Service Provider

Gateway

ConstrainedDevice

oneM2M CompliantDevice

UserApplication

Ref-X

Internal domain

Outside of domain

PTSN

4

What we cannot compromise• Time to deliver– 6 meeting cycle is too short to develop completely

new solutions– HTTP and XML/JSON technologies are matured

solution • Developer friendly-ness– Many developers are familiar with using RESTful API

• Security and Privacy– Choosing security solutions should be based on long-

term evaluation

5

Benefits on RESTful API over HTTP

• Over 6000 Open API are published• We can re-use common parts of web services

like Web servers, DBMS, SSL Accelerators, and developing tools

• Security and privacy mechanism for ‘RESTful API over HTTP’ are developed and evaluated by security experts

6

Conclusion

• Early TP-wide decision making on protocol choice is suggested to deliver technical specifications on time.

• Choosing ‘RESTful API over HTTP’ as protocol candidate for ref-X is also suggested.

7