RE: webtv-ISSUE-6 (UC Service Provider): Use Case: Document as a Service Provider [HOME_NETWORK_TF]

[Samsung] UPnP makes a distinction between entities that control devices (UPnP Control Points) and entities that implement UPnP Devices. UPnP Control Points are non-discoverable and use (but dont implement services) while UPnP Devices are discoverable and generally implement services.


From: on behalf of Jean-Claude Dufourd
Sent: Tue 4/26/2011 7:32 AM
Subject: Re: webtv-ISSUE-6 (UC Service Provider): Use Case: Document as a Service Provider [HOME_NETWORK_TF]

On 26/4/11 15:32 , Russell Berkoff wrote: 

	[Samsung] UPnP does not allow unencapsulated services or casual access to SSDP so a UPnP device wrapper would need to be provided. At that point the proffered UPnP device would become discoverable and could offer UPnP services. This assumes the UA supported the necessary UPnP stack functions (GENA, SSDP, SOAP, HTTP)and the page could access these functions. The question is loading a document into a UA that turns it into a UPnP device beneficial? 

JCD: A document does not turn into a UPnP device. A document may provide an additional service on the current device.
The current device is necessarily an HNTF UA, so already is exposed as a UPnP device and provides at least HNTF-related services.
Best regards

	Note: this could present significant security concerns. Also the question of the lifetime of the page and the ability page to establish itself as a background process become relevant.

JC Dufourd
Directeur d'Etudes/Professor
Groupe Multimedia/Multimedia Group
Traitement du Signal et Images/Signal and Image Processing
Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France 
Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144

Received on Tuesday, 26 April 2011 14:47:54 UTC