| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/IEC 15404:2000 |
Information technology — Office machines — Minimum information to be included in specification sheets — Facsimile equipment |
|
Published |
2000-07 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
33.050.30
Equipment for telex, teletext, telefax
|
| ISO/IEC 29341-17-13:2011 |
Information technology — UPnP Device Architecture — Part 17-13: Quality of Service Device Control Protocol — Level 3 — Quality of Service Device Service — Underlying Technology Interfaces |
ISO/IEC 29341-17-13:2011(E) is a service definition addendum and contains recommendations for implementing interfaces between the UPnP QosDevice Service and various lower transport layers. Its purpose is to ensure that implementers of these interfaces use consistant mapping of methods and parameters from UPnP to the lower layers.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-17-1:2011 |
Information technology — UPnP Device Architecture — Part 17-1: Quality of Service Device Control Protocol — Level 3 — Quality of Service Architecture |
ISO/IEC 29341-17-1:2011(E) describes the motivation, use and interaction of the three services that comprise version 3 of the UPnP-QoS Framework:
- The QosDevice:3 Service [QD:3],
- The QosPolicyHolder:3 Service [QPH:3],
- and The QosManager:3 Service [QM:3]. It does not define a new device type. Since Quality of Service issues need to be solved for multiple usage scenarios, it is expected that vendors could use any UPnP device as a container for the services defined by UPnPQoS. The UPnP-QoS Framework is compliant with the UPnP Device Architecture version 1.0.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-10:2011 |
Information technology — UPnP Device Architecture — Part 18-10: Remote Access Device Control Protocol — Remote Access Inbound Connection Configuration Service |
ISO/IEC 29431-18-10:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as InboundConnectionConfig service. The InboundConnectionConfig service is a UPnP service that allows control points to configure the parameters that will enable the service to test if the host device is reachable from the internet. InboundConnectionConfig uses Dynamic DNS to manage at least one public address for home-network services; it uses STUN to ensure that any intermediate NAT device is navigatable, i.e. it is a
full-cone NAT. Thus, this service provides control points with the following functionality:
- Configure the dynamic DNS client co-located with the service,
- Configure the STUN client co-located with the service,
- Check if the device hosting the service is reachable from the internet.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-11:2011 |
Information technology — UPnP Device Architecture — Part 18-11: Remote Access Device Control Protocol — Remote Access Discovery Agent Service |
ISO/IEC 29341-18-11:2011(E) covers service definition and is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as RADAConfig service. This service type enables configuration of the in-band synchronization mechanism between Remote Access Clients and Remote Access Server.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-12:2011 |
Information technology — UPnP Device Architecture — Part 18-12: Remote Access Device Control Protocol — Remote Access Discovery Agent Synchronization Service |
ISO/IEC 29341-18-12:2011(E) describes the service definition which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as RADASync service. This service type enables an in-band synchronization mechanism between Remote Access Clients and Remote Access Server.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-13:2011 |
Information technology — UPnP Device Architecture — Part 18-13: Remote Access Device Control Protocol — Remote Access Transport Agent Configuration Service |
ISO/IEC 29341-18-13:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as RATAConfig service. The RATAConfig service is a UPnP service that allows control points to provision and configure the parameters that are required for enabling a Remote Access Server to accept and a Remote Access Client to initiate remote access connections. This service provides control points with the following functionality:
- Determine the Remote Access Transport Agents that can be configured by the service.
- Determine the delivery mechanisms for credentials supported by the service.
- Configure Remote Access Transport Agent profiles.
- Management of Remote Access Transport Agent profiles.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 44 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-1:2011 |
Information technology — UPnP Device Architecture — Part 18-1: Remote Access Device Control Protocol — Remote Access Architecture |
ISO/IEC 629431-18-1:2011(E) describes an architecture that provides the infrastructure that allows generic UPnP devices, services and control points deployed in remote physical devices to interact with the corresponding UPnP devices, services and control points physically attached to the home network. The mechanisms defined in this architecture will allow to extend the home network so that it will logically include the remote devices so that all devices will be able to communicate among themselves using the UPnP Forum defined mechanisms, e.g. UDA. The desired behaviour of the interactions between the remote device and home devices is envisioned to be similar with the one expected as if all devices are located in the
same local area network.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-2:2011 |
Information technology — UPnP Device Architecture — Part 18-2: Remote Access Device Control Protocol — Remote Access Client Device |
ISO/IEC 29431-18-2:2011(E) Contains device definition which is compliant with the UPnP Device Architecture version 1.0. It defines a device type referred to herein as RAClient device. The RAClient device is a UPnP device that allows control points to configure Remote Access Clients. This device provides control points with the following functionality: - Enumerate the Remote Access Transport mechanisms supported by the Remote Access Client (RAC). - Enumerate the Credentials Delivery mechanisms supported by the RAC. - Configure active Remote Access Transport profiles.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-3:2011 |
Information technology — UPnP Device Architecture — Part 18-3: Remote Access Device Control Protocol — Remote Access Server Device |
ISO/IEC 29341-18-3:2011(E) includes the device definition which is compliant with the UPnP Device Architecture version 1.0. It defines a device type referred to herein as RAServer Device. The RAServer Device is a UPnP Device UPnP device that allows control points to configure Remote Access Servers. This Device provides control points with the following functionality:
- Determine if the Remote Access Server is reachable from the public Internet;
- Enable a Remote Access Server to be reachable from the public Internet;
- Enumerate the Remote Access Transport mechanisms supported by the Remote Access Server;
- Enumerate the Credentials Delivery mechanisms supported by the Remote Access Server;
- Configure active Remote Access Transport profiles;
- Configure filters for allowing which local Devices are visible in remote networks;
- Configure filters for allowing which remote Devices are visible in the local network;
- Maintains list of registered remote users, and authenticates when they log in depending on their pre-configured info appropriately.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-18-4:2011 |
Information technology — UPnP Device Architecture — Part 18-4: Remote Access Device Control Protocol — Remote Access Discovery Agent Device |
ISO/IEC 29341-18-4:2011(E) describes the device definition which is compliant with the UPnP Device Architecture version 1.0. It defines a device type referred to herein as RADiscoveryAgent device. The RADiscoveryAgent device is a UPnP device that provides the functionality capability for synchronizing the UPnP discovery information between two remote networks. The Remote Access Discovery Agent functionality is a combination of a RADASync service and a control point functionality that interacts with a remote RADASync service running on the remote network. Each control point is pushing discovery information about devices available in its local area network to its corresponding RADASync peer. This device provides control points with the following functionality:
- Ability to push discovery information from a remote network that will be used to recreate and propagate the original information into the local network.
- Ability to propagate multicast events from a remote network into the local network.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-19-10:2011 |
Information technology — UPnP Device Architecture — Part 19-10: Solar Protection Blind Device Control Protocol — Two Way Motion Motor Service |
ISO/IEC 29341-19-10:2011(E) describes the service definition which is compliant with the UPnP Device Architecture version 1.0. This service-type enables the following functions:
- Driving a motor between two fixed end limits.
- Reaching any position written in percentage of the full run (optional).
- Returning the actual blind position written in percentage of the full run (optional).
|
Published |
2011-10 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-19-1:2011 |
Information technology — UPnP Device Architecture — Part 19-1: Solar Protection Blind Device Control Protocol — Solar Protection Blind Device |
ISO/IEC 29341-19-1:2011(E) is a device template which is compliant with the Universal Plug and Play Architecture, Version 1.0. SolarProtectionBlind:1 provides the following functionality: Provide shade with a blind. Any position can be reach between fully opened and fully closed. The control is manual, automatic or disable. A protected mode avoids the deterioration of the product.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-10:2017 |
Information technology — UPnP Device Architecture — Part 20-10: Audio video device control protocol — Level 4 — Audio video transport service |
ISO/IEC 29341-20-10:2017 is compliant with UPnP Device Architecture version 1.0 [14].
This service type enables control over the transport of audio and video streams. The service type defines a common model for A/V transport control suitable for a generic user interface. It can be used to control a wide variety of disc, tape and solid-state based media devices such as CD players, VCRs and MP3 players. A minimal implementation of this service can be used to control tuners.
The service type is related to the ConnectionManager service type, which describes A/V connection setup procedures, and the ContentDirectory service, which offers meta-information about the resource stored on the media. AVTransport also offers an action to retrieve any metadata embedded in the resource itself.
This service type does not offer scheduled recording.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 114 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-11:2017 |
Information technology — UPnP Device Architecture — Part 20-11: Audio video device control protocol — Level 4 — Connection manager service |
ISO/IEC 29341-20-11:2017 is compliant with the UPnP Device Architecture version 1.0 [14].
This service-type enables modeling of streaming capabilities of A/V devices, and binding of those capabilities between devices. Each device that is able to send or receive a stream according to the UPnP AV Architecture will have 1 instance of the ConnectionManager service. This service provides a mechanism for control points to:
a) Perform capability matching between source/server devices and sink/renderer devices,
b) Find information about currently ongoing transfers in the network,
c) Setup and teardown connections between devices (when required by the streaming protocol).
The ConnectionManager service is generic enough to properly abstract different kinds of streaming mechanisms, such as HTTP-based streaming, RTSP/RTP-based and 1394-based streaming.
The ConnectionManager enables control points to abstract from physical media interconnect technology when making connections. The term ?stream' used in this service template refers to both analog and digital data transfer.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 71 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-12:2017 |
Information technology — UPnP Device Architecture — Part 20-12: Audio video device control protocol — Level 4 — Content directory service |
ISO/IEC 29341-20-12:2017 specifies the characteristics of the UPnP networked service named ContentDirectory, version 4. This service definition is compliant with UPnP Device Architecture 1.0 [14].
Many devices within the home network contain various types of content that other devices would like to access (for example, music, videos, still images, etc). As an example, a MediaServer device might contain a significant portion of the homeowner's audio, video, and still-image library. In order for the homeowner to enjoy this content, the homeowner needs to be able to browse the objects stored on the MediaServer, select a specific one, and cause it to be played on an appropriate rendering device (for example, an audio player for music objects, a TV for video content, an Electronic Picture Frame for still-images, etc).
For maximum convenience, it is highly desirable to let the homeowner to initiate these operations from a variety of UI devices. In most cases, these UI devices will either be a UI built into the rendering device, or it will be a stand-alone UI device such as a wireless PDA or tablet. In any case, it is unlikely that the homeowner will interact directly with the device containing the content (that is: the homeowner won't have to walk over to the server device). In order to enable this capability, the server device needs to provide a uniform mechanism for UI devices to browse the content on the server and to obtain detailed information about individual content objects. This is the purpose of the ContentDirectory service.
The ContentDirectory service additionally provides a lookup/storage service that enables clients (for example, UI devices) to locate (and possibly store) individual objects (for example, songs, movies, pictures, etc) that the (server) device is capable of providing. For example, this service can be used to enumerate a list of songs stored on an MP3 player, a list of still-images comprising various slide-shows, a list of movies stored in a DVD-Jukebox, a list of TV shows currently being broadcast (a.k.a an EPG), a list of songs stored in a CD-Jukebox, a list of programs stored on a PVR (Personal Video Recorder) device, etc. Nearly any type of content can be enumerated via this ContentDirectory service. For devices that contain multiple types of content (for example, MP3, MPEG2, JPEG, etc.), a single instance of the ContentDirectory service can be used to enumerate all objects, regardless of their type.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 335 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-13:2017 |
Information technology — UPnP Device Architecture — Part 20-13: Audio video device control protocol — Level 4 — Rendering control service |
ISO/IEC 29341-20-13:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a service type referred to herein as RenderingControl.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 124 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-14:2017 |
Information technology — UPnP Device Architecture — Part 20-14: Audio video device control protocol — Level 4 — Scheduled recording service |
ISO/IEC 29341-20-14:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a service type referred to herein as ScheduledRecording service.
The ScheduledRecording service is a UPnP service that allows control points to schedule the recording of content. Generally, this content is broadcast content, but this specification does not limit itself to broadcast content. This service type enables the following functions:
- Create a recordSchedule so that it is added to the list of recordSchedule instances. Each recordSchedule describes user-level recording instructions for the ScheduledRecording service.
- Browse a list of recordSchedule instances stored by the ScheduledRecording service.
- Delete a recordSchedule so that it is removed from the list of recordSchedule instances.
- Browse a list of recordTask instances, stored by the ScheduledRecording service. The ScheduledRecording service may create zero or more recordTask instances for each recordSchedule. A recordTask represents a discrete recording operation of a recordSchedule.
- Enable or disable individual recordTask instances.
- Enable or disable a recordSchedule.
- Receive notifications i ndicating change of recordSchedule or recordTask list.
The ScheduledRecording service does not require a dependency on any UPnP services other than a co-located ContentDirectory service, which provides the following functions:
- A ContentDirectory service provides channel line-up to allow users to find recordable channels. A control point may use this metadata when creating a recordSchedule on a ScheduledRecording service.
- A ContentDirectory service may provide Electronic Program Guide (EPG) features to allow users to find recordable content. A control point may use this metadata when creating a recordSchedule on a ScheduledRecording service.
- Contents recorded by the ScheduledRecording service may be exposed by a ContentDirectory service.
The architectural relationship among the different concepts, defined by the ScheduledRecording service can be summarized as follows: A ScheduledRecording service owns a flat (that is: non-nested) list of recordSchedule instances, meaning that the ScheduledRecording service may create, destroy, or change recordSchedule instances. A recordSchedule represents user-level instructions to perform recording operations. Generally, a user constructs his instructions to a ScheduledRecording service via a control point that invokes UPnP actions that affect the list of recordSchedule instances. In all cases, the ScheduledRecording service shall be able to describe discrete recording operations for a recordSchedule through a list of associated recordTask instances. A recordTask can only exist with a recordSchedule (that is: never orphaned). Thus when a recordTask is created by the ScheduledRecording service, its lifetime depends on its parent recordSchedule. An individual recordTask can be selectively enabled or disabled.
This service template does not address:
Implementations where the ScheduledRecording service and its associated ContentDirectory service are not co-located in the same device.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 271 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-1:2017 |
Information technology — UPnP Device Architecture — Part 20-1: Audio video device control protocol — Level 4 — Audio video architecture |
ISO/IEC 29341-20-1:2017 describes the overall UPnP AV Architecture, which forms the foundation for the UPnP AV Device and Service templates. The AV Architecture defines the general interaction between UPnP control points and UPnP AV devices. It is independent of any particular device type, content format, and transfer protocol. It supports 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 the PC. The AV Architecture allows devices to support different types of formats for the entertainment content (such as MPEG2, MPEG4, JPEG, MP3, Windows Media Architecture (WMA), bitmaps (BMP), NTSC, PAL, ATSC, etc.) and multiple types of transfer protocols (such as IEC-61883/IEEE-1394, HTTP GET, RTP, HTTP PUT/POST, TCP/IP, etc.). The following clauses describe the AV Architecture and how the various UPnP AV devices and services work together to enable various end-user scenarios.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 3324-1:1993 |
Aircraft tyres and rims — Part 1: Specifications |
|
Withdrawn |
1993-11 |
Edition : 3 |
Number of pages : 23 |
Technical Committee |
83.160.20
Aircraft tyres
|
| ISO/IEC 29341-20-2:2017 |
Information technology — UPnP Device Architecture — Part 20-2: Audio video device control protocol — Level 4 — Media renderer device |
ISO/IEC 29341-20-2:2017 is compliant with the Universal Plug and Play Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaRenderer.
The MediaRenderer specification defines a general-purpose device template that can be used to instantiate any Consumer Electronics (CE) device that is capable of rendering AV content from the home network. It exposes a set of rendering controls in which a control point can control how the specified AV content is rendered. This includes controlling various rendering features such as brightness, contrast, volume, etc.
Example instances of a MediaRenderer include traditional devices such as TVs and stereo systems. Some more contemporary examples include digital devices such as MP3 players and Electronic Picture Frames (EPFs). Although most of these examples typically render one specific type of content (for example, a TV typically renders video content), a MediaRenderer is able to support a number of different data formats and transfer protocols. For example, a sophisticated implementation of a TV MediaRenderer could also support MP3 data so that its speakers could be used to play MP3 audio content.
The MediaRenderer device specification is very lightweight and is easy to implement on low-resource devices such as an MP3 player. However, it can also be used to expose the high-end capabilities of devices such as a PC.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-3:2017 |
Information technology — UPnP Device Architecture — Part 20-3: Audio video device control protocol — Level 4 — Media server device |
ISO/IEC 29341-20-3:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaServer.
The MediaServer specification defines a general-purpose device that can be used to instantiate any Consumer Electronics (CE) device that provides AV content (for example, media) to other UPnP devices on the home network. It is based on the UPnP AV Architecture Framework (described in another document). It exposes its content via the ContentDirectory service (refer to the ContentDirectory service specification for details). The MediaServer may also provide functionality to record content using the ScheduledRecording service (refer to the ScheduledRecording service specification). As such, the MediaServer can handle any specific type of media, any data format, and transfer protocol.
Example instances of a MediaServer include traditional devices such as VCRs, CD Players, DVD Players, audio-tape players, still-image cameras, camcorders, radios, TV Tuners, and set-top boxes. Additional examples of a MediaServer also include new digital devices such as MP3 servers, PVRs, smartphones and Home MediaServers such as the PC. Although these devices contain diverse (AV) content in one form or another, the MediaServer (via the ContentDirectory service) is able to expose this content to the home network in a uniform and consistent manner. This ability allows the MediaServer to instantiate traditional single-function devices as well as more recent multi-function devices such as VCR-DVD players and the general purpose Home MediaServer, which contains a wide variety of content such as MPEG2 video, CD audio, MP3 and/or WMA audio, JPEG images, etc.
The MediaServer specification is very lightweight and can easily be implemented on low-resource devices such as still-image cameras or MP3 players that want to expose their local content to the home network. The MediaServer can also be used for high-end Home MediaServers that contain dozens of Gigabytes of heterogeneous content. Refer to the Theory Of Operation subclause for some specific examples of the MediaServer.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-20-4:2017 |
Information technology — UPnP Device Architecture — Part 20-4: Audio video device control protocol — Level 4 — Datastructure template |
ISO/IEC 29341-20-4:2017 defines the layout of the AV Datastructure Template (AVDT) XML document. An AVDT document describes the format requirements and restrictions of various data structures used within the UPnP AV specifications. Although these data structures are defined very precisely in the appropriate service specification, in most cases, each data structure definition allows for a certain degree of variation in order to accommodate differences between individual devices.
The purpose of an AVDT document is to enable each device to describe (at run-time) its particular variation of these AV data structures. AVDT documents allow users of AV data structures (e.g. UPnP control points) to reduce the number of instances of those data structures that comply with the service specification but are not compatible with the device's particular capabilities. The ultimate goal of an AVDT document is to reduce those error conditions that are caused by control points creating instances of a data structure that exceed the static (known) capabilities of the device. Unfortunately, the AVDT mechanism will never eliminate all preventable error conditions, but it will help to reduce them by giving the client more information about the device's particular capabilities.
As described above, an AVDT document is a machine readable, implementation-specific variant of an AV data structure defined by one of the UPnP AV specifications. For a given device, each instance of that data structure shall conform to both the specification definition and the device's AVDT definition of that data structure.
Ironically, an AVDT document is both a more-restrictive and more-permissive variant of the specification definition. AVDT documents are more restrictive because they limit certain aspects of the data structure (e.g. such as the allowed values for each field) that are otherwise permitted by the specification definition. However, due to limitations of the AVDT constructs, it is simply not possible to express some of the more intricate requirements defined by the specification (e.g. subtle interdependencies between data structure fields). Consequently, instances of a data structure that comply with a given AVDT description may not fully comply with all of the requirements defined in the specification.
The types of data structures that can be described by an AVDT document represent a (non-hierarchitical) set of named property values. The set of allowed property names and their allowed values for a given data structure are defined by one of the UPnP AV specifications. Individual instances of these data structures are manifested via an XML document whose elements and attributes correspond to the set of named properties. In other words, within the XML document that corresponds to a given instance of a certain data structure, each XML element and attribute contains the value of a specific named property.
An AVDT document is conceptually similar to an XML schema in that both entities identify the XML elements and attributes that appear in any given document instance. Additionally, both AVDT documents and XML schemas identify the allowed values that are permitted for each element and/or attribute which corresponds to a specific property. However, unlike an XML schema, an AVDT document can also identify certain dependencies between two or more properties. For example, the set of allowed values of one property may depend on the actual value of another property. This type of interrelationship is difficult to represent using an XML schema. Hence, the AVDTdocument structure is needed.
In the various AV Architecture scenarios, sometimes there is a need to exchange device capabilities to ensure high level interoperability. In order to express the parameterized capability, an AV specification defines various templates for each purpose. A device uses the template and populates it with values to reflect its capabilities at run-time.
The AV Datastructure Template (AVDT) is a common structure to define various templates, which are called "Datastructure". This is written in XML and each data structure uses a subset of the AVDT to meet the necessary requirement.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-24-10:2017 |
Information technology — UPnP Device Architecture — Part 24-10: Internet gateway device control protocol — Level 2 — Wide area network internet protocol — Connection service |
ISO/IEC 29341-24-10:2017 specifies the characteristics of the UPnP networked service named WANIPConnection, version 2. This service definition is compliant with UPnP Device Architecture 1.0 [1] . It is one component of the Device Control Protocol for the UPnP Internet Gateway Device (see [3]).
This service enables a UPnP control point to:
- configure and control an IP connection between a LAN client on one side of an Internet gateway (see [3]) and a WAN host on the other side;
- manage any physical WAN interface?such as DSL or cable?that supports an IP connection.
This service is a required in a WANConnectionDevice (see [5]) when the device supports an IP connection.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 65 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-24-11:2017 |
Information technology — UPnP Device Architecture — Part 24-11: Internet gateway device control protocol — Level 2 — Wide area network internet protocol v6 — Firewall control service |
ISO/IEC 29341-24-11:2017 specifies the characteristics of the UPnP networked service named WANIPv6FirewallControl, version 1. This service definition is compliant with UPnP Service Architecture 1.0 [1].
This service supports the management IPv6 firewall pinholes in Internet gateway devices independent of the WAN access type (PPP, DHCP, ?). It also supports access control to restrict operations to authorized control points and users. It enables UPnP control points to:
- create and delete pinholes of limited duration that allow external communication from the WAN side of the gateway to reach devices on the LAN side
- determine operational status of a pinhole
This service does not support:
- retrieving detailed information about pinholes (such as associated external port or remaining lease duration)
- outbound packet filtering
- modification of security policies of a gateway device
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-29-10:2017 |
Information technology — UPnP Device Architecture — Part 29-10: Multiscreen device control protocol — Level 2 — Application management service |
ISO/IEC 29341-29-10:2017 specifies the characteristics of the UPnP networked service named ApplicationManagement, version 2. This service definition is compliant with UPnP Device Architecture 1.0 [1].
This service type enables to manage applications and the communications between applications providing various time-sensitive and interactive services including implementation-specific applications among various display devices, that is, Screen Devices [3] and Screen Control Points..
Screen Devices shall implement this service [3], but this service is allowed to be implemented for any UPnP devices as an add-on service.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-24-1:2017 |
Information technology — UPnP Device Architecture — Part 24-1: Internet gateway device control protocol — Level 2 — Internet gateway device |
ISO/IEC 29341-24-1:2017 specifies the characteristics of a device that manages connectivity to the Internet as an "edge" device between a residential Local Area Network and a Wide Area Network. The gateway can be physically implemented as a standalone device, or logically as a set of UPnP devices and services on a PC. This specified device is intended to be controlled from inside the home network. Control from outside the home network typically requires access control mechanisms that are outside the scope of this document. This specified device is also not intended for use with small business networks.
ISO/IEC 29341-24-1:2017 defines version 2 of the device named InternetGatewayDevice. It is a UPnP root device, and is identified by the UPnP device type InternetGatewayDevice:2. It is compliant with the UPnP Device Architecture, Versions 1.0 and 1.1 ([15] and [16], respectively). InternetGatewayDevice:2 encapsulates several sub-devices and services that collectively comprise the Internet Gateway Device Control Protocol (DCP).
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-24-2:2017 |
Information technology — UPnP Device Architecture — Part 24-2: Internet gateway device control protocol — Level 2 — Wide area network connection device |
ISO/IEC 29341-24-2:2017 specifies the characteristics of the UPnP networked device named WANConnectionDevice, version 2. This device definition is compliant with UPnP Device Architecture 1.0 [14] and UPnP Device Architecture 1.1 [15].
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-24-3:2017 |
Information technology — UPnP Device Architecture — Part 24-3: Internet gateway device control protocol — Level 2 — Wide area network device |
ISO/IEC 29341-24-3:2017 specifies the characteristics of a UPnP embedded virtual device that models a physical Wide Area Network interface on an Internet gateway. This specification describes version 2 of the device named WANDevice (WANDevice:2). WANDevice:2 also enables the control of the WAN interface, and is a required device in the UPnP Internet Gateway Device Control Protocol (as specified in [1]).
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-10:2017 |
Information technology — UPnP Device Architecture — Part 26-10: Telephony device control protocol — Level 2 — Call management service |
ISO/IEC 29341-26-10:2017 is compliant with [1]. It defines a service type referred to herein as the CallManagement service.
The CallManagement service is a UPnP service that allows control points to use the telephony features(e.g., voice call, video call, and data transfer etc.) provided by a Telephony Server (TS).
The CallManagement service enables the following features to a Telephony Control Point (TelCP):
- start an outgoing call
- accept an incoming call
- modify the capability of an existing call (e.g., changing from a voice call to a video call)
- terminate a call
- preview call logs
- register a call back and check the availability of the registered call back
To realize these features, the CallManagement service manages the connectivity of calls and media streams.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 296 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-11:2017 |
Information technology — UPnP Device Architecture — Part 26-11: Telephony device control protocol — Level 2 — Media management service |
ISO/IEC 29341-26-11:2017 is compliant with [1]. It defines a service type referred to herein as the MediaManagement service.
The MediaManagement service enables the feature to set-up a media session on a Telephony Client (TC), under the control of a Telephony Control Point (TelCP). This service provides the following functions:
- Set up a media session to send and/or receive media streams between a TC and a TS. To set up a media session, The MediaManagement service provides an interface for a TelCP to negotiate the media capabilities (e.g., codec types, IP address, port number etc.) between a TC and a TS. This ensures a TelCP to select a common set of the media capabilities to be used to send and/or receive media streams between a TS and a TC. After the media session is established, the TC starts sending and/or receiving media streams based on the media chapabilities negotiated between the TC and the TS.
- The mechanism to modify the media capabilities of an existing media session. For instance, if a media session is created for sending and receiving an audio media stream, it is possible to modify the media session for sending and receiving a video media stream.
- The mechanism to terminate a media session.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 185 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-1:2017 |
Information technology — UPnP Device Architecture — Part 26-1: Telephony device control protocol — Level 2 — Telephony architecture |
ISO/IEC 29341-26-1:2017 describes an architecture that allows UPnP Telephony devices, services and control points defined in the propoded DCP to be deployed in the home network environment and to enable management of incoming and outgoing telephony calls, messaging, presence information and phone features configuration through UPnP means from devices within the home.
In order to accommodate the above mentioned goals, the Telephony Architecture defines several UPnP devices and services that can be embedded to the devices defined for telephony. The architecture model describes interaction among the telephony devices, services and control points. The architecture also describes various deployment scenarios.
The architecture does not describe any interfaces to "service" gateways that will enable non-UPnP entities to interact with the UPnP devices, services and control points physically attached to the home network.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-12:2017 |
Information technology — UPnP Device Architecture — Part 26-12: Telephony device control protocol — Level 2 — Messaging service |
ISO/IEC 29341-26-12:2017 is compliant with [1]. It defines a service type referred to herein as Messaging service.
The Messaging service is a UPnP service that allows control points to use the messaging features provided by a Telephony Server (TS) or a Telephony Client (TC).
It provides in the UPnP network the overall set of messaging capabilities of a phone (e.g., smartphone, IP phone, VoIP gateway, etc.), as the role of a TS. Additionally, or as an alternative, a device with the role of a TC can provide the Messaging service via UPnP Telephony.
This service provides the control points with the following functionalities:
- Page Mode Messaging (e.g., e-Mail, SMS, MMS, etc.): notification of incoming messages, reading messages, sending a message, deleting a message.
- Session Mode Messaging (e.g., Instant Messaging, SMS, etc.): notification of incoming messages, retrieving and sending the messages within a session, creating, modifying or closing a messaging session.
- File transfer session, to transfer the files in near real time.
This service does not provide the following functionalities:
- Connection to a remote server for sending or receiving the messages (e.g., WAN side);
- Rendering of message notifications and messages to the end user;
- Configuring the Messaging service with account for connecting to remote servers;
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 69 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-13:2017 |
Information technology — UPnP Device Architecture — Part 26-13: Telephony device control protocol — Level 2 — Phone management service |
ISO/IEC 29341-26-13:2017 specifies the PhoneManagement profile of the ConfigurationManagement Service defined in [7].
The PhoneManagement profile can be used for managing the configuration of the UPnP TelephonyServer device (i.e. a telephone), with tasks such as managing an address book, configuring the settings of the phone, configuring the ringing modes, checking the battery level of the phone. This profile is compliant with the UPnP Telephony Architecture defined in [9].
PhoneManagement defines
- A profile of the CMS in order to satisfy the requirements for PhoneManagement (see clause 5).
- The Phone Data Model to perform configuration management of the specific features of a phone (see Annex A) by reusing the CMS data model (see [7], Annex B).
The ConfigurationManagement service offers a general purpose data model and a set of configuration management operations for retrieving and managing the actual configuration parameters of a device. These features are completely reused from CMS in the PhoneManagement.
The ConfigurationManagement service defines the functions for manipulating the configuration and status parameters that are exposed by the device hosting the ConfigurationManagement service. These actions and state variables defined in the ConfigurationManagement service are reused in order to manage the configuration parameters of a TelephonyServer device for e.g. phone, defined in the data model of the PhoneManagement.
The main goal of this specification is to define the data model (called herein as Phone Data Model) for the TelephonyServer device like Phone, according to the rules defined by the ConfigurationManagement service for defining a new data model.
The Phone Data Model is organized as a hierarchical tree of parameter sets, where each set represent a feature of a TelephonyServer (e.g. address book, ringing modes etc) that can be managed by a TelCP.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 71 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-14:2017 |
Information technology — UPnP Device Architecture — Part 26-14: Telephony device control protocol — Level 2 — Address book service |
ISO/IEC 29341-26-14:2017 is compliant [1]. It defines a service type referred to herein as AddressBook.
This service provides the following functionalities:
- Managing the network address book: accessing the network address book, adding new contact information in the network address book, synchronizing the local address book of Telephony Server with the network address book etc.
- Contact Share: sharing the local/network address book's contact information with other contacts of the user.
- Personal Contact Card: enabling mangement of his/her own contact information and sharing his own information with his/her contacts.
- Contact Invitation; allow handling of the Contact Invitation from the remote party.
This service does not provide the following functionalities:
Interaction between Telephony Server and the network address book.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-15:2017 |
Information technology — UPnP Device Architecture — Part 26-15: Telephony device control protocol — Level 2 — Calendar service |
ISO/IEC 29341-26-15:2017 is compliant with [1]. It defines a service type referred to herein as Calendar.
This service provides the following functionalities:
- Manage the family calendar events and share calendar events between the family members.
- Calendar events includes Reminders/Alarms/Free-BusyTime.
- Synchronizing the local calendar events with family calendar.
- Registrating for receiving the events notification on WAN side using any kinds of messaging service mechanism.
- Memo handling : Posting simple memos, retrieveing memos.
- Registrating for receiving the memo notifications on the WAN side using any kind of messaging service.
This service does not provide the following functionalities:
- Interaction between Telephony Server and network side calendar service
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 36 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-16:2017 |
Information technology — UPnP Device Architecture — Part 26-16: Telephony device control protocol — Level 2 — Presence service |
ISO/IEC 29341-26-16:2017 is compliant with the [1]. It defines a service type referred to herein as Presence service.
The Presence service is a UPnP service that allows control points, or better known as Telephony Control Points (TelCP), to manage presence information through a Telephony Server (TS) device or a Telephony Client (TC) device (in the role of UPnP server device for Presence service). This service provides control points with the following functionality:
- Presence of contacts, access the presence information of contacts, as provided by the UPnP Telephony Server device. Contacts referenced by the Presence service may be managed via PhoneManagement service and the Phone Data Model.
- Managing presence information, update the presence status stored in the TS;
This service does not provide the following functionality:
- To update the presence status of the local UPnP network, from the UPnP server device to remote presence servers (i.e. outside the local UPnP network).
- To retrieve the presence information of contacts from remote presence servers (i.e. outside the local UPnP network).
When the features provided by the Presence service are associated to the PhoneManagement features, then an integrated management of the address book and the presence of contacts in the address book can be delivered.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-2:2017 |
Information technology — UPnP Device Architecture — Part 26-2: Telephony device control protocol — Level 2 — Telephony client device |
ISO/IEC 29341-26-2:2017 defines a device type named TelephonyClient, that complies with [1].
The TelephonyClient device is a UPnP device that allows control points to exploit a set of telephony features such as management of media session with a telephony server, messaging, presence etc via UPnP though other UPnP enabled home network devices. This device provides control points with the following functionality:
- Managing media session with a telephony server including setting up and terminating of media session with a telephony server.
- Messaging features including sending and retrieving messages and notifications of incoming messages.
- Enabling user friendly input capability.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-26-3:2017 |
Information technology — UPnP Device Architecture — Part 26-3: Telephony device control protocol — Level 2 — Telephony server device |
ISO/IEC 29341-26-3:2017 defines a device type named TelephonyServer that complies with [1].
The TelephonyServer device is a UPnP device that allows control points to exploit a set of telephony features such as managing telephony calls, messaging, presence etc via UPnP though other UPnP enabled home network devices. This device provides control points with the following functionality:
- Managing telephony calls including initiation of a call, rejection of a call, acceptance and mofications of a call.
- Messaging features including sending and retrieving messages and notifications of incoming messages.
- Enabling user friendly input capability.
- Configuring of the Telephony Server via phone data model.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-27-1:2017 |
Information technology — UPnP Device Architecture — Part 27-1: Friendly device control protocol — Friendly information update service |
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 <friendlyName> and <iconList> 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.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-28-10:2017 |
Information technology — UPnP Device Architecture — Part 28-10: Multiscreen device control protocol — Application management service |
ISO/IEC 29341-28-10:2017 specifies the characteristics of the UPnP networked service named ApplicationManagement, version 1. This service definition is compliant with UPnP Device Architecture 1.0 [1].
This service type enables to manage applications and the communications between applications providing various time-sensitive and interactive services including implementation-specific applications among various display devices, that is, Screen Devices [3] and Screen Control Points.
Screen Devices shall implement this service [3], but this service is allowed to be implemented for any UPnP devices as an add-on service.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-28-1:2017 |
Information technology — UPnP Device Architecture — Part 28-1: Multiscreen device control protocol — Multiscreen architecture |
Today multi-screen/second-screen solutions are proliferating. However, each is a proprietary vertical for particular vendor(s). Therefore users expectations aren't being met:
- Seamless interoperability across vendors.
- Ability for second screen integrated usages rather than 100s of different apps.
The UPnP Multi-Screen Device Control Protocols (DCPs) provide an open interface to enable this interoperability between devices and applications, i.e. enable time-sensitive and interactive services, including implementation-specific applications, among various display devices.
ISO/IEC 29341-28-1:2017 describes the overall Multi-Screen Architecture, which forms the foundation for the UPnP Multi-Screen Device and Service templates. The Multi-Screen Architecture defines the general interaction between UPnP control points and UPnP devices defined by the UPnP Multi-Screen DCPs.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-28-2:2017 |
Information technology — UPnP Device Architecture — Part 28-2: Multiscreen device control protocol — Screen device |
ISO/IEC 29341-28-2:2017 defines a device type referred to as ScreenDevice version 1. This device specification is compliant with UPnP Device Architecture 1.0 [1].
The ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-Screen Architecture:1 [2] for details.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 5138-3:1981 |
Office machines — Vocabulary — Part 3: Addressing machines |
Presented bilingual vocabulary is intended to facilitate international communication in the field of office machines. Establishes reference between entries. Covers vocabulary of addressing machines.
|
Withdrawn |
1981-07 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.260
Office machines
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 29341-29-2:2017 |
Information technology — UPnP Device Architecture — Part 29-2: Multiscreen device control protocol — Level 2 — Screen device |
ISO/IEC 29341-29-2:2017 defines a device type referred to as ScreenDevice version 2. This device specification is compliant with UPnP Device Architecture 1.0 [1].
ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-Screen Architecture:1 [2] for details.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-10:2008 |
Information technology — UPnP Device Architecture — Part 3-10: Audio Video Device Control Protocol - Audio Video Transport Service |
ISO/IEC 29341-3-10:2008(E) defines a common model for AV transport control suitable for generic user interface. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-11:2008 |
Information technology — UPnP Device Architecture — Part 3-11: Audio Video Device Control Protocol - Connection Manager Service |
ISO/IEC 29341-3-11:2008(E) defines the service type modeling of streaming capabilities of AV devices and binding of those capabilities between devices. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-12:2008 |
Information technology — UPnP Device Architecture — Part 3-12: Audio Video Device Control Protocol - Content Directory Service |
ISO/IEC 29341-3-12:2008(E) defines the a content directory service which enables the user to acces various types of content that other devices would like to access, such as music, videos and still images. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 86 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-13:2008 |
Information technology — UPnP Device Architecture — Part 3-13: Audio Video Device Control Protocol - Rendering Control Service |
ISO/IEC 29341-3-13:2008(E) provides control points with the ability to query and/or adjust any rendering attribute that the device supports. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-1:2008 |
Information technology — UPnP Device Architecture — Part 3-1: Audio Video Device Control Protocol - Audio Video Architecture |
ISO/IEC 29341-3-1:2008(E) describes the overall UPnP AV architecture that forms the foundation for the UPnP AV device and service templates. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-2:2008 |
Information technology — UPnP Device Architecture — Part 3-2: Audio Video Device Control Protocol - Media Renderer Device |
ISO/IEC 29341-3-2:2008(E) defines a general-purpose device template that can be used to instantiate any Consumer Electronic (CE) device that is capable of rendering AV content from the home network. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-2:2008 |
Information technology — UPnP Device Architecture — Part 6-2: Heating, Ventilation, and Air Conditioning Device Control Protocol - Zone Thermostat Device |
ISO/IEC 29341-6-2:2008(E) describes a zone level controller (HVAC-Zone Thermostat) for heating and/or cooling. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-3-3:2008 |
Information technology — UPnP Device Architecture — Part 3-3: Audio Video Device Control Protocol - Media Server Device |
ISO/IEC 29341-3-3:2008(E) defines a general-purpose device that can be used to instantiate any Consumer Electronic (CE) device that provides AV content (e.g. media) to other UPnP devices on the home network. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-30-10:2017 |
Information technology — UPnP Device Architecture — Part 30-10: IoT management and control device control protocol — Data store service |
ISO/IEC 29341-30-10:2017 defines the service DataStore:1, which identifies Version 1 of the service named DataStore. This Publicly Available Specification is applicable to Standardized DCPs of the UPnP Forum which include this service.
This service definition is compliant with the UPnP Device Architecture, version 1.0.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 42 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-30-11:2017 |
Information technology — UPnP Device Architecture — Part 30-11: IoT management and control device control protocol — IoT management and control data model service |
This part of Publicly Available Specification ISO/IEC 29341-30-11:2017 specifies Sensor Data Models. It is intended to be an adjunct document to the IoT Management and Control Device [11] and DataStore Service [13] specifications.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 105 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-30-12:2017 |
Information technology — UPnP Device Architecture — Part 30-12: IoT management and control device control protocol — IoT management and control transport generic service |
This part of Publicly Available Specification ISO/IEC 29341 specifies the characteristics of a networked service that offers sensor and/or actuator data transport capabilities to an independent networked entity known as a control point.
ISO/IEC 29341-30-12:2017 defines the service SensorTransportGeneric:1 (in short TransportGeneric), which identifies Level 1 of the UPnP IoT Management and Control TransportGeneric:1 Service [10]. This Publicly Available Specification is applicable to Standardized DCPs of the UPnP Forum which include this service.
This service enables UPnP clients to access sensors and/or actuators without needing a detailed knowledge of the target sensor or actuator or its connectivity to the UPnP network. Sensors and Actuators are instead treated a generic data sources or sinks.
This service definition is compliant with the UPnP Device Architecture version 1.0 [1]. It defines a service type referred to herein as TransportGeneric service.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-30-1:2017 |
Information technology — UPnP Device Architecture — Part 30-1: IoT management and control device control protocol — IoT management and control architecture overview |
ISO/IEC 29341-30-1:2017 describes the overall UPnP IoTManagementAndControl Architecture, which forms the foundation for the UPnP IoTManagementAndControl device [11] and UPnP DataStore service [13] specifications. The IoTManagementAndControl device hosts services to bridge sensor devices connected to both UPnP networks as well as non-UPnP based networks. The DataStore service provides persistent retention and distribution of both sensor data as well as data from mobile devices which may leave the UPnP network at any time. This service can be hosted within the UPnP IoTManagementAndControl device as well as within other UPnP compliant devices.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-30-2:2017 |
Information technology — UPnP Device Architecture — Part 30-2: IoT management and control device control protocol — IoT management and control device |
ISO/IEC 29341-30-2:2017 defines the device for IOT Management and Control, which identifies Level 1 of the device named IOT Management and Control. This Publicly Available Specification is applicable to Standardized DCPs of the UPnP Forum which include this device.
This device definition is compliant with the UPnP Device Architecture version 1.0 [1]. It defines a device type referred to herein as IOT Management and Control device.
This specification defines a general-purpose device that can be used to instantiate a bridge or gateway device that is connected to Sensors and Actuators. This device implements a bridge between the UPnP network and Sensors/Actuators endpoints. It exposes services to check the status, and send and receive data from Sensors. Sensors/Actuators may be connected using a variety of transport protocols including Bluetooth, ZigBee and IEEE 11073.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-31-1:2017 |
Information technology — UPnP Device Architecture — Part 31-1: Energy management device control protocol — Energy management service |
ISO/IEC 29341-31-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type named EnergyManagement service. It is scoped to any UPnP Device that needs to convey energy management functionality available for the UPnP Device and its services.
|
Published |
2017-09 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 12857-2:1997 |
Optics and optical instruments — Geodetic instruments — Field procedures for determining accuracy — Part 2: Theodolites |
|
Withdrawn |
1997-08 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
17.180.30
Optical measuring instruments
|
| ISO/IEC 29341-4-10:2008 |
Information technology — UPnP Device Architecture — Part 4-10: Audio Video Device Control Protocol - Level 2 - Audio Video Transport Service |
ISO/IEC 29341-4-10:2008(E) enables control over the transport of audio and video streams. The service type defines a common model for AV transport control suitable for a generic user interface. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 83 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-4-11:2008 |
Information technology — UPnP Device Architecture — Part 4-11: Audio Video Device Control Protocol - Level 2 - Connection Manager Service |
ISO/IEC 29341-4-11:2008(E) enables modelling of streaming capabilities of AV devices and binding of those capabilities between devices. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-4-12:2008 |
Information technology — UPnP Device Architecture — Part 4-12: Audio Video Device Control Protocol - Level 2 - Content Directory Service |
ISO/IEC 29341-4-12:2008(E) enables the homeowner to browse the objects stored on the Media Server, select one and cause it to be played on a suitable rendering device. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 150 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-4-13:2008 |
Information technology — UPnP Device Architecture — Part 4-13: Audio Video Device Control Protocol - Level 2 - Rendering Control Service |
ISO/IEC 29341-4-13:2008(E) provides control points with the ability to query and/or adjust any rendering attribute that the device supports, such as control characteristics (e.g. brightness and contrast) and audio characteristics (e.g. volume, balance and equalizer settings). 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 71 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-4-14:2008 |
Information technology — UPnP Device Architecture — Part 4-14: Audio Video Device Control Protocol - Level 2 - Scheduled Recording Service |
ISO/IEC 29341-4-14:2008(E) allows control points to schedule the recording of content, such as bradcast content. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 237 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-4-2:2008 |
Information technology — UPnP Device Architecture — Part 4-2: Audio Video Device Control Protocol - Level 2 - Media Renderer Device |
ISO/IEC 29341-4-2:2008(E) defines a any Consumer Electronics (CE) device that is capable of rendering AV content from the home network. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-4-3:2008 |
Information technology — UPnP Device Architecture — Part 4-3: Audio Video Device Control Protocol - Level 2 - Media Server Device |
ISO/IEC 29341-4-3:2008(E) defines a general-purpose device that can be used ton istantiate any Consumer Electronics (CE) device that provides AV content to other UPnP devices on the home network. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 19944-2:2022 |
Cloud computing and distributed platforms — Data flow, data categories and data use — Part 2: Guidance on application and extensibility |
This document provides guidance on the application of the taxonomy and use statements from ISO/IEC 19944-1 in real world scenarios, and how to develop extensions to the data taxonomy, data processing and use categories and data use statements.
|
Published |
2022-04 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.210
Cloud computing
|
| ISO/IEC 29341-4-4:2008 |
Information technology — UPnP Device Architecture — Part 4-4: Audio Video Device Control Protocol - Level 2 - Audio Video Data Structures |
ISO/IEC 29341-4-4:2008(E) defines the layout of the AV Data structure template (AVDT) XML document. An AVDT document describes the format requirements and restrictions of various data structures used within the UPnP AV specifications. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-5-10:2008 |
Information technology — UPnP Device Architecture — Part 5-10: Digital Security Camera Device Control Protocol - Digital Security Camera Motion Image Service |
ISO/IEC 29341-5-10:2008(E) enables delivery and control of live snapshot images from a digital security camera. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-5-11:2008 |
Information technology — UPnP Device Architecture — Part 5-11: Digital Security Camera Device Control Protocol - Digital Security Camera Settings Service |
ISO/IEC 29341-5-11:2008(E) provides control of the basic setting of the actual image generating part of the security camera. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-5-12:2008 |
Information technology — UPnP Device Architecture — Part 5-12: Digital Security Camera Device Control Protocol - Digital Security Camera Still Image Service |
ISO/IEC 29341-5-12:2008(E) enables delivery and control of live snapshot images from a digital security camera. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-5-1:2008 |
Information technology — UPnP Device Architecture — Part 5-1: Digital Security Camera Device Control Protocol - Digital Security Camera Device |
ISO/IEC 29341-5-1:2008(E) provides control of basic settings of the actual image generating part, access to live snapshop still images and live motion images. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-10:2008 |
Information technology — UPnP Device Architecture — Part 6-10: Heating, Ventilation, and Air Conditioning Device Control Protocol - Control Valve Service |
ISO/IEC 29341-6-10:2008(E) provides programmatic control and status information for modulating water control valves or modulating air dampers used in Heating Ventilation and Air-Conditioning applications. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-11:2008 |
Information technology — UPnP Device Architecture — Part 6-11: Heating, Ventilation, and Air Conditioning Device Control Protocol - Fan Operating Mode Service |
ISO/IEC 29341-6-11:2008(E) describes the function of changing and reading of the user operating modes of a Forced air HVAC system. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 5138-4:1981 |
Office machines — Vocabulary — Part 4: Letter opening machines |
Included bilingual vocabulary serves for facilitating international communication in the field of office machines. Establishes references between entries. Covers vacabulary of letter opening machines.
|
Withdrawn |
1981-04 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.260
Office machines
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 29341-6-12:2008 |
Information technology — UPnP Device Architecture — Part 6-12: Heating, Ventilation, and Air Conditioning Device Control Protocol - Fan Speed Service |
ISO/IEC 29341-6-12:2008(E) defines a service type which provides programmatic control and status information for air fans used in Heating Ventilation and Air-Conditioning applications. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-13:2008 |
Information technology — UPnP Device Architecture — Part 6-13: Heating, Ventilation, and Air Conditioning Device Control Protocol - House Status Service |
ISO/IEC 29341-6-13:2008(E) provides an indication about house occupancy status and operational mode. It is commonly used as a mechanism for influencing the state of Devices and/or Control Points depending upon whether people are in the house. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-14:2008 |
Information technology — UPnP Device Architecture — Part 6-14: Heating, Ventilation, and Air Conditioning Device Control Protocol - Setpoint Schedule Service |
ISO/IEC 29341-6-14:2008(E) provides a description of variables for which timed setpoints are established, such as day of week, event name and heating or cooling setpoint. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-15:2008 |
Information technology — UPnP Device Architecture — Part 6-15: Heating, Ventilation, and Air Conditioning Device Control Protocol - Temperature Sensor Service |
ISO/IEC 29341-6-15:2008(E) describes a service type which enables the setting and reading of a temperature sensor. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-16:2008 |
Information technology — UPnP Device Architecture — Part 6-16: Heating, Ventilation, and Air Conditioning Device Control Protocol - Temperature Setpoint Service |
ISO/IEC 29341-6-16:2008(E) describes the service type which enables the means to set and get a temperature setpoint for use by a temperature controller. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-17:2008 |
Information technology — UPnP Device Architecture — Part 6-17: Heating, Ventilation, and Air Conditioning Device Control Protocol - User Operating Mode Service |
ISO/IEC 29341-6-17:2008(E) describes the service which enables the means to change and read the user operating modes of a HVAC system. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-6-1:2008 |
Information technology — UPnP Device Architecture — Part 6-1: Heating, Ventilation, and Air Conditioning Device Control Protocol - System Device |
ISO/IEC 29341-6-1:2008(E) describes a device template which provides functionalities such as 1 to n Zone Thermostats, set or get system level operating and fan modes and optionally an outdoor temperature sensor service. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 2132:1972 |
Offset duplicators — Attachment features of plates |
Lays down a method of attaching an offset plate to a duplicating machine. Specifies the diameter and the spacing of holes and their position tolerance. Cover single edge and double edge punched plates.
|
Withdrawn |
1972-02 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
37.100.10
Reproduction equipment
|
| ISO/IEC 29341-7-10:2008 |
Information technology — UPnP Device Architecture — Part 7-10: Lighting Device Control Protocol - Dimming Service |
ISO/IEC 29341-7-10:2008(E) describes a service type which enables funtions such as remote control of a dimmable lighting device. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-7-11:2008 |
Information technology — UPnP Device Architecture — Part 7-11: Lighting Device Control Protocol - Switch Power Service |
ISO/IEC 29341-7-11:2008(E) describes a service type which enables the basic power switching for emmbedding devices. 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.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-7-1:2008 |
Information technology — UPnP Device Architecture — Part 7-1: Lighting Device Control Protocol - Binary Light Device |
ISO/IEC 29341-7-1:2008(E) describes the functionality of switching the light source on or off. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-7-2:2008 |
Information technology — UPnP Device Architecture — Part 7-2: Lighting Device Control Protocol - Dimmable Light Device |
ISO/IEC 29341-7-2:2008(E) describes the functionalities of switching the light source on or off, changing the intensity of the light source and gives a definition of interaction between switch power and dimming service. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-10:2008 |
Information technology — UPnP Device Architecture — Part 8-10: Internet Gateway Device Control Protocol - Local Area Network Host Configuration Management Service |
ISO/IEC 29341-8-10:2008(E) enables the remote control, monitoring and configuration of a Dynamic Host Configuration Protocol (DHCP) and DNS server, serving a residential LAN. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-11:2008 |
Information technology — UPnP Device Architecture — Part 8-11: Internet Gateway Device Control Protocol — Layer 3 Forwarding Service |
ISO/IEC 29341-8-11:2008(E) is an optional service which includes all IP / layer-3 routing services. However, any such services that are configurable on a per connection instance basis, will be modeled in the context of the connection service itself. Network Address Translation (NAT) and Realm Specific (RSIP) are examples of such services. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-12:2008 |
Information technology — UPnP Device Architecture — Part 8-12: Internet Gateway Device Control Protocol - Link Authentication Service |
ISO/IEC 29341-8-12:2008(E) enables a UPnP control point to configure and control the parameters pertaining to authentication by an authentication server. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 5138-5:1981 |
Office machines — Vocabulary — Part 5: Letter folding machines |
Outlines terms used for letter folding machines, their main functions and types, in order to facilitate international exchange. Contains bilingual (English, French) collection of words and definitions and indicates references between them.
|
Withdrawn |
1981-04 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.260
Office machines
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 29341-8-13:2008 |
Information technology — UPnP Device Architecture — Part 8-13: Internet Gateway Device Control Protocol - Radius Client Service |
ISO/IEC 29341-8-13:2008(E) enables the control and configuration of radius component of IEEE 802.11 Wireless Access Points for the unmanaged network space, namely residential and small office LANs. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-14:2008 |
Information technology — UPnP Device Architecture — Part 8-14: Internet Gateway Device Control Protocol - Wide Area Network Cable Link Configuration Service |
ISO/IEC 29341-8-14:2008(E) encapsulates physical and link layer properties that are specific to a cable connection used for Internet access. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-15:2008 |
Information technology — UPnP Device Architecture — Part 8-15: Internet Gateway Device Control Protocol - Wide Area Network Common Interface Configuration Service |
ISO/IEC 29341-8-15:2008(E) models physical layer properties of a WAN interface on an Internet Gateway used for Internet access. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-16:2008 |
Information technology — UPnP Device Architecture — Part 8-16: Internet Gateway Device Control Protocol - Wide Area Network Digital Subscriber Line Configuration Service |
ISO/IEC 29341-8-16:2008(E) models physical and link layer properties specific to a single physical connection of a Digital Subscriber Line (DSL) modem used for Internet access on an Internet Gateway Device. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-17:2008 |
Information technology — UPnP Device Architecture — Part 8-17: Internet Gateway Device Control Protocol - Wide Area Network Ethernet Link Configuration Service |
ISO/IEC 29341-8-17:2008(E) models physical and link layer properties of a WAN Ethernet interface used for Internet Gateway Device. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-18:2008 |
Information technology — UPnP Device Architecture — Part 8-18: Internet Gateway Device Control Protocol - Wide Area Network Internet Protocol Connection Service |
ISO/IEC 29341-8-18:2008(E) enables a UPnP control point to configure and control Internet Protocol connections on the WAN interface of a UPnP compliant Internet Gateway Device. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 74 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-8-19:2008 |
Information technology — UPnP Device Architecture — Part 8-19: Internet Gateway Device Control Protocol - Wide Area Network Plain Old Telephone Service Link Configuration Service |
ISO/IEC 29341-8-19:2008(E) models physical and link layer properties specific to a Plain Old Telephone System (POTS) modem used for Internet access on an Internet Gateway Device. 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.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 2132:1972/Amd 1:1975 |
Offset duplicators — Attachment features of plates — Amendment 1 |
Page 1, clause 1: delete the final paragraph.
|
Withdrawn |
1975-04 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
37.100.10
Reproduction equipment
|