2Review and Approval of Agenda

oneM2M Notice

The document to which this cover statement is attached is submitted to oneM2M. Participation in, or attendance at, any activity of oneM2M, constitutes acceptance of and agreement to be bound by terms of the Working Procedures and the Partnership Agreement, including the Intellectual Property Rights (IPR) Principles Governing oneM2M Work found in Annex 1 of the Partnership Agreement.

1Opening of meeting

1.1Welcome

1.2Schedule

1.3Attendees

2Review and Approval of Agenda

• oneM2M-ARC-2013-0497-Agenda_ARC_7_2
• oneM2M-ARC-2013-0497-Agenda_ARC_7_2 was agreed

3Review and Approval of previous Minutes

• Approval by correspondence

4Review of Objectives for the Meeting

• Agree to the new Baseline TS
• Process the contributions to the Architecture TS

5Action Item Status

6Contributions

• Presented by Tim Carey, Alcatel Lucent
• Comments and Issues
• Add a definition for Release Package (different contribution)
• Decisions and Actions

• oneM2M-ARC-2013-0489 was AGREED

• Presented by Tim Carey, Alcatel Lucent
• Comments and Issues
• Remove the highlighting on “Device”
• Separate contribution to address DM 7,8,9 and clarify the editorial notes.
• Decisions and Actions

• oneM2M-ARC-2013-0490R01 was AGREED

• Presented by George Foti, Ericsson
• Comments and Issues
• When you define a service you have 2 components – the resource itself, and the actions on the resource. The service is the actions that can be performed on the resource.
• Have to be able to package services into components that you
• Do we start with services and then go to CSF or the other way round.
• Is the service component the same as a sub-functions of a CSF?
• What are the next steps?
• Do we follow steps 1 and 2 first or step 3 first?
• Security will be needed by all others. It is hierarchal rather than flat.
• All will need to interwork with others to provide a macro service.
• Resource type and identifier. Need to be strict in following the templates.
• The slogan and sub service overlap.
• Proposal for the rapporteur to restore the Resource type and identifier.
• Try to apply this to a few examples.
• Will create a small task force to continue with this
• Decisions and Actions

• oneM2M-ARC-2013-0495 was Noted
• Action A-ARC-2013-0006. Omar will establish a task force to further develop the resource related services

• Presented by Rajesh Bhala, ZTE
• Comments and Issues
• None
• Decisions and Actions

• oneM2M-ARC-2013-0496 was AGREED
• Functional Architecture Spec TS-0001 v0.2.1 will be uploaded to the portal and will be the new baseline for further contributions.

• Presented by SeungMyeong Jeong, LGE
• Comments and Issues
• It may be easier to clarify those to which we cannot subscribe
• Don’t duplicate among resources – extend the editors note.
• Decisions and Actions

• oneM2M-ARC-2013-0393R04 was NOTED

7Planning for next Meeting(s)

Conference Calls

November 7th 13:00 – 15:00 UTC

November 14th 13:00 – 15:00 UTC

November 21st 13:00 – 15:00 UTC

Joint with MAS November 25th 13:00 to 15:00 UTC

Face-to-Face

December 9th to 13th Mayazaki, Japan

8Any other business

9Closure of meeting

Annex 1Participants list

© 2013 oneM2M PartnersPage 1 (of 6)