EN 15531-1:2015
Withdrawn
A Withdrawn Standard is one, which is removed from sale, and its unique number can no longer be used. The Standard can be withdrawn and not replaced, or it can be withdrawn and replaced by a Standard with a different number.
Public transport - Service interface for real-time information relating to public transport operations - Part 1: Context and framework
29-02-2016
26-08-2015
European foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviations
5 Types of reference data used in SIRI
6 Notation
Annex A (informative) - Checklist for Implementing SIRI
Annex B (informative) - Business Context
Annex C (informative) - Background and Mapping of Some
Current Implementations to SIRI
Bibliography
1.1Interfaces specified by this standard
1.1.1Business 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.2SIRI 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.3SIRI 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.
Committee |
CEN/TC 278
|
DevelopmentNote |
Supersedes CEN/TS 15531-1 & PREN 15531-1. (09/2015)
|
DocumentType |
Standard
|
PublisherName |
Comite Europeen de Normalisation
|
Status |
Withdrawn
|
Supersedes |
Standards | Relationship |
DS EN 15531-1 : 2015 | Identical |
ONORM EN 15531-1 : 2015 | Identical |
NBN EN 15531-1 : 2015 | Identical |
UNI EN 15531-1 : 2015 | Identical |
NF EN 15531-1 : 2015 | Identical |
I.S. EN 15531-1:2015 | Identical |
NS EN 15531-1 : 2015 | Identical |
NEN EN 15531-1 : 2015 | Identical |
UNE-EN 15531-1:2015 | Identical |
BS EN 15531-1:2015 | Identical |
PN EN 15531-1 : 2015 | Identical |
DIN EN 15531-1:2015-12 | Identical |
PNE-prEN 15531-1 | Identical |
CEN/TR 17143:2017 | Intelligent transport systems - Standards and actions necessary to enable urban infrastructure coordination to support Urban-ITS |
BS EN 12896-3:2016 | Public transport. Reference data model Timing information and vehicle scheduling |
PREN 12896-2 : DRAFT 2015 | ROAD TRANSPORT AND TRAFFIC TELEMATICS - PUBLIC TRANSPORT REFERENCE DATA MODEL - PART 2: PUBLIC TRANSPORT NETWORK |
CEN/TS 16614-3:2016 | Public transport - Network and Timetable Exchange (NeTEx) - Part 3: Public transport fares exchange format |
CEN/TS 15531-5:2016 | Public transport ‐ Service interface for real‐time information relating to public transport operations ‐ Part 5: Functional service interfaces situation exchange: Situation Exchange |
EN 12896-3:2016 | Public transport - Reference data model - Part 3: Timing information and vehicle scheduling |
EN 15531-3:2015 | Public transport - Service interface for real-time information relating to public transport operations - Part 3: Functional service interfaces |
EN 12896-1:2016 | Public transport - Reference data model - Part 1: Common concepts |
CEN/TS 17118:2017 | Intelligent transport systems - Public transport - Open API for distributed journey planning |
PD CEN/TR 17143:2017 | Intelligent transport systems. Standards and actions necessary to enable urban infrastructure coordination to support Urban-ITS |
BS EN 15531-2:2015 | Public transport. Service interface for real-time information relating to public transport operations Communications |
I.S. EN 12896-2:2016 | PUBLIC TRANSPORT - REFERENCE DATA MODEL - PART 2: PUBLIC TRANSPORT NETWORK |
BS EN 12896-2:2016 | Public transport. Reference data model Public transport network |
DIN CEN/TS 16614-3;DIN SPEC 4623:2016-08 | PUBLIC TRANSPORT - NETWORK AND TIMETABLE EXCHANGE (NETEX) - PART 3: PUBLIC TRANSPORT FARES EXCHANGE FORMAT |
S.R. CEN/TS 17118:2017 | INTELLIGENT TRANSPORT SYSTEMS - PUBLIC TRANSPORT - OPEN API FOR DISTRIBUTED JOURNEY PLANNING |
15/30315135 DC : DRAFT APR 2015 | BS EN 12896-2 - ROAD TRANSPORT AND TRAFFIC TELEMATICS - PUBLIC TRANSPORT REFERENCE DATA MODEL - PART 2: PUBLIC TRANSPORT NETWORK |
BS EN 15531-3:2015 | Public transport. Service interface for real-time information relating to public transport operations Functional service interfaces |
PD CEN/TS 15531-5:2016 | Public transport. Service interface for real-time information relating to public transport operations Functional service interfaces situation exchange: Situation Exchange |
PD CEN/TS 17118:2017 | Intelligent transport systems. Public transport. Open API for distributed journey planning |
15/30315138 DC : DRAFT APR 2015 | BS EN 12896-3 - INTELLIGENT TRANSPORT SYSTEMS - REFERENCE DATA MODEL - PART 3: TIMING INFORMATION AND VEHICLE SCHEDULING |
S.R. CEN/TS 15531-5:2016 | PUBLIC TRANSPORT - SERVICE INTERFACE FOR REALTIME INFORMATION RELATING TO PUBLIC TRANSPORT OPERATIONS - PART 5: FUNCTIONAL SERVICE INTERFACES SITUATION EXCHANGE: SITUATION EXCHANGE |
I.S. EN 15531-3:2015 | PUBLIC TRANSPORT - SERVICE INTERFACE FOR REAL-TIME INFORMATION RELATING TO PUBLIC TRANSPORT OPERATIONS - PART 3: FUNCTIONAL SERVICE INTERFACES |
I.S. EN 12896-1:2016 | PUBLIC TRANSPORT - REFERENCE DATA MODEL - PART 1: COMMON CONCEPTS |
S.R. CEN/TS 16614-3:2016 | PUBLIC TRANSPORT - NETWORK AND TIMETABLE EXCHANGE (NETEX) - PART 3: PUBLIC TRANSPORT FARES EXCHANGE FORMAT |
BS EN 12896-1:2016 | Public transport. Reference data model Common concepts |
PREN 12896-3 : DRAFT 2015 | INTELLIGENT TRANSPORT SYSTEMS - REFERENCE DATA MODEL - PART 3: TIMING INFORMATION AND VEHICLE SCHEDULING |
13/30285301 DC : 0 | BS EN 15531-3 - PUBLIC TRANSPORT - SERVICE INTERFACE FOR REAL-TIME INFORMATION RELATING TO PUBLIC TRANSPORT OPERATIONS - PART 3: FUNCTIONAL SERVICE INTERFACES |
DIN CEN/TS 15531-5;DIN SPEC 91254:2016-07 | Public transport - Service interface for real-time information relating to public transport operations - Part 5: Functional service interfaces situation exchange: Situation Exchange; English version CEN/TS 15531-5:2016 |
13/30285298 DC : 0 | BS EN 15531-2 - PUBLIC TRANSPORT - SERVICE INTERFACE FOR REAL-TIME INFORMATION RELATING TO PUBLIC TRANSPORT OPERATIONS - PART 2: COMMUNICATIONS |
PD CEN/TS 16614-3:2016 | Public transport. Network and Timetable Exchange (NeTEx) Public transport fares exchange format |
I.S. EN 15531-2:2015 | PUBLIC TRANSPORT - SERVICE INTERFACE FOR REAL-TIME INFORMATION RELATING TO PUBLIC TRANSPORT OPERATIONS - PART 2: COMMUNICATIONS |
I.S. EN 12896-3:2016 | PUBLIC TRANSPORT - REFERENCE DATA MODEL - PART 3: TIMING INFORMATION AND VEHICLE SCHEDULING |
S.R. CEN/TR 17143:2017 | INTELLIGENT TRANSPORT SYSTEMS - STANDARDS AND ACTIONS NECESSARY TO ENABLE URBAN INFRASTRUCTURE COORDINATION TO SUPPORT URBAN-ITS |
EN 15531-2:2015 | Public transport - Service interface for real-time information relating to public transport operations - Part 2: Communications |
ISO 639-1:2002 | Codes for the representation of names of languages — Part 1: Alpha-2 code |
EN 28701:2012 | Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT) |
ISO 639:1988 | Code for the representation of names of languages |
ISO/IEC 8859-15:1999 | Information technology 8-bit single-byte coded graphic character sets Part 15: Latin alphabet No. 9 |
CEN/TS 16614-1:2014 | PUBLIC TRANSPORT - NETWORK AND TIMETABLE EXCHANGE (NETEX) - PART 1: PUBLIC TRANSPORT NETWORK TOPOLOGY EXCHANGE FORMAT |
ISO/IEC 19501:2005 | Information technology — Open Distributed Processing — Unified Modeling Language (UML) Version 1.4.2 |
ISO 8601:2004 | Data elements and interchange formats Information interchange Representation of dates and times |
ENV 13998:2001 | ROAD TRANSPORT AND TRAFFIC TELEMATICS - PUBLIC TRANSPORT - NON-INTERACTIVE DYNAMIC PASSENGER INFORMATION ON GROUND |
EN 12896:2006 | Road transport and traffic telematics - Public transport - Reference data model |
SAE J 1939/71 : 2016 | VEHICLE APPLICATION LAYER |
CEN/TS 13149-6:2005 | PUBLIC TRANSPORT - ROAD VEHICLE SCHEDULING AND CONTROL SYSTEMS - PART 6: CAN MESSAGE CONTENT |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.