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

Slides:

Advertisements

Similar presentations

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

Advertisements

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

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

Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date:

Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:

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.

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

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,

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

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

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.

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

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

Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,

SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed draft.

SCFAH r1 Title: Working Draft “Ad-Hoc Recommendation to SC on 3GPP2 Future” Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.

OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.

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

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.

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

Setting oneM2M’s Market direction

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

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,

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

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

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

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:

SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future ver2 Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed.

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

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

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

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, Meeting Date: TST #21 Document.

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

SCFAH r2 Title: “Ad-Hoc Recommendation to SC on 3GPP2 Future” – Working Draft Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.

Status summary of the ad-hoc discussions 29th of June 2012 oneM2M call.

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

A discussion on Release duration TP #14 Source: JaeSeung Song, KETI (TTA), Meeting Date: TP Discussion_on_Release_duration.

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

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

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.

Doc.: IEEE /176r1 Submission March 2000 John Barr, MotorolaSlide 1 Project: IEEE Working Group for Wireless Personal Area Networks (WPANs)

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:

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

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:

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.

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

Issues on TST #28 (Overview)

Semantic testing in oneM2M

WPM ad-hoc group report TP#25

Invite IIC testbeds to oneM2M interops

Considering issues regarding handling token

Discussion on feature catalogue

Presentation transcript:

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

Background oneM2M SC will continue Ad-Hoc on Certification to discuss further technical and political aspects. Political aspects will be investigated further at the SC level Technical aspects need to be consulted by TST WG © 2014 oneM2M Partners 2

Political Questions (F.Y.I) Political questions which will be further discussed in the Ad-Hoc are as follows: – Where certification body has to be located (within oneM2M or outside of oneM2M)? – Will there multiple certification bodies for oneM2M certification? – Should the same oneM2M logo be used? Or different logo? (e.g., oneM2M certified) © 2014 oneM2M Partners 3 Certified

Technical Questions Technical questions which need to be discussed further within TST WG and provided to the SC Ad- Hoc for their information: – TQ1: Which nodes are the subjects for oneM2M certification? + All Nodes defined in oneM2M? + End Nodes? + End Nodes and Middle Node? © 2014 oneM2M Partners 4 ADNASNMNIN

Technical Questions Technical questions which need to be discussed further within TST WG and provided to the SC Ad- Hoc for their information: – TQ2: How self-certification and formal-certification will be applied to these nodes? © 2014 oneM2M Partners 5 ADNASNMNIN

Technical Questions Technical questions which need to be discussed further within TST WG and provided to the SC Ad- Hoc for their information: – TQ3: What are the target for oneM2M certification? + Hardware? + Software? © 2014 oneM2M Partners 6 AE CSE AE CSE

Technical Questions Technical questions which need to be discussed further within TST WG and provided to the SC Ad- Hoc for their information: – TQ4: Are all the releases subject for full certification? Or only additional features? © 2014 oneM2M Partners 7 Rel-1 Rel-2

Technical Questions Technical questions which need to be discussed further within TST WG and provided to the SC Ad- Hoc for their information: – TQ5: What about patched version based on the same release? © 2014 oneM2M Partners 8 Rel-1 Bugs Fixes

Proposal Call for your opinion on the technical questions. After some discussion + one hour discussion in one of conference calls (18.1~18.3), a summary needs to be prepared. Any volunteer to take this action item? © 2014 oneM2M Partners 9