1. WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: 2013-12-09/13 Agenda Item: WG Reports

2. Issues for DECISION in TP WI on “Service Component Architecture” – Supporting companies: “Alcatel-Lucent; AT&T; Verizon; Ericsson; ZTE; Orange; LG Electronics” – oneM2M-TP-2013-0375R02 oneM2M-TP-2013-0375R02 – Background information: issues pertaining to the Services Task Group reported: oneM2M-ARC-2013-0528R03 “service task group status”, WG2 chair/VConeM2M-ARC-2013-0528R03 “service task group status LS 3GPP: “LS to 3GPP on support of alternate device triggering scheme for non-SMS capable devices” – oneM2M-TP-2013-0382, “LS on Alternate Device Triggering Scheme”, NTT DOCOMO oneM2M-TP-2013-0382“LS on Alternate Device Triggering Scheme © 2013 oneM2M Partners 2

3. Issues for DISCUSSION in TP Noted sustained objection from Ericsson pertaining to agreement on a charging contribution (pertaining to ARC TS): – oneM2M-ARC-2013-0565R01 “resources to establish charging policies”; InterDigital oneM2M-ARC-2013-0565R01“resources to establish charging policies © 2013 oneM2M Partners 3

4. Items for INFORMATION © 2013 oneM2M Partners 4

5. Highlights Progressed Work-Items – WI-0002 TS-0001(WG2) Architecture – Agreed a number of contributions according to guidelines to progress our work. All dispositions for contributions are available under the portal (in near real time) – 231 contributions processed including revisions – 51 agreed contributions Continuous coordination with other WGs – WG4: role based access control, security architecture – WG5: management architecture considerations and CSF © 2013 oneM2M Partners 5

6. Highlights - WI-0002 TS-0001(WG2) Architecture Progressed stage 2 work (data structures and flows) : – Subscribe/notify – M2M service subscription – Application – CSE, node – Location – Device management (converged with WG5) – Interworking with underlying network – Identifiers – Container – Group Enhancements and corrections to existing data structures Generated an LS to 3GPP pertaining to device triggering for IP only capable devices © 2013 oneM2M Partners 6

7. Open Issues © 2013 oneM2M Partners 7 Need to focus work on identified gaps and avoid increase of the TS features list Gaps that need immediate/focused attention (feedback welcome): Logical sequence of flows Resource structure URI structure Relationship between identifiers and URI Procedures Security integration Access control and access right aspects Service subscriptions Interworking Minimal charging Questions pertaining to a bottom up approach for resource definitions

8. Open Action Items Contributions formalism: Provide detailed instructions and/ or a tutorial on the use of the CR template © 2013 oneM2M Partners 8

9. Next Steps Need to focus the work on identified gaps and focus areas Addition of new features will be treated as low priority Be more strict on consistency checking Initiate editorial cleaning Calls and meetings will focus on specific gaps and focus areas so as to expedite the completion of the current TS © 2013 oneM2M Partners 9

10. Next Meetings / Calls Proposed Interim meetings between TP#8 and TP#9 – ARC#8.1 ad’hoc Thursday – 1:00 pm UTC, december 19 2013 – ARC#8.2 Thursday – 1:00 pm UTC, January 9 2014 – ARC#8.3 Thursday – 1:00 pm UTC, January 16 2014 – ARC#8.4 Thursday – 1:00 pm UTC, January 23 2014 © 2013 oneM2M Partners 10