CCS content. CI - Common Interface TAF/TAP TSI Common Interface (CI) for data exchange between IMs/RUs and between RU

Transcription

1 1

2 CCS content CRD - Central Reference File Database Reference files for locations Reference files for companies TAF TSI Metadata (self contained schemas) CI - Common Interface TAF/TAP TSI Common Interface (CI) for data exchange between IMs/RUs and between RU Locally installed Could be used also for messages outside the regulation CA - Certification Authority All actors require a X509 certificate for secure communication CA is established RNE provides the X509 certificates for TLS/SSL 27 January,

3 Regulation 1305/2014 and 454/2011 Telematics Application for Freight Services and Telematics Application for Passenger Services Both Regulation requires from Rail Industry to support certain business processes by exchanging of standardized messages. Involved Actors are: Infrastructure Manager (IM) Railway Undertakings (RU) Waggon keeper (WK) Station Master (SM) Legal background 27 January

4 TAF TSI Functions Grouped Joint IM-RU Functions Reference Files Common Interface Short Term Path Request Train Preparation Train Running Information Train Forecast Service Disruption Deviations from plan (TAP) (Train Identifiers) RU (fright) Only Functions * Consignment Note Data WIMO Wagon Movement Shipment ETA * Commercial part of TAP is not considered in the table 27 January

5 Regulation 1305/ Repealing the Regulation (EC) No 62/ Reference Files For the operation of freight trains on the European network the following reference files must be available and accessible to all service providers (IMs, RUs, logistic providers and fleet managers)... Centrally stored and administrated: Reference File of the Coding for all IMs, RUs, Service provider companies; Reference File of the Coding for Freight Transport Customers; Reference File of the Coding of Locations (Primary and subsidiary). 27 January

6 Regulation 1305/ Data Quality For data quality assurance purposes, the originator of any TSI message will be responsible for the correctness of the data content of the message at the time when the message is sent. Where the source data for data quality assurance purposes is available from the databases provided as part of the TSI, the data contained within those databases must be used for data quality assurance.. 27 January

7 Reference files Country (ISO 3166) Company Location Primary Location Subsidiary Location Subsidiary Location Type 27 January

8 Reference File Country The Country code is as part of Location Code. Locations are unique per Country 27 January

9 Reference File Company The Company Code is part of location code. Also the identification by the Company code is a pre-condition for the usage of the Common Interface, as it is used for identification in the Message Header of TAF / TAP messages. 27 January

10 Allocation of Company Codes Status of registered Companies December 2015 Companies Passenger Freight Infrastructure Others Companies UIC (Allocation Entity) CRD (operated by RNE ) TAF / TAP Actors subscribe check, register maintain CRD Access to company codes Subscription + Maintenance Fee UIC RNE Maintenance Agreement CCS User Agreement 27 January

11 Apply for a Company code at European central entity At the time being this is UIC, independent if company is UIC member or not It is the same as known by RICS code Apply at Get registered as Company After registration the company code will be maintained in the Central Reference File Database (CRD) 27 January

12 Location Reference File Location is a place, a geographic point, inside or outside the rail network, which is needed to be identified for operational, technical, administrative or statistical purposes. This can be either a Railway or a Customer location Primary Location This location is a network rail point managed by an Infrastructure Manager (IM). Code is managed nationally by an allocation entity May be an Infrastructure Manager May be a national Location entity 27 January

13 Primary Location Examples Trains can start, end, stop, change line and time needs to be provided. 27 January

14 Location coding example Primary location example 27 January

15 Subsidiary Location Subsidiary Location identifies a location as a part of primary location e.g. a junction, a signal, a marker point, etc. This may be a non-rail point or a rail point that is not managed by an Infrastructure Manager (IM). Subsidiary location without Primary location is not possible. It is always in combination with a Primary Location. Subsidiary locations have subsidiary type code 27 January

16 Subsidiary Location Examples 27 January

17 Subsidiary Location Type 27 January

18 Subsidiary Location Type Subsidiary location Types are part of the TAF coding schema At the type code it is indicated which entity is in principle allowed to maintain the subsidiary locations 27 January

19 Subsidiary Location example 27 January

20 Common Components System 27 January

