Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, 2016-03-18 Agenda Item: Discuss directions."— Presentation transcript:

1 Directions for Release 3 Group Name: SEC Source: Mihai.Moraru@neclab.eu, NEC Europe Ltd. Meeting Date: SEC22, 2016-03-18 Agenda Item: Discuss directions for R3 and possible WI

2 Features MAS SEC TST Resources, Flows, Semantics ARC, PRO, REQ ESData, ESPrim, ACPs, Roles, Dyn AuthZ, Distrib AuthZ Implementation

3 Covered in Rel1 and Rel2 Resources – Confidentiality, Integrity (ESData) – Authorization (dynamic, distributed) Flows – Confidentiality, Integrity (ESPrim) Entities – Authentication © 2014 oneM2M Partners 3

4 Centralized application design ADN MN IN Infrastructure domain Field domain ADN MN …… Centralized data processing by AE-IN Sensors generate data which is drained towards the infrastructure

5 Extend security support MAS SEC TST Virtual resources, Availability requirements Etc. ARC, PRO, REQ Secure environment, Change of ownership

6 Support more flexible designs Focus on existing requirements Processing on the M2M Gateway – Mobile scenarios, intermediate processing Data security at rest – Big Data repository, outsourcing

7 Processing on the M2M Gateway

8 Problems with centralized design ADN MN IN Infrastructure domain Field domain ADN MN …… Centralized data processing by AE-IN Congestion, latency, inefficient bandwidth usage Connectivity loss Car Broken link Device mobility

9 Processing on MN – automotive example Sensor ECU … Infrastructure Sensor Compute speed Broadcast speed Following vehicle Vehicle Verify

10 Processing on MN – automotive example … Communication inside the automobile Communication outside the automobile Vehicle ADN-AE ADN ADN-AE ADN ADN-AE ADN MN-AE MN2 MN-CSE MN-AE MN1 MN-CSE IN-AE IN IN-CSE Possible mapping to oneM2M Compute Verify

11 Processing on MN – automotive example Clarifications, open issues – Node registrations are not represented – Tbd: How MN1 discovers MN2 – Communication paths are logical, they show information flow. Tbd: exact retrieval mechanism (i.e.: request or notify) This is only one example where processing on the MN is needed in a secure way Discussions are welcome – Gathering support for a new WI


Download ppt "Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, 2016-03-18 Agenda Item: Discuss directions."

Similar presentations


Ads by Google