UPnP_Device_Architecture_Generic_20000710

UPnP_Device_Architecture_Generic_20000710 - UPnP Device...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: UPnP Device Architecture Networking is easy, except… Ad hoc networks don't have resources just for the sake of the network E.g., DHCP, DNS, directory, … Network is unreliable Nodes added / removed unpredictably Programs need to talk to programs But software is heterogeneous One size doesn't fit all Must upgrade system piece at a time UPnP Strategy 1. Just send data over the network (No executables) Minimize version issues Minimize security issues 2. Keep implementation private Be agnostic re: programming language, OS Update implementation w/o affecting interop Improve performance Reduce footprint Improve capabilities 3. Agree on meaning / format of data Choose substrate of proven protocols Define device (service) specific protocols in a Forum UPnP Tactics Start simple Build in only universal things that everybody needs (and can live with) Add as needed Minimize requirements Basic IP network connectivity Common HTTP protocol stack Leverage existing standards HTTP, XML Goals Describe the protocols for communication between Control points Controller, usually client Device Controlled, usually server An actual device might contain both functions Device Device Service Service Control Point Control Point Control Point Control Point Device Device Service Service Steps to UPnP Networking 0 Control point and device get addresses 1 Control point finds interesting device 2 Control point learns about device capabilities 3 Control point invokes actions on device 4 Control point listens to state changes of device 5 Control point controls device and/or views device status using HTML UI 0 Addressing 0 Addressing 1 Discovery 1 Discovery 2 Description 2 Description 5 Presentation 5 Presentation 4 Eventing 4 Eventing 3 Control 3 Control Vendor-specific API above Vendor-specific OS below UPnP Protocol Stack Vendor-specific physical net UPnP Device Architecture UPnP Device Architecture UDP UDP IP IP HTTPU/MU HTTPU/MU GENA GENA SSDP SSDP SOAP SOAP HTTP HTTP HTTP HTTP GENA GENA TCP TCP UPnP Forum UPnP Forum UPnP vendor UPnP vendor Steps to UPnP Networking 0* Control point and device get addresses 1 Control point finds interesting device 2 Control point learns about device capabilities 3 Control point invokes actions on device 4 Control point listens to state changes of device 5 Control point controls device and/or views device status using HTML UI 0* Addressing 0* Addressing 1 Discovery 1 Discovery 2 Description 2 Description 5 Presentation 5 Presentation 4 Eventing 4 Eventing 3 Control 3 Control 0 Addressing Control point and device get address Use a DHCP server Else use Auto IP What is Auto IP?...
View Full Document

This note was uploaded on 10/19/2009 for the course CNT 5517 taught by Professor Helal during the Fall '09 term at University of Florida.

Page1 / 40

UPnP_Device_Architecture_Generic_20000710 - UPnP Device...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online