CEN/TS 15531-2:2007

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviations
5 Common communication aspects
   5.1 Data Exchange Patterns of Interaction
         5.1.1 General
         5.1.2 Request/Response Pattern
         5.1.3 Publish/Subscribe Pattern
         5.1.4 Publish/Subscribe with Broker Pattern
         5.1.5 Request/Response - Compound Requests
         5.1.6 Publish/Subscribe - Compound Subscriptions
   5.2 Delivery Patterns
         5.2.1 General
         5.2.2 Direct Delivery
         5.2.3 Fetched Delivery
         5.2.4 Data Horizon for Fetched Delivery
         5.2.5 Get Current Message
         5.2.6 Multipart Despatch of a Delivery
         5.2.7 Multipart Despatch of a Fetched Delivery - MoreData
   5.3 Mediation Behaviour
         5.3.1 General
         5.3.2 Mediation Behaviour - Maintaining Subscription
                Last Updated State
         5.3.3 Mediation Behaviour - Subscription Filters
   5.4 Recovery Considerations for Publish Subscribe
         5.4.1 General
         5.4.2 Check Status - Polling
         5.4.3 Heartbeat - Pinging
         5.4.4 Degrees of Failure
         5.4.5 Detecting a Failure of the Producer
         5.4.6 Detecting a Failure of the Consumer
   5.5 Recovery Considerations for Direct Delivery
   5.6 Request Parameters and Interactions
   5.7 Error Conditions for Requests
   5.8 Versioning
         5.8.1 General
         5.8.2 The Overall SIRI Framework Version Level
         5.8.3 The SIRI Functional Service Type Version Level
   5.9 Access Controls: Security and Authentication
         5.9.1 General
         5.9.2 System Mechanisms External to SIRI Messages
         5.9.3 Application Access Controls Reflected in SIRI
                Processing
   5.10 Service Discovery
         5.10.1 General
         5.10.2 Discovery of Servers that Support SIRI
         5.10.3 Discovery of the Capabilities of a SIRI Server
         5.10.4 Discovery of the Coverage of a Given SIRI
                Functional Service
   5.11 Capability Matrix
         5.11.1 General
         5.11.2 SIRI General Capabilities
6 Request/response
   6.1 Making a Direct Request
         6.1.1 General
         6.1.2 ServiceRequest Message
         6.1.3 The ServiceRequestContext
         6.1.4 Common Properties of ServiceRequest Messages
         6.1.5 ServiceRequest Example
         6.1.6 Access Controls on a Request
   6.2 Receiving a Data Delivery
         6.2.1 General
         6.2.2 ServiceDelivery Message
7 Subscriptions
   7.1 Setting up Subscriptions
         7.1.1 General
         7.1.2 SubscriptionRequest
         7.1.3 SubscriptionResponse
   7.2 Subscription Validity
   7.3 Terminating Subscriptions
         7.3.1 General
         7.3.2 The TerminateSubscriptionRequest
         7.3.3 TerminateSubscriptionResponse
8 Delivering data
   8.1 Direct Delivery
         8.1.1 Procedure
         8.1.2 DataReceivedAcknowledgement Message
         8.1.3 DataReceivedAcknowledgement Example
   8.2 Fetched Delivery
         8.2.1 General
         8.2.2 Signalling Data Availability
                (DataReadyNotification/DataReadyResponse)
         8.2.3 Polling Data (DataSupplyRequest/ServiceDelivery)
9 Recovery from system failure
   9.1 General
   9.2 Recovery after Client Failure
   9.3 Recovery after Server Failure
   9.4 Reset after Interruption of Communication
   9.5 Alive Handling
         9.5.1 General
         9.5.2 CheckStatusRequset
         9.5.3 CheckStatusResponse
         9.5.4 HeartbeatNotification
10 Transport of SIRI messages
   10.1 Separation of Addressing from Transport Protocol
   10.2 Logical Endpoint Addresses
         10.2.1 Endpoint Addresses
         10.2.2 Endpoint Address Examples
   10.3 Parallelism and Endpoint Addresses
   10.4 Encoding of XML messages
         10.4.1 Principles
         10.4.2 Encoding of Errors in XML
         10.4.3 Character Set
         10.4.4 Schema Packages
   10.5 Use of SIRI with SOAP
         10.5.1 General
         10.5.2 Web Services
         10.5.3 Use of SOAP
         10.5.4 SIRI WSDL
         10.5.5 WSDL Producer Server Operations
         10.5.6 WSDL Client Operations
         10.5.7 SIRI WSDL Status
11 Capability discovery requests
   11.1 General
   11.2 Capability Request
   11.3 Service Capability Discovery Request
   11.4 Service Capability Discovery Response
   11.5 Service Capability Discovery Response
         11.5.1 General
         11.5.2 Service Capability Response Example
   11.6 Functional Service Capability Permission Matrix
         11.6.1 General
         11.6.2 OperatorPermissions
         11.6.3 LinePermissions
         11.6.4 ConnectionLinkPermissions
         11.6.5 StopMonitorPermissions
         11.6.6 VehicleMonitorPermissions
         11.6.7 InfoChannelPermissions
12 Shared groups of elements
   12.1 General
   12.2 FramedVehicleJourneyRef
   12.3 ServiceInfoGroup
   12.4 VehicleJourneyInfoGroup
   12.5 JourneyPatternInfoGroup
   12.6 DisruptionGroup
   12.7 JourneyProgressGroup
   12.8 Location
   12.9 OperationalBlockGroup
   12.10 OperationalInfoGroup
   12.11 Error
Bibliography

SIRI uses a consistent set of general communication protocols to exchange information between client and server. The same pattern of message exchange may be used to implement different specific functional interfaces as sets of concrete message content types.Two well-known specific patterns of client server interaction are used for data exchange in SIRI: Request/Response and Publish/Subscribe.-Request/Response allows for the ad hoc exchange of data on demand from the client.-Publish/Subscribe allows for the repeated asynchronous push of notifications and data to distribute events and Situations detected by a Real-time Service.The use of the Publish/Subscribe pattern of interaction follows that described in the Publish-Subscribe Notification for Web Services (WS-PubSub) specification, and as far as possible, SIRI uses the same separation of concerns and common terminology for publish/subscribe concepts and interfaces as used in WS-PubSub. WS-PubSub breaks down the server part of the Publish/Subscribe pattern into a number of separate named roles and interfaces (for example, Subscriber, Publisher, Notification Producer, and Notification Consumer): in an actual SIRI implementation, certain of these distinct interfaces may be combined and provided by a single entity. Although SIRI is not currently implemented as a full WS-PubSub web service, the use of a WS-PubSub architecture makes this straightforward to do in future.For the delivery of data in responses (to both requests and subscriptions), SIRI supports two common patterns of message exchange, as realised in existent national systems: -A one step ‘Direct Delivery’, as per the classic client-server paradigm, and normal WS-PubSub publish subscribe usage; and; -A two step ‘Fetched Delivery’ which elaborates the delivery of messages into a sequence of successive messages pairs to first notify the client, and then to send the data when the client is ready.