Intelligent transport systems — Reference model architecture(s) for the ITS sector — Part 6: Use of ASN.1

Systèmes intelligents de transport (ITS) — Architecture(s) de modèle de référence pour le secteur ITS — Partie 6: Présentation de données dans ASN.1

ISO 14813-6:2017 provides a formal means to achieve consistency in the use of ASN.1 when specifying data types that are to be used in ITS International Standards. This is designed to ensure unambiguous and interoperable data exchange while providing consistent documentation of these exchanges. This document provides the necessary specifications to ensure consistent interpretation by providing formal references to several standards and in some cases specifying additional rules to promote greater consistency among standards.

ISO 14813-6:2017 does not require the use of ASN.1 for anything other than providing data type definitions in a common and flexible form. This document makes specific provision for the support of:

-      Embedding other extant standardised encoding formats, e.g. jpg, while maintaining interoperability and reuse within ITS;

-      Allowing alternative representations of data type definitions, e.g. XML schema;

-      Allowing alternative encoding of defined data.

The rules presented in this document enable data types to be recorded in a common ITS data registry, and in ITS International Standards, in a common and consistent form.


Road vehicles — Compressed natural gas (CNG) fuel system components — Part 2: Performance and general test methods

Véhicules routiers — Composants des systèmes de combustible gaz naturel comprimé (GNC) — Partie 2: Performances et méthodes d'essai générales

ISO 15500-2:2016 specifies performance and general test methods for compressed natural gas (CNG) fuel system components intended for use on the types of motor vehicles defined in ISO 3833.

ISO 15500-2:2016 is applicable to vehicles (mono-fuel, bi-fuel or dual-fuel applications) using compressed natural gas in accordance with ISO 15403 (all parts). It is not applicable to the following:

a)    liquefied natural gas (LNG) fuel system components located upstream of, and including, the vaporizer;

b)    fuel containers;

c)    stationary gas engines;

d)    container-mounting hardware;

e)    electronic fuel management;

f)     refuelling receptacles.


Particle size analysis — Laser diffraction methods

Analyse granulométrique — Méthodes par diffraction laser

This document provides guidance on instrument qualification and size distribution measurement of particles in many two-phase systems (e.g. powders, sprays, aerosols, suspensions, emulsions and gas bubbles in liquids) through the analysis of their light-scattering properties. It does not address the specific requirements of particle size measurement of specific materials.

This document is applicable to particle sizes ranging from approximately 0,1 µm to 3 mm. With special instrumentation and conditions, the applicable size range can be extended above 3 mm and below 0,1 µm.

For spherical and non-spherical particles, a size distribution is reported, where the predicted scattering pattern for the volumetric sum of spherical particles matches the measured scattering pattern. This is because the technique assumes a spherical particle shape in its optical model. For non-spherical particles the resulting particle size distribution is different from that obtained by methods based on other physical principles (e.g. sedimentation, sieving).


Rolling bearings — Thermal speed rating — Calculation

Roulements — Vitesse de référence thermique — Calculs

ISO 15312:2018 defines the thermal speed rating for oil bath lubricated rolling bearings and defines calculation principles for the determination of this parameter. The parameter determined in accordance with this document applies to rolling bearings of the given series and sizes of standard design or of a design that, from a frictional point of view, can be related to a standard design bearing.

In most cases of standard assembly, the permissible temperature determines the maximum operating speed. Heating of the assembly is then generated by the bearing.

Thrust ball bearings are excluded from this document as kinematic effects do not allow the thermal speed rating defined in this document to be applied.

NOTE 1    In Annex A mean values for the coefficients f0r and f1r are given ? f0r for calculating viscous losses of oil bath lubricated bearings and f1r for calculating frictional losses of bearings.

NOTE 2    Explanatory notes on the limiting criterion are given in Annex B.

NOTE 3    In Annex C the reference conditions for grease lubrication are defined. The reference conditions are chosen such that the thermal speed rating for grease lubrication is identical to that for oil bath lubrication.


Road vehicles — Vehicle to grid communication interface — Part 1: General information and use-case definition

Véhicules routiers — Interface de communication entre véhicule et réseau électrique — Partie 1: Informations générales et définition de cas d'utilisation

This document, as a basis for the other parts of the ISO 15118 series, specifies terms and definitions, general requirements and use cases for conductive and wireless HLC between the EVCC and the SECC.

This document is applicable to HLC involved in conductive and wireless power transfer technologies in the context of manual or automatic connection devices.

This document is also applicable to energy transfer either from EV supply equipment to charge the EV battery or from EV battery to EV supply equipment in order to supply energy to home, to loads or to the grid.

This document provides a general overview and a common understanding of aspects influencing identification, association, charge or discharge control and optimisation, payment, load levelling, cybersecurity and privacy. It offers an interoperable EV-EV supply equipment interface to all e-mobility actors beyond SECC.

The ISO 15118 series does not specify the vehicle internal communication between battery and other internal equipment (beside some dedicated message elements related to the energy transfer).

NOTE 1    Electric road vehicles specifically are vehicles in categories M (used for carriage of passengers) and N (used for carriage of goods) (compare ECE/TR ANS/WP.29/78 ev.2). This does not prevent vehicles in other categories from adopting the ISO 15118 series as well.

NOTE 2    This document is destined to orientate the message set of ISO 15118‑2 and ISO 15118‑20[1]. The absence of any particular use case in this document does not imply that it will not be put into practice, with the required messages.

NOTE 3    This document, ISO 15118‑2 and ISO 15118‑20 are designed to work independent of data transfer medium used. However, the ISO 15118 series is made for fitting the specified data link layers in the corresponding documents in this series.

[1] Under preparation. Stage at the time on publication: ISO/DIS 15118-20:2019.


Road vehicles — Vehicle to grid communication interface — Part 2: Network and application protocol requirements

Véhicules routiers — Interface de communication entre véhicule et réseau électrique — Partie 2: Exigences du protocole d'application et du réseau


Road vehicles — Diagnostic communication over K-Line (DoK-Line) — Part 2: Data link layer

Véhicules routiers —  Communication de diagnostic sur la ligne K (DoK-Line) — Partie 2: Couche de liaison de données

