EP3259171B1 - Method for operating a train safety assembly, train safety assembly, and rail vehicle comprising a train safety assembly - Google Patents

Description

The invention relates to a method for operating a train protection arrangement with a vehicle device of a first train protection system and with a specific transmission device, which is connected via an interface with the vehicle device and which is adapted to a trackside part of a second train protection system, wherein the vehicle device with a version of a first Software is started, wherein the specific transmission device is started with a version of a second software and wherein the started one version of the first software and the started one version of the second software are checked for compatibility.

The generic methods known as "check of version" are, for example, in version 2.1.1 (http://www.era.europa.eu/Document-Register/Documents/Set-1-Index008-SUBSET-035 % 20v211.pdf) and version 3.1.0 (http://www.era.europa.eu/Document-Register/Documents/SUBSET-035%20v310.pdf) of the UNISIG specification SUBSET-035: "Specific Transmission Module FFFIS "described.

"UNISIG" (long "Union Industry of Signaling") is a working group of the Association of the European Railway Industry, which was founded in 1998 with the aim to set the specifications for a single European Rail Traffic Management System (ERTMS) create. The single European rail traffic control system "ERTMS" consists of two components - on the one hand from a European train control system "ETCS" (long "European Train Control System") and on the other hand from a railway mobile radio system "GSM-R" (long "Global System for Mobile communication railways ").

The documentation of the UNISIG specifications for the single European rail traffic control system "ERTMS" consists of numerous documents (parts), the so-called "SUBSETs", some of which are obligatory and some merely informative. The documents (parts) develop over numerous versions. For concrete developments, sets of documents have been compiled. These sets of documents are i.a. after the first digit of a system requirement specification version "SRS-V" (long "System Requirement Specification Versions") - ie after the first digit of the version of its document relating to the system requirements specification SUBSET-026: "System Requirement Specification" ("SRS" for short) ) named.

