CEN/TS 16157-3:2011
(Main)Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 3: Situation Publication
Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 3: Situation Publication
This Technical Specification (CEN/TS 16157-3) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, the data content, the data structure and relationships and the communications specification.
This Technical Specification is applicable to:
- traffic and travel information which is of relevance to road networks (non urban and urban);
- public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service).
This Technical Specification establishes specifications for data exchange between any two instances of the following actors:
- Traffic Information Centres (TICs);
- Traffic Control Centres (TCCs);
- Service Providers (SPs).
Use of this Technical Specification may be applicable for use by other actors.
This Technical Specification includes the following types of information content:
- road traffic event information - planned and unplanned occurrences both on the road network and in the surrounding environment;
- operator initiated actions;
- road traffic measurement data, status data and travel time data;
- travel information relevant to road users, including weather and environmental information;
- road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 specifies the informational structures, relationships, roles, attributes and associated data types required for publishing situation traffic and travel information within the DATEX II framework. This is specified as a DATEX II Situation Publication sub-model which is part of the DATEX II platform independent model, but this Part excludes those elements that relate to location information which are specified in CEN/TS 16157-2 and those elements that relate to VMS settings which are specified in Part 4 of CEN/TS 16157 [4].
Intelligente Transportsysteme - DATEX II Datenaustausch Spezifikationen für Verkehrsmanagement und Informationen - Teil 3: Situationsveröffentlichungen
Systèmes de transport intelligents - Spécifications DATEX II d'échange de données pour la gestion du trafic et l'information routière - Partie 3: Publication de situations
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri upravljanju prometa in informiranju - 3. del: Objava situacije
Ta tehnična specifikacija (FprCEN/TS 16157-3) določa in definira vidike komponent, ki podpirajo izmenjavo in skupno uporabo podatkov in informacij v prometu in na potovanju.
Vidiki komponent vključujejo okvir in kontekst za izmenjave, pristope modeliranja, vsebino podatkov, podatkovne strukture in odnose, specifikacijo komunikacij.
Ta tehnična specifikacija velja za:
- informacije o prometu in potovanju, ki so pomembne za cestna omrežja (neurbana in urbana),
- informacije javnega prevoza, ki so neposredno pomembne za uporabo cestnega omrežja (npr. cestna povezave z železniško ali trajektno storitvijo).
Ta tehnična specifikacija vzpostavlja specifikacije za podatkovno izmenjavo med katero koli izmed instanc naslednjih udeležencev:
- prometnoinformacijski centri (TIC),
- prometnokontrolni centri (TCC),
- ponudniki storitev (SP).
Uporaba te tehnične specifikacije lahko velja, kadar jo uporabljajo drugi udeleženci.
Ta tehnična specifikacija vsebuje naslednje vrste informacijske vsebine:
- informacije o dogodkih v cestnem prometu – načrtovani in nenačrtovani dogodki na cestnem omrežju in v bližnjem okolju,
- kakor jih sporoča operater sprožene akcije,
- podatke o merjenju cestnega prometa, statusne podatke in podatke o času potovanja,
- potovalne informacije, pomembne za uporabnike cest, vključno z vremenom in okoljskimi informacijami,
- informacije nadzora cestnega prometa ter informacije in navodila, povezane z uporabo cestnega omrežja.
Ta del FprCEN/TS 16157 določa informacijske strukture, odnose, vloge, atribute in povezane podatkovne tipe, potrebne za objavo informacij o stanju prometa in potovanja v okviru DATEXA II.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2011
1DGRPHãþD
SIST ENV 13106:2003
SIST ENV 13777:2003
Inteligentni transportni sistemi - Specifikacije za izmenjavo podatkov DATEX II pri
upravljanju prometa in informiranju - 3. del: Objava situacije
Intelligent transport systems - DATEX II data exchange specifications for traffic
management and information - Part 3: Situation Publication
Intelligente Verkehrssysteme - DATEX II Datenaustauschspezifikation für
Verkehrsmanagement und Verkehrsinformation - Teil 3: Publikation von
Verkehrssituationen
Systèmes de transport intelligents - Spécifications DATEX II d'échange de données pour
la gestion du trafic et l'information routière - Partie 3: Publication de situations
Ta slovenski standard je istoveten z: CEN/TS 16157-3:2011
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.
TECHNICAL SPECIFICATION
CEN/TS 16157-3
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
October 2011
ICS 35.240.60 Supersedes ENV 13106:2000, ENV 13777:2000
English Version
Intelligent transport systems - DATEX II data exchange
specifications for traffic management and information - Part 3:
Situation Publication
Systèmes de transport intelligents - Spécifications DATEX Intelligente Transportsysteme - DATEX II Datenaustausch
II d'échange de données pour la gestion du trafic et Spezifikationen für Verkehrsmanagement und
l'information routière - Partie 3: Publication de situations Informationen - Teil 3: Situationsveröffentlichungen
This Technical Specification (CEN/TS) was approved by CEN on 10 April 2011 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available
promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)
until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2011 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16157-3:2011: E
worldwide for CEN national Members.
Contents Page
Introduction .7
1 Scope .8
2 Conformance .8
3 Normative references .9
4 Terms and definitions .9
5 Symbols and abbreviations . 10
6 UML notation . 11
7 The Situation Publication model . 11
7.1 Overview of the Situation Publication model . 11
7.2 The “SituationPublication” package. 11
7.2.1 Overview of the “SituationPublication” package . 11
7.2.2 Semantics of the “SituationPublication” package . 12
7.3 The “SituationRecord” package . 13
7.3.1 Overview of the “SituationRecord” package . 13
7.3.2 Semantics of the “SituationRecord” package . 14
7.4 The “Impact” package . 16
7.4.1 Overview of the “Impact” package . 16
7.4.2 Semantics of the “Impact” package . 17
7.5 The “Validity” package . 18
7.5.1 Overview of “Validity” package . 18
7.5.2 Semantics of the “Validity” package . 20
7.6 The “TimePeriodOfDay” package . 21
7.6.1 Overview of the “TimePeriodOfDay” package . 21
7.6.2 Semantics of the “TimePeriodOfDay” package . 21
7.7 The “NonRoadEventInformation” package . 22
7.7.1 Overview of the “NonRoadEventInformation” package . 22
7.7.2 Semantics of the “NonRoadEventInformation” package . 22
7.8 The “TrafficElement” package . 23
7.8.1 Overview of the “TrafficElement” package . 23
7.8.2 Semantics of the “TrafficElement” package . 24
7.9 The “Conditions” package . 25
7.9.1 Overview of the “Conditions” package . 25
7.9.2 Semantics of the “Conditions” package . 25
7.10 The “WeatherRelated” package . 26
7.10.1 Overview of the “WeatherRelated” package . 26
7.10.2 Semantics of the “WeatherRelated” package . 27
7.11 The “Humidity” package . 27
7.11.1 Overview of the “Humidity” package . 27
7.11.2 Semantics of the “Humidity” package. 27
7.12 The “Temperature” package . 28
7.12.1 Overview of the “Temperature” package . 28
7.12.2 Semantics of the “Temperature” package . 28
7.13 The “Visibility” package . 29
7.13.1 Overview of the “Visibility” package . 29
7.13.2 Semantics of the “Visibility” package . 29
7.14 The “Wind” package . 30
7.14.1 Overview of the “Wind” package . 30
7.14.2 Semantics of the “Wind” package . 30
7.15 The “Pollution” package . 31
7.15.1 Overview of the “Pollution” package . 31
7.15.2 Semantics of the “Pollution” package . 31
7.16 The “PrecipitationDetail” package . 32
7.16.1 Overview of the “PrecipitationDetail” package . 32
7.16.2 Semantics of the “PrecipitationDetail” package . 32
7.17 The “RoadSurfaceConditionMeasurements” package . 33
7.17.1 Overview of the “RoadSurfaceConditionMeasurements” package . 33
7.17.2 Semantics of the “RoadSurfaceConditionMeasurements” package . 33
7.18 The “Accident” package . 34
7.18.1 Overview of the “Accident” package . 34
7.18.2 Semantics of the “Accident” package . 35
7.19 The “Obstruction” package . 36
7.19.1 Overview of the “Obstruction” package . 36
7.19.2 Semantics of the “Obstruction” package . 37
7.20 The “Activity” package . 38
7.20.1 Overview of the “Activity” package . 38
7.20.2 Semantics of the “Activity” package . 39
7.21 The “Vehicle” package . 40
7.21.1 Overview of the “Vehicle” package . 40
7.21.2 Semantics of the “Vehicle” package . 41
7.22 The “VehicleCharacteristics” package . 42
7.22.1 Overview of the “VehicleCharacteristics” package . 42
7.22.2 Semantics of the “VehicleCharacteristics” package . 43
7.23 The “OperatorAction” package . 43
7.23.1 Overview of the “OperatorAction” package . 43
7.23.2 Semantics of the “OperatorAction” package . 44
7.24 The “Roadworks” package . 45
7.24.1 Overview of the “Roadworks” package . 45
7.24.2 Semantics of the “Roadworks” package . 46
7.25 The “NetworkManagement” package . 47
7.25.1 Overview of the “NetworkManagement” package . 47
7.25.2 Semantics of the “NetworkManagement” package
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.