ISO/IEC 29341-27-1:2017 PDF

Information technology — UPnP Device Architecture — Part 27-1: Friendly device control protocol — Friendly information update service

First page of standard ISO/IEC 29341-27-1:2017

Open preview (PDF)

Title (English):

ISO/IEC 29341-27-1:2017

Information technology — UPnP Device Architecture — Part 27-1: Friendly device control protocol — Friendly information update service

Document status:: Active
Format:: Electronic (PDF)
Number of pages:: 27
Publication date:: September 13, 2017
Edition:: ISO/IEC IS 29341 edition 1 version 1
ICS:: 35.200

Delivery type:

Full version25 €Read online 24h10 €Read online 72h15 €

Document language:

enru

Delivery time:Immediate download

Price:25 €

Description (English):

ISO/IEC 29341-27-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as FriendlyInfoUpdate service . It is scoped to the Device Description Document (DDD) and is a service allowing control points to create orderly updates to the and elements. Once a change has taken place the status of the DDD might not reflect that of the advertised description because the device can not leave the network during ongoing activities. Therefore a state variable is provided to indicate if the DDD contains non-advertised (pending) values. If for any reason the device goes off line, power cycles, or reboots it will most likely advertise its new DDD. If DeviceProtection UPnP DP is implemented on the device then it will support restricting control point actions to control points with specific Roles.

Technical details

Technical committee: ISO/IEC JTC 1 - Information technology
SKU: ISO/IEC 29341-27-1:2017

Abstract

Overview

ISO/IEC 29341-27-1:2017 (part of the ISO/IEC 29341 UPnP Device Architecture series) defines the Friendly information update service of the Friendly Device Control Protocol. Aligned with UPnP Device Architecture 1.0, this standard specifies a service that lets UPnP control points perform orderly, moderated updates to a device’s Device Description Document (DDD) - specifically the device’s human-readable identity fields (for example, the device and ). It addresses the need to indicate pending versus advertised values while a device remains online and may be performing ongoing activities.

Key topics and technical requirements

Service model and XML description: normative service type and XML service description for the FriendlyInfoUpdate service consistent with UPnP DCP conventions.
State variables: definitions such as FriendlyNameStatus and FriendlyIconListStatus plus argument data types (e.g., A_ARG_TYPE_NewName, A_ARG_TYPE_IconURI, A_ARG_TYPE_Token).
Actions: standardized operations for control points, including GetFriendlyName(), GetFriendlyIconList(), SetFriendlyName(), SetFriendlyIconList(), and RestoreFriendlyInfo().
Eventing and moderation: event notifications and moderation rules to ensure consistent update sequencing and visibility of pending changes in the DDD.
Security/Access control: support for DeviceProtection (UPnP DP) semantics - the standard identifies restrictable vs non-restrictable actions and allows restricting updates to control points with specific Roles.
Error handling and state transitions: defined error codes and allowed icon/status transitions to ensure predictable device behavior during updates, reboots or network loss.
Patent disclosures: the document records patent declarations by multiple technology companies; implementers should review intellectual property statements.

Practical applications

Ensures consistent, race-free updates of device identity information in networked environments where devices cannot leave the network while changing attributes.
Useful for smart home hubs, media devices, IoT endpoints, printers, gateways and any UPnP-enabled consumer electronics that advertise human-readable names or icons.
Enables UX scenarios where remote management tools or provisioning systems update device names/icons while preserving advertised state consistency.

Who should use this standard

UPnP device manufacturers and firmware developers implementing device description management.
UPnP stack authors and middleware vendors adding FriendlyInfoUpdate support.
Systems integrators and OEMs building provisioning or device-management platforms.
Test labs and certification bodies validating UPnP DDD update behavior and DeviceProtection role-based restrictions.

Related standards

ISO/IEC 29341 series (UPnP Device Architecture) - base DCP and other device/service parts
UPnP Device Architecture 1.0 (original UPnP specifications)

Keywords: ISO/IEC 29341-27-1:2017, UPnP, FriendlyInfoUpdate, Device Description Document, DDD, FriendlyNameStatus, SetFriendlyName, SetFriendlyIconList, DeviceProtection, UPnP Device Architecture.

Related standards

Mentioned in the description and other ISO standards

Abstract

Overview

Key topics and technical requirements

Service model and XML description: normative service type and XML service description for the FriendlyInfoUpdate service consistent with UPnP DCP conventions.
State variables: definitions such as FriendlyNameStatus and FriendlyIconListStatus plus argument data types (e.g., A_ARG_TYPE_NewName, A_ARG_TYPE_IconURI, A_ARG_TYPE_Token).
Actions: standardized operations for control points, including GetFriendlyName(), GetFriendlyIconList(), SetFriendlyName(), SetFriendlyIconList(), and RestoreFriendlyInfo().
Eventing and moderation: event notifications and moderation rules to ensure consistent update sequencing and visibility of pending changes in the DDD.
Security/Access control: support for DeviceProtection (UPnP DP) semantics - the standard identifies restrictable vs non-restrictable actions and allows restricting updates to control points with specific Roles.
Error handling and state transitions: defined error codes and allowed icon/status transitions to ensure predictable device behavior during updates, reboots or network loss.
Patent disclosures: the document records patent declarations by multiple technology companies; implementers should review intellectual property statements.

Practical applications

Ensures consistent, race-free updates of device identity information in networked environments where devices cannot leave the network while changing attributes.
Useful for smart home hubs, media devices, IoT endpoints, printers, gateways and any UPnP-enabled consumer electronics that advertise human-readable names or icons.
Enables UX scenarios where remote management tools or provisioning systems update device names/icons while preserving advertised state consistency.

Who should use this standard

UPnP device manufacturers and firmware developers implementing device description management.
UPnP stack authors and middleware vendors adding FriendlyInfoUpdate support.
Systems integrators and OEMs building provisioning or device-management platforms.
Test labs and certification bodies validating UPnP DDD update behavior and DeviceProtection role-based restrictions.

Related standards

ISO/IEC 29341 series (UPnP Device Architecture) - base DCP and other device/service parts
UPnP Device Architecture 1.0 (original UPnP specifications)

Keywords: ISO/IEC 29341-27-1:2017, UPnP, FriendlyInfoUpdate, Device Description Document, DDD, FriendlyNameStatus, SetFriendlyName, SetFriendlyIconList, DeviceProtection, UPnP Device Architecture.

ISO/IEC 29341-27-1:2017 PDF

Technical details

Abstract

Overview

Key topics and technical requirements

Practical applications

Who should use this standard

Related standards

Related standards

Abstract

Overview

Key topics and technical requirements

Practical applications

Who should use this standard

Related standards

Related standards

Information technology — UPnP Device Architecture — Part 4-13: Audio Video Device Control Protocol - Level 2…

Systems and software engineering — Software life cycle processes

Asset management — Vocabulary, overview and principles

Asset management — Asset management system — Requirements

Information technology — Radio frequency identification device conformance test methods — Part 2: Test method…

Information technology — Multimedia framework (MPEG-21) — Part 22: User Description

Milk — Determination of the lactoperoxidase activity — Photometric method (Reference method)

Carbonaceous materials for the production of aluminium — Cold and tepid ramming pastes — Expansion/shrinkage…