Cart (0)
  • No items in cart.
Total
$0
There is a technical issue about last added item. You can click "Report to us" button to let us know and we resolve the issue and return back to you or you can continue without last item via click to continue button.
Search book title
Enter keywords for book title search
Search book content
Enter keywords for book content search
Filters:
FORMAT
BOOKS
PACKAGES
EDITION
to
PUBLISHER
(1)
(317)
(572)
(44)
(234)
(969)
(649)
(2114)
(64)
(92448)
(54)
(535)
(117)
(33)
(20)
(19)
(92811)
(3)
(17)
(1)
(351)
(300)
(6217)
(239)
(16)
(5)
(1621)
(16)
(18)
(28)
(4)
 
(6)
(7)
(115)
(3)
(57)
(5)
(5)
(1)
(1)
(2)
(23)
(26)
(27)
(13)
(61)
(24)
(22)
(7)
(8)
(20)
(1)
(3)
(50)
(6)
(31)
CONTENT TYPE
 Act
 Admin Code
 Announcements
 Bill
 Book
 CADD File
 CAN
 CEU
 Charter
 Checklist
 City Code
 Code
 Commentary
 Comprehensive Plan
 Conference Paper
 County Code
 Course
 DHS Documents
 Document
 Errata
 Executive Regulation
 Federal Guideline
 Firm Content
 Guideline
 Handbook
 Interpretation
 Journal
 Land Use and Development
 Law
 Legislative Rule
 Local Amendment
 Local Code
 Local Document
 Local Regulation
 Local Standards
 Manual
 Model Code
 Model Standard
 Notice
 Ordinance
 Other
 Paperback
 PASS
 Periodicals
 PIN
 Plan
 Policy
 Product
 Program
 Provisions
 Requirements
 Revisions
 Rules & Regulations
 Standards
 State Amendment
 State Code
 State Manual
 State Plan
 State Standards
 Statute
 Study Guide
 Supplement
 Technical Bulletin
 All
  • BSI
    BS EN 15531-1:2015 Public transport. Service interface for real-time information relating to public transport operations - Context and framework
    Edition: 2015
    $538.63
    / user per year

Description of BS EN 15531-1:2015 2015

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.

The following editions for this book are also available...

About BSI

BSI Group, also known as the British Standards Institution is the national standards body of the United Kingdom. BSI produces technical standards on a wide range of products and services and also supplies certification and standards-related services to businesses.

X