ISO/IEC 29341-16-1:2011

ISO/IEC 29341-16-1
Edition 1.0 2011-08
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture –
Part 16-1: Low Power Device Control Protocol – Low Power Architecture

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about ISO/IEC copyright or have an enquiry about obtaining additional rights to this
publication, please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
 Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
 IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
 Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
 Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
ISO/IEC 29341-16-1
Edition 1.0 2011-08
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture –
Part 16-1: Low Power Device Control Protocol – Low Power Architecture

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
Q
ICS 35.200 ISBN 978-2-88912-645-3

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 1 —
CONTENTS
Glossary . 3
1  Introduction . 4
2  UPnP Low Power Feature Overview . 4
2.1  The Need for UPnP Low Power . 4
2.2  System Power States . 4
2.3  UPnP Low Power Network Elements . 5
2.4  Overarching Use Cases . 6
2.4.1  UPnP Low Power Solution - Without Proxy . 6
2.4.2  UPnP Low Power Solution – With Basic Power Management Proxy . 7
2.5  Low Level Use Cases . 8
2.5.1  Use Case 1 – Device Waking PC without Use of Proxy . 9
2.5.2  Use Case 2 – Node Going to Sleep . 10
2.5.3  Use Case 3 – Device Entering System . 11
2.5.4  Use case 4 – Device leaving system . 12
2.5.5  Use Case 5 – Node Changing IP Address . 13
2.5.6  Use Case 6 – Device Waking PC – Using proxy . 14
3  Theory of Operation . 15
3.1  Impact on UPnP Device Architecture 1.0 and 1.1 . 15
3.2  UPnP Low Power Requirements . 15
3.2.1  Low Power Requirements and Compatibility with Legacy Control
Points . 16
3.2.2  Low Power Requirements Supported By Low Power Aware Control
Point . 16
3.2.3  UPnP Low Power states . 17
3.2.4  New SSDP headers . 21
3.2.5  Bearer Dependent Wake Up Mechanism . 22
3.2.6  UPnP Low Power Devices . 22
3.2.7  UPnP Power Management Proxy . 24
3.2.8  UPnP Low Power Aware Control Point . 26
3.3  Architecture Sequence Diagrams . 26
3.3.1  Scenarios Without proxy . 26
3.3.2  Scenarios with Basic Power Management Proxy . 33
4  UPnP Low Power Service Protocol . 36
5  UPnP Low Power Proxy Service Protocol . 36
6  Use of UPnP Low Power Feature by Applications . 36
6.1  Digital Media Adapter / Player . 36
6.2  Mobile / Handheld . 36
7  References . 37

Figure 1 — UPnP Low Power solution without Proxy . 6
Figure 2 — UPnP Low Power Solution with Basic Proxy . 7
Figure 3 — Device waking PC without use of proxy . 9
Figure 4 — Node going to sleep . 10
Figure 5 — Device Entering System . 11

XXXX: © IEC:2010 — 2 — 29341-16-1 © ISO/IEC:2011(E)
Figure 6 — Device Leaving System . 12
Figure 7 — Node Changing IP Address . 13
Figure 8 — Device waking PC – using Proxy . 14
Figure 9 — UPnP Low Power states. . 19
Figure 10 — Basic functionality between autonomous wake up low power device in
Transparent Sleep and Deep Sleep Online, Legacy and Low Power Aware Control
Points without Proxy. . . 27
Figure 11 — Basic functionality between controlled wake up sleep device in
Transparent Sleep and Deep Sleep Offline, Legacy and Low Power Aware Control
points without Proxy. . 28
Figure 12 — Wake up functionality between autonomous wake up device and Low
Power Aware Control points without Proxy . 29
Figure 13 — Basic functionality between controlled wake up device in Transparent
Sleep and Deep Sleep Offline, Legacy and Low Power Aware Control Points without
Proxy. . 31
Figure 14 — Interaction of a Low Power UPnP device with a Basic Power Management
Proxy, a Low Power Aware Control Point and a Legacy Control Point . 33
Figure 15 — Low Power Aware Control Point waking up a device from Deep Sleep
Offline State . 35

