1. WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, zhangyongjing@huawei.com Meeting Date: 2014-02-17 to 2014-02-21 Agenda Item: TP#9, Item 12, Reports from Working Groups

2. Issues for DECISION in TP Request for TP endorsement on Refinement of “M2M Area Network” definition: – MAS-2014-0333 CR_on_definition_of_M2M_Area_Network © 2014 oneM2M Partners TP-2014-0022 2

3. Issues for DISCUSSION in TP Issue 1: Issue 2: © 2014 oneM2M Partners TP-2014-0022 3 N/A

4. Items for INFORMATION Latest contribution status can be found in – MAS-2014-0329R04-MAS#9_contribution_list © 2014 oneM2M Partners TP-2014-0022 4

5. Highlights TS-0001 Functional Architecture – Agreed (jointly with ARC) contributions: ARC-2014-0046Device Management Editorial Updates MAS-2014-0013R04Management Server Interaction Updates ARC-2014-0163R04Annex for management resources ARC-2014-0165R02Definition of mgmtDefinition ARC-2014-0164R01Change to moAttribute ARC-2014-0177R02deviceInfo, batteryMgmt, deviceCapability, capabilityInstance Resource – Agreed by WG5 for WG2 endorsement ARC-2014-0624R04 Resource Specification Refinements – Stage 2 work regarding management aspect is considered as ‘stable’ Generalized management architecture & resource template DMG CSF & ASM CSF A list of specific resources providing actual management services: – Diagnostics & Monitoring (battery, memory, reboot/reset, eventLog) – Configuration (deviceCapability, CMDH) – Firmware, Software – Topology (areaNwkInfo, areaNwkDeviceInfo) © 2013 oneM2M Partners TP-2014-0022 5

6. Highlights TS-0005: Management enablement (OMA) – Agreed contributions: MAS-2014-0027R01skeleton of TS0005 – Output version: v0.0.1 – Current status: First draft (10%) – Milestone forecast: No change. TS-0006: Management enablement (BBF) – Agreed contributions: MAS-2014-0023Skeleton of TS0006 – Output version: v0.0.1 – Current status: First draft (10%) – Milestone forecast: No change. © 2014 oneM2M Partners 6

7. Highlights TR-0007: Abstraction & Semantics TR – Agreed contributions: MAS-2014-0024Overview on Semantics for TR 0007 MAS-2014-0328R02Gym Semantics Use Case MAS-2014-0025R01Semantic Home Control use case MAS-2014-0029R03UseCase-Intelligent Alarm Service – Output version: v0.7.0 – Current status: Draft (50%) – Use cases – Guideline example for mapping Information Models into oneM2M Resources – Introduction to existing semantics-related solutions – Milestone forecast: No change. © 2014 oneM2M Partners 7

8. Open Issues © 2014 oneM2M Partners 8 N/A

9. Open Action Items © 2014 oneM2M Partners TP-2014-0022 9 #Action Item DescriptionOwnerStatus A-WG5- 9.0-001 TS-0004: CMDH Policies data typeQualcommOPEN A-WG5- 9.0-002 TS-0004: resources schema, primitives, procedures Huawei, LGE, Qualcomm OPEN A-WG5- 9.0-003 TS-0004: resources schema, primitives, procedures IDCCOPEN A-WG5- 9.0-004 TS-0005: Mapping to DM1.xHuawei, LGEOPEN A-WG5- 9.0-005 TS-0005: Mapping to DM2.0LGE, GemaltoOPEN A-WG5- 9.0-006 TS-0005: Mapping to LWM2MLGE, Gemalto, Ericsson OPEN A-WG5- 9.0-007 TS-0005: New objects (CMDH Policies)QualcommOPEN A-WG5- 9.0-008 TS-0006: Mapping to BBF TR069, New objects (CMDH Policies) ALU, QualcommOPEN

10. Next Steps - Management Further refine TS-0001 (Functional Architecture) jointly with WG2 on Management Aspects. – To Refine the ASM/DMG CSF description (e.g. state machine) – To clarify & refine of individual resources (hooking places, CMDH) – To clarify operations – Consistency review Progress TS-0004 (Protocol) jointly with WG3 on Management Aspects. – Mangement data types, resource schema, primitives, procedures – See details in Annex I Progress TS-0005 (OMA) & TS-0006 (BBF) – Mapping of basic data types, identifiers, existing resources from TS-0004, DM Server Interactions, New Objects (e.g. CMDH Policies) – See details in Annex I Collaboration with BBF & OMA on management aspects (by ad-hoc meetings) – bulk synchronization, least priviledges, security enironments © 2014 oneM2M Partners 10