21 What is the Common Components System? Central Reference Files Database (CRD) * Coding of Locations and Companies Common Metadata Certificate Authority * which provides X509 certificates for secure communication Common Interface (CI) a software package which is locally installed within the user s IT environment *) In the regulation also mentioned as Central Repository Domain 27 January

22 Who developed CCS? The TAF TSI Common Components Group (CCG) a Special Group of UIC have developed the CC and are in roll-out since January Stakeholders Main European Infrastructure Managers and some smaller ones o DB Netz, RFF, RFI, Infrabel, ProRail, PLK, MAV, NetworkRail, Eurotunnel, etc. Largest Freight Railway Undertakings and some smaller ones o DB Schenker Group, SNCF fret, Trenitalia, RCA, Green Cargo, etc. Current Supplier (contractor) EVRY - largest IT supplier in Nordic countries 27 January,

23 The CCG General Assembly on 9 December 2014 approved the transfer of the Common Components to RNE with all the verification transfer conditions successfully implemented. The CCG was dissolved on 31 December What was Transferred?: Software IP Rights (IPR) Service Contracts Transfer of the CC to RNE As of 1 January 2015, RNE is now in charge of further development, maintenance and on-going operations of the TAF TAP Common Components. 27 January

24 Common Components System at RNE RNE is charged since 1st January 2015 with the further development, maintenance and on-going operations of Common Interface (CI) Central Reference Files Database (CRD) The Location Reference File which uniquely identifies physical rail points (e.g. stations, customer sidings, loading places) The Partner Reference File uniquely identifies all rail actors who exchange information (Company Codes) Certificate Authority 27 January

25 Allocation Process Location Data 27 January

26 How to feed the Reference files 1) CSV file Maintenance of location reference files by national entities (or registered companies for defined subsidiary type codes) Central Reference File Database (CRD) 2) WEB GUI (Browser) Https CRD Location codes: - Primary - Subsidiary Common Interface 3) Legacy location database (messaging) A B C D Configuration Mapping Metadata Routing and Security 27 January 2016

27 Ask for import templates at RNE by Deliver an CSV file with the qualified Location coding by to RNE Find more information in the TAF / TAP sector handbook in chapter 9 Initial Population content/uploads/2015/11/ _tap_taf_ru_im_sector- Handbook_v2.1.2_1.1.pdf 27 January

28 Reference file distribution CRD Reference file download via authenticated WS directly to a legacy system Filter parameters Search Export via HMI Filter parameters (e.g. last modified date, country, subsidiary type code) CI local Instance Replication Reference files via Web Service (WS) to Local Instance Filter parameters (e.g. last modified date, country, subsidiary type code) Scheduler defined by Local Instance of CI Company Legacy System Search and export via Browser on Local Instance Reference file download via WS to Legacy System Filter parameters (e.g. last modified date, country, subsidiary type code) Scheduler to be defined by Legacy System 27 January

29 Two variants of Reference file replication Via local Common Interface CRD Directly from CRD to legacy System via secure Web service Deletions Locations Reference file download via authenticated WS and registered user directly to a legacy system Filter parameters CI CI local Instance Deletions Locations Locations Legacy System Company 27 January

30 Reference File Replication - Configuration on Common Interface 27 January

31 Status of Reference File System System is up and running, operated by RNE First population of operational, quality approved location data was started in May 2013 More than 150 Users are registered on CRD More than Primary Location codes are populated by end of December 2015 for 39 Infrastructure Managers Infrastructure Managers / National Location Entities are requested to populate and maintain the location data (primary Location) 27 January

32 Status of Location Codes At least 1 large IM published In Progress Not populated yet Non ex CCG IM ~ Primary Locations for 39 IM ~ 330 Subsidiary Location Type 36 ~ 330 Subsidiary Location Type 42 ~ Subsidiary Location Type 41 01/ January

33 Common Interface 27 January

34 Regulation 1305/ Repealing the Regulation (EC) No 62/ Common interface The common interface is mandatory for each actor in order to join the rail interoperability community The common interface has to be able to handle: message formatting of outgoing messages according to the metadata, signing and encryption of outgoing messages, addressing of the outgoing messages, authenticity verification of the incoming messages decryption of incoming messages conformity checks of incoming messages according to metadata, handling the single common access to various databases Where a Common Interface is in common use with the TAP TSI, the development and changes must be in line with TAP TSI, in order to achieve optimum synergies. 27 January

