System and method for redundant communication between MVB bus and TCMS network

Abstract

The invention discloses a system and a method for redundant communication between an MVB (Multifunction Vehicle Bus) and a TCMS (Train Communication Management System) network. An MVB bus; a vehicle TCMS network; the at least two sets of MVB-TCMS conversion gateways are used for carrying out MVB-TCMS protocol conversion on the received data; wherein the two sets of MVB-TCMS conversion gateways are parallel gateways of each other; the vehicle-mounted equipment is connected with each MVB-TCMS conversion gateway through an MVB bus; each MVB-TCMS conversion gateway is connected with a vehicle TCMS network; and the vehicle-mounted equipment sends the vehicle-mounted data to the MVB-TCMS conversion gateway through the MVB bus, receives the vehicle network data sent by the MVB-TCMS conversion gateway, and selects the main and standby states of the vehicle network data as the main vehicle network data for use. According to the invention, the bidirectional redundant communication between the MVB communication system and the TCMS communication system can be realized under the condition that the cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of network communication technology, and in particular to a system and method for redundant communication between an MVB bus and a TCMS network. Background Art

[0002] MVB (Multifunction Vehicle Bus) is mainly used for serial data communication between interconnected devices that require interoperability and interchangeability. It has a fixed transmission rate of 1.5Mbps and supports single-wire and dual-wire physical transmission media. MVB is mainly used to connect standard devices located in the same vehicle, such as realizing serial data communication between devices. TCMS (Train Control and Management System) is the core system of high-speed trains, responsible for processing and distributing various internal and external data during train operation. TCMS connects the subsystem equipment on the train through the network to achieve communication and information sharing.

[0003] In EMU trains equipped with TCMS, the automatic train protection system (ATP) and the automatic train control system (ATO) are on-board devices. They communicate bidirectionally with various control units inside the vehicle, including braking, traction and over-phase control units, through the TCMS vehicle network to obtain device status and output control commands. The on-board devices developed earlier do not support the TCMS network interface, but support the MVB interface. In order to adapt to EMU trains equipped with TCMS network control systems, it is necessary to design and implement bidirectional communication between the MVB bus and the TCMS network. This process not only needs to ensure high reliability of communication, but also needs to take into account cost control. Summary of the invention

[0004] The object of the present invention is to provide a system and method for redundant communication between an MVB bus and a TCMS network, which realizes bidirectional redundant communication between two communication formats, MVB and TCMS, under the condition of reducing costs.

[0005] In order to achieve the above objectives, the present invention is implemented by the following technical solutions:

[0006] A system for redundant communication between an MVB bus and a TCMS network, comprising: an on-board device; an MVB bus; a vehicle TCMS network; at least two sets of MVB-TCMS conversion gateways, for performing MVB-TCMS protocol conversion on received data; wherein the two sets of the MVB-TCMS conversion gateways are parallel gateways to each other; the on-board device is connected to each of the MVB-TCMS conversion gateways via the MVB bus; each of the MVB-TCMS conversion gateways is connected to the vehicle TCMS network; the on-board device sends on-board data to the MVB-TCMS conversion gateway via the MVB bus, receives vehicle network data sent by the MVB-TCMS conversion gateway, and selects the primary and secondary states of the vehicle network data for use as the primary vehicle network data.

[0007] Optionally, the vehicle TCMS network is connected to each of the MVB-TCMS conversion gateways via Ethernet, for sending the vehicle network data to the MVB-TCMS conversion gateway and receiving the vehicle-mounted data sent by the MVB-TCMS conversion gateway.

[0008] Optionally, it also includes: a judicial recorder, which is connected to the vehicle-mounted device via a Profibus bus, receives and stores vehicle network data currently used by the vehicle-mounted device, and the available status of the current main gateway and backup gateway for fault diagnosis.

[0009] Optionally, the number of the vehicle TCMS networks is the same as the number of the MVB-TCMS conversion gateways, and the two are connected in a one-to-one correspondence.

[0010] Optionally, when the on-board device sends data to the vehicle TCMS network, the on-board device sends the on-board data to the MVB bus, and each of the MVB-TCMS conversion gateways receives the on-board data from the configured MVB bus port, performs protocol conversion to form network data packets, and sends them to the corresponding vehicle TCMS network through the network protocol.

