How to connect non IP devices into the UPnP - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

How to connect non IP devices into the UPnP

Description:

How to connect non IP devices into the UPnP v1 fabric. Vijay Dhingra. Director of Standards ... for Non IP device Fabric. True Open System. Standards-based ... – PowerPoint PPT presentation

Number of Views:86
Avg rating:3.0/5.0
Slides: 17
Provided by: vijayd4
Category:
Tags: upnp | connect | devices | fabric | non

less

Transcript and Presenter's Notes

Title: How to connect non IP devices into the UPnP


1
How to connect non IP devices into the UPnPv1
fabric
Vijay Dhingra Director of Standards Echelon Corp.
2
Enhanced Consumers Experience
  • To enhance consumers 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.

3
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

4
Interaction bridge UPnP devices
UPnP
Interoperable open standard ANSI/CEA 709.1
5
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

6
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.

7
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-to-peer
    communications (direct communications among
    transducers without mediation by a master).
  • Cost Savings
  • Lower product cost, installation costs,
    life-cycle costs.

8
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.

9
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.

10
Solution - Architecture
UPnP Protocol
LNS Network Operating System
  • LONWORKS Networks

11
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

12
Solution implementation details
  • On any PC bridge application with Echelons
    LNS (LonWorks Network Services API) loaded in a
    server-independent mode
  • All the mandatory network variables are mapped
    into UPnP stack
  • Optional features (manufacturers specific
    extensions) can further be developed in the
    future
  • Translator modules as Microsoft .Net assembly
    DLLs.

13
Software Architecture of LonWorks/ UPnP Bridge
14
Hardware adapters
  • Possible solutions
  • PL to Serial converter
  • PL to Ethernet adapter
  • i.Lon 10
  • PL to Web Services Server
  • i.Lon 100
  • PL to PCI Bus
  • PCLTA 20 SMX w/PLM 22

15
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.

16
For the interconnected lifestyle
Write a Comment
User Comments (0)
About PowerShow.com