1. © 2004Kizoom 1 PROTOCOLS Data Content Exchange Behaviour Transport Protocol Common Submodels? Location, Base Types, Incidents Request / Response Publish/Subscribe Topic Filtering Policy Filtering Restart /Heartbeat WS PUB SUB Lite: Http Get Medium HTTP POST + XML Heavy SOAP, ORB

2. © 2004Kizoom 2 DATEX II Data Content Exchange Behaviour Transport Protocol defined XML schema (draft, work in progress) D2 deliverable specifies… may be revised? in progress for 2006 publication HTTP GET, POST, SOAP.

3. © 2004Kizoom 3 SIRI Data Content Exchange Behaviour Transport Protocol well-defined interactions with XML schema representations Mainstream Internet HTTP POST, SOAP. defined XML Schema For payload XML Http Post SOAP TransModelWS-PubSub http get ? IP

4. © 2004Kizoom 4 Mediation - Efficiency Reducing Traffic

5. © 2004Kizoom 5 SIRI XSD Packages – Layered Reuse Common Request Management Common Request Management SIRI Functional Services Low Level Types SIRI Common Model

6. © 2004Kizoom 6 Acceptable Optimisations =TransModel Isomorphic? A B F C D * * Bs Cs E G * 11 A X (C+D+E) * Cs G 1 1 1 1 * A B C D * * Bs Cs E G * 1 1 1 1 OK NOT OK Compression Compounding *

7. © 2004Kizoom 7 SIRI Overview

8. © 2004Kizoom 8 Interaction 2- Publish/Subscribe

9. © 2004Kizoom 9 SIRI – Introduction Real-time Server-to-Server Services for Public Transport –Defines a Service Interface for exchanging real- time information of public transport networks. –Complements an underlying static information model for network and timetable description (TRIDENT,VDV, TransXChange) –Provides information on any change on the timetabled information, from original publication to the actual & predicted transport running times.

10. © 2004Kizoom 10 Gene Pool

11. © 2004Kizoom 11 PUB SUB Greater compelxcity –Public Transport Data TransModel : Terminology, model (isomorphic) VDV 453, 454, Trident, RTIG-XML –Real systems & experience! GML, WGS84 –Technology XML, XSD WS-Soap, WS-PubSub  Web Service enabled UML, ISO 24531, RFC Participants –Germany (VDV453, VDV 454) –France (Trident, TransModel) –UK (RTIG-XML, Trident, TransModel) –Denmark, Sweden, Norway, (PubTrans) –Czechoslovakia

12. © 2004Kizoom 12 Motivation - Uses of SIRI Services Rapid growth in real-time info - makes Public Transport more efficient to operate & more attractive to use. –Provision of Real time Service Information to Passengers. At Stop, On board, tethered & mobile internet –Provision of Information to Journey Planners. Real-time augmented –Facilitating Connections for Passengers. –PT Fleet and Network Management. –General Business Communication. E.g. Adherence to schedule Growth of mobile & internet –On-line, real time data. Roaming! –Ubiquitous embedded computing

13. © 2004Kizoom 13 Motivation – Linking up Orchestrating Multiple Actors in federated systems –Passenger information services involving multiple providers Connection/interchange information Stop Point/Station operated by several transport operators etc. –Services between different operators Single PT line – several operators Connection management –Services with other content providers To provide information to content providers To get information from content providers

14. © 2004Kizoom 14 Motivation - Standards Value to Passenger Transport Executives and Authorities / Operators as Customers –Open, modular architectures & supplier independence. –Protection of investment. –Efficient tender specification criteria. Value to Suppliers –European economies of scale & markets. –Reduced complexity & deployment costs –More reuse, Cheaper integration –Simplified tendering, quality differentiator. Value to Both –Enables new types of services –European economies of scale –Lowers costs - creating new markets –Modern, Modular, scaleable architectures –Harnesses open internet standards

15. © 2004Kizoom 15 The SIRI Specifications SIRI Documents (Completed 2005) –Technical Standard Part 1: Context and Framework Part 2: Communications Infrastructure Part 3: Functional Service Interfaces –Supporting XML Schema – W3C.XSD Modular package structure, one per service Support WSDL /SOAP binding using same xsd schema Migration path from existing standards –Country Profiles & Guidance Notes

16. © 2004Kizoom 16 SIRI Approach & Services Separation of Concerns –Transport layer is separate –Web Service architecture (http &/or SOAP…..) –SIRI General Communications Services Common to all types of Functional Service Robust, scaleable, architecture for Real-Time Tuneable for efficient deployment –SIRI Functional Services Timetables & Timetable Changes Stop Events (Arrivals & Departures) Vehicle Movement Connection Protection (Timetables, Events) General Informative Messages

17. © 2004Kizoom 17 Support Different Environments Able to optimise for different operational characteristics –High/Low bandwidth –Fast/slow processors –Hi/Low traffic –Large/small networks –Sparse /dense usage –Central or distributed Evolvable –Able to implement on different generations of technology –Allow modular, incremental implementation: roadmap

18. © 2004Kizoom 18 SIRI Functional Services

19. © 2004Kizoom 19 SIRI Timetable Services Production Timetable (PT) –Distribute latest timetable Schedule to AVMS AVMS to client Estimated Timetable (ET) –Distribute latest timetable including real-time Cancellations, additions, short working Realtime-predictions

20. © 2004Kizoom 20 SIRI Stop Services Stop Timetable (ST) –Distribute latest timetable Stop Centric Timetables Provisions Clients with latest data. Stop Monitoring (SM) –Real time Arrival & Departure Boards Arrivals, Departures, pass-throughs At stop, onboard, away

