Esileht»Infoteenus

35 INFOTEHNOLOOGIA

Tagasi peagrupi juurde

Uued standardid


EVS-EN 82304-1:2017
Hind 13,22 EUR
Identne IEC 82304-1:2016; EN 82304-1:2017
Meditsiinitarkvara. Osa 1: Põhinõuded toote ohutusele
IEC 82304-1:2016 applies to the safety and security of health software products designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware, and its primary focus is on the requirements for manufacturers. It covers the entire lifecycle including design, development, validation, installation, maintenance, and disposal of health software products.

EVS-EN 50090-6-1:2017
Hind 15,40 EUR
Identne EN 50090-6-1:2017
Home and Building Electronic Systems (HBES) - Part 6-1: Interfaces - Webservice interface
This European Standard defines a standardized web service based interface between Home and Building HBES Open Communication System and other information technology (IT) systems. The standardized interface is encapsulated in a gateway device, the HBES Gateway, which is able to communicate with both the Home and Building HBES Open Communication System and the connected IT systems. The HBES Gateway implements a set of encoding standards (see 10.2) as well as various message exchange protocols (see 10.3) to enable remote access to the Home and Building HBES Open Communication System via the Internet or another wide area network (WAN). For this purpose, gateway profiles define different implementation levels (see 10.4).

CEN ISO/TS 19844:2017
Hind 42,39 EUR
Health informatics - Identification of medicinal products - Implementation guidelines for data elements and structures for the unique identification and exchange of regulated information on substances (ISO/TS 19844:2016)
ISO/TS 19844:2016 is used in the implementation of ISO 11238. This document defines substances based on their scientific identity (i.e. what they are) rather than on their use or method of production. ISO 11238 provides the conceptual framework for defining Substances and Specified Substances and for assigning unique identifiers in the context of the ISO IDMP standards. ISO 11238 describes general concepts for defining and distinguishing substances and a high level model for the structuring of information for substances. This document provides detailed explanations of each type or grouping of substance information, an element-by-element description for implementation of ISO 11238, and examples for a variety of Substances and Specified Substances. This second edition of the document addresses substances, Groups 1 to 3 of the Specified Substances as defined in ISO 11238 and Annexes A, B, C, D, E, F, G and H. It is anticipated that Specified Substances Group 4, as defined in ISO 11238, will be addressed in a subsequent edition of this document. Some information that would typically fall under Specified Substances Group 4 may be covered in the Annexes of this document. This information, although not defining of either a Substance or a Specified Substance Group 1, may be essential to distinguishing substances. This document addresses the following: Data elements necessary for defining Substances and Specified Substances Groups 1 to 3; The logical use of data elements as defined in ISO 11238; Substances and Specified Substances Groups 1 to 3 business rules for - determining necessary data elements, - distinguishing and defining materials according to ISO 11238, - triggering the assignment of identifiers. ISO/TS 19844:2016 does not address the following: Business processes for data management; Implementation of a specific data information system (e.g. a relational database schema); Normative messaging standards for substances; The maintenance of controlled vocabularies; The specific global identifier system that should be used; Nomenclature standards for substances.

ISO/IEC 14651:2016/Amd 1:2017
Hind 14,94 EUR
ISO/IEC 14651:2016 - Amendment
Amendment to ISO/IEC 14651:2016

ISO/IEC/IEEE 24765:2017
Hind 184,86 EUR
Systems and software engineering -- Vocabulary
ISO/IEC/IEEE 24765:2017 provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. ISO/IEC/IEEE 24765:2017 is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. ISO/IEC/IEEE 24765:2017 includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.
Asendab ISO/IEC/IEEE 24765:2010

ISO/TS 17444-1:2017
Hind 110,17 EUR
Electronic fee collection -- Charging performance -- Part 1: Metrics
ISO/TS 17444-1:2017 defines metrics for the charging performance of electronic fee collection (EFC) systems in terms of the level of errors associated with charging computation. ISO/TS 17444-1:2017 is a toolbox standard of metrics. The detailed choice of metrics depends on the application and the respective context. ISO/TS 17444-1:2017 describes a set of metrics with appropriate definitions, principles and formulations, which together make up a reference framework for the establishment of requirements for EFC systems and their later examination of the charging performance. The charging performance metrics defined in ISO/TS 17444-1:2017 are intended for use with any Charging Scheme, regardless of its technical underpinnings, system architecture, tariff structure, geographical coverage, or organizational model. They are defined to treat technical details that can be different among technologies and vendors or vary over time as a "black box". They focus solely on the outcome of the charging process, i.e. the amount charged in relation to a pre-measured or theoretically correct amount, rather than intermediate variables from various components as sensors, such as positioning accuracy, signal range, or optical resolution. This approach ensures comparable results for each metric in all relevant situations. The metrics are designed to cover the information exchanged on the Front End interface and the interoperability interfaces between Toll Service Providers, Toll Chargers and Road Users as well as on the End-to-End level.
Asendab ISO/TS 17444-1:2012

