Sökning - 2 resultat för 'TK 255'
- +Allmänt. Terminologi. Standardisering. Dokumentation (6)
- +Ledningssystem (4)
- +Kvalitet (0)
- +Naturvetenskap och tillämpad vetenskap (3)
- +Hälso- och sjukvård (6)
- +Miljö- och hälsoskydd. Säkerhet (39)
- +Maskinsäkerhet (6)
- +Metrologi och mätning. Fysikaliska fenomen (4)
- +Provning (1)
- +Mekaniska system och komponenter: allmänt (2)
- +Fluidsystem och delar: allmänt (10)
- +Produktionsteknik (3)
- +Sociologi. Service. Företagsorganisation och företagsledning. Administration. Transport Administration (10)
- +Energi- och värmeöverföring (4)
- +Elektroteknik (2)
- +Elektronik (0)
- +Telekommunikation (1)
- +Informationsteknik, kontorsutrustning (29)
- +Bildteknik (0)
- +Finmekanik. Juvelerararbeten (2)
- +Fordonsteknik (3)
- +Järnvägsteknik (0)
- +Textil- och läderteknik (2)
- +Flyg- och rymdteknik (16)
- +Utrustning för materialhantering (4)
- +Förpackningar och distribution (1)
- +Skeppbyggnadteknik och marina konstruktioner (3)
- +Konfektionsindustri (0)
- +Jordbruk (3)
- +Livsmedelsteknik (5)
- +Kemiteknik (3)
- +Gruvdrift och mineraler (0)
- +Petroleum och motsvarande tekniker (6)
- +Metallurgi (7)
- +Träteknik (10)
- +Glasindustri och keramisk industri (2)
- +Gummi- och plastindustri (4)
- +Pappersteknik (0)
- +Färgindustrin (1)
- +Byggnadsmaterial och byggnader (15)
- +Byggstandardpaket (1)
- +Anläggningsarbete (6)
- +Byggnadsprojektering (0)
- +Militärväsen. Militärteknik. Vapen (0)
- +Hem och hushåll. Underhållning. Sport (5)
- +Externa kategorier (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.