IT- tillämpningar inom transport
- +Ämnesområden
- +Informationsteknik, kontorsutrustning (27)
- Informationsteknik: allmänt (2)
- IT-säkerhet (4)
- +Kodning av information (2)
- Programspråk (0)
- Programutveckling och systemdokumentation (1)
- +Öppna system (OSI) (0)
- Nätarkitekturer (0)
- Datorgrafik (0)
- Mikroprocessorsystem (0)
- Terminalutrustning och övrig kringutrustning (0)
- Gränssnitt och anslutningsutrustning (0)
- Molnbaserade datortjänster (0)
- +Datalagringsmedier (0)
- +IT-tillämpningar (22)
- IT-tillämpningar: allmänt (3)
- Datorstödd design (1)
- Identifieringskort och tillhörande läsarenheter (1)
- IT-tillämpningar i kontorsarbete (1)
- IT- tillämpningar inom information, dokumentation och förlagsverksamhet (0)
- IT- tillämpningar inom finansiella system (0)
- IT- tillämpningar inom industrin (0)
- IT- tillämpningar inom transport (4)
- IT-tillämpningar inom handel (1)
- IT- tillämpningar inom bygg- och anläggningsindustri (0)
- IT-tillämpningar inom jordbruk (0)
- IT- tillämpningar inom posttjänster (0)
- IT- tillämpningar inom vetenskap (1)
- Hälso- och sjukvårdsinformatik (10)
- IT- tillämpningar inom utbildning (0)
- Internettillämpningar (0)
- IT- tillämpningar inom övriga områden (1)
- Kontorsutrustning (0)
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 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.