CEN TS 17118-2017 Intelligent transport systems - Public transport - Open API for distributed journey planning.pdf

1、Intelligent transport systems - Public transport - Open API for distributed journey planningPD CEN/TS 17118:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 17118 November 2017 ICS 35.2

2、40.60 English Version Intelligent transport systems - Public transport - Open API for distributed journey planning Intelligente Verkehrssysteme - ffentlicher Verkehr - Offene API fr verteilte Reiseplanung This Technical Specification (CEN/TS) was approved by CEN on 28 August 2017 for provisional app

3、lication. 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 Standard. CEN members are required to announce the exis

4、tence 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 decision about the possible conversion of the CEN/TS int

5、o 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, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherl

6、ands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2017 CEN A

7、ll rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 17118:2017 ENational forewordThis Published Document is the UK implementation of CEN/TS 17118:2017.The UK participation in its preparation was entrusted to Technical Committee EPL/278,

8、 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 responsible for its correct application. The British Standards Instituti

9、on 2017 Published by BSI Standards Limited 2017ISBN 978 0 580 97647 6ICS 35.240.60Compliance with a British Standard cannot confer immunity from legal obligations.This Published Document was published under the authority of the Standards Policy and Strategy Committee on 30 November 2017.Amendments/c

10、orrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CEN/TS 17118:2017TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 17118 November 2017 ICS 35.240.60 English Version Intelligent transport systems - Public transport - Open API for distributed journ

11、ey planning Intelligente Verkehrssysteme - ffentlicher Verkehr - Offene API fr verteilte Reiseplanung This Technical Specification (CEN/TS) was approved by CEN on 28 August 2017 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After two years th

12、e members 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

13、 level in 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, Croati

14、a, Cyprus, 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, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey

15、 and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2017 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref

16、. No. CEN/TS 17118:2017 EPD CEN/TS 17118:2017CEN/TS 17118:2017 (E) 2 Contents Page European foreword 10 0 Introduction . 11 0.1 General . 11 0.2 An Open API for distributed journey planning (OJP) 11 0.3 The public transport information tensions 11 0.4 Distributed journey planning architecture beyond

17、 scope 12 0.4.1 General . 12 0.4.2 The distributed journey planning approach 13 0.4.3 Distributed or centralised approaches 13 0.4.4 The basis for the Open API 14 0.4.5 Other possible uses for the Open API 14 0.5 The European ITS Directive . 14 1 Scope . 15 2 Normative references . 15 3 Terms and de

18、finitions 15 4 Symbols and abbreviations 32 5 Use cases 33 5.1 General . 33 5.2 Key tasks for Distributed Journey Planning . 34 5.2.1 Planning a component of a trip . 34 5.2.2 Discovering relevant stops . 35 5.2.3 Obtaining information about accessibility and services for those with special needs .

19、35 5.2.4 Seeking route information that can be displayed on maps 35 5.3 Other possible tasks for a Distributed Journey Planning system . 35 5.3.1 Requesting a stop timetable . 35 5.3.2 Requesting times for all intermediate stops in a trip . 35 5.3.3 Requesting expected events at a particular stop 36

20、 5.3.4 Requesting information about the fares and ticket options for a particular trip . 36 5.3.5 Other possible questions . 36 6 System Architectures, Metadata and Data 36 6.1 General . 36 6.2 General considerations 36 6.3 Metadata requirements . 38 6.4 Core data requirements . 38 7 Open API for Di

21、stributed Journey Planning OJP Services 40 7.1 Departure Monitor 40 7.1.1 Purpose 40 7.1.2 Interactions 41 7.1.3 Concerned Components . 41 7.1.4 Function 1: Departure Monitor . 41 7.2 Fare Information 42 7.2.1 Purpose 42 7.2.2 Interactions 42 7.2.3 Concerned Components . 43 PD CEN/TS 17118:2017CEN/T