Table 1 — Low Power requirements supported by Legacy Control Point and Low Power
Aware Control Point . 15
Table 2 — UPnP Low Power States . 18
Table 3 — State Machine Transition Description . 21
Table 4 — SSDP UPnP Low Power Extension Headers . 22
Table 5 — UPnP Low Power Device Requirements . 23
Table 6 — UPnP Basic Power Management Proxy Requirements . 24

29341-16-1 29341-16-1 © ISO/IEC:2011(E) ISO/IEC:2011(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 16-1: Low Power Device Control Protocol –
Low Power Architecture
FOREWORD
1) ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in
the development of International Standards. Their preparation is entrusted to technical committees; any ISO and
IEC member body interested in the subject dealt with may participate in this preparatory work. International
governmental and non-governmental organizations liaising with ISO and IEC also participate in this preparation.
2) In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
3) The formal decisions or agreements of IEC and ISO on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation
from all interested IEC and ISO member bodies.
4) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC and ISO member bodies in that sense. While all reasonable efforts are made to ensure that the
technical content of IEC, ISO and ISO/IEC publications is accurate, IEC or ISO cannot be held responsible for
the way in which they are used or for any misinterpretation by any end user.
5) In order to promote international uniformity, IEC and ISO member bodies undertake to apply IEC, ISO and
ISO/IEC publications transparently to the maximum extent possible in their national and regional publications.
Any divergence between any ISO/IEC publication and the corresponding national or regional publication
should be clearly indicated in the latter.
6) ISO and IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for
any equipment declared to be in conformity with an ISO/IEC publication.
7) All users should ensure that they have the latest edition of this publication.
8) No liability shall attach to IEC or ISO or its directors, employees, servants or agents including individual experts
and members of their technical committees and IEC or ISO member bodies for any personal injury, property
damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees)
and expenses arising out of the publication of, use of, or reliance upon, this ISO/IEC publication or any other IEC,
ISO or ISO/IEC publications.
9) Attention is drawn to the normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
10) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
International Standard ISO/IEC 29341-16-1 was prepared by UPnP Forum Steering
committee , was adopted, under the fast track procedure, by subcommittee 25:
Interconnection of information technology equipment, of ISO/IEC joint technical committee 1:
Information technology.
The list of all currently available parts of the ISO/IEC 29341 series, under the general title
Information technology – UPnP device architecture, can be found on the IEC web site.
This International Standard has been approved by vote of the member bodies, and the voting
results may be obtained from the address given on the second title page.

—————————
rd
UPnP Forum Steering committee, UPnP Forum, 3855 SW 153 Drive, Beaverton, Oregon 97006 USA. See also
“Introduction”.
2929341-16-1 341-16-1 © ISO/IEC:2011(E) ISO/IEC:2011(E)

IMPORTANT – The “colour inside” logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this publication using a colour printer.

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 3 —
Glossary
ACPI
Advanced Configuration and Power Interface
AP
Access Point: Any entity that has station functionality and provides access to the distribution
services (Ethernet network), via the wireless medium for associated stations
AV
Audio / Video
BOOTID
BOOTID is a part of the SSDP:Alive header defined in UPnP Device Architecture 1.1 and is
defined as a number that is increased each time device sends an initial announcement
BPMPX
Basic Power Management Proxy
BTH
Bluetooth
CP
Control Point
DHCP
Dynamic Host Configuration Protocol
DMA
Digital Media Adapter
DMP
Digital Media Player
IP
Internet Protocol
LPACP
Low Power Aware Control Point
NIC
Network Interface Card
OSPM
Operating System-directed Power Management
PAN
Personal Area Network
PC
Personal Computer
PM
Power Management
PM Service
UPnP Based Power Management Service
SSDP
Simple Service Discovery Protocol
Standby period
Time interval SoftAP monitors traffic for no activity before going to standby mode.

