80 likes | 332 Views
Service Discovery for UPnP Printer. Date: 2014-01-20. Authors:. Abstract. According to the meeting discussion in Dallas, we would like to know the exact service discovery steps for UPnP or Bonjour. This document presents a service discovery protocol for UPnP. Background.
E N D
Service Discovery for UPnP Printer Date: 2014-01-20 Authors: Ping FANG, Huawei
Abstract According to the meeting discussion in Dallas, we would like to know the exact service discovery steps for UPnP or Bonjour. This document presents a service discovery protocol for UPnP. Ping FANG, Huawei
Background In 13/501r0, a architecture with service registration and service discovery is registered. Per the meeting discussion, the registration can be done in MAC layer or upper layer after association. In 13/796r0, the procedure on how a STA discovers necessary service information before association is described with a high level 2-step service discovery procedure proposed. In 13/796r1, more details on service indication are further discussed. In 13/893r0, different service hash values proposed to be carried in service discovery request and response with public action frame for privacy and security. In 13/1403r0, Service indication from AP, network discovery and detailed service information query are described. Ping FANG, Huawei
UPnP Device Architecture Controllers Devices NOTIFY messages (presence announcements) SSDP Discovery M-SEARCH messages (device/service search) SSDP GET device & service description Description XML UPnP Actions SOAP Control Event subscriptions GENA Events Event notifications GENA Ping FANG, Huawei
GAS for UPnP Printer STA/CP AP/Proxy Service / Network or associated devices NOTIFY with SSDP:alive GAS Req [urn:schemas-upnp-org:device:printer:1] M-SEARCH: urn:schemas-upnp-org:device:printer:1 URL to Device Description Document GAS Res [UPnP: URL to DDD] May be GAS comeback responses. GAS Req [UPnP: URL to DDD] GET: URL for DDD XML Device Description GAS Res [UPnP:XML Device list, Service list] GAS Req [UPnP: URL to service description] GET: URL to service description XML for service description GAS Res [UPnP:XML for service description] Ping FANG, Huawei
GAS for UPnP PrintBasic Service STA/CP AP/Proxy Service / Network or associated devices NOTIFY with SSDP:alive GAS Req [urn:schemas-upnp-org:service:PrintBasic:1] M-SEARCH: urn:schemas-upnp-org:service:PrintBasic:1 URL to service description GAS Resp [UPnP: URL to service description] GAS Req [UPnP: GET: XML for service description] May be GAS comeback responses. GET: XML for service description XML Service Description GAS Res [UPnP:XML for service description] Ping FANG, Huawei
Further Discussion • At what level of service information, should proxy build and keep? • Just service name/service ID + URL • Above all + Description Document • If proxy also keeps description document, should proxy fully support upper layer service discovery protocol? • For PAD, to what level of service name can be expect? Printer, UPnP Printer, urn:schemas-upnp-org:service:PrintBasic:1? Ping FANG, Huawei
References • IEEE Std 802.11™-2012 • UPnP Device Architecture 1.0 - UPnP Forum • Printer:1 Device Template Version 1.01. For UPnP™ Version 1.0 • PrintBasic:1 Service Template Version 1.01. For UPnP™ Version 1.0 Ping FANG, Huawei