21. © 2004Kizoom 21 SIRI Connection Services Connection Timetable (CT) –Distribute planned interchanges Stop Centric Provisions Clients. Connection Monitoring (CM) –Connection management –Guaranteed connection support

22. © 2004Kizoom 22 SIRI General Message Services General Message (GM) –Exchange Structured Messages Simple or embedded structures (eg TPEG, Trident etc) Situation, operational, and general info messages

23. © 2004Kizoom 23 Transport & General Communications

24. © 2004Kizoom 24 Transport & Communications Common Protocols for all SIRI Functional Services –Independent of Functional Message Content –Based on new Web services standard Ws- PubSub, Ws-Address etc (W3C) –Communications Transport Independent XML + http POST, WSDL SOAP Binding

25. © 2004Kizoom 25 Common Communications Services General Functions Common to all SIRI Service Types –Subscription Management –Recovery & Restart –Access Controls – Who is allowed to access? –Versioning – Allows distributed upgrades –Discovery – Which systems have which data? Some Capabilities are Optional

26. © 2004Kizoom 26 Communications Framework Patterns Alternate Patterns of Interaction 1.Request/Response vs. Publish/Subscribe Choose for scaleability & responsibility 2.Direct Delivery vs. Fetched Delivery Allows efficient implementation choices 3.Notification Mediation Reduces traffic for publish subscribe –Last Update, Change Threshold, –Subscriber Groups

27. © 2004Kizoom 27 Interaction 1- Request/Response

28. © 2004Kizoom 28 Delivery - Direct

29. © 2004Kizoom 29 Delivery - Direct & Fetched

30. © 2004Kizoom 30 Mediation Filtering of Data & Notifications to Reduce data traffic –Incremental Data Changes: Only send data changes since last update –Change threshold Only notify if change is more than a certain amount –Grouping of subscriptions One notification for changes to many subscriptions in a group

31. © 2004Kizoom 31 Mediation Interaction of simple patterns can be quite complex.

32. © 2004Kizoom 32 Possible Additional Work Items Real-time Facility Changes Service FR –Allows changes to availability of facilities and equipment of stop, vehicle and service to be exchanged in real time. This can be used for example to communicate equipment changes affecting impaired access to PT such as lift or escalator changes. Information is of use to real-time journey-planning and alert services. Should consider interchange aspects. Situation/Event Structured Incident model UK/FR –Enhance GMS to have preferred structured incident model for describing disruptions to services, model relates to SIRI, Based on TPEG + TransModel Control Actions Server Interface SE –Service for distributing control actions amongst participants, for example for coordinating management of late services. Traffic Status / Prioritisation Interface for UTMC UK/DE –Allows real-time public transport management systems to exchange information with road UTMC systems, eg to provide real time delay information a road speed information to the road traffic management system, or to allow for the exchange of signal priority options.

33. © 2004Kizoom 33 SIRI Further Technical Points

34. © 2004Kizoom 34 Recovery & Restart Subscriber is responsible for recreating subscriptions on restart, Consumer is responsible for Detecting Loss –Check Status –Heartbeat Consumer must know Subscriber!

35. © 2004Kizoom 35 Subscription Management Roles “Stateful pattern of interaction” –Subscriber assigns identifier –Notification Producer grants new subscriptions –Subscription manager handles any changes Notification Producer & Manager know each other Management Messages –SubscriptionRequest SubscriptionIdentifier –SubscriptionResponse Granted or refused –TerminateSubscriptionRequest

36. © 2004Kizoom 36 Extensions Access Control –Well defined Capabilities –Request based Checking Discovery –Capability –Coverage Stops Lines Product, Service, Vehicle - Features /Attributes ?

37. © 2004Kizoom 37 Access Controls Optional Capability on Requests –By ParticipantCode Configuration Matrix Restrict By –By Function &/or Capability (Static) E.g. Stop Events, Vehicle Movements –E.g. Subscribe, detail level –By Topic (Dynamic) E.g. Certain Stops, Certain Lines –By Resource level (Dynamic)

38. © 2004Kizoom 38 Appendix

39. © 2004Kizoom 39 Technical Challenges How to give migration path from existing standards –VDV, RTIG, TRIDENT –Allow alternative delivery patterns –Allow alternative formats for some detailed response messages where necessary. Semantically identical. –Allow modular, incremental implementation: roadmap What is canonical TransModel XML? –Trident XML not being kept current Further improvements in TransModel since Trident New developments/standards in XML / WS technology Further application requirements for SIRI What real-time efficiency optimisations are needed? –Principle of strict Transmodel Isomorphism ? –Allow different message patterns and tradeoffs

40. © 2004Kizoom 40 SIRI Data Models TransModel based; Small Subset Common Concepts& Elements –Participants (Systems) –StopPoints (Pluggable to national systems) –Lines, Directions –Journeys, VehicleJourneys & Calls DatedVehicleJourneys & Calls MonitoredVehcielJourneys & Calls ConnectingJourneys –Features Service Vehicle Product Common Structures –Isomorphic optimisations of TransModel for use in interface

41. © 2004Kizoom 41 Example Stop Monitoring Request NADER 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 P30M EH00001 7 2 normal

42. © 2004Kizoom 42 Example Stop Monitoring Delivery 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 2004-12-17T09:25:46-05:00 HLTST011 Line123 Out 2004-12-17 034567 123 Paradise Park VEH987654 0014 false 2004-12-17T09:40:44-05:00 2004-12-17T09:40:46-05:00 2004-12-17T09:42:47-05:00 2004-12-17T09:40:47-05:00 ……..