Transcript Non-IP Connectivity and Bridging

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
UPnP
Control Point
(Pocket PC)
Interoperable open
standard ANSI/CEA
709.1
Control Point
(Remote Control)
Lightweight Device
(LonWorks(r) Submetering
Device)
IP Network
Native Device
(UPnP VCR)
Echelon UPnP Bridge
Native Device
(UPnP Alarm Clock)
Lightweight Device
(LonWorks Thermostat)
Non-IP Bus/Networks
Lightweight Device
(Light Switch)
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, etc
Distributed control systems with peer-topeer communications (direct
communications among transducers
without mediation by a master).
Cost Savings

Lower product cost, installation costs, lifecycle 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
UPnP ™ Protocol
LNS® Network Operating System
LONWORKS® Networks
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 serverindependent 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.
IP Netw ork
239.255.255.0:19
Discovery
subsystem
cached info for
device discovery
Built-in w eb
server
subscription
interfaces
description
and
control
interfaces
LonMark object -t ranslat o
LonMark objecttranslator
sof t ware module-t ranslat or
sof t ware module-t ranslat or
softw are moduletranslator
Control and
monitoring
dispatcher
LNS mode
switchover
netw ork configuration
agent (LNS full client)
control and monitoring (LNS
server-independent mode)
LonWorks protocol stack
LonWorks Adapter
netw ork database
LonWorks devices
netw ork address
Software
Architecture of
LonWorks/
UPnP Bridge
Hardware adapters
Possible solutions:

PL to Serial
converter

PL to Ethernet
adapter


PL to Web Services
Server


i.Lon 10
i.Lon 100
PL to PCI Bus

PCLTA 20 –
SMX 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