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 – generally, for fleet and network management. – Between a control centre and an information provision system – generally, to provide operational information for presentation to the public. – Between information provision systems – generally, sharing information to ensure that publicly available information is complete and comprehensive. – Between information provision systems – 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 (‘functional services’). 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 ‘Publish-Subscribe Notification for Web Services (WS-PubSub)’. 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 ‘direct’ delivery: allowing the simple rapid delivery of data; – two-step ‘fetched’ 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.

PDF Catalog

PDF Pages	PDF Title
4	Contents Page
6	European foreword
7	Introduction
9	1 Scope 1.1 Interfaces specified by this standard 1.1.1 Business context 1.1.2 SIRI communications
10	Figure 1 — Structure of SIRI: a set of optional service interface specifications using a common communications layer 1.1.3 SIRI functional services
11	1.2 Use of the SIRI standard
12	1.3 Limitations on SIRI and possible future developments 2 Normative references
13	3 Terms and definitions 3.1 Transport related terms
15	course of journey– Transmodel data system – Transmodel dated vehicle journey – Transmodel delayed – SIRI delivery variant – NeTEx destination display – Transmodel (with clarification) direction – Transmodel
16	display assignment – NeTEx distributor – SIRI / NeTEx distributor departure – SIRI early – SIRI / NeTEx estimated passing time – Transmodel event – Transmodel facility – SIRI (Conflict with NeTEx) facility condition – SIRI
17	feeder – SIRI (Informal Transmodel term) feeder arrival – SIRI foreign vehicle – SIRI (Informal Transmodel Term) group of lines – NeTEx headway interval – SIRI / NeTEx headway SERVICE – SIRI incident –Transmodel in congestion – SIRI in panic – SIRI interchange rule – NeTEx
18	journey cancellation – Transmodel journey creation – Transmodel journey meeting – Transmodel journey part – Transmodel journey pattern – Transmodel late – SIRI line – Transmodel line number – Transmodel location – Transmodel
19	local vehicle – SIRI logical display – NeTEx monitored call – SIRI monitored connection – SIRI monitored vehicle journey – Transmodel observed passing time – Transmodel notice – NeTEx passing time – Transmodel
20	occupancy – SIRI (Informal Transmodel term) on time – SIRI operating day – Transmodel passenger trip – SIRI (Informal Transmodel term) passenger information facility – Transmodel / NeTEx place – Transmodel point – Transmodel point in journey pattern – Transmodel prediction inaccurate – SIRI
21	prediction quality level – SIRI product category – SIRI production plan – Transmodel production timetable – SIRI pt trip – Transmodel quay – IFOPT / NeTEx ride – Transmodel roaming – SIRI
22	route – Transmodel scheduled stop point – Transmodel schedule deviation – SIRI service journey – Transmodel service journey interchange – Transmodel service pattern – Transmodel short working – SIRI
23	situation – Trident / SIRI stop area – Transmodel stop monitoring – SIRI stop monitoring point – SIRI stop assignment – NeTEx stop order –Transmodel stop place – IFOPT / NeTEx stop visit – SIRI
24	stop visit count – SIRI target passing time – Transmodel timing point – Transmodel timetabled – Transmodel train – Transmodel train block – Transmodel train block part – Transmodel train component – Transmodel train element – Transmodel
25	train number – NeTEx vehicle journey – Transmodel vehicle monitoring – Transmodel Version – Transmodel version frame – Transmodel visit number – SIRI zone – Transmodel
26	3.2 Communications and software concepts access control – SIRI access permission – SIRI account – SIRI authentication key – SIRI built-in constraint – General Software Term capability – SIRI client – General Software Term
27	compound request – SIRI configuration – General Software Term consumer – WS-PubSub data horizon – SIRI data ready notification – SIRI data validity – SIRI delivery – SIRI direct delivery – SIRI endpoint address – WS-PubSub
28	endpoint reference – WS-PubSub end user – General Software term error condition – SIRI fetched delivery – SIRI filter – WS-PubSub heartbeat – SIRI initial termination time– WS-PubSub
29	incremental update – SIRI interface version – General Software Term intrinsic constraint – SIRI informative channel – SIRI informative message – SIRI item – SIRI lease – WS-PubSub
30	life sign – SIRI message reference – WS-PubSub metadata – General Software Term multipart despatch – SIRI namespace – General Software Term notification – WS-PubSub notification consumer – WS-PubSub
31	notification producer – WS-PubSub notification broker – WS-PubSub participant – SIRI participant reference – SIRI payload – SIRI producer – WS-PubSub provisioning – SIRI
32	publish-subscribe – WS-PubSub publisher registration – WS-PubSub publisher – WS-PubSub request – General Software Term requestor – General Software Term schema validation – XML sensitivity threshold – SIRI server – General Software Term service – WS-PubSub
33	service layer – General Software Term service participant – SIRI siri functional Service – SIRI situation – WS-PubSub subscriber – WS-PubSub subscription – WS-PubSub subscriber channel – SIRI
34	subscriber reference – SIRI subscription manager – WS-PubSub subscription reference – WS-PubSub subscription request – WS-PubSub subscription response – WS-PubSub subscription policy – WS-PubSub service subscription request – SIRI subscription termination – WS-PubSub
35	topic – WS-PubSub transport layer – SIRI ws-resource – WS-PubSub 4 Symbols and abbreviations
36	5 Types of reference data used in SIRI 5.1 General
37	Table 1 — Data References for SIRI
38	5.2 Date and time format 5.3 Location coordinate system
39	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
40	5.6.2 Model 5.6.3 Namespace and scope 5.7 Point and place references 5.7.1 General Table 2— 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
41	Table 3 — Examples of Point / Place References and Services 5.7.5 Model 5.7.6 Namespace and scope
42	5.8 Vehicle journey references 5.8.1 General 5.8.2 Model 5.8.3 Namespace and scope
43	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
44	Table 4 — Example of Stop Sequence, order and Visit Numbers
45	Table 5 — 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
46	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 — Product Category: Transport Submodes
47	5.12.4.3 Rail submode (TPEG Pti02 railway_type) Table 7 — Product Category: Rail Submodes 5.12.4.4 Coach submode (TPEG Pti03 coach_type) Table 8 — Product Category: Coach Submodes
48	5.12.4.5 Metro submode (TPEG Pti4 urban_railway_type / Loc11 metro rail link) Table 9 — Product Category: Metro Submodes 5.12.4.6 Bus submode (TPEG Pti05 bus_type) Table 10 — Product Category: Bus Submodes
49	5.12.4.7 Air submode (TPEG Pti08 air_type) Table 11 — 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
50	5.14 Service features 5.14.1 General Table 12 — Some Recommended Vehicle Feature Values
51	5.14.2 Namespace and scope 5.14.3 Recommended values
52	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
53	Table 13 — Possible Scopes for References 5.17 Transmodel compliant models
54	5.18 Modelling vehicle journeys in SIRI 5.18.1 General Figure 2 — UML Diagram of SIRI Abstract Journey Model
55	Figure 3 — UML Diagram of Concrete Journey Model
56	Figure 4 — UML Diagram of Concrete Journey Models showing Inheritance of Properties
57	5.18.2 Element equivalences and inheritance – timetable & journey Table 14 — Inheritance of Timetable Properties
59	5.18.3 Element equivalences and inheritance – stop call Table 15 — Inheritance of Call Properties
60	5.18.4 Element equivalences and inheritance – service interchange
61	Table 16 — Inheritance of Call Properties 5.18.5 Passing times Table 17 — Transmodel Passing Time Terminology
62	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
63	Table 18 — Example of XML Structure Notation 6.3.2 Organizational group label 6.3.3 Element name
64	6.3.4 Multiplicity & choice (min:max) 6.3.5 Data type 6.3.6 Description 6.4 Notation for diagrams
65	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
66	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
67	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
68	A.4.2 Provisioning
69	Annex B (informative) Business Context B.1 Purpose of this section
70	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
71	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
72	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
73	B.3.2.2 Transport infrastructure B.3.2.3 PT infrastructure
74	B.3.2.4 PTV schedules B.3.2.5 Integrated PT plan B.3.2.6 Real-Time PT status
75	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
76	B.3.3.6 Reporting and analysis B.3.4 Information security B.3.5 Regulatory issues
77	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
78	Figure B.1 — Two models of passenger information provision B.4.2.2 Service requirements – SIRI Stop Monitoring (SM)
79	B.4.2.3 Service requirements – SIRI Vehicle Monitoring (VM) B.4.3 Use case: journey planning B.4.3.1 User requirements B.4.3.2 Service requirements – SIRI Production Timetable (PT) B.4.3.3 Service requirements – SIRI Estimated Timetable (ET)
80	B.4.4 Use case: facilitating connections for passengers B.4.4.1 User requirements B.4.4.2 Service requirements – SIRI Connection Timetable (CT) B.4.4.3 Service requirements – SIRI Connection Monitoring (CM)
81	B.4.5 Use case: fleet and network management B.4.5.1 User requirements B.4.5.2 Service requirements – SIRI Vehicle Monitoring (VM) B.4.6 Use case: general business communications B.4.6.1 User requirements B.4.6.2 Service requirements – SIRI General Message (GM) B.5 SIRI System Model B.5.1 Modularization
82	B.5.2 PT Infrastructure Management Module B.5.3 Transport Infrastructure Management Module Figure B.2 — Generic model of PT operations, showing exchange points for RTI and the SIRI services available for these roles B.5.4 PT Scheduling Module
83	B.5.5 PT Integration Module B.5.6 Traffic Management Control Centre B.5.7 PT Operational Control
84	B.5.8 PT Journey Planner B.5.9 Passenger Information
86	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
87	C.2.3 RTIG-XML
88	C.2.4 CEN TC278 WG3 SG7
89	Table C.1 — List of SIRI Functional Services with RTIG and VDV equivalent services currently deployed C.3 Deployment Example – Berlin Figure C.1 — Physical deployment example – Berlin
90	C.4 Deployment Example – Hamburg Figure C.2 — Physical deployment example – Hamburg C.5 Deployment Example – West Yorkshire
91	Figure C.3 — Physical deployment example – West Yorkshire C.6 Deployment Example – Czech Republic Figure C.4 — Physical deployment example – Czech Republic
92	C.7 Deployment Example – Copenhagen Figure C.5 — Physical deployment example – Copenhagen
93	C.8 Deployment example – Île-de-France Figure C.6 — Physical deployment example – Île-de-France
94	Figure C.7 — Targeted physical deployment example – Île-de-France
95	C.9 SIRI Equivalences C.9.1 GTFS-real-time feeds Table C.2 — GTFS & SIRI Functional Service Equivalences
96	Bibliography

Published By	Publication Date	Number of Pages
BSI	2015	98


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Title	Public transport. Service interface for real-time information relating to public transport operations – Context and framework
Replaces	DD CEN/TS 15531-1:2007
Publisher	BSI
Committee	EPL/278
Pages	98
Publication Date	2015-08-31
Withdrawn Date	2022-09-05
Replaced By	BS EN 15531-1:2022
ISBN	978 0 580 83397 7
Standard Number	BS EN 15531-1:2015
Identical National Standard Of	EN 15531-1:2015
Descriptors	Interfaces (data processing), Data transmission, Transportation, Railways, Information exchange, Messages, Timetables, Information, Passenger transport, Rail transport, Road transport, Display devices
ICS Codes	35.240.60 - IT applications in transport

BS EN 15531-1:2015

PDF Catalog

Related products

BS EN 15531-1:2015 – TC:2020 Edition

BSI 21/30437183 DC:2021 Edition