Sie sind auf Seite 1von 10

Connected home application based on M2M services platform

ETSI M2M Workshop Oct 19th 2010


Thibault Cantegrel AirVantage Product Management & Marketing Director

Sierra Wireless Proprietary and Confidential

Page 1

Summary
Introduction New concerns raised by consumer oriented applications Presentation of a connected home use case Enablement platform & tools Benefits of the architecture

Sierra Wireless Proprietary and Confidential

Page 2

M2M enables smart solutions


Smart vs smart solutions:
for Industry market (most of currently running M2M solutions), smart = data collecting over the air.
Enhanced M2M applications: Software/firmware update over the air, solution-wide monitoring, alerting and diagnostics capabilities (differentiate subscription/connectivity/module/embeddedsoftware issues) provided by a M2M services platform allow a better cost of ownership of the M2M solution.

for Consumer market, smart = live remote monitoring and control from my smart phone, get support (customer care service), add new services & apps
Strong customer care support needs, that require the above M2M enhanced features, embedded intelligence on devices/gateways, strong APIs, and strong backend architecture to handle the volume of communications of devices and applications.

Sierra Wireless Proprietary and Confidential

Page 3

Connected Home Use Case

Sierra Wireless Proprietary and Confidential

Page 4

Some of the new concerns raised by consumer oriented M2M applications


Multi-channels bi-directional communication
Example: ADSL (main) + GPRS/3G (if no ADSL available) Mediation server to solve the concern of reaching the device from the server using the right channel, and reaching it behind a firewall (ADSL channel)

Services provided in local and in remote


Example: local control via the set-top box / remote control via a smart phone Need of synchronization box server

Traffic/bandwidth control (can be huge)


Example: each action sends data to the server (ADSL box) Different protocols for device management and application data between devices and server Mechanisms provided to handle different behavior of the device and the server depending upon the channel used, and upon whether anybody is connected remotely to control/monitor the device or not: communications between devices and servers can be avoided for more cases.

Responsiveness/latency of remote services


Remote controlling requires sometimes high reactivity

Openness to new services


The device is actually a platform on top of what other offers and services can be provided by 3rd parties (enables applications store models) Impacts on devices embedded logic and the server
Page 5

Sierra Wireless Proprietary and Confidential

Connected Home Use Case


Service Provider Administration Interface SaaS M2M Server Data/Configurations hosting APIs Business Web Application Hosting Mediation server Device Management Web Portal (monitoring, diagnostics, FW/SW update)
Telecom Operator Infrastructure ADSL GPRS 3G ADSL box Wifi Ethernet Protocols: OMA-DM (device management) AWT-DA (applications) Mediation services (UDP)

End-Customer Remote Services

VPN

End-Customer Local Services

Wifi Ethernet (HTTP)

Routing Monitoring Alerting Application container Local web server


RF-433 X10 wired RF-868 X10 wireless

Home

X10, RF-433 & RF-868 Sensors and Actuators

Sierra Wireless Proprietary and Confidential

Page 6

Enablement platform & tools used


Help developing embedded applications in coherence with backend server and applications
RF-868 Sensors X10 Actuators RF-433 Sensors

RF-868 Actuators

Communication with equipments Remote LUA scripts Applications container Applications logs Configuration store Data storage Monitoring Shells Network manager & cnx policy Mediation services Software update Security, encryption Local services (HTTP) (monitoring & control) Communication through Ethernet and GPRS/3G bearers (OMA-DM, AWT-DA)

Templ ates App 1 App 1 App 1 Device Model

PIC microcontroller

App 1 App 1 Execution env. + Libraries

upload

Applications (services) Execution env. + Libraries Embedded O/S Firmware


Gateway (Programmable Module)

Web server

Eclipse IDE: Dev tools

Sierra Wireless Proprietary and Confidential

Page 7

Enablement platform & tools used


Help developing server side applications in coherence with embedded logic

Templ ates App 1 App 1 App 1 Device Model

App 1 App 1 Device Simulator

deploy

Custom Applications (widgets based)

Administrator, Customer care

Web Services Eclipse IDE: Dev tools API Asset Management


AWT-DA

Web Portal UI

Device Management
Protocol Adapter

Subscriber Management

Account Management

OMA-DM MSCI

M2M Services Platform


API

Data

Devices

Carrier Network

Assets

Sierra Wireless Proprietary and Confidential

Page 8

Highlight few benefits


Module agnostic solution (embedded agent can run on multiple embedded O/S) Network topology agnostic solution (Mediation Server) Based on standards for device management (OMA-DM) (Telecom Operators to enhance their Subscription Management platforms with device management capabilities someday?) Applications oriented, self descriptive, compressed, open protocol for applicative data (AWT-DA) SaaS model avoids strong investments before having rolled out the first device Fast go-to-market thanks to
development tools & pre-integrated components deployment & operating self-care web portal Launching soon!

Sierra Wireless Proprietary and Confidential

Page 9

Thank you for your attention tcantegrel@sierrawireless.com

Page

Das könnte Ihnen auch gefallen