IEC 62056-6-2:2017
Hind 326,77 EUR
Electricity metering data exchange - The DLMS/COSEM suite - Part 6-2: COSEM interface classes
IEC 62056-6-2:2017 specifies a model of a meter as it is seen through its communication interface(s). Generic building blocks are defined using object-oriented methods, in the form of interface classes to model meters from simple up to very complex functionality. Annexes A to F (informative) provide additional information related to some interface classes. This third edition cancels and replaces the second edition of IEC 62056-6-2 published in 2016. It constitutes a technical revision. The significant technical changes with respect to the previous edition are listed in Annex F(Informative).
Asendab IEC 62056-6-2:2016

ISO 9241-960:2017
Hind 110,17 EUR
Ergonomics of human-system interaction -- Part 960: Framework and guidance for gesture interactions
ISO 9241-960:2017 gives guidance on the selection or creation of the gestures to be used in a gesture interface. It addresses the usability of gestures and provides information on their design, the design process and relevant parameters that are to be considered. In addition, it provides guidance on how gestures should be documented. This document is concerned with gestures expressed by a human and not with the system response generated when users are performing these gestures. NOTE 1 Specific gestures are standardized within ISO/IEC 14754 and the ISO/IEC 30113 series. NOTE 2 Input devices such as tablets or spatial gesture recognition devices can capture gestures in 2D or 3D. All human gestures are 3D.

ISO/IEC 19770-4:2017
Hind 147,51 EUR
Information technology -- IT asset management -- Part 4: Resource utilization measurement
ISO/IEC 19770-4:2017 establishes specifications for an information structure to contain Resource Utilization Measurement information to facilitate IT asset management (ITAM). This document is applicable to all types of organization (for example, commercial enterprises, government agencies, and non-profit organizations).

ISO/IEC 29341-20-1:2017
Hind 128,84 EUR
Information technology -- UPnP Device Architecture -- Part 20-1: Audio video device control protocol -- Level 4 -- Audio video architecture
ISO/IEC 29341-20-1:2017 describes the overall UPnP AV Architecture, which forms the foundation for the UPnP AV Device and Service templates. The AV Architecture defines the general interaction between UPnP control points and UPnP AV devices. It is independent of any particular device type, content format, and transfer protocol. It supports a variety of devices such as TVs, VCRs, CD/DVD players/jukeboxes, settop boxes, stereos systems, MP3 players, still-image cameras, camcorders, electronic picture frames (EPFs), and the PC. The AV Architecture allows devices to support different types of formats for the entertainment content (such as MPEG2, MPEG4, JPEG, MP3, Windows Media Architecture (WMA), bitmaps (BMP), NTSC, PAL, ATSC, etc.) and multiple types of transfer protocols (such as IEC-61883/IEEE-1394, HTTP GET, RTP, HTTP PUT/POST, TCP/IP, etc.). The following clauses describe the AV Architecture and how the various UPnP AV devices and services work together to enable various end-user scenarios.

ISO/IEC 29341-20-4:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 20-4: Audio video device control protocol -- Level 4 -- Datastructure template
ISO/IEC 29341-20-4:2017 defines the layout of the AV Datastructure Template (AVDT) XML document. An AVDT document describes the format requirements and restrictions of various data structures used within the UPnP AV specifications. Although these data structures are defined very precisely in the appropriate service specification, in most cases, each data structure definition allows for a certain degree of variation in order to accommodate differences between individual devices. The purpose of an AVDT document is to enable each device to describe (at run-time) its particular variation of these AV data structures. AVDT documents allow users of AV data structures (e.g. UPnP control points) to reduce the number of instances of those data structures that comply with the service specification but are not compatible with the device's particular capabilities. The ultimate goal of an AVDT document is to reduce those error conditions that are caused by control points creating instances of a data structure that exceed the static (known) capabilities of the device. Unfortunately, the AVDT mechanism will never eliminate all preventable error conditions, but it will help to reduce them by giving the client more information about the device's particular capabilities. As described above, an AVDT document is a machine readable, implementation-specific variant of an AV data structure defined by one of the UPnP AV specifications. For a given device, each instance of that data structure shall conform to both the specification definition and the device's AVDT definition of that data structure. Ironically, an AVDT document is both a more-restrictive and more-permissive variant of the specification definition. AVDT documents are more restrictive because they limit certain aspects of the data structure (e.g. such as the allowed values for each field) that are otherwise permitted by the specification definition. However, due to limitations of the AVDT constructs, it is simply not possible to express some of the more intricate requirements defined by the specification (e.g. subtle interdependencies between data structure fields). Consequently, instances of a data structure that comply with a given AVDT description may not fully comply with all of the requirements defined in the specification. The types of data structures that can be described by an AVDT document represent a (non-hierarchitical) set of named property values. The set of allowed property names and their allowed values for a given data structure are defined by one of the UPnP AV specifications. Individual instances of these data structures are manifested via an XML document whose elements and attributes correspond to the set of named properties. In other words, within the XML document that corresponds to a given instance of a certain data structure, each XML element and attribute contains the value of a specific named property. An AVDT document is conceptually similar to an XML schema in that both entities identify the XML elements and attributes that appear in any given document instance. Additionally, both AVDT documents and XML schemas identify the allowed values that are permitted for each element and/or attribute which corresponds to a specific property. However, unlike an XML schema, an AVDT document can also identify certain dependencies between two or more properties. For example, the set of allowed values of one property may depend on the actual value of another property. This type of interrelationship is difficult to represent using an XML schema. Hence, the AVDTdocument structure is needed. In the various AV Architecture scenarios, sometimes there is a need to exchange device capabilities to ensure high level interoperability. In order to express the parameterized capability, an AV specification defines various templates for each purpose. A device uses the template and populates it with values to reflect its capabilities at run-time. The AV Datastructure Template (AVDT) is a common structure to define various templates, which are called "Datastructure". This is written in XML and each data structure uses a subset of the AVDT to meet the necessary requirement.

