ISO/IEC 29341-12-11:2008

Information technology - UPnP Device Architecture - Part 12-11: Remote User Interface Device Control Protocol - Remote User Interface Server Service

ISO/IEC 29341-12-11:2008(E) describes the service which is required by all Remote UI server devices. This service is required for all Remote UI clients. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.

General Information

• Status: Published
• Publication Date: 27-Nov-2008
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: DELPUB - Deleted Publication
• Start Date: 15-Jun-2015
• Completion Date: 14-Feb-2026

Overview

ISO/IEC 29341-12-11:2008 - "Information technology - UPnP Device Architecture - Part 12-11: Remote User Interface Device Control Protocol - Remote User Interface Server Service" defines the UPnP service required for Remote UI server devices and used by Remote UI clients. It is part of the ISO/IEC 29341 series (Universal Plug and Play, UPnP) that standardizes peer-to-peer connectivity for intelligent appliances, wireless devices and PCs in homes, small businesses, public spaces and Internet-attached environments. The service is identified by the UPnP service type urn:schemas-upnp-org:service:RemoteUIServer:1 (and referenced as urn:schemas-upnp-org:service:RemoteUIServerDevice).

Key Topics and Requirements

• Service model and ServiceType: Defines the service URN and compliance template for Remote UI servers.
• State variables: Includes required and optional state variables such as A_ARG_TYPE_CompatibleUIs, A_ARG_TYPE_DeviceProfile, A_ARG_TYPE_URI, UIListingUpdate (evented) and an integer lifetime value. These govern capability advertisement and runtime state.
• Actions: Standard action interfaces include GetCompatibleUIs() and SetUILifetime(), with specified arguments, return values and common error codes. Vendor-specific (non-standard) actions are allowed but must be documented.
• Eventing and moderation: Specifies evented variables and rules for change notifications to Remote UI clients.
• Schemas and descriptors: Provides XSD schemas for A_ARG_TYPE_CompatibleUIs and DeviceProfile, plus a complete XML service description for UPnP device stacks.
• Theory of operation: Example state values, argument formats (URI, string, int), UI filters and relationships between actions are included to guide implementation.

Practical Applications

• Remote presentation and control of device user interfaces over a network (smart TVs, set-top boxes, media renderers, printers, IoT appliances).
• Remote accessibility interfaces (off-device control panels, screen sharing or alternate UI delivery).
• Embedded device firmware and middleware that expose UI capabilities to UPnP Remote UI clients.
• Environments that require ad-hoc, standards-based remote UI discovery and dynamic capability negotiation.

Who Should Use This Standard

• Device manufacturers implementing UPnP Remote UI server functionality.
• Firmware and software developers building UPnP stacks, Remote UI clients or interoperability layers.
• System integrators and architects designing connected-device ecosystems that require standardized remote control or display of device UIs.

Related Standards

• ISO/IEC 29341 (UPnP Device Architecture) general parts and Remote UI family parts: -12-1 (RemoteUIClientDevice), -12-2 (RemoteUIServerDevice), -12-10 (RemoteUIClient Service) and other UPnP service definitions in the 29341 series.

Keywords: ISO/IEC 29341-12-11, Remote User Interface Server Service, UPnP, Remote UI, Device Control Protocol, GetCompatibleUIs, SetUILifetime, A_ARG_TYPE_CompatibleUIs, device profile, XSD schema, XML service description.

Standards Content (Sample)

ISO/IEC 29341-12-11
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 12-11: Remote User Interface Device Control Protocol – Remote User
Interface Server Service
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: [e-mail]
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: [e-mail]
Tel.: [phone]
Fax: [phone]
ISO/IEC 29341-12-11
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 12-11: Remote User Interface Device Control Protocol – Remote User
Interface Server Service
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
H
ICS 35.200 ISBN 978-2-88910-910-4

