EP3259171B1 - Verfahren zum betrieb einer zugsicherungsanordnung, zugsicherungsanordnung und schienenfahrzeug mit einer zugsicherungsanordnung - Google Patents

Verfahren zum betrieb einer zugsicherungsanordnung, zugsicherungsanordnung und schienenfahrzeug mit einer zugsicherungsanordnung Download PDF

Info

Publication number
EP3259171B1
EP3259171B1 EP16713406.3A EP16713406A EP3259171B1 EP 3259171 B1 EP3259171 B1 EP 3259171B1 EP 16713406 A EP16713406 A EP 16713406A EP 3259171 B1 EP3259171 B1 EP 3259171B1
Authority
EP
European Patent Office
Prior art keywords
version
software
started
transmission device
specific transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP16713406.3A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3259171A1 (de
Inventor
Frank Simon
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens Mobility GmbH
Original Assignee
Siemens Mobility GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens Mobility GmbH filed Critical Siemens Mobility GmbH
Publication of EP3259171A1 publication Critical patent/EP3259171A1/de
Application granted granted Critical
Publication of EP3259171B1 publication Critical patent/EP3259171B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/70—Details of trackside communication
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L15/00—Indicators provided on the vehicle or train for signalling purposes
    • B61L15/0063—Multiple on-board control systems, e.g. "2 out of 3"-systems
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L15/00—Indicators provided on the vehicle or train for signalling purposes
    • B61L15/0081—On-board diagnosis or maintenance
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/20—Trackside control of safe travel of vehicle or train, e.g. braking curve calculation
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B61—RAILWAYS
    • B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/20—Trackside control of safe travel of vehicle or train, e.g. braking curve calculation
    • B61L2027/202—Trackside control of safe travel of vehicle or train, e.g. braking curve calculation using European Train Control System [ETCS]

Definitions

  • 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.
  • ERTMS European Rail Traffic Management System
  • 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.
  • 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.
  • ECS European Train Control System
  • a conventional national train protection system forms the second train control system.
  • 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.
  • 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.
  • an additional device in the form of a specific transmission device is used.
  • STM Long "Specific Transmission Module” or alternatively also as “NTC” (long “National Train Control”).
  • NTC Long "National Train Control”
  • 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.
  • EMC long "European Vital Computer”
  • 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.
  • 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.
  • 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.
  • 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.
  • the vehicle device with the one version of the first software automatically restarts each time the specific transmission device is restarted.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the started one version of the first software and the launched another version of the second Software 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.
  • 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").
  • ECS European Train Control System
  • 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.
  • this train safety arrangement is designed to carry out the method according to the invention.
  • the invention relates to a rail vehicle with such a train control arrangement.
  • 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.
  • 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.
  • 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.
  • S.1 the transmission of information of the second train control system 10 takes place.
  • 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.
  • the specific transmission devices 14.1, 14.2, ..., 14.n are adapted to the trackside part of the respective second train control system.
  • 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.
  • STM control function unit 20 a driver / machine interface unit (DMI) 21, a brake interface unit ("Brake Interface Unit”).
  • BIU brake interface unit
  • Odometry odometry
  • 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.
  • the vehicle device 7 is provided with a version v i of a first software.
  • 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.
  • 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.
  • 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. 2 ).
  • the version information V Info is a number.
  • 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.
  • 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. 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".
  • 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".
  • 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. 2 ).
  • the vehicle device 7 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.
  • 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.
  • 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.
  • 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. 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.
  • 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.
  • 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. 2 ).
  • 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.
  • the main number "3” instead of the main number "3", the main number "4" is stored as version information V Info (see method step 48 in FIG. 2 ).
  • the specific transmission device 14.1 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.
  • the vehicle device 7 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 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. 2 ) and in response receives the version response signal S V-Antw again (see method step 51 in 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. 2 ).
  • 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. 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. 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. 2 ).
  • 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.
  • 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 ,
  • 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.
  • 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 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.
  • the required version of the second software can be selected.
  • a selection of the baseline can be realized by the specific transmission device.
  • 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.
  • 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.
  • 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.
  • the specific transmission device 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.
  • 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.
  • the specific transmission device is designed so that it does not automatically start any of the existing versions of the second software twice.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Train Traffic Observation, Control, And Security (AREA)
  • Communication Control (AREA)
  • Stored Programmes (AREA)
  • Electric Propulsion And Braking For Vehicles (AREA)