XXXX: © IEC:2010 — 4 — 29341-16-1 © ISO/IEC:2011(E)
UDN
Unique Device Number
UI
User Interface
UUID
Universally Unique Identifier
UPnP
Universal Plug and Play
WoLAN
Wake On LAN
WoWLAN
Wake on Wireless LAN
1 Introduction
The UPnP Low Power architecture allows devices implementing power saving modes to
conserve energy. The purpose of this document is to define an architecture that will address
the issue of reporting and tracking power states of nodes in a network. The UPnP Low Power
solution is designed to enable nodes in the network to report and track the Low Power states
of other nodes in the network. Additionally, for nodes that support wake up capabilities, this
architecture addresses methods to wake up those nodes when required. The objective of the
UPnP Low Power solution is to allow UPnP devices to conserve energy and still be
discoverable by UPnP Control Points. The UPnP Control Point will be aware of the UPnP
devices and services implemented on a Low Power device even when the Low Power device
is in a power savings mode.
This architecture document defines two UPnP services that comprise the UPnP Low Power
framework:
• Low Power device service
• Basic Power Management Proxy service
The Low Power device service allows UPnP devices to transition to low power states and still
be part of the UPnP network. The Basic Power Management Proxy service can optionally
represent the sleeping UPnP devices in the network and is capable of certain limited functions
to support the discovery of Low Power devices that are in a power saving mode. The
introduction of Low Power into the UPnP architecture will help align UPnP with emerging
energy regulation requirements.
2 UPnP Low Power Feature Overview
2.1  The Need for UPnP Low Power
Platforms and devices must be able to run in an energy efficient manner. It is important that
these platforms and devices intelligently transition between system power levels to reduce
system power consumption, heat and noise.  It is equally important that these systems be
able to return to normal running power state with limited impact to the responsiveness of the
overall system. For example, on PC platforms, in the state known as System Standby (G1,
S3), video and hard drive subsystems, and the fan are powered down. In mobile platforms,
where power consumption is a primary consideration, standby mode allows extended battery
life. On desktop platforms, especially in residential environments, system noise is often a
significant issue. Power Management reduces noise by transitioning desktops platforms to a
power saving mode when not in use.
2.2  System Power States
A system can have many power states. The Advanced Configuration and Power Interface
(ACPI) specification was developed to establish industry common interfaces; enabling robust
operating system (OS) directed motherboard device configuration and Power Management of

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 5 —
devices. ACPI is the key element in Operating System-directed configuration and Power
Management (OSPM). For more details, please refer [ACPI].
UPnP Power states are defined in Table 2 in clause 3.2.3. A Low Power device controls its
internal power state and UPnP Low Power implementation advertises the power state of the
Low Power device to other UPnP devices in the network. The UPnP Low Power
implementation abstracts the internal power state of Low Power device and represents the
internal power state as one of the Low Power defined power states in Table 2.
2.3  UPnP Low Power Network Elements
A typical set of power managed networked devices may be a PC, laptop, printer, networked
CE devices or a handheld. Each node on the network that supports UPnP Low Power runs the
UPnP Control Point (CP) and/or UPnP Low Power service. Some nodes may act as a Proxy, if
they wish to represent other UPnP Low Power devices in power savings mode.
• UPnP Low Power Aware Control Point: A device or a UPnP control point that can
monitor the sleep state of other nodes in the network. It can also monitor the entry and
exit of nodes from the network. It may store/cache this information. A UPnP Low
Power Aware Control Point can wake up a device from a sleep state or request the
device to go into a low power state.
• UPnP Low Power Device: A UPnP device informs the UPnP network about change in
power state of the node. It also informs the UPnP networked devices about its entry
into and exit from the network. A UPnP Low Power device can be classified into the
following categories:
a) Sleep-autonomous device: A device that can go to sleep autonomously using
internal timers.
b) Sleep-controlled device: A device that can go to a sleep state on receiving an
external control message.
c) Wake up-autonomous devices: A device that wakes up autonomously using
internal timers.
d) Wake up-controlled devices: A device that requires an external interaction, such
as control message, to wake up.
• UPnP Basic Power Management Proxy: This node will act on behalf of sleeping
devices and make sure that the devices are discoverable if they are in low power
state. This node will also store methods for waking the UPnP Low Power devices.