[0011] Optionally, when the vehicle TCMS network sends data to the on-board device, the MVB-TCMS conversion gateway receives the corresponding vehicle network data from the corresponding vehicle TCMS network through a network protocol, and receives the corresponding MVB data of the parallel gateway from the MVB bus. The MVB-TCMS conversion gateway determines and updates its own master-slave status and determines the data availability status of the parallel gateway based on preset rules according to the received vehicle network data and the MVB data of the parallel gateway. The MVB-TCMS conversion gateway converts the corresponding on-board network data into new MVB data, and appends its own master-slave status and the data availability status of the parallel gateway to the new MVB data, and sends it to the MVB bus. The on-board device simultaneously receives the new MVB data sent by each of the MVB-TCMS conversion gateways through the MVB bus, selects the MVB data with the master-slave status as the master in the new MVB data, and sends the new MVB data to the judicial recorder for storage through the Profibus bus.

[0012] Optionally, the switching condition of the master / slave state is determined and updated based on the preset rule as follows:

[0013] Rule 1: After power-on, initialize the two sets of MVB-TCMS conversion gateways to the standby state, and configure one gateway to start after a 60-second delay after power-on.

[0014] Rule 2: This MVB-TCMS conversion gateway needs to monitor the TCMS heartbeat in the received vehicle network data. If it does not change for more than 1 second, the vehicle network data received by this MVB-TCMS conversion gateway is considered invalid, and the master-slave state of this MVB-TCMS conversion gateway is set to standby.

[0015] Rule 3: If the master-slave status in the output of this MVB-TCMS conversion gateway is standby, and the vehicle network data received by this MVB-TCMS conversion gateway is valid, and the master-slave status received from the parallel gateway output is standby, then the master-slave status of this MVB-TCMS conversion gateway is set to master.

[0016] Rule 4: If the master-slave state of this MVB-TCMS conversion gateway is standby, and the vehicle network data received by this MVB-TCMS conversion gateway is valid, and no MVB data from the parallel gateway is received for more than 1 second, the master-slave state of this MVB-TCMS conversion gateway is set to master.

[0017] Before power-on initialization, the priorities of the two sets of MVB-TCMS conversion gateways are preset, where the priority of one MVB-TCMS conversion gateway is greater than the priority of the other MVB-TCMS conversion gateway. When there may be a conflict between the two sets of MVB-TCMS conversion gateways, Rule 5 is executed; Rule 5, if the MVB-TCMS conversion gateway with a lower priority detects that the master-slave state of the MVB-TCMS conversion gateway with a higher priority is master, the master-slave state of the MVB-TCMS conversion gateway with a lower priority is unconditionally set to slave, and the MVB-TCMS conversion gateway with a higher priority does not need to detect its own master-slave state again.

[0018] Optionally, the judgment rule for the data availability status of the parallel gateway is: if the TCMS heartbeat in the parallel gateway MVB data received by this MVB-TCMS conversion gateway does not change for more than 1 second, the MVB data availability status of the parallel gateway is set to unavailable, otherwise it is set to available.

[0019] Optionally, the vehicle-mounted device receives two channels of new MVB data from the MVB bus, and selects one channel of new MVB data for use according to the master / slave status in the new MVB data; the selection principle is as follows:

[0020] When the master-slave state of the new MVB data sent by this MVB-TCMS conversion gateway is master, and the master-slave state of the new MVB data sent by the parallel gateway of this MVB-TCMS conversion gateway is standby, the on-board equipment uses the new MVB data sent by this MVB-TCMS conversion gateway.

[0021] When the master-slave state of the new MVB data sent by the parallel gateway of this MVB-TCMS conversion gateway is master, and the master-slave state of the new MVB data sent by this MVB-TCMS conversion gateway is standby, the on-board equipment uses the new MVB data sent by the parallel gateway of this MVB-TCMS conversion gateway.

[0022] When the active and standby states of the two sets of the MVB-TCMS conversion gateways are both active, or the active and standby states of the two sets of the MVB-TCMS conversion gateways are both standby, the vehicle-mounted device does not use any MVB data and determines that the communication fails.

[0023] On the other hand, the present invention also provides a method for redundant communication between an MVB bus and a TCMS network, based on the system implementation of redundant communication between an MVB bus and a TCMS network as described above, the method comprises:

[0024] The received vehicle data is converted into a protocol through the MVB-TCMS conversion gateway and then sent to the corresponding vehicle TCMS network.

[0025] And / or, the received vehicle network data is converted into a protocol through the MVB-TCMS conversion gateway and then sent to the MVB bus.