ISO/IEC 29341-20-10:2017
Hind 184,86 EUR
Information technology -- UPnP Device Architecture -- Part 20-10: Audio video device control protocol -- Level 4 -- Audio video transport service
ISO/IEC 29341-20-10:2017 is compliant with UPnP Device Architecture version 1.0 [14]. This service type enables control over the transport of audio and video streams. The service type defines a common model for A/V transport control suitable for a generic user interface. It can be used to control a wide variety of disc, tape and solid-state based media devices such as CD players, VCRs and MP3 players. A minimal implementation of this service can be used to control tuners. The service type is related to the ConnectionManager service type, which describes A/V connection setup procedures, and the ContentDirectory service, which offers meta-information about the resource stored on the media. AVTransport also offers an action to retrieve any metadata embedded in the resource itself. This service type does not offer scheduled recording.

ISO/IEC 29341-20-11:2017
Hind 166,18 EUR
Information technology -- UPnP Device Architecture -- Part 20-11: Audio video device control protocol -- Level 4 -- Connection manager service
ISO/IEC 29341-20-11:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. This service-type enables modeling of streaming capabilities of A/V devices, and binding of those capabilities between devices. Each device that is able to send or receive a stream according to the UPnP AV Architecture will have 1 instance of the ConnectionManager service. This service provides a mechanism for control points to: a) Perform capability matching between source/server devices and sink/renderer devices, b) Find information about currently ongoing transfers in the network, c) Setup and teardown connections between devices (when required by the streaming protocol). The ConnectionManager service is generic enough to properly abstract different kinds of streaming mechanisms, such as HTTP-based streaming, RTSP/RTP-based and 1394-based streaming. The ConnectionManager enables control points to abstract from physical media interconnect technology when making connections. The term ?stream' used in this service template refers to both analog and digital data transfer.

ISO/IEC 29341-20-12:2017
Hind 184,86 EUR
Information technology -- UPnP Device Architecture -- Part 20-12: Audio video device control protocol -- Level 4 -- Content directory service
ISO/IEC 29341-20-12:2017 specifies the characteristics of the UPnP networked service named ContentDirectory, version 4. This service definition is compliant with UPnP Device Architecture 1.0 [14]. Many devices within the home network contain various types of content that other devices would like to access (for example, music, videos, still images, etc). As an example, a MediaServer device might contain a significant portion of the homeowner's audio, video, and still-image library. In order for the homeowner to enjoy this content, the homeowner needs to be able to browse the objects stored on the MediaServer, select a specific one, and cause it to be played on an appropriate rendering device (for example, an audio player for music objects, a TV for video content, an Electronic Picture Frame for still-images, etc). For maximum convenience, it is highly desirable to let the homeowner to initiate these operations from a variety of UI devices. In most cases, these UI devices will either be a UI built into the rendering device, or it will be a stand-alone UI device such as a wireless PDA or tablet. In any case, it is unlikely that the homeowner will interact directly with the device containing the content (that is: the homeowner won't have to walk over to the server device). In order to enable this capability, the server device needs to provide a uniform mechanism for UI devices to browse the content on the server and to obtain detailed information about individual content objects. This is the purpose of the ContentDirectory service. The ContentDirectory service additionally provides a lookup/storage service that enables clients (for example, UI devices) to locate (and possibly store) individual objects (for example, songs, movies, pictures, etc) that the (server) device is capable of providing. For example, this service can be used to enumerate a list of songs stored on an MP3 player, a list of still-images comprising various slide-shows, a list of movies stored in a DVD-Jukebox, a list of TV shows currently being broadcast (a.k.a an EPG), a list of songs stored in a CD-Jukebox, a list of programs stored on a PVR (Personal Video Recorder) device, etc. Nearly any type of content can be enumerated via this ContentDirectory service. For devices that contain multiple types of content (for example, MP3, MPEG2, JPEG, etc.), a single instance of the ContentDirectory service can be used to enumerate all objects, regardless of their type.

ISO/IEC 29341-20-13:2017
Hind 184,86 EUR
Information technology -- UPnP Device Architecture -- Part 20-13: Audio video device control protocol -- Level 4 -- Rendering control service
ISO/IEC 29341-20-13:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a service type referred to herein as RenderingControl.

