US 12,030,535 B2
Railway automation network and method for transmitting messages in a railway automation network
Uwe Eckelmann-Wendt, Wolfenbuettel (DE); Stefan Gerken, Braunschweig (DE); Hans-Peter Huth, Munich (DE); Johannes Riedl, Ergolding (DE); and Andreas Schallenberg, Peine (DE)
Assigned to Siemens Mobility GmbH, Munich (DE)
Appl. No. 16/756,549
Filed by SIEMENS MOBILITY GMBH, Munich (DE)
PCT Filed Sep. 17, 2018, PCT No. PCT/EP2018/075078
§ 371(c)(1), (2) Date Apr. 16, 2020,
PCT Pub. No. WO2019/076559, PCT Pub. Date Apr. 25, 2019.
Claims priority of application No. 102017218460.4 (DE), filed on Oct. 16, 2017.
Prior Publication US 2020/0290657 A1, Sep. 17, 2020
Int. Cl. B61L 27/00 (2022.01); B61L 15/00 (2006.01); G05D 1/00 (2024.01); H04L 12/46 (2006.01); H04W 4/06 (2009.01)
CPC B61L 15/0027 (2013.01) [B61L 15/0072 (2013.01); H04W 4/06 (2013.01)] 14 Claims
OG exemplary drawing
 
1. A railway automation network, comprising:
a publish/subscribe system including:
at least one transmitter-end application configured for publication of messages,
at least one transmitter-end message broker,
at least one receiver-end message broker, and
at least one receiver-end application configured for receipt of messages;
at least two redundant, at least partly physically independent network paths of the railway automation network;
each said at least one transmitter-end application being linked for communication to said at least one transmitter-end message broker;
each said at least one transmitter-end message broker being configured to respectively map a message published by said at least one transmitter-end application based on a subject specified in said message onto each of said at least two network paths;
said at least two network paths configured to transfer said message and at least one physically independent copy of said message respectively and simultaneously over said at least two network paths to said at least one receiver-end message broker;
each said at least one receiver-end application being linked for communication to said at least one receiver-end message broker;
said at least one receiver-end message broker being configured to transfer said message and said at least one copy of said message to said at least one receiver-end application;
a plurality of said receiver-end message brokers simultaneously receiving said message and said at least one copy of said message, said plurality of receiver-end message brokers each being assigned to at least two multicast groups, and each of said multicast groups using one of said network paths; and
all of said message brokers being connected for communication with one another by using pre-configured multicast groups for exchanging administration data.