[0026] On the other hand, the vehicle-mounted device selects the main standby state in the vehicle network data as the main vehicle network data for use. On the other hand, the present invention also provides an electronic device, including a processor and a memory, wherein a computer program is stored on the memory, and when the computer program is executed by the processor, the method described above is implemented.

[0027] In other aspects, the present invention further provides a readable storage medium, wherein the readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described above is implemented.

[0028] The present invention has at least one of the following technical effects:

[0029] In terms of system architecture, the present invention realizes bidirectional redundant communication between MVB and TCMS communication formats by deploying a conversion gateway. The architecture is streamlined, the cabinet space requirement is small, the adaptability is strong, and the transformation cost is low.

[0030] In terms of solution design, the redundant switching function is mainly implemented by the conversion gateway. The on-board equipment only needs to select data according to the flag bit, which reduces the operating burden of the on-board equipment. The operation cycle of the conversion gateway is very short, which can realize fast equipment redundant switching, does not affect the normal operation of the on-board equipment and vehicle network, and has high reliability.

[0031] In terms of system maintenance, the complete TCMS data and the working status of the primary and standby gateways are recorded through the judicial recorder to facilitate fault diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of the architecture of a system for redundant communication between an MVB bus and a TCMS network provided by an embodiment of the present invention;

[0033] Figure 2 A schematic diagram of a data transmission path from an on-board device to a vehicle TCMS network provided in an embodiment of the present invention;

[0034] Figure 3 A schematic diagram of a data transmission path from a vehicle TCMS network to an on-board device provided by an embodiment of the present invention;

[0035] Figure 4 A diagram of gateway active / standby state transition provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0036] The following is a further detailed description of a system and method for redundant communication between an MVB bus and a TCMS network proposed in the present invention in conjunction with the accompanying drawings and specific embodiments. According to the following description, the advantages and features of the present invention will be clearer. It should be noted that the drawings are in a very simplified form and use non-precise proportions, which are only used to conveniently and clearly assist in explaining the purpose of the embodiments of the present invention. In order to make the purposes, features and advantages of the present invention more obvious and easy to understand, please refer to the accompanying drawings. It should be noted that the structure, proportion, size, etc. illustrated in the drawings of this specification are only used to match the contents disclosed in the specification for people familiar with this technology to understand and read, and are not used to limit the limiting conditions for the implementation of the present invention, so they have no technical substantive significance. Any structural modification, change in proportional relationship or adjustment of size, without affecting the effects that can be produced by the present invention and the purposes that can be achieved, should still fall within the scope of the technical content disclosed by the present invention.

