ENV 12315-1:1996
(Main)Traffic and Traveller Information (TTI) - TTI Messages via Dedicated Short-Range Communication - Part 1: Data Specification - Downlink (Roadside to Vehicle)
- BACK
- 20-Aug-1996
- 13-Apr-2025
- 35.240.60
- M/018
- CEN/TC 278
Traffic and Traveller Information (TTI) - TTI Messages via Dedicated Short-Range Communication - Part 1: Data Specification - Downlink (Roadside to Vehicle)
This pre-Standard provides a common message structure for Traffic and Traveller Information messages which are disseminated via dedicated beacon infrastructure (for short-range communications, only).
Prometne in potovalne informacije (TTI) - Sporočila TTI prek posebne komunikacije kratkega dosega – 1. del: Podatkovne specifikacije – Navzdolnja povezava (od cestnega roba do vozila)
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-oktober-2003
3URPHWQHLQSRWRYDOQHLQIRUPDFLMH77,6SRURþLOD77,SUHNSRVHEQH
NRPXQLNDFLMHNUDWNHJDGRVHJD±GHO3RGDWNRYQHVSHFLILNDFLMH±1DY]GROQMD
SRYH]DYDRGFHVWQHJDUREDGRYR]LOD
Traffic and Traveller Information (TTI) - TTI Messages via Dedicated Short-Range
Communication - Part 1: Data Specification - Downlink (Roadside to Vehicle)
Ta slovenski standard je istoveten z: ENV 12315-1:1996
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
...
This May Also Interest You
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), 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 can 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 MSD 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).
- Draft30 pagesEnglish languagesale 10% offe-Library read for×1 day
- 08-Apr-2025
- 03.220.20
- 35.240.60
- 2010/40/EU
- CEN/TC 278
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Draft83 pagesEnglish languagesale 10% offe-Library read for×1 day
- 11-Mar-2025
- 03.220.20
- 35.240.20
- 35.240.60
- CEN/TC 278
In respect of operating requirements specified in EN 16072, this document specifies adaptations to enable the provision of eCall for powered two-wheel vehicles.
As with the existing provisions for eCall for category M1/N1 vehicles, these are specified within the paradigm of being OEM-fit equipment supplied with new vehicles.
This document includes only the requirements for category L1 and L3 P2WV (vehicle based) with the exception of L1e-A (powered cycle), although other documents can subject other ‘L’ subcategories to use this document. Other documents can be prepared for other UNECE category ‘L’ variants.
The requirements herein relate only to the provision of pan-European eCall and does not provide requirements for third party service provision of eCall. Other than in the 112-eCall using IMS over packet switched networks paradigm, which involves a direct call from the vehicle to the most appropriate PSAP, third party service provision involves the support of an intermediary third-party service provider before the call is forwarded to the PSAP.
The provision of eCall for vehicles via the aftermarket (post sales and registration), and the operational requirements for any such aftermarket solution, will be the subject of other work.
- Draft19 pagesEnglish languagesale 10% offe-Library read for×1 day
- 04-Mar-2025
- 35.240.60
- CEN/TC 278
This document specifies a unified logical data model based on available existing dynamic information standards. The data has precise relative location references to be linked with ISO/TS 22726-1 which specifies the architecture and the logical data model of static map data for connected and automated driving applications. Dynamic event data comes from external systems and has been defined and specified independently by existing standards. Therefore, the logical data model in this document is formed to synthesize contents referring to other standards.
- Draft115 pagesEnglish languagesale 10% offe-Library read for×1 day
- 04-Mar-2025
- 03.220.20
- 35.240.60
- 2010/40/EU
- CEN/TC 278
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
— ASN.1 (data) types within the field of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
- Standard65 pagesEnglish languagesale 10% offe-Library read for×1 day
- 17-Dec-2024
- 03.220.20
- 35.240.60
- CEN/TC 278
The Technical Specification will be adapted in the following way:
• OJP will be realigned with the latest Transmodel version and NeTEx issues, where appropriate (e.g.
New Modes)
• The integration of new modes especially the conceptual equivalency to major multi-modal standards
shall be studied and if necessary, adaptions to OJP occur. The idea is to study OSDM, TOMP, TRIAS
and GBFS/GOFS. The interactions should be smooth. Interaction between OJP and distribution
features will be settled.
• OJP is extended as far into the distribution area as it is considered a good idea. For the actual
booking and purchase steps, OSDM, TOMP, TRIAS and/or GOFS are to be used. The line we think to
draw is: booking. OJP should not transfer personalized information. This results in the following
proposed adaptions to fit OJP into a full MaaS roaming environment:
o An availability request (with response)
o Token/id handling for trips and trip legs (for hand-over) and pushed information during trips. We will
need to model bookable items on some level.
o OJPFare needs to be extended/adapted.
o TripInfoRequest and -Response need to be updated to reflect, information about trips and trip legs
and not only vehicle and journey.
• All work prepared under the heading OJP 1.1 will be finalised.
• EPIAP (Accessibility) minimal profile will be used to verify that the trip planning can make use of it.
• The provision of an OpenAPI and REST/JSON derived directly from the XSD shall be studied
(eventually using a converter).
- Technical specification256 pagesEnglish languagesale 10% offe-Library read for×1 day
- 10-Dec-2024
- 35.240.60
- 2010/40/EU
- M/456
- CEN/TC 278
This document defines the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE/4G) as:
1) In-vehicle system (3.20) (IVS)/vehicle,
2) Mobile network Operator (MNO),
3) Public safety answering point (3.27) (PSAP),
and to provide conformance tests for actor groups 1) - 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS eCall) are not within the scope of this deliverable. This is because the core TPS-eCall (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29).
NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184.
NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks.
The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
- Standard188 pagesEnglish languagesale 10% offe-Library read for×1 day
- 03-Dec-2024
- 35.240.60
- CEN/TC 278
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 via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
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 or IMS packet switched network) 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.
This document makes reference to those provisions but does not duplicate them.
- Standard37 pagesEnglish languagesale 10% offe-Library read for×1 day
- 26-Nov-2024
- 35.240.60
- CEN/TC 278
This document specifies the set-up of a testing system and the test suite structure and test purposes, i.e. tests to be used to assess the level of interference from RLAN devices operating in the 5,8 GHz range on tolling and tachograph devices operating in the same frequency range.
To obtain generalized results that can subsequently be used to design appropriate mitigation techniques, the test environment and the test cases are designed to:
1. acquire a large number of transactions on devices of different makes and characteristics;
2. ensure anonymity of results.
The test results ensure calculation of averages as well as standard deviations.
The tests specified in this document are for the sole purpose of investigating RLAN interference over DSRC communications. Other factors that can impact the performance of DSRC and also the level of interference in a test scenario are not subject to test specifications and out of the scope of this document.
- Technical specification33 pagesEnglish languagesale 10% offe-Library read for×1 day
- 01-Oct-2024
- 33.070.30
- 35.240.60
- 2019/520
- CEN/TC 278
This document defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2021. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between Toll Chargers and Toll Service Providers.
This document covers:
— exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
o charging related data (exception lists, toll declarations, billing details, payment claims);
o administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
o confirmation data.
— transfer mechanisms and supporting functions;
— semantics of data elements;
— restrictions on parameters and their values
— implementation conformance statement proforma, in an Annex, as a basis for assessment of conformity to this document;
— an Interoperability statement proforma, in an Annex, as a basis for assessment of transactional interoperability of two technical implementations;
— a web service definition, in an Annex, for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered.
- Standard225 pagesEnglish languagesale 10% offe-Library read for×1 day
- 23-Jul-2024
- 35.240.60
- 2019/520
- M/338
- CEN/TC 278
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.