1. doc.: IEEE 802.11-14/0067r0 Submission Jan 2014 Ping FANG, HuaweiSlide 1 Service Discovery for UPnP Printer Date: 2014-01-20 Authors:

2. doc.: IEEE 802.11-14/0067r0 Submission Jan 2014 Ping FANG, HuaweiSlide 2 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.

3. doc.: IEEE 802.11-14/0067r0 Submission Jan 2014 Ping FANG, HuaweiSlide 3 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.

4. doc.: IEEE 802.11-14/0067r0 Submission UPnP Device Architecture Jan 2014 Ping FANG, HuaweiSlide 4 Devices Controllers NOTIFY messages (presence announcements) M-SEARCH messages (device/service search) GET device & service description XML UPnP Actions SOAP SSDP Event subscriptions Event notifications Discovery Description Control Events GENA

5. doc.: IEEE 802.11-14/0067r0 Submission GAS for UPnP Printer Jan 2014 Ping FANG, HuaweiSlide 5 STA/CPAP/Proxy Service / Network or associated devices GAS Req [urn:schemas-upnp-org:device:printer:1] GET: URL for DDD XML Device Description GAS Res [UPnP: URL to DDD] NOTIFY with SSDP:alive GAS Req [UPnP: URL to DDD] GAS Res [UPnP:XML Device list, Service list] M-SEARCH: urn:schemas-upnp-org:device:printer:1 URL to Device Description Document GET: URL to service description XML for service description GAS Req [UPnP: URL to service description] GAS Res [UPnP:XML for service description] May be GAS comeback responses.

6. doc.: IEEE 802.11-14/0067r0 Submission GAS for UPnP PrintBasic Service Jan 2014 Ping FANG, HuaweiSlide 6 STA/CPAP/Proxy Service / Network or associated devices GAS Req [urn:schemas-upnp-org:service:PrintBasic:1] GET: XML for service description XML Service Description GAS Resp [UPnP: URL to service description] NOTIFY with SSDP:alive GAS Req [UPnP: GET: XML for service description] GAS Res [UPnP:XML for service description] M-SEARCH: urn:schemas-upnp-org:service:PrintBasic:1 URL to service description May be GAS comeback responses.

7. doc.: IEEE 802.11-14/0067r0 Submission Jan 2014 Ping FANG, HuaweiSlide 7 Further Discussion 1.At what level of service information, should proxy build and keep? a)Just service name/service ID + URL b)Above all + Description Document 2.If proxy also keeps description document, should proxy fully support upper layer service discovery protocol? 3.For PAD, to what level of service name can be expect? Printer, UPnP Printer, urn:schemas-upnp-org:service:PrintBasic:1?

8. doc.: IEEE 802.11-14/0067r0 Submission References 1.IEEE Std 802.11™-2012 2.UPnP Device Architecture 1.0 - UPnP Forum 3.Printer:1 Device Template Version 1.01. For UPnP™ Version 1.0 4.PrintBasic:1 Service Template Version 1.01. For UPnP™ Version 1.0 Jan 2014 Ping FANG, HuaweiSlide 8