35 Regulation 454/ Common interface for RU / IM communication The common interface is mandatory for each actor in order to join the rail interoperability community. The common interface has to be able to handle: message formatting of outgoing messages according to the metadata, signing and encryption of outgoing messages, addressing of outgoing messages, authenticity verification of incoming messages, decryption of incoming messages, conformity checks of incoming messages according to the metadata, handling the single common access to the various databases. Where the Common Interface is in common use with the TAF TSI, the development and changes shall take place as closely as possible to the implemented TAF TSI, in order to achieve optimum synergies. 27 January

36 Architecture Supporting Peer2Peer ISR Orfeus HMI Reference files Location ID Company ID CI CI CRD Common Meta Data Certificate Authority RU CI IP Network CI Wagon Ref. Files CI Wagon Ref. Files RU CI CI CI CI CI - Common Interface IM - Infrastructure Manager RU - Railway Undertaking HMI - Human Machine Interface SM - Station Master CRD Central Reference File Database IM 1 IM 2 SM CI RU CI RU RU CI RU RU 27 January

37 Common Interface Reference Implementation 27 January

38 Communications 27 January

39 Certificate Authority (CA) RNE acts as a Certificate Authority (CA) and provides X-509 certificates to support secure communication between partners, along with message-based encryption and signature. X-509 certificates are requested for: SSL/TLS communication on Https between CI A and CI B, and between CI A / CI B and CRD Encryption of messages Signature of messages. Only certificates from the RNE Certificate Authority (with the same root) will trust each other. 27 January

40 The Common Interface Reference Implementation was build by the TAF TSI Common Components Group based on Requirements TAF Common interface TAP Common Interface for RU / IM Communication TAF Appendix E : TAF TSI Appendix D.2: Appendix E COMMON INTERFACE European public tender Stakeholder funding EU Commission funding CI Reference Implementation 27 January

41 CI Hardware Requirements Hardware to be provided and operated locally by User company 27 January

42 Download of software and documentation Software and Documentation can be downloaded from ftp server Server, User name and password will be provided by Helpdesk 27 January

43 Installation using Install Jammer Hardware to be provided locally by user company Win OS and Linux RedHat Enterprise are supported. Other Linux distributions may also work, but have not been tested. Hardware sizing depends on the required message throughput LI Installation is automated using Install Jammer and bundled as executable. Separate installable for Windows and Linux platforms. This will install the following software : MySQL 5.x or 5.5 (64bit) Java 1.8.x JBoss 6.1 with ESB 4.10 LI application components Administration after installation via a Web Browser from remote Language of all documentation and User Guide is English GUI can be translated localy (effort to be taken) 27 January

44 What can be expected? The CI Reference Implementation will support Multiple Instances, if desired Installation Support Documentation and User Manuals Service Desk On-line Ticket Support Telephone Support Working Hours Hot-line Support 24hour incident management 27 January

45 LS / Connectors LS (Legacy Systems) Existing (or future) IT applications which will use an CI to exchange messages LI (Local Instance of a Common Interface) Connector Part of the LI used to link a LS to CI (and vice-versa) Connector Types are File System JMS / WMQ IP-Socket FTP (client) Web Service (defined by CI) JMS SMTP 27 January

46 Message Format Examples UIC Leaflet (text + binary) = private Format 27 January

47 UIC Leaflet (text + binary) Private Message Examples MFLI Flintsbach MKI Kiefersfelden January

48 Private Message Format Examples UIC Leaflet Hermes 30 (xml) = private 27 January

