hgiâ€s smart home task force and device abstraction requirements

HGI‘s Smart Home Task Force

and Device Abstraction Requirements

Presentation for ETSI M2M WorkshopOctober, 2012

Duncan Bees, HGI CTO/CBO, [email protected] Bees, HGI CTO/CBO, [email protected]

Lindsay Frost, NEC [email protected]

“CONNECTING HOMES – ENABLING SERVICES”

HGI: Two focus areas - One aspiration

CONNECTING HOMES

Creating an ecosystem

for the

2

ENABLING SERVICES

for the digital home

Cooperating with external partners

to unify the smart home ecosystemETSI M2M Workshop, October 2012. (C) HGI

HGI: Connecting Homes, Enabling Services

ETSI M2M Workshop, October 2012. (C) HGI

Liaison Partners & Cooperators

CECED Smart

Grid Group

Energy@Home

4

... And others


How we approached the Smart Home

Phase 1

Home Gateway Energy Efficiency

Phase 2

Home Network Energy Efficiency

Phase 3

5

Phase 3

Home Energy Management (HEM)

Service

Smart Home Services Platform

HEM + other services

SWEX - HG Requirements for

Software Modularity

Energy Efficiency work in 3 phases

FXS

FXS phone

DECT phone

PS

Phase 1

Phase 3

Fridge

Washing machine

Phase 2

int. PS

PS

6

ETH

Wi-Fi

DECT

USB WANLED

STB

Wi-Fi device

USB device

PS

Ethernet device

Heating

Air condition

Consumer electronics

Home Gateway

CPUint. PS

PS

PS

PS

Home Network

Home Energy Management and Control


Smart Meter Interface

New HGI Requirements Project:

“HG requirements for local communication with a smart

meter”

� Smart Meter interfaces depend on national or state level state

jurisdiction.

� The HG must be able to deal with already-defined national � The HG must be able to deal with already-defined national

interfaces.

� HGI will define a core set of common functionality required in

the HG

� HGI will aim to minimise national customisation

DMS # HGI5678

LED by the major HGI Service Providers with vendor input

SW modularity Enables the SH-HG

SWEX (Software Execution Environment) framework provides

key attributes to allow local applications

� Modularisation

� Resource sharingHGI results:

� Generic requirements � Security

� Reuseability

� Flexibility

� Logging

� Life cycle management

� Configuration Management

� Generic requirements

for SWEX

� Specific requirements

for OSGi

� Hardware and Software

requirements for HG’s

� Test Event requirements

for HG’s

8ETSI M2M Workshop, October 2012. (C) HGI

SH-GW as Connection Hub & Service Enabler

Smart Home GW

PC

TV

SmartPhone

„The Phone“

Note-book

PlatformProvider

ASP_1

ASP_2 ASP_3

ASP_xSmart

Home GW

&

APPS

Tablet

GameConsole

Blended Home

Services

CordlessPhone

ALL ACCESS

Provider

• Specifying the Smart Home Platform

• Forging an Ecosystem


The Smart Home Service Gateway is …

The Hub of the home network

A 24/7 – AlwaysOn Device

Always secure connected with QoS

Managed point of service presence

A reliable 3rd party apps environment


Scope of Smart Home Task ForceSpecify requirements and guidelines for

• the business/service models

• service use cases

• technical architecture (hardware/software/interfaces)

• detailed technical requirements

For a specific set of smart home services:

• Home Energy ManagementAlready published HGI-GD017

HEM Architecture & Use Cases• Home Energy Management

• Ambient Assisted Living / eHealth

• Alarms & Security

• Comfort

• Media / NG Communications

Define Architecture

Test-requirements for the HG Test Plan

Promote cooperation with ETSI M2M, OSGi, OneM2M, BBF,

and other partners to unify the smart home architecture

HEM Architecture & Use Cases


SWEX testing already part of

HGI test events since 2010

Business Models

� Platform & Services provided by the

Broadband Service Provider

� Services provided by an Applications Service

Provider

� Full Apps Store model� Full Apps Store model

12

SH Project Technical Goals

� Define s/w reference points, feature requirements, and

test requirements within the HGI Smart Home

architecture

� Support for local applications, cloud applications, and a

mixmix

� Device abstraction to enable applications to access

devices without requiring detailed interconnect

knowledge.

� Primary interest for the cloud interface is ETSI M2M, but