11. Next Steps – Abstraction & Semantics Progress TR-0007 (WI-0005: Abstraction & Semantics Study) – To continue investigation on existing activities about Semantics / ontology – To collaboration with PT2 on information model, device types, integration/interworking – Gap analysis of existing solutions versus oneM2M requirements – To prepare integration of Semantics support in the oneM2M Architecture – To work on device abstraction/template (also including aspects related to device classification, WI-0006/TR-0010) – See details in Annex II © 2014 oneM2M Partners TP-2014-0022 11

12. Next Meetings / Calls Conference Calls – MAS#9.1 (Semantics): Mon, Mar 3, 2014, UTC 13:00-15:00 – MAS#9.2: Mon, Mar 10, 2014, UTC 13:00-15:00 – MAS#9.3: Mon, Mar 17, 2014, UTC 13:00-15:00 – oneM2M-BBF-OMA ad hoc #4: Mon, Mar 24th, 2014, UTC 13:00- 15:00 Face-to-Face – MAS#10.0: April 07 - 11, 2014, Berlin, Germany © 2014 oneM2M Partners TP-2014-0022 12

13. Annex I – Next Steps on Management © 2014 oneM2M Partners TP-2014-0022 13

14. TS-004 Management Data Types – CMDH policies and other Complex Types as well as Enumerations CMDH- Qualcomm Other types – all contributors of relevant resources MgmtObj – Huawei, LGE, QC (CMDH) – Resources (e.g. schema) – Primitives and Procedures – Individual Management Definitions MgmtCmd - IDCC – Resources (e.g. schema) – Primitives and Procedures © 2014 oneM2M Partners TP-2014-0022 14

15. TS-005 OMA Work on – OMA-DM 1x: Huawei, LGE, – OMA-DM 2x: LGE, Gemalto – LWM2M: LGE, Gemalto, Ericsson Mapping of basic data types, identifiers, existing resources from TS-0004 DM Server Interactions New Objects – CMDH – QC © 2014 oneM2M Partners TP-2014-0022 15

16. TS-006 - BBF In general – ALU, Cisco Mapping of basic data types, identifiers, existing resources from TS-0004 DM Server Interactions New Objects – CMDH – QC © 2014 oneM2M Partners TP-2014-0022 16

17. Annex II – Next Steps on Device Abstraction & Semantics © 2014 oneM2M Partners TP-2014-0022 17

18. Today deliverable status o TR-0007 Study of Abstraction and Semantics Enablements provides o guideline example for mapping Information Models into oneM2M Resources  Proposal: oneM2M should encourage external bodies, who wish to interwork with oneM2M, that Information Models should be published as XSD files. more details in §6.1.2. o the semantic relation between each concrete instance (e.g. the ZigBee Information Model) and the common super type (the Abstraction Information Model) has to be modelled.  Proposal: to add semantic information by linking resources to ontology concepts, e.g. as specified in RDF or OWL ontology files. o Introduction to Semantics-related solutions  ETSI M2M  The OGC Sensor Web Enablement (SWE)  W3C Semantic Sensor Network Ontology o Part of next steps for completion of TR-0007: Gap analysis of existing solutions versus oneM2M requirements needs to be done 18 © 2014 oneM2M Partners TP-2014-0022 18

19. Next steps for WG5 To continue looking at existing activities about Semantics / ontology – encouraging interactive calls with the corresponding projects / SDOs members – analyzing the relevance of the solutions for oneM2M semantics support to progress with PT2 (e.g.HGI, Continua Alliance) on – available information models in their respective domains – device types they have defined / are defining – to concretely look at how to make the glue between oneM2M information model and these ‘vertical’ information models to prepare integration of Semantics support in the oneM2M Architecture – via the interworking proxy entity – … To propose a device classification – related to the device templates 19 © 2014 oneM2M Partners TP-2014-0022 19