– 2 – 29341-12-11 © ISO/IEC:2008(E)
CONTENTS
FOREWORD .3
ORIGINAL UPNP DOCUMENTS (informative) .5
1. Overview and Scope .7
2. Service Modeling Definitions .8
2.1. ServiceType .8
2.2. State Variables.8
2.2.1. UIListingUpdate .8
2.2.2. A_ARG_TYPE_DeviceProfile .8
2.2.3. A_ARG_TYPE_URI .8
2.2.4. A_ARG_TYPE_CompatibleUIs.9
2.2.5. A_ARG_TYPE_String .9
2.2.6. A_ARG_TYPE_Int .9
2.3. Eventing and Moderation .9
2.4. Actions.10
2.4.1. GetCompatibleUIs.10
2.4.2. SetUILifetime .11
2.4.3. Non-Standard Actions Implemented by a UPnP Vendor .12
2.4.4. Relationships Between Actions.12
2.4.5. Common Error Codes.12
3. Theory of Operation.13
3.1. Example Values of State Variables.13
3.1.1. A_ARG_TYPE_URI .13
3.1.2. A_ARG_TYPE_CompatibleUIs.13
3.1.3. A_ARG_TYPE_DeviceProfile .17
3.1.4. UIListingUpdate .18
3.1.5. UIFilter Examples.18
4. A_ARG_TYPE_CompatibleUIs XSD Schema .19
5. DeviceProfile XSD Schema .20
6. XML Service Description .21

LIST OF TABLES
Table 1: Service State Variables .8
Table 2: Event moderation.9
Table 3: Actions.10
Table 4: Arguments for GetCompatibleUIs().10
Table 5: Arguments for SetUILifetime().11
Table 6: Common Error Codes.12
Table 7: shortName values for known remoting protocols .16

29341-12-11 © ISO/IEC:2008(E) – 3 –
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 12-11: Remote User Interface Device Control Protocol –
Remote User Interface Server Service
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.
IEC and ISO draw attention to the fact that it is claimed that compliance with this document may involve the use of
patents as indicated below.
ISO and IEC take no position concerning the evidence, validity and scope of the putative patent rights. The holders
of the putative patent rights have assured IEC and ISO that they are willing to negotiate free licences or licences
under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect,
the statements of the holders of the putative patent rights are registered with IEC and ISO.
Intel Corporation has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Intel Corporation
Standards Licensing Department
5200 NE Elam Young Parkway
MS: JFS-98
USA – Hillsboro, Oregon 97124
Microsoft Corporation has informed IEC and ISO that it has patent applications or granted patents as listed below:

– 4 – 29341-12-11 © ISO/IEC:2008(E)
6101499 / US; 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US; 7069312 / US;
10/783 524 /US
Information may be obtained from:
Microsoft Corporation
One Microsoft Way
USA – Redmond WA 98052
Philips International B.V. has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Philips International B.V. – IP&S
High Tech campus, building 44 3A21
NL – 5656 Eindhoven
NXP B.V. (NL) has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
NXP B.V. (NL)
High Tech campus 60
NL – 5656 AG Eindhoven
Matsushita Electric Industrial Co. Ltd. has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Matsushita Electric Industrial Co. Ltd.
1-3-7 Shiromi, Chuoh-ku
JP – Osaka 540-6139
Hewlett Packard Company has informed IEC and ISO that it has patent applications or granted patents as listed
below:
5 956 487 / US; 6 170 007 / US; 6 139 177 / US; 6 529 936 / US; 6 470 339 / US; 6 571 388 / US; 6 205
466 / US
Information may be obtained from:
Hewlett Packard Company
1501 Page Mill Road
USA – Palo Alto, CA 94304
Samsung Electronics Co. Ltd. has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Digital Media Business, Samsung Electronics Co. Ltd.
416 Maetan-3 Dong, Yeongtang-Gu,
KR – Suwon City 443-742
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights
other than those identified above. IEC and ISO shall not be held responsible for identifying any or all such patent
rights.
ISO/IEC 29341-12-11 was prepared by UPnP Implementers Corporation and adopted, under the PAS procedure, by
joint technical committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of
ISO and IEC.
The list of all currently available parts of the ISO/IEC 29341 series, under the general title Universal plug and play
(UPnP) 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.

