1 / 11

UPnP TM Remote I/O

Explore user scenarios, device definitions, and basic DCP for controlling application interfaces on various devices. Get insights on the working committee progress and key events.

sheilachapman
Download Presentation

UPnP TM Remote I/O

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. UPnPTM Remote I/O Mark R. Walker Intel Markus Wischy Siemens

  2. UPnP Remote I/OExample user scenarios • A home PC remotely displaying application user interfaces on the living room television. • A DVR/set top box displays control menus on all televisions in the home.

  3. UPnP events & control actions UPnP Remote I/O Home Server UPnP Remote I/OExample user scenarios • A home automation/security system displays controls and alerts on many UI devices

  4. UPnP Remote I/OInformal vocabulary • "Remoting" - running application logic and user interface on different devices. • "Protocol" - the format of peer-to-peer communication between the application and remote UI (not standardized by UPnP Remote I/O). • "Remote I/O client device" - where the UI is executed/displayed. • "UI server" - exposes lists of remote-able applications and status of running applications.

  5. UPnP Remote I/OSimpledevice definitions • UPnP Remote I/O clients: • Have controls for connecting & administering user interface sessions, • May expose protocol-required information: (display screen size, keyboard type, etc.) • UPnP Remote IO UI servers: • Expose lists of remote-able UIs, • Expose status of instantiated UIs and UI sessions, • Have controls for destroying instantiated, unconnected UIs.

  6. UPnP Remote I/O Basic DCP • UPnP Remote I/O UI servers advertise listings of remote-enabled UIs. • UPnP Remote I/O control entities match UI descriptions with remote client capabilities and establish sessions. • Note: communication protocol between UI and client is not standardized - vendors choose. • Example protocols: MS RDP, Intel XRT, EIA775, etc.

  7. Control Point 3 - Session 1 2 1.) Control point finds UI server andUI listings 2.) Control point finds client and supported protocols 3.) Control point matches UI and device protocol andstarts a session UPnP Remote I/O Example #1: Remote client UI server legend: standardized by UPnP Remote I/O not standardized

  8. 1.) Finds Remote I/O clients Laundry finished 1 2 2.) DisplayMessage(“Laundry finished”) 1 2 Laundry finished Laundry finished UPnP Remote I/O Example #2: Remote client Any UPnP Control Point legend: Remote client standardized by UPnP Remote I/O

  9. UPnP Remote I/OWorking committee progress • Progress to-date: • Working committee approved: Dec '02 • Co-chairs: Intel, Siemens • 30 teleconferences and 5 face-to-face meetings • Requirement documents (available at www.upnp.org): • UPnP™ Remote IO Requirements V 0.9 • UPnP™ Remote IO Client Description V 0.8 • UPnP™ Remote IO Server Description V 0.81 • Service drafts underway

  10. UPnP Remote I/O Working committee schedule • Upcoming events: • Preliminary Design: Oct ’03 • Plugfest: Oct ’03 • Feature Complete (v0.8): Dec ’03 • 45-day review completed: March ’04 • Final approval: May ’04

  11. For the interconnected lifestyle

More Related