ISO 14230-2:2016 specifies data link layer services tailored to meet the requirements of UART-based vehicle communication systems on K-Line as specified in ISO 14230‑1. It has been defined in accordance with the diagnostic services established in ISO 14229‑1 and ISO 15031‑5, but is not limited to use with them and is also compatible with most other communication needs for in-vehicle networks. The protocol specifies an unconfirmed communication.

The diagnostic communication over K-Line (DoK-Line) protocol supports the standardized service primitive interface as specified in ISO 14229‑2.

ISO 14230-2:2016 provides the data link layer services to support different application layer implementations like the following:

-      enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics);

-      emissions-related OBD as specified in ISO 15031, SAE J1979-DA and SAE J2012-DA;

-      in addition, ISO 14230-2:2016 clarifies the differences in initialization for K-line protocols defined in ISO 9141 and ISO 14230. This is important since a server supports only one of the protocols mentioned above and the client has to handle the coexistence of all protocols during the protocol determination procedure.


Road vehicles — Local Interconnect Network (LIN) — Part 5: Application programmers interface (API)

Véhicules routiers — Réseau Internet local (LIN) — Partie 5: Interface du programmeur d'application (API)

ISO/TR 17987-5:2016 has been established in order to define the LIN application programmers interface (API).


Intelligent transport systems — Using web services (machine-machine delivery) for ITS service delivery — Part 1: Realization of interoperable web services

Utilisation des services du Web (livraison de machine à machine) pour la livraison de services ITS — Partie 1: Réalisation des services du Web interopérables

ISO 24097-1:2017 establishes a Service Oriented Architecture (SOA) for the realization of interoperable web services for Intelligent Transport Systems (ITS).

Web service behaviour is described at the metadata level, i.e. a higher level of abstraction, to enable auto-generation of both a ?service requester' program as well as a ?service provider' program. Figure 1 presents the principal entities involved in a web service scenario. They are service provider, service requester, and 'registry'. The registry includes business information and technical information such as interface and policy. Figure 1 also depicts the actions of the service provider and the service requester. A service provider interacts with the registry to enable it to "publish" the provided service. The service is characterized in the form of a web service interface describer in the form of a standardized web service description language (WSDL) and policy (WS-Policy). A service requester interacts with the registry to "discover" a provider for the service he is seeking. That interaction takes place through "Universal Description Discovery, and Integration" (UDDI) dialogue and endpoint reference (EPR). Once the service requester identifies a service provider, he "binds" to the service provider via an SOA protocol.

ISO 24097-1:2017 is applicable to inter-ITS sector web services as well as ITS web services for non-ITS users.


Intelligent transport systems — Roadside modules SNMP data interface — Part 1: Overview

Systèmes de transport intelligents — Interface de données SNMP pour les modules en bord de route — Partie 1: Vue d'ensemble

Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.

The ISO 20684 series defines data that can be used when field devices need to exchange information with other external entities (called “managers” in this document, even if they are other field devices). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided into several individual parts. This document (Part 1) introduces the ISO 20684 series and provides normative content that applies to all subsequent parts.


Information technology — Universal Coded Character Set (UCS)

Technologies de l'information — Jeu universel de caractères codés (JUC)

ISO/IEC 10646:2017 specifies the Universal Coded Character Set (UCS). It is applicable to the represen-tation, transmission, interchange, processing, storage, input, and presentation of the written form of the lan-guages of the world as well as of additional symbols.

-           specifies the architecture of this International Standard,

-           defines terms used in this International Standard,

-           describes the general structure of the UCS codespace,

-           specifies the Basic Multilingual Plane (BMP) of the UCS,

-           specifies supplementary planes of the UCS: the Supplementary Multilingual Plane (SMP), the Supplemen-tary Ideographic Plane (SIP), the Tertiary Ideographic Plane (TIP), and the Supplementary Special-purpose Plane (SSP),

-           defines a set of graphic characters used in scripts and the written form of languages on a world-wide scale,

-           specifies the names for the graphic characters and format characters of the BMP, SMP, SIP, TIP, SSP and their coded representations within the UCS codespace,

-           specifies the coded representations for control characters and private use characters,

-           specifies three encoding forms of the UCS: UTF-8, UTF-16, and UTF-32,

-           specifies seven encoding schemes of the UCS: UTF-8, UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE, and UTF-32LE,

-           specifies the management of future additions to this coded character set.

The UCS is an encoding system different from that specified in ISO/IEC 2022. The method to designate UCS from ISO/IEC 2022 is specified in 12.2.

A graphic character will be assigned only one code point in the standard, located either in the BMP or in one of the supplementary planes.


Horology — Procedure for evaluating the accuracy of quartz watches

Horlogerie — Procédure d'évaluation de la précision des montres à quartz

This document specifies the procedure for evaluating the accuracy of quartz watches, individually and by lots (see Annex A which presents the methods for statistical evaluation of accuracy by lot), and the relationship between the accuracy tested and the accuracy classification given by the manufacturer.

It applies to quartz watches having accompanying documents on which the accuracy classification is indicated.


Drawing and writing instruments — Ball point pens and roller ball pens — Vocabulary

Instruments de dessin et d'écriture — Stylos à pointe bille et stylos rollers — Vocabulaire

ISO 12756:2016 defines terms related to ball point pens and roller ball pens.


Gel ink ball pens and refills — Part 1: General use

Stylos à bille à encre gel et recharges — Partie 1: Utilisation générale

ISO 27668-1:2016 establishes minimum quality requirements for gel ink ball pens (refillable and non-refillable) and refills for general use.

Additional requirements for gel ink ball pens for documentary use are given in ISO 27668‑2.


Roller ball pens and refills — Part 1: General use

Stylos rollers et recharges — Partie 1: Utilisation générale

ISO 14145-1:2016 establishes minimum quality requirements for roller ball pens (refillable and non-refillable) and refills for general use.

Additional requirements for roller ball pens for documentary use are given in ISO 14145‑2.


Ball point pens and refills — Part 1: General use

Stylos à pointe bille et recharges — Partie 1: Utilisation générale

ISO 12757-1:2016 establishes minimum quality requirements for ball point pens (refillable or non-refillable) and refills for general use.

