Feedbacks on oneM2M certification Group Name: TP Source: JaeSeung Song KETI, TST WG Chair Meeting Date: 2015-09-07 Agenda Item:

Slides:

Advertisements

Similar presentations

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

Advertisements

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.

Analysis of oneM2M Certification Model TST 15 Source: Sookhyun Jeon, TTA, Meeting Date:

Test WG (WG6) 2015 Planning TST 15 Source: JaeSeung Song, TST WG Convenor (TTA), Meeting Date: TST WG6_2015_planning.

TST WG Progress Report at TP 15 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Miami, USA Agenda.

Analysis of Available oneM2M Certification Models TST 15.3 Source: JaeSeung Song (WG6 Chair, Sookhyun Jeon (TTA,

Zach Little Program Manager Microsoft Corporation.

Conflict Management Group Name: WG1 Source: KETI, ETRI, SK Telecom, nTels, KCA, Kaonmedia Meeting Date: dd Agenda Item: Discussion.

TST WG Progress Report at TP 18 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP18,

TST WG Progress Report at TP 17 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Sapporo, Japan Agenda.

App-ID Ad-Hoc Technical Issues TP AppID R01 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,

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

3GPP Rel-13 Interworking discussions

Work Programme Management Ad hoc Group Report Group Name: one M2M TP9 Source: Convenor WPM Joachim Koss, Gemalto M2M,

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.

Setting oneM2M’s Market direction

Work Programme Management Ad hoc Group Report Group Name: one M2M TP12 Source: Convenor WPM Joachim Koss, Gemalto M2M,

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

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.

Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

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

Work Programme Management Ad hoc Group Report Group Name: one M2M TP13 Source: Convenor WPM Nicolas Damour, Meeting Date:

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

Considerations From an IPv6 Product Developer Thomas Narten May 4, 2007, NIST.

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

TST WG Progress Report at TP 19 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP19, Item.

SEC Conference calls following TP#11 Group Name: WG4 (SEC ) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information.

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

Discussion for the next oneM2M release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

MoW&M&P Report Group Name: TP18 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

3GPP Rel-13 Interworking discussions

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

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

TST WG Progress Report at TP #20 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP20, Item.

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Meeting Date: TST #21 Document.

Test environments serving device certification Group Name: WG6 (TST) Source: Denis Chabot, Sierra Wireless,

TST WG Progress Report at TP 18 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP18, Item.

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

WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

WG2 - ARC TP #20 Status Report Group Name: oneM2M TP #20 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

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

TST Developing_SEC_TP Developing SEC TP - discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:

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

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

TST WG Status Report to TP #21 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP21, Item.

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

TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

Discussion points for 2 nd Interop Event Group Name: TST WG Source: Keebum Kim, TTA, Meeting Date: TP#22.

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.

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

Discussion on Certification Group Name: TST WG Source: JaeSeung Song, WG6 Chair, Meeting Date: TST #21.

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

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

2 nd oneM2M Interoperability Event Prof. Song JaeSeung (KETI, TST WG Chair) TST Introduction-to-2 nd -interop-event.

Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.

TST R01-MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM)

TST TTCN-3_development_plan TTCN-3 development plan Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:

Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.

TST MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting.

3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:

Introduction of TTA Verified Program for oneM2M TP #23 Closing Session(20 th, May 2016) Source : Kanghae Lee,

Issues on TST #28 (Overview)

Semantic testing in oneM2M

WPM ad-hoc group report TP#25

Invite IIC testbeds to oneM2M interops

Windows 8 Hardware Certification Program and KIT Overview

Version Control CS169 Lecture 7 Prof. Aiken CS 169 Lecture 7 1.

Presentation transcript:

Feedbacks on oneM2M certification Group Name: TP Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda Item: TBD

Background In the oneM2M SC #27, there were several online/offline questions on oneM2M certification In order to help making a good decision on oneM2M certification, TST WG takes these questions and prepares feedbacks © 2014 oneM2M Partners 2

Feedbacks on oneM2M Certification Issues © 2014 oneM2M Partners 3 CertifiedReady Q1: Where to locate a Certification Body (CB)? Outside of oneM2M Q2: Multiple CB vs. Single CB? Both are possible In the case of multiple CBs, these bodies must run the same certification program Q3: Logo? Should use a variation of oneM2M logo for brand recognition, for example.. Permission is required from oneM2M partners

Feedbacks on oneM2M Certification Issues Q4: Which functionalities on which reference points are subject to certification? Depending on the scenarios, types of deployment, and market situation (this should be reflected in the test specifications) Different certification profiles can help minimise fragmentations (e.g. MPEG-4) Q5: Hardware vs. Software? As oneM2M is standardising the Service Layer, functionalities are subject for certification Q6: Self-certification, -declaration, and formal certification? All should co-exist Self-certification is cost effective But, this needs validated certification tools and test suites © 2014 oneM2M Partners 4

To be updated after one more TST ad-hoc session Feedbacks on oneM2M Certification Issues Q7: Are all releases subject for full certification? Yes, all releases are subject for full certification Q8: What about software patches? This depends on CB. Once Certification has been awarded, then it cannot be rescinded just because of a bug(s) Latest version of the test specs/tools/test cases should contain bug-fixes © 2014 oneM2M Partners 5

Report to oneM2M SC oneM2M TST WG believes that oneM2M needs a strong certification program as soon as possible © 2014 oneM2M Partners 6