Wayforward of Abstract Information Model (Mapping Model with Resource Structure) Group Name: WG5 Source: Heedong Choi([email protected]), LG Electronics Meeting Date: 2015-05-18 Agenda Item: TR-0017 Introduction • In WG5, the abstract information model is developing for home appliances such as washer, refrigerator as working of TR-0017. – 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 wayforward to apply them in the architecture scope. – The developed model needs to be mapped to resource structure. 2 Design Principle (one of candidates) Home appliances (e.g., TV, airconditioner, Washer…) Common Characteristic Device-specific Characteristic To avoid duplicating the description For describe device-specific characteristics [Source] Chapter 5.2.1 “Design Principle: Approach 1” in TR-0017 Vendor-specific Characteristic For un-predefined characteristic in abstract information model Example (Washer) Common Device -specific Vendor -specific Characteristic Name Data Type Value Permission deviceFirmwareVer xs:string - RW Firmware version deviceModel Name xs:string - RO Device model name deviceID xs:string - RO Device ID powerStatus xs:boolean 0: off 1: on RW Power status RO Configured water flow information RO Remain time (HHMM) waterFlow xs:nonNegativeInteger 0: None 1: Strong 2: Normal 3: Weak remainTime xs:string - vendorSpecific [Source] Chapter 5.3.1 “Abstract Information Model: Approach 1” in TR-0017 undefined Description Wayforward (1/3) • How to map the developed abstract information model with resource structure? – Although we can utilize existing resource types (such as <container>, <contentInstance>), we introduce the specialized resource types for the abstract information of home appliances (as <homeApplianceProfile>) – Here, the specialization concept of <homeApplianceProfile> is equivalent to <mgmtObj>. 5 Wayforward (2/3) • The [washer] resource is used to share information regarding the washer. The [washer] resource is a specialization of the <homeApplianceProfile>resource. New resource type Specialization of <homeApplianceProfile> resource type [washer] <homeApplianceProfile> 1 0..1(L) [commonChar] 0..1(L) 1 [deviceSpecificChar] Specialization of [commonChar], [deviceSpecificChar], respectively 1 1 0..1(L) vendorSpecificChar Specifies the type of <homeApplianceProfile> resource. E.g., washer, refrigerator 1 0..n 0..1(L) 1 profileDefinition <subscription> 0..n commonChar_1 commonChar_2 deviceSpecificChar_1 deviceSpecificChar_2 [vendorSpecificChar] profileDefinition <subscription> Wayforward (3/3) Naming Convention : “device Type”_ “manufacture”_ “device ID” Naming Convention : Fixed name based on pre-defined abstract information model. washer_LGE_0001 1 1 1 1 1 1 0..1 1 < Structure of [washer] resource (example) > 0..n deviceFirmwareVer deviceID deviceID Characteristic Name Data Type Value Permission deviceFirmware Ver xs:string - RW … … … … remainTime xs:string - RO powerStatus waterFlow remainTime LG_specific_char_1 profileDefinition <subscription> For un-predefined characteristics, ‘vendorSpecific’ can be generated. Resource Structure Comparison A user can manipulate the washer with common dictionary. A user can manipulate the washer with semantic dictionary. washer_LGE_0001 washer_LGE_0001 ontologyRef ontologyRef semanticDescriptor semanticDescriptor powerStatus powerStatus < Resource structure with pre-defined abstract information model > < Resource structure with semantics >
© Copyright 2026 Paperzz