Additional requirements for ball point pens for documentary use are given in ISO 12757‑2.


Implants for surgery — Partial and total hip joint prostheses — Part 4: Determination of endurance properties and performance of stemmed femoral components — Amendment 1

Implants chirurgicaux — Prothèses partielles et totales de l'articulation de la hanche — Partie 4: Détermination des propriétés d'endurance et des performances des tiges fémorales — Amendement 1


Medical devices — Part 2: Guidance on the application of usability engineering to medical devices

Dispositifs médicaux — Partie 2: Titre manque

IEC TR 62366-2:2016(E), which is a Technical Report, contains background information and provides guidance that addresses specific areas that experience suggests can be helpful for those implementing a USABILITY ENGINEERING (HUMAN FACTORS ENGINEERING) PROCESS both as defined in IEC 62366-1:2015 and as supporting goals other than SAFETY. This technical report is not intended to be used for regulatory purposes. It contains no requirements and only provides guidance and tutorial information.


High yield strength steel plates and wide flats for cold forming — Delivery conditions

Produits plats en acier à haute limite d'élasticité pour formage à froid — Conditions de livraison

This document specifies the requirements for weldable high yield strength plates and wide flats for cold forming.

It does not apply to weldable structural steels, whether or not of special quality, which are covered by other International Standards, namely:

—          structural steels: ISO 630 (all parts);

—          high yield strength flat steel products: ISO 4950-1, ISO 4950-2 and ISO 4950-3;

—          hot-rolled steel sheet of higher yield strength with improved formability: ISO 5951;

—          sheet and strip: refer to ISO/TC 17, Steel, SC 12, Continuous mill flat rolled products;

—          tubular products; refer to ISO/TC 5, Ferrous metal pipes and metallic fittings, SC 1, Steel tubes.


Mechanical pencils for technical drawings — Part 1: Classification, dimensions, performance requirements and testing

Porte-mines pour le dessin technique — Partie 1: Classification, dimensions, exigences de performance et essais

ISO 9177-1:2016 specifies classification, dimensions, performance requirements and testing for hand-held mechanical pencils used for technical drawings.


Technical product documentation (TPD) — General principles of representation — Part 2: Basic conventions for lines

Documentation technique de produits (TPD) — Principes généraux de représentation — Partie 2: Conventions de base pour les traits

This document establishes the types of lines used in technical drawings (e.g. diagrams, plans or maps), their designations and their configurations, as well as general rules for the draughting of lines. In addition, this document specifies general rules for the representation of leader and reference lines and their components as well as for the arrangement of instructions on or at leader lines in technical documents. Annexes have been provided for specific information on mechanical, construction and shipbuilding technical drawings.

For the purposes of this document the term "technical drawing" is interpreted in the broadest possible sense encompassing the total package of documentation specifying the product (workpiece, subassembly, assembly).


Technical product documentation (TPD) — General principles of representation — Part 3: Views, sections and cuts

Documentation technique de produits (TPD) — Principes généraux de représentation — Partie 3: Vues, sections et coupes

This document specifies the general principles for presenting views, sections and cuts applicable to various kinds of technical drawings (e.g. mechanical, electrical, architectural, civil engineering), following the orthographic projection methods specified in ISO 5456-2. Views and sections for shipbuilding technical drawings are discussed in ISO 128-15. Views and sections for 3D models are discussed in ISO 16792.

Attention has also been given in this document to the requirements of reproduction, including microcopying in accordance with ISO 6428.


Implants for surgery — Metallic materials — Part 7: Forgeable and cold-formed cobalt-chromium-nickel-molybdenum-iron alloy

Implants chirurgicaux — Produits à base de métaux — Partie 7: Alliage à forger mis en forme à froid à base de cobalt, de chrome, de nickel, de molybdène et de fer

ISO 5832-7:2016 specifies the characteristics of, and corresponding test methods for, forgeable and cold-formed cobalt-chromium-nickel-molybdenum-iron alloy for use in the manufacture of surgical implants.


Test targets for image quality measurements on small size photographic prints


Characterization of physical aspects and print quality of photo books


Photography — Lenticular print for changing images — Measurements of image quality

Photographie — Impression lenticulaire pour images changeantes — Mesurages de la qualité des images

This document specifies the measurement methods and specification of image quality of lenticular prints that are used for changing images. This document does not cover lenticular prints that are used for 3D images.

NOTE       Lenticular prints for 3D images can be measured with the same types of procedures. However, it needs more information, such as the dependence of the measurement distance, to evaluate the 3D performance.

This document specifically describes measurement methods for cross-talk, viewing angle range, angular misalignment from the designed viewing angle and the uniformity of the image within the printing area of the lenticular print images. These are critical for the image quality of lenticular prints for changing images.

This document is applicable to lenticular prints produced by printing technologies that include impact and non-impact printing. Examples of the former are off-set, gravure and flexography, while the examples of the latter are silver halide, inkjet, dye diffusion thermal transfer and electrophotography. The multiple laser images (MLI) and changeable laser images (CLI) process of using a laser to write through a lenticular screen at different angles to create multiple images is also used.


Accelerated life test method of mixed metal oxide anodes for cathodic protection — Part 1: Application in concrete

Méthode d'essai accéléré de durabilité des anodes à oxydes métalliques mixtes pour la protection cathodique — Partie 1: Application dans le béton

ISO 19097-1:2018 specifies accelerated life test method of mixed metal oxide anodes for impressed current cathodic protection used in concrete. The accelerated life test results can be used to compare the durability of the anodes and to evaluate whether the anodes can comply with required specifications of design life expectancy at rated current output.

ISO 19097-1:2018 is also applicable to other anode systems that are used as impressed current anodes embedded in concrete with suitably modified apparatus to hold anodes of different geometry.


Accelerated life test method of mixed metal oxide anodes for cathodic protection — Part 2: Application in soils and natural waters

Méthode d'essai accéléré de durabilité des anodes à oxydes métalliques mixtes pour la protection cathodique — Partie 2: Application dans les sols et aux naturelles

