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

Slides:

Advertisements

Similar presentations

World Class Standards 1 SCP(11)0001 SCP Plenary #47 January 12-14, 2011 Title*: Update on TC M2M activities (and Smart Metering Mandate) Submitted by:

Advertisements

Securing Emerging Mobile Technology JOHN G. LEVINE PH.D. D/CHIEF ARCHITECTURE GROUP 13 SEP

Citrix Secure Gateway v1.1 Technical Presentation August 2002 Technical Presentation August 2002.

Blue Coat and the Blue Coat logo are trademarks of Blue Coat Systems, Inc., and may be registered in certain jurisdictions. All other product or service.

oneM2M and AllJoyn Interworking

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

A Scalable Virtual Registry Service for jGMA Matthew Grove CCGRID WIP May 2005.

Identity Management Based on P3P Authors: Oliver Berthold and Marit Kohntopp P3P = Platform for Privacy Preferences Project.

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

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

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.

App development in SharePoint 2013 LIVE Introducing Cloud App Model Cloud-hosted Apps Experiences from the Field.

Authors list to be completed.

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

Authors list to be completed.

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

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

Honeypot and Intrusion Detection System

Step by step approach Group Name: WG2

(Preliminary) Gap Analysis Hannes Tschofenig. Goal of this Presentation The IETF has developed a number of security technologies that are applicable to.

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

© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Identifying Application Impacts on Network Design Designing and Supporting.

Collaboration with IEEE P2413 Source: Omar Elloumi, TP Chair WG: TP Meeting: TP17.

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

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

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

WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,

Jeju, 13 – 16 May 2013Standards for Shared ICT TIA TR-50 M2M-Smart Device Communications Dr. Jeffery Smith Chief Innovation and Technology Officer/EVP.

Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:

Proposal for WG3 & WG5 work area split

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

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

An introduction to oneM2M

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

What are our conclusions? What is the take-home work?

Introduction to Computers Lesson 8B. home Ways to Connect to the Internet Direct connection Remote terminal connection Gateway connection LAN Modem High-speed.

WoT Outreach: joint slide set Outreach slide set aims to increase the awareness of W3C’s WoT work # Comments Arne: Abgrenzung zu anderen Initiativen.

Role Based Access Control In oneM2m

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

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.

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

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

Admin API for Secure Environment Group Name: SEC Source: Giesecke & Devrient 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.

oneM2M based IoT Platform Development of SK Telecom

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

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

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:

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

Proposed Process for Forming the oneM2M Baseline  Group name: TP#1  Source: Laurent Laporte, Sprint,

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

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

ArcGIS for Server Security: Advanced

Provisional Architecture for oneM2M

Possible options of using DDS in oneM2M

GRUPPO TELECOM ITALIA The IoT 5G Network Infrastructures and the IoT Data Store & Share Platform: challenges and opportunities Roberto Gavazzi – TIM Technology.

WPM ad-hoc group report TP#25

Solving the IoT Platform Challenge

Peer-to-peer networking

Considering issues regarding handling token

Release2 Workshop in Tokyo

An introduction to oneM2M

TIA TR-50 M2M-Smart Device Communications

Presentation transcript:

Focus on developing RESTful API Group Name: TP Source: Shingo Fujimoto, FUJITSU (TTC), Meeting Date: Agenda 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-Z M2M Service Provider Gateway Constrained Device oneM2M Compliant Device User Application 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