CEN TS 16614-2-2014 Public transport - Network and Timetable Exchange (NeTEx) - Part 2 Public transport scheduled timetables exchange format《公共交通 网络和时间表交换（NETEX） 第2部分 公共交通的计划时间表交换格.pdf

1、BSI Standards PublicationPublic transport Network and Timetable Exchange (NeTEx)Part 2: Public transport scheduled timetables exchange formatPD CEN/TS 16614-2:2014National forewordThis Published Document is the UK implementation of CEN/TS 16614-2:2014.The UK participation in its preparation was entr

2、usted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions ofa contract. Users are responsible for its correct applicatio

3、n. The British Standards Institution 2014.Published by BSI Standards Limited 2014ISBN 978 0 580 82692 4ICS 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee

4、on 30 June 2014.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TS 16614-2:2014TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16614-2 May 2014 ICS 35.240.60 English Version Public transport - Network and Timetable Exchange (NeT

5、Ex) - Part 2: Public transport scheduled timetables exchange format Transport Public - changes des informations planifies (NeTEx) - Partie 2: Description de loffre de transport ffentlicher Verkehr - Netzwerk und Fahrplan Austausch (NeTEx) - Teil 2: Fahrplne This Technical Specification (CEN/TS) was

6、approved by CEN on 12 November 2013 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 their comments, particularly on the question whether the CEN/TS can be converted into a European

7、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 in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final d

8、ecision 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, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Irelan

9、d, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centr

10、e: Avenue Marnix 17, B-1000 Brussels 2014 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 16614-2:2014 EPD CEN/TS 16614-2:2014CEN/TS 16614-2:2014 (E) 2 Contents Page Foreword . 4 Introduction 5 1 Scope 6 1.1 General . 6 1.2 Tra

11、nsport modes . 6 1.3 Compatibility with existing standards and recommendations . 6 2 Normative references . 6 3 Terms and definitions . 7 4 Symbols and abbreviations . 7 5 Use Cases for Journey managing vehicle fleets; issuing tickets and receipts; providing real-time information on service running,

12、 and so on. This European Technical Specification specifies a Network and Timetable Exchange (NeTEx) about public transport. It is intended to be used to exchange information between PT organisations systems containing scheduled public transport data. It can also be seen as a complement to the SIRI

13、(Service Interface for Real-time Information) standard, as SIRI needs reference data exchange in the scope of NeTEx before any possible real-time exchange. Well-defined, open interfaces have a crucial role in improving the economic and technical viability of public transport Information Systems of a

14、ll kinds. Using standardised interfaces, systems can 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

15、of each functional module, vital for managing the 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 transpo

16、rt information and service management: Interoperability 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 for

17、 real-time vehicle information; (ii) using common data models and schemas for the messages exchanged for each service; and (iv) introducing a consistent approach to data management. Technical advantages include the following: reusing a common communication layer shared with SIRI for all the various

18、technical services enables cost-effective implementations, and makes the standard readily extensible in future. PD CEN/TS 16614-2:2014CEN/TS 16614-2:2014 (E) 6 1 Scope 1.1 General NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V5.1

19、(EN 12896), IFOPT (EN 28701) and SIRI (CEN/TS 15531-4 and CEN/TS 15531-5 and prEN 15531-1, prEN 15531-2 and prEN 15531-3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems. NOTE Many NeTEx concepts are taken directly from Transmode

20、l and IFOPT; the definitions and explanation of these concepts are extracted directly from the respective standards and reused in NeTEx, sometimes with further adaptions in order to fit the NETEx context. The data exchanges targeted by NeTEx are predominantly oriented towards passenger information a

21、nd also for data exchange between transit scheduling systems and AVMS (Automated Vehicle Monitoring Systems). However it is not restricted to these purposes, and NeTEx can provide an effective solution to many other use cases for transport exchange. 1.2 Transport modes Most public transport modes ar

22、e taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional provisions that apply especially to air transport. 1.3 Compatibility with e

23、xisting standards and recommendations The concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train composition and facilities; planned passing times;

24、timetable versions and validity conditions. In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as

25、 the Commission Regulation (EU) No 454/2011), based on UIC directives. As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public Transport Interface Standard). The

26、data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are

27、 indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. prEN 15531-1:2013, Public transport - Service interface for real-time information relating to public tra

