1. Discussion for the next oneM2M release Group Name: TP Source: JaeSeung Song, KETI, jssong@sejong.ac.kr; Jaeho Kim, KETI, jhkim@keti.re.kr;jssong@sejong.ac.krjhkim@keti.re.kr Victor Kueh, Huawei, Victor.Kueh@huawei.com, Jungsoo Park, ETRI, pjs@etri.re.kr;Victor.Kueh@huawei.compjs@etri.re.kr Kyunggeun Kim, KCA, relmk3@kca.kr;relmk3@kca.kr Sangho Choi, SK Telecom, sangho.choi@sk.comsangho.choi@sk.com Meeting Date: 2014-06-09 Agenda Item: Discussion TP-2014-0428R01-Discussion_for_the_next_oneM2M_release

2. First release Procedures for Standardization Typically, adjacent releases have some overlap to ensure continuity and improve efficiency. Why not for oneM2M? Stage 1 Stage 2 Stage 3 Second release Stage 1 Stage 2 Stage 3 Through a small overlap between adjacent releases, oneM2M could provide information to the market (and member companies) on what oneM2M intends to do in the next release.

3. Procedures for Standardization Through this small overlap between adjacent releases, oneM2M could expect various positive effect as follows: Providing information to the market what oneM2M will do in the next release (to enable verticals to start their preparation for the next release) Notifying the fact that oneM2M is working well like other successful standard organizations Shortening the total length of standard development Increasing the number of participants otherwise ‘requirements’ people may hesitate to participate in meetings until active discussion is started in WG1. Through this small overlap between adjacent releases, oneM2M could expect various positive effect as follows: Providing information to the market what oneM2M will do in the next release (to enable verticals to start their preparation for the next release) Notifying the fact that oneM2M is working well like other successful standard organizations Shortening the total length of standard development Increasing the number of participants otherwise ‘requirements’ people may hesitate to participate in meetings until active discussion is started in WG1.

4. Proposed schedule MeetingsDescription oneM2M TP #11 (Xian) Start initial discussion on what we should do in the next release Know which companies are interested in which items oneM2M TP #12 (Sophia Antipolis) Start to discuss draft work items Select some initial features for second release (If time permits) some proposals item can be submitted as formal work item description for approval oneM2M TP #13 (USA) Approve Rel-2 work items Start to discuss actual use cases and requirements for the selected features (WG1)

5. Some thoughts for Rel-2 features Here is an initial proposed (non-exhaustive) list of features that potentially could be standardized in the next Release: – Rel-1 enhancements and optimizations – Big Data (analytics, data collection, storage and sharing) – Interworking with heterogeneous devices – Interworking with underlying network – Device abstraction & Semantics – Security – Authentication, key derivation, key agreement, and identity protection – Studying the Home domain to derive missing features and enhance Rel-1 NOTE1: The list above is not exhaustive, and contains a compiled list of input from different companies – it does not necessarily mean that each supporting company of this contribution agree to work on every of the feature listed above.