Common Service Entities

Slides:

Advertisements

Similar presentations

Adapted Multimedia Internet KEYing (AMIKEY): An extension of Multimedia Internet KEYing (MIKEY) Methods for Generic LLN Environments draft-alexander-roll-mikey-lln-key-mgmt-01.txt.

Advertisements

Unlicensed Mobile Access (UMA) Dasun Weerasinghe School of Engineering and Mathematical Sciences City University London.

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.

IoT in ODL Lionel Florit, Principal Engineer, ODL ID lflorit

“It’s going to take a month to get a proof of concept going.” “I know VMM, but don’t know how it works with SPF and the Portal” “I know Azure, but.

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:

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

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

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

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

oneM2M-OIC Interworking Technical Comparison

Step by step approach Group Name: WG2

Proposal for OID-based M2M Node ID Group Name: WG2 Architecture at TP#8 (Miyazaki, December 2013) Source: Yong-Suk Park, KETI, Meeting.

An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.

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

3GPP Rel-13 Interworking discussions

Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4.

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

WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.

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

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

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

Proposal for WG3 & WG5 work area split

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

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

Overview of analysis of existing SDO M2M architectures Group Name: REQ ARC#2 Source: Alcatel-Lucent.

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

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.

September 28, 2006 Page 1 3GPP2 MMD Status for IMS Workshop Jack Nasielski

Role Based Access Control In oneM2m

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

Process for Documenting Resources related services and Alignment with Service Components Group Name: WG2-ARC-( ) Source: Ericsson Meeting Date:

LWM2M Interworking Group Name: Architecture

M2M Service Session Management (SSM) CSF

Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless

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.

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

Realizing Ms Interface with OMA DM Group Name: MAS WG Source: Seungkyu Park, LG Meeting Date:

SE abstraction scenarios Group Name: SEC Source: Claus Dietze, Giesecke & Devrient Meeting Date: Agenda Item: WI SE abstraction.

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

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

Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

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:

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

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.

Resource subscription using DDS in oneM2M

Provisional Architecture for oneM2M

Service Framework Proposal

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

Group multicast fanOut Procedure

NIDD Discussion Points

Proposed design principles for modelling interworked devices

Considering issues regarding handling token

Discussion on feature catalogue

LWM2M Interworking with <mgmtObj> Resources

Service Layer Dynamic Authorization [SLDA]

Summary of the MAF and MEF Interface Specification TS-0032

AAA: A Survey and a Policy- Based Architecture and Framework

Presentation transcript:

Common Service Entities Group Name: WG2 Source: Lionel Florit lflorit@cisco.com and Syed Z Hosain Syed.Hosain@aeris.net Meeting Date: 2013-06-14 Agenda Item: ARCH

Introduction In TP#4, ARC255 we have outlined a generic functional view grouped in CSEs (Common Functional Entity). The CSEs contain CSFs (Common Services Functions) This contribution proposes candidate service layer CSFs for inclusion in R1 of the oneM2M architecture Methodology Describe call flows for 2 verticals: from device turn up to data collection Derive the example of a generic call flow Conclude with the CSFs needed

Example for AMI (Smart Grid) AMI Head-End Meter NMS Network Auth w AAA, Key Mgt Route Discovery RPL IP Add Assignment & NMS/HE IP resolution DHCP CSMP Registration Message Node “UP” in NMS Validation of NMS signature CSMP Signed Configuration Message Connection Management Sign on (negotiate comm param, windowing etc.) DSLM/COSEM E52056-21 List of parameters measured & security attributes Data Read

Example for AMI (With oneM2M) AF Meter AMI HeadEnd CSE (Intermediate) CSE (Infra) AF (AMI Head-End) AF CSE (Node) M2M AAA Data Mediation Sys NMS Registration Network Auth w AAA, CA, AD (EAP-TLS) Route Discovery RPL IP Add Assignment DHCP Device Resource creation Verification CSMP Registration Message Validation of NMS signature Node “UP” in NMS CSMP Signed Configuration Message Verification Registration Device Resource creation Sign on (negotiate comm param, windowing etc.) Notification Subscription Device Resource Structure update List of parameters measured & security attributes DLMS/COSEM E52056-21 Data Read Notification X Interface Y Interface Y Interface X Interface

Example for Transportation Billing Syst Data Mediation Enterprise Prov Syst Vehicle Device Enterprise Syst NMS AAA HLR/HSS Device Id creation Account creation Device ID Reg (MEID, IMEI, ICCID, etc ) Application Reg (service) Reg Device (IMSI, Cust#...) Resp (MEID, Keys, IMSI etc) Verification Device Programming Power-on registration Subscription MO Network Access Proc (MO-SMS) Device Reg with service Verification Data Read Notification Retrieval MT Network Access Proc (MT-SMS) Resp Data Read Notification Retrieval

Example for Transportation Billing Syst Data Mediation Enterprise Prov Syst Vehicle Device Enterprise Syst NMS AAA HLR/HSS CSE (Infra) Device Id creation Account creation Device ID Reg (MEID, IMEI, ICCID, etc ) Application Reg (service) Reg Device (IMSI, Cust#...) Resp (MEID, Keys, IMSI etc) Verification Device Programming Power-on registration Subscription MO Network Access Proc (MO-SMS) Device Reg with service Data Read Verification Notification Retrieval MT Network Access Proc (MT-SMS) Resp Data Read Notification Retrieval

Generic Call Flow CSE (Node) CSE (Intermediate) CSE (Infra) AP AF Charging Connection Mgt Security Discovery (any parameters, CSE itself, capabilities etc.) App Registration Verification Dev Application Id Registration Verification Registration (any parameters, CSE itself, capabilities etc.) Verification Resource Creation Dev Application Id Registration Verification Resource Creation Subscribe to Notifications Data Output Verification Notification X Interface Yor Z Interface Y or Z Interface X Interface

Subscriptions/ Notification Generic Call Flow Security Discovery CSE (Node) CSE (Intermediate) CSE (Infra) AP AF Charging Connection Mgt Security Discovery (any parameters, CSE itself, capabilities etc.) App Registration Verification Dev Application Id Registration Verification Registration (any parameters, CSE itself, capabilities etc.) Verification Subscriptions/ Notification Resource Creation Dev Application Id Registration Session Mgt Verification Resource Creation Subscribe to Notifications Data Output Verification Data Management Notification Connectivity Mgt Charging & Billing X Interface Yor Z Interface Y or Z Interface X Interface

Proposed CSF (needed to address the examples of this contribution) Discovery Data Management Session management Connectivity Management Subscription and Notification Security Charging & Billing