Programmatic control UPnP architecture also enables conventional application programmatic control. UPnP stacks are available for most platforms and operating systems in both closed and open source forms. Operating system and programming language independence Any operating system and any programming language can be used to build UPnP products. User interface (UI) Control Optionally, the UPnP architecture enables devices to present a user interface through a web browser (see Presentation below).
LA PMP AWARE DRIVER
No special device driver support is necessary common network protocols are used instead. Media and device independence UPnP technology can run on many media that support IP including Ethernet, FireWire, IR ( IrDA), home wiring ( G.hn) and RF ( Bluetooth, Wi-Fi). UPnP was published as a 73-part international standard, ISO/IEC 29341, in December 2008.
Devices can disconnect from the network automatically without leaving state information. Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) servers are optional and are only used if they are available on the network. A UPnP-compatible device from any vendor can dynamically join a network, obtain an IP address, announce its name, advertise or convey its capabilities upon request, and learn about the presence and capabilities of other devices.
The UPnP architecture supports zero-configuration networking. UPnP control points (CPs) are devices which use UPnP protocols to control UPnP controlled devices (CDs). It is a distributed, open architecture protocol based on established standards such as the Internet Protocol Suite (TCP/IP), HTTP, XML, and SOAP. The UPnP architecture allows device-to-device networking of consumer electronics, mobile devices, personal computers, and networked home appliances. UPnP is generally regarded as unsuitable for deployment in business settings for reasons of economy, complexity, and consistency: the multicast foundation makes it chatty, consuming too many network resources on networks with a large population of devices the simplified access controls don't map well to complex environments and it does not provide a uniform configuration syntax such as the CLI environments of Cisco IOS or JUNOS. UPnP devices are plug and play in that, when connected to a network, they automatically establish working configurations with other devices. Responses to search requests are also sent over UDP, but are instead sent using unicast (known as HTTPU).Ĭonceptually, UPnP extends plug and play-a technology for dynamically attaching devices directly to a computer-to zero-configuration networking for residential and SOHO wireless networks. Device search requests and advertisements are supported by running HTTP on top of UDP ( port 1900) using multicast (known as HTTPMU). UPnP assumes the network runs Internet Protocol (IP) and then leverages HTTP, on top of IP, in order to provide device/service description, actions, data transfer and event notification. Since 2016, all UPnP efforts have been managed by the Open Connectivity Foundation (OCF). The Forum consisted of more than 800 vendors involved in everything from consumer electronics to network computing. The UPnP protocols were promoted by the UPnP Forum, a computer industry initiative to enable simple and robust connectivity to standalone devices and personal computers from many different vendors. UPnP is intended primarily for residential networks without enterprise-class devices. Universal Plug and Play ( UPnP) is a set of networking protocols that permits networked devices, such as personal computers, printers, Internet gateways, Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services.
0 kommentar(er)
