SANS 55531-1-2008 Public transport - Service interface for real-time information relating to public transport operations Part 1 Context and framework《公共交通 与公共运输业务相关的实时信息服务界面 第1部分 背.pdf

《SANS 55531-1-2008 Public transport - Service interface for real-time information relating to public transport operations Part 1 Context and framework《公共交通 与公共运输业务相关的实时信息服务界面 第1部分 背.pdf》由会员分享，可在线阅读，更多相关《SANS 55531-1-2008 Public transport - Service interface for real-time information relating to public transport operations Part 1 Context and framework《公共交通 与公共运输业务相关的实时信息服务界面 第1部分 背.pdf（90页珍藏版）》请在麦多课文档分享上搜索。

1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA

2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any

3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-21370-1 SANS 55531-1:2008Edition 1CEN/TS 15531-1:2007Edition 1SOUTH AFRICAN NATIONAL STANDARD Public transport Service interface for real-

4、time information relating to public transport operations Part 1: Context and framework This national standard is the identical implementation of CEN/TS 15531-1:2007 and is adopted with the permission of CEN, rue de Stassart 36, B-1050 Brussels. Published by Standards South Africa 1 dr lategan road g

5、roenkloof private bag x191 pretoria 0001 tel: 012 428 7911 fax: 012 344 1568 international code + 27 12 www.stansa.co.za Standards South Africa SANS 55531-1:2008 Edition 1 CEN/TS 15531-1:2007 Edition 1 Table of changes Change No. Date Scope National foreword This South African standard was approved

6、by National Committee StanSA SC 71H, Information technology Intelligent transport systems, in accordance with procedures of Standards South Africa, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in May 2008. TECHNICAL SPECIFICATIONSPCIFICATION TECHNIQUETECHNISC

7、HE SPEZIFIKATIONCEN/TS 15531-1July 2007ICS 35.240.60English VersionPublic transport - Service interface for real-time informationrelating to public transport operations - Part 1: Context andframeworkffentlicher Verkehr - Dienstleitungsschnittstelle frzeitnahe Informationen zum Betrieb des ffentliche

8、nVerkehrs - Teil 1: Rahmen und GerstThis Technical Specification (CEN/TS) was approved by CEN on 23 October 2006 for provisional application.The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit theircomments, partic

9、ularly on the question whether the CEN/TS can be converted into a European Standard.CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS availablepromptly at national level in an appropriate form. It is permissible to keep conflicting

10、national standards in force (in parallel to the CEN/TS)until the final decision about the possible conversion of the CEN/TS into an EN is reached.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hu

11、ngary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGManagement Centre:

12、rue de Stassart, 36 B-1050 Brussels 2007 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. CEN/TS 15531-1:2007: ESANS 55531-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CE

13、N/TS 15531-1:2007 (E) 2 Contents Page Foreword4 Introduction .5 1 Scope 6 1.1 Interfaces Specified by this Technical Specification.6 1.1.1 Business Context.6 1.1.2 SIRI Communications6 1.1.3 SIRI Functional Services.7 1.2 Use of the SIRI standard .7 1.3 Limitations on SIRI and Possible Future Develo

14、pments.8 2 Normative references 9 3 Terms and definitions .9 3.1 Transport Related Terms 9 3.2 Communications managing vehicle fleets; issuing tickets and receipts; providing real-time information on service running, and so on. This Technical Specification specifies a Service Interface for Real-time

15、 Information (SIRI) about Public Transport. It is intended to be used to exchange information between servers containing real-time public transport vehicle or journey time data. These include the control centres of transport operators and information systems that utilise real-time vehicle informatio

16、n, for example, to deliver services such as travel information. Well-defined, open interfaces have a crucial role in improving the economic and technical viability of Public Transport Information Systems of all kinds. Using standardised interfaces, systems can be implemented as discrete pluggable mo

17、dules that can be chosen from a wide variety of suppliers in a competitive market, rather than as monolithic proprietary systems from a single supplier. Interfaces also allow the systematic automated testing of each functional module, vital for managing the complexity of increasing large and dynamic

18、 systems. Furthermore, individual functional modules can be replaced or evolved, without unexpected breakages of obscurely dependent function. This Technical Specification will improve a number of features of public transport information and service management: Interoperability the Technical Specifi

19、cation will facilitate interoperability between information processing systems of the transport operators by: (i) introducing common architectures for message exchange; (ii) introducing a modular set of compatible information services for real-time vehicle information; (ii) using common data models

20、and schemas for the messages exchanged for each service; and (iv) introducing a consistent approach to data management. Improved operations management the Technical Specification will assist in better vehicle management by (i) allowing the precise tracking of both local and roaming vehicles; (ii) pr

