444:(GENA). A UPnP description for a service includes a list of actions the service responds to and a list of variables that model the state of the service at run time. The service publishes updates when these variables change, and a control point may subscribe to receive this information. The service publishes updates by sending event messages. Event messages contain the names of one or more state variables and the current value of those variables. These messages are also expressed in XML. A special initial event message is sent when a control point first subscribes; this event message contains the names and values for all
366:(SSDP). When a device is added to the network, SSDP allows that device to advertise its services to control points on the network. This is achieved by sending SSDP alive messages. When a control point is added to the network, SSDP allows that control point to actively search for devices of interest on the network or listen passively to the SSDP alive messages of devices. The fundamental exchange is a discovery message containing a few essential specifics about the device or one of its services, for example, its type, identifier, and a pointer (network location) to more detailed information.
919:
955:
854:; it does not apply when the router/firewall does not support UPnP IGD or has been disabled on the router. Also, not all routers can have such things as DNS server settings altered by UPnP because much of the specification (including LAN Host Configuration) is optional for UPnP enabled routers. As a result, some UPnP devices ship with UPnP turned off by default as a security measure.
831:. There also exists a non-standard solution called UPnP-UP (Universal Plug and Play - User Profile) which proposes an extension to allow user authentication and authorization mechanisms for UPnP devices and applications. Many UPnP device implementations lack authentication mechanisms, and by default assume local systems and their users are completely trustworthy.
484:(MR) version 2.0 classes. These enhancements are created by adding capabilities to the MediaServer and MediaRenderer device classes, allowing a higher level of interoperability between products made by different manufacturers. Some of the early devices complying with these standards were marketed by
546:
is the UPnP-server ("master" device) that provides media library information and streams media-data (like audio/video/picture/files) to UPnP clients on the network. It is a computer system or a similar digital appliance that stores digital media, such as photographs, movies, or music and shares these
273:
Each UPnP product can have device-specific services layered on top of the basic architecture. In addition to combining services defined by UPnP Forum in various ways, vendors can define their own device and service types, and can extend standard devices and services with vendor-defined actions, state
862:
In 2011, researcher Daniel Garcia developed a tool designed to exploit a flaw in some UPnP IGD device stacks that allow UPnP requests from the
Internet. The tool was made public at DEFCON 19 and allows portmapping requests to external IP addresses from the device and internal IP addresses behind the
766:
There are numerous compatibility issues due the different interpretations of the very large actually backward compatible IGDv1 and IGDv2 specifications. One of them is the UPnP IGD client integrated with current
Microsoft Windows and Xbox systems with certified IGDv2 routers. The compatibility issue
472:
is an audio and video extension of the UPnP, supporting a variety of devices such as TVs, VCRs, CD/DVD players/jukeboxes, settop boxes, stereos systems, MP3 players, still image cameras, camcorders, electronic picture frames (EPFs), and personal computers. The UPnP AV architecture allows devices to
334:
The foundation for UPnP networking is IP addressing. Each device must implement a DHCP client and search for a DHCP server when the device is first connected to the network. If no DHCP server is available, the device must assign itself an address. The process by which a UPnP device assigns itself an
904:
OCF had published a fix to the protocol specification in April 2020, but since many devices running UPnP are not easily upgradable, CallStranger is likely to remain a threat for a long time to come. CallStranger has fueled calls for end-users to abandon UPnP because of repeated failures in security
866:
In
January 2013, the security company Rapid7 in Boston reported on a six-month research programme. A team scanned for signals from UPnP-enabled devices announcing their availability for internet connection. Some 6900 network-aware products from 1500 companies at 81 million IP-addresses responded to
387:, manufacturer name, (presentation) URLs to vendor-specific web sites, etc. The description also includes a list of any embedded services. For each service, the Device Description document lists the URLs for control, eventing and service description. Each service description includes a list of the
114:
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 do not map
992:
The UPnP protocols were promoted by the UPnP Forum (formed in
October 1999), a computer industry initiative to enable simple and robust connectivity to standalone devices and personal computers from many different vendors. The Forum consisted of more than 800 vendors involved in everything from
762:
expose themselves as
Internet Gateway Devices, allowing any local UPnP control point to perform a variety of actions, including retrieving the external IP address of the device, enumerating existing port mappings, and adding or removing port mappings. By adding a port mapping, a UPnP controller
448:
variables and allows the subscriber to initialize its model of the state of the service. To support scenarios with multiple control points, eventing is designed to keep all control points equally informed about the effects of any action. Therefore, all subscribers are sent all event messages,
170:
The UPnP architecture supports zero-configuration networking. 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.
415:
Having retrieved a description of the device, the control point can send actions to a device's service. To do this, a control point sends a suitable control message to the control URL for the service (provided in the device description). Control messages are also expressed in XML using the
374:
After a control point has discovered a device, the control point still knows very little about the device. For the control point to learn more about the device and its capabilities, or to interact with the device, the control point must retrieve the device's description from the location
495:
Since 2006, versions 3 and 4 of the UPnP audio and video device control protocols have been published. In March 2013, an updated uPnP AV architecture specification was published, incorporating the updated device control protocols. UPnP Device
Architecture 2.0 was released in April 2020.
900:
On 8 June 2020, yet another protocol design flaw was announced. Dubbed "CallStranger" by its discoverer, it allows an attacker to subvert the event subscription mechanism and execute a variety of attacks: amplification of requests for use in DDoS; enumeration; and data exfiltration.
473:
support different types of formats for the entertainment content, including MPEG2, MPEG4, JPEG, MP3, Windows Media Audio (WMA), bitmaps (BMP), and NTSC, PAL or ATSC formats. Multiple types of transfer protocols are supported, including IEEE 1394, HTTP, RTP and TCP/IP.
684:
refers to control mechanisms that can provide different priority to different users or data flows, or guarantee a certain level of performance to a data flow in accordance with requests from the application program. Since UPnP AV is mostly to deliver
449:
subscribers receive event messages for all "evented" variables that have changed, and event messages are sent no matter why the state variable changed (either in response to a requested action or because the state the service is modeling changed).
887:
is enabled on a switch, or more commonly a wireless router/switch, it will interfere with UPnP/DLNA device discovery (SSDP) if incorrectly or incompletely configured (e.g. without an active querier or IGMP proxy), making UPnP appear unreliable.
461:, and depending on the capabilities of the page, allow a user to control the device and/or view device status. The degree to which each of these can be accomplished depends on the specific capabilities of the presentation page and device.
693:
or real-time audio/video data which it is critical to be delivered within a specific time or the stream is interrupted. QoS guarantees are especially important if the network capacity is limited, for example public networks, like the
106:
wireless networks. UPnP devices are plug-and-play in that, when connected to a network, they automatically establish working configurations with other devices, removing the need for users to manually configure and add devices through
879:
UPnP is often the only significant multicast application in use in digital home networks; therefore, multicast network misconfiguration or other deficiencies can appear as UPnP issues rather than underlying network issues.
63:
access points and mobile devices, to seamlessly discover each other's presence on the network and establish functional network services. UPnP is intended primarily for residential networks without enterprise-class devices.
778:, both of which have been standardized as RFCs by the IETF. These alternatives are not yet known to have compatibility issues between different clients and servers, but adoption is still low. For consumer routers, only
870:
In
February 2013, the UPnP forum responded in a press release by recommending more recent versions of the used UPnP stacks, and by improving the certification program to include checks to avoid further such issues.
891:
Typical scenarios observed include a server or client (e.g. smart TV) appearing after power on, and then disappearing after a few minutes (often 30 by default configuration) due to IGMP group membership expiring.
424:, the service returns any action-specific values in response to the control message. The effects of the action, if any, are modeled by changes in the variables that describe the run-time state of the service.
1037:
The WFAWLANConfig service is a required part and defines ways to query the capabilities of a wireless access point and set up wireless connections. This service is used in the AP-ER and UPnP-C types of
850:
request which allows a router implementing the UPnP IGD protocol to be controlled by a malicious web site when someone with a UPnP-enabled router simply visits that web site. This only applies to the
867:
their requests. 80% of the devices are home routers; others include printers, webcams and surveillance cameras. Using the UPnP-protocol, many of those devices can be accessed and/or manipulated.
2321:
315:(known as HTTPU). UPnP uses UDP due to its lower overhead in not requiring confirmation of received data and retransmission of corrupt packets. HTTPU and HTTPMU were initially submitted as an
261:
Any operating system and any programming language can be used to build UPnP products. UPnP stacks are available for most platforms and operating systems in both closed- and open-source forms.
846:
programs running outside the sandbox of the browser (e.g. this requires specific version of Adobe Flash with acknowledged security issues) are capable of generating a specific type of
2297:
303:
on top of IP, in order to provide device/service description, actions, data transfer and eventing. Device search requests and advertisements are supported by running HTTP on top of
33:
1581:
457:
The final step in UPnP networking is presentation. If a device has a URL for presentation, then the control point can retrieve a page from this URL, load the page into a
767:
still exist since the introduced of the IGDv1 client in
Windows XP in 2001, and a IGDv2 router without a workaround that makes router port mapping impossible.
1519:
2111:
339:. In UPnP Device Architecture Version 1.0, AutoIP is defined within the specification itself; in UPnP Device Architecture Version 1.1, AutoIP references
179:(DNS) servers are optional and are only used if they are available on the network. Devices can disconnect from the network automatically without leaving
2328:
770:
If UPnP is only used to control router port mappings and pinholes, there are alternative, newer much simpler and lightweight protocols such as the
351:
607:- which sends/receives control-commands between the UPnP-client and UPnP-server over network, (like record, schedule, play, pause, stop, etc.).
1270:
1248:
589:- which is the UPnP-client (a 'slave' device) that can auto-detect UPnP-servers on the network to browse and stream media/data-files from them.
725:
which contains a set of parameters that define the characteristics of the traffic stream, (for example operating requirement and scheduling).
2304:
2418:
115:
well to complex environments; and it does not provide a uniform configuration syntax such as the CLI environments of Cisco IOS or JUNOS.
362:
Once a device has established an IP address, the next step in UPnP networking is discovery. The UPnP discovery protocol is known as the
1934:
1329:
1589:
1497:
1076:
504:
1292:
1984:
1004:(DPWS) standard was a candidate successor to UPnP, but UPnP 1.1 was selected by the UPnP Forum. Version 2 of IGD is standardized.
554:, for browsing the media content of the server and request the media server to deliver a file to the control point for playback.
441:
1494:"Digital living network alliance (DLNA) home networked device interoperability guidelines - Part 1: Architecture and protocols"
1675:"UPNP_GetValidIGD returns Temporary IPv6 Address, causing UPNP_AddPinHole to fail with 606 · Issue #600 · miniupnp/miniupnp"
2097:
1582:"CEA-2014-B (ANSI) - Web-based Protocol and Framework for Remote User Interface on UPnP Networks and the Internet (Web4CE)"
1144:
1749:
1218:
1054:
172:
476:
On 12 July 2006, the UPnP Forum announced the release of version 2 of the UPnP Audio and Video specifications, with new
1611:
1007:
The UPnP Internet
Gateway Device (IGD) standard has a WANIPConnection service, which provides similar functionality to
729:
which is a unidirectional flow of data that originates at a source device and terminates at one or more sink device(s).
404:
2371:
2357:
1019:
specification contains a list of the problems with IGDP that prompted the creation of NAT-PMP and its successor PCP.
863:
NAT. The problem is widely propagated around the world, with scans showing millions of vulnerable devices at a time.
363:
354:, the device should use that name in subsequent network operations; otherwise, the device should use its IP address.
1585:
1530:
1070:
1059:
1001:
751:
657:
615:
2413:
2245:
2125:
1779:
1471:
1064:
500:
340:
2028:
1197:
2112:"CVE-2020-12695: CallStranger Vulnerability in Universal Plug and Play (UPnP) Puts Billions of Devices at Risk"
577:. As of May 2008, there were more software-based UPnP AV media servers than there were hardware-based servers.
319:, but it expired in 2001; these specifications have since been integrated into the actual UPnP specifications.
1556:
806:
UPnP IGDv2 and PCP implementation has been very buggy since its introduction. In many cases it does not work.
2388:
2151:
967:
350:. If during the DHCP transaction, the device obtains a domain name, for example, through a DNS server or via
323:
99:
1648:
2438:
2428:
1293:"UPnP Specifications Named International Standard for Device Interoperability for IP-based Network Devices"
1229:
994:
972:
56:
1000:
In the fall of 2008, the UPnP Forum ratified the successor to UPnP 1.0 Device
Architecture, UPnP 1.1. The
1148:
499:
The UPnP AV standards have been referenced in specifications published by other organizations including
2071:
1087:
80:
2211:
1700:"upnpc shows wrong duration for port forward longer than 120 seconds · Issue #222 · miniupnp/miniupnp"
1809:
1442:
1081:
775:
2283:
1962:
1173:
710:
570:
311:(known as HTTPMU). Responses to search requests are also sent over UDP, but are instead sent using
180:
103:
87:(known as HTTPMU). Responses to search requests are also sent over UDP, but are instead sent using
36:
UPnP logo as promoted by the UPnP Forum (2001–2016) and Open Connectivity Foundation (2016–present)
2423:
993:
consumer electronics to network computing. Since 2016, all UPnP efforts have been managed by the
144:
648:
to display on any other device connected to the home network. That means that one can control a
2433:
2408:
763:
behind the IGD can enable traversal of the IGD from an external address to an internal client.
680:- is an important (but not mandatory) service function for use with UPnP AV (Audio and Video).
574:
400:
379:) provided by the device in the discovery message. The UPnP Device Description is expressed in
304:
187:
76:
2383:
2176:
Bodlaender, M.P. (February 2005). "UPnP 1.1 - designing for performance & compatibility".
1890:
2270:
1092:
1039:
1012:
795:
771:
526:
Media Server: the server that stores content on the network to be accessed by Media Renderers
1333:
1303:
737:- defines methods for connecting UPnP device sets that are not in the same multicast domain.
523:
Control Point: a device that discovers Media Servers and Media Renderers, then connects them
1724:
839:
759:
625:
255:
124:
17:
1837:"A UPnP extension for enabling user authentication and authorization in pervasive systems"
8:
1520:"OpenCable Specifications Home Networking 2.0 - Home Networking Protocol 2.0 Revision 10"
1384:
717:
that indicates the kind of traffic in the traffic stream, (for example, audio or video).
649:
633:
388:
48:
1413:
971:
Please expand the article to include this information. Further details may exist on the
932:
Please help update this article to reflect recent events or newly available information.
2193:
1911:
835:
755:
681:
629:
433:
176:
72:
1414:"UPnP Forum Releases Enhanced AV Specifications Taking Home Network to the Next Level"
440:. The event notification protocol defined in the UPnP Device Architecture is known as
383:
and includes vendor-specific manufacturer information like the model name and number,
2367:
2353:
566:
529:
Media Renderer: a device that renders ('plays') content received from a Media Server.
288:
140:
132:
52:
2197:
75:. Device search requests and advertisements are supported by running HTTP on top of
2249:
2185:
1848:
558:
343:
251:
1835:
Sales, Thiago; Sales, Leandro; Almeida, Hyggo; Perkusich, Angelo (November 2010).
1699:
1674:
1022:
A number of further standards have been defined for the UPnP Device Architecture:
1725:"miniupnp.tuxfamily.org :: View topic - Setting up portforward doesn't work"
686:
640:(Web4CE). This standard allows a UPnP-capable home network device to provide its
417:
407:
and are described in terms of their data type, range, and event characteristics.
156:
1266:
561:
and many hardware platforms. UPnP AV media servers can either be categorized as
347:
2364:
UPnP Design by Example: A Software Developer's Guide to Universal Plug and Play
1267:"ISO/IEC standard on UPnP device architecture makes networking simple and easy"
1027:
820:
690:
641:
601:- control MediaRenderer settings; volume, brightness, RGB, sharpness, and more.
565:-based or hardware-based. Software-based UPnP AV media servers can be run on a
316:
231:
136:
71:
on top of IP to provide device/service description, actions, data transfer and
1853:
1836:
1757:
1356:"How Windows Firewall affects the UPnP framework in Windows XP Service Pack 2"
240:, the UPnP architecture enables devices to present a user interface through a
2402:
2189:
2007:
884:
747:
550:
UPnP AV media servers provide a service to UPnP AV client devices, so-called
421:
384:
267:
UPnP architecture also enables conventional application programmatic control.
225:
95:
2029:"UPnP Forum Responds to Recently Identified LibUPnP/MiniUPnP Security Flaw"
2008:"Whitepaper: Security Flaws in Universal Plug and Play: Unplug, Don't Play"
1493:
1119:
128:
55:(IP) that permits networked devices, such as personal computers, printers,
2393:
98:—a technology for dynamically attaching devices directly to a computer—to
1467:
1355:
843:
653:
458:
399:, for each action; the description for a service also includes a list of
241:
1958:
1636:
12 Fehler in der AVM UPnP IGD- und PCP-Implementation (aller FritzBoxen)
2218:
2035:
1783:
1753:
1446:
1420:
1391:
1299:
721:
which identifies data packets as belonging to a unique traffic stream.
108:
2241:
1787:
2254:
2212:"UPnP Forum Gateway Working Committee: IGD:2 Improvements over IGD:1"
2057:
1869:
1526:
1359:
842:
running the UPnP IGD protocol are vulnerable to attack. For example,
803:
508:
489:
308:
217:
84:
1098:
799:
787:
779:
695:
661:
645:
637:
621:
562:
284:
205:
201:
1612:"Detect FDSSDP as a microsoft client · miniupnp/miniupnp@8381867"
1016:
791:
783:
669:
573:
devices or any specific hardware for delivering media, such as a
485:
312:
200:
UPnP technology can run on many media that support IP, including
88:
1635:
966:
about UPnP DA 2.0, 2015 (revised 2020), difference described at
954:
228:
support is necessary; common network protocols are used instead.
1891:"Linux UPnP Internet Gateway Device - Documentation - Security"
823:, so UPnP device implementations must implement the additional
336:
326:
ports are derived from the SSDP alive and response messages.
221:
60:
2075:
1379:
1377:
519:
Generally a UPnP audio/video (AV) architecture consists of:
123:
The UPnP architecture allows device-to-device networking of
32:
1008:
847:
665:
595:- which is a 'slave' device that can render (play) content.
296:
292:
213:
209:
163:(CPs) are devices which use UPnP protocols to control UPnP
148:
68:
2298:"WFA WLANConfig Service 1.0 Service Template Version 1.01"
1834:
1813:
1328:
Goland, Yaron Y.; Schlimmer, Jeffrey C. (2 October 2000).
1374:
380:
376:
300:
152:
1557:"How DLNA and UPnP will enable easy home video networks"
834:
When the authentication mechanisms are not implemented,
335:
address is known within the UPnP Device Architecture as
274:
variables, data structure elements, and variable values.
2350:
Service and Device Discovery: Protocols and Programming
2239:
819:
The UPnP protocol, by default, does not implement any
569:. Hardware-based UPnP AV media servers may run on any
403:; these variables model the state of the service at
395:, to which the service responds, and parameters, or
143:
protocol based on established standards such as the
2322:"Wi-Fi Protected Setup Specification Version 2.0.8"
1468:"DLNA Networked Device Interoperability Guidelines"
754:(UPnP IGD Protocol), is implemented via UPnP. Many
1985:"Millions of devices vulnerable via UPnP - Update"
1810:"UPnP-UP - Universal Plug and Play - User Profile"
1034:) services related to the wireless access point.
2400:
1332:. UPnP Forum Technical Committee. Archived from
874:
67:UPnP assumes the network runs IP, and then uses
2242:"RFC 6886: NAT Port Mapping Protocol (NAT-PMP)"
1327:
1243:
1241:
1239:
709:(server-side/back-end) service functions. With
2126:"Disable UPnP on Your Wireless Router Already"
1271:International Organization for Standardization
605:UPnP Remote User Interface (RUI) client/server
503:Networked Device Interoperability Guidelines,
287:technologies. It assumes the network must run
1032:urn:schemas-wifialliance-org:device:WFADevice
782:and the open-source router software projects
1780:"Device Security and Security Console V 1.0"
1236:
1117:
857:
2175:
1192:
1190:
1168:
1166:
557:UPnP media servers are available for most
2253:
2178:IEEE Transactions on Consumer Electronics
2152:"OCF - UPnP Standards & Architecture"
2098:"OCF - UPnP Standards & Architecture"
1852:
1841:Journal of the Brazilian Computer Society
1498:International Electrotechnical Commission
1330:"Multicast and Unicast UDP HTTP Messages"
1120:"What is UPnP (Universal Plug and Play)?"
1077:List of UPnP AV media servers and clients
895:
505:International Electrotechnical Commission
432:Another capability of UPnP networking is
2233:
1118:Velimirovic, Andreja (13 January 2022).
852:"firewall-hole-punching"-feature of UPnP
752:Internet Gateway Device Control Protocol
31:
2240:S. Cheshire; M. Krochmal (April 2013).
1211:
1187:
1163:
442:General Event Notification Architecture
14:
2401:
2058:"CERT/CC Vulnerability Note VU#339275"
1959:"US-CERT Vulnerability Note VU#357851"
1867:
1249:"UPnP InternetGatewayDevice v1.0/v2.0"
322:UPnP uses UDP port 1900, and all used
2005:
427:
190:ISO/IEC 29341 in December 2008.
1649:"UPnP not working with my FRITX!Box"
948:
912:
611:Web4CE (CEA 2014) for UPnP Remote UI
511:OpenCable Home Networking Protocol.
1554:
1055:Comparison of UPnP AV media servers
644:(display and control options) as a
580:
173:Dynamic Host Configuration Protocol
24:
2419:Windows communication and services
2342:
2156:Open Connectivity Foundation (OCF)
1932:
1586:CEA R7 Home Home Network Committee
1145:"Using the UPnP Control Point API"
905:of its design and implementation.
851:
632:for Remote User Interface on UPnP
25:
2450:
2389:UPnP Standards & Architecture
2377:
1868:Eastep, Thomas M. (4 June 2014).
1302:. 5 February 2009. Archived from
814:
656:-based communications method for
364:Simple Service Discovery Protocol
245:
2006:Moore, H. D. (29 January 2013).
1588:. 1 January 2011. Archived from
1071:Internet Gateway Device Protocol
1060:Devices Profile for Web Services
1002:Devices Profile for Web Services
953:
917:
741:
616:Consumer Electronics Association
613:- CEA-2014 standard designed by
514:
186:UPnP was published as a 73-part
2314:
2290:
2246:Internet Engineering Task Force
2204:
2169:
2144:
2118:
2104:
2090:
2064:
2050:
2021:
1999:
1977:
1951:
1926:
1904:
1883:
1861:
1828:
1802:
1772:
1742:
1717:
1692:
1667:
1641:
1629:
1604:
1574:
1548:
1512:
1486:
1472:Digital Living Network Alliance
1460:
1435:
1406:
1348:
1255:. UPnP Forum. 10 December 2010.
1219:"UPnP Device Architecture v2.0"
1198:"UPnP Device Architecture v1.1"
1174:"UPnP Device Architecture v1.0"
1065:Digital Living Network Alliance
1031:
1030:defines a set of "WFA device" (
794:are currently known to support
533:
501:Digital Living Network Alliance
464:
452:
2362:Michael Jeronimo, Jack Weast:
2303:. January 2006. Archived from
1321:
1285:
1259:
1207:. UPnP Forum. 15 October 2008.
1183:. UPnP Forum. 15 October 2008.
1137:
1111:
369:
13:
1:
2072:"CallStranger CVE-2020-12695"
1529:. 30 May 2013. Archived from
1527:Cable Television Laboratories
1104:
875:IGMP snooping and reliability
723:Traffic Specification (TSPEC)
660:on a UPnP home network using
587:UPnP MediaServer ControlPoint
509:Cable Television Laboratories
418:Simple Object Access Protocol
329:
197:Media and device independence
193:Other UPnP features include:
100:zero-configuration networking
2352:, McGraw-Hill Professional,
995:Open Connectivity Foundation
705:(client-side/front-end) and
618:'s R7 Home Network Committee
357:
7:
1149:Microsoft Developer Network
1048:
809:
798:as an alternative to UPnP.
278:
118:
94:Conceptually, UPnP extends
27:Set of networking protocols
10:
2455:
1443:"Device Control Protocols"
1088:Port (computer networking)
908:
827:service, or implement the
410:
1854:10.1007/s13173-010-0022-2
1750:"Device Protection V 1.0"
1653:Syncthing Community Forum
1082:NAT Port Mapping Protocol
926:This section needs to be
664:and a special version of
599:UPnP RenderingControl DCP
2190:10.1109/TCE.2005.1405701
1987:. The H. 30 January 2013
1555:EDN (9 September 2005).
858:Access from the Internet
719:Traffic Identifier (TID)
701:QoS for UPnP consist of
682:QoS (quality of service)
678:QoS (quality of service)
1912:"Hacking The Interwebs"
829:Device Security Service
145:Internet Protocol Suite
139:. It is a distributed,
41:Universal Plug and Play
2414:Windows administration
2278:Cite journal requires
1729:miniupnp.tuxfamily.org
1385:"UPnP AV Architecture"
964:is missing information
896:Callback vulnerability
593:UPnP MediaRenderer DCP
188:international standard
37:
1093:Port Control Protocol
1040:Wi-Fi Protected Setup
1013:Port Control Protocol
480:(MS) version 2.0 and
35:
2394:ISO/IEC 29341-1:2011
1870:"Shorewall and UPnP"
1536:on 11 September 2014
1253:openconnectivity.org
1226:openconnectivity.org
1205:openconnectivity.org
547:with other devices.
542:UPnP AV media server
470:UPnP AV architecture
264:Programmatic control
256:programming language
125:consumer electronics
102:for residential and
49:networking protocols
2439:Discovery protocols
2429:Servers (computing)
2348:Golden G. Richard:
2310:on 8 December 2022.
1816:on 10 December 2013
1336:on 30 December 2006
1151:. 14 September 2012
727:Traffic Stream (TS)
652:device through any
291:(IP) and then uses
1965:. 30 November 2012
1760:on 17 October 2014
1273:. 10 December 2008
434:event notification
428:Event notification
420:(SOAP). Much like
177:Domain Name System
165:controlled devices
133:personal computers
91:(known as HTTPU).
73:event notification
38:
2334:on 22 March 2021.
2038:. 8 February 2013
1914:. 12 January 2008
1790:on 31 August 2014
1500:. 23 October 2013
990:
989:
947:
946:
825:Device Protection
746:One solution for
559:operating systems
507:IEC 62481-1, and
289:Internet Protocol
283:UPnP uses common
141:open architecture
57:Internet gateways
53:Internet Protocol
16:(Redirected from
2446:
2365:
2351:
2336:
2335:
2333:
2327:. Archived from
2326:
2318:
2312:
2311:
2309:
2302:
2294:
2288:
2287:
2281:
2276:
2274:
2266:
2264:
2262:
2257:
2255:10.17487/RFC6886
2237:
2231:
2230:
2228:
2226:
2216:
2208:
2202:
2201:
2173:
2167:
2166:
2164:
2162:
2148:
2142:
2141:
2139:
2137:
2122:
2116:
2115:
2108:
2102:
2101:
2094:
2088:
2087:
2085:
2083:
2074:. Archived from
2068:
2062:
2061:
2054:
2048:
2047:
2045:
2043:
2033:
2025:
2019:
2018:
2016:
2014:
2003:
1997:
1996:
1994:
1992:
1981:
1975:
1974:
1972:
1970:
1955:
1949:
1948:
1946:
1944:
1939:
1933:Garcia, Daniel.
1930:
1924:
1923:
1921:
1919:
1908:
1902:
1901:
1899:
1897:
1887:
1881:
1880:
1878:
1876:
1865:
1859:
1858:
1856:
1832:
1826:
1825:
1823:
1821:
1812:. Archived from
1806:
1800:
1799:
1797:
1795:
1786:. Archived from
1776:
1770:
1769:
1767:
1765:
1756:. Archived from
1746:
1740:
1739:
1737:
1735:
1721:
1715:
1714:
1712:
1710:
1696:
1690:
1689:
1687:
1685:
1671:
1665:
1664:
1662:
1660:
1645:
1639:
1633:
1627:
1626:
1624:
1622:
1608:
1602:
1601:
1599:
1597:
1592:on 29 April 2013
1578:
1572:
1571:
1569:
1567:
1552:
1546:
1545:
1543:
1541:
1535:
1524:
1516:
1510:
1509:
1507:
1505:
1490:
1484:
1483:
1481:
1479:
1464:
1458:
1457:
1455:
1453:
1439:
1433:
1432:
1430:
1428:
1418:
1410:
1404:
1403:
1401:
1399:
1389:
1381:
1372:
1371:
1369:
1367:
1352:
1346:
1345:
1343:
1341:
1325:
1319:
1318:
1316:
1314:
1308:
1297:
1289:
1283:
1282:
1280:
1278:
1263:
1257:
1256:
1245:
1234:
1233:
1232:. 17 April 2020.
1223:
1215:
1209:
1208:
1202:
1194:
1185:
1184:
1178:
1170:
1161:
1160:
1158:
1156:
1141:
1135:
1134:
1132:
1130:
1115:
1033:
985:
982:
976:
957:
949:
942:
939:
933:
921:
920:
913:
581:Other components
544:
543:
252:Operating system
212:), home wiring (
135:, and networked
21:
2454:
2453:
2449:
2448:
2447:
2445:
2444:
2443:
2399:
2398:
2380:
2366:, Intel Press,
2363:
2349:
2345:
2343:Further reading
2340:
2339:
2331:
2324:
2320:
2319:
2315:
2307:
2300:
2296:
2295:
2291:
2279:
2277:
2268:
2267:
2260:
2258:
2238:
2234:
2224:
2222:
2221:. 10 March 2009
2214:
2210:
2209:
2205:
2174:
2170:
2160:
2158:
2150:
2149:
2145:
2135:
2133:
2124:
2123:
2119:
2110:
2109:
2105:
2096:
2095:
2091:
2081:
2079:
2078:on 16 June 2020
2070:
2069:
2065:
2056:
2055:
2051:
2041:
2039:
2031:
2027:
2026:
2022:
2012:
2010:
2004:
2000:
1990:
1988:
1983:
1982:
1978:
1968:
1966:
1957:
1956:
1952:
1942:
1940:
1937:
1931:
1927:
1917:
1915:
1910:
1909:
1905:
1895:
1893:
1889:
1888:
1884:
1874:
1872:
1866:
1862:
1833:
1829:
1819:
1817:
1808:
1807:
1803:
1793:
1791:
1778:
1777:
1773:
1763:
1761:
1748:
1747:
1743:
1733:
1731:
1723:
1722:
1718:
1708:
1706:
1698:
1697:
1693:
1683:
1681:
1673:
1672:
1668:
1658:
1656:
1655:. 12 April 2022
1647:
1646:
1642:
1634:
1630:
1620:
1618:
1610:
1609:
1605:
1595:
1593:
1580:
1579:
1575:
1565:
1563:
1553:
1549:
1539:
1537:
1533:
1522:
1518:
1517:
1513:
1503:
1501:
1492:
1491:
1487:
1477:
1475:
1466:
1465:
1461:
1451:
1449:
1441:
1440:
1436:
1426:
1424:
1416:
1412:
1411:
1407:
1397:
1395:
1394:. 31 March 2013
1387:
1383:
1382:
1375:
1365:
1363:
1354:
1353:
1349:
1339:
1337:
1326:
1322:
1312:
1310:
1309:on 1 April 2014
1306:
1295:
1291:
1290:
1286:
1276:
1274:
1265:
1264:
1260:
1247:
1246:
1237:
1221:
1217:
1216:
1212:
1200:
1196:
1195:
1188:
1176:
1172:
1171:
1164:
1154:
1152:
1143:
1142:
1138:
1128:
1126:
1124:phoenixNAP Blog
1116:
1112:
1107:
1051:
986:
980:
977:
970:
958:
943:
937:
934:
931:
922:
918:
911:
898:
877:
860:
817:
812:
744:
687:streaming media
650:home networking
583:
541:
540:
536:
517:
467:
455:
430:
413:
372:
360:
332:
281:
137:home appliances
121:
28:
23:
22:
15:
12:
11:
5:
2452:
2442:
2441:
2436:
2431:
2426:
2424:Mobile content
2421:
2416:
2411:
2397:
2396:
2391:
2386:
2384:The UPnP Forum
2379:
2378:External links
2376:
2375:
2374:
2360:
2344:
2341:
2338:
2337:
2313:
2289:
2280:|journal=
2232:
2203:
2168:
2143:
2132:. 12 June 2020
2117:
2114:. 8 June 2020.
2103:
2089:
2063:
2049:
2020:
1998:
1976:
1950:
1935:"UPnP Mapping"
1925:
1903:
1882:
1860:
1847:(4): 261–277.
1827:
1801:
1771:
1741:
1716:
1691:
1666:
1640:
1628:
1603:
1573:
1547:
1511:
1485:
1459:
1434:
1423:. 12 July 2006
1405:
1373:
1347:
1320:
1284:
1258:
1235:
1210:
1186:
1162:
1136:
1109:
1108:
1106:
1103:
1102:
1101:
1096:
1090:
1085:
1079:
1074:
1068:
1062:
1057:
1050:
1047:
1046:
1045:
1044:
1043:
1028:Wi-Fi Alliance
988:
987:
961:
959:
952:
945:
944:
925:
923:
916:
910:
907:
897:
894:
876:
873:
859:
856:
821:authentication
816:
815:Authentication
813:
811:
808:
743:
740:
739:
738:
732:
731:
730:
691:near real-time
689:that is often
675:
674:
673:
602:
596:
590:
582:
579:
552:control points
535:
532:
531:
530:
527:
524:
516:
513:
466:
463:
454:
451:
429:
426:
422:function calls
412:
409:
371:
368:
359:
356:
352:DNS forwarding
331:
328:
317:Internet Draft
280:
277:
276:
275:
271:
268:
265:
262:
259:
249:
235:
232:User interface
229:
224:). No special
198:
161:control points
120:
117:
47:) is a set of
26:
9:
6:
4:
3:
2:
2451:
2440:
2437:
2435:
2434:Media servers
2432:
2430:
2427:
2425:
2422:
2420:
2417:
2415:
2412:
2410:
2409:Digital media
2407:
2406:
2404:
2395:
2392:
2390:
2387:
2385:
2382:
2381:
2373:
2372:0-9717861-1-9
2369:
2361:
2359:
2358:0-07-137959-2
2355:
2347:
2346:
2330:
2323:
2317:
2306:
2299:
2293:
2285:
2272:
2256:
2251:
2247:
2243:
2236:
2220:
2213:
2207:
2199:
2195:
2191:
2187:
2183:
2179:
2172:
2157:
2153:
2147:
2131:
2127:
2121:
2113:
2107:
2099:
2093:
2077:
2073:
2067:
2059:
2053:
2037:
2030:
2024:
2009:
2002:
1986:
1980:
1964:
1960:
1954:
1936:
1929:
1913:
1907:
1892:
1886:
1871:
1864:
1855:
1850:
1846:
1842:
1838:
1831:
1815:
1811:
1805:
1789:
1785:
1781:
1775:
1759:
1755:
1751:
1745:
1730:
1726:
1720:
1705:
1701:
1695:
1680:
1676:
1670:
1654:
1650:
1644:
1637:
1632:
1617:
1613:
1607:
1591:
1587:
1583:
1577:
1562:
1558:
1551:
1532:
1528:
1521:
1515:
1499:
1495:
1489:
1473:
1469:
1463:
1448:
1444:
1438:
1422:
1415:
1409:
1393:
1386:
1380:
1378:
1362:. 23 May 2014
1361:
1357:
1351:
1335:
1331:
1324:
1305:
1301:
1294:
1288:
1272:
1268:
1262:
1254:
1250:
1244:
1242:
1240:
1231:
1227:
1220:
1214:
1206:
1199:
1193:
1191:
1182:
1175:
1169:
1167:
1150:
1146:
1140:
1125:
1121:
1114:
1110:
1100:
1097:
1094:
1091:
1089:
1086:
1083:
1080:
1078:
1075:
1072:
1069:
1066:
1063:
1061:
1058:
1056:
1053:
1052:
1041:
1036:
1035:
1029:
1025:
1024:
1023:
1020:
1018:
1014:
1010:
1005:
1003:
998:
996:
984:
974:
968:
965:
962:This article
960:
956:
951:
950:
941:
929:
924:
915:
914:
906:
902:
893:
889:
886:
885:IGMP snooping
881:
872:
868:
864:
855:
853:
849:
845:
841:
837:
832:
830:
826:
822:
807:
805:
801:
797:
793:
789:
785:
781:
777:
773:
768:
764:
761:
757:
753:
750:, called the
749:
748:NAT traversal
742:NAT traversal
736:
735:Remote Access
733:
728:
724:
720:
716:
715:Traffic Class
712:
708:
707:Source Device
704:
700:
699:
697:
692:
688:
683:
679:
676:
671:
667:
663:
659:
655:
651:
647:
643:
639:
635:
631:
627:
623:
619:
617:
612:
609:
608:
606:
603:
600:
597:
594:
591:
588:
585:
584:
578:
576:
572:
568:
564:
560:
555:
553:
548:
545:
528:
525:
522:
521:
520:
515:AV components
512:
510:
506:
502:
497:
493:
491:
487:
483:
482:MediaRenderer
479:
474:
471:
462:
460:
450:
447:
443:
439:
435:
425:
423:
419:
408:
406:
402:
398:
394:
390:
386:
385:serial number
382:
378:
367:
365:
355:
353:
349:
345:
342:
338:
327:
325:
320:
318:
314:
310:
306:
302:
298:
294:
290:
286:
272:
270:Extensibility
269:
266:
263:
260:
257:
253:
250:
247:
243:
239:
236:
233:
230:
227:
226:device driver
223:
219:
215:
211:
207:
203:
199:
196:
195:
194:
191:
189:
184:
183:information.
182:
178:
174:
168:
166:
162:
158:
154:
150:
146:
142:
138:
134:
130:
126:
116:
112:
110:
105:
101:
97:
96:plug and play
92:
90:
86:
82:
78:
74:
70:
65:
62:
58:
54:
50:
46:
42:
34:
30:
19:
2329:the original
2316:
2305:the original
2292:
2271:cite journal
2259:. Retrieved
2235:
2225:11 September
2223:. Retrieved
2206:
2184:(1): 69–75.
2181:
2177:
2171:
2161:27 September
2159:. Retrieved
2155:
2146:
2134:. Retrieved
2129:
2120:
2106:
2092:
2080:. Retrieved
2076:the original
2066:
2052:
2042:11 September
2040:. Retrieved
2023:
2013:11 September
2011:. Retrieved
2001:
1991:11 September
1989:. Retrieved
1979:
1969:11 September
1967:. Retrieved
1953:
1943:11 September
1941:. Retrieved
1928:
1918:11 September
1916:. Retrieved
1906:
1896:11 September
1894:. Retrieved
1885:
1875:11 September
1873:. Retrieved
1863:
1844:
1840:
1830:
1818:. Retrieved
1814:the original
1804:
1794:11 September
1792:. Retrieved
1788:the original
1774:
1764:11 September
1762:. Retrieved
1758:the original
1744:
1734:18 September
1732:. Retrieved
1728:
1719:
1709:18 September
1707:. Retrieved
1703:
1694:
1684:18 September
1682:. Retrieved
1678:
1669:
1659:18 September
1657:. Retrieved
1652:
1643:
1631:
1621:18 September
1619:. Retrieved
1615:
1606:
1596:11 September
1594:. Retrieved
1590:the original
1576:
1566:27 September
1564:. Retrieved
1560:
1550:
1540:11 September
1538:. Retrieved
1531:the original
1514:
1504:11 September
1502:. Retrieved
1488:
1478:11 September
1476:. Retrieved
1474:. March 2014
1462:
1452:11 September
1450:. Retrieved
1437:
1427:11 September
1425:. Retrieved
1408:
1398:11 September
1396:. Retrieved
1366:11 September
1364:. Retrieved
1350:
1340:11 September
1338:. Retrieved
1334:the original
1323:
1313:11 September
1311:. Retrieved
1304:the original
1287:
1277:11 September
1275:. Retrieved
1261:
1252:
1225:
1213:
1204:
1180:
1155:11 September
1153:. Retrieved
1139:
1129:27 September
1127:. Retrieved
1123:
1113:
1021:
1006:
999:
991:
978:
963:
935:
927:
903:
899:
890:
882:
878:
869:
865:
861:
833:
828:
824:
818:
769:
765:
745:
734:
726:
722:
718:
714:
706:
702:
677:
614:
610:
604:
598:
592:
586:
556:
551:
549:
539:
537:
534:Media server
518:
498:
494:
492:brand name.
481:
477:
475:
469:
468:
465:AV standards
456:
453:Presentation
445:
437:
431:
414:
396:
392:
373:
361:
333:
321:
282:
258:independence
246:Presentation
237:
234:(UI) control
192:
185:
169:
164:
160:
122:
113:
109:IP addresses
93:
83:1900) using
66:
44:
40:
39:
29:
938:August 2017
844:Adobe Flash
703:Sink Device
654:web-browser
478:MediaServer
459:web browser
370:Description
242:web browser
175:(DHCP) and
2403:Categories
2219:UPnP Forum
2130:Lifehacker
2036:UPnP Forum
1784:UPnP Forum
1754:UPnP Forum
1447:UPnP Forum
1421:UPnP Forum
1392:UPnP Forum
1300:UPnP Forum
1105:References
1073:(UPnP IGD)
1011:-standard
981:April 2023
658:CE devices
488:under the
330:Addressing
238:Optionally
216:) and RF (
147:(TCP/IP),
1820:1 January
1360:Microsoft
1084:(NAT-PMP)
973:talk page
840:firewalls
804:Fritz!Box
760:firewalls
713:such as;
642:interface
630:Framework
490:Streamium
401:variables
397:arguments
358:Discovery
309:multicast
218:Bluetooth
131:devices,
85:multicast
2261:8 August
2248:(IETF).
2198:11792030
1181:upnp.org
1099:Zeroconf
1049:See also
810:Problems
788:OPNsense
774:and the
696:internet
662:ethernet
646:web page
638:Internet
636:and the
634:Networks
626:Protocol
563:software
438:eventing
405:run time
389:commands
285:Internet
279:Protocol
206:FireWire
202:Ethernet
119:Overview
2136:14 June
2082:14 June
1963:CERT/CC
1017:NAT-PMP
997:(OCF).
928:updated
909:History
836:routers
792:pfSense
784:OpenWrt
776:NAT-PMP
756:routers
711:classes
670:CE-HTML
668:called
624:-based
486:Philips
446:evented
411:Control
393:actions
313:unicast
248:below).
167:(CDs).
159:. UPnP
89:unicast
51:on the
2370:
2356:
2196:
1704:GitHub
1679:GitHub
1616:GitHub
1067:(DLNA)
1015:. The
790:, and
346:
337:AutoIP
307:using
208:, IR (
155:, and
129:mobile
2332:(PDF)
2325:(PDF)
2308:(PDF)
2301:(PDF)
2215:(PDF)
2194:S2CID
2032:(PDF)
1938:(PDF)
1534:(PDF)
1523:(PDF)
1417:(PDF)
1388:(PDF)
1307:(PDF)
1296:(PDF)
1222:(PDF)
1201:(PDF)
1177:(PDF)
1095:(PCP)
436:, or
391:, or
244:(see
222:Wi-Fi
181:state
61:Wi-Fi
2368:ISBN
2354:ISBN
2284:help
2263:2014
2227:2014
2163:2023
2138:2020
2084:2020
2044:2014
2015:2014
1993:2014
1971:2014
1945:2014
1920:2014
1898:2014
1877:2014
1822:2012
1796:2014
1766:2014
1736:2023
1711:2023
1686:2023
1661:2023
1623:2023
1598:2014
1568:2023
1542:2014
1506:2014
1480:2014
1454:2014
1429:2014
1400:2014
1368:2014
1342:2014
1315:2014
1279:2014
1157:2014
1131:2023
1026:The
1009:IETF
848:HTTP
838:and
758:and
666:HTML
628:and
348:3927
341:IETF
299:and
297:SOAP
293:HTTP
254:and
214:G.hn
210:IrDA
157:SOAP
149:HTTP
104:SOHO
81:port
69:HTTP
45:UPnP
18:UPnP
2250:doi
2186:doi
1849:doi
1561:EDN
1230:OCF
883:If
802:'s
800:AVM
796:PCP
780:AVM
772:PCP
622:Web
575:DVR
571:NAS
381:XML
377:URL
344:RFC
324:TCP
305:UDP
301:XML
153:XML
77:UDP
2405::
2275::
2273:}}
2269:{{
2244:.
2217:.
2192:.
2182:51
2180:.
2154:.
2128:.
2034:.
1961:.
1845:16
1843:.
1839:.
1782:.
1752:.
1727:.
1702:.
1677:.
1651:.
1614:.
1584:.
1559:.
1525:.
1496:.
1470:.
1445:.
1419:.
1390:.
1376:^
1358:.
1298:.
1269:.
1251:.
1238:^
1228:.
1224:.
1203:.
1189:^
1179:.
1165:^
1147:.
1122:.
786:,
698:.
620:.
567:PC
538:A
295:,
220:,
204:,
151:,
127:,
111:.
59:,
2286:)
2282:(
2265:.
2252::
2229:.
2200:.
2188::
2165:.
2140:.
2100:.
2086:.
2060:.
2046:.
2017:.
1995:.
1973:.
1947:.
1922:.
1900:.
1879:.
1857:.
1851::
1824:.
1798:.
1768:.
1738:.
1713:.
1688:.
1663:.
1638:.
1625:.
1600:.
1570:.
1544:.
1508:.
1482:.
1456:.
1431:.
1402:.
1370:.
1344:.
1317:.
1281:.
1159:.
1133:.
1042:.
983:)
979:(
975:.
969:.
940:)
936:(
930:.
672:.
375:(
79:(
43:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
