1 / 16

SMART HOME Expectation IN STANDARDS

SMART HOME Expectation IN STANDARDS. Philippe Calvet , Board Member of Home Gateway Initiative, Manager in ORANGE Patricia MARTIGNE, Smart Home & M2M Standardization Manager, ORANGE. GSC-18 Meeting, 22-23 July 2014, Sophia Antipolis, France. CONTENT OF THE PRESENTATION.

nolen
Download Presentation

SMART HOME Expectation IN STANDARDS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SMART HOME Expectation IN STANDARDS Philippe Calvet, Board Member of Home Gateway Initiative, Manager in ORANGE Patricia MARTIGNE, Smart Home & M2M Standardization Manager, ORANGE GSC-18 Meeting, 22-23 July 2014, Sophia Antipolis, France

  2. CONTENT OF THE PRESENTATION • Smart Home (SH) Markettoday • Smart Home evolution • HGI Enablers for Smart Home • Smart Home expectations with regard to IoT/M2M Standards GSC-18, 22-23 July 2014, Sophia Antipolis

  3. The SMART MARKET TODAY • Some examples … GSC-18, 22-23 July 2014, Sophia Antipolis

  4. Smart Home Services Evolution Integrated Smart Home Services Home Automation Services Home Automation Services Home Automation Services • Common approach to smart home services • HG Platform delivered by BSP • BSP and Partner Cloud Platforms • Application can be delivered by partners • GUI based service control • Remote Access • Per service • Platform • Ordering • Service control • Scheduling • Remote monitoring • User expectations for the control of smart home: • - Better user interfaces (smart phone/tablets) • Access from anywhere (in home, out of home) • Homogeneous installation (“Plug&Play”) mechanisms • Evolution of the services GSC-18, 22-23 July 2014, Sophia Antipolis

  5. Challenges addressedby HGI Service PF BSP App PF 3rd Party App PF KEY HGI FOCUS AREA GSC-18, 22-23 July 2014, Sophia Antipolis

  6. From Home Automation … to Smart home Migration towards multi-Service offers Connectivity Selection from the multiple possible technologies. Ecosystem Abstraction layer to hide the connectivity-technologies heterogeneity. Application Development and Device Semantics Enlarging the panel of applications: openness to 3rd party applications. From independently specified semantics of end devices to cross-domain interactions. HGI activities • Enablers for cross-domain interactions • Encouraging application development: SH ref. architecture with open APIs to 3rd parties • A common data model -> HGI/BBF Smart Home Task Force • Connectivity / WHAN requirements • HGI collaborative work with the different technology alliances (ZigBee Alliance, enOcean;etc.) • Ecosystem • Modularity software Requirements GSC-18, 22-23 July 2014, Sophia Antipolis Page 6

  7. Home Gateway Platform for Smart Home Services Access Network / Internet Applications installed on home located gateway platform. Cloud Servicesenabled TR-069 management RP4 M2M App1 App2 AppN Data representation for local GUI RP3 RP1 Smart Home Abstraction Layer (SHAL) HOME GATEWAY PLATFORM RP2 D1 D2 D3 D4 D5 DM Smart home buses connecting to smart home devices and sensors/actuators Reference Points for standards RP.. GSC-18, 22-23 July 2014, Sophia Antipolis

  8. SHAL: SMART HOME ABSTRACTION LAYER A KEY ENABLER FOR SMARTHOME • SHAL: Smart Home Abstraction Layer • Used by local applications to address HAN connected devices without awareness of technology-specific details • Enabled by the HGI Open Platform 2.0 framework • Can also be used by M2M framework to address these devices • Top level • Generic commands available to applications • Common data model • Bottom level • technology specific semantic/data model • Choose a small set of key HANs that span the major operator needs • Pass-through • Direct access to technology specific semantics GSC-18, 22-23 July 2014, Sophia Antipolis

  9. SMART HOME INDUSTRYEXPECTATIONS for IOT/M2M STANDARDs • Standard way to connect Cloud applications to home devices • Learn from (and build on) existing deployments/specs/APIs • An extensible standard supporting • Multiple business models (OTT, Operator-managed, 3rd-Party, etc) • Multiple deployment scenarios (logic in the Cloud, in a HGW, etc) • Unified APIs, independent of underlying HAN technologies, for applications to control home appliances • APIs to interact with devices independent of (wireless) connection technology • Support for enriched Smart Home services • Smart Home Semantics as part of more generic IOT/M2M Semantics, in order to allow for cross-application interactions GSC-18, 22-23 July 2014, Sophia Antipolis

  10. THANK YOU ! GSC-18, 22-23 July 2014, Sophia Antipolis

  11. Supplementary Slides GSC-18, 22-23 July 2014, Sophia Antipolis

  12. Example for Smart Energy Use Case Home Domain Overload Management USE CASE: Mr Martin wants to start his washing machine. The system collects consumption data from the smart meter. Based on washing machine consumption profile and Energy Utility tariffs, the system suggests to defer the start one hour. Operator‘s Data Center NSCL Server M2M App server Mca (mIa) Internet connection Mcc (mId) Internet connection Mr. Martin‘s Home Home Gateway Energy Box Some protocol (Zigbee, Z-Wave etc) Mr. Martin‘s Tablet Smart Meter LAN connection Some protocol(Zigbee, Z-Wave etc) Smart Plugs for older appliances Smart Appliances GSC-18, 22-23 July 2014, Sophia Antipolis

  13. Current Work on WHAN Requirements • Major HGI Operators have discussed requirements for selecting a WHAN interface suitable for smart home services • The document RD039 has just been ratified by the HGI member companies is available to the public at http://www.homegateway.org/documents/Current_HGI_Publications.asp

  14. SW modularity is key HGI Open Platform 2.0 framework provides key attributes to allow local applications • Modularisation • Resource sharing • Security • Reuseability • Flexibility • Logging • Life cycle management • Configuration Management • HGI results: • Generic requirements for Software Modularity • Specific requirements for OSGi • Hardware and Software requirements for HG’s • Test Event onrequirements for HG’s

  15. HGI’s Open Platform 2.0 Requirements, Test Program, and test code A full suite of tests for the Home Gateway on software modularity/ OSGi/ JVM • Test Event uses a remote server to download and automatically run OSGi test bundles by HGI • Extension to Smart Home APIs in future • Service Provider pre-qualification of vendor solutions HGI-RD048 just published See test.homegateway.org for details of test plan

  16. Device Model Template Document Acommon template to represent Smart Home devices • “common denominator” models of smart home devices • Ideally approved by all participating organizations (BBF, HGI, OneM2M, OSGi-A, …) • Template has an informal (text) and a formal section (machine-readable, probably XML based) • Template needs to be instantiated for specific devices by domain specific organizations • The Template is being developed in an open-source framework GSC-18, 22-23 July 2014, Sophia Antipolis

More Related