• einen mit "ETCS baseline 2 and GSM-R baseline 0" bezeichneten Satz von Dokumenten, bei dem die Nummer "2" der "ETCS baseline" der ersten Ziffer "2" der Version 2.3.0 der UNISIG Spezifikation SUBSET-026 entspricht (http://www.era.europa.eu/Core-Activities/ERTMS/Pages/Set-of-specifications-1.aspx), und
• einen mit "ETCS baseline 3 and GSM-R baseline 0" bezeichneten Satz von Dokumenten, bei dem die Nummer "3" der "ETCS baseline" der ersten Ziffer "3" der Version 3.4.0 der UNISIG Spezifikation SUBSET-026 entspricht (http://www.era.europa.eu/Core-Activities/ERTMS/Pages/Set-of-specifications-2.aspx).

For example, the European Railway Agency (ERA) has long put together the following two sets of documents on the Internet:

• a set of documents referred to as "ETCS baseline 2 and GSM-R baseline 0" in which the number "2" of the "ETCS baseline" corresponds to the first digit "2" of version 2.3.0 of the UNISIG specification SUBSET-026 (http : //www.era.europa.eu/Core-Activities/ERTMS/Pages/Set-of-specifications-1.aspx), and
• a set of documents referred to as "ETCS baseline 3 and GSM-R baseline 0" in which the number "3" of the "ETCS baseline" corresponds to the first digit "3" of version 3.4.0 of the UNISIG specification SUBSET-026 (http : //www.era.europa.eu/Core-Activities/ERTMS/Pages/Set-of-specifications-2.aspx ).

In the generic method known as "check of version", the European Train Control System "ETCS" is the first train protection system. A conventional national train protection system forms the second train control system.

In itself there is equipment according to the European Train Control System "ETCS" - hereinafter referred to as "ETCS equipment" - a track-side part and a vehicle-side part, so that a rail vehicle with the vehicle-mounted part of the ETCS equipment can drive on sections equipped with the track-side part of the ETCS equipment.

However, rolling stock with the on-board part of the ETCS equipment may also be used on sections not equipped with the trackside part of the ETCS equipment but with a trackside part of the equipment of a conventional national train protection system. For this purpose, an additional device in the form of a specific transmission device is used.

Such a specific transmission device is referred to as "STM" (long "Specific Transmission Module" or alternatively also as "NTC" (long "National Train Control").) The "STM" is on the one hand via an interface specified in UNISIG documents "FFFIS "Form Fit Functional Interface Specification") is connected to a vehicle device in the form of an "EVC" (long "European Vital Computer") of the vehicle-mounted part of the ETCS equipment, and the "STM" is part of the trackside equipment adapted to the conventional national train protection system fitted to the section of the route to be traveled, the specific transmission device receiving and partly processing information from the trackside part of the traditional national train protection system.

There are different software versions for the on-board part of the ETCS equipment and for the trackside part of the ETCS equipment. The different software versions correspond to different system requirement specification versions "SRS-V" for the European Train Control System "ETCS". There are software versions that correspond to the "SRS-V" 2.3.0 - the "ETCS baseline 2" - in the following the "ETCS baseline 2" also referred to as "standard baseline 2" or just "baseline 2" is. In addition, there are software versions that correspond to the "SRS-V" 3.4.0 - the "ETCS baseline 3" - hereinafter referred to as the "ETCS baseline 3" as "Standard Baseline 3" or just "Baseline 3" is. In the near future there will be software versions that correspond to a "Baseline 4".

Currently, there are in practice both vehicle equipment ("EVCs") for rail vehicles, where one of the "Baseline 2" corresponding version of a first software is implemented, as well as vehicle devices ("EVCs"), where one of the "Baseline 3" corresponding Version of the first software is realized.

Accordingly, there are currently in practice both specific transmission devices ("STMs") in which one of the "Baseline 2" equivalent version of a second software is implemented, as well as specific transmission devices ("STMs") in which one of the "Baseline 3 "corresponding version of the second software is realized, wherein the different versions of the second software differ essentially in terms of their connection to the interface.

It may constellations occur in which the realized versions of the first software of the vehicle device and the second software of the specific transmission device are not compatible. In the case of such incompatibility, the connection between the vehicle device and the specific transmission device is interrupted in the generic method known as "check of version". In practice, then a device replacement of the specific transmission device is required, in which the incompatible specific transmission device is replaced by a compatible specific transmission device. Such device replacement is expensive and time consuming.

Based on the aforementioned generic method, the invention is based on the object, the train control arrangement for use on a section, equipped with the trackside portion of the second train control system, faster and cheaper to deploy and put into operation.

This object is achieved with the method according to claim 1, characterized in that the specific transmission device automatically restarted in incompatibility of the started one version of the first software and the started one version of the second software with another version of the second software and that the started a version of the first software and the launched other version of the second software to be checked for compatibility.

The specific transmission device is characterized for example in an advantageous manner both with a variant of the vehicle device, in which the version of the first software according to the "Baseline 2" is realized, as well as with another variant (specification) of the vehicle device, in which the Version of the first software according to the "Baseline 3" is realized to be able to establish a connection by using it with the different versions of the second software provides different connections to the interface. For this purpose, only one version of the second software is compatible with the first software according to the "baseline 2" and the other version of the second software compatible with the first software according to the "baseline 3". The specific transmission device is thus designed to be available with its functionality for both variants of the vehicle device. It is therefore also suitable for controlling a conversion (an update) of the first software of the vehicle device from the version according to "Baseline 2" to the version according to "Baseline 3" or vice versa, without it having to be replaced.

In a preferred embodiment of the inventive method is provided that the specific transmission device in incompatibility of the started one version of the first software and the launched other version of the second Software automatically restarts with another version of the second software and that the started one version of the first software and the started additional version of the second software are checked for compatibility. The specific transmission device is thereby advantageously able to establish a connection with, for example, a further variant of the vehicle device in which the version of the first software, for example in accordance with the "baseline 4" binding in the near future, is realized its functionality also for this variant of the vehicle device to be available. Specifically, the specific transmission device could thus also master a changeover (an update) to the version according to the future binding "Baseline 4" without having to be replaced.

In addition, it is considered advantageous if the vehicle device with the one version of the first software automatically restarts each time the specific transmission device is restarted.

Furthermore, it is considered advantageous if a data memory, in particular a remanent data memory, with a stored version information about the version of the second software to be launched is assigned to the specific transmission device, wherein the specific transmission device at each start and at each restart to determine which to start Version of the second software transmitted via a data transmission connection, a version request signal to the data memory, wherein the data memory in response to the version request signal via the data transmission connection transmits a version response signal to the specific transmission device, the stored version information about the version to be launched of the second Software and wherein the specific transmission device in response to the version response signal starts the version of the second software to be started.

For this purpose, prior to starting the specific transmission device, information about the one version of the second software is preferably stored in the data memory as version information, so that the specific transmission device starts the one version of the second software in response to the version response signal.

With compatibility of the started one version of the first software and the started one version of the second software, the specific transmission device may advantageously transmit to the data memory a version maintenance signal, in response to the version maintenance signal, the information about the one version of the second software remains stored in the data memory or is stored again.

On the other hand, with incompatibility of the started one version of the first software and the started one version of the second software, the specific transmission device may advantageously transmit to the data memory a version change signal, in response to the version change signal instead of the information about the one version the second software stores information about the other version of the second software as version information in the data memory so that the specific transmission device restarts in response to the version response signal with the other version of the second software.

Accordingly, if the one version of the first software is started and the other version of the second software started, the specific transfer device may transmit the version save signal to the data store, wherein in response to the version save signal, the information on the other version of the second software resides in the data store is saved or saved again.

In case of incompatibility the started one version of the first software and the launched another version of the second Software, however, can transmit the specific transmission device to the data store, the version change signal, wherein in response to the version change signal instead of the information about the other version of the second software information about the further version of the second software is stored as version information in the data memory, such that the specific transmission device restarts in response to the version response signal with the further version of the second software.

• dass das spezifische Übertragungsgerät über die Schnittstelle ein Version-Angabesignal, das die Versionsinformation über die gestartete Version der zweiten Software umfasst, an das Fahrzeuggerät übermittelt,
• dass das Fahrzeuggerät anhand der übermittelten Versionsinformation über die gestartete Version der zweite Software und einer Versionsinformation über die gestartete Version der ersten Software überprüft, ob die gestarteten Versionen kompatibel oder nicht kompatibel sind,
• dass das Fahrzeuggerät die Schnittstelle zur weiteren Kommunikation mit dem spezifische Übertragungsgerät sperrt, wenn es die gestarteten Versionen als inkompatibel erkennt,
• dass das Fahrzeuggerät über die Schnittstelle ein Version-Angabesignal, das die Versionsinformation über die gestartete Version der ersten Software umfasst, an das spezifische Übertragungsgerät übermittelt, wenn es die gestarteten Versionen als kompatibel erkennt,
• dass das spezifische Übertragungsgerät anhand der übermittelten Versionsinformation über die gestartete Version der ersten Software und der Versionsinformation über die gestartete Version der zweiten Software überprüft, ob die gestarteten Versionen kompatibel oder nicht kompatibel sind,
• dass das spezifische Übertragungsgerät die Schnittstelle zur weiteren Kommunikation mit dem Fahrzeuggerät sperrt, wenn es die gestarteten Versionen als inkompatibel erkennt,
• dass das spezifische Übertragungsgerät das Version-Wechselsignal an den Datenspeicher übermittelt, wenn es die gestarteten Versionen als inkompatibel erkennt, und
• dass das spezifische Übertragungsgerät das Version-Erhaltungssignal an den Datenspeicher übermittelt, wenn es die gestarteten Versionen als kompatibel erkennt.

A preferred embodiment of the method according to the invention provides the following method steps:

• that the specific transmission device transmits, via the interface, a version-indication signal, which comprises the version information about the started version of the second software, to the vehicle device,
• that the vehicle device checks, based on the transmitted version information about the started version of the second software and a version information about the started version of the first software, whether the started versions are compatible or not compatible,
• that the vehicle device blocks the interface for further communication with the specific transmission device if it recognizes the started versions as being incompatible,
• that the vehicle device transmits, via the interface, a version indication signal, which comprises the version information about the started version of the first software, to the specific transmission device, if it recognizes the started versions as being compatible,
• that the specific transmission device checks, based on the transmitted version information about the started version of the first software and the version information about the started version of the second software, whether the started versions are compatible or not compatible,
• the specific transmission device blocks the interface for further communication with the vehicle device if it recognizes the started versions as being incompatible,
• that the specific transmission device transmits the version change signal to the data memory if it recognizes the started versions as incompatible, and
• that the specific transmission device transmits the version maintenance signal to the data store if it sees the started versions as compatible.

• dass das Fahrzeuggerät die Schnittstelle zur weiteren Kommunikation mit dem spezifische Übertragungsgerät freihält, wenn es die gestarteten Versionen als kompatibel erkennt und
• dass das spezifische Übertragungsgerät die Schnittstelle zur weiteren Kommunikation mit dem Fahrzeuggerät freihält, wenn es die gestarteten Versionen als kompatibel erkennt.

Furthermore, the following method steps are advantageous:

• that the vehicle device keeps the interface free for further communication with the specific transmission device if it recognizes the started versions as compatible and
• the specific transmission device keeps the interface free for further communication with the vehicle device if it recognizes the started versions as being compatible.

Preferably, the one version of the first software of the vehicle device and the versions of the software of the specific transmission device are each provided according to a system requirement specification version of the European Train Control System, the system requirement specification versions of the European Train Control System, which correspond to the different software versions of the specific transmission device, are different.

The version information about the respective version of the software is preferably provided as a number - for example in the form of a main number "X" of a so-called "FFFIS STM version number" ("FFFIS STM version number"), as in version 3.1.0 of the UNISIG specification SUBSET-035 is defined when the first train protection system is a European Train Control System ("ETCS").

The invention also relates to a train protection arrangement for a rail vehicle with a vehicle device of a first train protection system and with a specific transmission device, which is connected via an interface with the vehicle device and which is adapted to a trackside part of a second train control system.

In order to be able to provide such a train control arrangement for use on a route section, which is equipped with the trackside part of the second train control system, faster and less expensive and to be able to operate, it is provided that this train safety arrangement is designed to carry out the method according to the invention.

Moreover, the invention relates to a rail vehicle with such a train control arrangement.

Figur 1

ein Schienenfahrzeug mit einer erfindungsgemäßen Zugsicherungsanordnung und die

Figur 2

eine schematische Darstellung des erfindungsgemäßen Verfahrens.

The invention will be explained in more detail below with reference to FIGS. The show

FIG. 1

a rail vehicle with a train control arrangement according to the invention and the

FIG. 2

a schematic representation of the method according to the invention.

The rail vehicle 1 shown has a vehicle-side equipment, designated as a whole as 5, of a first train control system 6. The first train protection system 6 is a European Train Control System ("ETCS"). The on-board equipment 5 comprises a vehicle device 7 in the form of an ETCS vehicle computer ("EVC").

The rail vehicle 1 is located on a section 8, which is equipped with a trackside equipment 9 of a second train control system 10. The second train protection system 10 is a train safety system according to a national standard, here for example the Danish train protection system "ZUB 123".

The rail vehicle 1 has at least one vehicle-side device 11.1, which is connected to the second train control system 10 is adapted to ride the section shown section 5 can.

In addition, the rail vehicle 1 further vehicle-side devices 11.2, ..., 11.n, which are adapted to other train protection system to be able to drive on sections that are equipped with trackside equipment of these other train protection systems. The other train protection systems are train safety systems according to other national standards, such as the German train protection system "INDUSI" or the French train protection system "TVM".

The vehicle-side devices 11.1, 11.2,..., 11n have receivers 12.1, 12.2,..., 12.n, which are designed to receive signals from trackside equipment associated with transmitters. Thus, the vehicle-side device 10.1 to the receiver 12.1, which is designed to receive here as a whole with S.1 designated signals of a transmitter 13 of the trackside equipment shown 9 of the second train control system 10. By means of the signals S.1, the transmission of information of the second train control system 10 takes place.

Furthermore, the vehicle-side devices 11.1, 11.3, ..., 11.n have specific transmission devices 14.1, 14.2,..., 14.n and retentive data memories 15.1, 15.2,..., 15.n, the specific transmission devices 14.1 , 14.2, ..., 14.n via first data transmission connections 16.1, 16.2, ..., 16.n to the receivers 12.1, 12.2, ..., 12.n and via second data transmission connections 17.1, 17.2,. 17.n are communicatively connected to the remanent data memories 15.1, 15.2, ..., 15.n. Thus, the vehicle-side device 11.1 on the specific transmission device 14.1 and the remanent data memory 15.1, wherein the specific transmission device 14.1 via the first data transmission connection 16.1 with the trained as a vehicle coupling coil receiver 11.1 and above the second data transmission connection 17.1 is communicatively connected to the remanent data memory 15.1.

The specific transmission devices 14.1, 14.2, ..., 14.n are adapted to the trackside part of the respective second train control system. Thus, the specific transmission device 14.1 is adapted to the track-side part 9 of the second train control system 10 such that it can receive the information of the second train protection system 10 and partially process it.

The specific transmission devices 14.1, 14.2,..., 14.n are also communicatively connected to the vehicle device 7 of the first train protection system 6 via a data bus 18 forming an interface 19. The interface 19 represents an interface specified in UNISIG documents ("FFFIS").

The vehicle device 7 of the first train protection system 6 comprises various functional units connected to the data bus 18. These include, but are not limited to, an STM control function unit 20, a driver / machine interface unit (DMI) 21, a brake interface unit ("Brake Interface Unit"). Briefly, "BIU") 22 and an odometry unit ("Odometry") 23. In this case, the driver / machine interface unit 21 via a communication link 24 with an operable by the driver 25 cab display 26 and the brake interface unit 22 via a data transmission connection 27 with a brake system 28 connected.

In the second train protection system 10 (here "ZUB 123" for example), the trackside equipment 9 shown comprises in a known manner, inter alia, a route center 29, route devices 30 in the form of adapters, track couplers functioning as transmitters 13, signals 31 and connection lines 32, 33.

The vehicle device 7, the specific transmission device 14.1, the remanent data memory 15.1, the second data transmission connection 17.1 and the data bus 18 are part of a designated as a whole by 34 train protection arrangement, which is suitably designed, the below with reference to FIG. 2 perform described method.

First, the vehicle device 7 is provided with a version v _{i of} a first software. In addition, the specific transmission device 14.1 is provided with at least two versions V _I , V _{II of} a second software. The specific transmission device or data memory also contains a list of information about the different versions of the second software. In the present exemplary embodiment, the list 35.1 is stored in the specific transmission device 14.1. In the list 35.1 is in the first place information about a version V _I and second information about the other version V _{II of} the second software is.

The version v _{i of} the first software of the vehicle device 7 and the versions V _I and V _{II of} the software of the specific transmission device 14.1 are respectively provided in accordance with a system request specification version SRS-V of the European Train Control System, the system request specification versions of the European Train Control System the software versions V _I and V _{II of} the specific transmission device 14.1 correspond, are different.

Furthermore, information about one of the versions V _I , V _{II of} the second software-that is, one of the information from the list 35.1-is stored in the remanent data memory 15.1 as version _information V _Info . The remanent data memory is thus provided with the stored version _information V _Info about the one version of the second software to be started (see method step 40 in FIG FIG. 2 ).

The version _information V _Info is a number. For example, this number may be provided in the form of a "FFFIS STM version number" as defined in version 3.1.0 of UNISIG specification SUBSET-035. In the present embodiment, the version _information V _{Info is provided} as a main number "X" of the "FFFIS STM version number". With X = 3 - thus with the main number "3" - it concerns a "Baseline 2" appropriate version of the second software. If X = 4 - ie the main number "4" is a "Baseline 3" corresponding version of the second software. In the present exemplary embodiment, the list 35.1 thus contains two skin numbers - namely the main number "3" in the first place and the main number "4" in the second place.

The vehicle device 7 and the specific transmission device 14.1 are first started - so started up. The start of both devices is in the FIG. 2 denoted by 41. The vehicle device 7 starts with its one version v _{i of} the first software.

The specific transmission device 14.1 transmits a version request _signal S _V-Anfr to the data memory 15.1 for determining the version of the second software to be started via the data transmission connection 17.1 (see method step 42 in _FIG FIG. 2 ). The data memory 15.1 transmits a version-response signal S _V-Antw to the specific transmission _device 14.1 in response to the version request _signal S _V-Anfr via the data transmission connection 17.1 (see method step 43 in _FIG FIG. 2 ). The version response signal S _V-Antw comprises the stored version _information V _Info about the version of the second software to be started, that is, first the main number "3". In response to the version response signal S _V-Antw , the specific transmission _{device 14.1} starts with its version V _{I of} the second software, which in the embodiment shown corresponds to the "baseline 2".

If no version _information V _{Info was} initially stored in the data memory 15.1, then the specific transmission device 14.1 would use the information in the first place in the list 35.1 - that is, the main number "3" here as version information and start with the version V _I accordingly.

The specific transmission device 14.1 transmits via the interface 19 a version-indication signal S _V-Ang , which includes the version _information V _Info about the started one version V _{I of} the second software, to the vehicle device 7 (see method step 44 in FIG FIG. 2 ).

Based on the transmitted version _information V _Info about the started version V _{I of} the second software and a version information v _info on the started version v _{i of} the started first software, the vehicle device 7 checks whether the started versions V _I , v _{i are} compatible or not compatible (See method step 45 in the FIG. 2 ).

The vehicle device 7 would transmit via the interface 19 a version-indication signal s _v-ang , which includes the version information v _info on the started version v _{i of} the first software, to the specific transmission device 14.1, if it is the started versions V _I , v _i recognizes as compatible.

Subsequently, the specific transmission device 14 would check on the basis of the transmitted version information v _info on the started version v _{i of} the first software and the version _information V _Info about the started version V _{I of} the second software, if the started versions are compatible or not compatible.

The specific transmission device 14.1 would then transmit a version maintenance signal S _V-Erh to the data memory 15.1 if it recognizes the started versions V _I , v _i as compatible.

In response to the version maintenance signal S _V-Erh , the information about the one version V _{I of} the second software - in this case the main number "3" would remain stored in the data memory 15.1 or it would be stored there again.

In the in the FIG. 2 illustrated embodiment recognizes the STM control function unit 20 of the vehicle unit 7, however, that the two versions V _I , v _{i are} incompatible.

Although the vehicle device 7 still transmits its version information signal s _v-ang , which includes the version information v _info about the started version v _{i of} the first software, to the specific transmission device 14.1 (see method step 46 in FIG FIG. 2 ), but in turn blocks the interface 19 for further communication with the specific transmission device 14.1, since it has recognized the started versions V _I , v _i as incompatible.

And also the specific transmission device 14.1 in turn blocks the interface 19 for further communication with the vehicle device 7, after it has recognized the started versions V _I , v _i as incompatible.

In addition, the specific transmission device 14.1 transmits a version change signal S _V-change to the data memory 15.1 because it has recognized the started versions as incompatible (see method step 47 in FIG FIG. 2 ).

In response to the version change signal S _V-change , instead of the information about one version V _{I of} the second software, which here corresponds to baseline 2, the information about the other version V _{II of} the second software, here the baseline corresponds, as version _information V _Info stored in the data memory 15.1. Thus, instead of the main number "3", the main number "4" is stored as version _information V _Info (see method step 48 in FIG FIG. 2 ).

Due to the incompatibility of the started one version v _{i of} the first software and the started one version V _{l of} the second software, the specific transmission device 14.1 also restarts - automatically.

Each time the specific transmission device 14.1 is restarted, the vehicle device 7 also starts again with the one version _{v.sub.i of} the first software-and also automatically. The vehicle device 7 thus starts again with its one version v _{i of} the first software.

The automatic restart of both devices 7 and 14.1 is in the FIG. 2 denoted by 49.

The specific transmission device 14.1 now again transmits its version request _signal S _V-Anfr to the data memory 15.1 (see method step 50 in _FIG FIG. 2 ) and in response receives the version response signal S _{V-Antw again} (see method step 51 in _FIG FIG. 2 ). Since the version response signal S _V-Antw now includes the main number "4" as version _information V _Info , the specific transmission device 14.1 now starts with the other version V _{II of} the second software, which corresponds to the "baseline 3".

The specific transmission device 14.1 then transmits via the interface 19 its version-indication signal S _V-Ang , which now comprises the version _information V _Info about the started other version V _{II of} the second software, to the vehicle device 7 (see method step 52 in FIG FIG. 2 ).

First, the vehicle device 7 first checks the started version v _{i of} the first software and the started other version V _{II of} the second software for their compatibility (see method step 53 in FIG FIG. 2 ).

The vehicle device 7 transmits again via the interface 19 its version indication signal s _v-ang , which contains the version information v _info about the started version v _{i of} the first software, to the specific transmission device 14.1, since it recognizes the started versions V _II , v _i as compatible (see method step 54 in FIG FIG. 2 ).

The specific transmission device 14.1 transmits its version maintenance signal S _V-Erh to the data memory 15.1 since it has recognized the compatibility of the started one version v _{i of} the first software and the started other version V _{II of} the second software (see method step 55 in FIG FIG. 2 ). In response to the version maintenance signal S _V-Erh , the information about the other version V _{II of} the second software - ie the main number "4" - is stored in the data memory 15.1 or it is stored again.

If the specific transmission device 14.1 had a further version V _{III of} the second software, which corresponds for example to the "baseline 4", then in the list would be in the third place information about this further version V _III . Then, with incompatibility of the started one version v _{i of} the first software and the started another version V _{ii of} the second software, the specific transmission device would transmit the version change signal to the data store in response to the version change signal instead of the information about the other one Version V _{II of} the second software information about the additional version V _{III of} the second software would be stored as version information in the data memory.

The specific transmission device 14.1 would therefore automatically restart when incompatibility of the started one version v _{i of} the first software and the started other version V _{II of} the second software, in response to the version response signal now with the further version V _{III of} the second software ,

And then the started one version v _{i of} the first software and the started further version V _{III of} the second software would be checked for compatibility.

If compatibility of the started one version v _{i of} the first software and the started further version V _{III of} the second software, the specific transmission device 14.1 would transmit to the data memory 15.1 the version-preservation signal, wherein in response to the version-preservation signal the information about the further version V _{III of} the second software in the data memory 15.1 remain stored or stored again.

In the illustrated embodiment, however, the started one version v _{i of} the first software and the launched another version v _{ii of} the second software are compatible. The vehicle device 7, in turn, keeps the interface 19 free for further communication with the specific transmission device 14.1, since it recognizes the started versions as compatible and the specific transmission device, in turn, keeps the interface 19 free for further communication with the vehicle device 7, since it is the started versions recognizes as compatible.

In other words, with the method described in the connection setup between the specific transmission device 14.1 and the vehicle device 7 in conjunction with the remanent data memory 15.1, the required version of the second software can be selected. In other words, a selection of the baseline can be realized by the specific transmission device. In this case, the specific transmission device 14.1 and the vehicle device 7 communicate with each other via the data bus 18, via which the connection is established. When starting (ie during startup) is in the specific transmission device 14.1 - due to the _information stored in the memory as version _information V _Info main number "X" - initially assumed that the required version of the second software of the standard baselines equivalent. It is therefore initially assumed that the version of the second software is required, which is assigned to the UNISIG specification SUBSET-035 stored in the data memory 15.1 main number "X". The specific transmission device 14.1 starts with this version of the second software and tries with it via the data bus 18, the connection to the STM control function unit 20 of the vehicle device. 7

1. a.) Der Verbindungsaufbau gelingt und das Fahrzeuggerät 7 antwortet mit seinem Version-Angabesignal s_v-ang, das die Versionsinformation v_info über die gestartete Version der ersten Software - hier beispielhaft auch in Form einer nach UNISIG-Spezifikation SUBSET-035 definierten Hauptnummer "X" - umfasst. Das spezifische Übertragungsgerät 14.1 erkennt anhand der Hauptnummern, dass die gestartete Version der ersten Software und die gestartete Version der zweiten Software kompatibel sind. Mit anderen Worten antwortet das Fahrzeuggerät auf ein Baselineversionsformat des spezifischen Übertragungsgerätes mit einem Baselineversionsformat und das spezifische Übertragungsgerät erkennt, dass das Baselineversionsformat des Fahrzeuggerätes seinem Baselineversionsformat entspricht - die gestarteten Versionen der ersten Software und der zweiten Software sind kompatibel.
2. b.) Der Verbindungsaufbau gelingt und das Fahrzeuggerät 7 antwortet mit seinem Version-Angabesignal s_v-ang, das die Versionsinformation v_info in Form einer Hauptnummer "X" umfasst. Das spezifische Übertragungsgerät erkennt, dass die gestartete Version der ersten Software und die gestartete Version der zweiten Software nicht kompatibel sind. Mit anderen Worten antwortet das Fahrzeuggerät auf das Baselineversionsformat des spezifischen Übertragungsgerätes mit seinem Baselineversionsformat und das spezifische Übertragungsgerät erkennt, dass dieses Baselineversionsformat seinem Baselineversionsformat nicht entspricht - die Versionen sind inkompatibel.
3. c.) Der Verbindungsaufbau gelingt nicht, das Fahrzeuggerät 7 antwortet jedoch noch mit seinem Baselineversionsformat bevor es die Verbindung schließt. Das spezifische Übertragungsgerät 14.1 erkennt, dass die gestartete Version der ersten Software und die gestartete Version der zweiten Software nicht kompatibel sind - es erkennt also, dass sein Baselineversionsformat nicht dem Baselineversionsformat des Fahrzeuggerätes 7 entspricht.
4. d.) Der Verbindungsaufbau gelingt nicht, das Fahrzeuggerät 7 schließt die Verbindung sofort, ohne mit seinem Baselineversionsformat zu antworten. Auch anhand der ausbleibenden Antwort erkennt das spezifische Übertragungsgerät 14.1, dass die gestartete Version der ersten Software und die gestartete Version der zweiten Software nicht kompatibel sind.