28、nsport operations - Part 1: Context and framework prEN 15531-2:2013, Public transport - Service interface for real-time information relating to public transport operations - Part 2: Communications infrastructure prEN 15531-3:2013, Public transport - Service interface for real-time information relati

29、ng to public transport operations - Part 3: Functional service interfaces PD CEN/TS 16614-2:2014CEN/TS 16614-2:2014 (E) 7 CEN/TS 15531-4, Public transport - Service interface for real-time information relating to public transport operations - Part 4: Functional service interfaces: Facility Monitorin

30、g CEN/TS 15531-5, Public transport - Service interface for real-time information relating to public transport operations - Part 5: Functional service interfaces - Situation Exchange CEN/TS 16614-1:2014, Public transport - Network and Timetable Exchange (NeTEx) - Part 1: Public transport network topo

31、logy exchange format 3 Terms and definitions For the purposes of this document, the terms and definitions given in CEN/TS 16614-1:2014 apply. 4 Symbols and abbreviations For the purposes of this document, the symbols and abbreviations given in CEN/TS 16614-1:2014 apply. 5 Use Cases for Journey tempo

32、ral and other conditions (DAY TYPE, VALIDITY CONDITION); further descriptive and classification information (TRAIN NUMBER, PRODUCT CATEGORY, TYPE OF SERVICE, stops etc., ); and operational data (BLOCK). A TEMPLATE JOURNEY allows a set of VEHICLE JOURNEYs to be defined that follow a common temporal p

33、attern See FREQUENCY GROUPs below. PD CEN/TS 16614-2:2014CEN/TS 16614-2:2014 (E) 18 class NeTEx TM TP Vehicle Journey MODELInterchange MODEL:DEFAULT INTERCHANGEDEAD RUN+ DeadRunTypePK+ idInterchange MODEL:JOURNEY MEETINGCoupled Journey MODEL:JOURNEY PARTVEHICLE JOURNEY+ DepartureTime+ JourneyDuratio

34、n o1PK+ idPOINTService Pattern MODEL:SCHEDULED STOP POINTService Calendar MODEL:DAY TYPELINK SEQUENCEJourney Pattern MODEL:JOURNEY PATTERNPOINT IN LINK SEQUENCEJourney Pattern MODEL:TIMING POINT IN JOURNEY P ATTE RNName: NeTEx TM TP Vehicle Journey MODELAuthor: NeTExVersion: 1.0Created: 16/03/2010 1

35、2:53:31Updated: 01/10/2012 19:03:58Service Journey MODEL:SERVICE JOURNEYVehicle Service MODEL:BLOCKFacility MODEL:FACILITYFACILITY SETFacility MODEL:SERVICE FACILITY SETSITEStop Place MODEL:STOP PLACESTOP PLACE SPACEStop Place MODEL:QUAYStop Assignment MODEL:STOP ASSIGNMENTJOURNEY+ Name 01+ Descript

36、ion 01PK idGeneric Validity MODEL:VALIDITY CONDITIONTYPE OF SERVICEPK+ idTEMPLATE VEHICLE JOURNEYPK+ id 01Transport Organisations MODEL:OPERATIONAL CONTEXTService Journey MODEL:TEMPLATE SERVICE JOURNEYTRAIN NUMBER+ ForAdvertisement+ ForProduction+ Description 01PK+ idAccessibility MODEL:ACCESSIBILIT

37、Y ASSESSMENTTYPE OF PRODUCT CATEGORYPK+ id+the classification for01+classified as*+classifiedas0*+a classification for01+part of 1*+comprises 01+for0*+to 1+in 0*+containing10*neighbourof0*+for 0*+to 01+for0*+made using01+applicable for 0*+for 0*+applicable for0*+characterized by01+characterized by 0

38、*+characterizing0*+characterized by0*+characterizing 01+characterized by01+characterizing 010* subzoneof1+including01+in*+for 0*+made using 01+subdividedin1+partof*+identifying01+identified by0*+for 1+worked on *+combining *+combinedin*+sta rtof1+from*+for 0*+to 1+to*+endof1+concerning*+concernedby1

39、*+workedon*+for1*+made using*+for 1+the timingreference for1+by default timedfrom01+timedfrom*+the timing referencefor01+identifying0*+identified by0*Figure 11 Vehicle Journey Conceptual MODEL (UML) 7.2.1.2 Vehicle Journey Physical Model The VEHICLE JOURNEY physical model adds detailed attributes fo