ISO/IEC 29341-20-14:2017
Hind 184,86 EUR
Information technology -- UPnP Device Architecture -- Part 20-14: Audio video device control protocol -- Level 4 -- Scheduled recording service
ISO/IEC 29341-20-14:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a service type referred to herein as ScheduledRecording service. The ScheduledRecording service is a UPnP service that allows control points to schedule the recording of content. Generally, this content is broadcast content, but this specification does not limit itself to broadcast content. This service type enables the following functions: - Create a recordSchedule so that it is added to the list of recordSchedule instances. Each recordSchedule describes user-level recording instructions for the ScheduledRecording service. - Browse a list of recordSchedule instances stored by the ScheduledRecording service. - Delete a recordSchedule so that it is removed from the list of recordSchedule instances. - Browse a list of recordTask instances, stored by the ScheduledRecording service. The ScheduledRecording service may create zero or more recordTask instances for each recordSchedule. A recordTask represents a discrete recording operation of a recordSchedule. - Enable or disable individual recordTask instances. - Enable or disable a recordSchedule. - Receive notifications i ndicating change of recordSchedule or recordTask list. The ScheduledRecording service does not require a dependency on any UPnP services other than a co-located ContentDirectory service, which provides the following functions: - A ContentDirectory service provides channel line-up to allow users to find recordable channels. A control point may use this metadata when creating a recordSchedule on a ScheduledRecording service. - A ContentDirectory service may provide Electronic Program Guide (EPG) features to allow users to find recordable content. A control point may use this metadata when creating a recordSchedule on a ScheduledRecording service. - Contents recorded by the ScheduledRecording service may be exposed by a ContentDirectory service. The architectural relationship among the different concepts, defined by the ScheduledRecording service can be summarized as follows: A ScheduledRecording service owns a flat (that is: non-nested) list of recordSchedule instances, meaning that the ScheduledRecording service may create, destroy, or change recordSchedule instances. A recordSchedule represents user-level instructions to perform recording operations. Generally, a user constructs his instructions to a ScheduledRecording service via a control point that invokes UPnP actions that affect the list of recordSchedule instances. In all cases, the ScheduledRecording service shall be able to describe discrete recording operations for a recordSchedule through a list of associated recordTask instances. A recordTask can only exist with a recordSchedule (that is: never orphaned). Thus when a recordTask is created by the ScheduledRecording service, its lifetime depends on its parent recordSchedule. An individual recordTask can be selectively enabled or disabled. This service template does not address: Implementations where the ScheduledRecording service and its associated ContentDirectory service are not co-located in the same device.

ISO/IEC 29341-20-2:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 20-2: Audio video device control protocol -- Level 4 -- Media renderer device
ISO/IEC 29341-20-2:2017 is compliant with the Universal Plug and Play Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaRenderer. The MediaRenderer specification defines a general-purpose device template that can be used to instantiate any Consumer Electronics (CE) device that is capable of rendering AV content from the home network. It exposes a set of rendering controls in which a control point can control how the specified AV content is rendered. This includes controlling various rendering features such as brightness, contrast, volume, etc. Example instances of a MediaRenderer include traditional devices such as TVs and stereo systems. Some more contemporary examples include digital devices such as MP3 players and Electronic Picture Frames (EPFs). Although most of these examples typically render one specific type of content (for example, a TV typically renders video content), a MediaRenderer is able to support a number of different data formats and transfer protocols. For example, a sophisticated implementation of a TV MediaRenderer could also support MP3 data so that its speakers could be used to play MP3 audio content. The MediaRenderer device specification is very lightweight and is easy to implement on low-resource devices such as an MP3 player. However, it can also be used to expose the high-end capabilities of devices such as a PC.

ISO/IEC 29341-20-3:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 20-3: Audio video device control protocol -- Level 4 -- Media server device
ISO/IEC 29341-20-3:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaServer. The MediaServer specification defines a general-purpose device that can be used to instantiate any Consumer Electronics (CE) device that provides AV content (for example, media) to other UPnP devices on the home network. It is based on the UPnP AV Architecture Framework (described in another document). It exposes its content via the ContentDirectory service (refer to the ContentDirectory service specification for details). The MediaServer may also provide functionality to record content using the ScheduledRecording service (refer to the ScheduledRecording service specification). As such, the MediaServer can handle any specific type of media, any data format, and transfer protocol. Example instances of a MediaServer include traditional devices such as VCRs, CD Players, DVD Players, audio-tape players, still-image cameras, camcorders, radios, TV Tuners, and set-top boxes. Additional examples of a MediaServer also include new digital devices such as MP3 servers, PVRs, smartphones and Home MediaServers such as the PC. Although these devices contain diverse (AV) content in one form or another, the MediaServer (via the ContentDirectory service) is able to expose this content to the home network in a uniform and consistent manner. This ability allows the MediaServer to instantiate traditional single-function devices as well as more recent multi-function devices such as VCR-DVD players and the general purpose Home MediaServer, which contains a wide variety of content such as MPEG2 video, CD audio, MP3 and/or WMA audio, JPEG images, etc. The MediaServer specification is very lightweight and can easily be implemented on low-resource devices such as still-image cameras or MP3 players that want to expose their local content to the home network. The MediaServer can also be used for high-end Home MediaServers that contain dozens of Gigabytes of heterogeneous content. Refer to the Theory Of Operation subclause for some specific examples of the MediaServer.