[0037] like Figure 1 As shown, this embodiment provides a system for redundant communication between an MVB bus and a TCMS network, including: an on-board device 400; an MVB bus 100; a vehicle TCMS network (such as Figure 1 At least two sets of MVB-TCMS conversion gateways (such as Figure 1 The vehicle-mounted device 400 is connected to each of the MVB-TCMS conversion gateways via the MVB bus 100; each of the MVB-TCMS conversion gateways is connected to the vehicle TCMS network; the vehicle-mounted device 400 sends vehicle-mounted data to the MVB-TCMS conversion gateway via the MVB bus 100, and receives vehicle network data (vehicle TCMS network data) sent by the MVB-TCMS conversion gateway, and selects the vehicle network data in the primary and standby states for use as the primary vehicle network data.

[0038] This embodiment implements bidirectional redundant communication between the two communication systems, the MVB bus and the vehicle TCMS network, by deploying an MVB-TCMS conversion gateway. It has a streamlined architecture, requires less cabinet space, has strong adaptability, and has low transformation costs.

[0039] Please continue to refer to Figure 1 As shown, in this embodiment, the vehicle TCMS network is connected to each of the MVB-TCMS conversion gateways via Ethernet, for sending the vehicle network data to the MVB-TCMS conversion gateway and receiving the vehicle-mounted data sent by the MVB-TCMS conversion gateway.

[0040] The number of the vehicle TCMS networks is the same as the number of the MVB-TCMS conversion gateways, and the two are connected one-to-one.

[0041] For example, the vehicle TCMS network includes two sets, namely, vehicle TCMS network A201 and vehicle TCMS network B202; and two sets of MVB-TCMS conversion gateways, namely, gateway A301 and gateway B302 for short.

[0042] The vehicle TCMS network A201 is connected to the gateway A301 via Ethernet. The TCMS network B202 is connected to the gateway B302 via Ethernet.

[0043] Please continue to refer to Figure 1 As shown, this embodiment also includes: a judicial recorder 500, which is connected to the vehicle-mounted device 400 via a Profibus bus 600, receives and stores the vehicle network data currently used by the vehicle-mounted device 400, and the available status of the current main gateway and the backup gateway for fault diagnosis.

[0044] In this embodiment, in terms of system maintenance, the complete TCMS data and the working status of the primary and standby gateways are recorded by the judicial recorder 500 to facilitate fault diagnosis.

[0045] like Figure 2 As shown, in this embodiment, when the on-board device 400 sends data to the vehicle TCMS network, the on-board device 400 sends the on-board data (based on the MVB protocol) to the MVB bus 100, and each of the MVB-TCMS conversion gateways receives the on-board data from the configured MVB bus port, performs protocol conversion to form network data packets, and sends them to the corresponding vehicle TCMS networks through the network protocol.

[0046] For example, the vehicle-mounted device 400 sends the vehicle-mounted data to the MVB bus 100, and the gateway A301 and the gateway B302 receive the vehicle-mounted data from the MVB bus 100 respectively. It can be understood that the vehicle-mounted data on the MVB bus 100 is MVB data, and the MVB data is converted into a network data packet through protocol conversion. The gateway A301 sends the converted network data packet to the TCMS network A201, and the gateway B302 sends the converted network data packet to the TCMS network B202.

[0047] like Figure 3 As shown, the MVB-TCMS conversion gateway receives the corresponding vehicle network data from the corresponding vehicle TCMS network through a network protocol, and receives the MVB data of the corresponding parallel gateway from the MVB bus.

[0048] For example, gateway A301 receives vehicle network data A from vehicle TCMS network A201 , and gateway B302 receives vehicle network data B from vehicle TCMS network B202 .

[0049] Gateway A301 also receives MVB data B sent by its parallel gateway, gateway B302, from the MVB bus 100, and gateway B302 receives MVB data A sent by its parallel gateway, gateway A301, from the MVB bus 100.

[0050] The MVB-TCMS conversion gateway determines and updates its own master-slave status and judges the data availability status of the parallel gateway based on preset rules according to the received vehicle network data and the MVB data of the parallel gateway.

[0051] For example, gateway A301 coordinates the active and standby status of one gateway (gateway A301 / gateway B302) to active and the active and standby status of another gateway (gateway B302 / gateway A301) to standby based on a set of preset rules according to the received vehicle network data A and MVB data B, thereby determining and updating the active and standby status of the current gateway (gateway A301).

[0052] Similarly, gateway B302 coordinates the active and standby status of one gateway (gateway B302 / gateway A301) to active and the active and standby status of another gateway (gateway A301 / gateway B302) to standby through a set of rules based on the received vehicle network data B and MVB data A, thereby determining and updating the active and standby status of this gateway (gateway B302).

[0053] At the same time, gateway A301 and gateway B302 determine the data availability status of the parallel gateways.

[0054] The MVB-TCMS conversion gateway converts the corresponding vehicle network data into new MVB data, and appends its own master / slave status and data availability status of the parallel gateway to the new MVB data, and sends it to the MVB bus.

[0055] The vehicle-mounted device 400 simultaneously receives new MVB data sent by each MVB-TCMS conversion gateway through the MVB bus 100, selects the MVB data in the new MVB data that is in the primary standby state for use, and sends the new MVB data to the judicial recorder 500 for storage through the Profibus bus 600.

[0056] In this embodiment, the judgment rule for the availability status of the MVB data of the parallel gateway is: if the TCMS heartbeat in the MVB data of the parallel gateway received by this gateway does not change for more than 1 second, the availability status of the MVB data of the parallel gateway is set to unavailable, otherwise it is set to available.

[0057] For example, gateway A 301 determines the availability status of MVB data B of the parallel gateway (gateway B 302 ) obtained from the MVB bus.

[0058] When the TCMS heartbeat in the MVB data B of the parallel gateway (gateway B302) received by the gateway A301 does not change for more than 1 second, the availability status of the MVB data B of the parallel gateway (gateway B302) is set to unavailable, otherwise it is set to available.

[0059] When MVB data B is available, gateway A301 converts the vehicle network data A it receives into new MVB data A, and appends the master-slave status of this gateway (gateway A301) and the available status of MVB data B of the parallel gateway (gateway B302) to the new MVB data A, and sends the final new MVB data A to the MVB bus 100.

[0060] Gateway B 302 determines the availability status of the MVB data A of the parallel gateway (gateway A 301 ) obtained from the MVB bus.

[0061] When the TCMS heartbeat in the MVB data A of the parallel gateway (gateway A301) received by the gateway B302 does not change for more than 1 second, the availability status of the MVB data A of the parallel gateway (gateway A301) is set to unavailable, otherwise it is set to available.

[0062] When MVB data A is available, gateway B302 converts the vehicle network data B it receives into new MVB data B, and appends the master-slave status of this gateway (gateway B302) and the available status of MVB data A of the parallel gateway (gateway A301) to the new MVB data B, and sends the final new MVB data B to the MVB bus 100.

[0063] In this embodiment, the switching conditions of the active / standby state according to the preset rule are as follows:

[0064] Rule 1: After power-on, initialize the two gateways to the primary and standby states as standby, and configure one of the gateways to start after a 60-second delay after power-on.

[0065] Rule 2: This gateway needs to monitor the TCMS heartbeat in the received vehicle network data. If it does not change for more than 1 second, the vehicle network data received by this gateway is considered invalid, and the master-slave state of this gateway is set to standby.

[0066] Rule 3: If the master-slave state in the output of this gateway is backup, and the vehicle network data received by this gateway is valid, and the master-slave state received from the parallel gateway output is backup, then the master-slave state of this gateway is set to master.

[0067] Rule 4: If the master-slave state of this gateway is standby, and the vehicle network data received by this gateway is valid, and the MVB data of the parallel gateway cannot be received for more than 1 second, the master-slave state of this gateway is set to master.

[0068] Before power-on initialization, the priorities of the two sets of gateways are preset, and the priority of one gateway is greater than that of the other gateway. When there may be a conflict between the two sets of gateways, Rule 5 is executed; Rule 5, if the gateway with a low priority detects that the master-slave state of the gateway with a high priority is the master, the master-slave state of the gateway with a low priority is unconditionally set to the standby state, and the gateway with a high priority does not need to detect its own master-slave state again.

[0069] For example, before power-on initialization, the priorities of two sets of gateways are pre-set, and the priority of one gateway is greater than the priority of the other gateway. For example, the priority of gateway A301 is set to be greater than the priority of gateway B302. When there may be a conflict between the two sets of gateways (for example, when the master-slave state of gateway A301 is master, but gateway A301 fails, such as being disconnected from the bus, gateway B302 cannot detect gateway A301, then it will set its master-slave state to master. When gateway A301 is reconnected to the bus, at this time, the master-slave state settings of the two sets of gateways are both master, and thus there is a conflict between the two), gateway B302 executes rule 5, while for gateway A301, it does not need to execute rule 5 to avoid conflict. That is, if gateway B302 detects that gateway A301 is master, the master-slave state of gateway B302 is unconditionally set to standby.

[0070] In this embodiment, the redundant switching function is mainly implemented by the conversion gateway, and the vehicle-mounted equipment only needs to select data according to the flag bit, which reduces the operating burden of the vehicle-mounted equipment. The operation cycle of the conversion gateway is very short, which can realize fast device redundant switching, does not affect the normal operation of the vehicle-mounted equipment and the vehicle TCMS network, and has high reliability.

[0071] For example Figure 4 As shown in the figure, the typical gateway active / standby switching scenario is as follows Figure 4 As shown:

[0072] Scenario 1:

[0073] After power-on, according to rule 1, both gateways (gateway A and gateway B) are initialized as standby. Gateway B is configured to start after a 60-second delay after power-on. According to rule 3, gateway A sets itself as the primary. After gateway B starts, it detects that gateway A is the primary and gateway B remains as the standby. The vehicle-mounted device uses the data sent by gateway A.

[0074] Scenario 2:

[0075] The main gateway network is disconnected, and according to rule 2, it is set as the backup. The other gateway network is normal, and according to rule 3, it is set as the main one. The vehicle-mounted equipment switches to the active gateway.

[0076] Scenario 3:

[0077] The active gateway device fails and no longer sends MVB data. The parallel gateway works normally and sets itself as the active gateway according to rule 4. The vehicle-mounted device switches to the active gateway.

[0078] Scenario 4:

[0079] The MVB bus connection of the primary gateway (Gateway A) is interrupted, but the TCMS network connection is normal and remains the primary gateway. Gateway B cannot receive data from Gateway A, so it is set as the primary gateway and the vehicle-mounted equipment switches to using the data sent by Gateway B. After a period of time, Gateway A resumes connection with the MVB bus, and Gateway B receives that Gateway A is the primary gateway. According to Rule 5, Gateway B is set as the backup gateway. The vehicle-mounted equipment switches to using the data sent by Gateway A.

[0080] Scene 5:

[0081] The MVB bus connection of the main gateway (gateway B) is interrupted, but the TCMS network connection is normal and remains in the main function. Gateway A cannot receive data from gateway B, so it is set as the main function, and the vehicle-mounted equipment switches to using the data sent by gateway A. After a period of time, gateway B resumes the connection with the MVB bus, and gateway B receives the data from gateway A as the main function. According to rule 5, gateway B is set as the backup function. The vehicle-mounted equipment continues to use the data sent by gateway A.

[0082] In this embodiment, the vehicle-mounted device 400 receives two new MVB data from the MVB bus 100, and selects one new MVB data to use according to the active and standby states of the two new MVB data. The selection principle is as follows:

[0083] When the master-slave state of the MVB data of this gateway is master, and the master-slave state of the MVB data of the parallel gateway of this gateway is standby, the vehicle-mounted device uses the MVB data of this gateway.

[0084] For example, when the master-slave status of the new MVB data A sent by the gateway A is master, and the master-slave status of the new MVB data B sent by the parallel gateway (gateway B) of the gateway A is standby, the vehicle-mounted device 400 uses the new MVB data A sent by the gateway A.

[0085] When the master-slave state of the MVB data of the parallel gateway of this gateway is master, and the master-slave state of the MVB data of this gateway is standby, the vehicle-mounted device uses the MVB data of the parallel gateway of this gateway.

[0086] For example, when the master-slave state of the new MVB data B sent by gateway B is master, and the master-slave state of the new MVB data A sent by gateway A is standby, the vehicle-mounted device 400 uses the new MVB data B sent by gateway B.

[0087] When the active and standby states of the two sets of the MVB-TCMS conversion gateways are both active, or the active and standby states of the two sets of the MVB-TCMS conversion gateways are both standby, the vehicle-mounted device does not use any MVB data and determines that the communication fails.

[0088] For example, when the primary and secondary states of the new MVB data A sent by gateway A and the new MVB data B sent by gateway B are both primary, or the primary and secondary states of the new MVB data A sent by gateway A and the new MVB data B sent by gateway B are both secondary, the vehicle-mounted device 400 does not use any data channel and determines that a communication failure occurs.

[0089] On the other hand, this embodiment further provides a method for redundant communication between an MVB bus and a TCMS network, based on the system implementation of redundant communication between an MVB bus and a TCMS network as described above, the method includes:

[0090] The received vehicle data is converted into a protocol through the MVB-TCMS conversion gateway and then sent to the corresponding vehicle TCMS network.

[0091] The received vehicle network data is converted into a protocol through the MVB-TCMS conversion gateway and then sent to the MVB bus.

[0092] The vehicle-mounted device selects the vehicle network data in the primary-standby state for use as the primary vehicle network data.

[0093] On the other hand, this embodiment further provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method described above is implemented.

[0094] In other aspects, this embodiment further provides a readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method described above is implemented.

[0095] In summary, the present invention provides a system and method for redundant communication between the MVB bus and the TCMS network, which realizes bidirectional redundant communication between the vehicle-mounted device MVB bus and the vehicle TCMS network. The system consists of vehicle-mounted devices, MVB-TCMS conversion gateways (dual sets), vehicle TCMS networks (A network and B network), and judicial recorders. The system architecture is as follows: Figure 1As shown. Among them, the vehicle-mounted equipment is connected to the MVB-TCMS conversion gateway through the MVB bus, sending vehicle-mounted data to the gateway and receiving vehicle TCMS network data sent by the gateway. The vehicle TCMS network is connected to the MVB-TCMS conversion gateway through Ethernet, sending vehicle data to the gateway and receiving vehicle-mounted data sent by the gateway. The MVB-TCMS conversion gateway is redundantly set up and is responsible for MVB-TCMS protocol conversion. Gateway A and Gateway B monitor the TCMS network connection status of the gateway and receive the working status of the parallel gateway (the parallel gateway of Gateway A is Gateway B, and the parallel gateway of Gateway B is Gateway A) through the MVB bus. The main gateway and the backup gateway are determined through a set of rules, and the main and backup gateway switching function is executed. The judicial recorder is connected to the vehicle-mounted host through the Profibus bus, receives and stores the vehicle TCMS network data currently used by the vehicle-mounted host, the available status of the current main gateway and the backup gateway, for fault diagnosis.

[0096] The on-board device sends data to the vehicle TCMS network, and the on-board device sends the on-board data to the MVB bus. Gateway A and Gateway B receive the on-board data from the configured MVB bus port, perform protocol conversion to form network data packets, and send them to TCMS network A and TCMS network B respectively through the network protocol.

[0097] The vehicle TCMS network sends data to the on-board device. TCMS network A and TCMS network B send the vehicle network data to gateway A and gateway B respectively through the network protocol. Gateway A and gateway B determine whether the data is available based on the TCMS heartbeat in the network data, and obtain the master and standby status of the parallel gateway and the network data availability status through the MVB bus, and determine whether the gateway is the main gateway or the standby gateway through a set of rules. Gateway A and gateway B convert the network data into MVB data, and attach the master and standby status of the gateway and the availability status of the parallel gateway to the MVB data and send it to the MVB bus. The on-board device receives the data of gateway A and gateway B simultaneously through the MVB bus, selects the data with the master and standby status as the main data, and sends the data to the judicial recorder through the Profibus bus for storage.

[0098] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0099] It should be noted that the devices and methods disclosed in the embodiments of this article can also be implemented in other ways. The device implementation described above is only schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of this article. In this regard, each box in the flowchart or block diagram can represent a part of a module, program or code, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented by a dedicated hardware-based system for performing a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0100] In addition, the functional modules in the various embodiments of this document may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0101] Although the content of the present invention has been described in detail through the above preferred embodiments, it should be appreciated that the above description should not be considered as a limitation of the present invention. After reading the above content, it will be apparent to those skilled in the art that various modifications and substitutions of the present invention will occur. Therefore, the protection scope of the present invention should be limited by the appended claims.

