Service Interface for Real Time Information

Last updated

The Standard Interface for Real-time Information or SIRI is an XML protocol to allow distributed computers to exchange real-time information about public transport services and vehicles.

Contents

The protocol is a CEN norm, developed originally as a technical standard with initial participation by France, Germany (Verband Deutscher Verkehrsunternehmen), Scandinavia, and the UK (RTIG)

SIRI is based on the CEN Transmodel abstract model for public transport information, and comprises a general purpose model, and an XML schema for public transport information.

A SIRI White Paper is available for further information on the protocol. [1]

Scope

CEN SIRI allows pairs of server computers to exchange structured real-time information about schedules, vehicles, and connections, together with informational messages related to the operation of the services. The information can be used for many different purposes, for example:

CEN SIRI includes a number of optional capabilities. Different countries may specify a country profile of the subset of SIRI capabilities that they wish to adopt.

Architecture

The CEN SIRI standard has two distinct components:

  1. SIRI Common Protocol Framework. The Framework provides a uniform architecture for defining data messages either as request/response pairs or as publish/subscribe services. The payload content model is separated from the messaging aspects so that the same payload content can be used in both request and subscription services and the same common messaging components can be used for all the different functional services. Common functions for subscription management, service monitoring, content level authentication, etc are provided.
  2. SIRI Functional Services. The SIRI specification specifies a number of distinct functional services, each designed for the exchange of a specific type of public transport data, all using the same protocol framework and basing their payload content on the Transmodel conceptual model. Additional functional services may be added that use the same framework but different payload content models to cover additional services.

CEN SIRI Functional Services

SIRI V1.0 defined eight functional services;

Two further functional services have been added as part of the CEN SIRI specification;

Other CEN Standards that use the SIRI Common Protocol Framework

The CEN SIRI Common Protocol Framework can be used by other standards to define their own Functional Services. Two CEN standards that do this are;

Current version & Documentation

Version 2.0 of SIRI , representing the CEN documents as published, is currently available as a set of XSD files packaged as a zip file .

SIRI is maintained under a maintenance regime, with version control managed by a working group of the CEN TC/278 Working Group 3 . Later versions of the schema are available at the same site, together with change notes.

History

The CEN SIRI standard was developed from European national standards for real-time data exchange, in particular the German VDV 453 standard, between 2000 and 2005, and included eight functional services. V1.0 became a CEN Technical Standard in 2006 and a full CEN standard in 2009.

Two additional functional services were added later Situation Exchange (SX) (Technical Standard 2009, Standard 2016) and Facility Monitoring (FM) (2011).

A number of small enhancements were subsequently added as informal changes creating interim releases v1.1, v1.2, etc.

Two other CEN standards were developed that made use of the 'SIRI Common Protocol Framework' to define their own functional services; NeTEx (v1.0 published in 2014) and Open API for distributed journey planning (v 1.0 published in 2017).

Version 2.0 of CEN-SIRI was developed between adopted in 2015. This is backwards compatible with V1.0 and both formalises the adoption of the interim enhancements and adds a number of additional features. An important new addition in SIRI v2.0 was the description of a uniform transform for rendering CEN-SIRI messages into a flat format that can be used in simple http requests without an XML rendering.

Example of sites using SIRI

Different SIRI implementations are used in a number of sites globally

Europe

North America

Asia

Australia

See also

Related Research Articles

<span class="mw-page-title-main">SOAP</span> Messaging protocol for web services

SOAP is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks. It uses XML Information Set for its message format, and relies on application layer protocols, most often Hypertext Transfer Protocol (HTTP), although some legacy systems communicate over Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.

Simple Network Management Protocol (SNMP) is an Internet Standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behaviour. Devices that typically support SNMP include cable modems, routers, switches, servers, workstations, printers, and more.

Universal Business Language (UBL) is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills. UBL was developed by an OASIS Technical Committee with participation from a variety of industry data standards organizations. UBL is designed to plug directly into existing business, legal, auditing, and records management practices. It is designed to eliminate the re-keying of data in existing fax- and paper-based business correspondence and provide an entry point into electronic commerce for small and medium-sized businesses.

<span class="mw-page-title-main">NaPTAN</span> Dataset of public transport acccess poiints in the UK

The National Public Transport Access Node (NaPTAN) database is a UK nationwide system for uniquely identifying all the points of access to public transport in the UK. The dataset is closely associated with the National Public Transport Gazetteer.

Manufacturing Message Specification (MMS) is an international standard dealing with messaging systems for transferring real time process data and supervisory control information between networked devices or computer applications. The standard is developed and maintained by the ISO Technical Committee 184 (TC184). MMS defines the following

<span class="mw-page-title-main">IEC 62056</span>

IEC 62056 is a set of standards for electricity metering data exchange by International Electrotechnical Commission. The IEC 62056 standards are the international standard versions of the DLMS/COSEM specification.

<span class="mw-page-title-main">Transport Direct</span> Division of the UK Department for Transport