EP16713406.3A 2015-04-14 2016-03-30 Verfahren zum betrieb einer zugsicherungsanordnung, zugsicherungsanordnung und schienenfahrzeug mit einer zugsicherungsanordnung Active EP3259171B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102015206666.5A DE102015206666A1 (de) 2015-04-14 2015-04-14 Verfahren zum Betrieb einer Zugsicherungsanordnung, Zugsicherungsanordnung und Schienenfahrzeug mit einer Zugsicherungsanordnung
PCT/EP2016/056838 WO2016165935A1 (de) 2015-04-14 2016-03-30 Verfahren zum betrieb einer zugsicherungsanordnung, zugsicherungsanordnung und schienenfahrzeug mit einer zugsicherungsanordnung

Publications (2)

Publication Number Publication Date
EP3259171A1 EP3259171A1 (de) 2017-12-27
EP3259171B1 true EP3259171B1 (de) 2019-05-01

Family

ID=55646574

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16713406.3A Active EP3259171B1 (de) 2015-04-14 2016-03-30 Verfahren zum betrieb einer zugsicherungsanordnung, zugsicherungsanordnung und schienenfahrzeug mit einer zugsicherungsanordnung

Country Status (8)

Country Link
US (1) US10214226B2 (hu)
EP (1) EP3259171B1 (hu)
CN (1) CN107466277B (hu)
DE (1) DE102015206666A1 (hu)
ES (1) ES2739152T3 (hu)
HK (1) HK1248191A1 (hu)
HU (1) HUE044807T2 (hu)
WO (1) WO2016165935A1 (hu)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102015206666A1 (de) * 2015-04-14 2016-10-20 Siemens Aktiengesellschaft Verfahren zum Betrieb einer Zugsicherungsanordnung, Zugsicherungsanordnung und Schienenfahrzeug mit einer Zugsicherungsanordnung
JP7311245B2 (ja) * 2018-03-07 2023-07-19 トヨタ自動車株式会社 マスタ装置、マスタ、制御方法、プログラム及び車両
CN109885451A (zh) * 2019-01-11 2019-06-14 芜湖智久机器人有限公司 一种版本信息传输***及方法
CN110435724B (zh) * 2019-08-30 2022-01-21 湖南中车时代通信信号有限公司 一种将中国列车运行监控***与欧洲列车控制***互联互通的方法
CN113415313B (zh) * 2021-07-06 2023-04-21 北京全路通信信号研究设计院集团有限公司 一种特殊车载设备控车权切换方法及***

