1.1 Interfaces specified by this standard 1.1.1 Business context Real-time information may be exchanged between a number of different organizations, or between different systems belonging to the same organization. Key interfaces include the following: – Between public transport vehicle control centres \u2013 generally, for fleet and network management. – Between a control centre and an information provision system \u2013 generally, to provide operational information for presentation to the public. – Between information provision systems \u2013 generally, sharing information to ensure that publicly available information is complete and comprehensive. – Between information provision systems \u2013 and data aggregation systems that collect and integrate data from many different sources and different types of data supplier and then distribute it onwards. – Between information provision systems and passenger information devices such as mobile phones, web browsers, etc. Annex B describes the business context for SIRI in more detail. SIRI is intended for wide scale, distributed deployment by a wide variety of installations. In such circumstances it is often not practical to upgrade all the systems at the same time. SIRI therefore includes a formal versioning system that allows for the concurrent operation of different levels at the same time and a disciplined upgrade process. In this general framework, SIRI defines a specific set of concrete functional services. The services separate the communication protocols from the message content (\u2018functional services\u2019). This allows the same functional content to be exchanged using different transport mechanisms, and different patterns of exchange. Figure 1 below shows this diagrammatically. 1.1.2 SIRI communications SIRI provides a coherent set of functional services for exchanging data for different aspects of PT operation. A common data model, based on Transmodel 5.1, is used across all services. A communication layer defines common procedures for the requesting and exchanging of data. Within SIRI, the same general communication protocols are used for all the different concrete functional interfaces, and specify a common infrastructure for message referencing, error handling, reset behaviour and so forth. The communications layer is defined in Part 2 of the SIRI document set. To allow the most efficient use to be made of bandwidth and processing capacity, the SIRI communications architecture supports several different patterns of interaction. SIRI supports both request\/response and publish\/subscribe protocols between servers, allowing applications both to pull or to push data. The SIRI publish\/subscribe pattern of interaction follows the paradigm described in the W3C candidate standard \u2018Publish-Subscribe Notification for Web Services (WS-PubSub)\u2019. SIRI uses the same separation of concerns, and a similar terminology for Publish\/Subscribe concepts as is used in WS-PubSub. For the delivery of data in response to both requests and subscriptions, SIRI supports two common patterns of message exchange as realised in existent national systems: – one-step \u2018direct\u2019 delivery: allowing the simple rapid delivery of data; – two-step \u2018fetched\u2019 delivery: allowing a more optimised use of limited resources. 1.1.3 SIRI functional services SIRI provides specific protocols for the following functional services, defined in Part 3 of the SIRI document set: – Production Timetable (PT) Service: to send daily information on the operational timetable and associated vehicle running information. – Estimated Timetable (ET) Service: to send real-time information on timetable, including changes based on the production service and on actual running conditions. – Stop Timetable (ST) Service: to provide a stop-centric view of timetabled vehicle arrivals and departures at a designated stop. – Stop Monitoring (SM) Service: to send real-time arrival & departure information relating to a specific stop.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 4<\/td>\n | Contents Page <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | European foreword <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 1.1 Interfaces specified by this standard 1.1.1 Business context 1.1.2 SIRI communications <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | Figure 1 \u2014 Structure of SIRI: a set of optional service interface specifications using a common communications layer 1.1.3 SIRI functional services <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1.2 Use of the SIRI standard <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 1.3 Limitations on SIRI and possible future developments 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 3 Terms and definitions 3.1 Transport related terms <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | course of journey\u2013 Transmodel data system \u2013 Transmodel dated vehicle journey \u2013 Transmodel delayed \u2013 SIRI delivery variant \u2013 NeTEx destination display \u2013 Transmodel (with clarification) direction \u2013 Transmodel <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | display assignment \u2013 NeTEx distributor \u2013 SIRI \/ NeTEx distributor departure \u2013 SIRI early \u2013 SIRI \/ NeTEx estimated passing time \u2013 Transmodel event \u2013 Transmodel facility \u2013 SIRI (Conflict with NeTEx) facility condition \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | feeder \u2013 SIRI (Informal Transmodel term) feeder arrival \u2013 SIRI foreign vehicle \u2013 SIRI (Informal Transmodel Term) group of lines \u2013 NeTEx headway interval \u2013 SIRI \/ NeTEx headway SERVICE \u2013 SIRI incident \u2013Transmodel in congestion \u2013 SIRI in panic \u2013 SIRI interchange rule \u2013 NeTEx <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | journey cancellation \u2013 Transmodel journey creation \u2013 Transmodel journey meeting \u2013 Transmodel journey part \u2013 Transmodel journey pattern \u2013 Transmodel late \u2013 SIRI line \u2013 Transmodel line number \u2013 Transmodel location \u2013 Transmodel <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | local vehicle \u2013 SIRI logical display \u2013 NeTEx monitored call \u2013 SIRI monitored connection \u2013 SIRI monitored vehicle journey \u2013 Transmodel observed passing time \u2013 Transmodel notice \u2013 NeTEx passing time \u2013 Transmodel <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | occupancy \u2013 SIRI (Informal Transmodel term) on time \u2013 SIRI operating day \u2013 Transmodel passenger trip \u2013 SIRI (Informal Transmodel term) passenger information facility \u2013 Transmodel \/ NeTEx place \u2013 Transmodel point \u2013 Transmodel point in journey pattern \u2013 Transmodel prediction inaccurate \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | prediction quality level \u2013 SIRI product category \u2013 SIRI production plan \u2013 Transmodel production timetable \u2013 SIRI pt trip \u2013 Transmodel quay \u2013 IFOPT \/ NeTEx ride \u2013 Transmodel roaming \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | route \u2013 Transmodel scheduled stop point \u2013 Transmodel schedule deviation \u2013 SIRI service journey \u2013 Transmodel service journey interchange \u2013 Transmodel service pattern \u2013 Transmodel short working \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | situation \u2013 Trident \/ SIRI stop area \u2013 Transmodel stop monitoring \u2013 SIRI stop monitoring point \u2013 SIRI stop assignment \u2013 NeTEx stop order \u2013Transmodel stop place \u2013 IFOPT \/ NeTEx stop visit \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | stop visit count \u2013 SIRI target passing time \u2013 Transmodel timing point \u2013 Transmodel timetabled \u2013 Transmodel train \u2013 Transmodel train block \u2013 Transmodel train block part \u2013 Transmodel train component \u2013 Transmodel train element \u2013 Transmodel <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | train number \u2013 NeTEx vehicle journey \u2013 Transmodel vehicle monitoring \u2013 Transmodel Version \u2013 Transmodel version frame \u2013 Transmodel visit number \u2013 SIRI zone \u2013 Transmodel <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 3.2 Communications and software concepts access control \u2013 SIRI access permission \u2013 SIRI account \u2013 SIRI authentication key \u2013 SIRI built-in constraint \u2013 General Software Term capability \u2013 SIRI client \u2013 General Software Term <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | compound request \u2013 SIRI configuration \u2013 General Software Term consumer \u2013 WS-PubSub data horizon \u2013 SIRI data ready notification \u2013 SIRI data validity \u2013 SIRI delivery \u2013 SIRI direct delivery \u2013 SIRI endpoint address \u2013 WS-PubSub <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | endpoint reference \u2013 WS-PubSub end user \u2013 General Software term error condition \u2013 SIRI fetched delivery \u2013 SIRI filter \u2013 WS-PubSub heartbeat \u2013 SIRI initial termination time\u2013 WS-PubSub <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | incremental update \u2013 SIRI interface version \u2013 General Software Term intrinsic constraint \u2013 SIRI informative channel \u2013 SIRI informative message \u2013 SIRI item \u2013 SIRI lease \u2013 WS-PubSub <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | life sign \u2013 SIRI message reference \u2013 WS-PubSub metadata \u2013 General Software Term multipart despatch \u2013 SIRI namespace \u2013 General Software Term notification \u2013 WS-PubSub notification consumer \u2013 WS-PubSub <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | notification producer \u2013 WS-PubSub notification broker \u2013 WS-PubSub participant \u2013 SIRI participant reference \u2013 SIRI payload \u2013 SIRI producer \u2013 WS-PubSub provisioning \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | publish-subscribe \u2013 WS-PubSub publisher registration \u2013 WS-PubSub publisher \u2013 WS-PubSub request \u2013 General Software Term requestor \u2013 General Software Term schema validation \u2013 XML sensitivity threshold \u2013 SIRI server \u2013 General Software Term service \u2013 WS-PubSub <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | service layer \u2013 General Software Term service participant \u2013 SIRI siri functional Service \u2013 SIRI situation \u2013 WS-PubSub subscriber \u2013 WS-PubSub subscription \u2013 WS-PubSub subscriber channel \u2013 SIRI <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | subscriber reference \u2013 SIRI subscription manager \u2013 WS-PubSub subscription reference \u2013 WS-PubSub subscription request \u2013 WS-PubSub subscription response \u2013 WS-PubSub subscription policy \u2013 WS-PubSub service subscription request \u2013 SIRI subscription termination \u2013 WS-PubSub <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | topic \u2013 WS-PubSub transport layer \u2013 SIRI ws-resource \u2013 WS-PubSub 4 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 5 Types of reference data used in SIRI 5.1 General <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Table 1 \u2014 Data References for SIRI <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 5.2 Date and time format 5.3 Location coordinate system <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 5.4 National language of text elements 5.4.1 General 5.4.2 Model 5.4.3 Namespace and scope 5.5 Participant (information provider) identification 5.5.1 General 5.5.2 Model 5.5.3 Namespace and scope 5.6 Participant pair identification (service participant pair code) 5.6.1 General <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 5.6.2 Model 5.6.3 Namespace and scope 5.7 Point and place references 5.7.1 General Table 2\u2014 Examples of Point and Place Reference Scope and models 5.7.2 Global scope, uniform point model 5.7.3 Participant scope, uniform point model 5.7.4 Participant scope, alternative point models <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | Table 3 \u2014 Examples of Point \/ Place References and Services 5.7.5 Model 5.7.6 Namespace and scope <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 5.8 Vehicle journey references 5.8.1 General 5.8.2 Model 5.8.3 Namespace and scope <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 5.9 Line, and direction references 5.9.1 General 5.9.2 Model 5.9.3 Namespace and scope 5.10 Stop sequence references and circular journeys 5.10.1 General 5.10.2 Model <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | Table 4 \u2014 Example of Stop Sequence, order and Visit Numbers <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | Table 5 \u2014 Usages of Visit Numbers 5.10.3 Namespace and scope 5.11 Schedule version references 5.11.1 General 5.11.2 Model 5.11.3 Namespace and scope 5.12 Product category references 5.12.1 General <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 5.12.2 Model 5.12.3 Namespace and scope 5.12.4 Recommended values 5.12.4.1 General 5.12.4.2 Transport submode (TPEG Pti01 transport_mode transport_submode) Table 6 \u2014 Product Category: Transport Submodes <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 5.12.4.3 Rail submode (TPEG Pti02 railway_type) Table 7 \u2014 Product Category: Rail Submodes 5.12.4.4 Coach submode (TPEG Pti03 coach_type) Table 8 \u2014 Product Category: Coach Submodes <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 5.12.4.5 Metro submode (TPEG Pti4 urban_railway_type \/ Loc11 metro rail link) Table 9 \u2014 Product Category: Metro Submodes 5.12.4.6 Bus submode (TPEG Pti05 bus_type) Table 10 \u2014 Product Category: Bus Submodes <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 5.12.4.7 Air submode (TPEG Pti08 air_type) Table 11 \u2014 Product Category: Air Submodes 5.13 Vehicle feature references 5.13.1 General 5.13.2 Model 5.13.3 Namespace and scope 5.13.4 Recommended values <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 5.14 Service features 5.14.1 General Table 12 \u2014 Some Recommended Vehicle Feature Values <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 5.14.2 Namespace and scope 5.14.3 Recommended values <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 5.15 Situation references 5.15.1 General 5.15.2 Model 5.15.3 Namespace and scope 5.16 Summary of data reference scopes <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | Table 13 \u2014 Possible Scopes for References 5.17 Transmodel compliant models <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 5.18 Modelling vehicle journeys in SIRI 5.18.1 General Figure 2 \u2014 UML Diagram of SIRI Abstract Journey Model <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | Figure 3 \u2014 UML Diagram of Concrete Journey Model <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | Figure 4 \u2014 UML Diagram of Concrete Journey Models showing Inheritance of Properties <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 5.18.2 Element equivalences and inheritance \u2013 timetable & journey Table 14 \u2014 Inheritance of Timetable Properties <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | 5.18.3 Element equivalences and inheritance \u2013 stop call Table 15 \u2014 Inheritance of Call Properties <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | 5.18.4 Element equivalences and inheritance \u2013 service interchange <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | Table 16 \u2014 Inheritance of Call Properties 5.18.5 Passing times Table 17 \u2014 Transmodel Passing Time Terminology <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 6 Notation 6.1 Representation of XML model elements in text 6.2 Representing relationships in SIRI 6.3 Notation for XML model structures of SIRI messages 6.3.1 General <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | Table 18 \u2014 Example of XML Structure Notation 6.3.2 Organizational group label 6.3.3 Element name <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | 6.3.4 Multiplicity & choice (min:max) 6.3.5 Data type 6.3.6 Description 6.4 Notation for diagrams <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | Annex A (informative) Checklist for Implementing SIRI A.1 Usage of the DSRC application layer A.2 Legal and commercial Issues A.3 Functional aspects A.3.1 Main scope A.3.1.1 General A.3.1.2 General Capabilities <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | A.3.1.3 Service capabilities A.3.2 Service configuration A.3.2.1 Security & network A.3.2.2 Service context A.3.2.3 Access control A.3.2.4 Data quality control A.3.3 Reference data A.3.3.1 General <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | A.3.3.2 General reference data A.3.3.3 Service specific reference data A.3.4 Error handling A.4 Operational aspects A.4.1 Systems management <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | A.4.2 Provisioning <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | Annex B (informative) Business Context B.1 Purpose of this section <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | B.2 Business model B.2.1 Passenger transport operations B.2.1.1 General B.2.1.2 Mobile vehicles B.2.1.3 Infrastructure <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | B.2.1.4 Passengers B.2.1.5 Money B.2.1.6 Schedules B.2.1.7 Control centres B.2.1.8 Journey planners <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | B.2.2 Organizations B.3 Use of information in public transport B.3.1 Overview B.3.2 Data ownership B.3.2.1 General <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | B.3.2.2 Transport infrastructure B.3.2.3 PT infrastructure <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | B.3.2.4 PTV schedules B.3.2.5 Integrated PT plan B.3.2.6 Real-Time PT status <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | B.3.2.7 Real-Time transport infrastructure status B.3.3 Temporal considerations B.3.3.1 General B.3.3.2 Preparation of a new timetable B.3.3.3 Adjustments to a timetable B.3.3.4 Production timetable B.3.3.5 Estimated timetable <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | B.3.3.6 Reporting and analysis B.3.4 Information security B.3.5 Regulatory issues <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | B.4 Use Cases for this standard B.4.1 Introduction B.4.2 Use case: provision of service information to passengers B.4.2.1 User requirements <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | Figure B.1 \u2014 Two models of passenger information provision B.4.2.2 Service requirements \u2013 SIRI Stop Monitoring (SM) <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | B.4.2.3 Service requirements \u2013 SIRI Vehicle Monitoring (VM) B.4.3 Use case: journey planning B.4.3.1 User requirements B.4.3.2 Service requirements \u2013 SIRI Production Timetable (PT) B.4.3.3 Service requirements \u2013 SIRI Estimated Timetable (ET) <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | B.4.4 Use case: facilitating connections for passengers B.4.4.1 User requirements B.4.4.2 Service requirements \u2013 SIRI Connection Timetable (CT) B.4.4.3 Service requirements \u2013 SIRI Connection Monitoring (CM) <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | B.4.5 Use case: fleet and network management B.4.5.1 User requirements B.4.5.2 Service requirements \u2013 SIRI Vehicle Monitoring (VM) B.4.6 Use case: general business communications B.4.6.1 User requirements B.4.6.2 Service requirements \u2013 SIRI General Message (GM) B.5 SIRI System Model B.5.1 Modularization <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | B.5.2 PT Infrastructure Management Module B.5.3 Transport Infrastructure Management Module Figure B.2 \u2014 Generic model of PT operations, showing exchange points for RTI and the SIRI services available for these roles B.5.4 PT Scheduling Module <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | B.5.5 PT Integration Module B.5.6 Traffic Management Control Centre B.5.7 PT Operational Control <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | B.5.8 PT Journey Planner B.5.9 Passenger Information <\/td>\n<\/tr>\n | ||||||
| 86<\/td>\n | Annex C (informative) Background and Mapping of Some Current Implementations to SIRI C.1 Introduction C.2 SIRI origins C.2.1 VDV453\/VDV454 C.2.2 TRIDENT <\/td>\n<\/tr>\n | ||||||
| 87<\/td>\n | C.2.3 RTIG-XML <\/td>\n<\/tr>\n | ||||||
| 88<\/td>\n | C.2.4 CEN TC278 WG3 SG7 <\/td>\n<\/tr>\n | ||||||
| 89<\/td>\n | Table C.1 \u2014 List of SIRI Functional Services with RTIG and VDV equivalent services currently deployed C.3 Deployment Example \u2013 Berlin Figure C.1 \u2014 Physical deployment example \u2013 Berlin <\/td>\n<\/tr>\n | ||||||
| 90<\/td>\n | C.4 Deployment Example \u2013 Hamburg Figure C.2 \u2014 Physical deployment example \u2013 Hamburg C.5 Deployment Example \u2013 West Yorkshire <\/td>\n<\/tr>\n | ||||||
| 91<\/td>\n | Figure C.3 \u2014 Physical deployment example \u2013 West Yorkshire C.6 Deployment Example \u2013 Czech Republic Figure C.4 \u2014 Physical deployment example \u2013 Czech Republic <\/td>\n<\/tr>\n | ||||||
| 92<\/td>\n | C.7 Deployment Example \u2013 Copenhagen Figure C.5 \u2014 Physical deployment example \u2013 Copenhagen <\/td>\n<\/tr>\n | ||||||
| 93<\/td>\n | C.8 Deployment example \u2013 \u00cele-de-France Figure C.6 \u2014 Physical deployment example \u2013 \u00cele-de-France <\/td>\n<\/tr>\n | ||||||
| 94<\/td>\n | Figure C.7 \u2014 Targeted physical deployment example \u2013 \u00cele-de-France <\/td>\n<\/tr>\n | ||||||
| 95<\/td>\n | C.9 SIRI Equivalences C.9.1 GTFS-real-time feeds Table C.2 \u2014 GTFS & SIRI Functional Service Equivalences <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Public transport. Service interface for real-time information relating to public transport operations – Context and framework<\/b><\/p>\n |