This experiment may end with one of the following four results:

1. a.) The connection establishment succeeds and the vehicle device 7 responds with its version indication signal s _v-ang , the version information v _info on the started version of the first software - here by way of example also in the form of a UNISIG specification SUBSET-035 defined main number " X "- includes. The specific transmission device 14.1 recognizes from the main numbers that the started version of the first software and the started version of the second software are compatible. In other words, the vehicular device responds to a baseline version format of the specific transmission device having a baseline version format, and the specific transmission device recognizes that the baseline version format of the vehicular device corresponds to its baseline version format - the started versions of the first software and the second software are compatible.
2. b.) The connection establishment succeeds and the vehicle device 7 responds with its version indication signal s _v-ang , which includes the version information v _info in the form of a main number "X". The specific communication device recognizes that the started version of the first software and the started version of the second software are not compatible. In other words, the vehicle device responds to the baseline version format of specific transmission device with its baseline version format and the specific transmission device recognizes that this baseline version format does not match its baseline version format - the versions are incompatible.
3. c.) The connection establishment does not succeed, but the vehicle device 7 still responds with its baseline version format before it closes the connection. The specific transmission device 14.1 recognizes that the started version of the first software and the started version of the second software are not compatible - it thus recognizes that its baseline version format does not correspond to the baseline version format of the vehicle device 7.
4. d.) The connection is not successful, the vehicle unit 7 closes the connection immediately, without responding with its baseline version format. Based on the lack of response, the specific transmission device 14.1 recognizes that the started version of the first software and the started version of the second software are not compatible.

