BS PD CEN TS 16614-3-2016 Public transport Network and Timetable Exchange (NeTEx) Public transport fares exchange format《公共交通 网络和时间表交换 (NeTEx) 公共交通票价交换格式》.pdf

1、BSI Standards Publication PD CEN/TS 16614-3:2016 Public transport Network and Timetable Exchange (NeTEx) Part 3: Public transport fares exchange formatPD CEN/TS 16614-3:2016 PUBLISHED DOCUMENT National foreword This Published Document is the UK implementation of CEN/TS 16614-3:2016. The UK participa

2、tion in its preparation was entrusted to Technical Committee EPL/278, Intelligent transport systems. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are r

3、esponsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 90066 2 ICS 35.240.60 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Document was published under the authority of

4、the Standards Policy and Strategy Committee on 31 March 2016. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dPD CEN/TS 16614-3:2016TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16614-3 March 2016 ICS 35.240.60 English Version Public transp

5、ort - Network and Timetable Exchange (NeTEx) - Part 3: Public transport fares exchange format Transport public - Echange des donnes de rseau et dhoraires (NeTEx) - Partie 3 : Format dchange dinformations voyageurs concernant le rseau de transport public ffentlicher Verkehr - Netzwerk- und Fahrplan A

6、ustausch (NeTEx) - Teil 3: Austauschformat fr die Fahrkartenauskunft des ffentlichen Verkehrs This Technical Specification (CEN/TS) was approved by CEN on 17 August 2015 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After two years the member

7、s of CEN will be requested to submit their comments, particularly 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 available promptly at national level i

8、n an appropriate form. It is permissible to keep conflicting 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, Croatia, Cypru

9、s, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United King

10、dom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2016 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 166

11、14-3:2016 EPD CEN/TS 16614-3:2016 CEN/TS 16614-3:2016 (E) 2 Contents Page European foreword. 5 Introduction 6 1 Scope 7 1.1 General 7 1.2 Fares scope 7 1.3 Transport modes . 7 1.4 Compatibility with existing standards and recommendations 8 2 Normative references 8 3 Terms and definitions . 8 4 Symbo

12、ls and abbreviations 25 5 Use Cases for Fare Exchange 25 5.1 Purpose 25 5.2 Business context . 25 5.2.1 Fare planning process 25 5.3 Actors and use case types 31 5.3.1 General . 31 5.3.2 Use Cases for Fare Policy . 33 5.3.3 Use Cases for Organisation of Fare Policy Usage 33 5.4 Excluded Use Cases 33

13、 5.5 Use Cases . 34 5.5.1 Collection of Use Cases . 34 6 Generic Physical Model and XSD mapping rules. 61 7 Public Transport Fares Conceptual and physical data model 61 7.1 Conceptual Model overview . 61 7.1.1 Functional Domains 61 7.1.2 Data Model Overview 63 7.1.3 Main Concepts . 65 7.2 Fare Model

14、 dependencies . 70 7.2.1 NeTEx Part3 Use of Version Frames 74 7.2.2 Fare Frame 75 7.3 Reusable Fare Components 92 7.3.1 Fare Zone . 92 7.3.2 Fare Facility 112 7.4 Fare Structure 114 7.4.1 Fare Structure Model dependencies 114 7.4.2 Common Fare Structure . 115 7.4.3 Geographical Fare Structure 122 7.

15、4.4 Time Fare Structure 132 7.4.5 Quality Fare Structure 140 7.4.6 Fare Structure Element 150 7.4.7 Distance Matrix Element . 178 7.4.8 Validable managing vehicle fleets; publicising fares, issuing tickets and receipts; providing real-time information on service running, and so on. The first two par

16、ts of the European Technical Specification NeTEx specifies a Network and Timetable Exchange for Public Transport. It is intended to be used to exchange data relating to scheduled public transport between the systems of PT organiZations. It can also be seen as complementary to the SIRI (Service Inter

17、face for Real-time Information) standard, as SIRI needs a prior exchange of reference e to provide the necessary context for the subsequent exchange of a real-time data. This European Technical Specification (NeTex Part 3) specifies exchanges of Public Transport fares between systems and organisatio

18、ns. It is a complement to the Parts 1 and 2 in the sense that it uses a subset of concepts defined there. Well-defined, open interfaces have a crucial role in improving the economic and technical viability of Public Transport Information Systems of all kinds. Using standardized interfaces, systems c

19、an be implemented as discrete pluggable modules 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

20、complexity of increasing large and dynamic systems. Furthermore, individual functional modules can be replaced or evolved, without unexpected breakages of obscurely dependent function. This standard will improve a number of features of public transport information and service management: Interoperab

21、ility the standard 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, (iii) using common data models and schemas for the m

22、essages exchanged for each service; and (iv) introducing a consistent approach to data management. Technical advantages include the following: a modular reusing of a common communication layer shared with SIRI for all the various technical services enables cost-effective implementations, and makes t

23、he standard readily extensible in future. PD CEN/TS 16614-3:2016 CEN/TS 16614-3:2016 (E) 7 1 Scope 1.1 General NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V5.1 (EN 12986), IFOPT (EN 28701) and SIRI (CEN/TS 15531-4, CEN/TS

24、15531-5 and EN 15531-1, EN 15531-2, EN 15531-3 1 ) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS). NOTE NeTEx is a refinement and an implementation of Transmodel and IFOP

25、T; the definitions and explanations of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptations in order to fit the NeTEx context. Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger informa

26、tion systems and AVMS with data from transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange. 1.2 Fares scope This Part 3 of NeTEx, is specifically concerned with the exchange of fare struct

27、ures and fare data, using data models that relate to the underlying network and timetable models defined in Part 1 and Part 2 and the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope of Part 3. In summary, it is concerned with data for the following

28、 purposes: (i) To describe the many various possible fare structures that arise in public transport (for example, flat fares, zonal fares, time dependent fares, distance based fares, stage fares, pay as you go fares, season passes, etc., etc.). (ii) To describe the fare products that may be purchase

29、d having these fare structures and to describe the conditions that may attach to particular fares, for example if restricted to specific groups of users, or subject to temporal restrictions. These conditions may be complex. (i) To allow actual price data to be exchanged. Note however that NeTEx does

30、 not itself specify pricing algorithms or how fares should be calculated. This is the concern of Fare Management Systems. It may be used may be used to exchange various parameters required for pricing calculations that are needed to explain or justify a fare. (iii) To include the attributes and the

31、text descriptions necessary to present fares and their conditions of sale and use to the public. of retail systems and allows fare data to be managed and integrated with journey planning and network data in public facing information systems. It is of on the boundaries of NeTEx with Fare Management S

32、ystems. 1.3 Transport modes All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports, air journeys, and air fares, but there has not been any specific consideration of any additional requirements that apply specifically to air transport. 1Under development