Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces

There are many potential ways for passenger transport operations centres to interact. The approach taken by SIRI is for an open-ended set of standard data structures, carried over a communications channel constructed using one of a small number of specific options. Part 2 of this Technical Specification specifies the communications channel. This section specifies a number of functional modules, based on the 'use cases' identified in Annex B to Part 1: Production Timetable (PT): this service enables the provision of information on the planned progress of vehicles operating a specific service, identified by the vehicle time of arrival and departure at specific stops on a planned route for a particular Operational Day. Estimated Timetable (ET): this service enables the provision of information on the actual progress of Vehicle Journeys operating specific service Lines, detailing expected arrival and departure times at specific stops on a planned route. There will be recorded data for stops which have been passed, and predicted data for stops not yet passed. In addition the Estimated Timetable service allows Vehicle Journeys to be cancelled, added or changed. Stop Timetable (ST): this service provides a stop-centric view of timetabled vehicle arrivals and departures at a designated stop. It can be used to reduce the amount of information that needs to be transmitted in real-time to stops and displays, as reference data for a Stop Monitoring Service; and provides a data feed of the static timetables. Stop Monitoring (SM): this service provides a stop-centric view of vehicle arrivals and departures at a designated stop. It can be used by displays and other presentation services to provide departure board and other presentations of timetable and real-time journey information both at stops and at a distance. Vehicle Monitoring (VM): this service enables the provision of information on the current location and status of a set of vehicles. It does not relate to specific stops. It provides all the current relevant information from one AVMS relating to all vehicles fulfilling a set of selection criteria. Connection Timetable (CT): this service may be used to provide information about the scheduled arrivals of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then plan how to guarantee the connection, either with the expected vehicle or a different vehicle. Connection Monitoring (CM): this service is used to provide information about the expected arrival of a feeder vehicle to the operator of a connecting distributor service. The distributor operator can then manage the service to guarantee the connection, based on actual vehicle running. General Message (GM): the SIRI "General Message" service is used to exchange informative messages between identified individuals in free or an arbitrary structured format. It enables messages to be sent and to be revoked. Messages are assigned validity periods in addition to the actual content.

Öffentlicher Verkehr - Dienstleistungsschnittstelle für zeitnahe Informationen zum Betrieb des öffentlichen Verkehrs - Teil 3: Funktionale Dienstleistungsschnittstellen

Javni prevoz - Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza - 3. del: Funkcionalni vmesniki storitve

General Information

Status
Withdrawn
Publication Date
05-Jan-2009
Withdrawal Date
10-Sep-2015
Technical Committee
Current Stage
9900 - Withdrawal (Adopted Project)
Start Date
07-Sep-2015
Due Date
30-Sep-2015
Completion Date
11-Sep-2015

Relations

Buy Standard

Technical specification
TS CEN/TS 15531-3:2009
English language
124 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 15531-3:2009
01-februar-2009
-DYQLSUHYR]9PHVQLN]DLQIRUPLUDQMHYUHDOQHPþDVX]DSRWUHEHGHORYDQMD
MDYQHJDSUHYR]DGHO)XQNFLRQDOQLYPHVQLNLVWRULWYH
Public transport - Service interface for real-time information relating to public transport
operations - Part 3: Functional service interfaces
Öffentlicher Verkehr - Dienstleistungsschnittstelle für zeitnahe Informationen zum Betrieb
des öffentlichen Verkehrs - Teil 3: Funktionale Dienstleistungsschnittstellen
Ta slovenski standard je istoveten z: CEN/TS 15531-3:2007
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
SIST-TS CEN/TS 15531-3:2009 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TS CEN/TS 15531-3:2009

---------------------- Page: 2 ----------------------

SIST-TS CEN/TS 15531-3:2009
TECHNICAL SPECIFICATION
CEN/TS 15531-3
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
July 2007
ICS 35.240.60