The result a.) Thus occurs when the started version of the first software and the started one version of the second software are compatible. However, if these are incompatible, one of the results b.), C.) Or d.) Occurs.

In the case of compatibility (case A) the connection is correct. The specific transmission device 14.1 has thus chosen with its started version of the second software compatible with the started version of the first software of the vehicle device software. In other words, the specific transmission device 14.1, with its baseline started, has selected a baseline compatible with the baseline of the vehicle device. The specific transmission device provides Make sure that this compatible baseline is stored in the datastore before it shuts down and will pre-empt this baseline on a subsequent connection. All data traffic, including other functions of the vehicle device, for example the DMI or the BIU, is carried out with a corresponding protocol format of this selected baseline. The vehicle unit is now in the state of a configured baseline.

In the case of incompatibility (Case B), the specific transmission device has not received its baseline from the STM control functional unit 20 of the vehicle device 7. The specific transmission device then assumes that the cause is an incompatibility of the baselines. The baseline of the specific transmission device 14.1 is therefore changed. The information about the newly selected baseline is stored in the data memory 15.1 as version information.
This case B is initially at the in FIG. 2 shown embodiment, in which the specific transmission terminal first starts with the baseline 2 and then changes to baseline 3.

Both devices 7 and 14.1 are brought into a new connection setup. This is done by restarting both devices. The specific transmission device 14.1 again makes a connection attempt to the vehicle device 7, but now with the new baseline. It will come back to the just described case distinction. If the new baseline of the specific transmission device 14.1 is now compatible with the baseline of the vehicle device 7, then case A comes into force. Otherwise again case B. In the in FIG. 2 In the embodiment shown, the case A is now present, so that the specific transmission device retains the baseline 3.

