EN 15531-1:2015

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.GHORYDQMDÖffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen bezogen auf Operationen im öffentlichen Verkehr - Teil 1: Kontext und GrundstrukturTransport public - Interface de service pour les informations en temps réel relatives aux opérations de transport public - Partie 1 : Cadre et contextePublic transport - Service interface for real-time information relating to public transport operations - Part 1: Context and framework35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and tradeICS:Ta slovenski standard je istoveten z:EN 15531-1:2015SIST EN 15531-1:2015en,fr,de01-december-2015SIST EN 15531-1:2015SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 15531-1
August 2015 ICS 35.240.60 Supersedes CEN/TS 15531-1:2007English Version
Public transport - Service interface for real-time information relating to public transport operations - Part 1: Context and framework
Transport public - Interface de service pour les informations en temps réel relatives aux opérations de transport public - Partie 1 : Cadre et contexte
Öffentlicher Verkehr - Serviceschnittstelle für Echtzeitinformationen bezogen auf Operationen im öffentlichen Verkehr - Teil 1: Kontext und Grundstruktur This European Standard was approved by CEN on 20 June 2015.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
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, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2015 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 15531-1:2015 ESIST EN 15531-1:2015

European foreword .4 Introduction .5 1 Scope .7 1.1 Interfaces specified by this standard .7 1.2 Use of the SIRI standard .9 1.3 Limitations on SIRI and possible future developments. 10 2 Normative references . 10 3 Terms and definitions . 11 3.1 Transport related terms . 11 3.2 Communications and software concepts . 24 4 Symbols and abbreviations . 33 5 Types of reference data used in SIRI . 34 5.1 General . 34 5.2 Date and time format . 36 5.3 Location coordinate system . 36 5.4 National language of text elements . 37 5.5 Participant (information provider) identification . 37 5.6 Participant pair identification (service participant pair code) . 37 5.7 Point and place references . 38 5.8 Vehicle journey references . 40 5.9 Line, and direction references . 41 5.10 Stop sequence references and circular journeys . 41 5.11 Schedule version references . 43 5.12 Product category references . 43 5.13 Vehicle feature references . 47 5.14 Service features . 48 5.15 Situation references . 50 5.16 Summary of data reference scopes . 50 5.17 Transmodel compliant models . 51 5.18 Modelling vehicle journeys in SIRI. 52 6 Notation . 60 6.1 Representation of XML model elements in text . 60 6.2 Representing relationships in SIRI . 60 6.3 Notation for XML model structures of SIRI messages. 60 6.4 Notation for diagrams . 62 Annex A (informative) Checklist for Implementing SIRI . 63 A.1 Usage of the DSRC application layer. 63 A.2 Legal and commercial Issues . 63 A.3 Functional aspects . 63 A.4 Operational aspects . 65 Annex B (informative) Business Context . 67 B.1 Purpose of this section . 67 SIST EN 15531-1:2015

Figure 1 — Structure of SIRI: a set of optional service interface specifications using a common communications layer 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 realized in existent national systems: — one-step ‘direct’ delivery: allowing the simple rapid delivery of data; — two-step ‘fetched’ delivery: allowing a more optimized 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. SIST EN 15531-1:2015

Note 1 to entry: Events may include a delayed arrival of the FEEDER, a decision to prolong the wait by the DISTRIBUTOR vehicle, a change of the distributor departure point, or cancellation of either of the feeder or distributor journeys. 3.1.8 connection protection – SIRI coordination of inbound FEEDER and outbound DISTRIBUTOR journeys at an interchange so as to maximize the chances of passengers achieving their journeys Note 1 to entry: 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 GUARANTEED CONNECTIONS. 3.1.9 connection – Transmodel / NeTEx physical (spatial) possibility for a passenger to change from one public transport vehicle to another to continue a trip Note 1 to entry: Different transfer times may be necessary to cover interchange over a given CONNECTION link, depending on the kind of passenger. Note 2 to entry: In SIRI, a Feeder service may arrive at one STOP POINT in the CONNECTION link, and the Distributor may leave from the same or a different stop in the CONNECTION link. Note 3 to entry: The interchange duration, i.e. transfer time is the time needed to go from SCHEDULED STOP POINT to SCHEDULED STOP POINT across a CONNECTION link. In SIRI, it does not include time needed to board or alight. Several different types of interchange duration may be specified. Note 4 to entry: CONNECTION LINK has been renamed CONNECTION in NeTEx. 3.1.10 connection monitoring – SIRI real-time monitoring of FEEDER arrivals at an interchange 3.1.11 control action – Transmodel action resulting from a decision taken by the controller causing an amendment of the operation planned in the PRODUCTION PLAN 3.1.12 control centre – SIRI / NeTEx CONTROL CENTRE is an ORGANIZATIONAL UNIT that manages a network or networks of vehicles and their attendant real-time systems Note 1 to entry: In practice there is often a one-to-one corresponding between a control centre and a SIRI Service Participant. Each CONTROL CENTRE has a unique identifier, (the Control Centre Code), which provides a scope (i.e. unique namespace) for all non-global data references, such as stop identifiers, vehicle identifiers, etc. Within a Control SIST EN 15531-1:2015

