SIST EN 15531-3:2015
(Main)Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces
Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces
Update of CEN/TS 15531 respecting the results of the projects in different countries using the specification and taking into account new demands. The existing standard was developed by CEN TC278 WG3 SG7 starting in 2002 and published in 2007. It facilitates interoperability between information processing systems of the transport operators (Automatic Vehicle monitoring Systems: AVMS) in order to allow a better vehicle management as well as the delivery of real time information to end-users. The main elements of the standard are: - A communication layer, which defines common procedures for requesting and exchanging of data. The communication procedures are the same for all services and with that represent the interface infrastructure (message referencing, error handling, reset behaviour). Reusing it for the various technical services ensures cost-effective implementation and extension of the interface. o Request/Response o Publish/Subscribe Subscriptions define the type and volume of data to be exchanged. - An interface between control centres (AVMS) with the functions o connection protection (time or journey related) o connection information (time related) o real time passenger information (Departure Board, stop centric) o general message service (event and information message service) o time table information and network topology (Planned Data Exchange) o vehicle activity (VIS) - An interface for time table information between control centres (AVMS) and information systems with the functions o real time schedule information o Reference data service for schedule information. The new work item will consider the work of - Other sub-groups pf WG3: * SG4 Data Base Model for Public Transport (TRANSMODEL) * SG9 Network and Timetable Exchange (NeTEx) - National Mirror Groups Justification Since SIRI has been developed demands for information by interested public bodies and especially customers of public transport have risen substantially.
Existing national and international ‘standards’ (especially TRIDENT, RTIG and VDV-453/454) being in use already before the time of SIRI have reached a high level of performance. Now that time has come to replace the old systems by SIRI, CEN/TS 15531 has to meet this performance. Therefore it is urgent to enhance and refine SIRI, so it meets the level, real time data management has reached today.
Ö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
Javni prevoz - Vmesnik za informiranje v realnem času za potrebe delovanja javnega prevoza - 3. del: Funkcionalni vmesniki storitve
Posodobitev standarda CEN/TS 15531 ob upoštevanju rezultatov projektov v različnih državah, ki so uporabljale specifikacijo, in ob upoštevanju novih zahtev. Obstoječi standard so začeli razvijati v okviru CEN TC278 WG3 SG7 leta 2002 in ga objavili leta 2007. Olajšuje interoperabilnost med sistemi za obdelavo informacij o izvajalcih prevoza (avtomatski nadzorni sistemi za vozila: AVMS), da se omogoči boljše upravljanje vozil kot tudi zagotavljanje informacij za končne uporabnike v realnem času. Glavni elementi standarda so: - komunikacijska plast, ki določa skupne postopke za povpraševanje po podatkih in njihovo izmenjavo. Komunikacijski postopki so enaki za vse storitve in s tem predstavljajo infrastrukturo vmesnika (povezovanje sporočil, obravnavanje napak, vedenje ob ponastavitvi). Ponovna uporaba infrastrukture vmesnika za razne tehnične storitve zagotavlja stroškovno učinkovito izvajanje in razširitev vmesnika. o Zahteva/odziv o Objava/naročnina Naročnine določajo tip in količino podatkov za izmenjavo. - Vmesnik med kontrolnimi centri (AVMS) s funkcijami o zaščita povezave (v povezavi s časom ali potovanjem) o informacije o povezavi (v povezavi s časom) o informacije o potniku v realnem času (tabela odhodov, postanki) o splošna sporočila (storitev obveščanja o dogodkih in informacije) o informacije o voznem redu in topologija omrežja (načrtovana izmenjava podatkov) o aktivnost vozila (VIS) - vmesnik za informacije o voznem redu med kontrolnimi centri (AVMS) in informacijske sisteme s funkcijami o informacije o razporedu v realnem času o storitev referenčnih podatkov za informacije o razporedu. Nova delovna postavka bo obravnavala delo - drugih podskupin pf WG3: * SG4 podatkovni model za javni prevoz (TRANSMODEL) * SG9 omrežje in izmenjava voznega reda (NeTEx) - Obrazložitev nacionalnih zrcalnih odborov; od pojava aplikacije SIRI so se znatno povečale zahteve po informacijah s strani zainteresiranih javnih organov in predvsem odjemalcev javnega potniškega prevoza. Obstoječi nacionalni in mednarodni »standardi« (zlasti TRIDENT, RTIG in VDV-453/454), ki so bili v uporabi še pred pojavom aplikacije SIRI, so dosegli visoko raven izvajanja. Zdaj pa je prišel čas za zamenjavo starih sistemov s SIRI in CEN/TS 15531 se mora prilagoditi novim zmogljivostim. Zato je treba nujno okrepiti in izboljšati SIRI, da bo ustrezala stopnji, ki jo danes dosega upravljanje podatkov v realnem času.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.GHORYDQMDÖffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen, bezogen auf Operationen im öffentlichen Verkehr - Teil 3: Funktionelle ServiceschnittstelleTransport 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 individuelsPublic transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and tradeICS:Ta slovenski standard je istoveten z:EN 15531-3:2015SIST EN 15531-3:2015en,fr,de01-december-2015SIST EN 15531-3:2015SLOVENSKI
STANDARDSIST-TS CEN/TS 15531-3:20091DGRPHãþD
SIST EN 15531-3:2015
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 15531-3
August 2015 ICS 35.240.60 Supersedes CEN/TS 15531-3:2007English 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 réel relatives aux opérations de transport public - Partie 3 : Modules d'interface d'application individuels
Öffentlicher Verkehr - Serviceschnittstelle für 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 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, 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:
Avenue Marnix 17,
B-1000 Brussels © 2015 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15531-3:2015 ESIST EN 15531-3:2015
EN 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 .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 Matrices . 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 Service [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 . 51 8.4 StopMonitoringRequest . 53 8.5 StopMonitoringMultipleRequest . 58 8.6 StopMonitoringSubscriptionRequest . 59 8.7 StopMonitoringDelivery . 60 8.8 Using the Stop Timetable & Stop Monitoring services together . 80 9 Vehicle Monitoring Service [VM] . 81 9.1 Purpose . 81 9.2 Reference Data . 81 9.3 Capability and Permission Matrices . 81 9.4 VehicleMonitoringRequest . 83 9.5 VehicleMonitoringSubscriptionRequest . 85 9.6 VehicleMonitoringDelivery . 87 10 Connection Timetable Data Service [CT] . 96 10.1 Purpose . 96 SIST EN 15531-3:2015
EN 15531-3:2015 (E) 3 10.2 Reference Data . 97 10.3 Capability and Permission Matrices . 98 10.4 ConnectionTimetableRequest . 100 10.5 ConnectionTimetableSubscriptionRequest. 101 10.6 ConnectionTimetableDelivery . 102 11 Connection Monitoring Service [CM] . 106 11.1 Purpose . 106 11.2 Capability and Permission Matrices . 107 11.3 The ConnectionMonitoringRequest . 109 11.4 The ConnectionMonitoringSubscriptionRequest . 112 11.5 ServiceDelivery with Connection Monitoring Deliveries — Element . 113 12 General Message Service [GM] . 121 12.1 Purpose . 121 12.2 Reference Data . 122 12.3 Capability and Permission Matrices . 122 12.4 The GeneralMessageRequest . 123 12.5 The GeneralMessageSubscriptionRequest . 124 12.6 The GeneralMessageDelivery . 125 Bibliography . 129
SIST EN 15531-3:2015
EN 15531-3:2015 (E) 4 European foreword This document (EN 15531-3:2015) 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 February 2016 and conflicting national standards shall be withdrawn at the latest by February 2016. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. This document supersedes CEN/TS 15531-3:2007. This presents Part 3 of the European European Standard known as “SIRI”. SIRI provides a framework for specifying communications and data exchange protocols for organizations 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 (Part 3). — Two additional parts define additional functional services as CEN Technical Standards: — Additional data structures for additional application interface module FM (Facility Monitoring: Part 4). — Additional data structures for additional application interface module SX (Situation eXchange: Part 5). The XML schema can be downloaded from http://www.siri.org.uk/, along with available guidance on its use, example XML files, and case studies of national and local deployments. It is recognized 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. According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: 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, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 15531-3:2015
EN 15531-3:2015 (E) 5 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 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 and 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 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 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 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) 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 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 distribution 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, well 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 extensible in future. SIST EN 15531-3:2015
EN 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 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 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 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. 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 referenced 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 EN 15531-1:2015 apply. SIST EN 15531-3:2015
EN 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 that 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 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 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 Timetable 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 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 system. 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-TimetableCapabilitiesResponse message pair can be used to determine the implementation’s 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 Common 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 filtered by OPERATOR. Default is ‘true’. FilterByLineRef 1:1 xsd:boolean Whether results can be filtered by LINE. Default is ‘true’. SIST EN 15531-3:2015
EN 15531-3:2015 (E) 8 FilterByVersionRef 1:1 xsd:boolean Whether results can be filtered by TIMETABLE Version. Default is ‘true’. Request Policy RequestPolicy 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 GmlCoordinateFormat 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?
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 access control by LINE is supported. Default is ‘true’. CheckConnection-LinkRef 0:1 xsd:boolean If access control is supported, whether access control by CONNECTION link is supported. Default is ‘true’. any Extensions 0:1 xsd:any* Placeholder for user extensions.
5.2.2 Permission Matrix If the implementation supports both Capability Discovery and Access Controls, then the ProductionTimetableCapabilitiesResponse response can include the access permissions for the requestor participant to access data. Table 2 shows this. Table 2 — Production Timetable Service — Permissions ProductionTimetablePermission +Structure Permissions to use implementation of Production Timetable service. In-herit ::: 1:1 xxxService-Permissions See SIRI Part 2 for Common Permission elements. Topic OperatorPermissions 0:1 +Structure OPERATOR permissions for participant. See Part 2. LinePermissions 0:1 +Structure LINE permissions for participant. See Part 2. ConnectionLinkPermissions 0:1 +Structure CONNECTION link permissions for participant. See Part 2.
SIST EN 15531-3:2015
EN 15531-3:2015 (E) 9 5.3 ProductionTimetableRequest 5.3.1 ProductionTimetableRequest — Element The ProductionTimetableRequest states which timetables should be returned – see Table 3 below. Table 3 — ProductionTimetableRequest — Attributes ProductionTimetableRequest
+Structure Request for daily production timetables Attributes version 1:1 VersionString Version identifier of Production Timetable Service, e.g. 1.0c Endpoint Properties Request-Timestamp 1:1 xsd:dateTime See SIRI Part 2 for common properties of SIRI Functional Service Requests. Message-Identifier 0:1 Message-Qualifier Line Topic ValidityPeriod 0:1 ClosedTimestampRange-Structure Start and end of timetable validity (time window) of journeys for which schedules are to be returned. Refers to the departure time at the first stop of each VEHICLE JOURNEY. If blank the configured data horizon will be used.
Start 1:1 xsd:dateTime The (inclusive) start time.
End 1:1 xsd:dateTime The (inclusive) end time. Timetable-VersionRef 0:1 xsd:string Communicate only differences to the timetable specified by this version of the timetable. OperatorRef 0:* :lperator-Code Filter the results to include only results for the specified operator or operators. Optional SIRI capability: TopicFiltering / Bylperatorh Lines
LineDirection
LineRef 0:1 :iineCode Filter the results to include only results for the given LINE or LINEs.
DirectionRef 0:1 :airection-Code Filter the results to include only journeys for VEHICLEs running in a specific relative DIRECTION. Optional SIRI capability: TopicFiltering / Byairection. Policy Language 0:1 xml:lang Preferred language in which to return text values. Optional SIRI capability: Nationalianguageh Include-Translations 0:1 xsd:boolean Whether the producer should include any available translations of NLString text elements into multiple languages. If false elements only one value per text element will be provided. +SIRI.2.0 Default is false. Incremental-Updates 0:1 xsd:boolean Whether the producer should return the complete set of current data, or only provide updates to the last timetable returned, i.e. additions, modifications and deletions, as indicated by the TimetableVersionRef. If false each subscription response will contain the full information as specified in this request. any Extensions 0:1 xsd:any* Placeholder for user extensions.
The ProductionTimetableRequest can be used in both a direct request, and for a subscription. If used for a subscription, additional ProductionTimetableSubscriptionPolicy parameters can be specified. SIST EN 15531-3:2015
EN 15531-3:2015 (E) 10 The primary Topic term on the request is the time window for which timetables are to be returned. Additional topic filtering on LINE and timetable version is also allowed. If filtering is not specified, all LINEs known to the AVMS are transmitted. If the timetable version is
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.