ISO/IEC 29341-24-1:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 24-1: Internet gateway device control protocol -- Level 2 -- Internet gateway device
ISO/IEC 29341-24-1:2017 specifies the characteristics of a device that manages connectivity to the Internet as an "edge" device between a residential Local Area Network and a Wide Area Network. The gateway can be physically implemented as a standalone device, or logically as a set of UPnP devices and services on a PC. This specified device is intended to be controlled from inside the home network. Control from outside the home network typically requires access control mechanisms that are outside the scope of this document. This specified device is also not intended for use with small business networks. ISO/IEC 29341-24-1:2017 defines version 2 of the device named InternetGatewayDevice. It is a UPnP root device, and is identified by the UPnP device type InternetGatewayDevice:2. It is compliant with the UPnP Device Architecture, Versions 1.0 and 1.1 ([15] and [16], respectively). InternetGatewayDevice:2 encapsulates several sub-devices and services that collectively comprise the Internet Gateway Device Control Protocol (DCP).

ISO/IEC 29341-24-2:2017
Hind 54,15 EUR
Information technology -- UPnP Device Architecture -- Part 24-2: Internet gateway device control protocol -- Level 2 -- Wide area network connection device
ISO/IEC 29341-24-2:2017 specifies the characteristics of the UPnP networked device named WANConnectionDevice, version 2. This device definition is compliant with UPnP Device Architecture 1.0 [14] and UPnP Device Architecture 1.1 [15].

ISO/IEC 29341-24-3:2017
Hind 54,15 EUR
Information technology -- UPnP Device Architecture -- Part 24-3: Internet gateway device control protocol -- Level 2 -- Wide area network device
ISO/IEC 29341-24-3:2017 specifies the characteristics of a UPnP embedded virtual device that models a physical Wide Area Network interface on an Internet gateway. This specification describes version 2 of the device named WANDevice (WANDevice:2). WANDevice:2 also enables the control of the WAN interface, and is a required device in the UPnP Internet Gateway Device Control Protocol (as specified in [1]).

ISO/IEC 29341-24-10:2017
Hind 166,18 EUR
Information technology -- UPnP Device Architecture -- Part 24-10: Internet gateway device control protocol -- Level 2 -- Wide area network internet protocol -- Connection service
ISO/IEC 29341-24-10:2017 specifies the characteristics of the UPnP networked service named WANIPConnection, version 2. This service definition is compliant with UPnP Device Architecture 1.0 [1] . It is one component of the Device Control Protocol for the UPnP Internet Gateway Device (see [3]). This service enables a UPnP control point to: - configure and control an IP connection between a LAN client on one side of an Internet gateway (see [3]) and a WAN host on the other side; - manage any physical WAN interface?such as DSL or cable?that supports an IP connection. This service is a required in a WANConnectionDevice (see [5]) when the device supports an IP connection.

ISO/IEC 29341-24-11:2017
Hind 128,84 EUR
Information technology -- UPnP Device Architecture -- Part 24-11: Internet gateway device control protocol -- Level 2 -- Wide area network internet protocol v6 -- Firewall control service
ISO/IEC 29341-24-11:2017 specifies the characteristics of the UPnP networked service named WANIPv6FirewallControl, version 1. This service definition is compliant with UPnP Service Architecture 1.0 [1]. This service supports the management IPv6 firewall pinholes in Internet gateway devices independent of the WAN access type (PPP, DHCP, ?). It also supports access control to restrict operations to authorized control points and users. It enables UPnP control points to: - create and delete pinholes of limited duration that allow external communication from the WAN side of the gateway to reach devices on the LAN side - determine operational status of a pinhole This service does not support: - retrieving detailed information about pinholes (such as associated external port or remaining lease duration) - outbound packet filtering - modification of security policies of a gateway device

ISO/IEC 29341-26-1:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 26-1: Telephony device control protocol -- Level 2 -- Telephony architecture
ISO/IEC 29341-26-1:2017 describes an architecture that allows UPnP Telephony devices, services and control points defined in the propoded DCP to be deployed in the home network environment and to enable management of incoming and outgoing telephony calls, messaging, presence information and phone features configuration through UPnP means from devices within the home. In order to accommodate the above mentioned goals, the Telephony Architecture defines several UPnP devices and services that can be embedded to the devices defined for telephony. The architecture model describes interaction among the telephony devices, services and control points. The architecture also describes various deployment scenarios. The architecture does not describe any interfaces to "service" gateways that will enable non-UPnP entities to interact with the UPnP devices, services and control points physically attached to the home network.