29341-12-11 © ISO/IEC:2008(E) – 5 –
ORIGINAL UPNP DOCUMENTS
(informative)
Reference may be made in this document to original UPnP documents. These references are retained in order to
maintain consistency between the specifications as published by ISO/IEC and by UPnP Implementers Corporation.
The following table indicates the original UPnP document titles and the corresponding part of ISO/IEC 29341:
UPnP Document Title ISO/IEC 29341 Part
UPnP Device Architecture 1.0 ISO/IEC 29341-1
UPnP Basic:1 Device ISO/IEC 29341-2
UPnP AV Architecture:1 ISO/IEC 29341-3-1
UPnP MediaRenderer:1 Device ISO/IEC 29341-3-2
UPnP MediaServer:1 Device ISO/IEC 29341-3-3
UPnP AVTransport:1 Service ISO/IEC 29341-3-10
UPnP ConnectionManager:1 Service ISO/IEC 29341-3-11
UPnP ContentDirectory:1 Service ISO/IEC 29341-3-12
UPnP RenderingControl:1 Service ISO/IEC 29341-3-13
UPnP MediaRenderer:2 Device ISO/IEC 29341-4-2
UPnP MediaServer:2 Device ISO/IEC 29341-4-3
UPnP AV Datastructure Template:1 ISO/IEC 29341-4-4
UPnP AVTransport:2 Service ISO/IEC 29341-4-10
UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11
UPnP ContentDirectory:2 Service ISO/IEC 29341-4-12
UPnP RenderingControl:2 Service ISO/IEC 29341-4-13
UPnP ScheduledRecording:1 ISO/IEC 29341-4-14
UPnP DigitalSecurityCamera:1 Device ISO/IEC 29341-5-1
UPnP DigitalSecurityCameraMotionImage:1 Service ISO/IEC 29341-5-10
UPnP DigitalSecurityCameraSettings:1 Service ISO/IEC 29341-5-11
UPnP DigitalSecurityCameraStillImage:1 Service ISO/IEC 29341-5-12
UPnP HVAC_System:1 Device ISO/IEC 29341-6-1
UPnP HVAC_ZoneThermostat:1 Device ISO/IEC 29341-6-2
UPnP ControlValve:1 Service ISO/IEC 29341-6-10
UPnP HVAC_FanOperatingMode:1 Service ISO/IEC 29341-6-11
UPnP FanSpeed:1 Service ISO/IEC 29341-6-12
UPnP HouseStatus:1 Service ISO/IEC 29341-6-13
UPnP HVAC_SetpointSchedule:1 Service ISO/IEC 29341-6-14
UPnP TemperatureSensor:1 Service ISO/IEC 29341-6-15
UPnP TemperatureSetpoint:1 Service ISO/IEC 29341-6-16
UPnP HVAC_UserOperatingMode:1 Service ISO/IEC 29341-6-17
UPnP BinaryLight:1 Device ISO/IEC 29341-7-1
UPnP DimmableLight:1 Device ISO/IEC 29341-7-2
UPnP Dimming:1 Service ISO/IEC 29341-7-10
UPnP SwitchPower:1 Service ISO/IEC 29341-7-11
UPnP InternetGatewayDevice:1 Device ISO/IEC 29341-8-1
UPnP LANDevice:1 Device ISO/IEC 29341-8-2
UPnP WANDevice:1 Device ISO/IEC 29341-8-3
UPnP WANConnectionDevice:1 Device ISO/IEC 29341-8-4
UPnP WLANAccessPointDevice:1 Device ISO/IEC 29341-8-5
UPnP LANHostConfigManagement:1 Service ISO/IEC 29341-8-10
UPnP Layer3Forwarding:1 Service ISO/IEC 29341-8-11
UPnP LinkAuthentication:1 Service ISO/IEC 29341-8-12
UPnP RadiusClient:1 Service ISO/IEC 29341-8-13
UPnP WANCableLinkConfig:1 Service ISO/IEC 29341-8-14
UPnP WANCommonInterfaceConfig:1 Service ISO/IEC 29341-8-15
UPnP WANDSLLinkConfig:1 Service ISO/IEC 29341-8-16
UPnP WANEthernetLinkConfig:1 Service ISO/IEC 29341-8-17
UPnP WANIPConnection:1 Service ISO/IEC 29341-8-18
UPnP WANPOTSLinkConfig:1 Service ISO/IEC 29341-8-19
UPnP WANPPPConnection:1 Service ISO/IEC 29341-8-20
UPnP WLANConfiguration:1 Service ISO/IEC 29341-8-21
UPnP Printer:1 Device ISO/IEC 29341-9-1
UPnP Scanner:1.0 Device ISO/IEC 29341-9-2
UPnP ExternalActivity:1 Service ISO/IEC 29341-9-10
UPnP Feeder:1.0 Service ISO/IEC 29341-9-11
UPnP PrintBasic:1 Service ISO/IEC 29341-9-12
UPnP Scan:1 Service ISO/IEC 29341-9-13
UPnP QoS Architecture:1.0 ISO/IEC 29341-10-1
UPnP QosDevice:1 Service ISO/IEC 29341-10-10
UPnP QosManager:1 Service ISO/IEC 29341-10-11
UPnP QosPolicyHolder:1 Service ISO/IEC 29341-10-12
UPnP QoS Architecture:2 ISO/IEC 29341-11-1
UPnP QOS v2 Schema Files ISO/IEC 29341-11-2