49 Private Message Examples xml UIC Leaflet Hermes 30 (xml) = private <?xml version="1.0" encoding="utf-8"?><preadvice_404-2_2006><g1><h1>2174</h1><h2>0016</h2><h3> T00:10:39+02:00</H3><H4>1</H4><H5>02</H5><H6>1</H6></G1><G5_A_1><I5_A_1_1>44801</I5_A_1_1><I5_A_1_2> T02:43:00+02:00</I5_A_1_2><I5_A_1_3> T00:42:00+02:00</I5_A_1_3></G5_A_1><G5_A_2><I5_A_2_1>1</I5_A_2_1><G5_A_2_2><I5_A_2_2_1>2180</I5_A_2_2_1><I5_A_2_2_2>2181</I5_A_ 2_2_2><G5_A_2_3_1><I5_A_2_3_1_1>80</I5_A_2_3_1_1><I5_A_2_3_1_2>62</I5_A_2_3_1_2></G5_A_2_3_1></G5_A_2_2></G5_A_2><G5_A_3><I5_A _3_1>1</I5_A_3_1><I5_A_3_2>23</I5_A_3_2><G5_A_3_3><I1_0> </I1_0><I3_11>1</I3_11><I1_1>04</I1_1><I1_2>120</I1_2><I1_3>0270 0</I1_3><I1_4>026900</I1_4><G1_5><I1_5_1>1</I1_5_1><I1_5_2>13</I1_5_2></G1_5><I1_6>0</I1_6><G1_7><I1_7_1>2</I1_7_1><I1_7_2>20</I1_7_2 ></G1_7><G1_8><I1_8_1>3</I1_8_1><I1_8_2>0</I1_8_2><I1_8_4>029</I1_8_4><I1_8_4>029</I1_8_4></G1_8><I1_9>090</I1_9><I1_10>2</I1_10><I1_ 12>080</I1_12><I1_17>0900</I1_17><I1_18>ATG </I1_18><G2_2><I2_2_1>1</I2_2_1><G2_2_2><G2_2_2_1><I2_2_2_1_1>00</I2_2_2_1_1></G2_2_2_1><G2_2_2_2><I2_2_2_2_1>2</I2_2_2_2_1><G2_ 2_2_2_2><I2_2_2_2_2_1>100</I2_2_2_2_2_1><I2_2_2_2_2_2>2</I2_2_2_2_2_2><I2_2_2_2_2_1>120</I2_2_2_2_2_1><I2_2_2_2_2_2>0</I2_2_2_2_2_ 2></G2_2_2_2_2></G2_2_2_2><G2_2_2_3><I2_2_2_3_1>03</I2_2_2_3_1><I2_2_2_3_2>A</I2_2_2_3_2><I2_2_2_3_2>B</I2_2_2_3_2><I2_2_2_3_2>C< /I2_2_2_3_2></G2_2_2_3><I2_2_2_4>0185</I2_2_2_4><I2_2_2_4>0000</I2_2_2_4><I2_2_2_4>0185</I2_2_2_4><I2_2_2_4>0000</I2_2_2_4><I2_2_2_ 4>0185</I2_2_2_4><I2_2_2_4>0000</I2_2_2_4></G2_2_2><I2_2_3>120</I2_2_3></G2_2><I2_3>02650</I2_3><G2_6><G2_6_1><I2_6_1_1> </I2_6_1_1><I2_6_1_2>6</I2_6_1_2></G2_6_1><I2_6_2> </I2_6_2></G2_6><G2_8><I2_8_1> </I2_8_1><I2_8_2>12</I2_8_2></G2_8><G3_1><G3_1_1><I3_1_1_1>84</I3_1_1_1><G3_1_1_2><I3_1_1_2_1> January

50 Message Header You may use the Common Interface also for other messages than TAF and TAP TSI framework The Standard Message Header is required in all Messages exchanged between Common Interface First node after the root node in the x-path Must be included in common or shared metadata MessageReference (Type, Version, Identifier, DateTime) MessageRoutingID (optional) SenderReference (optional) Sender / Receiver Common and shared metadata are technically the same only difference is the legal view on it 27 January

51 Message Header Position of the Header in common / shared Metadata 27 January

52 Message Header 27 January