ISO 19097-2:2018 specifies accelerated life test method of mixed metal oxide anodes for impressed current cathodic protection used in soil or natural waters. The accelerated life test results can be used to compare the durability of the anodes and to evaluate whether the anodes can comply with required specifications of design life expectancy at rated current output.


Road vehicles — Clock extension peripheral interface (CXPI)Part 1: General information and use case definition Part 2: Transport protocol and network layer services Part 3: Protocol specificationPart 4: Protocol conformance test specification

Véhicules routiers — Interface du périphérique d'extension d'horloge (CXPI)- Partie 1 : Informations générales et définition de cas d'usage- Partie 2 : Protocole de transport et services de couche de réseau- Partie 3 : Spécification du protocole- Partie 4 : Spécification du test de conformité du protocole


Road vehicles — Vehicle on-board diagnostics (OBD) — Part 1: Emission system communication requiements

Véhicules routiers — Titre manque — Partie 1: Titre manque


Road vehicles — Vehicle on-board diagnostics (OBD) — Part 2: Emission system communication requirements conformance test plan

Véhicules routiers — Titre manque — Partie 2: Titre manque


Road vehicles — Implementation of world-wide harmonized on-board diagnostics (WWH-OBD) communication requirements — Part 3: Common message dictionary

Véhicules routiers — Mise en application des exigences de communication pour le diagnostic embarqué harmonisé à l'échelle mondiale (WWH-OBD) — Partie 3: Dictionnaire de messages communs


Road vehicles — Implementation of world-wide harmonized on-board diagnostics (WWH-OBD) communication requirements — Part 6: External test equipment

Véhicules routiers — Mise en application des exigences de communication pour le diagnostic embarqué harmonisé à l'échelle mondiale (WWH-OBD) — Partie 6: Équipement d'essai externe


Information technology — UPnP Device Architecture — Part 20-1: Audio video device control protocol — Level 4 — Audio video architecture

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-1: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Architecture audio-vidéo

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.


Nuclear energy — Nuclear fuel technology — Determination of plutonium in nitric acid solutions by spectrophotometry

Énergie nucléaire — Technologie du combustible nucléaire — Détermination du plutonium dans les solutions d'acide nitrique par spectrophotométrie

This document specifies an analytical method by spectrophotometry, for determining the plutonium concentration in nitric acid solutions, with spectrophotometer implemented in hot cell and glove box allowing the analysis of high activity solutions. Commonly, the method is applicable, without interference, even in the presence of numerous cations, for a plutonium concentration higher than 0,5 mg·l−1 in the original sample with a standard uncertainty, with coverage factor k = 1, less than 5 %.

The method is intended for process controls at the different steps of the process in a nuclear fuel reprocessing plant or in other nuclear facilities.


Information technology — UPnP Device Architecture — Part 20-4: Audio video device control protocol — Level 4 — Datastructure template

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-4: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Modèle de structure de données

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.


Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 1AX: Link aggregation

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 1AX: Agrégation de lien

Link Aggregation provides protocols, procedures, and managed objects that allow the following:

- One or more parallel instances of full-duplex point-to-point links to be aggregated together to form a Link Aggregation Group (LAG), such that a MAC Client can treat the LAG as if it were a single link.

- A resilient interconnect using multiple full-duplex point-to-point links among one to three nodes in a network and one to three nodes in another, separately administered, network, along with a means to ensure that frames belonging to any given service will use the same physical path in both directions between the two networks.

ISO/IEC/IEEE 8802-1AX:2015 defines the MAC-independent Link Aggregation capability and general information relevant to specific MAC types that support Link Aggregation. The capabilities defined are compatible with previous versions of this standard.


Information technology — UPnP Device Architecture — Part 20-10: Audio video device control protocol — Level 4 — Audio video transport service

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-10: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Service de transport audio-vidéo

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.


Information technology — UPnP Device Architecture — Part 20-11: Audio video device control protocol — Level 4 — Connection manager service

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-11: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Service de gestionnaire de connexion

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.


Information technology — UPnP Device Architecture — Part 20-12: Audio video device control protocol — Level 4 — Content directory service

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-12: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Service d'Annuaire de contenu

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.


Information technology — UPnP Device Architecture — Part 20-13: Audio video device control protocol — Level 4 — Rendering control service

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-13: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Service de contrôle de rendu

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.


Information technology — UPnP Device Architecture — Part 20-14: Audio video device control protocol — Level 4 — Scheduled recording service

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-14: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Service d'enregistrement programmé

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.


Information technology — UPnP Device Architecture — Part 20-2: Audio video device control protocol — Level 4 — Media renderer device

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-2: Protocole de contrôle de dispositif audio-vidéo — Niveau 4 — Dispositif de moteur de rendu de média

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.


Information technology — UPnP Device Architecture — Part 20-3: Audio video device control protocol — Level 4 — Media server device

Technologies de l'information — Architecture de dispositif UPnP — Partie 20-3: Protocole de contrôle de dispositif audio-vidéo —  Niveau 4 — Dispositif serveur de média

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.


Information technology — UPnP Device Architecture — Part 24-1: Internet gateway device control protocol — Level 2 — Internet gateway device

Technologies de l'information — Architecture de dispositif UPnP — Partie 24-1: Protocole de contrôle de dispositif de passerelle Internet — Niveau 2 — Dispositif de passerelle Internet

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).


Information technology — UPnP Device Architecture — Part 24-2: Internet gateway device control protocol — Level 2 — Wide area network connection device

Technologies de l'information — Architecture de dispositif UPnP — Partie 24-2: Protocole de contrôle de dispositif de passerelle Internet — Niveau 2 — Dispositif de connexion de réseau étendu

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].


Information technology — UPnP Device Architecture — Part 24-3: Internet gateway device control protocol — Level 2 — Wide area network device

Technologies de l'information — Architecture de dispositif UPnP — Partie 24-3: Protocole de contrôle de dispositif de passerelle Internet — Niveau 2 — Dispositif de réseau étendu

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]).


Information technology — UPnP Device Architecture — Part 24-10: Internet gateway device control protocol — Level 2 — Wide area network internet protocol — Connection service

Technologies de l'information — Architecture de dispositif UPnP — Partie 24-10: Protocole de contrôle de dispositif de passerelle Internet — Niveau 2 — Protocole internet de réseau étendu — Service de connexion

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.


