EN 15531-3:2022

SLOVENSKI STANDARD
01-november-2022
Nadomešča:
SIST EN 15531-3:2015
Javni prevoz - Vmesnik za informiranje v realnem času za potrebe delovanja
javnega prevoza - 3. del: Funkcionalni vmesniki storitve
Public transport - Service interface for real-time information relating to public transport
operations - Part 3: Functional service interfaces
Öffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen, bezogen auf
Operationen im öffentlichen Verkehr - Teil 3: Funktionelle Serviceschnittstelle
Transport public - Interface de service pour les informations en temps réel relatives aux
opérations de transport public - Partie 3 : Modules d'interface d'application individuels
Ta slovenski standard je istoveten z: EN 15531-3:2022
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 15531-3
EUROPEAN STANDARD
NORME EUROPÉENNE
July 2022
EUROPÄISCHE NORM
ICS 35.240.60 Supersedes EN 15531-3:2015
English Version
Public transport - Service interface for real-time
information relating to public transport operations - Part
3: Functional service interfaces
Transport public - Interface de service pour les Öffentlicher Verkehr - Serviceschnittstelle für
informations en temps réel relatives aux opérations de Echtzeitinformationen, bezogen auf Operationen im
transport public - Partie 3 : Interfaces des services öffentlichen Verkehr - Teil 3: Funktionelle
fonctionnels Serviceschnittstelle
This European Standard was approved by CEN on 13 June 2022.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

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, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 15531-3:2022 E
worldwide for CEN national Members.