53 Message Example TAF Message <?xml version="1.0" encoding="utf-8"?><trainrunninginformationmessage> <MessageHeader> <MessageReference> <MessageType>2002</MessageType> <MessageTypeVersion>5.1.9</MessageTypeVersion> <MessageIdentifier>d f4e-844a-fb8beafa9c05</MessageIdentifier> <MessageDateTime> T08:20: :00</MessageDateTime> </MessageReference> <Sender>0080</Sender> <Recipient>0016</Recipient> </MessageHeader> <MessageStatus>1</MessageStatus> <OperationalTrainNumberIdentifier> <OperationalTrainNumber> </OperationalTrainNumber> <ScheduledDateTimeAtTransfer> T18:15:00+01:00</ScheduledDateTimeAtTransfer> </OperationalTrainNumberIdentifier> <ReferenceOTN> <OperationalTrainNumberIdentifier> <OperationalTrainNumber> </OperationalTrainNumber> <ScheduledDateTimeAtTransfer> T15:00:36+01:00</ScheduledDateTimeAtTransfer> </OperationalTrainNumberIdentifier> </ReferenceOTN> <TrainLocationReport> <Location> <CountryCodeISO>DE</CountryCodeISO> <LocationPrimaryCode>20534</LocationPrimaryCode> <PrimaryLocationName>Flintsbach </PrimaryLocationName> </Location> > 27 January

54 LI Application Setup The Work Flow See also chapter 5 in User guide Configuring the Application 27 January

55 Mapping Definition 27 January

56 Mapping Functions 27 January

57 Message Routing 27 January

58 Message Processing Always push principle SOAP request contains in the SOAP body the message Acknowledgment between LS and CI depend on protocol WS > Http status 200 JMS > internal JMS queuing behaviour MQ > internal queuing behaviour IPS > acknowledgment Between CI there is message acknowledgment Message will be deleted on sending CI, only if ACK is received from Remote CI No end to end acknowledgment If required then application acknowledgment needs to be implemented (will be for the CI a regular message) 27 January

59 Example on Web service connectors Message Processing 27 January

60 Communication between LI Web Service Communication between LIs is done on SOAP (Https) Port 443. For each message a SOAP request is executed containing the message. The remote LI will send in the response an acknowledgment if the message is successfully arrived and persistent in the remote LI. Proxy configuration is possible. For the SSL communication a X.509 certificate has to be obtained from the RNE CC Service Desk. Heartbeat Between LIs Heartbeat Request is implemented. The LI sends Heartbeat requests to all configured remote LIs (Are you alive?). If the network is working and the remote LI is alive the remote LI will send back the HEART_BEAT_WS_RECEIVED. Encryption, Signature, Compression Besides the SSL communication on the transport layer message based encryption, signature, compression is supported. The configuration will be done in routing configuration and could be done by message type and sender/recipient, as agreements between partners require. The message can be digitally signed for security purposes. For signing, you have to obtain a client certificate from the RNE, which is the same as for SSL and encryption The TAF/TAP message payload in the request can be encrypted for security. The TAF/TAP message payload in the request can be compressed in order to save bandwidth and for faster communication. CI uses ZLIB compression libraries (Deflate and Inflate provided by JDK 1.6 for message compression and decompression). 27 January

61 Message Processing Graphical Overview 27 January

62 Message Processing Log OutboundMessageProcessing ConnectorTextLog ConnectorXMLLog IPS Log MessageProcessingLog ErrorLog InboundMessageProcessing MessageProcessingLog ErrorLog ConnectorTextLog ConnectorXMLLog Other Logs RemoteLIHeartBeatCheckLog.log LI.log Replication log 27 January

63 Troubleshooting and FAQ RNE provides CCS Service Desk Management which acts as Helpdesk and Incident desk. Ticket tool Service requests FAQ Section 27 January

64 RNE CCS Helpdesk Getting Access to Helpdesk Application for Help Reporting Incidents through Helpdesk Application Weekday 9:00 17:00 Help Desk Support 24 * 7 Incident Support Helpdesk Mail Helpdesk Phones 27 January

65 Status on Common Interface implementation 10 CI in Test 26 CI with Data exchange CI = Common Interface 01/

66 Price Model Adapted Price Model from 1 st January 2016 Common Interface One off Registration Fee Yearly Maintenance Fee Reference Files One off Registration Fee Yearly Maintenance Fee January

67 How to become a CCS user? Access to CCS for TAF and TAP actors is based on a user agreement that needs to be signed beforehand: In order to become a CCS User Please provide the following information to support.ccs@rne.eu: Name, company and department Contact details (phone, , postal address) More information about CCS can be found on our website at: 27 January

68 Thank you! 68