On Management, Abstraction & Semantics

Transcription

1 On, Abstraction & Semantics Yongjing Zhang Standard Research Lead, Carrier Software BU, Huawei Technologies Co., Ltd. onem2m

2 Agenda Concepts about M.A.S. The Capabilities in onem2m Architecture Resource modeling Protocol mapping The Generic Abstraction & Semantic Capabilities in onem2m Resource modeling Interworking framework Semantic enhancement Evolution roadmap Conclusion 27-Nov onem2m 2

3 Why M.A.S. IoT Applications Home Transport Health Energy Retail ABSTRACTed APIs onem2m Common Information Model & SEMANTICS Common Service Functions (e.g. MANAGEMENT) ZigBee KNX BLE ZWave mbus 3GPP/2 OMA BBF Heterogeneous Networks, s, Interfaces 27-Nov onem2m 3

4 Representation creation Representation creation Representation creation Abstraction: generalizing the information model Interworking: mapping Information between model two specific technologies to enable the information proprietary) exchange between heterogeneous systems Concepts - Abstraction Information Models of devices to hide the complexity of the specific technologies by providing a single format to represent devices and unified methods directly usable by the applications. Representations of Systems (standardized or Applications may still need to understand the native Example: information model (e.g. Zigbee profile) <xml> Description of data and procedures of N device Data: ABC procedure: abc (params) interworking Native device Native System (Technology) ZigBee On/Off Switch in a ZigBee network Abstraction: (manual) mapping data and procedures between Native and Abstract devices Interworking Proxy function ZigBee On/Off Switch interworked in onem2m <xml> Description of data and procedures of Abstract device Abstract M2M onem2m System Abstract Binary in onem2m Abstraction: (manual) mapping data and procedures between Native and Abstract devices Interworking Proxy function <xml> Description of data and procedures of N device interworking BACnet Binary Input Object interworked in onem2m Data: XYZ procedure: xyz (params) N ative device Interworking is the basis for Abstraction other Native System BACnet Binary Input Object in a BACnet nwk 27-Nov onem2m 4

5 Room: bedrooma, indoorrooma, indoor- Room: bed- Thing Type temperature temperature meaningfulness Thing Type Concepts - Semantics Semantics: adding the meaning and relationships between concepts (e.g. data, devices, things) and their instances to enable machine understandable interoperability without a-priori agreement or configuration between communication parties the formal specification of a conceptualization is done by 'ontology', which provides unambiguous vocabulary and model about objects, measurands, their properties and relationships. Data Data Temperature Temperature Physical TypePhysical Type20,5 C 20,5 C Data Type Raw Data Float: 20,5 Data Type Raw Data 0000 Float: 20, Description Description Measures indoor Measures indoor Type: Type: temperature temperature Temperature Temperature of bedroomaof bedrooma Sensor Sensor Levels of meaningfullness Application translation into Semantics is the evolution of Abstraction. Application-level command e.g. lower the living room temperature Semantic support helps understanding the original data, and the relationships between things, data, Measures a Measures Manufacturer a Manufacturer 2. Abstract device-level command temperature temperature Energy Energy Abstract Information e.g. "switch off the radiator with ID=00007 in Celsius in Celsius Model Abstraction of the specific technologies Returns a Returns a mapping into (syntactic support) float value float value 3. Techno-specific device-level command Sensor_8 Sensor_8 e.g. "send the command <ZigBee Specific Command> to endpoint ID=<ZigBee specific ID>" Abstraction vs. Semantic 27-Nov onem2m 5

6 Concepts - : the management (configuration, monitoring, trouble shooting, upgrade, etc.) of devices (ADN/ASN/NoDN), applications (AEs) and common service entities (CSEs) to provid 'Abstracted' unified & simplified management APIs for M2M applications. is essentially a specific aspect of onem2m Abstraction framework: Data models: the resources describing the mgmt capabilities, properties and status Operations: the actions performing mgmt tasks, e.g. download (firmware), get (status) or set (properties), execute (software installation) OMA Mgmt Applications onem2m Abstraction (data models & operations) BBF is a specific aspect of Abstraction 27-Nov onem2m 6

7 Capabilities Configuration Function (CF) Software Function (SMF) Managed Entity Configuration Function (DCF) Diagnostic and Monitoring Function (DDMF) Firmware Function (DFMF) Topology Function (DTMF) Common Services Entity (CSE) M2M / Gateway Application Entity (AE) M2M Area Network Application & Service Layer (ASM CSF) Configuration (e.g. CMDH Policy configuration) Software (e.g. download/ install/ activation): Common Services Entity (CSE) Application and Service Layer Discovery Registration Communication / Delivery Handling Group Security Application Entity (AE) Underlying Network Service Entity (NSE) Mca Reference Point Data & Repository Location Service Charging & Accounting Mcn Reference Point Network Service Exposure/Service Ex+Triggering Subscription and Notification (DMG CSF) Mcc Reference Point Configuration (e.g. enable/ disable capabilities, provisioning) Diagnostics and Monitoring (e.g. memory, battery, event logs, reboot) Firmware Topology (e.g. Area Network topology & characteristics ) 27-Nov onem2m 7

8 Architecture IN-DMG-MA Protocol Translation Interaction with the Mgmt Server Mgmt Server selection Discovery of external mgmt objects IN-AE Mca onem2m abstracted mgmt APIs (HTTP/CoAP/MQTT) MN/ASN IN CSE CSE Out of Scope DMG Adapter Mcc DMG Adapter in M2M Area Network la ms Invoking underlying mgmt server functions, Receiving mgmt results Proxy Client mp Proxy Client mc Server Managing Area Nwk & s (technology specific) Performing actual mgmt tasks by reusing existing techs (e.g. OMA, BBF) 27-Nov onem2m 8

9 Architecture MN-DMG-MA or ASN-DMG-MA Mapping between the DMG and Client Interaction with the Mgmt Client IN-AE Mca onem2m abstracted mgmt APIs (HTTP/CoAP/MQTT) MN/ASN CSE Mgmt resource creation, Service layer mgmt IN CSE Out of Scope DMG Adapter Mcc DMG Adapter in M2M Area Network Local mgmt objects discovery la ms Proxy Client mp Proxy Client mc Server 27-Nov onem2m 9

10 Specialization Abstraction onem2m TS-000 (ARC)/ TS-0004 (PRO) <mgmtobj> 0.. (L) 0.. (L) Generic Mgmt Resource Model mgmtdefinition objectids objectpaths A specialized mgmt func. type (e.g. "software") Tech-specific mapping info Application &Service Layer Mgmt [software] [cmdhpolicy] Mgmt 0.. (L) mgmtlink Link to sub-resources [firmware] [deviceinfo] [devicecapability] 0.. (L) n [objectattribute] description <subscription> Attributes to be specialized for a specific mgmt func. [eventlog] [battery] [memory] [areanwkinfo] [areanwkinfo] [reboot] 27-Nov onem2m 0

11 Specialization Abstraction onem2m TS-000 (ARC)/ TS-0004 (PRO) <mgmtobj> 0.. (L) 0.. (L) Generic Mgmt Resource Model mgmtdefinition objectids objectpaths A specialized mgmt func. type (e.g. "software") Tech-specific mapping info Application &Service Layer Mgmt [software] [cmdhpolicy] Mgmt 0.. (L) mgmtlink Link to sub-resources [firmware] [deviceinfo] [devicecapability] 0.. (L) n [objectattribute] description <subscription> Attributes to be specialized for a specific mgmt func. [eventlog] [battery] [memory] [areanwkinfo] [areanwkinfo] [reboot] onem2m TS-0005 (OMA) Mapping onem2m TS-0006 (BBF) OMA DM.X FUMO SCOMO DevInfo DiagMO OMA DM 2.0 OMA LWM2M Object Firmware Update Object Software Mgmt Object BBF TR069/TR8 Info SoftwareModules X_oneM2M_ 27-Nov onem2m

12 Abstraction <mgmtcmd> n description cmdtype execreqargs execenable exectarget execmode execfrequency execdelay execnumber <subscription> onem2m TS-000 (ARC)/ TS-0004 (PRO) Generic Resource Model for RPC-like mgmt commands (BBF TR069) RPC cmd type (e.g. "download") Cmd arguments (opaque) Trigger of execution (by 'UPDATE') Target device(s) (<node> or <group> URI) Execution mode(e.g. 'repeated') In association with execution mode <execinstance> (L) * Each execution creates a <execinstance> to maintain the execution status and result execstatus execresult execdisable exectarget execmode execfrequency execdelay execnumber execreqargs Cancel a pending cmd Inherit from the parent <mgmtcmd> <execinstance> 0..n <subscription> 27-Nov onem2m 2

13 Abstraction <mgmtcmd> n description cmdtype execreqargs execenable exectarget execmode execfrequency execdelay execnumber <subscription> onem2m TS-000 (ARC)/ TS-0004 (PRO) Generic Resource Model for RPC-like mgmt commands (BBF TR069) RPC cmd type (e.g. "download") Cmd arguments (opaque) Trigger of execution (by 'UPDATE') Target device(s) (<node> or <group> URI) Execution mode(e.g. 'repeated') In association with execution mode <execinstance> (L) * Each execution creates a <execinstance> to maintain the execution status and result execstatus execresult execdisable exectarget execmode execfrequency execdelay execnumber execreqargs Cancel a pending cmd Inherit from the parent <mgmtcmd> <execinstance> 0..n <subscription> Mapping onem2m TS-0006 (BBF) BBF TR069 RESET REBOOT UPLOAD DOWNLOAD SOFTWAREINSTALL SOFTWAREUNINSTALL 27-Nov onem2m 3

14 Example Flow IN-AE IN-CSE Mgmt Adaptor Mgmt Server Mgmt Client Mgmt Adaptor MN/ASN-CSE <IN-CSEbase> <ASN-remoteCSE> <ASN-node> [deviceinfo] [battery] [firmware] [ ] RETRIEVE [battery] Registration, CREATE <ASN-node> Resource creation CREATE <deviceinfo>, <battery>, <firmware> Resource creation Invoke battery monitoring Local mgt objects discovery Keep in sync by UPDATE Battery info Mgmt Session (e.g. DM/TR069) [battery] representation UPDATE [firmware] [battery] update Invoke firmware update OK Mgmt Session (e.g. DM/TR069) OK [firmware] update 27-Nov onem2m 4

15 Generic Abstraction/Semantics Resource types <AE>, <container> & <contentinstance> are used for the abstraction of M2M applications, data collection and instances.. Common Services Entity (CSE) Application and Service Layer Discovery Registration Communication / Delivery Handling Group Security Application Entity (AE) Mca Reference Point Data & Repository Location Service Charging & Accounting Underlying Network Service Entity (NSE) Mcn Reference Point Network Service Exposure/Service Ex+Triggering Subscription and Notification Application Mcc Reference Point <AE> 0.. (L) 0.. (L) n <contentinstance> appname App-ID AE-ID pointofaccess ontologyref <container> Data instance typeofcontent contentsize ontologyref content Data collection <container> n 0..n creator maxnrofinstances maxbytesize ontologyref <contentinstance> <container> Hierarchical data collection <container> 27-Nov onem2m 5

16 Generic Abstraction/Semantics Resource types <AE>, <container> & <contentinstance> are used for the abstraction of M2M applications, data collection and instances.. Attribute 'ontologyref' is to provide the semantic annotation (meaning) for application and data. It's the rudimentary step towards semantic capability enablement. Common Services Entity (CSE) Application and Service Layer Discovery Registration Communication / Delivery Handling Group Security Application Entity (AE) Mca Reference Point Data & Repository Location Service Charging & Accounting Underlying Network Service Entity (NSE) Mcn Reference Point Network Service Exposure/Service Ex+Triggering Subscription and Notification Application Mcc Reference Point <AE> 0.. (L) 0.. (L) n <contentinstance> appname App-ID AE-ID pointofaccess ontologyref <container> Data instance typeofcontent contentsize ontologyref content Data collection <container> n 0..n creator maxnrofinstances maxbytesize ontologyref <contentinstance> <container> Hierarchical data collection <container> 27-Nov onem2m 6

17 Interworking with non-onem2m (Informative) The Inter-working Proxy Application Entity (IPE) abstracts and maps the non-onem2m data model to the onem2m resources exposed via the Mca reference point Sensor/Meter Mbus/COSEM IPE Mca Application Service Node CSE Sensor/Meter Zigbee telco Profile IPE Mca Mcc Common Data model Awareness specific Data model Awareness Translation of non-onem2m Data Model to onem2m Specific Data Model Utily Application CSE Mca Infrastructure Node n Data Field IPE n M2M Area Network n n Application n Interface n Method <AE> ZigBee. DLMS/COSEM. Zwave. BACnet. ANSI C2. mbus. <AE>, <container>, <contentinstance> Generic data modeling of interworking 27-Nov onem2m 7

18 Interworking Proxy Application Entity Interface Parameter Interworking Enhancement (Informative) n M2M Area Network hasm2marea- Network n hasinterface- Parameter n Non-oneM2M n Function Block n hasnononem2m hasfunctionblock hasinterface n with Semantics n M2M Area Network hasm2marea- Parameter NetworkParameter n hasnononem2m- Parameter n hasfunction- BlockParameter Data Field hasdatafield Interface hasmethod Method n Non-oneM2M Parameter Function Block Parameter n Method Parameter hasmethodparameter A generic semantic concept model (ontology) representing an Area Network [non-onem2m application] ontologyref hasfunctionblock <contentinstance> 27-Nov onem2m 8 <contentinstance> content <AE> *Semantic URI ontologyref [FunctionBlock] ontologyref latest [FunctionBlock] <container> content * Attribute hasnon-onem2mparameter 'ontologyref' links to the ontology definition of each concept ontologyref (e.g. 'FunctionBlock'). [Non-oneM2MParameter] ontologyref latest *Semantic URI <container> *Semantic URI <contentinstance> <container> An example of mapping to onem2m resources

19 Roadmap to Semantic Enablement (Informative) Concepts Types Instances Is realized by Super Type My 234 Is of type hasoperation Operation Is realized by MyOperation hasparameter Parameter Is of type Type Type 2 Parameter m MyOperation Inherited from Super Type Operation n MyOperation 2 Type.a Specific Operation of Type Is of type Operation Super Type MyOperation Is of type MyParameter 7 MyOperation 2 Is of type MyParameter 3. Use of Semantic Technologies for specific Platform Functionalities Operation Type Operation Type 2 MyParameter MyParameter 7. Semantic Modeling (Ontology) 4. Full Semantic Platform 2. Semantic Annotation 27-Nov onem2m 9

20 Roadmap to Semantic Enablement (Informative) Concepts Types Instances Is realized by Super Type My 234 Is of type Operation Is realized by MyOperation MyOperation hasoperation hasparameter Operation n Parameter Parameter m Type.a Type Type 2 MyOperation Inherited from Super Type MyOperation 2 Is of type Is of type MyParameter 7 MyOperation 2 Is of type MyParameter Operation Super Type Specific Operation of Type Is of type Operation Type Operation Type 2 MyParameter MyParameter 7. Semantic Modeling (Ontology) 27-Nov onem2m 20

21 Roadmap to Semantic Enablement (Informative) 2. Semantic Annotation 27-Nov onem2m 2

22 Roadmap to Semantic Enablement (Informative) 3. Use of Semantic Technologies for specific Platform Functionalities 27-Nov onem2m 22

23 Roadmap to Semantic Enablement (Informative) 4. Full Semantic Platform 27-Nov onem2m 23

24 onem2m Common Service Layer Conclusion Applications Semantics Annotation Ontology Query Reasoning Mash-up <AE> (e.g. IPE), <container>, <contentinstance>, Abstraction Interworking [battery], [memory], [deviceinfo], [software], [firmware], <mgmtobj>, <mgmtcmd> Technology-specific ZigBee KNX OMA BBF Abstraction Semantics 27-Nov onem2m 24

25 Join us at the onem2m showcase event 27-Nov onem2m 25

26