The Transport Direct Programme was a division of the UK Department for Transport (DfT) to develop standards, data and better information technology systems to support public transport. It developed and operates the Transport Direct Portal which is a public facing multi-modal journey planner. It also supports the creation and management of comprehensive databases of all public transport movements in the United Kingdom with Traveline. During 2010 two key datasets were released as Open Data and published on www.data.gov.uk.

<span class="mw-page-title-main">Passenger information system</span>

A passenger information system, or passenger information display system, is an automated system for supplying users of public transport with information about the nature and the state of a public transport service through visual, voice or other media. It is also known as a customer information system or an operational information system. Among the information provided by such systems, a distinction can be drawn between:

The ISO/TC 215 is the International Organization for Standardization's (ISO) Technical Committee (TC) on health informatics. TC 215 works on the standardization of Health Information and Communications Technology (ICT), to allow for compatibility and interoperability between independent systems.

The National Transportation Communications for Intelligent Transportation System Protocol (NTCIP) is a family of standards designed to achieve interoperability and interchangeability between computers and electronic traffic control equipment from different manufacturers.

WS-Security Policy is a web services specification, created by IBM and 12 co-authors, that has become an OASIS standard as of version 1.2. It extends the fundamental security protocols specified by the WS-Security, WS-Trust and WS-Secure Conversation by offering mechanisms to represent the capabilities and requirements of web services as policies. Security policy assertions are based on the WS-Policy framework.

TransXChange is a UK national XML based data standard for the interchange of bus route and timetable information between bus operators, the Vehicle and Operator Services Agency, local authorities and passenger transport executives, and others involved in the provision of passenger information.

Transmodel is the CEN European Reference Data Model for Public Transport Information; it provides a conceptual model of common public transport concepts and data structures that can be used to build many different kinds of public transport information system, including for timetabling, fares, operational management, real time data, journey planning etc.

<span class="mw-page-title-main">Journey planner</span>

A journey planner, trip planner, or route planner is a specialized search engine used to find an optimal means of travelling between two or more given locations, sometimes using more than one transport mode. Searches may be optimized on different criteria, for example fastest, shortest, fewest changes, cheapest. They may be constrained, for example, to leave or arrive at a certain time, to avoid certain waypoints, etc. A single journey may use a sequence of several modes of transport, meaning the system may know about public transport services as well as transport networks for private transportation. Trip planning or journey planning is sometimes distinguished from route planning, which is typically thought of as using private modes of transportation such as cycling, driving, or walking, normally using a single mode at a time. Trip or journey planning, in contrast, would make use of at least one public transport mode which operates according to published schedules; given that public transport services only depart at specific times, an algorithm must therefore not only find a path to a destination, but seek to optimize it so as to minimize the waiting time incurred for each leg. In European Standards such as Transmodel, trip planning is used specifically to describe the planning of a route for a passenger, to avoid confusion with the completely separate process of planning the operational journeys to be made by public transport vehicles on which such trips are made.

IEC 60870 part 6 in electrical engineering and power system automation, is one of the IEC 60870 set of standards which define systems used for telecontrol in electrical engineering and power system automation applications. The IEC Technical Committee 57 have developed part 6 to provide a communication profile for sending basic telecontrol messages between two systems which is compatible with ISO standards and ITU-T recommendations.

A communication protocol is a system of rules that allows two or more entities of a communications system to transmit information via any variation of a physical quantity. The protocol defines the rules, syntax, semantics, and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both.

NeTEx is the CEN Technical standard for exchanging Public Transport Information as XML documents. It provides a W3C XML schema based on the Transmodel abstract model of common public transport concepts and data structures and can be used to exchange many different kinds of data between passenger information systems, including data describing for stops, facilities, timetabling and fares. Such data can be used by both operational management systems and customer facing systems for journey planning etc.

<span class="mw-page-title-main">Cyphal</span>

Cyphal is a lightweight protocol designed for reliable intra-vehicle communications using various communications transports, originally destined for CAN bus, but targeting various network types in subsequent revisions. OpenCyphal is an open-source project that aims to provide MIT-licensed implementations of the Cyphal protocol. The project was known as UAVCAN prior to rebranding in March 2022.

Packet Forwarding Control Protocol (PFCP) is a 3GPP protocol used on the Sx/N4 interface between the control plane and the user plane function, specified in TS 29.244. It is one of the main protocols introduced in the 5G Next Generation Mobile Core Network, but also used in the 4G/LTE EPC to implement the Control and User Plane Separation (CUPS). PFCP and the associated interfaces seek to formalize the interactions between different types of functional elements used in the Mobile Core Networks as deployed by most operators providing 4G, as well as 5G, services to mobile subscribers. These 2 types of components are:

  1. The Control Plane (CP) functional elements, handling mostly signaling procedures
  2. The User-data Plane (UP) functional elements, handling mostly packet forwarding, based on rules set by the CP elements.

References

  1. "SIRI (Service Interface for Real-time Information) – Management Overview – White Paper". VDV.de. 2006.
  2. Stephens, Matt (19 October 2011). "TfL wheels out digital bus info upgrade". The Register .