ISO/IEC 29341-26-2:2017
Hind 54,15 EUR
Information technology -- UPnP Device Architecture -- Part 26-2: Telephony device control protocol -- Level 2 -- Telephony client device
ISO/IEC 29341-26-2:2017 defines a device type named TelephonyClient, that complies with [1]. The TelephonyClient device is a UPnP device that allows control points to exploit a set of telephony features such as management of media session with a telephony server, messaging, presence etc via UPnP though other UPnP enabled home network devices. This device provides control points with the following functionality: - Managing media session with a telephony server including setting up and terminating of media session with a telephony server. - Messaging features including sending and retrieving messages and notifications of incoming messages. - Enabling user friendly input capability.

ISO/IEC 29341-26-3:2017
Hind 54,15 EUR
Information technology -- UPnP Device Architecture -- Part 26-3: Telephony device control protocol -- Level 2 -- Telephony server device
ISO/IEC 29341-26-3:2017 defines a device type named TelephonyServer that complies with [1]. The TelephonyServer device is a UPnP device that allows control points to exploit a set of telephony features such as managing telephony calls, messaging, presence etc via UPnP though other UPnP enabled home network devices. This device provides control points with the following functionality: - Managing telephony calls including initiation of a call, rejection of a call, acceptance and mofications of a call. - Messaging features including sending and retrieving messages and notifications of incoming messages. - Enabling user friendly input capability. - Configuring of the Telephony Server via phone data model.

ISO/IEC 29341-26-10:2017
Hind 184,86 EUR
Information technology -- UPnP Device Architecture -- Part 26-10: Telephony device control protocol -- Level 2 -- Call management service
ISO/IEC 29341-26-10:2017 is compliant with [1]. It defines a service type referred to herein as the CallManagement service. The CallManagement service is a UPnP service that allows control points to use the telephony features(e.g., voice call, video call, and data transfer etc.) provided by a Telephony Server (TS). The CallManagement service enables the following features to a Telephony Control Point (TelCP): - start an outgoing call - accept an incoming call - modify the capability of an existing call (e.g., changing from a voice call to a video call) - terminate a call - preview call logs - register a call back and check the availability of the registered call back To realize these features, the CallManagement service manages the connectivity of calls and media streams.

ISO/IEC 29341-26-11:2017
Hind 184,86 EUR
Information technology -- UPnP Device Architecture -- Part 26-11: Telephony device control protocol -- Level 2 -- Media management service
ISO/IEC 29341-26-11:2017 is compliant with [1]. It defines a service type referred to herein as the MediaManagement service. The MediaManagement service enables the feature to set-up a media session on a Telephony Client (TC), under the control of a Telephony Control Point (TelCP). This service provides the following functions: - Set up a media session to send and/or receive media streams between a TC and a TS. To set up a media session, The MediaManagement service provides an interface for a TelCP to negotiate the media capabilities (e.g., codec types, IP address, port number etc.) between a TC and a TS. This ensures a TelCP to select a common set of the media capabilities to be used to send and/or receive media streams between a TS and a TC. After the media session is established, the TC starts sending and/or receiving media streams based on the media chapabilities negotiated between the TC and the TS. - The mechanism to modify the media capabilities of an existing media session. For instance, if a media session is created for sending and receiving an audio media stream, it is possible to modify the media session for sending and receiving a video media stream. - The mechanism to terminate a media session.

ISO/IEC 29341-26-12:2017
Hind 166,18 EUR
Information technology -- UPnP Device Architecture -- Part 26-12: Telephony device control protocol -- Level 2 -- Messaging service
ISO/IEC 29341-26-12:2017 is compliant with [1]. It defines a service type referred to herein as Messaging service. The Messaging service is a UPnP service that allows control points to use the messaging features provided by a Telephony Server (TS) or a Telephony Client (TC). It provides in the UPnP network the overall set of messaging capabilities of a phone (e.g., smartphone, IP phone, VoIP gateway, etc.), as the role of a TS. Additionally, or as an alternative, a device with the role of a TC can provide the Messaging service via UPnP Telephony. This service provides the control points with the following functionalities: - Page Mode Messaging (e.g., e-Mail, SMS, MMS, etc.): notification of incoming messages, reading messages, sending a message, deleting a message. - Session Mode Messaging (e.g., Instant Messaging, SMS, etc.): notification of incoming messages, retrieving and sending the messages within a session, creating, modifying or closing a messaging session. - File transfer session, to transfer the files in near real time. This service does not provide the following functionalities: - Connection to a remote server for sending or receiving the messages (e.g., WAN side); - Rendering of message notifications and messages to the end user; - Configuring the Messaging service with account for connecting to remote servers;