21、oviding data that can be used to improve performance, such as the measurement of schedule adherence; and (iii) allowing the distribution of schedule updates and other messages in real-time. Delivery of real-time information to end-users the Technical Specification will assist the economic provision

22、of improved data by; (i) enabling the gathering and exchange of real-time data between VAMS systems; (ii) providing standardised, well defined interfaces that can be used to deliver data to a wide variety of distribution channels. Technical advantages include the following: Reusing a common communic

23、ation layer for all the various technical services enables cost-effective implementations, and makes the Technical Specification readily extensible in future. SANS 55531-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 15531-1:200

24、7 (E) 6 1 Scope 1.1 Interfaces Specified by this Technical Specification 1.1.1 Business Context Real-time information may be exchanged between a number of different organisations, or between different systems belonging to the same organisation. Key interfaces include the following: Between public tr

25、ansport 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

26、publicly available information is complete and comprehensive. 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

27、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 communicati

28、on 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 sent of functi

29、onal services for exchanging data for different aspects of PT operation. A common data model, based on TransModel 5.1, is used across all services. Figure 1 Structure of SIRI: a set of optional service interface specifications using a common communications layer SANS 55531-1:2008This s tandard may o

30、nly be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 15531-1:2007 (E) 7 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 fun

31、ctional 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 communicati

32、ons 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 ca

33、ndidate 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

34、 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 followin

35、g 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 o

36、n 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 for example, Scandinavia and the UK both have a relatively hi

37、gh degree of organisational disaggregation, and as a result may need standardisation on what would be internal interfaces elsewhere in Europe. SANS 55531-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 15531-1:2007 (E) 9 CEN welc

38、omes input from users of this Technical Specification as to where SIRI needs extension or refinement. Additional Information about the relation between SIRI and Transmodel has been produced by a Transmodel compliance study. It can be found at www.siri.org.uk: A table describing the exact mapping of

39、each SIRI element to the corresponding Transmodel object. An extract of the Transmodel objects underlying SIRI Services. A UML Schema definition. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition c

40、ited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 12896, Road transport and traffic telematics - Public transport - Reference data model CEN/TS 13149-6, Public transport - Road vehicle scheduling and control systems - Part 6: C

41、AN message content ISO 8601, Data elements and interchange formats Information interchange Representation of dates and times ISO 639-1, Codes for the representation of names of languages - Part 1: Alpha-2 code 3 Terms and definitions For the purposes of this document, the following terms and definit

42、ions apply. 3.1 Transport Related Terms This section includes terms for both PT entities and properties of PT entities used in SIRI. For each term, it is indicated whether the term derives from TransModel (EN 12896 version 5.0) or whether the term is specific to SIRI. 3.1.1 BEARING SAE J1939/71 (CEN

43、/TS 13149-6) the heading of the vehicle in degrees expressed as a floating point number: compliant to SAE J1939/71 (Compatible with CEN/TS 13149-6) 3.1.2 BLOCK TransModel the work of a vehicle from the time it leaves a PARKING POINT after parking until its next return to park at a PARKING POINT. Any

44、 subsequent departure from a PARKING POINT after parking marks the start of a new BLOCK. The period of a BLOCK has to be covered by DUTIES. 3.1.3 CALL ACTIVITY SIRI the activity a passenger may undertake when a Vehicle calls at a stop; Boarding, Alighting, or Pass Through SANS 55531-1:2008This s tan

45、dard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 15531-1:2007 (E) 10 3.1.4 CALL SIRI a visit by a VEHICLE to a specific STOP POINT as it follows the JOURNEY PATTERN of its VEHICLE JOURNEY to achieve a set of planned and estimated PASSING TIMEs. A

46、 VEHICLE may make more than one Call to the same stop in the course of a JOURNEY: different calls may typically be distinguished by a Visit Number count. The Call may have real time data associated with it. A SIRI Call may be regarded as a useful optimisation of a more normalised set of structures t

47、hat are articulated separately in TransModel. Call combines the TransModel elements of POINT IN JOURNEY PATTERN in with ESTIMATED PASSING TIME, OBSERVED PASSING TIME, typically this will be a short numeric code designed to be efficient for communication over a radio channel of restricted capacity. 3

48、.1.7 CONNECTION ACTIVITY SIRI a change to the planned arrival to, or departure from, a connection link for a vehicle journey that is material to passengers intending to make a planned interchange. Events may include a delayed arrival of the feeder, a decision to prolong the wait by the distributor v

49、ehicle, a change of the distributor departure point, or cancellation of either of the feeder or distributor journeys. 3.1.8 CONNECTION PROTECTION SIRI the coordination of inbound feeder and outbound distributor journeys at an interchange so as to maximise the chances of passengers achieving their journeys. Involves the exchange of information between feeder and distributor to inform dispatchers and passengers of the current situation, and the delaying of distributor vehicles so as to honour G