Date post: | 03-Jan-2016 |
Category: |
Documents |
Upload: | cleopatra-parrish |
View: | 221 times |
Download: | 0 times |
© 2004Kizoom
1
PROTOCOLS
DataContent
ExchangeBehaviour
TransportProtocol
Common Submodels? Location, Base Types, Incidents
•Request / Response•Publish/Subscribe•Topic Filtering•Policy Filtering•Restart /Heartbeat
WS PUB SUB
Lite: Http GetMedium HTTP POST + XMLHeavy SOAP, ORB
© 2004Kizoom
2
DATEX II
DataContent
ExchangeBehaviour
TransportProtocol
defined XML schema (draft, work in progress)
D2 deliverablespecifies…may be revised?
in progress for2006 publicationHTTP GET, POST,SOAP.
© 2004Kizoom
3
SIRI
DataContent
ExchangeBehaviour
TransportProtocol
well-defined interactionswith XML schemarepresentations
Mainstream Internet•HTTP POST,•SOAP.
definedXML SchemaFor payload
XML XML Http Post
SOAP
TransModel WS-PubSub
http get ?
IP
© 2004Kizoom
5
SIRI XSD Packages – Layered Reuse
Common
Request Management
Common
Request Management
SIRI Functional Services
SIRI Functional Services
Low Level TypesLow Level Types SIRISIRICommon
ModelCommon Model
© 2004Kizoom
6
Acceptable Optimisations =TransModel Isomorphic?
A
B
F
C
D
*
*
Bs
Cs
E
G *
1 1
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
*
© 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.
© 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
© 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
© 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
© 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
© 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
© 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
© 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
© 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
© 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
© 2004Kizoom
21
SIRI Connection Services
• Connection Timetable (CT)– Distribute planned interchanges
• Stop Centric • Provisions Clients.
• Connection Monitoring (CM)– Connection management– Guaranteed connection support
© 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
© 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
© 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
© 2004Kizoom
26
Communications Framework Patterns
• Alternate Patterns of Interaction1. 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
© 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
© 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.
© 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!
© 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
© 2004Kizoom
36
Extensions
• Access Control– Well defined Capabilities– Request based Checking
• Discovery– Capability– Coverage
• Stops• Lines• Product, Service, Vehicle - Features /Attributes ?
© 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)
© 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
© 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
© 2004Kizoom
41
Example Stop Monitoring Request
<ServiceRequest> • <RequestorRef>NADER</RequestorRef>• <RequestTimestamp>2004-12-17T09:30:47-05:00</RequestTimestamp>• <StopMonitoringRequest version=“1.0”>• <!-- All services from stop EH00001 in the next 30 mins-->• <RequestTimestamp>2004-12-17T09:30:47-05:00</
RequestTimestamp>• <!--=======TOPIC ======= -->• <PreviewInterval>P30M</PreviewInterval>• <MonitoringRef>EH00001</MonitoringRef>• <!--=======POLICY===========-->• <MaximumStopVisits>7</MaximumStopVisits>• <MinimumStopVisitsPerLine>2</MinimumStopVisitsPerLine>• <StopMonitoringDetailLevel>normal</StopMonitoringDetailLevel>• </StopMonitoringRequest></ServiceRequest>
© 2004Kizoom
42
Example Stop Monitoring Delivery• <StopMonitoringDelivery version="0.1d">• <ResponseTimestamp>2004-12-17T09:30:47-05:00</ResponseTimestamp>• <SubscriberRef>NADER</SubscriberRef>• <SubscriptionRef>2004-12-17T09:30:47-05:00</SubscriptionRef> • <!--====FIRST ARRIVAL ============================================ -->• <MonitoredStopVisit>• <RecordedAtTime>2004-12-17T09:25:46-05:00</RecordedAtTime>• <MonitoringRef>HLTST011</MonitoringRef>• <MonitoredVehicleJourney> • <LineRef>Line123</LineRef>• <DirectionRef>Out</DirectionRef>• <FramedVehicleJourneyRef>• <DataFrameRef>2004-12-17</DataFrameRef>• <DatedVehicleJourneyRef>034567</DatedVehicleJourneyRef>• </FramedVehicleJourneyRef> • <PublishedLineName>123</PublishedLineName>• <DestinationName>Paradise Park</DestinationName> • <VehicleRef>VEH987654</VehicleRef>• <MonitoredCall>• <VisitNumber>0014</VisitNumber>• <VehicleAtStop>false</VehicleAtStop> • <AimedArrivalTime>2004-12-17T09:40:44-05:00</AimedArrivalTime>• <ExpectedArrivalTime>2004-12-17T09:40:46-05:00</ExpectedArrivalTime>• <AimedDepartureTime>2004-12-17T09:42:47-05:00</AimedDepartureTime>• <ExpectedDepartureTime>2004-12-17T09:40:47-05:00</ExpectedDepartureTime>• </MonitoredCall> • </MonitoredVehicleJourney>• </MonitoredStopVisit>• ……..• </StopMonitoringDelivery>