English Version
Public transport - Service interface for real-time information
relating to public transport operations - Part 3: Functional
service interfaces
Öffentlicher Verkehr - Dienstleistungsschnittstelle für
zeitnahe Informationen zum Betrieb des öffentlichen
Verkehrs - Teil 3: Funktionale Dienstleistungsschnittstellen
This Technical Specification (CEN/TS) was approved by CEN on 23 October 2006 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, 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: rue de Stassart, 36  B-1050 Brussels
© 2007 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 15531-3:2007: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TS CEN/TS 15531-3:2009
CEN/TS 15531-3:2007 (E)
Contents Page
Foreword.6
Introduction .7
1 Scope .8
2 Normative references .8
3 Terms and definitions .8
4 Symbols and abbreviations .9
5 Production Timetable Service [PT] .9
5.1 Purpose.9
5.2 Capability and Permission Matrices .9
5.2.1 Capability Matrix .9
5.2.2 Permission Matrix.10
5.3 ProductionTimetableRequest.10
5.3.1 ProductionTimetableRequest Definition .10
5.3.2 ProductionTimetableRequest Example.11
5.4 ProductionTimetableSubscriptionRequest.12
5.4.1 ProductionTimetableSubscriptionRequest Definition.12
5.4.2 ProductionTimetableSubscriptionRequest Example.12
5.5 ProductionTimetableDelivery.13
5.5.1 General.13
5.5.2 ServiceDelivery with a ProductionTimetableDelivery.13
5.5.3 ProductionTimetableDelivery Element.13
5.5.4 DatedTimetableVersionFrame Element.13
5.5.5 ProductionTimetableDelivery Example .17
5.5.6 Efficient Delivery of Large Timetables .20
6 Estimated Timetable Service [ET].20
6.1 Purpose.20
6.2 Capability and Permission Matrices .20
6.2.1 Capability Matrix .20
6.2.2 Permission Matrix.21
6.3 EstimatedTimetableRequest.22
6.3.1 EstimatedTimetableRequest Definition.22
6.3.2 EstimatedTimetableRequest Example.23
6.4 EstimatedTimetableSubscriptionRequest .24
6.4.1 EstimatedTimetableSubscriptionRequest Definition.24
6.4.2 EstimatedTimetableSubscriptionRequest Example.24
6.5 The EstimatedTimetableDelivery .25
6.5.1 General.25
6.5.2 ServiceDelivery with a EstimatedTimetableDelivery.25
6.5.3 EstimatedTimetableDelivery Element.25
6.5.4 EstimatedTimetableVersionFrame Element.25
6.5.5 EstimatedVehicleJourney Element.26
6.5.6 EstimatedTimetableDelivery Example.29
6.6 Handling of Predictions in the Estimated Timetable Service.31
6.6.1 Supplementary Rule for the Delay Profile.31
6.6.2 Other Supplementary Rules .32
6.6.3 Quality of Prognoses and Prediction Windows.32
6.6.4 Reporting Rules and Monitored Journeys .33
6.6.5 Temporal Reporting Behaviour – Sensitivity Threshold .34
2

---------------------- Page: 4 ----------------------

SIST-TS CEN/TS 15531-3:2009
CEN/TS 15531-3:2007 (E)
6.6.6 Prediction Inaccurate – In Congestion.35
6.6.7 Unexpected Termination of Monitoring .35
6.7 General Rules and Definitions for Timetable Data.36
6.7.1 General .36
6.7.2 Cancelled Vehicle Journeys.36
6.7.3 Additional Vehicle Journeys .36
6.7.4 Changes to Journeys & Routings.37
6.7.5 Changes to Call Attributes .37
6.7.6 Planned Connections and “Stay Seated” Connections .37
6.7.7 Handling Train Data.37
7 Stop Timetable Service [ST].38
7.1 Purpose .38
7.2 Reference Data .38
7.3 Capability and Permission Matrices.38
7.3.1 Capability Matrix.38
7.3.2 Permission Matrix.39
7.4 StopTimetableRequest.40
7.4.1 StopTimetableRequest Definition.40
7.4.2 StopTimetableRequest Example.40
7.5 StopTimetableSubscriptionRequest .41
7.5.1 StopTimetableSubscriptionRequest Definition.41
7.5.2 StopTimetableSubscriptionRequest Example .41
7.6 StopTimetableDelivery.41
7.6.1 General .41
7.6.2 ServiceDelivery with a StopTimetableDelivery .42
7.6.3 StopTimetableDelivery Element.42
7.6.4 TimetabledStopVisit Element.42
7.6.5 TargetedVehicleJourney Element.43
7.6.6 TargetedCall Element.43
7.6.7 TimetabledStopVisitCancellation Element .44
7.6.8 StopTimetableDelivery Example.44
7.6.9 TargetedVehicleJourneyAsFlatGroup Element.45
8 Stop Monitoring Service [SM] .46
8.1 Purpose .46
8.2 Reference Data .46
8.2.1 General .46
8.2.2 Content Referencing .46
8.2.3 Direct Cleardown.46
8.3 Capability and Permission Matrices.47
8.3.1 Capability Matrix.47
8.3.2 Permission Matrix.48
8.4 StopMonitoringRequest.49
8.4.1 StopMonitoringRequest Definition .49
8.4.2 Use of PreviewInterval .50
8.4.3 StopMonitoringRequest Detail Levels.50
8.4.4 Use of Maximum and Minimum Number of Trips.50
8.4.5 StopMonitoringRequest Example.51
8.5 StopMonitoringSubscriptionRequest.52
8.5.1 StopMonitoringSubscriptionRequest Definition.52
8.5.2 Sensitivity Threshold .52
8.5.3 StopMonitoringSubscriptionRequest Example.53
8.6 StopMonitoringDelivery.54
8.6.1 General .54
8.6.2 ServiceDelivery with a StopMonitoringDelivery.54
8.6.3 StopMonitoringDelivery Element.54
8.6.4 MonitoredStopVisit Element.55
8.6.5 MonitoredStopVisitCancellation Element.61
8.6.6 StopLineNotice Element .62
3