Contents           Page
1 Scope . 10
2 Normative references . 11
3 Terms and definitions . 11
4 Symbols and abbreviations . 11
5 Production Timetable Service [PT] . 11
5.1 Purpose . 11
5.2 Capability and Permission Matrices . 11
5.2.1 Capability Matrix . 11
5.2.2 Permission Matrix . 13
5.3 ProductionTimetableRequest . 13
5.3.1 ProductionTimetableRequest — Element . 13
5.3.2 ProductionTimetableRequest — Example . 14
5.4 ProductionTimetableSubscriptionRequest . 15
5.4.1 ProductionTimetableSubscriptionRequest — Element . 15
5.4.2 ProductionTimetableSubscriptionRequest — Example. 15
5.5 ProductionTimetableDelivery . 16
5.5.1 Introduction . 16
5.5.2 ServiceDelivery with a ProductionTimetableDelivery . 16
5.5.3 ProductionTimetableDelivery — Element . 16
5.5.4 DatedTimetableVersionFrame — Element . 16
5.5.5 ProductionTimetableDelivery — Example . 30
5.5.6 Efficient Delivery of Large Timetables . 32
6 Estimated Timetable Service [ET] . 32
6.1 Purpose . 32
6.2 Capability and Permission Matrices . 33
6.2.1 Capability Matrix . 33
6.2.2 Permission Matrix . 34
6.3 EstimatedTimetableRequest . 34
6.3.1 EstimatedTimetableRequest — Element . 34
6.3.2 EstimatedTimetableRequest — Example. 36
6.4 EstimatedTimetableSubscriptionRequest. 36
6.4.1 EstimatedTimetableSubscriptionRequest — Element. 36
6.4.2 EstimatedTimetableSubscriptionRequest — Example . 37
6.5 The EstimatedTimetableDelivery . 38
6.5.1 Introduction . 38
6.5.2 ServiceDelivery with a EstimatedTimetableDelivery — Element . 38
6.5.3 EstimatedTimetableDelivery — Element . 38
6.5.4 EstimatedJourneyVersionFrame — Element . 38
6.5.5 EstimatedVehicleJourney — Element . 39
6.5.6 EstimatedServiceJourneyInterchange — Element (SIRI v2.0) . 49
6.5.7 EstimatedTimetableDelivery — Example . 54
6.6 Handling of Predictions in the Estimated Timetable Service . 55
6.6.1 Supplementary Rule for the Delay Profile . 55
6.6.2 Other Supplementary Rules . 56
6.6.3 Quality of Prognoses and Prediction Windows . 56
6.6.4 Reporting Rules and Monitored Journeys . 56
6.6.5 Temporal Reporting Behaviour – Sensitivity Threshold . 57
6.6.6 Prediction Inaccurate – In Congestion . 58
6.6.7 Unexpected Termination of Monitoring . 59
6.6.8 Missing Expected or Actual Times . 60
6.7 Prediction Quality . 60
6.7.1 Definition . 60
6.7.2 Explicit prediction quality intervals . 61
6.7.3 Extrapolation rule for prediction quality . 61
6.8 General Rules and Definitions for Timetable Data . 62
6.8.1 Introduction . 62
6.8.2 Cancelled Vehicle Journeys . 62
6.8.3 Additional Vehicle Journeys . 62
6.8.4 Changes to Journeys & Routings . 63
6.8.5 Changes to Call Attributes . 63
6.8.6 Planned Connections and “Stay Seated” Connections . 63
6.8.7 Handling Train Data . 64
6.8.8 Validity Period of Production Timetables . 64
6.8.9 Initial State and Complete Stop Sequences . 64
6.8.10 Usage of Optional Elements with Default Values. 64
7 Stop Timetable Service [ST] . 65
7.1 Purpose . 65
7.2 Reference Data . 65
7.3 Capability and Permission Matrices . 65
7.3.1 Capability Matrix . 65
7.3.2 Permission Matrix . 66
7.4 StopTimetableRequest . 67
7.4.1 StopTimetableRequest — Element . 67
7.4.2 StopTimetableRequest — Example . 68
7.5 StopTimetableSubscriptionRequest . 68
7.5.1 StopTimetableSubscriptionRequest — Element . 68
7.5.2 StopTimetableSubscriptionRequest — Example . 69
7.6 StopTimetableDelivery . 69
7.6.1 Introduction . 69
7.6.2 ServiceDelivery with a StopTimetableDelivery . 69
7.6.3 StopTimetableDelivery — Element . 69
7.6.4 TimetabledStopVisit — Element . 70
7.6.5 TargetedVehicleJourney — Element. 70
7.6.6 TargetedCall — Element . 70
7.6.7 TimetabledStopVisitCancellation — Element . 71
7.6.8 StopTimetableDelivery — Example . 72
8 Stop Monitoring Service [SM] . 73
8.1 Purpose . 73
8.2 Reference Data . 73
8.2.1 Introduction . 73
8.2.2 Content Referencing. 74
8.2.3 Direct Cleardown . 74
8.3 Capability and Permission Matrices . 74
8.3.1 Capability Matrix . 74
8.3.2 Permission Matrix . 76
8.4 StopMonitoringRequest . 76
8.4.1 StopMonitoringRequest — Element . 76
8.4.2 Use of Preview Interval . 78
8.4.3 Use of Maximum and Minimum Number of Trips . 78
8.5 StopMonitoringMultipleRequest . 79
8.5.1 StopMonitoringMultipleRequest — Element . 79
8.5.2 StopMonitoringRequest — Example . 80
8.6 StopMonitoringSubscriptionRequest . 80
8.6.1 StopMonitoringSubscriptionRequest — Element . 80
8.6.2 Sensitivity Threshold . 81
8.6.3 StopMonitoringSubscriptionRequest — Example . 82
8.7 StopMonitoringDelivery . 82
8.7.1 Introduction . 82
8.7.2 ServiceDelivery with a StopMonitoringDelivery — Element . 82
8.7.3 StopMonitoringDelivery — Element . 83
8.7.4 MonitoredStopVisit — Element . 84
8.7.5 MonitoredStopVisitCancellation — Element . 98
8.7.6 StopLineNotice — Element . 99
8.7.7 StopLineNoticeCancellation — Element . 100
8.7.8 StopNotice — Element (+SIRI v2.0) . 100
8.7.9 StopNoticeCancellation — Element (+SIRI v2.0) . 101
8.7.10 ServiceException — Element (+SIRI v2.0) . 101
8.7.11 StopMonitoringDelivery — Examples . 102
8.8 Using the Stop Timetable & Stop Monitoring services together . 106
9 Vehicle Monitoring Service [VM] . 106
9.1 Purpose . 106
9.2 Reference Data . 107
9.3 Capability and Permission Matrices . 107
9.3.1 Capability Matrix . 107
9.3.2 Permission Matrix . 108
9.4 VehicleMonitoringRequest . 109
9.4.1 VehicleMonitoringRequest — Element . 109
9.4.2 VehicleMonitoringRequest — Example . 110
9.5 VehicleMonitoringSubscriptionRequest . 111
9.5.1 VehicleMonitoringSubscriptionRequest — Element . 111
9.5.2 Sensitivity Threshold. 111
9.5.3 VehicleMonitoringSubscriptionRequest — Example . 112
9.6 VehicleMonitoringDelivery . 112
9.6.1 Introduction . 112
9.6.2 ServiceDelivery with a VehicleMonitoringDelivery — Element . 112
9.6.3 VehicleMonitoringDelivery — Element . 113
9.6.4 VehicleActivity — Element . 113
9.6.5 VehicleActivityCancellation — Element . 118
9.6.6 VehicleMonitoringDelivery — Examples . 119
10 Connection Timetable Data Service [CT] . 121
10.1 Purpose . 121
10.2 Reference Data . 122
10.2.1 Content referencing . 122
10.2.2 Availability of Data . 123
10.2.3 Updating During the Course of a Journey. 124
10.3 Capability and Permission Matrices . 124
10.3.1 Capability Matrix . 124
10.3.2 Permission Matrix . 125
10.4 ConnectionTimetableRequest . 125
10.4.1 ConnectionTimetableRequest — Element . 125
10.4.2 ConnectionTimetableRequest — Example . 126
10.5 ConnectionTimetableSubscriptionRequest . 127
10.5.1 ConnectionTimetableSubscriptionRequest — Element . 127
10.5.2 ConnectionTimetableSubscriptionRequest — Example . 127
10.6 ConnectionTimetableDelivery . 127
10.6.1 Introduction . 127
10.6.2 ServiceDelivery with a ConnectionTimetableDelivery — Element . 127
10.6.3 ConnectionTimetableDelivery — Element . 128
10.6.4 ConnectionTimetableDelivery — Example . 130
11 Connection Monitoring Service [CM] . 131
11.1 Purpose . 131
11.1.1 Introduction . 131
11.1.2 Dated Vehicle-Journey-Based Connection Protection . 132
11.1.3 Time-Based Connection Protection . 132
11.2 Capability and Permission Matrices . 133
11.2.1 Capability Matrix . 133
11.2.2 Permission Matrix . 134
11.3 The ConnectionMonitoringRequest . 134
11.3.1 ConnectionMonitoringRequest — Element . 134
11.3.2 Use of PreviewInterval . 135
11.3.3 ConnectingTimeFilter — Element . 136
11.3.4 ConnectingJourneyFilter — Element . 136
11.3.5 ConnectionMonitoringRequest — Example . 136
11.4 The ConnectionMonitoringSubscriptionRequest . 137
11.4.1 ConnectionMonitoringSubscriptionRequest — Element . 137
11.4.2 Sensitivity Threshold . 137
11.4.3 ConnectionMonitoringSubscriptionRequest — Example . 138
11.5 ServiceDelivery with Connection Monitoring Deliveries — Element . 138
11.5.1 Introduction . 138
11.5.2 The ConnectionMonitoringFeederDelivery — Element . 138
11.5.3 The ConnectionMonitoringDistributorDelivery — Element. 142
12 General Message Service [GM] . 146
12.1 Purpose . 146
12.2 Reference Data . 147
12.2.1 Use of Reference Data . 147
12.2.2 Message Formats . 147
12.3 Capability and Permission Matrices . 147
12.3.1 Capability Matrix . 147
12.3.2 Permission Matrix . 148
12.4 The GeneralMessageRequest . 149
12.4.1 GeneralMessageRequest — Element . 149
12.4.2 GeneralMessageRequest — Example . 149
12.5 The GeneralMessageSubscriptionRequest . 149
12.5.1 GeneralMessageSubscriptionRequest — Element . 149
12.5.2 GeneralMessageSubscriptionRequest — Example . 150
12.6 The GeneralMessageDelivery . 150
12.6.1 Introduction . 150
12.6.2 ServiceDelivery with a GeneralMessageDelivery . 150
12.6.3 GeneralMessageDelivery — Element . 150
12.6.4 InfoMessage — Element. 151
12.6.5 InfoMessageCancellation — Element . 151
12.6.6 GeneralMessageDelivery — Example . 152