40、r VEHICLE JOURNEYs. PD CEN/TS 16614-2:2014CEN/TS 16614-2:2014 (E) 19 class XSD NeTEx TP Vehicle Journey ModelDataManagedObjectVehicleJourneyModel:TrainNumberForAdvertisement :normalizedString 01ForProduction :normalizedString 01Description :MultilingualString 01PKid :TrainNumberIdTypeDataManagedObje

41、ctInterchangeModel:DefaultInterchangeDataManagedObjectInterchangeModel:JourneyMeetingDataManagedObjectCoupledJourneyModel:JourneyPartTypeOfValueCoupledJourneyModel:PurposeOfJourneyPartitionVersionFrameTimetableFrameModel:TimetableFrameName: XSD NeTEx TP Vehicle Journey ModelAuthor: NeTExVersion: 1.0

42、Created: 25/11/2009 14:35:57Updated: 02/08/2012 14:55:54VehicleJourneyModel:DeadRunDirectionType :DirectionTypeEnum 01DeadRunType :DeadRunTypeEnum 01PKid :DeadRunIdTypeFKOperatorRef :OperatorRef* 01LineRef :LineRef* 01containedgroupsOfServices :GroupOfService 0*trainNumbers :TimeDemandTypeRef* 0*Ori

43、gin :JourneyEndpoint 01Destination :JourneyEndpoint 01calls :DeadRunCall 0* orderedVehicleJourneyModel:VehicleJourneyDepartureTime :timeJourneyDuration :duration 01PKid :VehicleJourneyIdTypecontainedFrequency :JourneyFrequency 01dayTypes :DayTypeRef* 0*timeDemandTypes :TimeDemandTypeRef* 0*parts :Jo

44、urneyPart 0*noticeAssignments :NoticeAssignmentView 0*waitTimes :VehicleJourneyWaitTime 0*runTimes :VehicleJourneyRunTime 0*layovers :VehicleJourneyLayover 0*passingTimes :TimetabledPassingTime 0*pointsInSequence :PointInSequence 0*FKRouteRef :RouteRef* 01JourneyPatternRef :JourneyPatternRef* 01Time

45、DemandTypeRef :TimeDemandTypeRef* 01TimingAlgorithmRef :TimingAlgorithmRef* 01FrequencyGroupRef :JourneyFrequencyGroupIdType* 01VehicleTypeRef :VehicleTypeRef* 01OperationalContextRef :VehicleTypeRef* 01BlockRef :BlockRef* 01CourseOfJourneysRef :CourseOfJourneysRef* 01AKPublicCode :normalizedString

46、01PointInJourneyPatternJourneyPatternModel:TimingPointInJourneyPatternLinkSequenceJourneyPatternModel:JourneyPatternDataManagedObjectServiceCalendarModel:DayTypeTimingPointServ icePatternModel:ScheduledStopPointenumerationVehicleJourneyValues:ReasonForMeetingEnumsplittingotherjoiningDataManagedObjec

47、tVehicleServiceModel:BlockTypeOfValueXmlImplementAs.FacilityModel:FacilityFacilitySetFacilityModel:ServiceFacilitySetDataManagedObjectTimeDemandTypeModel:TimeDemandTypeenumerationVehicleJourneyValues:DeadRunTypeEnumGarageRunOutGarageRunInTurningManoeuvreOtherGroupOfEntitiesVehicleJourneyFrequencyMod

48、el:JourneyFrequencyGroupServiceJourneyTemplateVehicleJourneyServiceJourneyModel:TemplateServiceJourneyPKid :TemplateServiceJourneyIdType 01ValidityConditionAvailabilityConditionModel:AvailabilityConditionVehicleJourneyFrequencyModel:JourneyFrequencyLinkSequenceVehicleJourneyModel:JourneyDescription

49、:MultilingualString 01TransportMode :VehicleModeEnum 01TransportSubmode :TransportSubMode 01ExternalVehicleJourneyRef :normalizedString*PKid :JourneyIdTypeFKTypeOfProductCategoryRef :TypeOfProductCategoryRef* 01TypeOfServiceRef :TypeOfServiceRef* 01LinkSequenceProjectionRef :LinkSequenceProjectionRef* 01containedjourneyAccountings :JourneyAccounting 0*Accessibility :AccessibilityAs