Discussion on feature catalogue

Slides:

Advertisements

Similar presentations

CMDH Refinement Contribution: oneM2M-ARC-0397

Advertisements

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

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.

Discussion on constraint device optimization Group Name: ARC Source: Jiaxin (Jason) Yin, Huawei Technologies Co., Ltd., Meeting Date:

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

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

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

Step by step approach Group Name: WG2

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless

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

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

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.

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

Device Management A unified way of managing devices enabled by different management technologies Group Name: WG2/WG5 Source: Huawei Technologies Co., Ltd.

LWM2M Interworking Object Instantiation Group Name: Architecture Source: ALU (TIA) Meeting Date: Arc 17.2 Agenda Item: LWM2M Interworking.

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

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.

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

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

Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.

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

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.

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

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

Planning for the test event Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

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

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Communication Method Group Name: ARC Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

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.

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

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

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

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

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

WPM ad-hoc group report TP#20 Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:

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

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

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

3GPP MBMS protocol stack

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

Proximal IoT Interworking discussion

Group multicast fanOut Procedure

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Proposed design principles for modelling interworked devices

Allow tool-specific code in TTCN-3 as well in conformance test suite

MAF&MEF Interface Specification discussion of the next steps

Invite IIC testbeds to oneM2M interops

Proximal IoT Interworking solution discussion

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

oneM2M Versioning Next Steps

ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC

Group multicast Group Name: ARC

Aggregation of notification

Considering issues regarding handling token

LWM2M Interworking with <mgmtObj> Resources

CMDH Refinement Contribution: oneM2M-ARC-0397R01

Presentation transcript:

Discussion on feature catalogue Group Name: TST/ARC Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Yinjiaxin@Huawei.com Meeting Date: 2016-10-17 Agenda Item: TBD

Background and rational WI-0055 was created in TP24 to define feature catalogue of oneM2M. The expected outcome of this WI would be a list with levels that could cover all oneM2M provided features. The discussion paper in focusing on a proposed architecture of feature catalogue.

Proposed architecture Feature Feature set AE CSF Feature Feature CSE Feature set Feature The defined CSF will be the highest granularity of the oneM2M defined function. Each CSF is then further categorized into feature sets. A feature set is a feature that may be composed across multiple resources and attributes. In one end to end call flow, the resources and attributes are always used to enforce the feature. The implementation of each feature will be divided into AE perspective and CSE perspective. Feature in the finest granularity. It’s one feature that cannot be divided any more.

CSF The 12 CSFs we have defined

Feature The atomic operation that is defined by oneM2M. On the consideration of service, it’s meaningless to divide the operation anymore. If a certain feature is enforced by one attribute, the feature is composed of CRUD of just this attribute. E.x., set the max number of instance of a container If a feature is enforced by multiple attributes together, the feature is composed of the CRUD of multiple attributes. E.x., application registration with AE-ID start by ‘S’

Feature set Several features that serves for the same service that is closely related but not strictly bound, i.e., as a feature set, it can be separated into more features. For example: Group management CSF Configuration of group feature set Fan out using group feature set Data management and repositary CSF Sharing data feature set which includes the CRUD of container and contentIntance Abstraction of data model includes the CRUD of flexContainer

An example from GMG CSF Group management CSF Configuration of group feature set Create group with members Create group with max number member limit Create group with member type Update group member Update group max number of member Retrieve group Delete group Fan out using group feature set Fan out request addressing members Fan out subscribe request

Conclusion A three level structure of all the features The top level and bottom level are explicit and easy to define CSFs and atomic features The middle level need some categorization.

Thanks!