European foreword
This document (EN 15531-3:2022) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by January 2023, and conflicting national standards shall
be withdrawn at the latest by January 2023.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersede EN 15531-3:2015.
SIRI (CEN/TS 15531-1:2006) has been a CEN Technical Specification since 2007 and a European
normative standard since 2013 and has been widely used in Europe and elsewhere and proven its
usefulness. This document proposes a revised version of SIRI as a European Standard, and is currently
submitted to the Formal Vote. The proposed revisions are minor enhancements arising from experience
of the deployment of SIRI in many live systems. This document also clarifies the relationship of SIRI to
NeTEx, the CEN Technical Standard for the XML exchange of Public Transport Reference data based on
the Transmodel CEN European Standard.
This document presents Part 3 of the European Standard known as “SIRI”. SIRI provides a framework for
specifying communications and data exchange protocols for organisations wishing to exchange Real-time
Information (RTI) relating to public transport operations.
The SIRI European Standard is presented in three parts:
• context and framework, including background, scope and role, normative references, terms and
definitions, symbols and abbreviations, business context and use cases (Part 1),
• the mechanisms to be adopted for data exchange communications links (Part 2),
• data structures for a series of individual application interface modules PT, ET, ST, SM, VM, CT, CM, GM
(Part 3).
Two additional parts define additional functional services as CEN Technical Specifications:
• additional data structures for additional application interface module FM (Part 4),
• additional data structures for additional application interface module SX (Part 5).
The XML schema can be downloaded from https://github.com/SIRI-CEN/SIRI, guidance on its use,
example XML files, and case studies of national and local deployments is located at http://siri-cen.eu/.
It is recognised that SIRI is not complete as it stands, and from time to time will need to continue to be
enhanced to add additional capabilities. It is therefore intended that a SIRI Management Group should
continue to exist, at European level, based on the composition of SG7.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: 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, Republic of North
Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United
Kingdom.
Introduction
Public transport services rely increasingly on information systems to ensure reliable, efficient operation
and widely accessible, accurate passenger information. These systems are used for a range of specific
purposes: setting schedules and timetables; managing vehicle fleets; issuing tickets and receipts;
providing real-time information on service running, and so on.
This document specifies a Service Interface for Real-time Information (SIRI) about Public Transport. It is
intended to be used to exchange information between servers containing real-time public transport
vehicle or journey time data. These include the control centres of transport operators and information
systems that utilise real-time vehicle information, for example, to deliver services such as travel
information.
Well-defined, open interfaces have a crucial role in improving the economic and technical viability of
Public Transport Information Systems of all kinds. Using standardised interfaces, systems can be
implemented as discrete pluggable modules that can be chosen from a wide variety of suppliers in a
competitive market, rather than as monolithic proprietary systems from a single supplier. Interfaces also
allow the systematic automated testing of each functional module, vital for managing the complexity of
increasing large and dynamic systems. Furthermore, individual functional modules can be replaced or
evolved, without unexpected breakages of obscurely dependent function.
This document will improve a number of features of public transport information and service
management:
• Interoperability – the document will facilitate interoperability between information processing
systems of the transport operators by: (i) introducing common architectures for message exchange;
(ii) introducing a modular set of compatible information services for real-time vehicle information;
(iii) using common data models and schemas for the messages exchanged for each service; and (iv)
introducing a consistent approach to data management.
• Improved operations management – the document will assist in better vehicle management by (i)
allowing the precise tracking of both local and roaming vehicles; (ii) providing data that can be used
to improve performance, such as the measurement of schedule adherence; and (iii) allowing the
distribution of schedule updates and other messages in real-time.
• Delivery of real-time information to end-users – the document will assist the economic provision of
improved data by; (i) enabling the gathering and exchange of real-time data between AVMS systems;
(ii) providing standardised, well defined interfaces that can be used to deliver data to a wide variety
of distribution channels. Version 2.0 of SIRI includes a new Simple Web Service designed to support
the widespread, massively scalable use of mobile devices and web browsers and other applications
to display public transport data directly to users.
Technical advantages include the following:
• Reusing a common communication layer for all the various technical services enables cost-effective
implementations and makes the European Standard readily extensible in future.
History
Version 1.0 of SIRI was developed in 2004-2005 and submitted to vote, eventually passing through the
CEN process to become an approved CEN Technical Specification in 2007. As well as the normative
Version 1.0 XSD schema, successive informal working versions of the schema (v 1.1 – 1.4) were released
to allow for fixes and to implement some very minor enhancements agreed by the working group. A WSDL
version was also developed.
Version 2.0 of SIRI was developed in 2012 to coincide with making the SIRI standard a full CEN norm.
SIRI includes a Simple Web Services “SIRI-LITE” as an additional
...