METHOD FOR PAPERLESS COMMISSIONING OF A RAIL LINE POINT
Patent Information
- Application Number
- DE502020009585
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-01-22
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2040-01-22
AI Technical Summary
The existing paper-based commissioning process for train control components in railway safety systems is cumbersome, prone to errors, and requires managing numerous files, which complicates infrastructure management, especially when configuration data changes.
A method for paperless programming and commissioning of control units that combines test-relevant data, including control data and checksums, into a single PDF file, using a project planning tool to provide a template with embedded encrypted checksums, calculates and compares checksums, and generates a final test report with metadata, reducing the number of files and ensuring compliance with safety standards like SIL4.
This method significantly reduces the number of files to manage, ensures error-free programming, and maintains compliance with safety standards by embedding critical information directly in the test report, allowing for efficient electronic documentation and verification, thus simplifying the commissioning process and reducing the risk of errors.
Description
[0001] The present invention relates to a method for paperless programming and commissioning of a control unit for a train protection component of a railway safety system, such as a MiniLEU S11, a LEU S21 and an MSTT signal for a train protection component, such as an ETCS Eurobalise, an ETCS Euroloop, a signal, a switch.
[0002] In the system engineering of European Train Control Systems (ETCS) line components (these are, for example, Eurobalises or Lineside Electronic Units), test reports have been generated in PDF format for around 20 years, printed out on paper and completed by hand during commissioning of the components. In addition to checksums, the name, date and signature of the inspector must be entered. The completed form is then scanned into a PDF document as evidence of the work carried out and the paper original is filed, for example, in the signal box of a railway operator. The same procedure is available to the railway operator's staff for maintenance work; they can then print out the provided blank test reports in PDF format themselves and use them accordingly. The set of test reports comprises two to four test reports (files) for each line component.In addition to these test reports and the programmable control data, the documentation of track components always includes files (e.g., XML or XLSX) with tables containing the contents of the planned ETCS data (configuration, telegrams, etc.) in a readable, verifiable, and electronically processable format. This is extensive information that is not included in the test reports. The conventional testing procedure using paper forms requires that the test reports be completed by two different people.
[0003] Specifically, the process for commissioning / acceptance of a trackside control unit previously required commissioning personnel to take printed test sheets, which contained the expected checksums for verifying the design data loaded onto the control unit, to the associated track point (where the track point is the combination of the control unit and the train protection unit in / on the track). After successful configuration and testing of the control unit (the target device) on site, commissioning personnel must sign the completed test sheets and then archive them. Given the large number of track points and the commissioning personnel's greater or lesser exposure to the elements, it is easy to imagine that the use of paper test sheets could lead to confusion and / or soiling and / or softening due to snow / rain.
[0004] European patent EP 2 927 088 B1 specifies a method for paperless commissioning of a control unit for a train protection component, which simplifies commissioning for commissioning personnel while simultaneously maintaining the required safety level according to SIL4. For the purposes of this application, the control unit is also considered synonymously as a target system. Specifically, a method for paperless commissioning of a control unit, in particular a MiniLEU S11, a LEU S21, and an MSTT signal, for a train protection component, in particular an ETCS balise, a signal, a switch, a level crossing, or an axle counter, is disclosed. The method comprises the following steps: a) Providing test-relevant data by means of a configuration tool for a programming tool, wherein the test-relevant data comprises the control data for the train control unit, a template for a second test report, and encrypted target values of checksums to check the correct loading of the control data onto the control unit; b) Programming the control unit by the programming tool with the control data provided by the configuration tool; c) Calculating checksums for the programmed control data on the control unit using a key unknown to the programming tool and transferring these calculated checksums to the programming tool; d) Comparing the calculated checksums with the encrypted target values for the checksums within the framework of a first test report to provide a second test report on the programming tool;e) displaying the result of the first test report on the programming tool and acknowledging a match between the calculated checksums and the encrypted target value for the checksums by a tester, f) creating the second test report using the template for the second test report supplied by the configuration tool, adding the identity of the tester as well as the calculated checksums and the encrypted target values for the checksums, isolated on the programming tool; and g) transferring the second test report from the programming tool to a database and archiving the second test report in the database.
[0005] In this way, this procedure, using the programming device, makes it possible to commission the route point paperlessly, or in other words, to guarantee its error-free programming. The commissioning personnel are only asked once to confirm the agreement of the calculated checksums with the encrypted target values for the checksums within the framework of the provided second test report. The first test report can be displayed in a very simple format on the programming tool, e.g., "Checksum comparison OKAY." Thus, only one person is required to carry out the test procedure on site.
[0006] Unfortunately, this electronic testing procedure has the disadvantage that it also generates a large number of files that must be continuously updated even when the design data changes. This poses significant challenges, especially for the infrastructure operator, regarding file management. These files include the PDF test reports for paper printouts, the scanned test reports, the template for the test report in text format, the file with the encrypted checksums, an electronically verified PDF test report, data tables for the control data (which include all relevant values recorded in the design tool), etc.
[0007] The present invention is therefore based on the object of specifying a method for paperless programming and commissioning of control units, which significantly reduces the number of files to be managed per control unit and nevertheless - if desired - leaves open the possibility of accepting the control unit in the old way with a paper test report.
[0008] This object is achieved according to the invention by a method for paperless programming and commissioning of a control unit for a train protection component of a railway safety system, such as a MiniLEU S11, a LEU S21 and an MSTT signal for a train protection component, such as an ETCS Eurobalise, an ETCS Euroloop, a signal, a switch, which comprises the following steps: a) Providing test-relevant data by means of a project planning tool for a programming tool, wherein the test-relevant data comprises the control data for the train protection component and a template in PDF format for a test report, and encrypted target values of checksums embedded in the template for the test report as metadata for checking the correct loading of the control data onto the control unit or for checking the completeness of commissioning; b) Programming the control unit by the programming tool with the control data provided by the project planning tool; c) Calculating and transferring actual checksums for the programmed control data from the control unit to the programming tool;d) Comparing the calculated checksums with the encrypted target values for the checksums embedded in the test report template to provide acknowledgment options in the test report on the programming tool; e) Displaying the result of the comparison on the programming tool and acknowledging a match between the calculated checksums and the target values for the checksums by a tester; f) Creating the final test report in PDF format using the test report template supplied by the design tool, embedding the identity of the tester and the calculated actual values of the checksums in the printable area of the test report and embedding this information as metadata in the test report on the programming tool; and g) Transferring the final test report, including all data embedded therein, from the programming tool to a database and archiving the test report in the database.
[0009] The advantages of the method according to the invention therefore lie in the consolidation of information into a single file which previously had to be stored and managed in different files, whereby this consolidation does not result in any loss in the area of application (usage processes) of the files. When using the invention, for example, for a Eurobalise in the application for Swiss railway customers only one PDF file needs to be created and managed instead of the previous four files, and for application in an international environment only two PDF files need to be created and managed as the starting point for programming and commissioning instead of the previous six files. For a Lineside Electronic Unit (LEU), the difference is two files instead of six for application in Switzerland and four files instead of seven for the international environment.
[0010] A further benefit arises from the optional embedding of the control data for the train control unit (train protection component) and possibly also the data tables for the control data (which include all relevant values recorded in the design tool) in the test report template in PDF format. This creates a direct context between the data in the programmable format, the data content in readable form, and the data verification. Publicly accessible methods allow the documentation to be extracted from both an uncompleted test report (template) and an electronically completed test report. If this evaluation is performed on the electronically completed test report, the embedded information can also be obtained and verified, showing who checked what, when, where, as well as the data status (checksum), and the data content involved.
[0011] A particularly advantageous embodiment of the present method can be achieved if the encrypted target values for the checksums are transmitted to the programming tool in a form that cannot be read and evaluated by a machine. This ensures that the calculated actual checksum was actually determined by the control unit and that the encrypted target values for the checksums contained as specifications in the programming tool are not erroneously output as actual values due to an error of any kind. This procedure is particularly relevant because the control data and the control units implemented with it must comply with the highest safety level in the railway sector, SIL4. However, the programming tool and the software (project planning tool) used to configure the control unit do not have to meet any safety level in the sense of a SIL level.
[0012] In a further advantageous embodiment of these variants, it can be provided that the target values for the checksums themselves are not transmitted in the template for the test report, but that a further hash checksum (for example, using the SHA 512 algorithm according to RFC 6234) is calculated and transmitted for each checksum target value. The actual target value of the checksum can no longer be determined from such a checksum. This ensures that the programming tool cannot mistakenly use the target values of the checksums for display or comparison instead of the actual values. To perform the comparison, the programming tool must therefore calculate hash checksum values based on the checksums from the calculated actual values of the checksums, using the same method as the configuration tool.
[0013] When generating the test report template using the project planning tool, as well as when generating the test report using the programming tool, it is advantageous for these reports to be created in PDF format according to ISO Standard 19005-3 or higher. The metadata is incorporated into the reports using the Extensible Metadata Platform (XMP) standard ISO 16684-1 or higher. While this metadata is not visible when the document is opened with a PDF reader, it can of course be electronically evaluated and displayed accordingly using appropriate evaluation tools.
[0014] Preferred embodiments of the present invention are explained in more detail below with reference to the drawing. The figure schematically shows the sequence of the method according to the invention.
[0015] The figure shows schematically the procedure for the paperless commissioning of a route point, such as an ETCS transparent data balise as a train control unit with its associated control unit 20 - also called target system.
[0016] In a first step 1, a project planning tool 10 provides test-relevant data for a programming tool 12. The project planning tool 10 can, for example, be linked to a signal box or a control system from which it receives the corresponding test-relevant data. Alternatively, the project planning tool 10 can also be enabled so that the test-relevant data can be generated with this tool. In the sense of the present invention, the test-relevant data includes control data 14 for the train control unit (also referred to as target system 20), a template 16 for a test report (this template is a PDF file according to ISO 19005-3), encrypted target values 18 of checksums for checking the correct loading of the control data 14 onto the control unit 20 orthe complete commissioning of the control unit 20 and data tables 19 (which include all relevant values recorded in the configuration tool). The encrypted setpoint values 18 of the checksums and optionally also the control data 14 and / or the data tables 19 generated by the configuration tool for the control data 14 are embedded as metadata in accordance with the Extensible Metadata Platform (XMP) standard according to ISO 16684-1 into the template 16 for the test report, which is to be represented by the arrows 15.
[0017] In a second step 2, the control unit 20 is programmed by the programming tool 12 using the control data 14 provided by the configuration tool 10. For this purpose, the commissioning personnel may connect the programming tool 12 to the control unit 20 on-site, either wired or wirelessly, and transmit the data via the appropriate interface. If, as described above, the control data 14 for the target system is embedded in the metadata of the template 16 for the test report 32 according to arrow 15, this data must first be isolated (extracted) by the programming tool for programming the target system 20.If, as described above, the data tables 19 for the control data 14 are embedded in the metadata of the template 16 for the test report 32, this information can be used to display useful information (for example, the name and properties of the control unit 20) on the programming tool 12 to the tester 29.
[0018] In a third step, the control unit 20 or the programming tool 12, for example, calculates the actual checksums 22 for the programmed control data 14 on the control unit 20. If the calculation is performed by the programming tool 12, the information required for the calculation is transferred from the target system 20 to the programming tool 12. The actual checksums calculated in this way (it can also be just a single checksum) are integrated as metadata into the template for the test report 32.
[0019] In a fourth step 4, the programming tool 12 compiles a target-actual comparison 28 for the checksums by automatically comparing the calculated actual checksums 22 with the target values 18 for the checksums. Important for achieving the SIL4 safety objective is that the programming tool 12 never has the target values 18 available in plain text (in the sense of machine-readable and analyzable), but rather, through a specifiable (e.g., mathematical) link between the actual checksums 22 and the target values 18 for the checksums supplied by the configuration tool and encrypted with a key 26 unknown to the programming tool 12, in the event of correct programming of the control unit 20, it arrives at a predefined constant value. The test is then successfully completed when this predefined constant value has been reached.
[0020] In a fifth step 5, the calculated checksums 22 and the encrypted target values 18 for the checksums are displayed on the programming tool 12 for commissioning personnel and / or a tester 29. This can also be done in a simplified form, for example, with the programming device displaying "Checksum(s) OKAY." For example, the target values 18 for the checksums can be transferred from the configuration tool 10 to the programming tool 12 in such a way that the target values 18 are not directly machine-readable and can be evaluated, but can still be displayed for commissioning personnel, e.g., in the form of an embedded image.
[0021] If a method is used in which the target values for the checksums 18 are encrypted and embedded (represented by a key 26) by the configuration tool 10 in the form of a hash checksum (for example, using the SHA 512 algorithm according to RFC 6234) for each target value, from which the target value of the checksum can no longer be determined, further advantages arise. This ensures that the programming tool 12 cannot mistakenly use the target values of the checksums for display or comparison instead of the actual values. To perform the comparison, the programming tool 12 must therefore calculate hash checksum values (represented by an additional key 24) from the calculated actual values of the checksums 22, using the same method as the configuration tool 10 used.
[0022] The commissioning personnel or the tester 29 must then acknowledge this test comparison. In the present embodiment, the test report is only displayed if the calculated checksums 22 and the encrypted target values 18 for the checksums match. As part of this acknowledgement, the name 30 of the acknowledging tester is also stored in the test report 32 or its template 16 with reference to the test report.
[0023] Using this information, the programming tool 12 creates, in a sixth step 6, a final test report 32 in the form of a PDF file according to ISO 19005-3, using the template 16 already transmitted to the programming tool, embedding the identity / name 30 of the auditor 29 and the calculated checksums 22 in the printable area of the test report 32 and additionally embedding this information in the metadata of the test report 32 by the programming tool 12.
[0024] In a further step 7, the generated audit log 32 can optionally be signed with an electronic signature. If this is done using an appropriate, trusted PKI infrastructure, this achieves the same level of authenticity as a handwritten signature on paper. Furthermore, in this step, the audit log 32 is transferred from the programming tool 12 to a database or corresponding data storage 36 and archived there. All data embedded in the audit log 32 is thus also available for later electronic evaluation.
Claims
1. Method for paper-free programming and commissioning of a control unit for a train protection component of a railway protection installation, such as a MiniLEU S11, an LEU S21 and an MSTT Signal for a train protection component, for example, such as an ETCS Eurobalise, an ETCS Euroloop, a signal, a set of points, for example, comprising the following steps: a) providing checking-relevant data by means of a project planning tool (10) for a programming tool (12), wherein the checking-relevant data comprises the control data (14) for the train protection component, a template (16) in PDF format for a checking protocol (32) and encrypted setpoint values (18), which are embedded as metadata in the template (16) for the checking protocol (32), of checksums for control of the correct loading of the control data (14) on the control unit (20) and / or for checking the completeness of the commissioning; b) programming the control unit (20) by way of the programming tool (12) with the control data (14) provided by the project planning tool (10); c) calculating and transferring actual checksums (22) for the programmed control data (14) from the control unit (20) to the programming tool (12); d) encrypting (24) and comparing the calculated actual checksums (22) with the encrypted setpoint values (18) for the checksums, by using these setpoint values from the metadata of the checking protocol template (16), to provide acknowledgement options of the checksum comparison (28) on the programming tool (12); e) presenting the result of the comparison on the programming tool (12) and acknowledging a match between the calculated checksums (22) and the encrypted setpoint values (18) for the checksums by way of a checker (29), f) creating the checking protocol (32) in PDF format on the basis of the template (16) for the checking protocol (32) delivered by the project planning tool (10) in PDF format, with embedding of the identity (30) of the checker (29) as well as of the calculated checksums (22) in the printable region of the checking protocol (32) and additionally embedding of said information in the metadata of the checking protocol (32) by way of the programming tool (12); and g) transferring the checking protocol (32), including all data embedded therein, from the programming tool (12) to a database (36) and archiving the checking protocol (32) in the database (36) .
2. Method according to claim 1, characterised in that the setpoint values (18) for the checksums are encrypted and transferred by the project planning tool (10) such that it is not possible for the programming tool (12) to ascertain any more setpoint values therefrom, preferably using an algorithm, such as the SHA 512 algorithm according to RFC 6234, for example, which forms a further checksum (26) depending on the checksum setpoint value (18).
3. Method according to claim 1 or 2, characterised in that the encrypted setpoint values (18), the control data (14) for the target system and the data tables (19) relating to the control data (14) are embedded and transferred into the template (16) for the checking protocol (32) and into the checking protocol (32).
4. Method according to one of claims 1 to 3, characterised in that the template (16) for the checking protocol (32) and the checking protocol (32) are created in PDF format according to ISO standard 19005-3 or higher and using the Extensible Metadata Platform standard according to ISO 16684-1 for the embedded data.