Information technology — UPnP Device Architecture — Part 24-11: Internet gateway device control protocol — Level 2 — Wide area network internet protocol v6 — Firewall control service

Technologies de l'information — Architecture de dispositif UPnP — Partie 24-11: Protocole de contrôle de dispositif de passerelle Internet — Niveau 2 — Protocole internet de réseau étendu v6— Service de contrôle du pare-feu

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


Information technology — UPnP Device Architecture — Part 25-1: Telephony device control protocol — Telephony architecture

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-1:


Information technology — UPnP Device Architecture — Part 25-2: Telephony device control protocol — Telephony security best practice

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-2:


Information technology — UPnP Device Architecture — Part 25-3: Telephony device control protocol — Telephony client device

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-3:


Information technology — UPnP Device Architecture — Part 25-4: Telephony device control protocol — Telephony server device

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-4:


Information technology — UPnP Device Architecture — Part 25-10: Telephony device control protocol — Call management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-10:


Information technology — UPnP Device Architecture — Part 25-11: Telephony device control protocol — Input configuration service

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-11:


Information technology — UPnP Device Architecture — Part 25-12: Telephony device control protocol — Media management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-12:


Information technology — UPnP Device Architecture — Part 25-13: Telephony device control protocol — Messaging service

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-13:


Information technology — UPnP Device Architecture — Part 25-14: Telephony device control protocol — Phone management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 25-14:


Information technology — UPnP Device Architecture — Part 26-1: Telephony device control protocol — Level 2 — Telephony architecture

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-1: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Architecture de téléphonie

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.


Information technology — UPnP Device Architecture — Part 26-2: Telephony device control protocol — Level 2 — Telephony client device

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-2: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Dispositif de client de téléphonie

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.


Information technology — UPnP Device Architecture — Part 26-3: Telephony device control protocol — Level 2 — Telephony server device

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-3: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Dispositif de serveur de téléphonie

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.


Information technology — UPnP Device Architecture — Part 26-10: Telephony device control protocol — Level 2 — Call management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-10: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de gestion des appels

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.


Information technology — UPnP Device Architecture — Part 26-11: Telephony device control protocol — Level 2 — Media management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-11: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de gestion des médias

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.


Information technology — UPnP Device Architecture — Part 26-12: Telephony device control protocol — Level 2 — Messaging service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-12: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de messagerie

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;


Mobile cranes — Determination of stability — Amendment 1

Grues mobiles — Détermination de la stabilité — Amendement 1


Information technology — UPnP Device Architecture — Part 26-13: Telephony device control protocol — Level 2 — Phone management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-13: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de gestion du téléphone

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.


Information technology — UPnP Device Architecture — Part 26-14: Telephony device control protocol — Level 2 — Address book service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-14: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de carnet d'adresses

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.


Information technology — UPnP Device Architecture — Part 26-15: Telephony device control protocol — Level 2 — Calendar service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-15: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de calendrier

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


Information technology — UPnP Device Architecture — Part 26-16: Telephony device control protocol — Level 2 — Presence service

Technologies de l'information — Architecture de dispositif UPnP — Partie 26-16: Protocole de contrôle de dispositif de téléphonie —  Niveau 2 — Service de présence

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.


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

Technologies de l'information — Architecture de dispositif UPnP — Partie 27-1: Protocole de contrôle de dispositif convivial — Service de présence — Service convivial de mise à jour de l'information

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.


Information technology — UPnP Device Architecture — Part 28-1: Multiscreen device control protocol — Multiscreen architecture

Technologies de l'information — Architecture de dispositif UPnP — Partie 28-1: Protocole de contrôle de dispositif multi-écran — Architecture multi-écran

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.


Information technology — UPnP Device Architecture — Part 28-2: Multiscreen device control protocol — Screen device

Technologies de l'information — Architecture de dispositif UPnP — Partie 28-2: Protocole de contrôle de dispositif multi-écran — Dispositif écran

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.


Information technology — UPnP Device Architecture — Part 28-10: Multiscreen device control protocol — Application management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 28-10: Protocole de contrôle de dispositif multi-écran — Service de gestion des applications

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.


Information technology — UPnP Device Architecture — Part 29-2: Multiscreen device control protocol — Level 2 — Screen device

Technologies de l'information — Architecture de dispositif UPnP — Partie 29-2: Protocole de contrôle de dispositif multi-écran — Niveau 2 — Dispositif écran

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.


Information technology — UPnP Device Architecture — Part 29-10: Multiscreen device control protocol — Level 2 — Application management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 29-10: Protocole de contrôle de dispositif multi-écran — Niveau 2 — Service de gestion des applications

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.


Information technology — UPnP Device Architecture — Part 30-1: IoT management and control device control protocol — IoT management and control architecture overview

Technologies de l'information — Architecture de dispositif UPnP — Partie 30-1: Protocole de contrôle de dispositif de gestion et de contrôle de l'Internet des objets — Aperçu général de l'architecture de gestion et de contrôle de l'Internet des objets

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.


Information technology — UPnP Device Architecture — Part 30-2: IoT management and control device control protocol — IoT management and control device

Technologies de l'information — Architecture de dispositif UPnP — Partie 30-2: Protocole de contrôle de dispositif de gestion et de contrôle de l'Internet des objets — Dispositif de gestion et de contrôle de l'Internet des objets

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.


Information technology — UPnP Device Architecture — Part 30-10: IoT management and control device control protocol — Data store service

Technologies de l'information — Architecture de dispositif UPnP — Partie 30-10: Protocole de contrôle de dispositif de gestion et de contrôle de l'Internet des objets — Service de stockage des données

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.


Information technology — UPnP Device Architecture — Part 30-11: IoT management and control device control protocol — IoT management and control data model service

Technologies de l'information — Architecture de dispositif UPnP — Partie 30-11: Protocole de contrôle de dispositif de gestion et de contrôle de l'Internet des objets — Service de modèle de données de gestion et de contrôle de l'Internet des objets

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.


Information technology — UPnP Device Architecture — Part 30-12: IoT management and control device control protocol — IoT management and control transport generic service