– 6 – 29341-12-11 © ISO/IEC:2008(E)
UPnP Document Title ISO/IEC 29341 Part
UPnP QosDevice:2 Service ISO/IEC 29341-11-10
UPnP QosManager:2 Service ISO/IEC 29341-11-11
UPnP QosPolicyHolder:2 Service ISO/IEC 29341-11-12
UPnP RemoteUIClientDevice:1 Device ISO/IEC 29341-12-1
UPnP RemoteUIServerDevice:1 Device ISO/IEC 29341-12-2
UPnP RemoteUIClient:1 Service ISO/IEC 29341-12-10
UPnP RemoteUIServer:1 Service ISO/IEC 29341-12-11
UPnP DeviceSecurity:1 Service ISO/IEC 29341-13-10
UPnP SecurityConsole:1 Service ISO/IEC 29341-13-11

29341-12-11 © ISO/IEC:2008(E) – 7 –
1. Overview and Scope
This service definition is compliant with the UPnP Device Architecture version 1.0.
This service is required for all Remote UI server devices.
It is specified in: urn:schemas-upnp-org:service:RemoteUIServerDevice

– 8 – 29341-12-11 © ISO/IEC:2008(E)
2. Service Modeling Definitions
2.1. ServiceType
The following service type identifies a service that is compliant with this template:
urn:schemas-upnp-org:service:RemoteUIServer:1.
2.2. State Variables
Table 1: Service State Variables
Variable Name Req. Data Allowed Default Eng.
or Type Value Value Units
Opt.
UIListingUpdate
O string Undefined Empty N/A
string
A_ARG_TYPE_DeviceProfile
R string Undefined Empty N/A
string
A_ARG_TYPE_CompatibleUIs
R string Undefined Empty N/A
string
A_ARG_TYPE_String
R string Undefined Empty N/A
string
A_ARG_TYPE_URI
O string Undefined Empty N/A
string
A_ARG_TYPE_Int
O int Undefined 0 N/A
Non-standard state variables implemented by a X TBD TBD TBD TBD
UPnP vendor go here.
R = Required, O = Optional, X = Non-standard.
Default values listed in this column are required. To specify standard optional values or to delegate assignment
of values to the vendor, you must reference a specific instance of an appropriate table below.
2.2.1. UIListingUpdate
The optional, evented UILisitingUpdate state variable informs control points of changes in the listing of user
interfaces exposed by the Remote UI server. UILisitingUpdate is composed of a list of unique identifiers
corresponding to user interfaces that have changed since the last event. Each line in the listing, including the last
line, must be terminated with a carriage-return character and a linefeed character. UILisitingUpdate values may
consist of an empty string when the event is issued by the Remote UI server for the first time. An example value
of UILisitingUpdate is shown in section 3.1.4.
2.2.2. A_ARG_TYPE_DeviceProfile
A_ARG_TYPE_DeviceProfile values are UTF-8 XML-formatted strings used by the UI client device to represent
the list of all supported remoting protocols.
2.2.3. A_ARG_TYPE_URI
An A_ARG_TYPE_URI value is a string formatted as a URI. UI server devices must be able to support values of
A_ARG_TYPE_URI that are 1024 bytes in length. UI server device support for longer values is optional. All
A_ARG_TYPE_URI values are never URI escaped and must be UTF-8 encoded.