In the train control arrangement 34 according to the invention, so the specific transmission device with both currently common characteristics of the vehicle device - ie with a version of baseline 2 or a version of the first software according to Baseline 3 - which was previously only possible with a complete device replacement.

The complete rebuilding of the selection (selection) of the baseline of the specific transmission device 14.1 can be done by deleting the stored version _information V _Info .

The pre-selection of the desired baseline can be done by a targeted storage of information about one of the existing versions of the second software - in other words, by a targeted storage of a baseline. If the information about this preselected version of the second software is not first in the list, then the selection continues with the first information, if both the initially preselected version and all versions whose information is after the information of the preselected Versions in the list are considered incompatible.

However, the specific transmission device is designed so that it does not automatically start any of the existing versions of the second software twice. Thus, if all existing versions of the second software prove incompatible with the version of the first software, then no automatic restart of the specific transmission device or such a restart would be aborted.

Claims (15)

1. Method for operating a train safety assembly (34) comprising an onboard apparatus (7) of a first train safety system (6) and comprising a specific transmission device (14.1), which is connected to the onboard apparatus (7) via an interface (19) and is adapted to a trackside part (9) of a second train safety system (10),

   - wherein the onboard apparatus (7) is started using a version (v_i) of a first software,

   - wherein the specific transmission device (14.1) is started using a version (V_I) of a second software and

   - wherein the started one version (v_i) of the first software and the started one version (V_I) of the second software are checked for their compatibility,
   characterised in

   - that, in the case of incompatibility of the started one version (v_i) of the first software and the started one version (V_I) of the second software, the specific transmission device (14.1) is automatically restarted with another version (V_II) of the second software and

   - that the started one version (v_i) of the first software and the started other version (V_II) of the second software are checked for their compatibility.
