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

Slides:

Advertisements

Similar presentations

A global Service layer platform for M2M communications

Advertisements

P449. p450 Figure 15-1 p451 Figure 15-2 p453 Figure 15-2a p453.

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

Database Systems: Design, Implementation, & Management, 5 th Edition, Rob & Coronel 1 Data Models: Degrees of Data Abstraction l Modified ANSI/SPARC Framework.

OneM2M portal introduction Group Name: Technical Plenary Source: Gerry McAuley, ETSI, Meeting Date: Agenda Item: 1.5.

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,

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

Common Service Entities

Step by step approach Group Name: WG2

Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, Meeting Date:

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:

Application Policy on Network Functions (APONF) G. Karagiannis and T.Tsou 1.

3GPP Rel-13 Interworking discussions

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

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

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,

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

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

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:

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

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:

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

Metadata and Meta tag. What is metadata? What does metadata do? Metadata schemes What is meta tag? Meta tag example Table of Content.

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

LWM2M Interworking Group Name: Architecture

Issues pertaining to IOP test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

Doc.: IEEE /0061r0 Submission June 2011 Mika Kasslin, NokiaSlide 1 Discovery system overview Notice: This document has been prepared to assist.

M2M Service Session Management (SSM) CSF

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

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

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

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

ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

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

3GPP SCEF Interworking Discussions

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

Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

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

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

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) 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#:

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:

Resource subscription using DDS in oneM2M

3GPP MBMS protocol stack

Provisional Architecture for oneM2M

Service Framework Proposal

Group multicast fanOut Procedure

3GPP interworking in R3 Group Name: ARC

Issues of <locationPolicy> Discussion

TS-0034 scope against TS-0001, and managing stage 2 Semantics

Considering issues regarding handling token

Discussion on feature catalogue

Business Documents: Agenda

IEEE MEDIA INDEPENDENT HANDOVER DCN:

Requirements Date: Authors: March 2010 Month Year

Presentation transcript:

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

© 2013 oneM2M Partners oneM2M-ARC Objective Specify the behavior of the systems in terms of the services provided to applications, based on the resources in the tree structure. This facilitates the support of the integrated approach, as well as ensuring that resources are justified.

© 2013 oneM2M Partners oneM2M-ARC Process Outline The process involves the following 3 steps: – List Service Slogan for every resource in the Resource tree – Describe the service in more details at an abstract level. – CSFs Re-alignment to service components

© 2013 oneM2M Partners oneM2M-ARC Steps 1&2 (1 of 3) Prepare for the following table for all resource groupings : SloganResource name Service DescriptionApplicable CSE Option ality List the service (only create aspect to be consid ered) Resource used to expose the service Refer to the appropriate section in section 6 where the CSE functions are described. This implies that this section have to be restructured to describe the services so it can be referenced Mandat ory/Op tional

© 2013 oneM2M Partners oneM2M-ARC The above applies to the following resources: – CSE Resource – Application Resource – Access Right Resource – Container Resource – Group Resource – Base Resource – As well as any additional resources to be later defined Step2 1&2 (2 of 3)

© 2013 oneM2M Partners oneM2M-ARC Partial example for access right Steps 1&2 (3 of 3) Service SloganResource Used Create an access control unit (instance) to be allocated., a list of the attributes Subscribe to changes in an access control unit (instance) - (Optional function)

CSE network Mcn Suscription Registration/ Identification Network Service Exposure Communication/ Data Exchange Device Management Security Step 3 -Service Grouping and CSF Re-alignment Location Management CSFs have to be regrouped to match the service components in the figure to facilitate ROA and SOA integration (regardless of any selected option) There has to be a complete alignment between CSF and service Components in the figure. This is mandatory Data Management Discovery