IT-tillämpningar

This International Standard provides a description of the primary services that have been internationally defined to promote consistency among implementations; implementations can provide any of these services in combination with any other services that are appropriate. This document
organizes ITS services by defining service groups, which are placed into one of several service domains.
Each service group contains one or more individual services, each of which is described.
This International Standard is intended for use by at least two groups of people involved in the ITS sector. The first group is those looking for ideas about the services that ITS implementations can provide and the second is those who are developing standards.
For the first group, this International Standard provides service descriptions that can act as the catalyst for more detailed descriptions. The level of detail can differ from one ITS implementation to another, depending on whether or not a national ITS architecture is involved, and whether this architecture
is based directly on services, or on groups of functions. The service descriptions in this standard are pitched at a high-level as too much detail can be prescriptive and reduces flexibility.
For standards developers, this International Standard is applicable to the working groups of ISO TC204 and other Technical Committees who are developing standards for the ITS sector. This International Standard is designed to provide information and explanation of services that can form the basis and reason for developing standards.
Due to its nature, this document is largely advisory and informative with minimal requirements. It is designed to assist the integration of services into a cohesive reference architecture, thereby promoting interoperability and the use of common data definitions. Specifically, services defined within the
service groups can be the basis for definition of 'use cases', 'user needs' or "user service requirements' depending on the methodology being used to develop the resultant ITS architecture functionality, along with definition of applicable data within data dictionaries, as well as applicable communications and data exchange standards.

I detta dokument:
— beskrivs det svenska adressystemet för belägenhetsadresser,
— anges krav och rekommendationer för den geografiska indelning som svenska kommuner utgår ifrån vid adressättning av platser,
— beskrivs hur en adress är uppbyggd och regler för adresskomponenter i belägenhetsadresser för gatuadresser, byadresser, gårdsadresser och metertalsadresser.
Detta dokument omfattar inte interna hänvisningar i en byggnad eller inom en anläggning

This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.
Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.
Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client.

This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.
Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.
Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client.

This document specifies the security characteristics for secure cryptographic devices (SCDs) based on the cryptographic processes defined in ISO 9564, ISO 16609, and ISO 11568.
This document:
— states the security characteristics concerning both the operational characteristics of SCDs and the management of such devices throughout all stages of their life cycle;
— provides guidance for methodologies to verify compliance with those requirements. This information is contained in Annex A.
Annex A provides an informative illustration of the concepts of security levels described in this document as being applicable to SCDs.
This document does not address issues arising from the denial of service of an SCD.
This document does not address software services that use Multi-Party Computation (MPC) to achieve some security objectives and relying on these, offer cryptographic services. These are sometimes called
‘soft’ or software HSMs in common language, which is misleading and is not correct according to this document, which defines an HSM as a physical device with the properties and security measures noted in this document.
NOTE ISO 13491-2 specifies checklists to be used to evaluate secure cryptographic devices (SCDs) incorporating cryptographic processes as specified in ISO 9564-1, ISO 9564-2, ISO 16609, ISO 11568 in the financial services environment. The checklists in ISO 13491-2 specify requirements for the security characteristics and management of specific types of SCD functionality and the environments into which SCDs may be deployed.

The ISO 15638 series (Parts 1 to 24) define the framework for online fleet management of regulated/ unregulated commercial freight vehicles utilizing data communication between in-vehicle systems and an application service provider via an on-board communication unit interfacing with road monitoring
infrastructure and roadside sensors. This document defines an unregulated service architecture framework for freight vehicle safety information provision architecture. This statement does not preclude the regulated service where jurisdiction requires such a function.
The objective of this document is to provide a freight vehicle safety information provision service function/application for non-enforcement applications [and sometimes for regulated application service (RAS)]. This is for the road transport safety management purposes of regulated commercial
freight vehicle movements.
This document intends to reinforce vehicle safety for non-enforcement and other purposes by providing safety advisory information of overhead clearance provisions to the freight vehicle drivers/operators transporting heavy goods on the freight vehicles.
This document defines the framework for remote vehicle safety information provision for nonenforcement and other management purpose applications conceptual operation.
This document is complementary to, and does not replace, any other documents in the ISO 15638 series.
This document is beneficial to vehicle safety management purpose entities, and it provides additional use cases for TARV service applications.
This document is specifically oriented towards the realization of safer road transport of freight vehicles by providing safety advisory information to the vehicle from the service provider. It utilizes the ISO 15638 series basic architecture framework defined in ISO 15638-21. The service provider provides users with safety information of overhead clearance for that vehicle and gives adequate safety advice messages, as necessary. The various V2X communication paths can be used according to the various use cases.