Technologies de l'information — Architecture de dispositif UPnP — Partie 30-12: Protocole de contrôle de dispositif de gestion et de contrôle de l'Internet des objets — Service de transport générique de gestion et de contrôle de l'Internet des objets

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.


Information technology — UPnP Device Architecture — Part 31-1: Energy management device control protocol — Energy management service

Technologies de l'information — Architecture de dispositif UPnP — Partie 31-1: Protocole de contrôle du dispositif de management de l'énergie — Service de management de l'énergie

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.


Method for the detection of Clostridium botulinum toxins (A, B, E, F) in food, based on immunological method

Méthode de détection de toxines botuliques de Clostridium (A, B, E, F) dans les aliments, basée sur la méthode immunologique


In vitro diagnostic test systems — Requirements for blood-glucose monitoring systems for self-testing in managing diabetes mellitus

Systèmes d'essais de diagnostic in vitro — Exigences relatives aux systèmes d'autosurveillance de la glycémie destinés à la prise en charge du diabète sucré


In vitro diagnostic medical devices — Evaluation of stability of in vitro diagnostic reagents

Dispositifs médicaux de diagnostic in vitro — Évaluation de la stabilité des réactifs de diagnostic in vitro


Underwater acoustics — Measurement of ambient sound


Underwater acoustics — Measurement of sound pressure


Underwater acoustics — Measurement of sound from offshore petroleum operations


Underwater acoustics — Calibration of autonomous acoustic receiver/recorder systems


Hand taps for parallel and taper pipe threads — General dimensions and marking

Tarauds à main pour filetages cylindrique et conique de tuyauterie — Dimensions générales et marquage

ISO 2284:2017 specifies the general dimensions and marking of hand taps for pipe threads.

It is applicable to the two following types of tap:

-      taps for parallel threads (see Figure 1 and Table 1),

-      taps for taper threads (see Figure 2 and Table 2),

having threads in accordance with ISO 7‑1 and ISO 228‑1.

Furthermore, it gives in Annex A the bases used for calculation of the dimensions, and in Annex B the relationship between designations in this document and the ISO 13399 series.


Hand- and machine-operated circular screwing dies for taper pipe threads — R series

Filières rondes de filetage, à main et à machine, pour filetages coniques de tuyauterie — Série R

ISO 4230:2016 is a supplement to ISO 2568 and ISO 4231 and specifies the dimensions of hand- and machine-operated circular screwing dies intended for production of taper pipe threads, R series, in accordance with ISO 7‑1.

With the exception of the die 1/16, the general dimensions of these dies (diameter, thickness and fixing dimensions) are in accordance with ISO 2568 so as to permit the driving of hand-operated dies with the aid of the die stocks defined in that document.


Hand- and machine-operated circular screwing dies for parallel pipe threads — G series

Filières rondes de filetage, à main et à machine, pour filetages cylindriques de tuyauterie — Série G

ISO 4231:2016 is a supplement to ISO 2568 and ISO 4230 and specifies the dimensions of hand- and machine-operated circular screwing dies intended for production of parallel pipe threads, G series, in accordance with ISO 228‑1.

The general dimensions of these dies (diameter, thickness and fixing dimensions) are in accordance with ISO 2568 so as to permit the driving of hand-operated dies with the aid of the die stocks defined in that document.


ISO 529:2017 specifies the general dimensions of short machine taps and hand taps. These dimensions, established as functions of the thread diameter and pitch, are the following:

-      length of thread (maximum);

-      overall length;

-      shank diameter and dimensions of driving square;

-      dimensions of the connecting portion between the shank and threaded part.

ISO 529:2017 is applicable to taps intended for cutting the following threads:

a)    ISO metric threads:

-      coarse pitch;

-      fine pitch;

b)    ISO inch threads:

-      "Unified Coarse" series (UNC) and "Unified Fine" series (UNF);

c)    Inch threads, non-recommended:

-      "British Standard Whitworth" (BSW) and "British Standard Fine" (BSF);

-      "British Association" (BA).

NOTE 1       The overall length, thread length and diameters of shank for taps whose thread diameter and pitch are not listed in tables are given in Table A.1.

NOTE 2       Annex B gives an abstract from ISO 237 for shank diameters and size of driving squares, for information.

NOTE 3       Technical specifications for taps covered by this document (including marking) are given in ISO 8830.


Rotary and rotary impact masonry drill bits with hardmetal tips — Dimensions

Forets pour bâtiment, à rotation et percussion, à plaquettes en métal-dur (carbures métalliques) — Dimensions

ISO 5468:2017 specifies the dimensions, in millimetres, of rotary and rotary impact masonry drill bits with hardmetal tips, having diameters in the range of 4 mm to 25 mm inclusive and overall, and working lengths in the series short, long and extra-long.

It does not apply to hammer drills.


Indexable inserts for cutting tools — Designation

Plaquettes amovibles pour outils coupants — Désignation

ISO 1832:2017 establishes a code for the designation of the usual types of indexable inserts for cutting tools in hard cutting materials or any other cutting materials, in order to simplify orders and specifications for such inserts.

It also specifies the designations for cubic boron nitride (BL, BH, BC) inserts, tipped and solid, as well as polycrystalline diamond (DP) inserts, tipped.


Information technology — Service management — Part 12: Guidance on the relationship between ISO/IEC 20000-1:2011 and service management frameworks: CMMI-SVC

Technologies de l'information — Gestion des services — Partie 12: Directives sur la relation entre l'ISO/IEC 20000-1:2011 et les cadres de management du service: CMMI-SVC

ISO/IEC TR 20000-12:2016 provides guidance on the relationship between ISO/IEC 20000‑1:2011 and CMMI-SVC V1.3 (through Maturity Level 3). Service providers can refer to this guidance as a cross-reference between the two documents to help them to plan and implement an SMS. An organization employing the practices in the indicated CMMI-SVC process areas can conform to many of the associated ISO/IEC 20000‑1 requirements.

