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

Slides:

Advertisements

Similar presentations

Access Control Mechanism Discussion

Advertisements

CMDH Refinement Contribution: oneM2M-ARC-0397

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

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

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

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

Discussion on oneM2M HTTP Binding Interoperability Test Spec.

Device Management using mgmtCmd resource

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

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

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

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

3GPP Rel-13 Interworking discussions

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.

SEC Identity_of_registrar_CSE Identity of Registrar CSE Group Name: SEC, ARC and PRO Source:FUJITSU Meeting Date: Agenda Item: Authentication.

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Proposal for WG3 & WG5 work area split

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

OIC device management interworking procedure

M2M Service Session Management (SSM) CSF

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

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

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.

Issue regarding authentication at MN-CSE Group Name: ARC & SEC Source: FUJITSU Meeting Date: Agenda Item: Security Admin API.

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

3GPP SCEF Interworking Discussions

LWM2M Interworking Proxy Procedures ARC Considerations

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Clarification of Access Control Mechanism on Rel-1 & Rel-2 Group Name: SEC ( ARC & PRO for information) Source: FUJITSU Meeting Date: Agenda.

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

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

CMDH and Policies Contribution: oneM2M-ARC-0603

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

Issues about management Group Name: MAS9.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

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

ARC Possible_Collaboration_Area_with_OSGi.pptx Possible Collaboration Area with OSGi Group Name: ARC WG Source: Hiroyuki Maeomichi, NTT (TTC)

Possible Solution of Interworking between oneM2M and OSGi

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

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:

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

[authenticationProfile] <mgmtObj> specialization

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

Group multicast fanOut Procedure

WG2 - ARC TP#29 Status Report

2nd Interoperability testing issues

Possible options of using DDS in oneM2M

Issues of <locationPolicy> Discussion

Proposed design principles for modelling interworked devices

oneM2M Service Layer Protocol Version Handling

WG2 - ARC TP#29 Status Report

Proximal IoT Interworking solution discussion

Discussion to clarify online/offline behavior

oneM2M Versioning Next Steps

Group multicast Group Name: ARC

Considering issues regarding handling token

LWM2M Interworking with <mgmtObj> Resources

CMDH Refinement Contribution: oneM2M-ARC-0397R01

MinitorEvent(UE_Reachability)

Development Guideline for oneM2M Products and Services

3GPP Interworking and use of <schedule> resource

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item: Protocol Core TS

PRO R01-URI_mapping_discussion Introduction The distributed administration of m2m resources looks good, but it may be troublesome in our M2M use cases. This contribution proposed to use single URI space covering resources which are hosted by multiple CSEs

PRO R01-URI_mapping_discussion Problem on CSE addressing Arc-TS specified the Registration procedure of CSE, but it is not feasible on multi-hopped MN-CSE configuration IN-CSE cannot find the route to Hosting CSE in this example, since Hosting CSE did not register on IN-CSE and IN-CSE cannot route the request to MN-CSE. Registrar CSE for AE AE IN-CSE MN-CSE (reachable) Hosting CSE (Target) MN-CSE (unreachable) Reachability information is not provided to IN-CSE by Registration

PRO R01-URI_mapping_discussion Single URI space for domain Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Delivery-path RegistrationInternal Request Forwarding Path Registration on IN-CSE (out-of-bound ?) Registration through Mca Path Registration on IN-CSE (Registration forwarding) Registration through Mca Forward Request to Hosting CSE via MN-CSE Forward Request to Hosting CSE Request to URI pointing IN-CSE URI  CSE Mapping

PRO R01-URI_mapping_discussion Use Case not require request forwarding Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Registrar CSE for AE AE IN-CSE MN-CSE Hosting CSE (Target) Container hosted by IN-CSEDevice Management through Mcn Management through Mcn Sending Data as ContentInstance Report Management Result thorugh Mcc Request to URI pointing IN-CSE Sending Data as ContentInstance Retrieval of Data

PRO R01-URI_mapping_discussion Proposed Assumption on URI URI will be based on the address of IN-CSE. Each CSE can be accessed through remoteCSE resource on IN-CSE. “Path-Registration” may be implemented to enable routing with in-bound communication. Request will be forwarded based on PoA information hop-by-hop from IN-CSE.

PRO R01-URI_mapping_discussion URI Examples  (rewrite URI)  mapping to Mcn access (ex. OMA-DM) to CSE-A  data storage hosting on IN-CSE as /container/pl1/… URI of CSEBase Name of remoteCSE ( via cseB.example.com) Path of resource URI of CSEBase Name of mgmtObj resource Path of MO URI of CSEBase Name of containers

PRO R01-URI_mapping_discussion Conclusion This change may not affect on Arc-TS, but WG3 member requested to check with WG2 HTTP/CoAP binding use URI as the address, and relationship between CSE-ID and (hierarchical) resource URI should be clarified