Claims

1. A system for redundant communication between an MVB bus and a TCMS network, characterized in that: include: Vehicle-mounted equipment; MVB bus; Vehicle TCMS network; At least two sets of MVB-TCMS conversion gateways, used to perform MVB-TCMS protocol conversion on the received data; wherein the two sets of MVB-TCMS conversion gateways are parallel gateways to each other; The vehicle-mounted device is connected to each of the MVB-TCMS conversion gateways via the MVB bus; Each of the MVB-TCMS conversion gateways is connected to the vehicle TCMS network; The vehicle-mounted device sends vehicle-mounted data to the MVB-TCMS conversion gateway through the MVB bus, receives vehicle network data sent by the MVB-TCMS conversion gateway, and selects the primary and secondary states of the vehicle network data for use as the primary vehicle network data.

2. The system for redundant communication between the MVB bus and the TCMS network according to claim 1, characterized in that: The vehicle TCMS network is connected to each of the MVB-TCMS conversion gateways via Ethernet, and is used to send the vehicle network data to the MVB-TCMS conversion gateway and receive the vehicle-mounted data sent by the MVB-TCMS conversion gateway.

3. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 2, characterized in that: Also includes: A judicial recorder is connected to the vehicle-mounted device via a Profibus bus, receives and stores the vehicle network data currently used by the vehicle-mounted device, and the available status of the current main gateway and backup gateway for fault diagnosis.

4. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 3, characterized in that: The number of the vehicle TCMS networks is the same as the number of the MVB-TCMS conversion gateways, and the two are connected one-to-one.

5. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 4, characterized in that: When the on-board device sends data to the vehicle TCMS network, the on-board device sends the on-board data to the MVB bus. Each of the MVB-TCMS conversion gateways receives the on-board data from the configured MVB bus port, performs protocol conversion to form network data packets, and sends them to the corresponding vehicle TCMS network through the network protocol.

6. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 4, characterized in that: When the vehicle TCMS network sends data to the vehicle-mounted device, the MVB-TCMS conversion gateway receives the corresponding vehicle network data from the corresponding vehicle TCMS network through a network protocol, and receives the corresponding MVB data of the parallel gateway from the MVB bus; The MVB-TCMS conversion gateway determines and updates its own master-slave status and determines the data availability status of the parallel gateway based on preset rules according to the received vehicle network data and the MVB data of the parallel gateway; The MVB-TCMS conversion gateway converts the corresponding vehicle network data into new MVB data, and appends its own master / slave status and data availability status of the parallel gateway to the new MVB data, and sends it to the MVB bus; The vehicle-mounted device simultaneously receives new MVB data sent by each MVB-TCMS conversion gateway through the MVB bus, selects the MVB data in the new MVB data in the primary standby state for use, and sends the new MVB data to the judicial recorder for storage through the Profibus bus.

7. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 6, characterized in that: The switching conditions for determining and updating its own master / slave status based on preset rules are as follows: Rule 1: After power-on, initialize the two sets of MVB-TCMS conversion gateways to the standby state, and configure one gateway to start after a 60-second delay after power-on; Rule 2: This MVB-TCMS conversion gateway needs to monitor the TCMS heartbeat in the received vehicle network data. If it does not change for more than 1 second, the vehicle network data received by this MVB-TCMS conversion gateway is considered invalid, and the master-slave state of this MVB-TCMS conversion gateway is set to standby; Rule 3: If the master-slave status in the output of this MVB-TCMS conversion gateway is backup, and the vehicle network data received by this MVB-TCMS conversion gateway is valid, and the master-slave status received from the parallel gateway is backup, then the master-slave status of this MVB-TCMS conversion gateway is set to master; Rule 4: If the master-slave state of the MVB-TCMS conversion gateway is standby, and the vehicle network data received by the MVB-TCMS conversion gateway is valid, and the MVB data from the parallel gateway cannot be received for more than 1 second, the master-slave state of the MVB-TCMS conversion gateway is set to master; Before power-on initialization, the priorities of the two sets of MVB-TCMS conversion gateways are preset, where the priority of one MVB-TCMS conversion gateway is greater than the priority of the other MVB-TCMS conversion gateway. When there may be a conflict between the two sets of MVB-TCMS conversion gateways, Rule 5 is executed; Rule 5, if the MVB-TCMS conversion gateway with a lower priority detects that the master-slave state of the MVB-TCMS conversion gateway with a higher priority is master, the master-slave state of the MVB-TCMS conversion gateway with a lower priority is unconditionally set to slave, and the MVB-TCMS conversion gateway with a higher priority does not need to detect its own master-slave state again.

8. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 6, characterized in that: The judgment rule for the data availability status of the parallel gateway is: if the TCMS heartbeat in the parallel gateway MVB data received by this MVB-TCMS conversion gateway does not change for more than 1 second, the MVB data availability status of the parallel gateway is set to unavailable, otherwise it is set to available.

9. The system for redundant communication between the MVB bus and the TCMS network as claimed in claim 6, characterized in that: The vehicle-mounted device receives two new MVB data from the MVB bus, and selects one new MVB data to use according to the master / slave status in the new MVB data. The selection principle is as follows: When the master-slave state of the new MVB data sent by the MVB-TCMS conversion gateway is master, and the master-slave state of the new MVB data sent by the parallel gateway of the MVB-TCMS conversion gateway is standby, the vehicle-mounted device uses the new MVB data sent by the MVB-TCMS conversion gateway; When the master-slave state of the new MVB data sent by the parallel gateway of the MVB-TCMS conversion gateway is master, and the master-slave state of the new MVB data sent by the MVB-TCMS conversion gateway is standby, the vehicle-mounted device uses the new MVB data sent by the parallel gateway of the MVB-TCMS conversion gateway; When the active and standby states of the two sets of the MVB-TCMS conversion gateways are both active, or the active and standby states of the two sets of the MVB-TCMS conversion gateways are both standby, the vehicle-mounted device does not use any MVB data and determines that the communication fails.

10. A method for redundant communication between an MVB bus and a TCMS network, characterized in that: Based on the system implementation of redundant communication between the MVB bus and the TCMS network according to any one of claims 1 to 9, the method comprises: The MVB-TCMS conversion gateway converts the received vehicle data into a protocol and sends it to the corresponding vehicle TCMS network; and / or, converting the received vehicle network data into a protocol through the MVB-TCMS conversion gateway and sending the converted data to the MVB bus; The vehicle-mounted device selects the vehicle network data in the primary-standby state for use as the primary vehicle network data.

11. An electronic device, characterized in that: The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method according to claim 10 is implemented.

12. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claim 10 is implemented.

Images