The guidance in Clause 4 describes how CMMI-SVC can support the demonstration of conformity to ISO/IEC 20000‑1:2011. A description of the purpose and content of both publications in 4.1 and 4.2 is followed by Clause 5, which relates process areas in CMMI-SVC to clauses in ISO/IEC 20000‑1:2011. The tables in Annexes A and B relate terms, clauses, and paragraphs in ISO/IEC 20000‑1:2011 to CMMI-SVC. Table B.1 is a simplified summary of the correlation seen in Table 3 for those readers who want an overview. The tables indicate those aspects of ISO/IEC 20000‑1:2011 and CMMI-SVC that represent the greatest link between the two sets of documents, from the perspective of a service provider.

ISO/IEC TR 20000-12:2016 can be used by any organization or person who wishes to understand how CMMI-SVC can be used with ISO/IEC 20000‑1:2011, including the following:

a)    a service provider that intends to demonstrate conformity to the requirements of ISO/IEC 20000‑1:2011 and is seeking guidance on the use of CMMI-SVC to establish and maintain the SMS and the services;

b)    a service provider that has demonstrated conformity to the requirements of ISO/IEC 20000‑1:2011 and is seeking guidance on ways to use CMMI-SVC to improve the SMS and the services;

c)    a service provider that already uses CMMI-SVC and is seeking guidance on how CMMI-SVC can be used to support efforts to demonstrate conformity to the requirements specified in ISO/IEC 20000‑1:2011;

d)    an appraiser or assessor who wishes to understand the use of CMMI-SVC as support for the requirements specified in ISO/IEC 20000‑1:2011.

ISO/IEC TR 20000-12:2016 can also be used with the other parts of the ISO/IEC 20000 series.


Indexable hardmetal (carbide) inserts with rounded corners, with cylindrical fixing hole — Dimensions

Plaquettes amovibles en métaux-durs (carbures métalliques) avec arrondi de pointe et trou de fixation cylindrique — Dimensions

ISO 3364:2017 specifies the dimensions of indexable hardmetal (carbide) inserts with rounded corners, with cylindrical fixing hole and with 0° normal clearance. These inserts are primarily intended to be mounted by top and hole clamping or by hole alone on turning and boring tools.


Gas cylinders — Seamless steel and aluminium-alloy gas cylinders — Evaluation of existing gas cylinders and consideration of their safe use in other jurisdictions

Bouteilles à gaz — Bouteilles à gaz en acier et en alliages d'aluminium, sans soudure — Évaluation des bouteilles à gaz existantes et considérations relatives à leur utilisation en toute sécurité dans d'autres jurisdictions

ISO/TS 15453:2017 details the checks, inspections and tests to be performed in order to qualify and certify existing seamless steel and aluminium-alloy cylinders of water capacity less than 150 l used for the transport of gases, manufactured in a jurisdiction in accordance with its national regulations, for use in jurisdictions other than that of manufacture or first use.

NOTE          For specific requirements regarding gas cylinders that have been used in toxic gas service, see 5.7.

ISO/TS 15453:2017 does not address acetylene cylinders.


Information technology — Object Identifier assignments for the Internet of Things


Geotechnical investigation and testing — Geotechnical monitoring by field instrumentation — Part 3: Measurement of displacements across a line: Inclinometers

Reconnaissance et essais géotechniques — Surveillance géotechnique par instrumentation in situ — Partie 3: Mesurages des déplacements perpendiculairement à une ligne par inclinomètre

ISO 18674-3:2017 specifies the measurement of displacements across a line by means of inclinometers carried out for geotechnical monitoring. General rules of performance monitoring of the ground, of structures interacting with the ground, of geotechnical fills and of geotechnical works are presented in ISO 18674‑1.

ISO 18674-3:2017 also refers to deflectometers (see Annex B) to supplement inclinometers for the determination of horizontal displacements across horizontal measuring lines.

NOTE       In general, there are two independent displacement components acting across measuring lines. Inclinometers allow the determination of the two components for vertical measuring lines. For horizontal lines, inclinometers are limited to the determination of the vertical component only.

If applied in conjunction with ISO 18674‑2, ISO 18674-3:2017 allows the determination of displacements acting in any direction.

ISO 18674-3:2017 is applicable to:

-      checking geotechnical designs in connection with the Observational Design procedure;

-      monitoring of geotechnical structures prior to, during and after construction (e.g. natural slopes, slope cuts, embankments, excavation walls, foundations, dams, refuse dumps, tunnels);

-      deriving geotechnical key parameters (e.g. from results of pile load tests or trial tunnelling);

-      identification and monitoring of active shear planes in the ground.

NOTE       ISO 18674-3:2017 fulfils the requirements for the performance monitoring of the ground, of structures interacting with the ground and of geotechnical works by the means of inclinometers as part of the geotechnical investigation and testing in accordance with References [1] and [2].


Information technology — Open data protocol (OData) v4.0 — Part 1: Core

Technologies de l'information — Protocole de données ouvertes (OData) v4.0 — Partie 1: Base

ISO/IEC 20802-1:2016 defines the core semantics and facilities of the Open Data Protocol (OData). This enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Locators (URLs) and defined in an Entity Data Model (EDM), to be published and edited by Web clients using simple HTTP messages.


Information technology — Open data protocol (OData) v4.0 — Part 2: OData JSON Format

Technologies de l'information — Protocole de données ouvertes (OData) v4.0 — Partie 2: Format OData JSON

ISO/IEC 20802-2:2016 extends ISO/IEC 20802-1, the core specification of the Open Data Protocol (OData) for representing and interacting with structured content, by defining representations for Odata requests and responses using a JSON format.


Metallic powders — Determination of acid-insoluble content in iron, copper, tin and bronze powders

Poudres métalliques — Détermination de la teneur en insolubles dans les acides pour les poudres de fer, de cuivre, d'étain et de bronze

ISO 4496:2017 specifies methods for determining, in iron, copper, tin and bronze powders, the approximate content of non-metallic materials which are insoluble in the ordinary mineral acids.

The insoluble matter referred to is generally considered to be acid-insoluble silica and silicates, carbides, alumina, clays or other refractory oxides which are either present in the raw material from which the powders are manufactured or introduced during the manufacturing process.


Hydrogen generators using water electrolysis — Industrial, commercial, and residential applications

Générateurs d'hydrogène utilisant le procédé de l'électrolyse de l'eau — Applications industrielles, commerciales et résidentielles

