UPnP Universal Plug and Play

UPnP规范基于TCP/IP协议和针对设备彼此间通讯而制订的新的Internet协议。要说计算机外设的即插即用(Plug and Play(缩写PnP))

Required. Search Target. Single URI. If ST header in request was,
ssdp:all
Respond 3+2d+k times for a root device with d embedded devices and s embedded services but only k distinct service types (see section 1.1.2 for a definition of each message to be sent). Value for ST header must be the same as for the NT header in NOTIFY messages with ssdp:alive. (See above.) Single URI.
upnp:rootdevice
Respond once for root device. Must be upnp:rootdevice. Single URI.
uuid:device-UUID
Respond once for each matching device, root or embedded. Must be uuid:device-UUID. Device UUID specified by UPnP vendor. Single URI.
urn:schemas-upnp-org:device:deviceType:v
Respond once for each matching device, root or embedded. Must be urn:schemas-upnp-org:device:deviceType:v. Device type and version defined by UPnP Forum working committee. Should specify the version of the device type contained in the M-SEARCH request.
urn:schemas-upnp-org:service:serviceType:v
Respond once for each matching service type. Must be urn:schemas-upnp-org:service:serviceType:v. Service type and version defined by UPnP Forum working committee. Should specify the version of the service type contained in the M-SEARCH request.
urn:domain-name:device:deviceType:v
Respond once for each matching device, root or embedded. Domain name, device type and version defined by UPnP vendor. Period characters in the domain name must be replaced with hyphens in accordance with RFC 2141. Should specify the version of the device type specified in the M-SEARCH request.
urn:domain-name:service:serviceType:v
Respond once for each matching service type. Domain name, service type and version defined by UPnP vendor. Period characters in the domain name must be replaced with hyphens in accordance

猜你喜欢

转载自sunj.iteye.com/blog/2400329