2. Method according to claim 1,
   characterised in

   - that, in the case of incompatibility of the started one version (v_i) of the first software and the started other version (V_II) of the second software, the specific transmission device (14.1) is automatically restarted with a further version (V_III) of the second software and

   - that the started one version (v_i) of the first software and the started further version (V_III) of the second software are checked for their compatibility.
3. Method according to claim 1 or 2, characterised in that, on each restart of the specific transmission device (14.1), the onboard apparatus (7) is automatically restarted with the one version (v_i) of the first software.
4. Method according to one of claims 1 to 3, characterised in that

   - a data memory (15.1), in particular a non-volatile data memory, with stored version-information (V_Info) on the version of the second software to be started is assigned to the specific transmission device (14.1),

   - wherein, on each start and each restart, to determine the version of the second software to be started, the specific transmission device (14.1) communicates a version-request signal (S_V-Anfr) to the data memory (15.1) via a data-transmission connection (17.1),

   - wherein in response to the version-request signal (S_V-Anfr), the data memory (15.1) communicates a version-response signal (S_V-Antw) comprising the stored version-information (V_Info) on the version of the second software to be started to the specific transmission device (14.1) via the data-transmission connection (17.1), and

   - wherein, in response to the version-response signal (S_V-Antw), the specific transmission device (14.1) starts the version of the second software to be started.