XXXX: © IEC:2010 — 6 — 29341-16-1 © ISO/IEC:2011(E)
2.4  Overarching Use Cases
The following use cases illustrate the use and need for UPnP Low Power solution.
2.4.1 UPnP Low Power Solution - Without Proxy
PC
d)
b)
Wireless
Dedicate
a)
e)
TV
c)
DMA
a) PC informing DMA that it is going e) PC sending movie
to sleep stream to DMA
b) PC going to sleep
c) DMA requesting PC to wake up
d) PC waking up
Figure 1 — UPnP Low Power solution without Proxy
a) The PC advertises that it is transitioning to a low power state. The transition information is
recorded by the DMA.
b) The PC completes the transition to a low power state.
c) Richard wants to watch a movie on his TV. The movie is stored on the PC, which is in low
power state (power saving mode). The DMA knows that the movie is on the PC (set up
was performed earlier). The DMA wakes up the PC based on the Power management
information it received from the PC. The DMA displays a user friendly message. Richard
observes a “Waking up PC … please wait” message on his TV, while the DMA wakes the
PC.
d) The TV displays a UI showing content selections on the PC. Using the UI, Richard
browses the servers and selects the movie he wants to watch.
e) The PC streams the movie to the TV via the DMA. Richard watches his movie.
The additional information below will help define the use case better.
f) Information regarding the wake up procedure of the PC needs to be communicated to the
DMA before it can wake up the PC. This information may contain wake up patterns (if
present).
g) A Wake on Wireless LAN solution will be required if the PC needs to be woken up using a
wireless link. A Wake on Wireless LAN solution is vendor specific mechanism and not
defined by the UPnP Low Power solution.

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 7 —
h) After the TV is turned off, the PC automatically enters a low power state when not in use.
2.4.2 UPnP Low Power Solution – With Basic Power Management Proxy
DMA
f)
b)
Access
e)
a)
Point PC Mobile
g)
c)
d)
a) PC informing DMA that it is going to g) PC streaming media to Mobile
sleep
b) PC is in a low power state
c) Mobile requesting wake up information from DMA
d) DMA sending wake up information to mobile
e) Mobile waking up the PC
f) PC waking up
Figure 2 — UPnP Low Power Solution with Basic Proxy
a) The PC advertises that it is transitioning to a low power state. The transition information is
recorded by the DMA. The Basic Power Management Proxy implemented on the DMA,
knows the current power state of the PC.
b) The PC completes the transition to a low power state.
c) John wants to watch a movie on his Mobile but the PC with the movie is in a low power
state. The Mobile is aware that the movie is on the PC. However, the Mobile has been out
of the house and is unaware of the current wake up settings of the PC. When the Mobile
comes back into the network, it requests for all sleeping devices from the Basic Power
Management Proxy (DMA).
d) The Basic Power Management Proxy Service on the DMA sends the Sleep state and wake
up information of the PC to the Mobile.
e) A Local UI displayed on the Mobile shows a list of media servers including the ones in low
power state that are discoverable because of the presence of UPnP Basic Power
Management Proxy Service. John selects media server with the movie. The Mobile wakes
up the PC. John observes a “Waking up PC … please wait” message on Mobile.
f) The PC wakes up and John browses the server contents and selects the movie he wants
to watch.
g) The PC streams the movie and John watches it on his Mobile/PDA.
Certain assumptions have been made in the above mentioned use case. They are:
h) The PC is configured to support UPnP Low Power functionality.
i) The Home Network is set up and functioning. The devices are connected via this Home
Network.
j) These devices support UPnP Low Power states to fulfill energy saving requirements.
k) The PC supports ability to enter and exit low power states (i.e. sleep / hibernation).
l) Requirements of what needs to be in place:

XXXX: © IEC:2010 — 8 — 29341-16-1 © ISO/IEC:2011(E)
1) Devices have to be discoverable and eventually available at all times but still be able
to minimize their energy consumption.
2) Media server in devices with limited resources, such as mobile phones must be
available in the background and not interfere with everyday phone use. They must also
be available for accepting incoming file sharing requests.
The additional information below will help define the use case better.
m) Information regarding the wake up procedure of the PC is communicated to a proxy before
it can propagate the wake up information to the mobile/PDA to wake up the PC.
n) In this scenario, the PC conveyed the wake up information to the DMA prior to entering the
sleep state. The DMA was able to act as a proxy and wake up the PC.
2.5  Low Level Use Cases
The following subclause describes the use cases that may arise in a network. The
overarching use cases mentioned above is broken down into smaller use cases that define
specific uses.
In all the diagrams below, the initial request is shown as an orange colored arrow.
The response is shown as a purple colored arrow.
Any information being sent out that does not require response are shown in blue. For example
a) A new device enters a system and announces its entry.
b) An existing device exits from the system and announces its exit.
c) An existing device changes its IP address.

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 9 —
2.5.1 Use Case 1 – Device Waking PC without Use of Proxy
Wired AP
PC
TV
DMA
DMA waking up the PC (1)
PC waking up (2)
PC sending the media stream to the TV via the DMA (3)

Figure 3 — Device waking PC without use of proxy
a) Jim is sitting in this living room and decides to watch a video that is stored on his PC
b) The PC is in a low power state.
c) Using his DMA remote control, Jim selects the stored video option on the DMA.
d) The DMA knows that the PC is in a low power state and it displays the following message:
“Please wait while the PC wakes up” and sends a message to the PC that wakes it up.
e) The packet is sent to the wired AP which forwards it to the PC.
f) The PC wakes up on receipt of the wake up packet and then let’s the DMA know that it is
awake.
g) The DMA sends the request for the list of stored videos.
h) The PC responds with the list (UI).
i) Jim selects a video to play (a basketball game).
j) The message is passed on to PC, which starts streaming the video to the DMA.
k) DMA displays the video on TV.

XXXX: © IEC:2010 — 10 — 29341-16-1 © ISO/IEC:2011(E)
2.5.2 Use Case 2 – Node Going to Sleep
Set Top Box
PC
Laptop
Wireless
Dedicated AP
Set top box sleeping
Laptop sending sleep state change information to all the nodes on

Figure 4 — Node going to sleep
a) Richard has a home network with a laptop, set top box and a PC. The PC and laptop are
awake whereas the set top box is asleep.
b) The laptop initiates process to go to a low power state.
c) The UPnP Low Power application on laptop realizes that the laptop is about to go to sleep.
d) It informs all other nodes on the system about the change in its power state.
e) The PC is awake and immediately updates its database with the new information.
f) Set top box remains asleep and will update its information when it wakes up later by using
the Basic Power Management Proxy service on the PC.

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 11 —
2.5.3 Use Case 3 – Device Entering System
Wireless
Dedicated AP
PC
Laptop
Figure 5 — Device Entering System
a) Ken buys a new laptop. The laptop is pre-configured and supports the UPnP Low Power
feature.
b) The PC in Ken’s home is already awake that time.
c) Ken attaches the new laptop to his home network.
d) The laptop informs PC about its presence and UPnP Low Power capabilities.
e) The packet is forwarded by the dedicated AP to the PC.
f) The PC stores the information regarding the existence of a new machine into the home
network.
g) Ken can use the laptop without any further configuration.
Note: From UPnP Low Power Service point of view, it does not matter what type of device enters a system. The
same message is sent out to all other nodes in network, whenever a laptop / PC / DMA or any other device joins
the network.
XXXX: © IEC:2010 — 12 — 29341-16-1 © ISO/IEC:2011(E)
2.5.4 Use case 4 – Device leaving system
Wireless
Dedicated
PC Lapto
p
Figure 6 — Device Leaving System
Ken wants to take the laptop out of his home network.
h) The PC is awake at the time when Ken presses power down button on the laptop to take it
off the home network.
i) Before halting operation, the laptops UPnP Low Power service informs other devices on
the network that it is about to go down.
j) This information is forwarded by the Dedicated AP to the PC.
k) The PC stores the information that laptop is no longer in the system.
l) If Ken later tries to access the laptop, the PC will display a message stating that the laptop
is no longer in the network.
Note: From a UPnP Low Power service point of view, it does not matter what type of device leaves the home
network system. The same message will be sent out to all nodes in the network, whenever a laptop / PC / DMA or
any other device exits the network.

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 13 —
2.5.5 Use Case 5 – Node Changing IP Address
Set Top
PC
Lapto
Wireless
Dedicated AP
Set top box sleeping
Laptop sending IP address change information to all the nodes on

