Way Forward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG2 Source: Heedong LG Electronics.

Slides:



Advertisements
Similar presentations
Heppenheim Producer-Archive Interface Specification Status of standardisation project Main characteristics, major changes, items pending.
Advertisements

Access Control Mechanism Discussion
Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.
Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:
Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.
WG5 - MAS Progress Report at TP #16 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
3GPP Presence Requirements Requirements for Presence Service based on 3GPP specifications and wireless environment characteristics draft-kiss-simple-presence-wireless-
Group:WG3 (PRO) Source:Peter Niblett, IBM, Date: Agenda:PRO#14 TS-0004 Data Representation Proposal Discussion.
WG5 - MAS Progress Report at TP #17 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
ISA–The Instrumentation, Systems, and Automation Society SP99 Work Group 2 TR#2 “Second Edition” Long Beach Meeting April 28, 2004.
Report of ETSI NGN IPTV activities Rainer Münch, TISPAN Chairman Presenter: Ian Spiers DOCUMENT #:GSC13-PLEN-56 FOR:Presentation SOURCE:Rainer Münch, Ian.
Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
Group:WG3 (PRO) Source:Peter Niblett, IBM, Date: Agenda:PRO#14 TS-0004 Data Representation Proposal Discussion.
1.1 1 Introduction Foundations of Computer Science  Cengage Learning.
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 5 Advanced Data Modeling.
Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,
Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.
1 OPSAWG Agenda Items 7,8, 9 Juergen Quittek, John Parello, Benoit Claise 78th IETF Meeting, Maastricht, Energy Management Framework / Architecture.
An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
M2M Abstraction & Semantics Group Name: WG5 Source: France Telecom, NEC Europe Ltd., Meeting Date: xx.
HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.
In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:
Potential use case for discussion – Device Abstraction Group Name: WG1/2 Source: Alcatel-Lucent Meeting Date: Joint-REQ-ARC-WGs-call Agenda Item: Use cases.
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.
What and Why? Next steps for oneM2M Semantics Group Name: WG5 Source: Joerg Swetina, Martin Bauer (NEC) Meeting Date: Agenda Item: WI-0005 oneM2M-MAS
App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.
WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.
RDA DAY 1 – part 2 web version 1. 2 When you catalog a “book” in hand: You are working with a FRBR Group 1 Item The bibliographic record you create will.
NIST BIG DATA WG Reference Architecture Subgroup Agenda for the Subgroup Call Co-chairs: Orit Levin (Microsoft) James Ketner (AT&T) Don Krapohl (Augmented.
Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.
WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.
Proposal for WG3 & WG5 work area split
Architectural Principles for Services Group Name: WG2- ARC Source: Tim Carey, ALU, Meeting Date: Agenda Item:
Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:
Work for the next release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,
Wayforward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG5 Source: Heedong LG Electronics.
WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to
WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.
Smart Home for disabled people Students: Atara Gutman and Anastasia Logvinenko Instructor: Alexander Kinko PDR presentation Semester Spring part.
Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.
Scenarios for oneM2M and OIC Interworking
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.
Introducing WI Proposal about Authorization Architecture and Policy Group Name: WG4 Source: Wei Zhou, Datang, Meeting Date: Agenda Item:
OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,
Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless
WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.
WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Reading in Business Administration Center for Academic and Technology Support.
Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.
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.
CLUE Framework 01 – comments and issues Interim meeting October 2011 Roni Even.
WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:
Discussion on oneM2M and OSGi Interworking Group Name: ARC Source: Jessie, Huawei, Meeting Date: Agenda Item:
WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,
TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.
Introducing User’s Role concept Group Name: WG2(ARC) and WG4(SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
Overview of oneM2M Home Appliances Information Model
Proposed design principles for modelling interworked devices
WPM ad-hoc group report TP#24
WPM ad-hoc group report TP#25
3GPP Interworking Abstraction
Considering issues regarding handling token
Data Mining Concept Description
Item 5.2 Standardised social variables
Presentation transcript:

Way Forward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG2 Source: Heedong LG Electronics Meeting Date: Agenda Item: TS-0001

Introduction In WG5, the abstract information model is developing for home appliances such as washer, refrigerator as working of TR – In order to avoid cumbersome process between application developers, the abstract information model provides common information model. In this contribution, we introduce the abstract information model for home appliances and discuss way forward to apply them in the architecture scope. – The developed model needs to be mapped to resource structure. 2

Design Principle (one of candidates) Common Characteristic Device-specific Characteristic Vendor-specific Characteristic Home appliances (e.g., TV, airconditioner, Washer…) [Source] Chapter “Design Principle: Approach 1” in TR-0017 To avoid duplicating the description For describe device-specific characteristics For un-predefined characteristic in abstract information model

Example (Washer) Characteristic Name Data TypeValuePermissionDescription deviceFirmwareVerxs:string-RWFirmware version deviceModel Name xs:string-RODevice model name deviceIDxs:string-RODevice ID waterFlowxs:nonNegativeInteger 0: None 1: Strong 2: Normal 3: Weak ROConfigured water flow information remainTimexs:string-RORemain time (HHMM) vendorSpecificundefined Common Device -specific Vendor -specific [Source] Chapter “Abstract Information Model: Approach 1” in TR-0017

Mapping to Resource Structure (1/5) How to map the developed abstract information model with resource structure? – Although we can utilize existing resource types (such as, ), we introduce the specialized resource types for the abstract information of home appliances (as ) – Here, the specialization concept of is similar to. 5

Mapping to Resource Structure (2/5) The resource type is used to represent a device information 1 0..n (L) vendorSpecific Instantiation of resource type 1 0..n 0..1(L) 0..1 vendorspecific [switch] switch temperature 1 deviceFirmwareVer deviceModelName a 1 R02324F32 Status = on [temperature] 0..1 Common Attribute specialization of Vendor-Specific Attribute coldStorage = -13 Boolean Interger Unit = 1 (celcius) Enum Refrige_LGE New resource type

0..1(L) 0..n [functionAttribute] accessControlPolicyIDs [switch] 0..1(L) 0..n 0..1 accessControlPolicyIDs 0..1 coldStorage Unit Interger Enum specialization of Mapping to Resource Structure (3/5) New resource type The specialized resource (such as [switch]) is similar to the [battery] in MgmtObj.

Mapping to Resource Structure (4/5) Why do we use new resource type instead of existing resources? – Effective management E.g., if a user wants to receive the notification by changing the “switch” functionality Each resource type has resource type as a child resource – Access control E.g., different access control policy can be applied for each device-specific feature 8

Refrige_LGE common_Char deviceFirmwareVer = a deviceModelName = R02324F32 … content attribute switch Status = on … content attribute temperature Unit = 1 (celcius) coldStorage = -13 … content attribute switch temperature a 1 R02324F32 Status = on coldStorage = -13 Unit = 1 (celcius) Refrige_LGE Smarthome Washer_LGE Using Mapping to Resource Structure (5/5) Smarthome Washer_LGE Using

How to Combine Two Resource Types to Represent a Device 10 RefrigeratorWasherLight switch brightnesstemperature Instantiated Resource of Instantiated Resource of a specialized

Way Forward After discussion, – Discuss and make a list of common/device-specific characteristics for appliance or devices(WG5) – Decide data types of common/device-specific characteristics (WG5/WG3) – Agree to the proposed resource types (WG2/WG5) 11