AUTBUS-MVB protocol conversion device and method
The AUTBUS-MVB protocol converter enables seamless integration between AUTBUS and MVB buses, resolving protocol incompatibility issues and improving data transmission efficiency and stability. It is suitable for applications in rail transit and intelligent manufacturing.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-29
- Publication Date
- 2026-04-07
AI Technical Summary
In existing technologies, the incompatibility of protocols between AUTBUS and MVB buses leads to problems such as data incompatibility and low transmission efficiency.
An AUTBUS-MVB protocol conversion device is adopted, including a bus protocol conversion module, an MVB communication module, and an AUTBUS communication module. Protocol compatibility and data format conversion are achieved through address mapping, data structure conversion unit, and communication timing coordination module. Buffer and flow control module prevents data congestion.
It achieves seamless integration between AUTBUS and MVB bus, ensuring real-time and stable data transmission, reducing upgrade costs, supporting high-speed data transmission, and meeting the needs of rail transit and intelligent manufacturing.
Smart Images
Figure CN121814864A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of industrial automation communication protocol conversion, and discloses an AUTBUS-MVB protocol conversion device and method. BACKGROUND
[0002] MVB bus (Multifunction Vehicle Bus) is a field bus technology specially designed for rail transit vehicles, which complies with IEC 61375 standard, adopts master-slave architecture, supports three types of transmission of process data, message data and supervision data, and has high real-time performance and reliability. It is widely used in key fields such as train control and management system (TCMS), traction and braking, and door control, and realizes distributed real-time data interaction and fault diagnosis. However, with the increasing requirements of vehicle intelligence, the 1.5 Mbps bandwidth of MVB bus has become a key bottleneck, and a new bus form is urgently needed to replace the train network bus. SUMMARY
[0003] In view of the above technical deficiencies, the purpose of the present application is to provide an AUTBUS-MVB protocol conversion device and method, which solves the problem of low transmission efficiency and data intercommunication caused by protocol incompatibility between AUTBUS and MVB bus in the prior art.
[0004] To solve the above technical problems, the present application adopts the following technical solutions: In a first aspect, the present application provides an AUTBUS-MVB protocol conversion device, comprising: a bus protocol conversion module for realizing protocol mapping between AUTBUS data frames and MVB master frames or slave frames, including data reorganization and address mapping; a MVB communication module connected to the MVB bus through a MVB DSUB9 interface, wherein the MVB bus is connected to a MVB device, and the MVB communication module is connected to the bus protocol conversion module through a UART interface; an AUTBUS communication module connected to the AUTBUS bus through an AUTBUS interface, wherein the AUTBUS bus is connected to an AUTBUS network, and the AUTBUS communication module is connected to the bus protocol conversion module through an OFDM interface; The bus protocol conversion module, the MVB communication module and the AUTBUS communication module work cooperatively.
[0005] Preferably, in a possible implementation of the first aspect, the bus protocol conversion module comprises an address mapping unit for converting MVB device addresses or function addresses into IP / Node ID and service port of AUTBUS addresses, or converting AUTBUS addresses into MVB slave device numbers or virtual node numbers according to a preconfigured address mapping table.
[0006] Preferably, in one possible implementation of the first aspect, the bus protocol conversion module includes a data structure conversion unit, used to encapsulate periodic data frames of MVB addresses into AUTBUS data frames and add a protocol header, timestamp and service identifier, or to restore AUTBUS event frames into MVB periodic frames or response frames, and to construct periodic control bytes and CRC check segments.
[0007] Preferably, in one possible implementation of the first aspect, it further includes a communication timing coordination module for scheduling data transmission timing, wherein: For data frames switching from the MVB protocol to the AUTBUS protocol, synchronize the AUTBUS bus transmission window; For data frames that switch from the AUTBUS protocol to the MVB protocol, cache the data and wait for the MVB master station to poll for a response.
[0008] Preferably, in one possible implementation of the first aspect, a buffering and flow control module is further included, which employs an enqueue and dequeue mechanism, supports sliding windows and congestion control, and triggers a packet loss strategy or returns a status code when the buffer of the bus protocol conversion module is full.
[0009] In a second aspect, the present invention provides an AUTBUS-MVB protocol conversion method, the method being implemented based on the apparatus described in the first aspect, comprising: Step S1: Receive the input data frame, parse the input data frame, identify its protocol type as MVB data frame or AUTBUS data frame, and extract key information; Step S2: Based on the key information extracted in step S1, determine the source protocol type and the data flow direction based on the frame header structure; Step S3: Following the data flow determined in step S2, the source protocol address is converted to the target protocol address by looking up the pre-configured address mapping table; Step S4: Based on the address information converted in step S3, reassemble the data format of the source protocol into the data format of the target protocol; Step S5: Based on the communication characteristics of the target protocol, schedule the timing of data transmission and coordinate the communication timing. Step S6: Manage the data flow through a queue mechanism, perform buffering and flow control processing to prevent data bursts from causing congestion; Step S7: Send the transformed data frame processed in steps S4 and S5 through the target interface.
[0010] Preferably, in one possible implementation of the second aspect, in step S1, the key information of the MVB data frame includes the device address, frame type, function code, and data content. Key information in an AUTBUS data frame includes the source IP / Node ID, port number, data area, and service type.
[0011] Preferably, in one possible implementation of the second aspect, step S3 includes: The address mapping table is pre-stored based on device configuration information and maps MVB addresses to AUTBUS addresses, or vice versa.
[0012] Preferably, in one possible implementation of the second aspect, the communication timing coordination employs a soft clock scheduling mechanism to simulate the behavioral logic of the target protocol, ensuring that data is sent within the window allowed by the target protocol.
[0013] Preferably, in one possible implementation of the second aspect, the buffering and flow control processing includes: Establish enqueue and dequeue queues, determine the idle status of the target interface, and perform packet loss or return error code when the cache is full.
[0014] The beneficial effects of this invention are as follows: by integrating a bus protocol conversion module, an MVB communication module, and an AUTBUS communication module, this invention achieves seamless connection between AUTBUS and the MVB bus.
[0015] The address mapping unit and data structure conversion unit respectively solve the compatibility problem between protocol address and data format, ensuring that the MVB device address can be accurately mapped to the AUTBUS node ID, and completing the bidirectional conversion between periodic data frames and event frames.
[0016] The communication timing coordination module adopts a soft clock scheduling mechanism to synchronize the AUTBUS sending window or buffered MVB polling data, thus avoiding timing conflicts.
[0017] The buffering and flow control module effectively prevents data congestion and improves transmission stability through sliding windows and congestion control.
[0018] This device achieves protocol compatibility without modifying existing MVB equipment, reducing the cost of industrial network upgrades. It also supports high-speed data transmission, meeting the urgent needs of heterogeneous bus interconnection in fields such as rail transit and intelligent manufacturing. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0020] Figure 1 This application provides a structural diagram of an AUTBUS-MVB protocol conversion device.
[0021] Figure 2 This application provides an AUTBUS-MVB protocol conversion flowchart. Detailed Implementation
[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0023] Example 1: As Figure 1 As shown, the present invention provides an AUTBUS-MVB protocol conversion device, including a bus protocol conversion module, an MVB communication module and an AUTBUS communication module. The modules work together through a standard interface to realize the reception, parsing, conversion and transmission of data frames.
[0024] The bus protocol conversion module is responsible for handling the protocol mapping between AUTBUS data frames and MVB master or slave frames. This module includes an address mapping unit and a data structure conversion unit, ensuring data integrity and real-time performance during the conversion process. The address mapping unit, based on a pre-configured address mapping table, converts MVB device addresses or function addresses into AUTBUS IP / Node IDs and service ports, or converts AUTBUS addresses into MVB slave device numbers or virtual node numbers. The data structure conversion unit is responsible for data format reassembly, such as encapsulating periodic data frames from MVB addresses into standard AUTBUS data frames, adding protocol headers, timestamps, and service identifiers, or restoring AUTBUS event frames into MVB periodic or response frames. This process ensures data structure compatibility across different protocols and supports efficient bidirectional conversion.
[0025] The MVB communication module connects to the MVB bus via the MVB DSUB9 interface, linking to external MVB devices such as train control systems or braking systems. This module integrates MVB protocol parsing functionality and connects to the bus protocol conversion module via a UART interface to receive and transmit MVB data. The MVB communication module can parse the 34-bit fixed format of the MVB master frame and the 16- to 256-bit variable length data of the slave frame, extracting process data or message data and transmitting them to the protocol conversion module. Simultaneously, this module supports the periodic master-slave scheduling mechanism of the MVB bus, ensuring timely response to data within the polling cycle.
[0026] The AUTBUS communication module connects to the AUTBUS bus via an AUTBUS interface, linking high-speed devices within the AUTBUS network. This module uses an OFDM interface to connect to the bus protocol conversion module, enabling AUTBUS bus signal conversion and network access. The AUTBUS communication module processes AUTBUS protocol data frames, parsing the source NodeID, port number, data area, and service type, and forwards the data to the conversion module. Since the AUTBUS bus supports bandwidths up to 100Mbps and transmission distances up to 500 meters, this module fully utilizes its high real-time performance, optimizing data transmission through time-division multiplexing and dynamic time slot allocation.
[0027] The device also integrates a communication timing coordination module to resolve timing differences between the MVB periodic master polling architecture and the AUTBUS event-driven architecture. This module employs a soft clock scheduling mechanism to simulate the behavioral logic of the target protocol. For data frames switching from the MVB protocol to the AUTBUS protocol, the module synchronizes the AUTBUS bus transmission window and controls the timing of data push; for data frames switching from the AUTBUS protocol to the MVB protocol, the module buffers the data and waits for the next poll from the MVB master before returning a response.
[0028] The device also includes a buffering and flow control module, which manages data flow through enqueueing and dequeueing mechanisms to prevent network congestion caused by data bursts. This module establishes input and output queues, determines the idle status of the target interface, and supports sliding window and congestion control algorithms. When the bus protocol conversion module's buffer is full, the module triggers a packet loss policy or returns a status code to the source protocol to ensure system stability.
[0029] The modules are connected via hardware interfaces, with the bus protocol conversion module acting as the central hub, coordinating the operation of the MVB and AUTBUS communication modules. The device adopts an embedded design and may be based on a high-performance processor such as a multi-core ARM or DSP, integrating a large-capacity cache and dedicated protocol acceleration units to support real-time data processing. The power supply module and communication auxiliary module ensure the normal operation of the device, with the power supply module providing 3.3V / 5V power to the bus protocol conversion module, MVB communication module, and AUTBUS communication module.
[0030] Example 2: This invention provides an AUTBUS-MVB protocol conversion method, which is implemented based on the device in Example 1. The process is as follows: Figure 2 As shown, the method includes steps such as receiving and parsing input frames, determining the source protocol type, address mapping, data structure conversion, communication timing coordination, buffering and flow control processing, and data transmission. This method achieves seamless interoperability between heterogeneous buses by efficiently mapping MVB periodic data and AUTBUS message data.
[0031] Step S1: Receive input data frames, parse the input data frames, identify their protocol type as MVB data frames or AUTBUS data frames, and extract key information.
[0032] Regardless of whether the data frames arrive from the MVB or AUTBUS interface, they are first processed by the message parsing module. This module identifies the protocol type of the frame and extracts key information. Key information for MVB data frames includes the device address, frame type, function code, and data content. For MVB frames, the parsing process involves the device address, frame type (e.g., periodic or event), function code, and data content. MVB frames consist of a 34-bit fixed-format main frame and variable-length data (16 to 256 bits) from the secondary frames, from which process data (e.g., traction control signals) or message data (e.g., fault diagnosis information) is extracted. Key information for AUTBUS data frames includes the source IP / Node ID, port number, data area, and service type. For AUTBUS frames, the parsing process involves the source Node ID, port number, data area, and service type (e.g., subscription or write operation).
[0033] Step S2: Based on the key information extracted in step S1, determine the source protocol type and the data flow direction based on the frame header structure.
[0034] The data flow is determined based on the frame header structure, and the corresponding processing branch is entered. The protocol conversion module analyzes the frame header characteristics to distinguish between MVB frames and AUTBUS frames. If the frame comes from the MVB bus, it enters the MVB to AUTBUS conversion branch; if the frame comes from the AUTBUS bus, it enters the AUTBUS to MVB conversion branch.
[0035] Step S3: Following the data flow determined in step S2, the source protocol address is converted to the target protocol address by looking up the pre-configured address mapping table.
[0036] The source protocol address is translated into the target protocol address by looking up a pre-configured address mapping table. Based on device configuration information, the address mapping unit maps MVB device addresses or function addresses to AUTBUS Node IDs and service ports, or maps AUTBUS addresses to MVB slave device numbers or virtual node numbers. The mapping table stores bidirectional address correspondences, such as MVB device numbers corresponding to AUTBUS IP and port combinations, ensuring consistency in address translation.
[0037] Step S4: Based on the address information converted in step S3, reassemble the data format of the source protocol into the data format of the target protocol.
[0038] The source protocol data format is reconstructed into the target protocol data format. For MVB frames redirected to AUTBUS, the data structure conversion unit encapsulates the periodic small frames of MVB into standard AUTBUS data frames, adding AUTBUS protocol headers, timestamps, and service identifiers to adapt to AUTBUS's event-driven structure. For AUTBUS frames redirected to MVB, the unit restores AUTBUS event frames to MVB periodic frames or response frames, while constructing periodic control bytes and CRC check segments to ensure the data format conforms to MVB's fixed-length requirements.
[0039] Step S5: Based on the communication characteristics of the target protocol, schedule the timing of data transmission and coordinate the communication timing.
[0040] A soft clock scheduling mechanism is employed to simulate the behavioral logic of the target protocol, thus resolving the timing differences between the MVB periodic master polling architecture and the AUTBUS event-driven architecture. When an MVB frame is switched to AUTBUS, the module synchronizes the AUTBUS bus transmission window, controls the data push timing, and utilizes AUTBUS's time-division multiplexing and dynamic time slot allocation to ensure priority transmission of critical data. When an AUTBUS frame is switched to MVB, the module buffers the data, waiting for the next poll from the MVB master before returning a response, simulating the MVB polling cycle.
[0041] Step S6: Manage the data flow through a queue mechanism, perform buffering and flow control processing to prevent data bursts from causing congestion.
[0042] The buffering and flow control process manages data flow through a queuing mechanism to prevent network congestion caused by data bursts. The module establishes enqueue and dequeue queues, determines the idle status of the target interface, and supports sliding window and congestion control algorithms. When data flows from a high-speed side such as AUTBUS to a low-speed side such as MVB, the buffering module temporarily stores the data to prevent overflow; if the buffer is full, it triggers a packet loss policy or returns an error code to the source protocol.
[0043] Step S7: Send the converted data frame processed in steps S4 and S5 through the target interface.
[0044] The converted frame is sent through the target interface. Once the target interface is ready and the data is successfully queued through the buffering and scheduling mechanism, the frame is sent. For the AUTBUS direction, an AUTBUS data frame is sent; for the MVB direction, the corresponding periodic frame is responded to when the master station polls. After sending is complete, the protocol conversion module returns to the state of waiting for the next frame, realizing continuous operation.
[0045] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.
Claims
1. An AUTBUS-MVB protocol conversion device, characterized in that, include; The bus protocol conversion module is used to implement protocol mapping between AUTBUS data frames and MVB master or slave frames, including data reassembly and address mapping. The MVB communication module is connected to the MVB bus via the MVB DSUB9 interface. The MVB bus is connected to the MVB device. The MVB communication module is connected to the bus protocol conversion module via the UART interface. The AUTBUS communication module is connected to the AUTBUS bus via an AUTBUS interface. The AUTBUS bus is connected to the AUTBUS network. The AUTBUS communication module is connected to the bus protocol conversion module via an OFDM interface. The bus protocol conversion module works in conjunction with the MVB communication module and the AUTBUS communication module.
2. The AUTBUS-MVB protocol conversion device according to claim 1, characterized in that, The bus protocol conversion module includes an address mapping unit, which is used to convert the MVB device address or function address into the IP / Node ID and service port of the AUTBUS address according to the pre-configured address mapping table, or to convert the AUTBUS address into the MVB slave device number or virtual node number.
3. The AUTBUS-MVB protocol conversion device according to claim 1, characterized in that, The bus protocol conversion module includes a data structure conversion unit, which is used to encapsulate periodic data frames of MVB addresses into AUTBUS data frames and add protocol headers, timestamps and service identifiers, or to restore AUTBUS event frames into MVB periodic frames or response frames and construct periodic control bytes and CRC check segments.
4. The AUTBUS-MVB protocol conversion device according to claim 3, characterized in that, It also includes a communication timing coordination module, used to schedule data transmission timing, wherein: For data frames switching from the MVB protocol to the AUTBUS protocol, synchronize the AUTBUS bus transmission window; For data frames that switch from the AUTBUS protocol to the MVB protocol, cache the data and wait for the MVB master station to poll for a response.
5. An AUTBUS-MVB protocol conversion device according to claim 3, characterized in that, It also includes a buffer and flow control module, which adopts an enqueue and dequeue mechanism, supports sliding window and congestion control, and triggers a packet loss strategy or returns a status code when the buffer of the bus protocol conversion module is full.
6. An AUTBUS-MVB protocol conversion method, characterized in that, The method is implemented based on the apparatus as described in any one of claims 1 to 5, comprising: Step S1: Receive the input data frame, parse the input data frame, identify its protocol type as MVB data frame or AUTBUS data frame, and extract key information; Step S2: Based on the key information extracted in step S1, determine the source protocol type and the data flow direction based on the frame header structure; Step S3: Following the data flow determined in step S2, the source protocol address is converted to the target protocol address by looking up the pre-configured address mapping table; Step S4: Based on the address information converted in step S3, reassemble the data format of the source protocol into the data format of the target protocol; Step S5: Based on the communication characteristics of the target protocol, schedule the timing of data transmission and coordinate the communication timing. Step S6: Manage the data flow through a queue mechanism, perform buffering and flow control processing to prevent data bursts from causing congestion; Step S7: Send the converted data frame processed in steps S4 and S5 through the target interface.
7. The AUTBUS-MVB protocol conversion method according to claim 6, characterized in that, In step S1, the key information of the MVB data frame includes the device address, frame type, function code, and data content. Key information in an AUTBUS data frame includes the source IP / Node ID, port number, data area, and service type.
8. The AUTBUS-MVB protocol conversion method according to claim 6, characterized in that, Step S3 includes: The address mapping table is pre-stored based on device configuration information and maps MVB addresses to AUTBUS addresses, or vice versa.
9. The AUTBUS-MVB protocol conversion method according to claim 6, characterized in that, The communication timing coordination adopts a soft clock scheduling mechanism to simulate the behavior logic of the target protocol and ensure that data is sent within the window allowed by the target protocol.
10. The AUTBUS-MVB protocol conversion method according to claim 6, characterized in that, The buffering and flow control processing includes: Establish enqueue and dequeue queues, determine the idle status of the target interface, and perform packet loss or return error code when the cache is full.