| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/IEC 15018:2004 |
Information technology — Generic cabling for homes |
ISO/IEC 15018:2004 specifies a generic cabling for three groups of applications in homes: Information and Communications Technologies (ICT), Broadcast and Communications Technologies (BCT), and Commands, Controls and Communications in Buildings (CCCB). It is intended to guide installations in new buildings or refurbishments, and also applies where cabling is installed to support only one or two of the three application groups listed above. A generic cabling infrastructure is specified based upon balanced cabling and / or coaxial cabling. ICT channels specified in this standard include optical fibre, but the wider use of fibre optical cabling in a home is for further study. The three groups of applications may also be supported by different types of cabling, which may be subject to other International Standards. For example, ISO/IE cabling for ICT applications in general for the office environment. While the cabling structure and reference implementations are matched to the home environment in ISO/IEC 15018:2004, the channel performances specified for ICT are identical to those specified in ISO/IEC 11801.
|
Withdrawn |
2004-06 |
Edition : 1 |
Number of pages : 72 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 15018:2004/Amd 1:2009 |
Information technology — Generic cabling for homes — Amendment 1: . |
|
Withdrawn |
2009-04 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 15044:2000 |
Information technology — Terminology for the Home Electronic System (HES) |
|
Published |
2000-08 |
Edition : 2 |
Number of pages : 11 |
Technical Committee |
35.200
Interface and interconnection equipment
;
01.040.35
Information technology (Vocabularies)
;
35.240.99
IT applications in other fields
|
| ISO/IEC 15045-1:2004 |
Information technology — Home Electronic System (HES) gateway — Part 1: A residential gateway model for HES |
The Residential Gateway (RG) is a device of the Home Electronic System (HES) that connects home network domains to network domains outside the house. It supports communications among devices within the premises, and among systems, service providers, operators and users outside the premises.
The RG enables service and content providers to deliver services such as entertainment, video and broadband digital streams, monitoring for health care, security and occupancy, home appliance control and preventive maintenance, remote metering, and energy management. The RG specified by this standard does not imply the use of any particular protocol such as IP and it is recognised that many forms of the RG will exist using many types of data such as analogue video and broadband digital streams.=
|
Published |
2004-01 |
Edition : 1 |
Number of pages : 29 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 15045-2:2012 |
Information technology — Home Electronic System (HES) gateway — Part 2: Modularity and protocol |
ISO/IEC 15045-2:2012(E) specifies a gateway architecture that provides an interconnection between one or more Wide Area Networks (WANs) and one or more Home Area Networks (HANs). It is not needed for a "simple gateway" linking one WAN to one HAN where there is no intention of future expansion. It applies to a "distributed gateway," and is also referred to in ISO/IEC 15045-1 as the Complex Modular Gateway. Also, it specifies how separate gateways in a single house can interoperate to provide co-ordinated functions.
|
Published |
2012-07 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 15067-2:1997 |
Information technology — Home Electronic Systems (HES) application model — Part 2: Lighting model for HES |
|
Published |
1997-08 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 15067-3:2012 |
Information technology — Home Electronic System (HES) application model — Part 3: Model of a demand-response energy management system for HES |
ISO/IEC 15067-3:2012(E) specifies an energy management model for programs that manage the consumer demand for electricity using a method known as "demand response". Three types of demand response are specified in this standard: direct control, local control and distributed control. It replaces ISO/IEC TR 15067-3, first edition, published in 2000, and constitutes a technical revision. It includes the following significant technical changes with respect to the previous edition:
- the demand response options have been expanded;
- distributed energy resources such as local generation and storage have been included;
- the terminology for demand response has been aligned with smart grid.
|
Published |
2012-07 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 15067-3:2000 |
Information technology — Home Electronic Systems (HES) application model — Part 3: Model of an energy management system for HES |
|
Withdrawn |
2000-10 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 15067-4:2001 |
Information technology — Home Electronic System (HES) Application Model — Part 4: Security System for HES |
Residential security systems are among the most popular applications in a home automation
system. This model is intended to be generic. It is applicable to a wide variety of security
functions that extend well-beyond traditional intrusion detection. Potential applications of home
security as represented in this model include activity monitoring, duress monitoring, and safety
monitoring of personal well-being.
The intrusion and safety applications of a security system are similar for commercial buildings.
This generic model can therefore be extended to commercial building security functions.
|
Published |
2001-06 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 15067-3-7:2020 |
Information technology — Home Electronic System (HES) application model — Part 3-7: GridWise transactive energy systems research, development and deployment roadmap |
This document, which is a Technical Report, explains the organization and structure of the transactive energy systems research, development, and deployment roadmap.
|
Published |
2020-09 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 15067-3-8:2020 |
Information technology — Home Electronic System (HES) application model — Part 3-8: GridWise transactive energy framework |
ISO/IEC TR 15067-3-8:2020(E), which is a Technical Report, provides a conceptual framework for developing architectures and designing solutions related to transactive energy (TE). Transactive energy allows electricity generated locally by consumers using wind, solar, storage, etc., at homes or buildings to be sold into a competitive market. This document provides guidance for enhancing interoperability among distributed energy resources involved in energy management systems at homes and buildings. It addresses gaps identified as problematic for the industry by providing definitions of terms, architectural principles and guidelines, and other descriptive elements that present a common ground for all interested parties to discuss and advance TE.
This document builds upon ISO/IEC 15067-3, with technology to accommodate a market for buying and selling electricity generated centrally or locally by consumers. The energy management agent (EMA) specified in ISO/IEC 15067-3 can represent the customer as a participant in TE. Transactive energy is important for achieving electric grid stability as power from renewable sources such as wind and solar fluctuates with time and weather.
|
Published |
2020-09 |
Edition : 1 |
Number of pages : 74 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 15067-3-3:2019 |
Information technology — Home Electronic System (HES) application model — Part 3-3: Model of a system of interacting Energy Management Agents (EMAs) for demand response energy management |
ISO/IEC 15067-3-3:2019(E) specifies a high-level architecture and a set of models for a demand-response energy management system with multiple interacting EMAs in a home or community housing (such as one or more apartment buildings or a campus of houses). These models specify the structure among multiple EMAs, which can be arranged in a mesh or hierarchical structure. This document builds upon ISO/IEC 15067-3.
|
Published |
2019-10 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 15067-3-2:2016 |
Information technology — Home Electronic System (HES) application model — Part 3-2: GridWise interoperability context-setting framework |
ISO/IEC TR 15067-3-2:2016(E) This Technical Report is based on work done by the GridWise Architecture Council. It describes a framework for identifying and discussing interoperability issues to facilitate the integration of entities that interact with electric power systems.
|
Published |
2016-11 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 17760-101:2015 |
Information technology — AT Attachment 8 — Part 101: ATA/ATAPI Command Set (ATA8-ACS) |
ISO/IEC 17760-101:2015(E) specifies the command set host systems use to access storage devices. It provides a common command set for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices.
|
Published |
2015-06 |
Edition : 1 |
Number of pages : 432 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 17760-102:2016 |
Information technology — AT Attachment — Part 102: ATA/ATAPI Command set - 2 (ACS-2) |
ISO/IEC 17760-102:2016(E) specifies the command set host systems use to access storage devices. It provides a common command set for systems manufacturers, systems integrators, and suppliers of intelligent storage devices.
|
Published |
2016-03 |
Edition : 1 |
Number of pages : 566 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 17760-103:2021 |
Information technology — AT Attachment — Part 103: ATA/ATAPI Command Set - 3 (ACS-3) |
This document specifies the command set host systems use to access storage devices. It provides a common command set for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices.This document maintains compatibility with the ACS-2 standard, ISO/IEC 17760-102, while providing additional functions.
|
Published |
2021-06 |
Edition : 1 |
Number of pages : 554 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 18012-1:2004 |
Information technology — Home Electronic System — Guidelines for product interoperability — Part 1: Introduction |
Specifies requirements for product interoperability in the area of home and building automation systems, with sufficient detail needed to design interoperable Home Electronic System products. The widespread development of many national standard and proprietary networks within and to the home has necessitated a standard for interoperability among home system applications and products from multiple manufacturers. Where widely varying devices need to interoperate, it is desirable that they do so seamlessly to present a single, uniform network and hence to deliver a variety of applications. Examples of such applications are lighting control, environmental control, audio/video equipment control and home security.
Although a single uniform home control system would simplify operations, this standard recognises that multiple different networks may co-exist in the same house, and therefore applies to devices connected to a single home control system or to different home control systems. It ensures that, where applications on the same or dissimilar networks co-exist within premises and are required to interoperate, they will do so in a safe, reliable, predictable and consistent manner. It specifies requirements to assure that devices from multiple manufacturers work together to provide a specific application; a specific device could also be used for multiple applications. Interoperability requirements are given with respect to safety, addressing, applications, transport of information, management, and set-up of devices/elements within home networks - static and/or dynamic binding between objects.
This part defines the components of interoperability for the purpose of providing a framework within which subsequent parts of the standard will be drafted. This part applies to components within networks, between networks and located within dissimilar networks, as well as to devices located at the junction of dissimilar networks.
|
Published |
2004-02 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 18012-2:2012 |
Information technology — Home Electronic System — Guidelines for product interoperability — Part 2: Taxonomy and application interoperability model |
ISO/IEC 18012-2:2012(E) specifies a taxonomy and application interoperability model for the interoperability of products in the area of home systems. It also specifies an interoperability framework to allow products from multiple manufacturers to work together in order to provide a specific application. It describes a application process that exists above the OSI reference model (ISO/IEC 7498-1) stack, with sufficient detail needed to establish interoperable applications in this domain. It is applicable to: single implementation home electronic system networks, connected devices and applications, multiple implementation home electronic system networks, connected devices and applications, automatically configured devices, manually configured devices and manually configured groups/clusters of devices.
|
Published |
2012-07 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 18036:2003 |
Information technology — Icon symbols and functions for World Wide Web browser toolbars |
ISO/IEC 18036:2003 defines a consistent set of icons and related functions that are represented by World Wide Web browser applications on a computer screen and that users interact with to control such applications. The toolbar icons typically represent actions by association with objects in the real world and conventional controls on hardware, and that prompt the user to recall the intended actions.
ISO/IEC 18036:2003 provides a consistent set of icons applying to such functions as: Back, Forward, Refresh, Home, Search, Print and Stop.
Each icon in ISO/IEC 18036:2003 is specified with the following:
Primary function;Specific instance;Components;Graphic.
Web browser toolbar icons enable users to invoke functions that act upon pre-selected or default objects. Functions initiated by these icons may also be available via text commands on menus. Web browser toolbar icons provide direct access to functions by graphically representing those text commands.
|
Published |
2003-10 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 18598:2016 |
Information technology — Automated infrastructure management (AIM) systems — Requirements, data exchange and applications |
ISO/IEC 18598:2016(E) This standard specifies the requirements and recommendations for data exchange attributes of automated infrastructure management (AMI) systems.
|
Published |
2016-09 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 18598:2016/Amd 1:2021 |
Information technology — Automated infrastructure management (AIM) systems — Requirements, data exchange and applications — Amendment 1 |
|
Published |
2021-03 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 19987:2015 |
Information technology — EPC Information services — Specification |
ISO/IEC 19987:2015 is a GS1 Standard that defines Version 1.1 of EPC Information Services (EPCIS). The goal of EPCIS is to enable disparate applications to create and share visibility event data, both within and across enterprises. Ultimately, this sharing is aimed at enabling users to gain a shared view of physical or digital objects within a relevant business context.
"Objects" in the context of EPCIS typically refers to physical objects that are identified either at a class or instance level and which are handled in physical handling steps of an overall business process involving one or more organizations. Examples of such physical objects include trade items (products), logistic units, returnable assets, fixed assets, physical documents, etc. "Objects" may also refer to digital objects, also identified at either a class or instance level, which participate in comparable business process steps. Examples of such digital objects include digital trade items (music downloads, electronic books, etc.), digital documents (electronic coupons, etc), and so forth. Throughout this document the word "object" is used to denote a physical or digital object, identified at a class or instance level, that is the subject of a business process step. EPCIS data consist of "visibility events," each of which is the record of the completion of a specific business process step acting upon one or more objects.
The EPCIS standard was originally conceived as part of a broader effort to enhance collaboration between trading partners by sharing of detailed information about physical or digital objects. The name EPCIS reflects the origins of this effort in the development of the Electronic Product Code (EPC). It should be noted, however, that EPCIS does not require the use of Electronic Product Codes, nor of Radio-Frequency Identification (RFID) data carriers, and as of EPCIS 1.1 does not even require instance-level identification (for which the Electronic Product Code was originally designed). The EPCIS standard applies to all situations in which visibility event data is to be captured and shared, and the presence of "EPC" within the name is of historical significance only.
EPCIS provides open, standardised interfaces that allow for seamless integration of well-defined services in inter-company environments as well as within companies. Standard interfaces are defined in the EPCIS standard to enable visibility event data to be captured and queried using a defined set of service operations and associated data standards, all combined with appropriate security mechanisms that satisfy the needs of user companies. In many or most cases, this will involve the use of one or more persistent databases of visibility event data, though elements of the Services approach could be used for direct application-to-application sharing without persistent databases.
With or without persistent databases, the EPCIS specification specifies only a standard data sharing interface between applications that capture visibility event data and those that need access to it. It does not specify how the service operations or databases themselves should be implemented. This includes not defining how the EPCIS services should acquire and/or compute the data they need, except to the extent the data is captured using the standard EPCIS capture operations. The interfaces are needed for interoperability, while the implementations allow for competition among those providing the technology and implementing the standard.
EPCIS is intended to be used in conjunction with the GS1 Core Business Vocabulary (CBV) standard [CBV1.1]. The CBV standard provides definitions of data values that may be used to populate the data structures defined in the EPCIS standard. The use of the standardized vocabulary provided by the CBV standard is critical to interoperability and critical to provide for querying of data by reducing the variation in how different businesses express common intent. Therefore, applications should use the CBV standard to the greatest extent possible in constructing EPCIS data.
|
Withdrawn |
2015-09 |
Edition : 1 |
Number of pages : 169 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 19987:2017 |
Information technology — EPC Information Services (EPCIS) Standard |
ISO/IEC 19987:2017 defines Version 1.2 of EPC Information Services (EPCIS). The goal of EPCIS is to enable disparate applications to create and share visibility event data, both within and across enterprises.
|
Published |
2017-10 |
Edition : 2 |
Number of pages : 125 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC DIS 19987 |
Information technology — EPC Information Services (EPCIS) |
|
Under development |
|
Edition : 3 |
Number of pages : 182 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24740:2008 |
Information technology — Responsive Link (RL) |
Specifies the communications protocol and interface of Responsive Link, a real-time communications method for parallel/distributed control. Corresponds to the functions specified in layer 1 to layer 4 of the OSI reference model.
|
Published |
2008-01 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TS 22237-5:2018 |
Information technology — Data centre facilities and infrastructures — Part 5: Telecommunications cabling infrastructure |
ISO/IEC TS 22237-5:2018 addresses the wide range of telecommunications cabling infrastructures within data centres based upon the criteria and classifications for "availability" within ISO/IEC TS 22237‑1.
ISO/IEC TS 22237-5:2018 specifies requirements and recommendations for the following:
a) information technology and network telecommunications cabling (e.g. SAN and LAN);
b) general information technology cabling to support the operation of the data centre;
c) telecommunications cabling to monitor and control, as appropriate, power distribution, environmental control and physical security of the data centre;
d) other building automation cabling;
e) pathways, spaces and enclosures for the telecommunications cabling infrastructures.
Safety and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by other standards and regulations. However, information given in this document may be of assistance in meeting these standards and regulations.
|
Published |
2018-05 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
35.020
Information technology (IT) in general
;
35.200
Interface and interconnection equipment
|
| ISO/IEC 24702:2006 |
Information technology — Generic cabling — Industrial premises |
In the field of customer premises cabling this International Standard specifies a wide range of communications services including automation, process control and monitoring applications for use in industrial premises. This International Standard complements the requirements of ISO/IEC 11801.
|
Withdrawn |
2006-10 |
Edition : 1 |
Number of pages : 79 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24702:2006/Amd 1:2009 |
Information technology — Generic cabling — Industrial premises — Amendment 1 |
|
Withdrawn |
2009-09 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 24704:2004 |
Information technology — Customer premises cabling for wireless access points |
The SCSI protocol is designed to provide an efficient peer-to-peer I/O bus with the maximum number of hosts and peripherals determined by the bus width (8 or 16). Data may be transferred asynchronously or synchronously at rates that depend primarily on device implementation and cable length. SCSI is an I/O interface that may be operated over a wide range of media and transfer rates. The set of SCSI standards provides for many different types of SCSI devices (disks, tapes, printers, scanners and many more), and specifies the interfaces, functions, and operations necessary to ensure interoperability between conforming SCSI implementations. This standard is a functional description of a device model that is applicable to all SCSI devices, and defines the SCSI commands that are mandatory and optional for all SCSI devices. Conforming implementations may employ any design technique that does not violate interoperability.
|
Published |
2004-07 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24739-1:2009 |
Information technology — AT Attachment with Packet Interface - 7 — Part 1: Register Delivered Command Set, Logical Register Set (ATA/ATAPI-7 V1) |
ISO/IEC 24739-1:2009(E) specifies the AT Attachment Interface between host systems and storage devices. It provides a common attachment interface for systems manufacturers, system integrators, software suppliers and suppliers of intelligent storage devices. It defines the register delivered commands used by devices implementing the standard.
|
Published |
2009-09 |
Edition : 1 |
Number of pages : 353 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24739-1:2009/Cor 1:2013 |
Information technology — AT Attachment with Packet Interface - 7 — Part 1: Register Delivered Command Set, Logical Register Set (ATA/ATAPI-7 V1) — Technical Corrigendum 1 |
|
Published |
2013-09 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24739-2:2009 |
Information technology — AT Attachment with Packet Interface - 7 — Part 2: Parallel transport protocols and physical interconnect (ATA/ATAPI-7) |
ISO/IEC 24739-2:2009(E) specifies the AT Attachment Interface between host systems and storage devices. It provides a common attachment interface for systems manufacturers, system integrators, software suppliers and suppliers of intelligent storage devices.
|
Published |
2009-11 |
Edition : 1 |
Number of pages : 214 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24739-3:2010 |
Information technology — AT Attachment with Packet Interface - 7 — Part 3: Serial transport protocols and physical interconnect (ATA/ATAPI-7 V3) |
ISO/IEC 24739-3:2010(E) specifies the connectors and cables for physical interconnection between host and storage device, the electrical and logical characteristics of the interconnecting signals, and the protocols for the transporting of commands, data, and status over the interface for the serial interface.
|
Published |
2010-03 |
Edition : 1 |
Number of pages : 228 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24739-3:2010/Cor 1:2013 |
Information technology — AT Attachment with Packet Interface - 7 — Part 3: Serial transport protocols and physical interconnect (ATA/ATAPI-7 V3) — Technical Corrigendum 1 |
|
Published |
2013-08 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 24746:2005 |
Information technology — Generic cabling for customer premises — Mid-span DTE power insertion |
Specifies mid-span power insertion into generic cabling as specified in ISO/IEC 11801, the location and allocation requirements in case of the replacement of a generic cabling component or components.
|
Published |
2005-08 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 24750:2007 |
Information technology — Assessment and mitigation of installed balanced cabling channels in order to support of 10GBASE-T |
This Technical Report specifies the transmission performance for channels to support 10GBASE-T. It also specifies the methods to assess whether Class E and Class F channels meet 10GBASE-T requirements.
|
Published |
2007-07 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24764:2010 |
Information technology — Generic cabling systems for data centres |
ISO/IEC 24764:2010(E) specifies generic cabling that supports a wide range of communications services for use within a data centre. It covers balanced cabling and optical fibre cabling. It is based upon and references the requirements of ISO/IEC 11801 and contains additional requirements that are appropriate to data centres in which the maximum distance over which communications services have to be distributed is 2 000 m.
|
Withdrawn |
2010-04 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24764:2010/Amd 1:2014 |
Information technology — Generic cabling systems for data centres — Amendment 1 |
|
Withdrawn |
2014-04 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24767-1:2008 |
Information technology — Home network security — Part 1: Security requirements |
ISO/IEC 24767-1:2008 specifies the security requirements that may come from inside or outside a home. This standard gives guidance for the design of security mechnisms applied either inside home networks or through the Internet, and it provides means to analyse the risks for each networked device and to define its specific security requirements.
|
Published |
2008-09 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.110
Networking
;
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 24767-2:2009 |
Information technology — Home network security — Part 2: Internal security services: Secure Communication Protocol for Middleware (SCPM) |
ISO/IEC 24767-2:2009(E) specifies security in a home network for equipment with limited IT capability. Secure Communication Protocol for Middleware (SCPM) is designed to support network security for equipment which is not capable of supporting Internet security protocols. SCPM provides the security services at the network layer and the protocol does not rely on any specific media transmission.
|
Published |
2009-01 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.110
Networking
;
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 24775-1:2014 |
Information technology — Storage management — Part 1: Overview |
ISO/IEC 24775-1:2014(E) defines an interface for the secure, extensible, and interoperable management of a distributed and heterogeneous storage system. This interface uses an object-oriented, XML-based, messaging-based protocol designed to support the specific requirements of managing devices and subsystems in this storage environment. Using this protocol, this part of ISO/IEC 24775 describes the information available to a WBEM Client from an Information Technology - Storage Management compliant CIM WBEM Server. This International Standard, together with ISO/IEC 24775-2 to ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. The significant technical changes with respect to the previous edition are listed in the INTRODUCTION.
|
Withdrawn |
2014-10 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-1:2021 |
Information technology — Storage management — Part 1: Overview |
The ISO/IEC 24775-1:2021 defines an interface for the secure, extensible, and interoperable management of a distributed and heterogeneous storage system. This interface uses an object-oriented, XML-based, messaging-based protocol designed to support the specific requirements of managing devices and subsystems in this storage environment. Using this protocol, this ISO/IEC 24775-1:2021 describes the information available to a WBEM Client from an SMI-S compliant WBEM Server
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 21 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-8:2014 |
Information technology — Storage management — Part 8: Media Libraries |
ISO/IEC 24775-8:2014(E) models various details of the following objects of the media library for monitoring: Library, Drives, Changer Devices, Slots, IO Slots, SCSI Interfaces and SCSI and FC Target Ports, Physical Tapes, Physical Package and Magazines. This International Standard, together with ISO/IEC 24775-1 to ISO/IEC 24775-7 and replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. It includes the following technical changes:
- reorganization into eight parts;
- maturity identification using stages and new profiles.
|
Withdrawn |
2014-11 |
Edition : 1 |
Number of pages : 125 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-2:2014 |
Information technology — Storage management — Part 2: Common Architecture |
ISO/IEC 24775-2:2014(E) defines the core architecture and protocols in SMI-S. The components of SMI-S architecture include:
- Transport - communicating management information between constituents of the management system;
- Health and fault management - detecting failures through monitoring the state of storage components;
- General information about the object model;
- Names - how SMI-S uses names to allow applications to correlate across SMI-S and to other standards;
- Standard messages - how exceptions are presented to client applications;
- Service discovery - techniques clients use to discover SMI-S services;
- Installation and upgrade - recommendations for implementations;
- Compliance - requirement for compliance to the standard. This International Standard, together with ISO/IEC 24775-1 and ISO/IEC 24775-2 to ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
- reorganization into eight parts;
- maturity identification using stages;
- and new profiles.
|
Withdrawn |
2014-10 |
Edition : 1 |
Number of pages : 170 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-2:2021 |
Information technology — Storage management — Part 2: Common Architecture |
Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4 defines the core architecture and protocols in SMI-S. The components of SMI-S architecture include:
Transport - communicating management information between constituents of the management system
Health and fault management - detecting failures through monitoring the state of storage components
General information about the object model
Names - how SMI-S uses names to allow applications to correlate across SMI-S and to other standards
Standard messages - how exceptions are presented to client applications
Service discovery - techniques clients use to discover SMI-S services
Installation and upgrade - recommendations for implementations
Compliance - requirement for compliance to the standard
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 192 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-3:2014 |
Information technology — Storage management — Part 3: Common Profiles |
ISO/IEC 24775-3:2014(E) defines profiles that are supported by profiles defined in the other parts of the ISO/IEC 24775 series. The first few clauses provide background material that helps explain the purpose and profiles and recipes (a subset of a profile). Common port profiles are grouped together since they serve as transport-specific variations of a common model. The port profiles are followed by other common profiles. Clause 50 presents recipes that span multiple profiles. This International Standard, together with ISO/IEC 24775-1, ISO/IEC 24775-2 and ISO/IEC 24775-4 to ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
- reorganization into eight parts;
- maturity identification using stages;
- and new profiles.
|
Withdrawn |
2014-10 |
Edition : 1 |
Number of pages : 401 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-3:2021 |
Information technology — Storage management — Part 3: Common profiles |
Storage Management Technical Specification, Part 3 Common Profiles, 1.8.0 Rev 4 defines profiles that are supported by profiles defined in the other parts of this standard. The first few clauses provide background material that helps explain the purpose and profiles. Common port profiles are grouped together since they serve as transport-specific variations of a common model. The port profiles are followed by other common profiles.
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 352 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-4:2014 |
Information technology — Storage management — Part 4: Block Devices |
ISO/IEC 24775-4:2014(E) defines an interface for the secure, extensible, and interoperable management of a distributed and heterogeneous storage system. This interface uses an object-oriented, XML-based, messaging-based protocol designed to support the specific requirements of managing devices and subsystems in this storage environment. Using this protocol, this International Standard describes the information available to a WBEM Client from an Information technology - Storage management compliant CIM WBEM
Server. This International Standard, together with ISO/IEC 24775-1 to ISO/IEC 24775-3 and ISO/IEC 24775-5 to ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
- reorganization into eight parts;
- maturity identification using stages;
- and new profiles.
|
Withdrawn |
2014-10 |
Edition : 1 |
Number of pages : 847 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-4:2021 |
Information technology — Storage management — Part 4: Block devices |
Thie ISO/IEC 24775-4:2021 defines an interface for the secure, extensible, and interoperable management of a distributed and heterogeneous storage system. This interface uses an object-oriented, XML-based, messaging-based protocol designed to support the specific requirements of managing devices and subsystems in this storage environment. Using this protocol, this e ISO/IEC 24775-4:2021 describes the information available to a WBEM Client from an SMI-S compliant WBEM Server.
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 946 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-5:2014 |
Information technology — Storage management — Part 5: File systems |
ISO/IEC 24775-5:2014(E) defines management profiles for Autonomous (top level) profiles for programs and devices whose central function
is providing support and access to file data. In addition, it provides documentation of component profiles (or subprofiles) that deal with file systems and management interface functions that may be used by other autonomous profiles not included in this part of the standard. This International Standard, together with ISO/IEC 24775-1 to ISO/IEC 24775-4 and ISO/IEC24775-6 to ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. This edition includes the following changes:
- Improved organisation;
- Maturity indication;
- expanded scope.
|
Withdrawn |
2014-12 |
Edition : 1 |
Number of pages : 375 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-5:2021 |
Information technology — Storage management — Part 5: File systems |
Storage Management Technical Specification, Part 2 Common Architecture, 1.8.0 Rev 4 defines the core architecture and protocols in SMI-S. The components of SMI-S architecture include:
Transport - communicating management information between constituents of the management system
Health and fault management - detecting failures through monitoring the state of storage components
General information about the object model
Names - how SMI-S uses names to allow applications to correlate across SMI-S and to other standards
Standard messages - how exceptions are presented to client applications
Service discovery - techniques clients use to discover SMI-S services
Installation and upgrade - recommendations for implementations
Compliance - requirement for compliance to the standard
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 377 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-6:2014 |
Information technology — Storage management — Part 6: Fabric |
ISO/IEC 24775-6:2014(E) defines management profiles for Autonomous (top level) profiles for programs and devices whose central function is providing support for storage networking. This standard includes four autonomous profiles: Fabric, Switch, Extender and iSCSI to FC Gateway. This International Standard, together with ISO/IEC 24775-1 to ISO/IEC 24775-5 and ISO/IEC 24775-7 and ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. It includes the following technical changes:
- reorganization into eight parts;
- maturity identification using stages and new profiles.
|
Withdrawn |
2014-11 |
Edition : 1 |
Number of pages : 288 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-6:2021 |
Information technology — Storage management — Part 6: Fabric |
The Storage Management Technical Specification, Part 6 Fabric defines management profiles for Autonomous (top level) profiles for programs and devices whose central function is providing support for storage networking. This version of Storage Management Technical Specification, Part 6 Fabric includes these autonomous profiles:
FabricThis profile defines the model and functions of a storage network including topology and zoning control.
SwitchThis profile defines the model and functions of a Fibre Channel Switch including state, status, and control of the device and it’s connections and product information,
ExtenderThis profile defines the model and functions of a networking device that allows for fibre channel to be extended over other networks, and specifically over IP (FCIP).
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 186 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-7:2014 |
Information technology — Storage management — Part 7: Host Elements |
ISO/IEC 24775-7:2014(E) defines management profiles for autonomous, component and abstract profiles for management of host-based storage devices. The autonomous profiles describe the management of a stand-alone host-based storage entity. The component profiles (or subprofiles) describe management of aspects of host-based storage entities that may be used by other autonomous profiles. Finally, this standard describes abstract profiles that may be used as a basis for creating additional Host-based autonomous profiles. This International Standard, together with ISO/IEC 24775-1 to ISO/IEC 24775-6 and ISO/IEC 24775-8, replaces ISO/IEC 24775, second edition, published in 2011, and constitutes a technical revision. It includes the following technical changes:
- reorganization into eight parts;
- maturity identification using stages and new profiles.
|
Withdrawn |
2014-11 |
Edition : 1 |
Number of pages : 132 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775-7:2021 |
Information technology — Storage management — Part 7: Host elements |
The host-base storage portion of the Storage Management Technical Specification defines management profiles for autonomous, component and abstract profiles for management of host-based storage devices. The autonomous profiles describe the management of a stand-alone host-based storage entity. The component profiles describe management of aspects of host-based storage entities that may be used by other autonomous profiles. Finally, this section describes abstract profiles that may be used as a basis for creating additional Host-based autonomous profiles.This version of the Host-based Storage portion of the Storage Management Technical Specification includes autonomous profiles:
"The Host Discovered Resources ProfileThis profile defines the model for the storage devices presented to an operating system running on a hostcomputer system. In addition, this profile describes the map of storage associated to a host-computer systemthat a client application can discover.
"The Fibre Channel HBA ProfileThis profile defines the model and functions of a Fibre Channel HBA that exports block storage to a hostcomputer system from a SAN device (Fibre Channel switch, array, tape library, etc.).
iSCSI Initiator ProfileThis profile defines the model and functions necessary to manage an iSCSI initiator.Component profiles used by autonomous profiles to describe aspects of host-based storage elementsand services. The component profiles defined in this version of the specification include:
Host Hardware RAID Controller ProfileThis profile defines the model and functions of a host-based RAID controller that exports block storage to ahost computer system from locally attached storage devices (internal hard drives, JBODs, etc.)
Storage HBA ProfileThis profile defines the model and functions of a SAS, SATA, SPI, or Fibre Channel HBA that exports storageto a host computer system from a SAN device (Fibre Channel switch, array, tape library, etc.).
Disk Partition ProfileThe Disk Partition profile models partition (or slice) configuration services provided by operating systems onsome platforms.
SB Multipath Management ProfileThe SB Multipath Management Profile models paths (connections between host controllers and device ports)for environments supporting the SB (Single Byte) command protocol.
SCSI Multipath Management ProfileThe SCSI Multipath Management profile models paths (connections between host controllers, device ports,and logical units) for environments supporting the SCSI command protocol.
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 165 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 14221:1998 |
Aerospace — Airframe ball bearings, single-row, self-aligning, precision, sealed, light duty — Inch series |
|
Withdrawn |
1998-05 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
49.035
Components for aerospace construction
|
| ISO/IEC 24775-8:2021 |
Information technology — Storage management — Part 8: Media libraries |
This version of the specification models various details of the following objects of the media library for monitoring.
Library
Drives
Changer Devices
Slots
IO Slots
SCSI Interfaces and SCSI and FC Target Ports
Physical Tapes
Physical Package
Magazines
In general, a CIM client can monitor the health and status of the above objects as well as get alert, status change and lifecycle CIM indications. In addition, a client can control the movement of media in a library using this specification.
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 55 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 24775:2011 |
Information technology — Storage management |
ISO/IEC 24775:2011(E) defines an interface for the secure, extensible,
and interoperable management of a distributed and heterogeneous storage system.
This interface uses an object-oriented, XML-based, messagingbased
protocol designed to support the specific requirements of managing devices and
subsystems in this storage environment. Using this protocol, this International
Standard describes the information available to a WBEM Client from an SMI-S
compliant CIM WBEM Server. This second edition cancels and replaces the first
edition published in 2007 and constitutes a technical. This edition includes
the following significant changes with respect to the previous edition:
- Expanded scope: The range of SAN components modeled by the profiles defined
in this specification has been greatly expanded. Many of the profiles that were
identified as either future work or experimental content at the time of the
initial publication have
matured to full profiles. In addition, new areas have been modeled
and included (e.g., SCSI Target Ports).
- Improved organization: The specification has been reorganized to provide more
information more easily. The experimental content has been incorporated into
the body of the document, rather than being segregated in an annex, to ease
planning for adoption of emerging techniques.
- Additional documentation of best practices and deployment concerns: The
specification now includes a more formal representation of common deployment
and usage practices, a more complete
treatment of backward compatibility issues and a more detailed discussion of
the capabilities of the API, grouping them into a five-level architecture,
spanning from physical devices to application-level manipulation, and
addressing error conditions, configuration, accounting performance and security
issues at each level.
|
Withdrawn |
2011-02 |
Edition : 2 |
Number of pages : 1484 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 29106:2007 |
Information technology — Generic cabling — Introduction to the MICE environmental classification |
This Technical Report acts as an introduction to the concepts used to develop the MICE environmental classification system used in cabling standards developed by ISO/IEC. It also gives the sources used to define the boundaries of MICE classifications.
|
Published |
2007-11 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 29106:2007/Amd 1:2012 |
Information technology — Generic cabling — Introduction to the MICE environmental classification — Amendment 1 |
|
Published |
2012-12 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 29106:2007/Amd 2:2019 |
Information technology — Generic cabling — Introduction to the MICE environmental classification — Amendment 2 |
|
Published |
2019-07 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 29107-1:2010 |
Information technology - Intelligent homes - Taxonomy of specifications — Part 1: The scheme |
ISO/IEC 29107-1:2010(E) specifies the concept for a taxonomy of standards and other related specifications applicable to intelligent homes. It is intended for the classification of specifications from ISO, IEC, ISO/IEC JTC 1, ITU and from organizations with liaison status with any of these. It is intended to the various standardisation bodies that are contributing to the intelligent home. With the help of the concept described in this report they should be able to classify their specifications. This will benefit the standardisation bodies to determine if there are overlapping specifications or areas for which specifications are missing.
|
Published |
2010-03 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC TR 29108:2013 |
Information technology — Terminology for intelligent homes |
ISO/IEC/TR 29108:2013(E) specifies the terminology recommended for future use in International Standards and other specifications for intelligent homes. In addition, it provides a collection of terms and definitions as already used and defined in relevant International Standards, Technical Specifications, Technical Reports and Recommendations developed by ISO, IEC, and ITU-T.
|
Published |
2013-03 |
Edition : 1 |
Number of pages : 71 |
Technical Committee |
35.200
Interface and interconnection equipment
;
01.040.35
Information technology (Vocabularies)
;
35.240.99
IT applications in other fields
|
| ISO/IEC 29341-10-1:2008 |
Information technology — UPnP Device Architecture — Part 10-1: Quality of Service Device Control Protocol - Quality of Service Architecture |
ISO/IEC 29341-10-1:2008(E) shows the three services in the UPnP architecture and illustrates the relationship of various QoS components. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TR 29125:2010 |
Information technology — Telecommunications cabling requirements for remote powering of terminal equipment |
ISO/IEC TR 29125:2010 targets the support of applications that provide remote power over balanced cabling to terminal equipment; covers the transmission and electrical parameters needed to support remote power over balanced cabling; covers various installation scenarios and how these may impact the capability of balanced cabling to support remote powering; specifies design and configuration of cabling as specified in International Standards ISO/IEC 11801, ISO/IEC 15018, ISO/IEC 24702 and ISO/IEC 24764; provides requirements and guidelines that will enable the support of a wide variety of extra low voltage (ELV) limited power source (LPS) applications using remote power supplied over balanced cabling.
|
Withdrawn |
2010-09 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TS 29125:2017 |
Information technology — Telecommunications cabling requirements for remote powering of terminal equipment |
ISO/IEC 29125:2017(E) This document specifies the use of generic balanced cabling for customer premises, as specified in the ISO/IEC 11801 series, for remote powering of terminal equipment. It provides guidance on new cabling installations and renovations. The customer premises may encompass one of more buildings or may be within a building that contains more than one organization. The cabling may be installed prior to the seelction of remote powering equipment or powered terminal equipment.
|
Published |
2017-04 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC TS 29125:2017/Amd 1:2020 |
Information technology — Telecommunications cabling requirements for remote powering of terminal equipment — Amendment 1 |
|
Published |
2020-05 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29145-1:2014 |
Information technology - Wireless Beacon-enabled Energy Efficient Mesh network (WiBEEM) for wireless home network services — Part 1: PHY Layer |
ISO/IEC 29145-1:2014(E) specifies the physical (PHY) layer of WiBEEM (Wireless beacon-enabled energy efficient mesh network) protocol for wireless home network services that supports a low power-consuming wireless mesh network topology as well as device mobility and QoS.
|
Published |
2014-03 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
35.110
Networking
;
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 29145-2:2014 |
Information Technology - Wireless Beacon-enabled Energy Efficient Mesh network (WiBEEM) for wireless home network services — Part 2: MAC Layer |
ISO/IEC 29145-2:2014(E) specifies the MAC of the WiBEEM (Wireless beacon-enabled energy efficient mesh network) protocol for wireless home network services that supports a low power-consuming wireless mesh network as well as device mobility and QoS.
|
Published |
2014-03 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
35.110
Networking
;
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 29145-3:2014 |
Information technology - Wireless Beacon-enabled Energy Efficient Mesh network (WiBEEM) for wireless home network services — Part 3: NWK Layer |
ISO/IEC 29145-3:2014(E) specifies the network layer (NWK) of the WiBEEM (Wireless Beacon-enabled Energy Efficient Mesh network) protocol for wireless home network services that supports a low power-consuming wireless mesh network as well as device mobility and QoS.
|
Published |
2014-03 |
Edition : 1 |
Number of pages : 29 |
Technical Committee |
35.110
Networking
;
35.200
Interface and interconnection equipment
;
35.240.99
IT applications in other fields
|
| ISO/IEC 29341-1:2008 |
Information technology — UPnP Device Architecture — Part 1: UPnP Device Architecture Version 1.0 |
ISO/IEC 29341-1:2008(E) gives an overall view the device architecture. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 79 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-10-12:2008 |
Information technology — UPnP Device Architecture — Part 10-12: Quality of Service Device Control Protocol - Quality of Service Policy Holder Service |
ISO/IEC 29341-10-12:2008(E) enables modeling of QoS Policy Holder function capabilities. QoS Policy Holder service is responsible for providing the traffic policy values for any given traffic stream as requested by an entitiy that manages home network traffic. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 3324-1:1985 |
Aircraft tyres and rims — Part 1: Specifications |
|
Withdrawn |
1985-10 |
Edition : 2 |
Number of pages : 48 |
Technical Committee |
83.160.20
Aircraft tyres
|
| ISO/IEC 29341-1:2011 |
Information technology — UPnP Device Architecture — Part 1: UPnP Device Architecture Version 1.0 |
ISO/IEC 29341-1:2011(E) Defines UPnP technology which describes an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices, and PCs of all form factors. It is designed to bring easy-to-use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces, or attached to the Internet. UPnP technology provides a distributed, open networking architecture that leverages TCP/IP and the Web technologies to enable seamless proximity networking in addition to control and data transfer among networked devices. The UPnP Device Architecture (UDA) is designed to support zero-configuration, "invisible" networking, and automatic discovery for a breadth of device categories from a wide range of vendors. A device can dynamically join a network, obtain an IP address, convey its capabilities, and learn about the presence and capabilities of other devices. Finally, a device can leave a network smoothly and automatically without leaving any unwanted state behind. The technologies leveraged in the UPnP architecture include Internet protocols such as IP, TCP, UDP, HTTP, and XML. Like the Internet, contracts are based on wire protocols that are declarative, expressed in XML, and communicated via HTTP. This International Standard replaces ISO/IEC 29341-1, first edition, published in 2008, and constitutes a technical revision.
|
Published |
2011-09 |
Edition : 2 |
Number of pages : 60 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-2:2008 |
Information technology — UPnP Device Architecture — Part 2: Basic Device Control Protocol - Basic Device |
ISO/IEC 29341-2:2008(E) provides a mecanism for products that wish to use UPnP, but for which there is not yet an appropriate standard base device type. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 4 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-1-1:2011 |
Information technology — UPnP Device Architecture — Part 1-1: UPnP Device Architecture Version 1.1 |
ISO/IEC 29341-1-1:2011(E) The UPnP Device Architecture (formerly known as the DCP Framework). It defines the protocols for communication between controllers, or control points, and devices. For discovery, description, control, eventing, and presentation, the UPnP Device Architecture uses the following protocol stack:
- UPnP vendor-specific information;
- information defined by UPnP;
- UPnPspecific protocols such as the Simple Service Discovery Protocol (SSDP) the General Event Notification Architecture (GENA) and the multicast event protocol defined in this document, and others that are referenced. SSDP is delivered via either multicast or unicast UDP. Multicast events are delivered via multicast UDP. GENA is delivered via HTTP. Ultimately, all messages above are delivered over IP. The remaining clauses of this document describe the content and format for each of these protocol layers in detail.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 101 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-1-2:2017 |
Information technology — UPnP Device Architecture — Part 1-2: UPnP Device Architecture Version 2.0 |
UPnP Forum has set up working committees in specific areas of domain expertise. These working committees are charged with creating proposed device standards, building sample implementations, and building appropriate test suites. ISO/IEC 29341-1-2:2017 indicates specific technical decisions that are the purview of UPnP Forum working committees.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 180 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-10-10:2008 |
Information technology — UPnP Device Architecture — Part 10-10: Quality of Service Device Control Protocol - Quality of Service Device Service |
ISO/IEC 29341-10-10:2008(E) enables modeling of QoS Device function capabilities. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-10-11:2008 |
Information technology — UPnP Device Architecture — Part 10-11: Quality of Service Device Control Protocol - Quality of Service Manager Service |
ISO/IEC 29341-10-11:2008(E) enables modeling of QoS Manager function capabilities. QoS Manager function is a combination of QoS Manager service and a control point functionality that discovers and controls QoS Device and QoS Policy Holder services running on the network. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO 2258:1976 |
Printing ribbons — Minimum markings to appear on containers |
Lays down rules for facilitating the storage and distribution of printing ribbons on the premises of manufacterers, dealers and users. Specifies the type and form of minimum information to appear on containers used as packaging unit for printing ribbons wound on spools or cores.
|
Published |
1976-08 |
Edition : 2 |
Number of pages : 1 |
Technical Committee |
35.260
Office machines
|
| ISO/IEC 29341-11-10:2008 |
Information technology — UPnP Device Architecture — Part 11-10: Quality of Service Device Control Protocol - Level 2 - Quality of Service Device Service |
ISO/IEC 29341-11-10:2008(E) enables modeling of the QoS Device funtion capabilities. It implements the source sink and intermediate network elements that are in the path of the traffic. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-11-11:2008 |
Information technology — UPnP Device Architecture — Part 11-11: Quality of Service Device Control Protocol - Level 2 - Quality of Service Manager Service |
ISO/IEC 29341-11-11:2008(E) enables modeling of QoS Manager function capabilities. QoS Manager functionality is a combination of QoS Manager service and control point functionality that discovers and controls QoS Device and QoS Policy Holder services running on the network. The QoS Manager function is responsible for requesting, updating, releasing and in general controlling the Quality of Service assigned by networking devices to various traffic streams. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-11-12:2008 |
Information technology — UPnP Device Architecture — Part 11-12: Quality of Service Device Control Protocol - Level 2 - Quality of Service Policy Holder Service |
ISO/IEC 29341-11-12:2008(E) enables modeling of QoS Policy Holder function capabilities. The functionality for the QoS Policy Holder service can be implemented by any device on the home network. The QoS Policy Holder service is responsible for providing the traffic policy values for any given traffic stream as requested by an entity that manages home network traffic, typically a QoS Management Entity. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-11-1:2008 |
Information technology — UPnP Device Architecture — Part 11-1: Quality of Service Device Control Protocol - Level 2 - Quality of Service Architecture |
ISO/IEC 29341-11-1:2008(E) describes prioritized QoS. UPnP QoS architecture defines 3 services. These are the QoS Policy Holder Service, QoS Manager Service and QoS Device Service. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-11-2:2008 |
Information technology — UPnP Device Architecture — Part 11-2: Quality of Service Device Control Protocol - Level 2 - Quality of Service Schemas |
ISO/IEC 29341-11-2:2008(E) defines the schemas referenced in the Quality of Service, Level 2, standards. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-12-10:2008 |
Information technology — UPnP Device Architecture — Part 12-10: Remote User Interface Device Control Protocol - Remote User Interface Client Service |
ISO/IEC 29341-12-10:2008(E) encapsulates the management of an out-of-band remoting protocol connection to a device capable of user interaction. This service is required for all Remote UI clients. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-12-11:2008 |
Information technology — UPnP Device Architecture — Part 12-11: Remote User Interface Device Control Protocol - Remote User Interface Server Service |
ISO/IEC 29341-12-11:2008(E) describes the service which is required by all Remote UI server devices. This service is required for all Remote UI clients. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-12-1:2008 |
Information technology — UPnP Device Architecture — Part 12-1: Remote User Interface Device Control Protocol - Remote User Interface Client Device |
ISO/IEC 29341-12-1:2008(E) encapsulates all services for the Remote UI Client Device Control Protocol. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-12-2:2008 |
Information technology — UPnP Device Architecture — Part 12-2: Remote User Interface Device Control Protocol - Remote User Interface Server Device |
ISO/IEC 29341-12-2:2008(E) encapsulates all services for the Remote UI Server Device Control Protocol. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-13-10:2008 |
Information technology — UPnP Device Architecture — Part 13-10: Device Security Device Control Protocol - Device Security Service |
ISO/IEC 29341-13-10:2008(E) provides the services necessary for strong authentication, authorization, replay prevention and privacy of UPnP SOAP (simple object access protocol) actions. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 84 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-13-11:2008 |
Information technology — UPnP Device Architecture — Part 13-11: Device Security Device Control Protocol - Security Console Service |
ISO/IEC 29341-13-11:2008(E) offers a user interface for administration of access control on security-aware UPnP devices. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.
|
Published |
2008-11 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-14-12:2011 |
Information technology — UPnP Device Architecture — Part 14-12: Audio Video Device Control Protocol — Level 3 — Audio Video Content Directory Service |
ISO/IEC 29341-14-12:2011(E) describes a service template which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as ContentDirectory service. The purpose of the ContentDirectory service is to allow the server device provide a uniform mechanism for UI devices to browse the content on the server and to obtain detailed information about object individual content. The ContentDirectory service additionally provides a lookup/storage service that allows clients to locate (and possibly store) individual objects (for example, songs, movies, pictures, etc) that the (server) device is capable of providing.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 219 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-14-3:2011 |
Information technology — UPnP Device Architecture — Part 14-3: Audio Video Device Control Protocol — Level 3 — Media Server Device |
ISO/IEC 29341-14-3:2011(E) is a device specification compliant with the UPnPTM Device Architecture version 1.0. 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 heScheduledRecording service (refer to the ScheduledRecording service specification). As such, the MediaServer can handle any specific type of media, any data format, and transfer protocol.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-15-10:2011 |
Information technology — UPnP Device Architecture — Part 15-10: Content Synchronization Device Control Protocol — Content Synchronization Service |
ISO/IEC 29341-15-10:2011(E) Describes the Content Synchronization service which enables two or more ContentDirectory services [CDS] to synchronize content with each other. This service also enables a UPnP control point to synchronize content with a ContentDirectory service. We refer this service as "CSS" or "ContentSync service" from hereon. If a CDS wants to support synchronization of objects and its resources with other CDSs, the implementation MUST enable this ContentSync service (CSS). CSS keeps change log as part of CDS object property that describe which CDS objects are added or modified or deleted since it has synchronized last. Since synchronization enables interaction between ContentSync services, each service has a Control Point (CP) functionality that invokes actions to other ContentSync service to achieve synchronization of contents with each other. This service definition is compliant with the UPnP Device Architecture version 1.0.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 90 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-16-10:2011 |
Information technology — UPnP Device Architecture — Part 16-10: Low Power Device Control Protocol — Low Power Proxy Service |
ISO/IEC 29341-16-10:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0.service. This service-type enables modelling of "Basic Power Management Proxy" function capabilities. Basic Power Management Proxy (BPMPX) is a combination of UPnP service and a control point. As Control Point, Proxy discovers and controls Low Power Device services running in the network, and as UPnP Proxy service, it advertises itself to the network, and responds to actions from low power aware Control Point. [LPARCH] Basic functions that BPMPX does are as follows:
- Receive multicast discovery messages from power managed UPnP devices in order to be. aware of their power states (i.e. the BPMPX will act as Control Point).
- Send multicast or unicast discovery messages (i.e. M-SEARCH) to query UPnP devices and keep track of their power states (i.e. the BPMPX will act as Control Point).
- Send GetPowerManagementInfo action to obtain power management mechanism provided by power-aware devices.
- Should send the appropriate wakeup message to the specified sleeping device when it receives WakeupDevice action from power aware Control Point. [LPARCH]. Act as UPnP service.
- Sending BPMPX service announcements and M-Search replies.
- Respond to SearchSleepingDevices action to provide the information of sleeping devices in network.
- Respond to Wakeup action from Control Point. (Wake up action is directed to the low power devices and not for waking up the BPMPX).
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-16-11:2011 |
Information technology — UPnP Device Architecture — Part 16-11: Low Power Device Control Protocol — Low Power Service |
ISO/IEC 29341-16-11:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0.service. This service enables implementation of power saving functionality for UPnP devices.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-16-1:2011 |
Information technology — UPnP Device Architecture — Part 16-1: Low Power Device Control Protocol — Low Power Architecture |
ISO/IEC 29341-16-1:2011(E) defines an architecture that will address the issue of reporting and tracking power states of nodes in a network. The UPnP Low Power solution is designed to enable nodes in the network to report and track the Low Power states of other nodes in the network. Additionally, for nodes that support wake up capabilities, this architecture addresses methods to wake up those nodes when required. The objective of the UPnP Low Power solution is to allow UPnP devices to conserve energy and still be discoverable by UPnP Control Points. The UPnP Control Point will be aware of the UPnP devices and services implemented on a Low Power device even when the Low Power device is in a power savings mode. This architecture document defines two UPnP services that comprise the UPnP Low Power framework: Low Power device service and Basic Power Management Proxy service.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-17-10:2011 |
Information technology — UPnP Device Architecture — Part 17-10: Quality of Service Device Control Protocol — Level 3 — Quality of Service Device Service |
ISO/IEC 29341-17-10:2011(E) describes the service definition which is compliant with the UPnP Device Architecture version 1.0.[DEVICE]. This service-type enables modeling of the 'QosDevice' function capabilities. The QosDevice:3 Service is a function typically implemented in source, sink and intermediate network. The QosDevice Service is responsible for providing the appropriate network resources to traffic streams and information about the state of the device as requested by the QosManager as defined in the QosManager:3 Service.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 99 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-17-11:2011 |
Information technology — UPnP Device Architecture — Part 17-11: Quality of Service Device Control Protocol — Level 3 — Quality of Service Manager Service |
ISO/IEC 29341-17-11:2011(E) describes the service-type that enables modelling of 'Quality of Service Manager' function capabilities. This service provides a mechanism for a Control Point to:
- Be agnostic of the QoS capabilities and associated details about the various QoS Devices on the network at the expense of potential network inefficiency.
- Abstract the tasks of setting up, modifying and revoking the QoS associated with every traffic stream.
- QosManager:3 defines new capabilities to set up Parameterized QoS. Control Points may now request reservations for specific resources for the exclusive use of individual streams. Successful resource reservation ensures that streams will always have the bandwidth and other resources to transport time critical data.
- QosManager:3 defines a method for Control Points to request preemption of existing reservations on the UPnP-QoS network if necessary to admit a new stream.
- QosManager:3 supports a mechanism for providing a list of blocking streams to a Control Point so that it can handle preemption on its own, if desired. This service definition is compliant with the UPnP Device Architecture version 1.0.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 83 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 29341-17-12:2011 |
Information technology — UPnP Device Architecture — Part 17-12: Quality of Service Device Control Protocol — Level 3 — Quality of Service Policy Holder Service |
ISO/IEC 29341-17-12:2011(E) describes the service type that enables modelling of the 'QosPolicyHolder' function capabilities. The functionality for the QosPolicyHolder Service can be implemented by any device on the network. The QosPolicyHolder Service is responsible for providing the traffic policy values for any given traffic stream as requested by an entity that manages the network traffic, typically a QoS Manager. The traffic policy values are determined by applying the policy rules, which are configured for the network, to the requested traffic information. This service definition is compliant with the UPnP Device Architecture version 1.0.
|
Published |
2011-08 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
35.200
Interface and interconnection equipment
|