1、Public transport Service interface for real-time information relating to public transport operations Part 5: Functional service interfaces situation exchange: Situation Exchange PD CEN/TS 15531-5:2016 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National foreword
2、 This Published Document is the UK implementation of CEN/TS 15531-5:2016. It supersedes DD CEN/TS 15531-5:2011 which is withdrawn. The UK participation in its preparation was entrusted to Technical Committee EPL/278, Intelligent transport systems. A list of organizations represented on this committe
3、e can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 91099 9 ICS 35.240
4、.60 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Document was published under the authority of the Standards Policy and Strategy Committee on 31 May 2016. Amendments/corrigenda issued since publication Date Text affected PUBLISHED DOCUMENT PD CEN/T
5、S 15531-5:2016 TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 15531-5 May 2016 ICS 35.240.60 Supersedes CEN/TS 15531-5:2011 English Version Public transport - Service interface for real-time information relating to public transport operations - Part 5: Functional serv
6、ice interfaces situation exchange: Situation Exchange Transport public - Interface de service pour les informations en temps rel relatives aux oprations de transport public - Partie 5: Service dinterface fonctionnelle - change de ltat de lexploitation et de son contexte ffentlicher Verkehr - Dienste
7、schnittstelle fr den Echtzeitaustausch von Betriebsinformationen des PNV (SIRI) - Teil 5: Funktionelle Serviceschnittstelle: Situativer Austausch This Technical Specification (CEN/TS) was approved by CEN on 25 February 2016 for provisional application. The period of validity of this CEN/TS is limite
8、d 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
9、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 standard
10、s 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, Sloven
11、ia, 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 2016 CEN All rights of exploitation in any form and by any means reserved w
12、orldwide for CEN national Members. Ref. No. CEN/TS 15531-5:2016 E PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 2 Contents Page European foreword . 6 Introduction 8 1 Scope . 10 2 Normative references . 11 3 Terms and definitions 11 4 Symbols and abbreviations 16 5 Situations as Software Entities 16
13、 5.1 General . 16 5.2 Structured Situations 17 5.3 Distributed Situation processing 18 5.3.1 Identity and Write-Only Updates 18 5.3.2 Currency and the Situation Life Cycle . 19 5.3.3 Representational model for Situation Elements . 20 5.3.4 Update chains Causal chains . 21 5.3.5 Cross-referencing Sit
14、uations Causal chains 22 5.3.6 Branching and distributed updates . 22 5.3.7 Archiving . 24 5.4 Summary of Situation Management 24 5.4.1 General . 24 5.4.2 Situation Identity 24 5.4.3 Situation Life Cycle 25 5.4.4 Situation Update Content 25 5.4.5 Example of identifier allocation 26 5.4.6 Date time s
15、tamps as identifiers. 26 5.5 Interoperability of Situation management systems 26 5.5.1 General . 26 5.5.2 Datex2 Interoperability . 27 5.5.3 TPEG Interoperability 28 5.5.4 Communications Bandwidth 28 6 The Situation Model 28 6.1 General . 28 6.2 Representing a PT Situation in SIRI-SX 29 6.2.1 Summar
16、y of PT Situation model . 29 6.2.2 PT Situation Element Body . 30 6.2.3 PT Situation Body Details 31 6.2.4 PT Situation Reason 33 6.2.5 Situation Consequence . 36 6.2.6 The PT AffectsScope 37 6.3 Representing a Road Situation in SIRI-SX . 43 6.3.1 Summary of Road Situation model 43 6.3.2 Road Situat
17、ion Element Body 45 6.3.3 Common Accessibility . 45 6.3.4 Publishing Actions . 46 6.3.5 Common Types 47 PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 3 7 Situation Exchange Service SX 54 7.1 Purpose. 54 7.2 Description 54 7.3 Reference Data . 54 7.4 Capability and Permission Matrices 54 7.4.1 Capabi
18、lity Matrix . 54 7.4.2 Permission Matrix 56 7.5 UML Diagrammatic Representation . 56 7.5.1 General . 56 7.5.2 UML Detailed Diagram of SituationExchangeRequest . 57 7.5.3 UML Diagram of SituationExchangeDelivery - Summary . 59 7.5.4 UML Diagram of SituationExchangeDelivery - Detail 60 7.5.5 UML Diagr
19、am of SituationContext 60 7.6 SituationExchangeRequest 61 7.6.1 SituationExchangeRequest Definition 61 7.6.2 SituationStatusFilter Definition 63 7.6.3 SituationNetworkFilter Definition . 64 7.6.4 SituationStopPlaceFilter Definition . 64 7.6.5 SituationJourneyFilter Definition . 65 7.6.6 SituationPla
20、ceFilter Definition 65 7.6.7 SituationRoadFilter Definition 65 7.6.8 AccessibilityNeedFilter Definition 66 7.6.9 SituationExchangeRequest Example . 66 7.7 SituationExchangeSubscriptionRequest 66 7.7.1 SituationExchangeSubscriptionRequest Definition . 66 7.7.2 SituationExchangeSubscriptionRequest Exa
21、mple 67 7.8 SituationExchangeDelivery . 67 7.8.1 ServiceDelivery with a SituationExchangeDelivery . 68 7.8.2 SituationExchangeDelivery Element . 68 7.8.3 SituationContext Element 68 7.8.4 SituationNetworkContext Element. 69 7.8.5 PtSituationElement 69 7.8.6 RoadSituationElement . 128 8 SituationExch
22、angeDelivery Examples - SituationExchangeDelivery PT Examples . 130 A.1 General 133 A.2 Classes 133 A.3 Enumerations 133 A.4 Groups 133 A.5 Notes . 133 A.6 Relationships . 133 A.7 Use of Colour 134 A.8 Serialisation: Containment and Reference . 134 A.9 Alternative Representations of XML Structures i
23、n UML 135 A.10 XML Fragment for Example 137 A.11 Order of Attributes 138 A.12 Direction of Reading . 138 PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 4 A.13 Simple Data Types 138 A.14 Reusable Complex Data Types . 138 B.1 SIRI-SX and Datex2 139 C.1 General . 142 C.2 Use Cases: Capture and Originati
24、on of Situations 142 C.3 CAPT#01 Situations entered manually by operator staff 142 C.4 CAPT#02 Situations updated manually by operator staff . 142 C.5 CAPT#03 Situations being generated automatically from a situation analyser . 143 C.6 CAPT#04 Situations arising from Facility Monitoring (e.g. lift f
25、ailure) 143 C.7 CAPT#05 Situations arising from Control Actions (e.g. short running, platform change) . 143 C.8 CAPT#06 Situations supplied automatically from a related PT network (e.g. rail incidents being fed to bus system) in both SIRI and TPEG formats . 143 C.9 CAPT#07 Situations supplied automa
26、tically from a related Road network (e.g. road situations being fed to bus system) Datex2 formats . 143 C.10 CAPT#08 Road work affecting bus lanes . 143 C.11 CAPT#09 Parking not available at an interchange to PT . 143 C.12 CAPT#10 Weather or non-network specific Situation or event 144 C.13 CAPT#11 C
27、ross referencing Situations with previous Situations . 144 C.14 CAPT#12 Workflow for verification, validation and editorial correction . 144 C.15 CAPT#13 Providing of collective guidance of passengers . 144 C.16 CAPT#14 Audit trails, retrospectives and process views 144 C.17 Use Cases: Relating Situ
28、ations to other SIRI services 144 C.18 XREF#01 Problem affecting a specific vehicle journey 145 C.19 XREF#02 Problem at a stop place affecting some or all journeys for some or all modes . 145 C.20 XREF#03 Problem affecting a whole line or a section of a line between two stop places 145 C.21 XREF#04
29、Problems affecting an interchange . 145 C.22 XREF#05 Problem affecting a whole network . 145 C.23 XREF#06 Disruption (e.g. partial blockage) or degradation (e.g. crowding) of normal travel . 146 C.24 XREF#07 Problems affecting particular classes of users e.g. impaired mobility 146 C.25 Use Cases: On
30、wards Distribution to other systems (e.g. in TPEG and Datex2) 146 C.26 DIST#01 Distribution of Situations to displays . 146 C.27 DIST#02 Distribution of Situations to external information services, e.g. broadcasters 146 C.28 DIST#03 Distribution of Situations to staff . 146 C.29 DIST#04 Distribution
31、 of Situations to alerts and travel angels 147 PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 5 C.30 DIST#05 Projection of Situations on maps . 147 C.31 DIST#06 Distribution of Situations to journey planners 147 C.32 DIST#07 Distribution of Situations to personal navigators and smart devices 147 C.33
32、 DIST#08 Distribution of Situations to other incident management systems 147 C.34 DIST#09 Distribution of updates to existing Situations 147 C.35 DIST#10 Aging of Situations and updates . 148 D.1 Mapping of SIRI-SX elements to GTFS-realtime 149 D.2 Mapping of SIRI-SX Journey Condition to GTFS-realti
33、me ScheduleRelationship . 150 D.3 Mapping of SIRI-SX Situation Categories to GTFS-realtime Cause . 150 D.4 Mapping of SIRI-SX Service Conditions to GTFS Real-time Effect . 151 Bibliography 152 PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 6 European foreword This document (CEN/TS 15531-5:2016) has b
34、een prepared by Technical Committee CEN/TC 278 “Intelligent transport systems”, the secretariat of which is held by NEN. 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 identify
35、ing any or all such patent rights. This document supersedes CEN/TS 15531-5:2011. The 15531 series consists of the following parts, under the general title Public transport - Service interface for real-time information relating to public transport operations Part 1: Context and framework Part 2: Comm
36、unications Part 3: Functional service interfaces Part 4: Functional service interfaces: Facility Monitoring Part 5: Functional service interfaces - Situation exchange The following corrections and modifications have been in this new version of CEN/TS 15531-5: Correct spec to include projection attri
37、butes for affectedStopPlaceComponent Document FacilityRef as part of request Document Access Mode as part of request Document Scope as part of request Document RoadFilter and Accessibility need filter as part of request Correct Documentation of AffectedRoads as part of Delivery Correct Documentation
38、 of capability Matrix Correct Documentation of Reason codes Added Annex D to Doc on GTFS real-time mapping StopMonitoringDelivery upgrade to DatexII All changes are available in the file ReadMe.txt which is accompanying the XSD-schema, available from http:/www.siri.org.uk. According to the CEN-CENEL
39、EC Internal Regulations, the national standards organizations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary
40、, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 7 Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. PD CEN/TS 15531-5:2016CEN/TS 15531-5:2016 (E) 8 Introduction
41、 Public transport services rely increasingly on information systems to ensure reliable, efficient operation and widely accessible, accurate passenger information. Well-defined, open interfaces have a crucial role in improving the economic and technical viability of Public Transport Information Syste
42、ms 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, connecting diverse systems; rather than as monolithic proprietary systems from a single supplier. Interfaces also allo
43、w the systematic automated testing of each functional module, vital for managing the complexity of increasing large and dynamic systems. Furthermore, with a well- defined, version interface, individual functional modules can be replaced or evolved, without unexpected breakages of obscurely dependent
44、 function. The SIRI framework is a European Technical Specification that provides a specification for a number of functional interfaces that allow public transport data of specific types to be exchanged readily using structured interfaces. This further Technical Specification specifies an additional
45、 SIRI functional service to exchange incident and event information about disruptions to public transport between servers containing real-time public transport vehicle or journey time data. These include the control centres of transport operators as well as information systems that deliver passenger
46、 travel information services. This document describes the SIRI Situation Exchange service, one of a modular set of services for the exchange of Real-time information. The Situation Exchange service (SIRI-SX) is concerned with the exchange of planned events and unplanned incident data among systems,
47、including incident capture, real-time management and dissemination systems. It is an additional functional service based on the European Technical Specification known as “SIRI” Service Interface for Real-time Information. SIRI provides a framework for specifying communications and data exchange prot
48、ocols for organisations wishing to exchange Real-time Information (RTI) relating to public transport operations. The specification for the base SIRI framework on which SIRI-SX is built is presented in three parts: a) context and framework, including background, scope and role, normative references,
49、terms and definitions, symbols and abbreviations, business context and use cases (SIRI Part 1: EN 15531-1); b) the mechanisms to be adopted for data exchange communications links (SIRI Part 2: EN 15531-2); c) data structures for a series of individual application interface modules (SIRI Part 3: EN 15531-3): 1) Production Timetable (SIRI-PT); 2) Estimated Timetable (SIRI-ET); 3) Stop Timetable (SIRI-ST); 4) Stop Monitoring (SIRI-SM); 5) Vehicle Monitoring (SIRI-VM); 6) Connection Timetable (SIRI-CT); 7) Connection Monitoring (SI
