EP3259171A1 - Procédé pour faire fonctionner un dispositif de sécurité de train, dispositif de sécurité de train et véhicule ferroviaire équipé d'un dispositif de sécurité de train - Google Patents

Procédé pour faire fonctionner un dispositif de sécurité de train, dispositif de sécurité de train et véhicule ferroviaire équipé d'un dispositif de sécurité de train

Info

Publication number
EP3259171A1
EP3259171A1 EP16713406.3A EP16713406A EP3259171A1 EP 3259171 A1 EP3259171 A1 EP 3259171A1 EP 16713406 A EP16713406 A EP 16713406A EP 3259171 A1 EP3259171 A1 EP 3259171A1
Authority
EP
European Patent Office
Prior art keywords
version
software
started
transmission device
information
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.)
Granted
Application number
EP16713406.3A
Other languages
German (de)
English (en)
Other versions
EP3259171B1 (fr
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 AG
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 AG filed Critical Siemens AG
Publication of EP3259171A1 publication Critical patent/EP3259171A1/fr
Application granted granted Critical
Publication of EP3259171B1 publication Critical patent/EP3259171B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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 two ⁇ th software are checked for compatibility.
  • the specific transmission device is thereby for example advantageously in the position 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 an on ⁇ their variant (feature) of the vehicle device, at the version of the first software according to the "Baseline 3" is realized to be able to establish a connection by providing different connections to the interface with the different versions of the second software.
  • the version of the second software kompati ⁇ bel to the first software according to the "Baseline 2" and the other version of the second software is compatible to the first
  • the rail vehicle 1 is located on a track section 8, which is equipped with a trackside equipment 9 of a second train control system 10.
  • the second train control system 10 is an ATP system according to a national standard, here for example the Danish Switzerlandsi ⁇ insurance system "ZUB 123".
  • the vehicle-side devices 11.1, 11.2, 11n have receivers 12.1, 12.2, 12n, which are designed to receive signals from trackside equipment associated with transmitters.
  • the transmission of information of the second train protection system 10 takes place.
  • the vehicle-side devices 11.1, 11.3, 11 have n specific transmission devices 14.1, 14.2,
  • 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 is ⁇ device 14.1 to the trackside part 9 of the second train protection system 10 is adapted such that it can also receive the process Informatio ⁇ NEN of the second train protection system 10 and partially.
  • the vehicle device 7 is provided with a version vi of a first software.
  • the specific transmission device 14.1 is provided with at least two versions V Ir V n 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 in ⁇ formation on the one version ⁇ ⁇ and second is information about the other version Vn of the second software.
  • the onboard unit 7 would be transmitted via the interface 19, a Ver ⁇ sion indication signal s v _ Arig that INF0 includes the version information of v over the launched version vi of the first software to the specific communication device 14.1, when the started versions V Ir v as recognizes compatible.
  • the vehicle device 7 transmits still be version- indication signal s v _ Arig that INF0 includes the version information of v over the launched version vi of the first software, to the specific communication device 14.1 (see. Step 46 in Figure 2), but then locks in turn the cutting ⁇ point 19 for further communication with the specific communication device 14.1, as it has the path versions V Ir i identified as incompatible. And was also locks the specific communication device 14.1 ⁇ nestein the interface 19 for further communication with the vehicle unit 7 after it has launched versions V Ir Vi recognized as incompatible.
  • the specific transmission device 14.1 transmits a version change signal S v - echs to the data memory 15.1 because it has recognized the started versions as being incompatible (see method step 47 in FIG. In response to the version change signal S v - echs is on
  • the information about the one version ⁇ ⁇ of the second software which here corresponds to the baseline 2
  • the information about the other version V n of the second software which here corresponds to the baseline 3
  • version information VInfo in the data memory 15.1.
  • the main number "4" is stored as version information V Inf0 (see method step 48 in FIG. Due to the incompatibility of the started one version i of the first software and the started one version ⁇ ⁇ of the second software, the specific transmission device 14.1 also restarts automatically.
  • the vehicle device 7 also starts again with the one version vi of the first software-and automatically as well.
  • the vehicle device 7 thus starts again with its one version vi of the first software.
  • 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 Inf0 about the started other version Vn of the second software, to the vehicle device 7 (see method step 52 in FIG. ,
  • the vehicle device 7 transmits via the interface 19 again its version indication signal s v _ ang , which is the version formation v inf0 over the started version vi of the first software, to the specific transmission device 14.1, since it recognizes the started versions V II ( vi as compatible (see method step 54 in FIG.
  • the specific transmission device 14.1 had a further version Vm of the second software, which corresponds, for example, to the "baseline 4", then information on this further version Vm would be in third place in the list, in which case the specific transmission device would upon incompatibility of the started one version vi of the first software and the started another version Vn of the second software to the data memory to transmit the version change signal, wherein in response to the version change signal instead of the information about the other Ver ⁇ sion Vn the second software Information about the further version Vm of the second software would be stored as version information in the data memory.
  • the specific transmission equipment 14.1 would start so at Inkom ⁇ patibility of started a version of vi of the first software and launched another version Vn the second software automatically again, in response to the release response signal now with another version Vm of the second software. And then the started one version vi of the first software and the started further version vm of the second software would be checked for compatibility.
  • the specific transmission device would 14.1 to the data memory 15.1 the version conservation signal ⁇ means, in response to the version-preserving signal information on the another version Vm the second
  • the launched are a version of the first software vi and the other launched Ver ⁇ sion V n of the second software but compatible.
  • the driving ⁇ generating device 7 in turn keeps free the interface 19 to the wide ⁇ ren communication with the specific communication device 14.1 as it recognizes the launched versions to be compatible and also the specific communication device itself holds the interface 19 for further communication with the vehicle unit 7 free since recognizes it as kompa ⁇ ible the started versions.
  • Baseline version format and specific Mattertra ⁇ supply device detects that the baseline version format of the vehicle device corresponds to its baseline version format - the launched versions of the first software and the second software are compatible. b. ) The connection succeeds, and the vehicle device 7 responds with its version indication signal s v _ HS, which comprises the version information v INF0 in the form of a main number "X".
  • the specific transmission device detects that the started version of the first soft ⁇ ware and the launched Version of the second software are incompatible, in other words, the vehicle device responds to the baseline version format of the specific transmission device with its own baseline version format and specific Mattertra ⁇ supply device recognizes that this
  • Baseline version format does not match its baseline version format - the versions are incompatible. c. ) However, the connection is unsuccessful, the Anlagenge ⁇ advises 7 replies yet with his
  • Baseline version format before closing the connection They know the specific communication device 14.1 ⁇ that the launched version of the first soft ⁇ ware and launched version of the second software are not compatible - that is, it recognizes that its baseline version format is not the
  • Baseline version format of the vehicle device 7 ent ⁇ speaks. d.
  • the connection establishment does not succeed, the vehicle device 7 closes the connection immediately, without responding with its baseline version format. Also based on the lack of response recognizes the specific ⁇ About tragungs réelle 14.1 that the launched version of the first software and the launched version of the two ⁇ th software are not compatible.
  • Baseline selected a baseline compatible with the vehicle device baseline.
  • the specific transmission device provides Make sure that this compatible baseline is stored in the datastore before it shuts down, and will use it from the outset on a subsequent connection
  • Baselines is.
  • the baseline of the specific admiratsge ⁇ rätes 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 present in the example shown in Figure 2 embodiment in which the specific Mattertra ⁇ supply terminal initially with baseline 2 starts and changes to the baseline.
  • Both devices 7 and 14.1 are brought into a new connection setup. This is done by rebooting both Gerä ⁇ te.
  • 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 ⁇ nen case distinction. Is the new baseline of the specific transmission device 14.1 now compatible with
  • the specific transmission device with both currently common characteristics of the vehicle device - ie with a version of first software according to Baseline 2, or with a version of the first software according to baseline 3 - to be connected, which could only be realized through a complete device to exchange ⁇ forth.
  • 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 Inf0 .
  • 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. Is the information on these pre-selected version of the second software is not the first place in the list, the Se ⁇ lesson continues with the related first information when both the first pre-selected version and all versions, the information after the information of the preselected version in the list have proved incompatible.
  • the specific communication device is so out ⁇ is that it starts none of the existing versions of the second software automatically twice. So any existing version of the second software prove to be incompatible with the version of the first software so no automatic ⁇ shear reboot of the specific transfer device or such a reboot is going to be canceled.

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)
  • Electric Propulsion And Braking For Vehicles (AREA)
  • Stored Programmes (AREA)
  • Communication Control (AREA)

Abstract

L'invention concerne un procédé pour faire fonctionner un dispositif de sécurité de train (34) comportant une unité de véhicule (7) d'un premier système de sécurité de train (6) et un dispositif de transmission spécifique (14.1) qui est relié par l'intermédiaire d'une interface (19) à l'unité de véhicule (7) et qui est adapté à un élément côté voie (9) d'un second système de sécurité de train (10). L'unité de véhicule (7) est démarrée avec une version (vi) d'un premier logiciel. Le dispositif de transmission spécifique (14.1) est démarré avec une version (νI) d'un second logiciel. La version de démarrage (vi) du premier logiciel et la version de démarrage (νI) du second logiciel sont vérifiés pour leur compatibilité. Selon l'invention, pour produire plus rapidement et de façon plus rentable le dispositif de sécurité pour l'utilisation sur une section de voie qui est équipée de la partie côté voie du second système de sécurité de trains, et pour pouvoir le mettre en service, le dispositif de transmission spécifique (14.1) redémarre automatiquement avec une autre version (νII) du second logiciel en cas d'incompatibilité de la version de démarrage (vi) du premier logiciel et de la version de démarrage (νI) du second logiciel et la version de démarrage (vi) du premier logiciel et l'autre version de démarrage (νII) du second logiciel sont vérifiés pour leur compatibilité. L'invention concerne également un dispositif de sécurité de train et un véhicule ferroviaire équipé d'un dispositif de sécurité de train.
EP16713406.3A 2015-04-14 2016-03-30 Procédé pour faire fonctionner un dispositif de sécurité de train, dispositif de sécurité de train et véhicule ferroviaire équipé d'un dispositif de sécurité de train Active EP3259171B1 (fr)

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 (fr) 2015-04-14 2016-03-30 Procédé pour faire fonctionner un dispositif de sécurité de train, dispositif de sécurité de train et véhicule ferroviaire équipé d'un dispositif de sécurité de train

Publications (2)

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

Family

ID=55646574

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16713406.3A Active EP3259171B1 (fr) 2015-04-14 2016-03-30 Procédé pour faire fonctionner un dispositif de sécurité de train, dispositif de sécurité de train et véhicule ferroviaire équipé d'un dispositif de sécurité de train

Country Status (8)

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

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 (fr) * 2005-06-21 2007-01-03 Hewlett-Packard Development Company, L.P. Procédé et système d'informatique pour l'installation de logiciel
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 (fr) * 2009-06-04 2018-05-02 Abbott Diabetes Care, Inc. Procédé et système de mise à jour d'un dispositif médical
EP2279926B1 (fr) 2009-07-10 2013-03-13 Siemens Aktiengesellschaft Véhicule sur rails doté d'un système de gestion de la configuration pour la sécurité de train
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 上海博泰悦臻网络技术服务有限公司 车载设备及其程序文件更新方法
EP2811696A4 (fr) * 2012-01-30 2015-03-04 Mitsubishi Electric Corp Dispositif de gestion d'informations de train et procédé pour sélectionner son logiciel de commande
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 (fr) * 2013-03-26 2020-02-19 GN Audio A/S Mise à jour de micrologiciel de casque d'écoute pour unité de base de casque
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

Also Published As

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

Similar Documents

Publication Publication Date Title
EP3259171A1 (fr) Procédé pour faire fonctionner un dispositif de sécurité de train, dispositif de sécurité de train et véhicule ferroviaire équipé d'un dispositif de sécurité de train
WO2015150313A1 (fr) Véhicule ferroviaire comportant une unité de bord etcs, rame de véhicules ferroviaires comportant au moins deux véhicules ferroviaires munis chacun d'une unité de bord etcs, et procédé de gestion de ladite rame de véhicules
EP1552997B1 (fr) Système de gestion de la circulation véhicules ferroviaires avec changement de la commande de la marche des trains
DE102019208515A1 (de) Verfahren zum Aufbau einer drahtlosen Datenverbindung zwischen einem Fahrzeug und einer externen Einheit, Verbindungsaufbaueinheit und Fahrzeug
DE102008045050A1 (de) Verfahren und Vorrichtung zur Zugbeeinflussung
WO2018145786A1 (fr) Procédé de mise à jour d'une carte numérique d'un dispositif serveur externe du véhicule à moteur
EP2443015B1 (fr) Procédé permettant la transmission de données à une balise d'un système de contrôle des trains par un appareil de programmation, appareil de programmation et balise
DE102017215710A1 (de) Verfahren zum Übertragen von Software
DE112013003240B4 (de) Verfahren zur Steuerung eines Kraftfahrzeuggetriebes
DE102005049205A1 (de) Vorrichtung und Verfahren zur Sprachnavigation
DE102017011774A1 (de) Verfahren zur Unterstützung eines Fahrzeugnutzers
DE102017010482A1 (de) Verfahren zur Aktualisierung von Kartendaten
DE102004030521A1 (de) Verfahren zur Zugbeeinflussung
DE102016222907A1 (de) Schienenfahrzeug und Verfahren zu dessen Betrieb
EP3771612B1 (fr) Dispositif de voie et procédé de fonctionnement d'un dispositif de voie
EP1914146B1 (fr) Procédé de transmissions sans fil d'informations entre des voitures de chemins de fer
DE102015218988A1 (de) Sicherungsverfahren und Sicherungssystem für ein Gleisstreckennetz
WO2014131629A2 (fr) Véhicule ferroviaire pourvu d'au moins un appareil de sécurité ferroviaire conforme à une norme nationale et d'un dispositif embarqué etcs, et procédé de fonctionement du véhicule ferroviaire
DE102019208512A1 (de) Verfahren zum Aufbau einer drahtlosen Datenverbindung zwischen einem Fahrzeug und einer externen Einheit, System und Schienenfahrzeug
DE102018008322A1 (de) Verfahren zum Betreiben einer Ladestation beim induktiven Laden eines elektrisch betriebenen Fahrzeugs, sowie ein Lademanagementsystem
AT503380A2 (de) Verfahren zur auswahl eines von zwei vorhandenen zugbussen für den fahrbetrieb eines zuges
DE102006013297A1 (de) Verfahren zum Betrieb eines Navigationssystems
DE102019000943A1 (de) Verfahren zum Aufbau einer Kommunikationsverbindung zwischen einem Kraftfahrzeug und einer Parkinfrastruktur zum automatischen Durchführen eines Parkvorgangs des Kraftfahrzeugs
DE102016217246A1 (de) Konzept zum Erfassen eines Umfelds eines Kraftfahrzeugs
DE102016219258A1 (de) Aktualisierung einer digitalen Karte

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