CMDH Refinement Contribution: oneM2M-ARC-0397

Slides:

Advertisements

Similar presentations

FIPA Interaction Protocol. Request Interaction Protocol Summary –Request Interaction Protocol allows one agent to request another to perform some action.

Advertisements

Summary on the M2M CMDH Policies Management Object (MCMDHMO)

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

Example for SCL resource usage according to ETSI TC M2M March 2011 Josef Blanz, Qualcomm Inc.

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:

Device Management using mgmtCmd resource

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

OneM2M-ARC Service_examples_and_evolution Service examples and evolution Group Name: WG2 Source: Philip Jacobs, Cisco Systems,

DEMIGUISE STORAGE An Anonymous File Storage System VIJAY KUMAR RAVI PRAGATHI SEGIREDDY COMP 512.

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

March 7, 2005MOBIKE WG, IETF 621 Mobility Protocol Options for IKEv2 (MOPO-IKE) Pasi Eronen.

Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

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

CMDH Policies Contribution: ARC R03-CMDH_Policies.ppt Source: Josef Blanz, Qualcomm UK, Hongbeom Ahn, LG Electronics,

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

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

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

(Business) Process Centric Exchanges

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

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

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

Usage Scenarios for CSE Group Name: WG2(ARC-WG) Source: Shingo Meeting Date: Agenda Item: Message.

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.

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

AllJoyn-Interworking Discussion Group Name: TP WG2 ARC Source: Josef Blanz, Phil Hawkes, Qualcomm Inc., Meeting Date:

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

Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

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

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

Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:

Interworking with an External Dynamic Authorization System Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.2,

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

1. How to handle Request-ID? oneM2M joint WG2 & WG3 discussion PRO Josef Blanz July 2 nd, 2014.

M2M Service Session Management (SSM) CSF

E2EKey Resource Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.3, Agenda Item: End-to-End Security.

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

ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.

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

App and Management End- to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm,

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

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

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:

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, 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.

CMDH and Policies Contribution: oneM2M-ARC-0603

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

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

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

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

Service Enabled AE (SAE)

End-to-End Security for Primitives

MAF&MEF Interface Specification discussion of the next steps

Network Services Interface

Discussion to clarify online/offline behavior

3GPP Interworking Abstraction

Considering issues regarding handling token

Discussion on feature catalogue

CMDH Refinement Contribution: oneM2M-ARC-0397R01

CMDH Policies Contribution: ARC-2014-xxxx

Service Layer Dynamic Authorization [SLDA]

Network Services Interface

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

CMDH Refinement Contribution: oneM2M-ARC-0397 Source: Josef Blanz, Qualcomm UK, jblanz@qti.qualcomm.com Meeting Date: ARC 6.7, 2013-10-03 Agenda Item: CSF definitions

CMDH: Refined Description Description of what CMDH is supposed to do Starts with simple UPDATE example Proposes Stage-2 message flow Does not cover protocol specific features (to discussed in WG3)

Access to local resource AE1 trying to access local resource: For instance an UPDATE to local resource Assumes that resource is hosted on CSE1 Request can be processed without help of other CSEs No need to involve CMDH on CSE1 or any other CSEs Y2 Infrastructure Node Middle Node Application Service Node AE1 CSE2 CSE3 Y1 CSE1 X CMDH UPDATE

Access to remote resource (1) AE1 trying to access remote resource: For instance an UPDATE to remote resource Assumes resource is hosted on CSE3, connectivity for Y1/Y2 may be off-line Request may contain preferences indicating ‘lifespan’, ‘event category’ etc. CSE1, CSE2 and CSE3 need to get involved Multiple steps needed… see following slides Infrastructure Node Middle Node Application Service Node AE1 CSE2 CSE3 CSE1 X CMDH UPDATE Y1 Y2

Access to remote resource (2) AE1 making request to local CSE (=CSE1), CSE1 checks request and accepts it (other CSFs involved) Request is targeting another CSE (=CSE3) CMDH on CSE1 takes responsibility to deliver it Infrastructure Node Middle Node Application Service Node AE1 CSE2 CSE3 CSE1 X CMDH CSE1 accepts request CMDH on CSE1 responsible to deliver Y1 Y2

Access to remote resource (3) CMDH on CSE1 is forwarding request to CSE2 CMDH on CSE1 waits until it is OK to connect to CSE2 (policies: when/how) CSE2 checks request and accepts it (other CSFs involved) Request is targeting another CSE (=CSE3) CMDH on CSE2 to takes responsibility to deliver it Infrastructure Node Middle Node Application Service Node AE1 CSE2 CSE3 CSE1 X CMDH CMDH on CSE2 responsible to deliver CSE2 accepts request CSE1 establishes connection to CSE2 Y1 Y2

Access to remote resource (4) CMDH on CSE2 is forwarding request to CSE3 CMDH on CSE2 waits until it is OK to connect to CSE3 (policies: when/how) CSE3 checks request and accepts it (other CSFs involved) Request is targeting local CSE (=CSE3) Local CSE3 executes original request (UPDATE) Infrastructure Node Middle Node Application Service Node AE1 CSE2 CSE3 CSE1 X CMDH CSE3 executes UPDATE CSE3 accepts request CSE2 establishes connection to CSE3 Y1 Y2

Message Flow: Example Assumptions: Originator is AE1 Original request is an ‘UPDATE’ to a remote resource on CSE3 ‘UPDATE’ options selected such that no feedback from update operation was requested, i.e. AE decided that it does not need to hear back from CSE3 Delivery related parameters (to be discussed separately): Lifespan Event Category

Resource Based DH Requesting a CSE to ‘deliver’ something could be done via a resource based service A CSE receiving such requests may have a simple path for that, e.g. /{CSE-base}/dh A special resource type <deliveryRequest> could be defined to capture the relevant data and meta-data for delivery requests Possible actions: Request to Deliver something CREATE(/{CSE-base}/dh, delivReqData, lifespan, eventCat, options) or CREATE(/{CSE-base}/dh/{pref-ID}, delivReqData, lifespan, eventCat, options) => If accepted, CSE responds with actual dhr-ID (possibly more data, depends on selected options) and executes on the delivery Request to retrieve status of delivery request RETRIEVE(/{CSE-base}/dh/{dhr-ID}) Request to change delivery parameters UPDATE(/{CSE-base}/dh/{dhr-ID}/lifespan, newLifespanValue, options) Request to delete / cancel a delivery request DELETE(/{CSE-base}/dh/{dhr-ID}, options) Delivery of data can be offered as a resource-based service in a RESTful manner

Message Flow (Resources) Assumptions: Originator is AE1 Original request is an ‘UPDATE’ to a remote resource on CSE3 ‘UPDATE’ options selected such that no feedback from update operation was requested, i.e. AE decided that it does not need to hear back from CSE3 Delivery related parameters (to be discussed separately): Lifespan Event Category