These are mainly used to inform passengers about expected times of arrival and/or departure, but may also be used for monitoring and re-planning. See also OBSERVED (ACTUAL) PASSING TIME, TARGET (AIMED) PASSING TIME and TIMETABLED PASSING TIME. 3.1.26 event – Transmodel EVENT may be raised in response to the disturbance and over the lifetime of the EVENT one of more CONTROLLER ACTIONS and messages may then be associated with it Note 1 to entry: In SIRI, the EVENT is generally avoided in favour of more specific terms for entities. 3.1.27 facility – SIRI (Conflict with NeTEx) EQUIPMENT or LOCAL Service that provides a specific convenience or service to passengers
EXAMPLE Ticket machines, elevators, mechanical stairs, toilets, porterage, left luggage, etc. A facility may be an equipment, a service, a personal device or a reserved area. Note 1 to entry:
in NeTEx, a facility is a named amenity available to the public at a SITE or on a Service. A facility has no further properties other than a name. An EQUIPMENT or LOCAL Service is used to describe the further properties provided as part of particular facility 3.1.28 facility condition – SIRI particular mode of being of a facility (EQUIPMENT); describing its state and availability SIST EN 15531-1:2015

A VEHICLE may perform both feeder and distributor roles at the same time, that is, both set down passengers to transfer to other services, and board passengers from other services. 3.1.30 feeder arrival – SIRI arrival of an incoming feeder VEHICLE JOURNEY to a CONNECTION link 3.1.31 foreign vehicle – SIRI (Informal Transmodel Term) given ORGANIZATIONAL UNIT, i.e. SIRI Control Centre system, manages its own set of Local VEHICLES and VEHICLE JOURNEYS, for which it is responsible for provisioning and updating the data Note 1 to entry:
It may also need to manage data for Foreign VEHICLES and VEHICLE JOURNEYS, whose data is originated by a different Control Centre. A Foreign Vehicle is thus a local VEHICLE from one Control Centre that is roaming into the area managed by another Control Centre. 3.1.32 group of lines – NeTEx grouping of LINEs which will be commonly referenced for a specific purpose 3.1.33 headway interval – SIRI / NeTEx for frequency based services, the interval between vehicles Note 1 to entry: It may be TIMETABLED, AIMED, ESTIMATED or ACTUAL. 3.1.34 headway SERVICE – SIRI frequent service whose time of departure is normally shown to the public as ‘every n minutes’ rather than a fixed time 3.1.35 incident –Transmodel unforeseen EVENT influencing the operation of the network Note 1 to entry:
In SIRI, progression of an incident is represented by a SITUATION. 3.1.36 in congestion – SIRI status of a VEHICLE stuck in a traffic jam causing its journey to be delayed and subject to non-deterministic factors; any predictions are likely to be inaccurate 3.1.37 in panic – SIRI status of a VEHICLE with an active panic alarm indicating a security or other incident that is likely to delay the journey according to non-deterministic factors; any predictions are likely to be inaccurate 3.1.38 interchange rule – NeTEx conditions for considering JOURNEYs to meet or not to meet, specified indirectly: by a particular MODE, DIRECTION or LINE SIST EN 15531-1:2015

A JOURNEY PATTERN may pass through the same POINT more than once. The first point of a JOURNEY PATTERN is the origin. The last point is the destination. Every VEHICLE JOURNEY has a JOURNEY PATTERN associated with it. Note 2 to entry: In SIRI, JOURNEY PATTERNs are not explicitly exposed in the interface: the LINE and Route DIRECTION elements that appear on VEHICLE JOURNEYS are assumed to be derived from the associated journey pattern. 3.1.44 late – SIRI categorization in presentations indicating that the vehicle has been classified as LATE i.e., that a VEHICLE is running behind schedule in excess of some specified criteria Note 1 to entry:
The status of LATE will be derived from the real-time progress data. 3.1.45 line – Transmodel group of ROUTEs which is generally known to the public by a similar
...