IT- tillämpningar inom transport

Kommittébeteckning: SIS/TK 477 (Skeppsteknik och Marin Teknologi)
Källa: ISO
Svarsdatum: den 1 dec 2020
Se merSe mindre
 

This document provides the minimum functions and requirements of software based planned maintenance system (SPMS) covering specific requirements for planning and implementing the maintenance schedule, recording, reporting, analysis and optimization to maintain onboard equipment and systems in support of ISM 2018 Part A /10.

Kommittébeteckning: SIS/TK 255 (Intelligenta transportsystem)
Källa: ISO
Svarsdatum: den 14 dec 2020
Se merSe mindre
 

This Document specifies:

— the Localized Message (LM) format: an NPDU of a networking & transport layer protocol that does not support routing of a packet through a network;

— the Service Advertisement Message (SAM): an APDU to be transported in e.g. an LM;

— the Service Response Message (SRM): an APDU acknowledging a SAM that offered a service based on an ITS application class,[2] to be transported in e.g. an LM;

— related basic requirements for procedures.

Specifications are partly done by normative references to IEEE 1609.3™-2016.

NOTE These message format specifications and basic procedures need to be complemented by complete procedures and SAP specifications according to the context of usage, i.e. an ITS station specified in ISO 21217,[4] or a WAVE device specified in IEEE 1609.0,[13] or any other context.

Kommittébeteckning: SIS/TK 477 (Skeppsteknik och Marin Teknologi)
Källa: ISO
Svarsdatum: den 15 dec 2020
Se merSe mindre
 

This part of ISO 28005 contains technical specifications that facilitate efficient exchange of electronic information between ships and shore for coastal transit or port calls. It covers safety, security and efficiency enhancement information requirements related mainly to the relationships between the ship and the port and coastal state authorities.

This part of ISO 28005 contains the definition of core data elements for use in electronic port clearance (EPC) messages. It does not define any structuring of messages or provide any guidance on what information is required for a particular purpose; it is a general data dictionary for safety, security or operation-related maritime information. Details about message formats and applications are defined in part 1 of this standard.

The data elements in this part of ISO 28005 covers the data elements and the data model defined in the IMO Reference Data Model as specified in the IMO Compendium on Facilitation and Electronic Business. This version of the standard also contains data elements required to implement mandatory ship reporting as defined in IMO Resolution A.851(20) as amended by resolution MEPC.138(53) and bulk loading and unloading information as defined in IMO Resolution A.862(20).

Kommittébeteckning: SIS/TK 255 (Intelligenta transportsystem)
Källa: ISO
Svarsdatum: den 15 dec 2020
Se merSe mindre
 

This document specifies the data structure and data exchange procedure related to the micro-mobility service applications utilizing P-ITS-S (i.e. nomadic devices) including car sharing, parcel delivery, last & first mile connections. In addition, this document also delivers related standards required to develop and operate the service platform between nomadic device and micro mobility with intelligent transport systems (ITS) technologies, which would undertake joint work with ISO Technical Committee 204 (ISO/TC204) – Intelligent Transport Systems (ITS).

This document defines the data structure and data exchange procedures based on dataset and messages which are defined in DIS 22085-2.

Kommittébeteckning: SIS/TK 255 (Intelligenta transportsystem)
Källa: CEN
Svarsdatum: den 1 jan 2021
Se merSe mindre
 

This document specifies
— the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. including systems that automatically read licence plate numbers of vehicles passing a toll point,
— an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.
     — charging related data (toll declarations, billing details),
     — administrative data, and
     — confirmation data,
— transfer mechanisms and supporting functions,
— information objects, data syntax and semantics,
— examples of data interchanges (see Annex B and Annex C), and
— an example of toll rounding (see Annex D).
This document is applicable for any toll service and any technology used for charging.
It is defined as a toolbox standard of transactions and Application Protocol Data Units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings.
The data types and associated coding related to the data elements described in clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document is not applicable, among others, to
— any communication between toll charger (TC) or toll service provider (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,
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents, and
— definitions of service communication channels, protocols and service primitives to transfer the APDUs.

Kommittébeteckning: SIS/TK 255 (Intelligenta transportsystem)
Källa: ISO
Svarsdatum: den 1 jan 2021
Se merSe mindre
 

This document specifies
— the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. including systems that automatically read licence plate numbers of vehicles passing a toll point,
— an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g.
     — charging related data (toll declarations, billing details),
     — administrative data, and
     — confirmation data,
— transfer mechanisms and supporting functions,
— information objects, data syntax and semantics,
— examples of data interchanges (see Annex B and Annex C), and
— an example of toll rounding (see Annex D).
This document is applicable for any toll service and any technology used for charging.
It is defined as a toolbox standard of transactions and Application Protocol Data Units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, ommunication stacks and timings.
The data types and associated coding related to the data elements described in clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document is not applicable, among others, to
— any communication between toll charger (TC) or toll service provider (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,
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents, and
— definitions of service communication channels, protocols and service primitives to transfer the APDUs.

Kommittébeteckning: SIS/TK 255 (Intelligenta transportsystem)
Källa: CEN
Svarsdatum: den 1 jan 2021
Se merSe mindre
 

In respect of pan-European eCall (operating requirements defined in EN 16072), this document defines the high-level application protocols, procedures and processes required to provide the eCall service using a TS12 emergency call over a mobile communications network.
NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI/TS 122 003) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third-party services supporting eCall can be found in EN 16102, and have been developed in conjunction with the development of this work item, and is consistent in respect of the interface to the PSAP. This deliverable makes reference to those provisions but does not duplicate them.

Kommittébeteckning: SIS/TK 255 (Intelligenta transportsystem)
Källa: CEN
Svarsdatum: den 7 jan 2021
Se merSe mindre
 

The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using 'Public Land Mobile Networks'(PLMN) (such as GSM and UMTS), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident.
This document specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP.
Private third party in-vehicle emergency supporting services may also provide a similar eCall function by other means. The provision of such services are defined in EN 16102, and are outside the scope of this document.
The communications protocols and methods for the transmission of the eCall message are not specified in this document.
This document specifies the operating requirements for an eCall service. An important part of the eCall service is a Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this document, but the form and data content of the MSD is not defined herein. A common European MSD is determined in EN 15722.
This document does not specify whether eCall is provided using embedded equipment or other means (for example in the case of aftermarket equipment).