Figure 7 — Node Changing IP Address
a) Denise has a home network, where the IP addresses are assigned by a DHCP server.
b) The PC and laptop are awake, whereas the recording set top box is in sleep state. PC is
running power management service.
c) The IP address of the laptop changes due to the expiration of the DHCP lease.
d) The UPnP Low Power application on the laptop detects the change in the IP address.
e) It informs all other nodes on the system of its new IP address.
f) The PC is awake and immediately updates its database with the new information.
g) The set top box is a Low Power Aware Control Point that is asleep and will update its
information from the PC or from the Laptop, when it wakes up later.
h) Denise can continue using UPnP Low Power aware applications in her Home Network,
oblivious to all of these changes occurring in the system.

XXXX: © IEC:2010 — 14 — 29341-16-1 © ISO/IEC:2011(E)
2.5.6 Use Case 6 – Device Waking PC – Using proxy
PC
Wired AP
TV
DMA
PC is in the Sleep State
DMA requests Proxy (Laptop) to
wake the PC
Laptop (BPMPX)
Laptop wakes the PC
PC wake up
PC streams video to the DMA
Figure 8 — Device waking PC – using Proxy
a) Jim is sitting in his living room and decides to watch a video that is stored on his PC
b) The PC is in low power state.
c) Jim selects the video option on the DMA using the DMA remote control.
d) The DMA is aware that the PC is in a low power state and displays a user friendly
message, for example, “Please wait while it wakes up the PC”.
e) The DMA requests the Proxy (laptop) to wake up the PC.
f) The Proxy knows the wake up mechanism of the PC and sends a “wake up” packet on the
network.
g) The packet is sent to the Wired Dedicated AP which forwards it to the PC.
h) The PC wakes up on receipt of the wake up packet and let’s the DMA/laptop know that it is
awake.
i) The DMA then sends the request for the list of stored videos.
j) The PC responds with the list (UI).
k) Jim selects a video (a basketball game) on the PC to play.
l) The message is passed to the PC, which starts streaming video to the DMA.
m) DMA displays the video on the TV.

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 15 —
3 Theory of Operation
3.1 Impact on UPnP Device Architecture 1.0 and 1.1
The impact of UPnP Low Power requirements on UPnP Device Architecture v1.0 and v1.1 has
been analyzed. The conclusion is that if the device follows the requirements defined in this
document, there is no impact on the UPnP Device Architecture v1.0 and v1.1. For
compatibility with UPnP Device Architecture v1.1 the device in Transparent Sleep is available
on the network and the BOOTID [UDA 1.1] remains the same when the Low Power device
transitions between Transparent Sleep and Active state. According to UPnP Device
Architecture 1.1, if the device leaves the network and sends a byebye message, the BOOTID
[UDA 1.1] has to be incremented when the device re-joins the network. Therefore the BOOTID
[UDA 1.1] is incremented when device transitions from Deep Sleep Online / Deep Sleep
Offline to Transparent Sleep or Active state.
3.2 UPnP Low Power Requirements
The UPnP Low Power solution is designed to be backward compatible with UPnP DA V1.0.
Table 1 lists the Low Power requirements that are supported by Legacy Control Points and by
Low Power Aware Control Points. The Legacy Control Points are those that do not include or
that cannot interpret the SSDP extensions defined by the UPnP Low Power specification. The
Low Power Aware Control Points are those that implement and are able to interpret the SSDP
extensions defined by the UPnP Low Power architecture. The Low Power Aware Control
Points can be bearer dependent (e.g. LAN, Bluetooth). Low Power devices are UPnP devices
that implement all or some of the different sleep states defined in Table 2 (e.g. Transparent
Sleep, Deep Sleep Online and Deep Sleep Offline) and may transition to any of the low power
states. Depending on the triggers that force the device to transition to different sleep states,
the device can be modeled as a Sleep-autonomous device, a Sleep-controlled device, a Wake
up-autonomous device or a Wake up-Controlled device.
The table below lists the Low Power requirements that are supported by Legacy Control
Points and Low Power Aware Control Points. The terminology in this table is explained in
subsequent subclauses.
Table 1 — Low Power requirements supported by Legacy Control Point and Low Power
Aware Control Point
Requirement Legacy Low Power
a a
CP aware CP
a) Low Power devices must be discoverable in Active and
X X
Transparent Sleep state.
b) A Control Points must be able to distinguish a sleeping device
- X
that will wake up from one that is disconnected.
c) Low Power device’s wake up mechanism should be
- X
discoverable.
d) A Control Point must recognize the transitions by a Low Power
- X
device to low power states.
e) Control Points must be able to identify Low Power devices that
X X
are in Transparent Sleep state.
f) Control Points must be able to identify the sleep state of
- X
sleeping devices.
g) Control Points should be able to request that a device enter a
- X
sleep state.
h) A Low Power device must be able to inform a Control Point that
- X
it is UPnP Low Power aware.
a
“X” = applicable, “-“ = not applicable