5. Method according to claim 4,
   characterised in that, before the specific transmission device (14.1) starts, information on the one version (V_I) of the second software is stored as version-information (V_Info) in the data memory (15.1) so that, in response to the version-response signal (SV-Antw), the specific transmission device (14.1) starts with the one version (V_I) of the second software.
6. Method according to claim 5,
   characterised in that

   - in the case of compatibility of the started one version (v_i) of the first software and the started one version (V_I) of the second software, the specific transmission device (14.1) communicates a version-retain signal (S_v-Erh) to the data memory (15.1),

   - wherein in response to the version-retain signal (S_v-Erh), the information on the one version (V_I) of the second software remains stored or is stored anew in the data memory.
7. Method according to claim 5,
   characterised in that

   - in the case of incompatibility of the started one version (v_i) of the first software and the started one version (V_I) of the second software, the specific transmission device (14.1) communicates a version-change signal (S_V-Wechs) to the data memory (15.1),

   - wherein, in response to the version-change signal (S_v-Wechs), instead of the information on the one version (V_I) of the second software, information on the other version (V_II) of the second software is stored as version-information (V_Info) in the data memory so that, in response to the version-response-signal (S_V-Antw), the specific transmission device (14.1) restarts with the other version (V_II) of the second software.
8. Method according to claim 7, characterised in that

   - in the case of compatibility of the started one version (v_i) of the first software and the started other version (V_II) of the second software, the specific transmission device (14.1) communicates the version-retain signal (S_v-Erh) to the data memory (15.1),

   - wherein, in response to the version-retain signal (S_v-Erh), the information on the other version (V_II) of the second software remains stored or is stored anew in the data memory (15.1).