other approaches should be enabled

13

The Home Gateway as an instantiation of an

M2M Gateway for the Home


App1 App2

localUSER

controlby

TABLET or TV etc

SWEX enabled

interaction of APPx

RP5

I/F Requ.RP1

M2M Frameworkin cloud

RP4

3rd Party APPs in aFlexible SWEX Framework

hard

ware

box

soft

ware

environm

ent

Interworking

S/W between Cloud and

HGW

Home Gateway

HGI Architecture (draft)

RP3

Physical H/W(USB dongle, chip in GW, LAN, WiFi)

Wired or Wireless Communication

Generic Driver

OS

Driver(native)

H/W Requ.

Diverse Home Devices

I/F Requ.

Z-Wave ZigbeeEchonet Lite

Serial Bundle

OS Serial

Driver(native)

DECT ULE

USB Bundle

OS USB

Driver(native)

IP Driver

OS

Driver(native)

CoAP

SWEX implementation of an Abstraction Layer (includes PASS-THROUGH)

Devices/Sensors (d)D' (ETSI M2M enabled device)

soft

ware

environm

ent

RP2RP2RP2RP2RP2RP2

App1 App2

localUSER

controlby

TABLET or TV etc

SWEX enabled

interaction of APPx

RP5

I/F Requ.RP1

M2M Framework

in cloud

RP4

3rd Party APPs in aFlexible SWEX Framework

hard

ware

box

soft

ware

environm

ent

Interworking

S/W between Cloud and

HGW

Home Gateway

AnnotationETSI M2M (BBF CSDA)

SDOs should agree a common

representation of devices

RP3

Physical H/W(USB dongle, chip in GW, LAN, WiFi)

Wired or Wireless Communication

Generic Driver

OS

Driver(native)

H/W Requ.

Diverse Home Devices

I/F Requ.

Z-Wave ZigbeeEchonet Lite

Serial Bundle

OS Serial

Driver(native)

DECT ULE

RPi

USB Bundle

OS USB

Driver(native)

RPiRPiRPi

IP Driver

OS

Driver(native)

CoAP

RPi

SWEX implmentation of an Abstraction Layer (includes PASS-THROUGH)

Devices/Sensors (d)D' (ETSI M2M enabled device)

soft

ware

environm

ent

RP2RP2RP2RP2RP2RP2

HGI Reference Points (draft)

� RP1 – Provides a common representation of devices for

applications

� RP2 – Provides a direct access for applications to the

device protocols

� RP3 – Provides “higher-level” service application interface

17

� RP3 – Provides “higher-level” service application interface

� RP4 – Provides a representation of the abstraction

interface to the cloud (ETSI M2M mId)

� RP5 – Provides access to local user interface. This could

be a functional requirement, or a standardised

representation of data used to drive the local interface

Device Abstraction Layer� Implemented in the SWEX framework

� Used by local applications to address HAN connected

devices without awareness of technology-specific details

� Can also be used by M2M framework to address these

devices

� Top levelTop level

� Generic commands available to applications

� Common data model

� Bottom level

� technology specific semantic/data model

HGI is currently exploring best approach for the abstraction

layer and welcomes cooperation with liaison partners


M2M parts

� The SH-HG plays the role of an M2M Gateway

� Interworking software is needed to connect M2M

mld to RP1

� Gateway Service Capability Layer is instantiated on

HG

19

HG

� GSCL will store/mirror state of connected devices. Device

state representation within the overall picture is being

discussed.

� May run as a module within the SWEX framework, or in

native code

HGI SH TF will explore the integration of the M2M

components within the architecture – input welcomed.


Security Requirements

� Many Smart Home use-cases have high need for data

security considerations.

� Example: smart meter

� Data ownership issues

� Data privacy� Data privacy

� Integrity and Safety issues

� HGI has started a security project to address current

needs for HG based security approaches.

20

Summary �� Next Steps

� Needed for a Smart Home Ecosystem

� development environment

� APIs/reference points

� Device representation with appropriate abstraction

� Cross-SDO collaboration to define device representation

and abstraction and abstraction

� HGI 2012 Test Event, November-December, 2012,

including SWEX requirements for HG

For more information please contact

[email protected]

Next HGI meeting is December 11-14 in Tokyo – observers are

welcomed


hgiâ€s smart home task force and device abstraction requirements

Documents