---------------------- Page: 5 ----------------------

SIST-TS CEN/TS 15531-3:2009
CEN/TS 15531-3:2007 (E)
8.6.7 StopLineNoticeCancellation Element.63
8.6.8 MonitoredStopVisit with MonitoredVehicleJourneyAsGroup Element.63
8.6.9 StopMonitoringDelivery Examples .64
8.7 Using the Stop Timetable & Stop Monitoring services together .72
9 Vehicle Monitoring Service [VM].72
9.1 Purpose.72
9.2 Reference Data.72
9.3 Capability and Permission Matrices .72
9.3.1 Capability Matrix .72
9.3.2 Permission Matrix.74
9.4 VehicleMonitoringRequest .74
9.4.1 VehicleMonitoringRequest Definition.74
9.4.2 VehicleMonitoringDetailLevel.75
9.4.3 VehicleMonitoringRequest Example.75
9.5 VehicleMonitoringSubscriptionRequest .76
9.5.1 VehicleMonitoringSubscriptionRequest Definition.76
9.5.2 Sensitivity Threshold .77
9.5.3 VehicleMonitoringSubscriptionRequest Example .77
9.6 VehicleMonitoringDelivery.78
9.6.1 General.78
9.6.2 ServiceDelivery with a VehicleMonitoringDelivery .78
9.6.3 VehicleMonitoringDelivery Element.78
9.6.4 VehicleActivity Element .79
9.6.5 VehicleActivityCancellation Element.83
9.6.6 VehicleActivity with MonitoredVehicleJourneyAsGroup Element .84
9.6.7 VehicleMonitoringDelivery Examples.84
10 Connection Timetable Data Service [CT] .89
10.1 Purpose.89
10.2 Reference Data.90
10.2.1 Content referencing.90
10.2.2 Availability of Data.91
10.2.3 Updating During the Course of a Journey .92
10.3 Capability and Permission Matrices .92
10.3.1 Capability Matrix .92
10.3.2 Permission Matrix.93
10.4 ConnectionTimetableRequest.94
10.4.1 ConnectionTimetableRequest Definition .94
10.4.2 ConnectionTimetableRequest Example .95
10.5 ConnectionTimetableSubscriptionRequest.95
10.5.1 ConnectionTimetableSubscriptionRequest Definition .95
10.5.2 ConnectionTimetableSubscriptionRequest Example.95
10.6 ConnectionTimetableDelivery .96
10.6.1 General.96
10.6.2 ServiceDelivery with a ConnectionTimetableDelivery.96
10.6.3 ConnectionTimetableDelivery Element .96
10.6.4 TimetabledFeederArrival with InterchangeJourneyAsFlatGroup Element.99
10.6.5 ConnectionTimetableDelivery Example .100
11 Connection Monitoring Service [CM].102
11.1 Purpose.102
11.1.1 General.102
11.1.2 Dated Vehicle-Journey-Based Connection Protection .102
11.1.3 Time-Based Connection Protection.103
11.2 Capability and Permission Matrices .103
11.2.1 Capability Matrix .103
11.2.2 Permission Matrix.104
11.3 The ConnectionMonitoringRequest.104
11.3.1 ConnectionMonitoringRequest Definition .104
11.3.2 Use of PreviewInterval .105
4

---------------------- Page: 6 ----------------------

SIST-TS CEN/TS 15531-3:2009
CEN/TS 15531-3:2007 (E)
11.3.3 ConnectingTimeFilter.105
11.3.4 ConnectingJourneyFilter.106
11.3.5 ConnectionMonitoringRequest Example .106
11.4 The ConnectionMonitoringSubscriptionRequest .107
11.4.1 ConnectionMonitoringSubscriptionRequest Definition .107
11.4.2 Sensitivity Threshold .107
11.4.3 ConnectionMonitoringSubscriptionRequest Example.108
11.5 ServiceDelivery with a Connection Monitoring Deliveries.108
11.5.1 General .108
11.5.2 The ConnectionMonitoringFeederDelivery.109
11.5.3 The ConnectionMonitoringDistributorDelivery .112
12 General Message Service [GM].116
12.1 Purpose .116
12.2 Reference Data .117
12.2.1 Use of Reference Data .117
12.2.2 Message Formats .117
12.3 Capability and Permission Matrices.117
12.3.1 Capability Matrix.117
12.3.2 Permission Matrix.118
12.4 The GeneralMessageRequest .118
12.4.1 GeneralMessageRequest Definition .118
12.4.2 GeneralMessageRequest Example.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.