doc IEEE 802 11 -14 0067 r 0

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 Service Discovery for UPn. P Printer Date: 2014 -01 -20 Authors: Submission Slide 1 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 Abstract According to the meeting discussion in Dallas, we would like to know the exact service discovery steps for UPn. P or Bonjour. This document presents a service discovery protocol for UPn. P. Submission Slide 2 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 Background In 13/501 r 0, 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/796 r 0, 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/796 r 1, more details on service indication are further discussed. In 13/893 r 0, different service hash values proposed to be carried in service discovery request and response with public action frame for privacy and security. In 13/1403 r 0, Service indication from AP, network discovery and detailed service information query are described. Submission Slide 3 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 UPn. P Device Architecture Controllers Devices Discovery NOTIFY messages (presence announcements) SSDP M-SEARCH messages (device/service search) Description SSDP GET device & service description XML Control UPn. P Actions Events SOAP Submission GENA Event subscriptions Event notifications GENA Slide 4 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 GAS for UPn. P Printer STA/CP Service / Network or associated devices AP/Proxy 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 [UPn. P: URL to DDD] May be GAS comeback responses. GAS Req [UPn. P: URL to DDD] GET: URL for DDD XML Device Description GAS Res [UPn. P: XML Device list, Service list] GAS Req [UPn. P: URL to service description] GET: URL to service description XML for service description GAS Res [UPn. P: XML for service description] Submission Slide 5 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 GAS for UPn. P Print. Basic Service STA/CP Service / Network or associated devices AP/Proxy NOTIFY with SSDP: alive GAS Req [urn: schemas-upnp-org: service: Print. Basic: 1] M-SEARCH: urn: schemas-upnp-org: service: Print. Basic: 1 GAS Resp [UPn. P: URL to service description] URL to service description GAS Req [UPn. P: GET: XML for service description] May be GAS comeback responses. GET: XML for service description XML Service Description GAS Res [UPn. P: XML for service description] Submission Slide 6 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 Further Discussion 1. At what level of service information, should proxy build and keep? a) b) 2. 3. 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, UPn. P Printer, urn: schemas-upnp-org: service: Print. Basic: 1? Submission Slide 7 Ping FANG, Huawei

doc. : IEEE 802. 11 -14/0067 r 0 Jan 2014 References 1. IEEE Std 802. 11™-2012 2. UPn. P Device Architecture 1. 0 - UPn. P Forum 3. Printer: 1 Device Template Version 1. 01. For UPn. P™ Version 1. 0 4. Print. Basic: 1 Service Template Version 1. 01. For UPn. P™ Version 1. 0 Submission Slide 8 Ping FANG, Huawei