Family Cites Families (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5377938A (en) * 1992-12-01 1995-01-03 Pulse Electronics, Inc. Railroad telemetry and control systems
US6467088B1 (en) * 1999-06-30 2002-10-15 Koninklijke Philips Electronics N.V. Reconfiguration manager for controlling upgrades of electronic devices
US7188341B1 (en) * 1999-09-24 2007-03-06 New York Air Brake Corporation Method of transferring files and analysis of train operational data
US6430481B1 (en) * 1999-10-28 2002-08-06 General Electric Company Remote verification of software configuration information
US6886472B2 (en) * 2003-02-20 2005-05-03 General Electric Company Method and system for autonomously resolving a failure
FR2878217B1 (fr) * 2004-11-22 2007-04-20 Alstom Belgium Sa Systeme de securite embarque sur un vehicule ferroviaire
US7386845B1 (en) * 2005-03-24 2008-06-10 Network Appliance, Inc. Automated compatibility and upgrade/downgrade knowledge base
EP1739552A1 (en) * 2005-06-21 2007-01-03 Hewlett-Packard Development Company, L.P. Software installation method and computer system
JP2008027129A (ja) * 2006-07-20 2008-02-07 Yamaha Corp 互換性判定装置およびプログラム
JP4751785B2 (ja) * 2006-07-31 2011-08-17 富士通株式会社 伝送装置およびソフトウェア自動更新方法
US20090013317A1 (en) * 2007-02-08 2009-01-08 Airnet Communications Corporation Software Management for Software Defined Radio in a Distributed Network
US20080243927A1 (en) * 2007-03-28 2008-10-02 Siemens Aktiengesellschaft Method and a system for maintaining an integrity of a product
US8151257B2 (en) * 2007-05-29 2012-04-03 Sap Ag Managing different versions of server components regarding compatibility with collaborating servers
US8255896B2 (en) * 2008-04-01 2012-08-28 Honeywell International Inc. Network software normalization and installation in a fire detection system
US8561052B2 (en) * 2008-12-08 2013-10-15 Harris Corporation Communications device with a plurality of processors and compatibility synchronization module for processor upgrades and related method
US8892699B2 (en) * 2008-12-31 2014-11-18 Schneider Electric USA, Inc. Automatic firmware updates for intelligent electronic devices
US20100306757A1 (en) * 2009-05-28 2010-12-02 Karin Becker Determining compatibility among service versions
EP2438527B1 (en) * 2009-06-04 2018-05-02 Abbott Diabetes Care, Inc. Method and system for updating a medical device
EP2279926B1 (de) * 2009-07-10 2013-03-13 Siemens Aktiengesellschaft Schienenfahrzeug mit Konfigurationsmanager für Zugsicherungssysteme
US20120096451A1 (en) * 2010-10-15 2012-04-19 Roche Diagnostics Operations, Inc. Firmware update in a medical device with multiple processors
US8713559B2 (en) * 2010-11-15 2014-04-29 Schneider Electric It Corporation System and method for updating firmware
US9003363B2 (en) * 2011-03-21 2015-04-07 Microsoft Technology Licensing, Llc Device flags
DE102011102425A1 (de) * 2011-05-24 2012-11-29 Heidelberger Druckmaschinen Ag Simultanes Softwareupdate
US8869131B2 (en) * 2011-06-09 2014-10-21 Dot Hill Systems Corporation Method and apparatus for downgrading firmware in a controller
CN102501891B (zh) * 2011-11-02 2014-07-09 株洲南车时代电气股份有限公司 一种列车运行监控装置管理***
CN103135996A (zh) * 2011-11-23 2013-06-05 上海博泰悦臻网络技术服务有限公司 车载设备及其程序文件更新方法
JP5178962B1 (ja) * 2012-01-30 2013-04-10 三菱電機株式会社 列車情報管理装置及びその制御ソフトウェアの選択方法
US8972970B2 (en) * 2012-07-02 2015-03-03 Taiwan Gomet Technology Co. Ltd. Firmware overwriting method in paired use wireless microphone and receiver
US9038053B2 (en) * 2012-08-27 2015-05-19 Lenovo Enterprise Solutions (Singapore) Pte. Ltd Non-disruptive software updates for servers processing network traffic
GB2508599A (en) * 2012-12-04 2014-06-11 Ibm Software version management when downgrading software
US9342298B2 (en) * 2013-03-14 2016-05-17 Microsoft Technology Licensing, Llc Application compatibility checking in a distributed computing environment
US9710250B2 (en) * 2013-03-15 2017-07-18 Microsoft Technology Licensing, Llc Mechanism for safe and reversible rolling upgrades
EP2784668B1 (en) * 2013-03-26 2020-02-19 GN Audio A/S Headset firmware update from headset base unit
US10474808B2 (en) * 2013-03-29 2019-11-12 Hill-Rom Services, Inc. Hospital bed compatibility with third party application software
US9104434B2 (en) * 2013-12-20 2015-08-11 Microsoft Technology Licensing, Llc Property accesses in dynamically typed programming languages
JP6281413B2 (ja) * 2014-05-28 2018-02-21 富士通株式会社 ファームウェア更新装置、ストレージ制御装置およびプログラム
US10095500B2 (en) * 2014-09-30 2018-10-09 Apple Inc. Revision locking
DE102015206666A1 (de) * 2015-04-14 2016-10-20 Siemens Aktiengesellschaft Verfahren zum Betrieb einer Zugsicherungsanordnung, Zugsicherungsanordnung und Schienenfahrzeug mit einer Zugsicherungsanordnung

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US20180118241A1 (en) 2018-05-03
ES2739152T3 (es) 2020-01-29
HUE044807T2 (hu) 2019-11-28
CN107466277A (zh) 2017-12-12
CN107466277B (zh) 2020-03-20
WO2016165935A1 (de) 2016-10-20
DE102015206666A1 (de) 2016-10-20
HK1248191A1 (zh) 2018-10-12
US10214226B2 (en) 2019-02-26
EP3259171A1 (de) 2017-12-27

Similar Documents

Publication Publication Date Title
EP3259171B1 (de) Verfahren zum betrieb einer zugsicherungsanordnung, zugsicherungsanordnung und schienenfahrzeug mit einer zugsicherungsanordnung
EP1065128B1 (de) System zur Initialisierung von Zügen auf Basis eines Datenkommunikationssystems, bei dem allen Kommunikationsteilnehmern die Informationen in der Initialisierungsphase zugänglich sind
EP3102474B1 (de) Schienenfahrzeug mit einer etcs-bordeinheit, schienenfahrzeug-verband mit mindestens zwei schienenfahrzeugen mit jeweils einer etcs-bordeinheit und verfahren zum steuern eines derartigen schienenfahrzeug-verbands
DE102018201646A1 (de) Verfahren und eine Vorrichtung zur dezentralen Kooperationsabstimmung von Fahrzeugen
DE102016100675A1 (de) Horizontbasierte Fahrerassistenzsysteme und Verfahren
EP1552997B1 (de) Betriebsführungssystem für schienengebundene Verkehrsmittel mit Wechsel der Art der Zugbeeinflussung
EP1013533A1 (de) Verfahren zum Bestimmen der physischen Reihenfolge von Fahrzeugen eines zusammengestellten Zuges und Anordnung zur Durchführung des Verfahrens
DE102016226309A1 (de) Vorrichtung und Verfahren zur Fahrzeugführung eines Kraftfahrzeugs
EP3964419A1 (de) Übertragung von daten zwischen einem spurgebundenen fahrzeug und einer landseitigen einrichtung
WO2019072524A1 (de) Verfahren zur kartierung eines streckenabschnitts
DE102016007588A1 (de) Verfahren zur Durchführung einer Fahrt von mehreren Fahrzeugen
DE102016203695A1 (de) Bahntechnische Anlage und Verfahren zum Betreiben einer bahntechnischen Anlage
WO2018145786A1 (de) Verfahren zum aktualisieren einer digitalen karte einer kraftfahrzeugexternen servervorrichtung
DE102016220215A1 (de) Verfahren zum Betreiben von Schienenfahrzeugen
DE102016200049B4 (de) Verfahren, Führungsfahrzeug und Lastkraftwagen zum Auffahren auf und Abfahren von einer Autobahn durch den Lastkraftwagen
EP3013666B1 (de) Verfahren zum betreiben eines zugbeeinflussungssystems und zugbeeinflussungssystem
DE102016204984A1 (de) Schnittstelle, Ein- oder Ausgabemittel, Umrüstsatz und Verfahren zur Umrüstung eines Schienenfahrzeugs für einen autonomen Fahrbetrieb
DE102018213206A1 (de) Verfahren zum zumindest teilautomatisierten Führen eines Kraftfahrzeugs innerhalb einer Infrastruktur
DE102004031525A1 (de) Verfahren bei der Sicherung des Fahrbetriebes
EP3328706B1 (de) Sicherungsverfahren und sicherungssystem für ein gleisstreckennetz
DE102008039170B4 (de) Automatische Konfiguration von Teilsystemen und Kommunikation zwischen Systemen in Fahrzeugen
EP3771612B1 (de) Streckeneinrichtung und verfahren zum betreiben einer streckeneinrichtung
DE102017011774A1 (de) Verfahren zur Unterstützung eines Fahrzeugnutzers
DE102012016169A1 (de) Verfahren zur Daten-Aktualisierung eines Steuergeräts
DE102016222907A1 (de) Schienenfahrzeug und Verfahren zu dessen Betrieb

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170920

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIEMENS MOBILITY GMBH

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: B61L 15/00 20060101AFI20181023BHEP

Ipc: B61L 27/00 20060101ALN20181023BHEP

INTG Intention to grant announced

Effective date: 20181130

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1126550

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190515

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502016004429

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: SIEMENS SCHWEIZ AG, CH

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190901

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190801

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

REG Reference to a national code

Ref country code: HU

Ref legal event code: AG4A

Ref document number: E044807

Country of ref document: HU

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190801

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190802

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190901

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2739152

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20200129

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502016004429

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

26N No opposition filed

Effective date: 20200204

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200330

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200331

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200330

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190501

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20220620

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20230621

Year of fee payment: 8

Ref country code: CH

Payment date: 20230612

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: HU

Payment date: 20230523

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230403

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20240304

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: AT

Payment date: 20240212

Year of fee payment: 9