ISO/IEC 29341-26-13:2017
Hind 166,18 EUR
Information technology -- UPnP Device Architecture -- Part 26-13: Telephony device control protocol -- Level 2 -- Phone management service
ISO/IEC 29341-26-13:2017 specifies the PhoneManagement profile of the ConfigurationManagement Service defined in [7]. The PhoneManagement profile can be used for managing the configuration of the UPnP TelephonyServer device (i.e. a telephone), with tasks such as managing an address book, configuring the settings of the phone, configuring the ringing modes, checking the battery level of the phone. This profile is compliant with the UPnP Telephony Architecture defined in [9]. PhoneManagement defines - A profile of the CMS in order to satisfy the requirements for PhoneManagement (see clause 5). - The Phone Data Model to perform configuration management of the specific features of a phone (see Annex A) by reusing the CMS data model (see [7], Annex B). The ConfigurationManagement service offers a general purpose data model and a set of configuration management operations for retrieving and managing the actual configuration parameters of a device. These features are completely reused from CMS in the PhoneManagement. The ConfigurationManagement service defines the functions for manipulating the configuration and status parameters that are exposed by the device hosting the ConfigurationManagement service. These actions and state variables defined in the ConfigurationManagement service are reused in order to manage the configuration parameters of a TelephonyServer device for e.g. phone, defined in the data model of the PhoneManagement. The main goal of this specification is to define the data model (called herein as Phone Data Model) for the TelephonyServer device like Phone, according to the rules defined by the ConfigurationManagement service for defining a new data model. The Phone Data Model is organized as a hierarchical tree of parameter sets, where each set represent a feature of a TelephonyServer (e.g. address book, ringing modes etc) that can be managed by a TelCP.

ISO/IEC 29341-26-14:2017
Hind 128,84 EUR
Information technology -- UPnP Device Architecture -- Part 26-14: Telephony device control protocol -- Level 2 -- Address book service
ISO/IEC 29341-26-14:2017 is compliant [1]. It defines a service type referred to herein as AddressBook. This service provides the following functionalities: - Managing the network address book: accessing the network address book, adding new contact information in the network address book, synchronizing the local address book of Telephony Server with the network address book etc. - Contact Share: sharing the local/network address book's contact information with other contacts of the user. - Personal Contact Card: enabling mangement of his/her own contact information and sharing his own information with his/her contacts. - Contact Invitation; allow handling of the Contact Invitation from the remote party. This service does not provide the following functionalities: Interaction between Telephony Server and the network address book.

ISO/IEC 29341-26-15:2017
Hind 147,51 EUR
Information technology -- UPnP Device Architecture -- Part 26-15: Telephony device control protocol -- Level 2 -- Calendar service
ISO/IEC 29341-26-15:2017 is compliant with [1]. It defines a service type referred to herein as Calendar. This service provides the following functionalities: - Manage the family calendar events and share calendar events between the family members. - Calendar events includes Reminders/Alarms/Free-BusyTime. - Synchronizing the local calendar events with family calendar. - Registrating for receiving the events notification on WAN side using any kinds of messaging service mechanism. - Memo handling : Posting simple memos, retrieveing memos. - Registrating for receiving the memo notifications on the WAN side using any kind of messaging service. This service does not provide the following functionalities: - Interaction between Telephony Server and network side calendar service

ISO/IEC 29341-26-16:2017
Hind 128,84 EUR
Information technology -- UPnP Device Architecture -- Part 26-16: Telephony device control protocol -- Level 2 -- Presence service
ISO/IEC 29341-26-16:2017 is compliant with the [1]. It defines a service type referred to herein as Presence service. The Presence service is a UPnP service that allows control points, or better known as Telephony Control Points (TelCP), to manage presence information through a Telephony Server (TS) device or a Telephony Client (TC) device (in the role of UPnP server device for Presence service). This service provides control points with the following functionality: - Presence of contacts, access the presence information of contacts, as provided by the UPnP Telephony Server device. Contacts referenced by the Presence service may be managed via PhoneManagement service and the Phone Data Model. - Managing presence information, update the presence status stored in the TS; This service does not provide the following functionality: - To update the presence status of the local UPnP network, from the UPnP server device to remote presence servers (i.e. outside the local UPnP network). - To retrieve the presence information of contacts from remote presence servers (i.e. outside the local UPnP network). When the features provided by the Presence service are associated to the PhoneManagement features, then an integrated management of the address book and the presence of contacts in the address book can be delivered.

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

ISO/IEC 29341-28-1:2017
Hind 54,15 EUR
Information technology -- UPnP Device Architecture -- Part 28-1: Multiscreen device control protocol -- Multiscreen architecture
Today multi-screen/second-screen solutions are proliferating. However, each is a proprietary vertical for particular vendor(s). Therefore users expectations aren't being met: - Seamless interoperability across vendors. - Ability for second screen integrated usages rather than 100s of different apps. The UPnP Multi-Screen Device Control Protocols (DCPs) provide an open interface to enable this interoperability between devices and applications, i.e. enable time-sensitive and interactive services, including implementation-specific applications, among various display devices. ISO/IEC 29341-28-1:2017 describes the overall Multi-Screen Architecture, which forms the foundation for the UPnP Multi-Screen Device and Service templates. The Multi-Screen Architecture defines the general interaction between UPnP control points and UPnP devices defined by the UPnP Multi-Screen DCPs.

ISO/IEC 29341-28-2:2017
Hind 35,48 EUR
Information technology -- UPnP Device Architecture -- Part 28-2: Multiscreen device control protocol -- Screen device
ISO/IEC 29341-28-2:2017 defines a device type referred to as ScreenDevice version 1. This device specification is compliant with UPnP Device Architecture 1.0 [1]. The ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-Screen Architecture:1 [2] for details.

