Upload
gervase-stanley
View
212
Download
0
Embed Size (px)
Citation preview
Wayforward of Abstract Information Model (Mapping Model with Resource Structure)
Group Name: WG5Source: Heedong Choi([email protected]), LG Electronics Meeting Date: 2015-05-18Agenda 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)
CommonCharacteristic
Device-specificCharacteristic
Vendor-specificCharacteristic
Home appliances(e.g., TV, airconditioner, Washer…)
[Source] Chapter 5.2.1 “Design Principle: Approach 1” in TR-0017
To avoid duplicatingthe description
For describedevice-specific characteristics
For un-predefined characteristicin abstract information model
Example (Washer)
Characteristic Name
Data Type Value Permission Description
deviceFirmwareVer xs:string - RW Firmware version
deviceModelName
xs:string - RO Device model name
deviceID xs:string - RO Device ID
powerStatus xs:boolean0: off1: on
RW Power status
waterFlow xs:nonNegativeInteger
0: None1: Strong2: Normal3: Weak
RO Configured water flow information
remainTime xs:string - RO Remain time (HHMM)
vendorSpecific undefined
Common
Device-specific
Vendor-specific
[Source] Chapter 5.3.1 “Abstract Information Model: Approach 1” in TR-0017
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
• The [washer] resource is used to share information regarding the washer. The [washer] resource is a specialization of the <homeApplianceProfile>resource.
<subscription>
<homeApplianceProfile>
New resource type
Wayforward (2/3)
0..1(L)
0..n
[commonChar]
0..1(L)[deviceSpecificChar]
0..1(L)vendorSpecificChar
<subscription>
[washer]
Specialization of <homeApplianceProfile> resource type
1
0..n
commonChar_1
0..1(L)
commonChar_2
1deviceSpecificChar_1
deviceSpecificChar_2
1
1
[vendorSpecificChar]
1profileDefinition profileDefinition
1
Specifies the type of <homeApplianceProfile>resource. E.g., washer, refrigerator
Specialization of [commonChar], [deviceSpecificChar], respectively
For un-predefined characteristics, ‘vendorSpecific’ can be generated.
washer_LGE_0001
deviceFirmwareVer
deviceID
deviceID
powerStatus
waterFlow
remainTime
<subscription>
1
LG_specific_char_1
1
1
1
1
1
0..1
1
Naming Convention: “device Type”_ “manufacture”_ “device ID”
Wayforward (3/3)
Naming Convention: Fixed name based on pre-defined abstract information model.
CharacteristicName
Data Type Value Permission
deviceFirmwareVer
xs:string - RW
… … … …
remainTime xs:string - RO
profileDefinition
0..n < Structure of [washer]resource (example) >
Resource Structure Comparison
washer_LGE_0001
ontologyRef
semanticDescriptor
< Resource structure with semantics >
A user can manipulate the washer with common dictionary.
< Resource structure with pre-definedabstract information model >
powerStatus
washer_LGE_0001
ontologyRef
semanticDescriptor
powerStatus
A user can manipulate the washer with semantic dictionary.