29341-12-11 © ISO/IEC:2008(E) – 9 –
2.2.4. A_ARG_TYPE_CompatibleUIs
An A_ARG_TYPE_CompatibleUIs value is a string formatted as UTF-8 XML representing the list of all UIs that
are compatible with a designated Remote UI client device. Remote UI server devices must be able to support
values of A_ARG_TYPE_CompatibleUIs that are 10k bytes in length. UI server support for longer values is
optional.
2.2.5. A_ARG_TYPE_String
A simple string type.
2.2.6. A_ARG_TYPE_Int
A simple integer type.
2.3. Eventing and Moderation
Table 2: Event moderation
Variable Name Evented Moderated Max Logical Min
Event Event Relation Delta
Rate per
Event
UIListingUpdate
Yes Yes 0.5 N/A N/A
A_ARG_TYPE_DeviceProfile
No N/A N/A N/A N/A
A_ARG_TYPE_CompatibleUIs
No N/A N/A N/A N/A
A_ARG_TYPE_String
No N/A N/A N/A N/A
A_ARG_TYPE_URI
No N/A N/A N/A N/A
A_ARG_TYPE_Int
No N/A N/A N/A N/A
Determined by N, where Rate = (Event)/(N seconds).
(N) * (allowedValueRange Step).

– 10 – 29341-12-11 © ISO/IEC:2008(E)
2.4. Actions
Immediately following this table is detailed information about these actions, including short descriptions of the
actions, the effects of the actions on state variables, and error codes defined by the actions.
Table 3: Actions
Name Req. or Opt.
GetCompatibleUIs
R
SetUILifeTime
O
Non-standard actions implemented by an UPnP vendor go here. X
R = Required, O = Optional, X = Non-standard.
2.4.1. GetCompatibleUIs
This action retrieves a list of user interfaces that are compatible with a given client device as specified by the
client A_ARG_TYPE_DeviceProfile. It returns a (possibly empty) list of UIs compatible with the specified device
profile.
2.4.1.1. Arguments
Table 4: Arguments for GetCompatibleUIs()
Argument Direction relatedStateVariable
InputDeviceProfile A_ARG_TYPE_DeviceProfile
IN
UIFilter A_ARG_TYPE_String
IN
UIListing A_ARG_TYPE_CompatibleUIs
OUT
• UIFilter is a string employed to request additional filtering of the UIListing output. UIFilter is employed to
limit the UIListing result to UIs that possess specific values of A_ARG_TYPE_CompatibleUIs schema
elements and attributes. UIFilter is composed of a comma-separated list of A_ARG_TYPE_CompatibleUIs
schema elements, attributes and their values (see section 3.1.5 for UIFilter examples). The
InputDeviceProfile argument always takes precedence over the UIFilter argument in generating the
UIListing result.
• When the value of InputDeviceProfile is an empty string, all UI listings are returned in the UIListing output
argument.
• When no UIs matching the InputDeviceProfile are found, GetCompatibleUIs() is successful and returns an
empty string in the UIListing output argument.

29341-12-11 © ISO/IEC:2008(E) – 11 –
2.4.1.2. Dependency on State (if any)
2.4.1.3. Effect on State
2.4.1.4. Errors
errorCode errorDescription Description
400-499 TBD See UPnP Device Architecture section on Control.
500-599 TBD See UPnP Device Architecture section on Control.
600-699 TBD See UPnP Device Architecture section on Control.
701 Operation Rejected The Remote UI server has rejected the operation.
702 Invalid Filter GetCompatibleUIs() failed because the UIFilter argument
Argument
specifies an invalid filter.
2.4.2. SetUILifetime
Sets the lifetime of UIs for those UIs that permit the default lifetime setting to be modified. A control point may
alter the default lifetime setting to change the policy for setting the persistence of the UI after it has been
disconnected from a RUI client. After a UI has been disconnected (or was never connected) and the lifetime
expires, a UI server will presumably destroy that UI and the state (if any) of the associated application.
For UIs that permit the default lifetime setting
...