This document forms Part 1 of the 23793 series addressing the minimum requirements for minimal risk manoeuvres (MRM), which are the response of an ADS to perform automated fallback to reach a minimal risk condition (MRC).
This document contains the classification framework for all type of MRMs. The classification framework establishes the concept of MRM operation, classification of different MRM types, and basic principles of the decision-making process to decide which MRM type may be performed based on the situation.
This document also contains the minimum requirements of the control strategy and test procedures for the two simplest types: Straight Stop for type1 and In-lane Stop for type2.
The scope of the MRM described in this document covers minimum requirements for ADS performance during MRM action, from initiation to termination, which aims to achieve an MRC. MRM action-specific
safety requirements for robust system design, such as what is specified in ISO 26262[4] and ISO 21448,[5] are not within the scope of this standard.
The MRM described in this standard are intended to be used on light-duty vehicles equipped with Level 3-5 ADS.
The scope does not include methods for detecting ADS failures and the decision-making process to initiate an MRM. This is because there are numerous cases that can initiate MRMs, and there is no general agreement on classification of those cases in the industry.

This standard defines the identification, data, information services, application guidance aspects, and applicable requirements of AIDC technology for different items and their hierarchy in Industrial
Construction during their whole life-cycle. It:
— provides unique identification for items in Industrial construction.
— specifies the semantics and data syntax to be used.
— specifies the data carriers to be used on items of various categories, substitutes, and sizes.
— makes recommendations about the metadata of the items.
— specifies the application test method and parameters based on the large scale test and scientific sampling rules.
— define the information services protocol to be used as interface between business applications and the AIDC system.
— makes guidance for designers, workers, engineers, managers, end users and maintainers about the AIDC application in their daily work.

This document provides information and specifications enabling management of road traffic in controlled zones (CZ) by applying geofencing. Specifically, this document provides
— a “Controlled Zone Data Dictionary” (CZDD) for management of controlled zones providing an extendible toolkit that regulators can use e.g. to inform potential CZ users, e.g. vehicles, about
— the CZ area, i.e. the geographical boundaries of the CZ;
— CZ access conditions including exemptions;
— time windows indicating when these CZ access conditions are applicable,
allowing the potential CZ users to select an appropriate routing, either by pre-trip planning or ad hoc re-routing,
— and illustrations and guidelines on how to use this toolkit.
The toolkit is designed in compliance with the general ITS station and communications architecture specified in ISO 21217, and optionally applicable C-ITS protocols and procedures, e.g., ISO 22418 on
“Service Announcement”, ISO 18750 on the “Local Dynamic Map”, and ISO 17419 on globally unique identifiers. Cybersecurity provision can be provided by complying to ISO 21177.
Enforcement is out of scope of this document.

This document defines a technical solution for encrypting resources in digital publications (especially EPUB1)), effectively registering a device certificate to providers and securely delivering decryption keys to reading systems included in licenses tailored to specific devices. This technical solution uses
the passphrase-based authentication method defined in ISO/IEC 23078-2 for reading systems to receive the license and access the encrypted resources of such digital publications.

This part of the ISO 28005 series defines the principles and methods for message exchanges between ships, ships' representatives, and shore parties, using this series of standards. This includes the
definition of message structure, including how the data content is assembled from other parts of the ISO 28005 series, and how digital signatures for authentication, integrity and confidentiality of the message shall be used. It also includes specification of basic message exchange patterns and the
responsibilities of each party in the message exchange. Furthermore, it specifies how more specific message implementation guides (MIG) shall be provided for each type of communication application.
Examples of the latter for the maritime single window (MSW) and for mandatory ship reporting systems (MRS) are included in annexes. The specifications in this part are conformant to the requirements in ISO 23807 and uses message exchange and party definitions from IMO FAL.5/Circ.46.

This document provides rules and guidelines for the use of a conceptual schema language within the context of modelling geographic information. The chosen conceptual schema language is the Unified Modeling Language (UML).
This document defines a UML profile for modelling geographic information.
This document defines a set of core data types for use in conceptual schemas.
The standardization target type of this document is conceptual schemas describing geographic information.

This document establishes
— terms and definitions for quantifying finger image quality,
— methods used to quantify the quality of finger images, and
— standardized encoding of finger image quality,
for finger images at 196,85 px/cm spatial sampling rate and a bit depth of 8 bit for the greyscale pixel intensity values scanned or captured using optical area sensors in direct contact with friction ridges.

This part of ISO/IEC 19795 establishes requirements for estimating and reporting of performance variations observed when cohorts belonging to different demographic groups engage with biometric enrolment and recognition systems. Performance in this context refers to failure to enrol and acquire rates, shifts in comparison score, recognition error rates, and aspects of response and processing time (throughput).
Additionally, this part of ISO/IEC 19795 is applicable to the following:
— demographic group membership,
— using phenotypic measures,
— terms and definitions to be used when reporting performance variation across demographic groups,
— reporting of tests,
— stating statistical uncertainty estimates,
— operational thresholds settings,
— equitability, and
— procurement agency activities.
This part of ISO/IEC 19795 is applicable to technology tests of algorithms, subsystems, and systems;
scenario tests of systems; and operational tests of fielded systems. Application of this part of ISO/IEC 19795 does not require detailed knowledge of the system’s algorithms but it does require specific knowledge of the demographic characteristics for the population of interest.