ISO/IEC 29341-29-10:2017

Overview

ISO/IEC 29341-29-10:2017 defines the ApplicationManagement (AMS) networked service, version 2, as part of the UPnP Device Architecture series. This Level‑2 multiscreen device control protocol specifies how UPnP-enabled devices manage applications and inter-application communications across multiple display devices (called Screen Devices) and Screen Control Points. The standard is compliant with UPnP Device Architecture 1.0 and may be implemented as a required service on Screen Devices or as an add‑on on other UPnP devices.

Key technical topics and requirements

• Service model and type: Formal service type definition for ApplicationManagement v2 consistent with UPnP conventions.
• State variables: Standard state variables used for discovery and control (examples in the standard include FeatureList, AppInfoList, RunningAppList, TransitioningApps).
• Actions / API: Defined control actions for application lifecycle and management, such as:
  • Discovery: GetFeatureList(), GetAppIDList(), GetAppInfoByIDs()
  • Lifecycle: StartAppByID(), StartAppByURI(), StopApp()
  • Installation: InstallAppByID(), InstallAppByURI(), UninstallApp(), GetInstallationStatus()
  • Connectivity: GetAppConnectionInfo(), ConnectApptoApp(), DisconnectApptoApp(), GetCurrentConnectionInfo()
• Eventing and moderation: Event notification model and moderation rules to control event frequency and payloads.
• Security and roles: Defined SECURITY feature, roles and permission mappings for actions, and common error codes for access control.
• XML service description & testing: Complete XML service description and test guidance to enable interoperability and conformance testing.
• Error handling: Tables of error codes and mapping for common and action-specific failures.

Practical applications and who uses this standard

• Application: Enables coordinated, time-sensitive and interactive applications across multiple screens - e.g., multiscreen streaming, second-screen interactivity, digital signage orchestration, conference room displays, and smart-home multi-display scenarios.
• Users:
  • Device manufacturers building UPnP Screen Devices or display products
  • Middleware and platform developers implementing multiscreen application management
  • Application developers integrating app lifecycle and inter-app communication across displays
  • Systems integrators and quality engineers using the XML service description and test cases for interoperability
• Benefits: Standardized control APIs, consistent eventing, and defined security roles improve interoperability and faster integration across vendors.

Related notes

• This part is one piece of the ISO/IEC 29341 UPnP Device Architecture family (Multiscreen device control protocol - Level 2). The standard includes patent declarations from multiple companies; implementers should review intellectual property statements when designing commercial solutions.

Keywords: UPnP, ApplicationManagement, multiscreen, device control protocol, Level 2, UPnP Device Architecture, Screen Devices, Screen Control Points, application management service.