22、S 17118:2017 (E) 3 7.2.4 Function 1: Tariff Zones for Stop / Station 44 7.2.5 Function 2: Static Fare Information . 44 7.2.6 Function 3: Trip-Related Fare Information . 44 7.3 Location text matching . 44 7.3.1 Purpose 44 7.3.2 Interactions . 45 7.3.3 Concerned Components . 45 7.3.4 Function: Locatio

23、n text matching . 45 7.4 Object Information Service . 45 7.4.1 Purpose 45 7.4.2 Interactions . 46 7.4.3 Concerned Components . 46 7.4.4 Function 1: Object Information . 46 7.4.5 Function 2: Finding relevant exchange points . 46 8 Open API for Distributed Journey Planning Interface Description . 47 8

24、.1 Notation of XML-Elements and XML-Structures 47 8.1.1 General . 47 8.1.2 Display of XML Elements in the Text . 47 8.1.3 Display of Relationships . 47 8.1.4 Table Notation of XML Structures . 48 8.1.4.1 General . 48 8.1.4.2 Grouping 49 8.1.4.3 Element Name 49 8.1.4.4 Multiplicity or an IT service;

25、or a journey planning, information or other functional service; or an immaterial facility such as Left Luggage. The context is often clear when it is used with another term (as in PT service, special service, service link, service pattern, etc) 3.1.98 ServiceDelivery IT service, taken from SIRI resp

26、onse from producer to consumer to deliver payload data. Either answers a direct ServiceRequest or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupplyRequest 3.1.99 ServiceFacility view of a SERVICE FACILITY SET in TMv6 (a view of) SERVICE

