1 / 19

Telcordia Technologies Proprietary – Internal Use Only

Simon Tsang, Ph.D. Director Internet Architecture Research Telcordia Technologies, Inc. 445 South Street 1A 264R Morristown, NJ 07960-6438 Voice: 973-829-4511 Fax: 973-829-5889 E-mail: stsang@telcordia.com. An SAIC Company.

azia
Télécharger la présentation

Telcordia Technologies Proprietary – Internal Use Only

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. Simon Tsang, Ph.D. Director Internet Architecture Research Telcordia Technologies, Inc. 445 South Street 1A 264R Morristown, NJ 07960-6438 Voice: 973-829-4511 Fax: 973-829-5889 E-mail: stsang@telcordia.com An SAIC Company Instant Messaging and Presencefor SIP Enabled Networked Appliances(Authors: S. Moyer, A. Roychowdhury) Prepared For: IPTEL 2001 April 2, 2001 Telcordia Technologies Proprietary – Internal Use Only This document contains proprietary information that shall be distributed, routed or made available only within Telcordia Technologies, except with written permission of Telcordia Technologies. An SAIC Company

  2. Coming up… • What is a Networked Appliance? (aka IPA) • IPAC* Architecture + Issues • SIP + Instant Messaging ++ for IPAC* • From our lab… • Future work… *IPAC = Internet Personal Appliance Control

  3. What is a Networked Appliance? (aka IPA) • A networked device with • Dedicated functionality, limited configurability, and optimized UI • Ability to interact with the physical environment through sensors & actuators • Limited (or restricted) general-purpose computational power • A.k.a. Internet Personal Appliances (IPAs), networked appliances, Internet appliances, IP appliances, networked devices, …

  4. Anatomy of an IPA… Available in “Fat” IPAs Application control Network Interface I/O control IP networks Sensors, Actuators • Home: TV display, Heating element • Car: Speedometer, Radar detector • Industrial: Fuel cell, Robot • Medical: Pressure monitor, Pacemaker

  5. What We’d Like To Do With IPAs…(securely from the Internet) • Command and control • Query • Notification of events • Sessions/Media Streaming

  6. Networking Appliances Today…A Multitude of Devices and Technologies… X.10 VESA home n/w UPnP Jini HAVi OSGi

  7. IPA Control (IPAC) Architecture[currently subject of discussion] IPA registration/ Discovery protocols IPA Location Service IPA location protocol IPA Application (Controller) IPA Gateway IPA control protocol Legacy protocols

  8. IPAC Issues…[also currently subject of discussion] • IPA Control Protocol (incl. Event notifications) • IPA Naming, Addressing • IPA Discovery, Registration • IPA Mobility • Security • Across multiple domains • Different policy on a per usage basis?

  9. A New SIP Request — DO SUBSCRIBE/ NOTIFY Extensions SessionInitiationProtocol (SIP) New payloadtype — DMP? Modified SIPURL Addressing? Proposed Solution(SIP + IM extensions ++…) RFC 2543 Device Messaging Protocol Internet Draft SUBSCRIBE/NOTIFY Internet Draft Need a hierarchical addressing scheme — TBD SIP Extensions for Communicating with Networked Appliances Internet Draft

  10. DO Message Received Acknowledgement Timeout period 1xx (to acknowledge message received) 200 (to acknowledge action completed) SIP DO Message + Responses Sender Receiver

  11. SIP DO Body (Device Message Part)[Still subject of discussion!!] • Device Message Part (MIME type) • Generic Content-function will be ‘render’. DO [d=lamp?one/r=bedroom/u=stsang]@home.net Via: ISP.net Via: MyHostDomain.com From: simon@MyHostDomain.com To: [d=lamp?one/r=bedroom/u=stsang]@simon.home.net CSeq: 1231 MESSAGE Timestamp: 17:16 EST May 26 2000 Content-function: render Content-type: application/dmp <xml><command>ON</command></xml>

  12. SIP + Instant Messaging For IPAC…WHY? • Leverage existing infrastructure. • Leverage existing management and operations systems. • Leverage existing expertise/skills in SIP. • THIS IS JUST ANOTHER VALUE-ADDED APPLICATION USING SIP.

  13. Why not… SNMP • Not real-time response, Client/server relationship assumed. HTTP • No support for event notification, Poor mobility support, Connection oriented SMTP • No event notification, No support for sessions/media streaming, Not real-time response A new protocol • Do we need yet another protocol?

  14. From our lab… SIP for IPAC in Action

  15. SIP NOTIFY SIP NOTIFY X.10 SIP SUBSCRIBE Event Notification Webphone PocketPC Clock Controller SIP UA WML SIP UA X.10 Controller OSGi GW SIP Proxy Alert Register Event Ring Bell SIP UA Rule Engine Clients Announcement Server SIP UA Web Server Network Server

  16. SIP DO X.10 SIP DO Event Notification – Open Door Webphone PocketPC Authenticate & Authorize Clock Controller SIP UA WML SIP UA X.10 Controller OSGi GW Translate SIP Proxy Open Door Open SIP UA Rule Engine Watcher Announcement Server SIP UA Web Server Network Server

  17. IETF 51 (?) Architecture Requirements Future WG? OSGi Device Interest Group “Device Excitation” Remote Management Conclusions… • SIP + IM extensions ++ new extensions for networked appliance (aka IPA) control. Mailing list: Appliances@research.telcordia.com Web page: http://www.argreenhouse.com/iapp/

  18. SPARE SLIDES(Technical Descriptions)

  19. SIP DO Headers[Still subject of discussion!!] • NewAddressing Methodology (in To: field) DO [d=lamp?one/r=bedroom/u=stsang]@home.net Via: ISP.net Via: MyHostDomain.com From: simon@MyHostDomain.com To: [d=lamp?one/r=bedroom/u=stsang]@simon.home.net Timestamp: 17:16 EST May 26 2000

More Related