ISO/IEC 29341-28-10:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 28-10: Multiscreen device control protocol -- Application management service
ISO/IEC 29341-28-10:2017 specifies the characteristics of the UPnP networked service named ApplicationManagement, version 1. This service definition is compliant with UPnP Device Architecture 1.0 [1]. This service type enables to manage applications and the communications between applications providing various time-sensitive and interactive services including implementation-specific applications among various display devices, that is, Screen Devices [3] and Screen Control Points. Screen Devices shall implement this service [3], but this service is allowed to be implemented for any UPnP devices as an add-on service.

ISO/IEC 29341-29-2:2017
Hind 35,48 EUR
Information technology -- UPnP Device Architecture -- Part 29-2: Multiscreen device control protocol -- Level 2 -- Screen device
ISO/IEC 29341-29-2:2017 defines a device type referred to as ScreenDevice version 2. This device specification is compliant with UPnP Device Architecture 1.0 [1]. ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-Screen Architecture:1 [2] for details.

ISO/IEC 29341-29-10:2017
Hind 128,84 EUR
Information technology -- UPnP Device Architecture -- Part 29-10: Multiscreen device control protocol -- Level 2 -- Application management service
ISO/IEC 29341-29-10:2017 specifies the characteristics of the UPnP networked service named ApplicationManagement, version 2. This service definition is compliant with UPnP Device Architecture 1.0 [1]. This service type enables to manage applications and the communications between applications providing various time-sensitive and interactive services including implementation-specific applications among various display devices, that is, Screen Devices [3] and Screen Control Points.. Screen Devices shall implement this service [3], but this service is allowed to be implemented for any UPnP devices as an add-on service.

ISO/IEC 29341-31-1:2017
Hind 110,17 EUR
Information technology -- UPnP Device Architecture -- Part 31-1: Energy management device control protocol -- Energy management service
ISO/IEC 29341-31-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type named EnergyManagement service. It is scoped to any UPnP Device that needs to convey energy management functionality available for the UPnP Device and its services.

Asendatud või tühistatud standardid


CEN ISO/TS 19844:2015
Health informatics - Identification of medicinal products - Implementation guidelines for data elements and structures for the unique identification and exchange of regulated information on substances (ISO/TS 19844:2015)
This Technical Specification is used in the implementation of ISO 11238. This Technical Specification defines substances based on their scientific identity (i.e. what they are) rather than on their use or method of production. ISO 11238 provides the conceptual framework for defining substances and specified substances and for assigning unique identifiers in the context of the ISO IDMP standards. ISO 11238 describes general concepts for defining and distinguishing substances and a high level model for the structuring of information for substances. This Technical Specification provides detailed explanations of each type or grouping of substance information, an element-byelement description for implementation of ISO 11238, and examples for a variety of substances and specified substances. This first edition of the Technical Specification will only address substances, and Groups 1 to 3 of the specified substances as defined in ISO 11238 and Annexes A, B, C, and D. It is anticipated that specified substances Group 4, as defined in ISO 11238, will be addressed in a subsequent edition of this Technical Specification. Some information that would typically fall under specified substances Group 4 may be covered in the Annexes of this Technical Specification. This information, although not defining of either a substance or a specified substance Group 1, may be essential to distinguishing substances.
Keel: Inglise

Kavandite arvamusküsitlus


prEN ISO 19146
Identne ISO/DIS 19146; prEN ISO 19146
Tähtaeg 18.11.2017
Geographic information - Cross-domain vocabularies (ISO/DIS 19146:2017)
This document establishes a methodology for cross-mapping vocabularies. It also specifies an implementation of ISO 19135-1:2015 Geographic information — Procedures for item registration – Part 1: Fundamentals for the purpose of registering cross-mapped vocabulary entries. Methodologies for the development of ontologies and taxonomies that relate to geographic information and geomatics are not within the scope of this document.
Keel: Inglise

prEN 62680-1-2:2017
Identne IEC 62680-1-2:201X; prEN 62680-1-2:2017
Tähtaeg 18.11.2017
Universal Serial Bus interfaces for data and power - Part 1-2: Common components - USB Power Delivery Specification
This specification is intended as an extension to the existing [USB 2.0], [USB 3.1], [USB Type-C 1.2] and [USBBC 1.2] specifications. It addresses only the elements required to implement USB Power Delivery. It is targeted at power supply vendors, manufacturers of [USB 2.0], [USB 3.1], [USB Type-C 1.2] and [USBBC 1.2] Platforms, Devices and cable assemblies. Normative information is provided to allow interoperability of components designed to this specification. Informative information, when provided, may illustrate possible design implementation.
Keel: Inglise

EN 62657-2:2017/prA1:2017
Identne IEC 62657-2:2017/A1:201X; EN 62657-2:2017/prA1:2017
Tähtaeg 18.11.2017
Industrial communication networks - Wireless communication networks - Part 2: Coexistence management
Amendment for EN 62657-2:2017
Keel: Inglise