1. 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

2. Contents Background Description Source Actors Pre-conditions Triggers Normal Flow Alternate Flow Post-conditions High Level Illustration Potential requirements

3. Background Device Abstraction is a capability of a horizontal M2M Platform that removes the need for M2M Applications to understand the control protocols of Devices. Industry segment organisations: none known Industry segment standards: BBF, HGI, ETZSI Methods – Device Identification – Discovery of Device Functions – Abstract Function Definition – Translation from Abstract Functions to Device Functions

4. Description – 3 sub-use cases Device Abstraction allows for M2M Applications to control Devices without the need to understand the Device’s control protocol: Device Coordination – M2M Applications contain business logic that requires control of multiple Devices where the Devices have different control protocols. Device Events – A Device emits an event based to M2M Applications. The M2M Applications can then respond to the event similar to Use Case Device Coordination Device Replacement – A Device that supports one control protocol is replaced with a Device that supports a different control protocol.

5. Source (as applicable) Broadband Forum – PD-282 Control Plane Home Gateway Initiative – Smart Home

6. Actors (as applicable) Network M2M Application Local M2M Application Interworking Proxy aim is to Translate between technology specific Information Model and the Abstract Information Model Device

7. Pre-conditions (if any) See sub-case flows

8. Triggers (if any) See sub-case flows

9. Normal Flow (as applicable) See sub-case flows

10. Sub use case 1 – Device Coordination Summary: (no atomic action steps) Trigger: M2M Application initiate requests Action: Prepare home for occupation Detailed flow (no confirmation, etc. – actors in “quotes”, system under study in italics) 1)Local M2M Application sets specified Lights to “On” to Interworking Proxy – Interworking Proxy translate Abstract Function “On” to ZigBee “On” 2)M2M Application sets specified Thermostats to 70 degrees Fahrenheit to Interworking Proxy – Interworking Proxy translate Abstract Function 70 Degrees Fahrenheit to Zwave 21 Degrees Celsius

11. Sub use case 2 – Device Events Summary: (no atomic action steps) Trigger: Device triggers a over temperature event Action: M2M Application reduces temperature Detailed flow (no confirmation, etc. – actors in “quotes”, system under study in italics) 1)Device emits KNX “over temperature” event to Interworking Proxy Interworking Proxy translate KNX “over temperature” to Abstract event “over temperature” Interworking Proxy emits Abstract event to subscribed M2M Applications 2)M2M Application sets specified Thermostats to 70 degrees Fahrenheit to Interworking Proxy (See – sub use case 1)

12. Sub use case 3 – Device Replacement Summary: (no atomic action steps) Trigger: Device triggers a over temperature event Action: M2M Application reduces temperature Detailed flow (no confirmation, etc. – actors in “quotes”, system under study in italics) 1)User replaces ZigBee Light #1 with Zwave Light #2 2)Zwave Device #2 identifies itself and its Device functions (on/off) to the Interworking Proxy 3)Interworking Proxy associates Device #2 Light functions with Abstract Light Functions 4)Interworking Proxy announces Device #2 to subscribed M2M Applications

13. Alternate Flow (if any) Not Applicable to requirements definition

14. Post-conditions (if any) Not Applicable to requirements definition

15. High Level Illustration

16. Interworking Proxy

17. Potential requirements (as applicable) Req NumberCategoryText 1Device AbstractionThe M2M System shall provide the capability for M2M Applications to communicate with a device without the need for the M2M Applications to be aware of the technology specific communication protocol of the device. 3Device Abstraction - Discovery The M2M System shall support one or more globally unique identifiers for the device. These identifiers do not change for the lifetime that the device has associated M2M Services. 4Device Abstraction - Discovery The M2M System shall provide the capability for M2M Applications to discover devices. 5Device Abstraction - Discovery The M2M System shall provide the capability for M2M Applications to discover the functionalities of the device. 6Device Abstraction - Translation The M2M System shall provide the capability to map sets of similar functions of devices to specified abstract functions. 7Device Abstraction - Translation The M2M System shall provide a capability to associate abstract functions with the functionalities of a device. 8Device Abstraction - Translation The M2M System shall provide the capability for M2M Applications to invoke a function of the device through the abstract functions associated with the functionalities of the device. 9Device Abstraction - Ecosystem The M2M system shall provide a semantic/ meta-language model that can map industry-specific information models for end device application functionalities to common and application-agnostic abstract functions that are understood components of the M2M system.