XXXX: © IEC:2010 — 16 — 29341-16-1 © ISO/IEC:2011(E)
3.2.1 Low Power Requirements and Compatibility with Legacy Control Points
The following paragraph letter designators—a), b), .—refer to requirements with the same
letter designator in Table 1.
a) Low Power devices must be discoverable in Active and Transparent Sleep state. Sleep
capable or Low Power devices must be discoverable by legacy CP if they are in Active and
Transparent Sleep state. If a device transitions to a deep sleep state (e.g. either Online or
Offline), the device must send an extended byebye message. Legacy Control Points will
conclude that the device left the network. This requirement is not applicable to devices in
deep sleep because they are considered disconnected and the devices are visible only in
Transparent Sleep state.
b) Control Points must be able to distinguish a sleeping device that will wake up from the one
that is disconnected. Legacy Control Points will not see the sleeping devices in any sleep
state other than Transparent Sleep state.
c) Low Power device’s wake up mechanisms should be discoverable. Legacy controls points
cannot interpret the UPnP Low Power information provided by the sleeping devices.
d) A Control Point must recognize the transitions by a Low Power device to low power states.
A Low Power device advertises the transitions to low power state and broadcasts the
sleep period, and the new sleep state to the interested devices acting as Control Points.
Legacy Control Points cannot interpret the information provided by Low Power devices.
e) Control Points must be able to identify Low Power devices that are in Transparent Sleep
state. For Legacy Control Points, Low Power device in Transparent Sleep state appear as
if they are in Active state.
f) Control Points must be able to identify the power state of sleeping devices. Legacy
Control Points cannot identify the sleep state of sleeping Low Power devices. For Legacy
Control Points the devices are either in Active or Disconnected state.
g) Control Points should be able to request that a device enter a sleep state. Legacy Control
Points will not be able to use this mechanism.
h) A Low Power device must be able to inform a Control Point that it is UPnP Low Power
aware. Legacy Control Points cannot interpret the information provided by sleep capable
devices.
3.2.2 Low Power Requirements Supported By Low Power Aware Control Point
The following paragraph letter designators—a), b), .—refer to requirements with the same
letter designator in Table 1.
a) Low Power devices must be discoverable in Active and Transparent Sleep state. Low
Power devices are discoverable by Low Power Aware Control Points. Sleeping devices in
Transparent Sleep state must be discoverable. Sleeping devices in Deep Sleep Online
and Deep Sleep Offline require a Proxy to be discoverable. The wake up mechanism for
devices in Deep Sleep Offline is bearer dependent (e.g. Wake on LAN). A Control Point
can wake up the device if it supports the bearer dependent wake up mechanism. If a Low
Power Aware Control Point does not support the bearer dependent wake up mechanism of
the Low Power device it requires a Basic Power Management Proxy device to wake up the
Low Power device. The BPMPX needs to support the bearer dependent wake up
mechanism of the Low Power device and is also required to have a bearer independent
UPnP control action that can be used by the Low Power Aware Control Point to wake up
devices in Deep Sleep Offline. Low Power Aware Control Points use the information in the
extended byebye message to track the power/sleep state of the Low Power device. The
control point can also query the proxy for the information of all sleeping devices and get
the wake up mechanism and wake the device directly.
b) Control Points must be able to distinguish a sleeping device that will wake up from the one
that is disconnected. If a sleep capable device is in Deep Sleep Offline state, a Basic
Power Management Proxy is required to receive actions from the Control Point. If the
Control Point supports the bearer dependent wake up mechanism, it should wake the
sleeping device. Otherwise, the proxy should wake the sleeping device. This must be
done before the device is able to respond to any control requests. A sleep capable device

