Informationsteknik, kontorsutrustning

Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal basic electrocardiograph (ECG) devices and managers (e.g. cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability is established in ISO/IEEE11073-10406:2012. Appropriate portions of existing standards including ISO/IEEE 11073 terminology and IEEE 11073-20601 information models are leveraged. The use of specific term codes, formats and behaviours in telehealth environments restricting optionality in base frameworks in favour of interoperability is specified. A common core of communication functionality for personal telehealth basic ECG (1- to 3-lead ECG) devices is defined. Monitoring ECG devices are distinguished from diagnostic ECG equipment with respect to support for wearable ECG devices, limiting the number of leads supported by the equipment to three, and not requiring the capability of annotating or analysing the detected electrical activity to determine known cardiac phenomena. ISO/IEEE 11073-10406:2012 is consistent with the base framework and allows multifunction implementations by following multiple device specializations (e.g. ECG and respiration rate).

This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services and re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of their content and syntax. The data structures are specified as communications-agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.

This document specifies:

—   the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;

—   an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.:

—  charging-related data (toll declarations, billing details, payment claims, payment announcements),

—  administrative data (trust objects, EFC context data, etc.), and

—  confirmation data;

—   transfer mechanisms and supporting functions;

—   information objects, data syntax and semantics.

This document is applicable for any vehicle-related toll service and any technology used for charging.

The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.

This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).

This document does not specify, amongst others:

—   any communication between TC or TSP with any other involved party;

—   any communication between elements of the TC and the TSP that is not part of the back-office communication;

—   interfaces for EFC systems for public transport;

—   any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges;

—   processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;

—   definitions of service communication channels, protocols and service primitives to transfer the APDU.

Amendment

1  Scope

Replace the last paragraph with the following text (in which “any complex transfers (transactions), i.e. 

sequences of inter-related ADUs that can possibly involve several APDU exchanges has been removed”):

This document does not specify, amongst others:

— any communication between TC or TSP with any other involved party;

— any communication between elements of the TC and the TSP that is not part of the back-office 

communication;

— interfaces for EFC systems for public transport;

— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;

— definitions of service communication channels, protocols and service primitives to transfer the APDU.

This document specifies methodologies for measuring the performance of AI models for classification, regression, clustering and recommendation tasks.

This document specifies the test method and performance metrics to evaluate the behaviour of a vehicle equipped with rear cross traffic alerting system during several collision scenarios. These collisions occur during straight-line reverse manoeuvres when the vehicle under test (VUT) approaches other vehicles or traffic participants.

This document applies to M1 category vehicles.

Note: Depending on accidentology, only a part of the scenarios can be used for an evaluation of performance.

This document specifies the test method and performance metrics to evaluate the behaviour of a vehicle equipped with rear cross traffic alerting system during several collision scenarios. These collisions occur during straight-line reverse manoeuvres when the vehicle under test (VUT) approaches other vehicles or traffic participants.

This document applies to M1 category vehicles.

Note: Depending on accidentology, only a part of the scenarios can be used for an evaluation of performance.

This document specifies additional requirements to ISO/IEC 17021-1. The requirements contained in this document, when implemented, support the demonstration of competence, consistency and reliability by the bodies performing auditing and certification of an artificial intelligence management system (AIMS) according to ISO/IEC 42001 for organizations that provide, develop or use AI systems. Certification of AIMS is a third-party conformity assessment activity (as described in ISO/IEC 17000:2020, 4.5), and bodies performing this activity are third-party conformity assessment bodies. This document also provides the necessary information and confidence to customers about the way certification has been granted. NOTE This document can be used as a criteria document for accreditation or peer assessment.