This document defines the construction, safety, and performance requirements of modular or factory-matched hydrogen gas generation appliances, herein referred to as hydrogen generators, using electrochemical reactions to electrolyse water to produce hydrogen.

This document is applicable to hydrogen generators that use the following types of ion transport medium:

—     group of aqueous bases;

—     group of aqueous acids;

—     solid polymeric materials with acidic function group additions, such as acid proton exchange membrane (PEM);

—     solid polymeric materials with basic function group additions, such as anion exchange membrane (AEM).

This document is applicable to hydrogen generators intended for industrial and commercial uses, and indoor and outdoor residential use in sheltered areas, such as car-ports, garages, utility rooms and similar areas of a residence.

Hydrogen generators that can also be used to generate electricity, such as reversible fuel cells, are excluded from the scope of this document.

Residential hydrogen generators that also supply oxygen as a product are excluded from the scope of this document.


Particle size analysis — Small angle X-ray scattering (SAXS)

Analyse granulométrique — Diffusion des rayons X aux petits angles (SAXS)

This document specifies a method for the application of small-angle X-ray scattering (SAXS) to the estimation of mean particle sizes in the 1 nm to 100 nm size range. It is applicable in dilute dispersions where the interaction and scattering effects between the particles are negligible. This document describes several data evaluation methods: the Guinier approximation, model-based data fitting, Monte-Carlo?based data fitting, the indirect Fourier transform method and the expectation maximization method. The most appropriate evaluation method is intended to be selected by the analyst and stated clearly in the report. While the Guinier approximation only provides an estimate for the mean particle diameter, the other methods also give insight in the particle size distribution.


Determination of the specific surface area of porous and particulate systems by small-angle X-ray scattering (SAXS)

Détermination de la surface spécifique pour des systèmes poreux et particulaires par diffusion des rayons X aux petits angles (SAXS)

This document specifies the application of small-angle X-ray scattering (SAXS) for the determination of specific surface area. Both the mass specific surface area in the order of 1 m2g-1 to 2 000 m2g-1 and the volume specific surface areas in the range from 0,01 m2cm-3 to 1 000 m2cm-3 can be obtained.

The method described is applicable to dilute and concentrated systems.

NOTE:      In ISO 17867:2020, the determination of the particle size by SAXS is limited to dilute systems.

The determination of surfaces with SAXS is straightforward for two-phase systems only. Surface determination in systems with more than two phases is beyond the scope of this document.

The term ‘surface’ refers to any interface between domains of different density (more precisely: electron density) and is not restricted to the external surface of particles. As any interfaces between areas with different electron density, not only to air or vacuum, can be probed, the method can be applied to any heterogeneous system.

SAXS measures not only the specific surface area of open pores but also of inaccessible, closed pores or inclusions.

NOTE:      This is in contrast to gas sorption methods which are described in ISO 9277:2010.

In addition to porous systems, there can be contributions of internal interfaces to the measured specific surface area of any heterogeneous compact solid system, such as between crystalline and amorphous phases, provided there is an electron density contrast. Although materials comprising micropores (pore width < 2 nm) can also be analysed with respect to their specific surface area with SAXS, this document does not cover these materials.


Information technology — Home electronic system (HES) interfaces — Part 3: Modular communications interface for energy management

Technologies de l'information — Interfaces de systèmes électroniques domestiques (HES) — Partie 3: Titre manque

ISO/IEC 10192-3:2017(E) this part of ISO/IEC 10192 specifies a Universal Communication Module (UCM) that transfers energy management data via a home network between an end device and an energy management agent (specified in ISO/IEC 15067-3) or an energy service provider. This document specifies the mechanical, electrical and logical characteristics of the interfaces of UCM to an end device and a choice of interfaces to a home communications network.


Essential oil of cypress (Cupressus sempervirens L.)

Huile essentielle de cyprès (Cupressus sempervirens L.)

ISO 20809:2017 specifies certain characteristics of the essential oil of cypress (Cupressus sempervirens L.) in order to facilitate assessment of its quality.


Biological evaluation of medical devices — Guidance on the conduct of biological evaluation within a risk management process

Évaluation biologique des dispositifs médicaux — Directives relatives à la conduite d'une évaluation biologique au sein d'un procédé de management du risque

ISO/TR 15499:2016 is applicable to the conduct of biological evaluation of medical devices according to the requirements of ISO 10993‑1. It does not add to, or otherwise change, the requirements of ISO 10993‑1. This document does not include requirements to be used as the basis of regulatory inspection or certification assessment activities.

This guidance is applicable to all biological evaluation of all types of medical devices including active, non-active, implantable and non-implantable medical devices.


Metallic powders — Determination of flow rate by means of a calibrated funnel (Hall flowmeter)

Poudres métalliques — Détermination du temps d'écoulement au moyen d'un entonnoir calibré (appareil de Hall)

ISO 4490:2018 specifies a method for determining the flow rate of metallic powders, including powders for hard metals, by means of a calibrated funnel (Hall flowmeter).

The method is applicable only to powders which flow freely through the specified test orifice.


Metallic powders — Determination of apparent density — Part 1: Funnel method

Poudres métalliques — Détermination de la masse volumique apparente — Partie 1: Méthode de l'entonnoir

This document specifies the funnel method for the determination of the apparent density of metallic powders under standardized conditions.

The method is intended for metallic powders that flow freely through a 2,5 mm diameter orifice. It can, however, be used for powders that flow with difficulty through a 2,5 mm diameter orifice but flow through a 5 mm diameter orifice.

Methods for the determination of the apparent density of powders that will not flow through a 5 mm diameter orifice are specified in ISO 3923‑2[1].


Cranes — Cabins and control stations — Part 2: Mobile cranes

Appareils de levage à charge suspendue — Cabines et postes de conduite — Partie 2: Grues mobiles

ISO 8566-2:2016 establishes the criteria for cabins for mobile cranes as defined in ISO 4306‑2. These criteria are intended to cover cabins only for crane operation and not for road travel.

The general criteria for cabins on mobile cranes are presented in ISO 8566‑1.


ISO 4506:2018 specifies a method of determining the ultimate strength and proof stress of cemented carbide under uniaxial compressive loads.