29341-16-1 XXXX: © IEC© ISO/IEC:2011(E):2010 — 17 —
can wake up autonomously. In such a case the Low Power device need not provide any
mechanism for waking up on external actions.
c) Low Power device’s wake up mechanism should be discoverable. The wake up
mechanism may be bearer dependent (e.g. Wake on LAN). The wake up mechanism can
be internal (e.g. based on timers in case of autonomous wake up devices) or external (e.g.
control actions or messages defined by the Low Power service). A Basic Power
Management Proxy could receive and utilize this information to wake up a device when a
Low Power Aware Control Point intends to interact with the sleeping device. A Proxy could
be used when a device goes into deep sleep state and requires bearer dependent wake up
mechanism and the Low Power Aware Control Point is bearer agnostic.
d) A Control Point must recognize the transitions by a Low Power device to low power states.
A Low Power device advertises the transitions to low power state and broadcasts the
sleep period, and the new sleep state to the interested devices acting as Control Points.
The only exception to this requirement is when the device transitions from Deep Sleep
Offline to Disconnect state. A Low Power Aware Control Point is capable of recognizing
low power state transitions.
e) Control Points must be able to identify Low Power devices in Transparent Sleep state.
f) Control Points must be able to identify the sleep state of sleeping devices. Low Power
Aware Control Points should be able to identify when a sleeping node is in the network
and should be aware when they leave the network while sleeping.
g) Control Points should be able to request that a device enter a sleep state.
h) A Low Power device must be able to inform a Control Point that it is UPnP Low Power
aware. This information should be presented to the user appropriately.
3.2.3 UPnP Low Power states
The UPnP Low Power architecture defines a set of power states that will allow the device to
conserve energy and still be discoverable and controllable under certain circumstances. The
table also includes the correspondence between the internal UPnP device power state and
the Low Power states.
XXXX: © IEC:2010 — 18 — 29341-16-1 © ISO/IEC:2011(E)
Table 2 — UPnP Low Power States
Active FULL Same ON 802.3: LINK None None On

b
ON/ATTACHED
802.11:ON
BTH: ON/PAN ON
Transparent FULL Same ON 802.3: LINK Invoking the Optional On/

Sleep ON/ATTACHED Wakeup Action on c
Sleep
the device or
802.11: ON/Power
autonomous wake
Save
up
BTH: Sniff &Hold/PAN
ON
Deep Sleep dNew ON 802.3: LINK Invoking the e Sleep
PARTIAL Optional /
Online ON/ATTACHED Wakeup Action on
f
Required
the device (e.g.
802.11: ON/ Power
Unicast Wakeup
Save
Action message)
BTH: Sniff &Hold/PAN
ON
Deep Sleep OFF New OFF 802.3: LINK Bearer specific Sleep
h
Optional /
Offline OFF/ATTACHED wakeup
i
Required
mechanisms i.e.,
802.11: OFF
Wake-On-XXX
BTH: LINK ON/PAN
mechanism (e.g.
OFF
g
WoL )
Non-bearer
specific wakeup
mechanisms (e.g.
infrared)
Autonomous
Wake up
Disconnect OFF New OFF 802.3: LINK Vendor defined None Off
O
...