1、BSI Standards PublicationBS EN 15531-3:2015Public transport Serviceinterface for real-timeinformation relating to publictransport operationsPart 3: Functional service interfacesBS EN 15531-3:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN 15531-3:2015.It su
2、persedes DD CEN/TS 15531-3:2007 which is withdrawn.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to
3、include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2015. Published by BSI StandardsLimited 2015ISBN 978 0 580 83399 1ICS 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This B
4、ritish Standard was published under the authority of theStandards Policy and Strategy Committee on 31 August 2015.Amendments issued since publicationDate Text affectedBS EN 15531-3:2015EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 15531-3 August 2015 ICS 35.240.60 Supersedes CEN/TS 15531-3:20
5、07English 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 informations en temps rel relatives aux oprations de transport public - Partie 3 : Modules
6、 dinterface dapplication individuels ffentlicher Verkehr - Serviceschnittstelle fr Echtzeitinformationen, bezogen auf Operationen im ffentlichen Verkehr - Teil 3: Funktionelle Serviceschnittstelle This European Standard was approved by CEN on 20 June 2015. CEN members are bound to comply with the CE
7、N/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 Ce
8、ntre 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 t
9、he official versions. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Nethe
10、rlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2015 CEN All rig
11、hts of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15531-3:2015 EBS EN 15531-3:2015EN 15531-3:2015 (E) 2 Contents Page European foreword .4 Introduction .5 1 Scope 6 2 Normative references 6 3 Terms and definitions .6 4 Symbols and abbreviations
12、 7 5 Production Timetable Service PT 7 5.1 Purpose .7 5.2 Capability and Permission Matrices 7 5.3 ProductionTimetableRequest .9 5.4 ProductionTimetableSubscriptionRequest 10 5.5 ProductionTimetableDelivery 11 6 Estimated Timetable Service ET . 20 6.1 Purpose 20 6.2 Capability and Permission Matrice
13、s . 21 6.3 EstimatedTimetableRequest 22 6.4 EstimatedTimetableSubscriptionRequest . 24 6.5 The EstimatedTimetableDelivery 25 6.6 Handling of Predictions in the Estimated Timetable Service . 34 6.7 Prediction Quality . 39 6.8 General Rules and Definitions for Timetable Data 40 7 Stop Timetable Servic
14、e ST 42 7.1 Purpose 42 7.2 Reference Data 42 7.3 Capability and Permission Matrices . 43 7.4 StopTimetableRequest . 44 7.5 StopTimetableSubscriptionRequest . 45 7.6 StopTimetableDelivery . 46 8 Stop Monitoring Service SM 50 8.1 Purpose 50 8.2 Reference Data 50 8.3 Capability and Permission Matrices
15、. 51 8.4 StopMonitoringRequest . 53 8.5 StopMonitoringMultipleRequest . 58 8.6 StopMonitoringSubscriptionRequest . 59 8.7 StopMonitoringDelivery . 60 8.8 Using the Stop Timetable managing vehicle fleets; issuing tickets and receipts; providing real-time information on service running, and so on. Thi
16、s European Standard 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 an
17、d information systems that utilise real-time vehicle information, for example, to deliver services such as travel information. SIRI 2 has also added, with SITI Lite, a possible exchange between server and end-user devices like smartphones or web browsers. Well-defined, open interfaces have a crucial
18、 role in improving the economic and technical viability of Public Transport Information Systems of all kinds. Using standardized 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
19、 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 breakage
20、s of obscurely dependent function. This European Standard will improve a number of features of public transport information and service management: Interoperability the European Standard will facilitate interoperability between information processing systems of the transport operators by: (i) introd
21、ucing 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.
22、 Improved operations management the European Standard 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 d
23、istribution of schedule updates and other messages in real-time. Delivery of real-time information to end-users the European Standard will assist the economic provision of improved data by; (i) enabling the gathering and exchange of real-time data between VAMS systems; (ii) providing standardized, w
24、ell defined interfaces that can be used to deliver data to a wide variety of distribution channels. 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
25、extensible in future. BS EN 15531-3:2015EN 15531-3:2015 (E) 6 1 Scope 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
26、a small number of specific options. Part 2 of this European Standard specifies the communications channel. Part 3 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 plan
27、ned 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
28、 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
29、 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
30、 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 presen
31、tations 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 provides all the current relevant information from one AVMS relating to all v
32、ehicles 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, eit
33、her 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 conn
34、ection, 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 period
35、s in addition to the actual content. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the ref
36、erenced document (including any amendments) applies. EN 15531-1:2015, Public transport - Service interface for real-time information relating to public transport operations - Part 1: Context and framework 3 Terms and definitions For the purposes of this document, the terms and definitions given in E
37、N 15531-1:2015 apply. BS EN 15531-3:2015EN 15531-3:2015 (E) 7 4 Symbols and abbreviations For the purposes of this document, the symbols and abbreviations given in EN 15531-1:2015 apply. 5 Production Timetable Service PT 5.1 Purpose The SIRI Production Timetable Service transmits daily timetables th
38、at include any planned updates that are known about at the time of transmission. The service is used typically to communicate between Scheduling systems and AVMS systems, and also between AVMS systems and intelligent clients of the AVMS system. The timetables exchanged should cover all LINEs covered
39、 by the AVMS system. The SIRI Production Timetable Service is also used to transmit the planned interchanges between journeys, including information about the linking of vehicle journey parts through the interchange, such as whether passengers are able to remain seated in the VEHICLE. The provision
40、of known updates gives a more accurate data set of journeys for the SIRI Estimated Timetable Service to reference, allowing a more efficient real-time exchange of content. However, the provision of a Production Timetable Service is not absolutely essential for the functioning of the Estimated Timeta
41、ble service. Because of the enhanced quality of data given by an increased integration with operational and back-office scheduling systems, SIRI implementations that are able to obtain production timetables should always provide and make use of a SIRI Production Timetable Service. An AVMS system may
42、 be aware of additional operational journeys and CALLs such as dead runs, and layovers. As the schedule information system usually only knows about VEHICLE JOURNEYs that are relevant to the passenger, the AVMS should only transmit passenger carrying VEHICLE JOURNEYs to the schedule information syste
43、m. 5.2 Capability and Permission Matrices 5.2.1 Capability Matrix Table 1 shows the set of required and optional capabilities defined for the Production Timetable service. If the service supports Capability Discovery the ProductionTimetableCapabilitiesRequest / Production-TimetableCapabilitiesRespon
44、se message pair can be used to determine the implementations capabilities. Table 1 ProductionTimetableCapabilities Matrix ProductionTimetableCapabilities +Structure Capabilities describing implementation of Production Timetable service inherit : 1:1 See xxx-Capability-Response See SIRI Part 2 for Co
45、mmon Capability attributes. Topic TopicFiltering 0:1 +Structure Which optional filtering features are supported? FilterByValidityPeriod 1:1 xsd:boolean Whether results can be filtered by Validity Period. Required Capability: Fixed is true. FilterByOperatorRef 1:1 xsd:boolean Whether results can be f
46、iltered by OPERATOR. Default is true. FilterByLineRef 1:1 xsd:boolean Whether results can be filtered by LINE. Default is true. BS EN 15531-3:2015EN 15531-3:2015 (E) 8 FilterByVersionRef 1:1 xsd:boolean Whether results can be filtered by TIMETABLE Version. Default is true. Request Policy RequestPoli
47、cy 0:1 +Structure Which features of Request Policy are supported by the service? Language 1:* xsd:language National languages used by service. Translations 0:1 xsd:boolean Whether the producer supports translations. SIRI 2.0 Default is false. choice Location reference system for coordinates. a GmlCo
48、ordinateFormat 0:1 SrsNameType Default coordinate format is given by a GML value. b WgsDecimalDegrees EmptyType Default coordinate data system is WGS 84 latitude and longitude. Sub-scription Policy SubscriptionPolicy 0:1 +Structure Which features of Subscription Policy are supported by the service?
49、HasIncremental-Updates 0:1 xsd:boolean Whether incremental updates can be specified for updates. Default is true. Access Control AccessControl 0:1 +Structure Which optional Access Control features are supported by service? RequestChecking 1:1 xsd:boolean Whether access control of requests is supported. Default is false. CheckOperatorRef 0:1 xsd:boolean If access control is supported, whether access control by OPERATOR is supported. Default is true. CheckLineRef 0:1 xsd:boolean If access control is supported, whether a