27、 FACILITY SET (a set of FACILITies available for a specific VEHICLE TYPE (e.g. carriage equipped with low floor) possibly only for a service (or for a SERVICE JOURNEY or a JOURNEY) 3.1.100 ServiceRequest an IT service, taken from SIRI request for the immediate delivery of data. Answered with a Servi

28、ceDelivery (or a DataReadyRequest) PD CEN/TS 17118:2017CEN/TS 17118:2017 (E) 25 3.1.101 ServiceResponse an IT service, taken from SIRI response message containing a payload and various attributes of its own 3.1.102 ServiceStatus parameters which describe the current status of a DATED VEHICLE JOURNEY

29、 3.1.103 ServiceViaPoint specialisation of VIA in TMv6 STOP PLACE or SCHEDULED STOP POINT as a VIA for a particular SERVICE PATTERN. Specialisation of a VIA 3.1.104 SharingModel sharing service loan and return scheme 3.1.105 SharingService transport service that provides shared vehicles 3.1.106 Sign

30、ature data for transmission of message signatures (public key cryptography), used to prove Message Integrity 3.1.107 SituationFullRef reference to situation message. Message details might be found in response context or through other communication channels 3.1.108 Situations as SIRI container for th

31、e structured description of situations in public transport or on the road (individual transport) 3.1.109 Speed relative speed in percent. If given slows the standard speed (below 100) or increases it (above 100) 3.1.110 StaticFare specialisation of a FARE PRODUCT in TMv5.1 and NeTEx list of FARE PRO

32、DUCTS under the responsibility of a FARE AUTHORITY, independent of any specific trip result 3.1.111 Status whether the request was processed successfully or not. Default is “true“ PD CEN/TS 17118:2017CEN/TS 17118:2017 (E) 26 3.1.112 StopAttributes properties of a SCHEDULED STOP POINT or STOP PLACE i

33、n TMv6 selection of attributes of ACCESSIBIITY LIMITATION related to a SCHEDULED STOP POINT extended by attributes referring to some PLACE EQUIPMENT 3.1.113 StopCallStatus see SIRI CALL current status of each stop along the route of a PT Service 3.1.114 StopEvent see SIRI CALL departure or arrival e

34、vent or both 3.1.115 StopEventContent see SIRI CALL parameters which define the extent of information to be returned in a Stop Event result 3.1.116 StopEventData see SIRI CALL parameters which establish various filtering criteria for Stop Event results 3.1.117 StopEventParam see SIRI CALL parameters

35、 which define what is to be included in a Stop Event result 3.1.118 StopEventPolicy see SIRI CALL parameters which define the number, Time Window and types of Stop Event to be included 3.1.119 StopFacility corresponds to a SITE FACILITY SET in TMv6 FACILITY that applies to a stop 3.1.120 StopFare st

36、op-related FARE PRODUCT information 3.1.121 StopPlace extended view of STOP PLACE in TMv6 STOP PLACE extended by ACCESSIBILITY LIMITATION properties and of the associated equipment, comprising one or more locations where vehicles may stop and where passengers may board or leave vehicles or prepare t

37、heir trip, and which will usually have one or more wellknown names PD CEN/TS 17118:2017CEN/TS 17118:2017 (E) 27 3.1.122 StopPoint extended view of SCHEDULED STOP POINT in TMv6 SCHEDULED STOP POINT extended by ACCESSIBILITY LIMITATION attributes and with identifier and name where passengers can board

38、 or alight from vehicles 3.1.123 SubMode TMv6 variant of a MODE, as for instance international or domestic rail (rail being the MODE) 3.1.124 Subscription see SIRI arrangement which allows a specific organisation to access an information system - usually taking the form of security parameters which

39、may or may not need to be paid for 3.1.125 SubscriptionRequest see SIRI request from a subscriber to a producer for a subscription to a particular IT service. Answered with a SubscriptionResponse 3.1.126 TariffZone corresponds to TARIFF ZONE in TMv5.1 and NeTEx ZONE used to define a zonal fare struc

40、ture in a zone-counting or zone-matrix system 3.1.127 TerminateSubscription see SIRI request to end a subscription to a particular IT service 3.1.128 Ticket corresponds to a FARE PRODUCT in TMv5.1 and NeTEx FARE PRODUCT which may be materialised as a TRAVEL DOCUMENT and which gives the passenger an

41、entitlement to travel on one or more specific TRIPLEGs subject to specified conditions 3.1.129 TimedLeg corresponds to a RIDE in TMv6 (with related information) passenger TRIPLEG with timetabled schedule 3.1.130 TimeWindow window of opportunity that the traveller has to perform a specific TRIPLEG 3.

42、1.131 TopographicPlace TMv6 type of PLACE providing the topographical context when searching for or presenting travel information, for example as the origin or destination of a trip. It may be of any size (e.g. County,City, Town, Village) and of different specificity (e.g. Greater London, London, We

43、st End, Westminster, St Jamess) PD CEN/TS 17118:2017CEN/TS 17118:2017 (E) 28 3.1.132 TrackSection LINK PROJECTION on the infrastructure network of the TRIPLEG together with time information 3.1.133 Transfer travel between two POINTs located sufficiently near to each other that they represent for a p

44、assenger a possibility to reach one of the POINTs when starting at the other in a timescale which is realistic when undertaking a TRIP, eg: ACCESS or CONNECTION 3.1.134 TransferDuration attribute of a CONNECTION (not INTERCHANGE) in TMv6 calculated duration in a response taking into account the requ

45、est parameters.; TransferDuration plus waiting time is the minimum interval between arrival and departure time 3.1.135 TransferLeg specialisation of NAVIGATION PATH in TMv6 description of a TRIPLEG which links other TRIPLEGs where a TRANSFER between different LOCATIONs is required 3.1.136 TransferMo

46、des MODEs dedicated to peform TRANSFERs 3.1.137 Transition transition types for interchanges 3.1.138 Trip extended view of TRIP PATTERN in TMv5.1 (to include time-related information) whole journey from passenger origin to passenger destination in one or more TRIPLEGs 3.1.139 TripContent parameters

47、that control the level of detail of the TRIP results 3.1.140 TripData data to be included/excluded from search, eg: modes, operators, etc 3.1.141 TripFare Fare for a specified TRIP 3.1.142 TripFareProduct specialisation of FARE PRODUCT in TMv5.1 and NeTEx FAREPRODUCT covering a part or the whole of a TRIP from boarding the first public transport vehicle to alighting from the last public transport vehicle (corresponds to a package of PREASSIGNED FARE PRODUCTs) PD CEN/TS 17118:2017