9. Method according to claim 7, characterised in that

   - in the case of incompatibility of the started one version (v_i) of the first software and the started other version (V_II) of the second software, the specific transmission device (14.1) communicates the version-change signal (S_V-Wechs) to the data memory (15.1),

   - wherein, in response to the version-change signal (S_V-Wechs), instead of the information on the other version (V_II) of the second software, information on the further version (V_III) of the second software is stored as version-information (V_Info) in the data memory so that, in response to the version-response signal (S_V-Antw), the specific transmission device (14.1) restarts with the further version (V_III) of the second software.
10. Method according to one of claims 6 to 9, characterised in

    - that the specific transmission device (14.1) communicates a version-indication signal (S_V-Ang) comprising the version-information (V_Info) on the started version of the second software to the onboard apparatus (7) via the interface (19),

    - that the onboard apparatus (7) uses the communicated version-information (V_Info) on the started version of the second software and version-information (v_info) on the started version of the first software to check whether the started versions are compatible or incompatible,

    - that the onboard apparatus (7) blocks the interface (19) for further communication with the specific transmission device (14.1) if it identifies the started versions as incompatible,

    - that the onboard apparatus (7) communicates a version-indication signal (S_{V_ang}) comprising the version-information (v_info) on the started version of the first software to the specific transmission device (14.1) via the interface (19) if it identifies the started versions as compatible,

    - that the specific transmission device (14.1) uses the communicated version-information (v_info) on the started version of the first software and the version-information (V_info) on the started version of the second software to check whether the started versions are compatible or incompatible,

    - that the specific transmission device (14.1) blocks the interface (19) for further communication with the onboard apparatus (7) if it identifies the started versions as incompatible,

    - that the specific transmission device (14.1) communicates the version-change signal (S_V-Wechs) to the data memory (15.1) if it identifies the started versions as incompatible, and

    - that the specific transmission device (14.1) communicates the version-retain signal (S_V-Erh) to the data memory (15.1) if it identifies the started versions as compatible.
11. Method according to claim 10, characterised in

    - that the onboard apparatus (7) keeps the interface (19) free for further communication with the specific transmission device (14.1) if it identifies the started versions as compatible and

    - that the specific transmission device (14.1) keeps the interface (19) free for further communication with the onboard apparatus (7) if it identifies the started versions as compatible.
12. Method according to one of claims 1 to 11, characterised in that

    - the one version (v_i) of the first software of the onboard apparatus (7) and the versions (V_I, V_II, V_III) of the software of the specific transmission device (14.1) are each provided in accordance with a System Requirements Specification Version (SRS V) of a European Train Safety System (ETCS),

    - wherein the System Requirements Specification versions (SRS V) of the European Train Safety System (ETCS) are different to those corresponding to different versions of the second software of the specific transmission device (14.1).
13. Method according to one of claims 4 to 12, characterised in that the version-information (v_info or V_Info) on the respective version of the software is provided as a number.
14. Train safety assembly (34) for a rail vehicle (1) comprising an onboard apparatus (7) of a first train safety system (6) and a specific transmission device (14.1), which is connected via an interface (19) to the onboard apparatus (7) and adapted to a trackside part (9) of a second train safety system (10), characterised in that the train safety assembly (34) is embodied as suitable to carry out the method according to one of claims 1 to 13.
15. Rail vehicle (1)
    characterised by
    a train safety assembly (34) according to claim 14.

Images