How to connect non IP devices into the UPnP™v1 fabric

Vijay Dhingra

Director of Standards

Echelon Corp.

Enhanced Consumer’s Experience

To enhance consumer’s experience with home automation, “all devices” in the home need to integrate seamlessly with computer and A/V network.

Examples of “all devices” Of course, computers, printers, PDAs, Cell

Phones, A/Vs And non-IP devices – light switches,

thermostats, occupancy sensors, security sensors, etc.

Seamless Integration?

What is seamless integration for consumers Zero-configuration, "invisible" networking,

and automatic discovery A breadth of device categories from a wide

range of vendors. Dynamically join a network, obtain an IP

address, convey its capabilities, and learn about the presence and capabilities of other devices

Same experience with UPnP devices and non-IP devices

Interaction bridge & UPnP devices

IP Network

Non-IP Bus/Networks

Control Point(Pocket PC)

Lightweight Device(LonWorks Thermostat)

Echelon UPnP Bridge

Native Device(UPnP Alarm Clock)

Control Point(Remote Control)

Native Device(UPnP VCR)

Lightweight Device(Light Switch)

Lightweight Device(LonWorks(r) Submetering

Device)

Interoperable open Interoperable open standard ANSI/CEA standard ANSI/CEA 709.1709.1

UPnPUPnP

Why do you need a Bridge

Prohibitively expensive to implement UPnP stack in “everyday devices” such as light switches, thermostats etc.

Ability to connect with largely deployed legacy networks.

Connects UPnP devices and control points with non IP devices

Requirements for Non IP device Fabric

True Open System Standards-based interoperable technology Multiple subsystems, multiple product vendors,

multiple integrators, multiple user interfaces, multiple markets.

Interoperable Freedom to choose best of breed products from

multiple vendors and have them work together. Ability to enhance home over time without being

locked into a single vendor or support contractor.

Requirements for Non IP device Fabric(Cont)

Scalability Number of devices per network, flexibility

of deciding media types, mixing and matching of different mediums.

Power Line, twisted pair, fiber optic, RF, etcPower Line, twisted pair, fiber optic, RF, etc Distributed control systems with peer-to-

peer communications (direct communications among transducers without mediation by a master).

Cost Savings Lower product cost, installation costs, life-

cycle costs.

Requirements for Non IP device Fabric(Cont)

Built-in Security Low overhead built-in security.

Time to Market Faster implementation of newly developed

and fully optimized End-to-End solution products and tools.

Pervasive Network Statistics

LonWoRks® technology from Echelon is the most widely used network in the world for home & building automation Over 30 million LonWorks devices installed

worldwide Wide range of LonWorks products available from

thousands of manufacturers

LonMark® Interoperability Associations Industry groups define how products work together Certification program has approved ~ 500 devices &

certification centers located worldwide.

Solution - Architecture

LONWORKS® Networks

LNS® Network Operating System

UPnP ™ Protocol

Solution implementation

LonWorks technology semantics – LonMark® functional object and network variables are defined at the application level (similar to UPnP™ functional profiles)

LonMark® objects are mapped into UPnP™ devices

Solution implementation details

On any PC – bridge application with Echelon’s LNS® (LonWorks Network Services API) loaded in a server-independent mode All the mandatory network variables are

mapped into UPnP™ stack Optional features (manufacturer’s specific

extensions) can further be developed in the future

Translator modules as Microsoft .Net™ assembly DLLs.

Software Software Architecture of Architecture of LonWorks/ LonWorks/ UPnP BridgeUPnP Bridgesubscription

interfaces

LonMark object-translato

LonWorks devices

LonWorks protocol stack

LonWorks Adapter

netw ork configuration agent (LNS full client)

control and monitoring (LNS server-independent mode)

netw ork address

netw ork database

LNS mode switchover

Control and monitoring dispatcher

Discovery subsystem

cached info for device discovery

description and

Built-in w eb server

control interfaces

239.255.255.0:19

software module-translator

software module-translator

softw are module-translator

LonMark object-translator

IP Netw ork

Hardware adaptersPossible solutions:

PL to Serial converter

PL to Ethernet adapter

i.Lon 10i.Lon 10

PL to Web Services Server

i.Lon 100i.Lon 100

PL to PCI Bus PCLTA 20 – PCLTA 20 –

SMX w/PLM 22SMX w/PLM 22

Conclusions

With existing technology, everyday devices (LonWorks devices) can successfully be mapped into UPnP domain.

Further work is required to commercialize the hardware and software bridge.

For the interconnected lifestyle