CN115348199A - Vehicle-mounted network debugging system and method based on MVB bus - Google Patents

Vehicle-mounted network debugging system and method based on MVB bus Download PDF

Info

Publication number
CN115348199A
CN115348199A CN202210803564.3A CN202210803564A CN115348199A CN 115348199 A CN115348199 A CN 115348199A CN 202210803564 A CN202210803564 A CN 202210803564A CN 115348199 A CN115348199 A CN 115348199A
Authority
CN
China
Prior art keywords
subsystems
cloud server
mvb bus
subsystem
bus
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.)
Pending
Application number
CN202210803564.3A
Other languages
Chinese (zh)
Inventor
宾华佳
黄赫
熊艳
许清
汤长春
王拥军
李洁
罗钦洋
杨军
左宇辰
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.)
Zhuzhou CRRC Times Electric Co Ltd
Original Assignee
Zhuzhou CRRC Times Electric Co Ltd
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 Zhuzhou CRRC Times Electric Co Ltd filed Critical Zhuzhou CRRC Times Electric Co Ltd
Priority to CN202210803564.3A priority Critical patent/CN115348199A/en
Publication of CN115348199A publication Critical patent/CN115348199A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/50Testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L2012/40267Bus for use in transportation systems
    • H04L2012/40293Bus for use in transportation systems the transportation system being a train

Abstract

The invention discloses a vehicle-mounted network debugging system and method based on MVB bus, comprising a cloud server and a plurality of subsystems in different regions; the cloud server is provided with a virtual interface module corresponding to each local interface device of the plurality of subsystems; each subsystem is connected with the cloud server in a wireless mode, and each subsystem carries out MVB bus vehicle-mounted network debugging on the basis of the virtual interface module in the cloud server and the subsystem in the corresponding region. By applying the vehicle-mounted network debugging method based on the MVB bus, each subsystem based on the MVB bus communication can realize remote ground joint debugging, and the problem that equipment in each subsystem needs to be intensively installed in the same space due to the limitation of the communication distance of the MVB bus is solved. By constructing the virtual remote connection system, the subsystems in different regions can realize MVB communication among a plurality of subsystems without intensively installing equipment in the same space, so that the cost is reduced, and the resource waste is avoided.

Description

Vehicle-mounted network debugging system and method based on MVB bus
Technical Field
The invention relates to the technical field of rail transit, in particular to a vehicle-mounted network system and a vehicle-mounted network method based on MVB.
Background
The MVB Bus (Multifunction Vehicle Bus) is a part of a TCN (Train Communication Network), and is a serial data Bus designed mainly for (not dedicated) inter-connected devices with interoperability and interchangeability. Generally, an MVB bus is made up of one or more bus segments using the following transmission media, including: (1) The ESD short-distance medium adopts a differential transmission wire according to RS-485 standard, and can support 32 connection devices within a transmission distance of 20m at most without electrical isolation; (2) The EMD electric medium distance medium adopts a shielding twisted pair, can support 32 connecting devices at most within a transmission distance of 200m, and allows a transformer to be used as electric isolation; (3) The OGF optical fiber medium adopts optical fibers and forms a network through a star coupler, the transmission distance of the OGF optical fiber medium can reach 2.0km, and the OGF optical fiber medium is mainly used in harsh environments. In current rail transit application, MVB communication based on EMD medium distance medium is mostly adopted in most communication, and the maximum transmission distance is 200 meters.
In the prior art, as shown in fig. 1, when a vehicle-mounted network based on an MVB bus needs to be debugged, a debugging process based on the MVB bus is as follows: assuming that a complete MVB topology network exists in the A place, all MVB network subsystems are connected through an MVB bus in the A place, and the MVB topology network needs to be provided with an MVB bus management master device; a router needs to be configured on the site A, the router supports a 4G/5G internet access function, target equipment of the site A supports an Ethernet debugging function, and the target equipment is accessed to a local router through a single point; and at the moment, the monitoring and debugging of the target equipment in the site A can be realized at the PC end of the site B through the router.
Before a train is debugged for loading in the first train, the ground joint debugging is usually required to be executed, that is: and simulating an interface of an actual train loading subsystem and performing functional test in a laboratory or other non-loading environments. Therefore, the ground joint debugging is an important link from design to operation of the whole train, the connection and joint debugging test of all subsystems of the train before the train is loaded can be realized, the problems of interfaces and functions are effectively reduced, the related design functions can be verified in advance, and the time of the train in the actual debugging process can be greatly saved.
The technology for realizing train communication by the MVB based on the IEC 61375 standard is widely applied to rail transit, and the maximum transmission distance of the MVB communication is 2000 meters according to the IEC 61375 standard requirement. Therefore, in the ground debugging link in this case, the actual distance of connection of each subsystem cannot exceed 2000 meters, and for manufacturers located in different regions, if vehicle-mounted network ground joint debugging based on the MVB bus is to be implemented, the devices must be installed in the same space in a centralized manner. It should be noted that, the number of existing subsystems for performing communication based on the MVB bus is already up to 20, and the sizes of the subsystems are also not uniform, and if the subsystems are installed in a specific space in a centralized manner to perform ground joint debugging, not only is the cost in all aspects increased, but also a great waste of resources is caused.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: when the ground joint debugging is performed, equipment in the subsystem based on the MVB needs to be installed in a specific space to perform the ground joint debugging, so that the cost is increased, and resources are wasted.
In order to solve the technical problem, the invention provides a vehicle-mounted network debugging system based on an MVB bus, which is characterized by comprising: the system comprises a cloud server and a plurality of subsystems located in different regions;
the cloud server has a virtual interface module corresponding to each local interface device of the plurality of subsystems;
each subsystem is connected with the cloud server by utilizing a wireless communication technology, and each subsystem carries out MVB bus vehicle-mounted network debugging on the basis of a virtual interface module in the cloud server and the subsystem in the corresponding region.
Optionally, the cloud server includes:
a separately located server or server cluster; alternatively, the first and second electrodes may be,
a server in a plurality of subsystems.
Optionally, the plurality of subsystems communicate with the cloud server through an ethernet or a 4G/5G network.
Optionally, the cloud server is provided with an MVB bus management master device, and the MVB bus management master device implements remote virtual access to the multiple subsystems according to a polling mechanism.
Optionally, the plurality of subsystems include subsystems located in two different regions, and the first device in the first subsystem is used as a bus management master device.
Optionally, the cloud server implements access and verification of the authority of each subsystem; managing the interaction among the data of each subsystem; carrying out visual interface display on statistical data of the system, and carrying out data simulation; supporting firewall and event audit log.
In order to solve the technical problem, the invention provides a vehicle-mounted network debugging method based on an MVB bus, which is applied to the vehicle-mounted network debugging system based on the MVB bus and comprises the following steps:
the method comprises the steps of establishing communication connection between a cloud server and an MVB bus in advance;
the cloud server simulates local interface devices of a plurality of subsystems to obtain virtual interface modules corresponding to the local interface devices, wherein the subsystems are located in different regions;
and establishing communication connection between the subsystems and the cloud server, and performing vehicle-mounted network joint debugging based on a virtual test platform constructed by the cloud server and the virtual connection modules.
Optionally, the local MVB bus topology is provided with a master frame, and the data transmitted by each local interface device to the cloud server is a slave frame responded by the slave device of each subsystem or a received bus slave frame of another subsystem.
To solve the above technical problem, the present invention provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method according to claim 7 or 8 when executing the computer program.
To solve the above technical problem, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the program is to implement the method according to claim 7 or 8 when executed by a processor.
Compared with the prior art, one or more embodiments in the above scheme can have the following advantages or beneficial effects:
by applying the vehicle-mounted network debugging system and method based on the MVB bus, each subsystem based on MVB bus communication can realize remote ground joint debugging, and the problem that equipment in each subsystem needs to be intensively installed in the same space due to the limitation of the communication distance of the MVB bus in the prior art is solved. Moreover, by constructing the virtual remote connection system, the MVB communication among the subsystems can be realized by the subsystems in different regions without intensively installing equipment in the same space, so that the cost is reduced, and the resource waste is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is an architecture diagram of a conventional remote access topology network according to an embodiment of the present invention;
fig. 2 is a structural diagram of a vehicle network debugging system based on an MVB bus according to an embodiment of the present invention;
fig. 3 is a flowchart of a vehicle network debugging method based on MVB bus according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a data flow process of each subsystem according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an ethernet transport format according to an embodiment of the present invention;
fig. 6 is a block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
When the ground joint debugging is performed, equipment in the subsystem based on the MVB needs to be installed in a specific space to perform the ground joint debugging, so that the cost is increased, and resources are wasted. In order to solve the technical problem, the invention provides a vehicle-mounted network debugging system and method based on an MVB bus.
The vehicle-mounted network debugging system based on the MVB bus provided by the embodiment of the invention is explained below.
Example one
As shown in fig. 2, an architecture diagram of a vehicle network debugging system based on MVB bus provided in an embodiment of the present invention includes: a cloud server and a plurality of subsystems located in different regions. Specifically, the subsystems in FIG. 2 may include subsystems located at A site, B site, C site, \8230;, X site.
Wherein the cloud server has a virtual interface module corresponding to each local interface device of the plurality of subsystems.
Optionally, the cloud server includes: a server or server cluster set individually; or, a server in multiple subsystems. In practical applications, the cloud server in the vehicle network debugging system for the MVB bus may not be set, for example, the function of the cloud server is realized by moving the related function of the cloud server down to the local interface terminal.
Each subsystem is respectively connected with the cloud server by utilizing a wireless communication technology, and in one situation, the subsystems are communicated with the cloud server through an Ethernet or a 4G/5G network; and each subsystem carries out MVB bus vehicle-mounted network debugging based on the virtual interface module in the cloud server and the subsystem in the corresponding region. It should be noted that the present invention does not need to limit the specific form of the wireless communication technology, and only needs to satisfy the remote communication.
In one embodiment, the cloud server is provided with an MVB bus management master device, and the MVB bus management master device implements remote virtual access of the plurality of subsystems according to a polling mechanism.
In one case, the plurality of subsystems may include subsystems located in two different regions, and the first device in the first subsystem is used as a bus management master device. For example, two subsystems of a certain a place and a certain B place may be included, and a first device of a certain a place, such as device A1, serves as a bus management master device.
In addition, the cloud server realizes authority access and inspection of each subsystem; managing interaction between data of each subsystem; carrying out visual interface display on statistical data of the system, and carrying out data simulation; supporting firewall and event audit log.
It should be noted that the method can realize remote connection between subsystems based on MVB bus communication, thereby "breaking" the restriction of MVB bus communication distance, i.e. the subsystems in different regions can realize MVB bus communication of multiple systems without installing physical objects in a certain space, thereby constructing a virtual remote connection system.
Moreover, the vehicle-mounted network debugging system based on the MVB bus provided by the embodiment of the invention can be accessed in various places to obtain the data of the whole train, inquire the actual situation of the train through a local device, construct big data analysis of the train based on an on-line cloud system, and realize multi-party sharing of the big data of the train; based on the system, joint debugging of different systems in various regions can be realized, and a virtual test platform constructed by the current train is supported.
By applying the vehicle-mounted network debugging system based on the MVB bus, each subsystem based on MVB bus communication can realize remote ground joint debugging, and the problem that equipment in each subsystem needs to be intensively installed in the same space due to the limitation of the communication distance of the MVB bus in the prior art is solved. Moreover, by constructing the virtual remote connection system, the MVB communication among the subsystems can be realized by the subsystems in different areas without intensively installing equipment in the same space, so that the cost is reduced, and the resource waste is avoided.
The vehicle-mounted network debugging method based on the MVB bus provided by the embodiment of the present invention is explained below.
Example two
As shown in fig. 3, which is a flowchart of a vehicle network debugging method based on an MVB bus according to an embodiment of the present invention, the method applied to the vehicle network debugging system based on the MVB bus may include the following steps:
step S101: and communication connection between the cloud server and the MVB is established in advance.
Step S102: the cloud server simulates local interface devices of a plurality of subsystems to obtain virtual interface modules corresponding to the local interface devices, wherein the subsystems are located in different regions.
Step S103: and establishing communication connection between the subsystems and the cloud server, and performing vehicle-mounted network joint debugging based on a virtual test platform constructed by the cloud server and the virtual connection modules.
In one example of the present invention, the local MVB bus topology is provided with a master frame, and the data transmitted by each local interface device to the cloud server is a slave frame responded by the slave device of each subsystem or a received bus slave frame of other subsystem.
The devices in different subsystems networked by the system can be located in all places of the world, the transmission delay and the response interval reach the millisecond level, however, the reply interval between the master frame and the slave frame needs to respond within the specified time such as the microsecond level, and if the remote interaction between the subsystems is realized, the normal polling between the master device and the slave device cannot be realized. For example, the A1 device in the subsystem a is set as the bus master of the subsystem a, the subsystem B, and the subsystem C (which may be referred to as a bus master for ease of understanding), the local interface device B of the subsystem B is the master device in the subsystem B (which may be referred to as a bus master for ease of understanding), and the local interface device C of the subsystem C is the master device in the subsystem C (which may be referred to as a bus master for ease of understanding). The local interface device a of the subsystem a becomes a slave device (for convenience of understanding, it may be referred to as a bus slave) of the subsystem a.
The setting principle of the local master equipment and the local slave equipment is as follows: the local interface device of the subsystem where the bus management main equipment is positioned is secondary slave equipment in a bus topological structure; and the local interface devices of other subsystems are secondary main equipment in a bus topological structure, and replace the bus management main equipment to complete the communication of a master-slave mechanism in a system formed locally.
It should be noted that, referring to fig. 4, the local interface device in each subsystem may be divided into two major parts, i.e., a first management unit and a second management unit according to the implemented functions, where the first management unit may receive data, configuration instructions, and the like sent by the cloud server through the MVB bus, or send data in a fixed format to the cloud server, and the second management unit may manage a locally-constructed bus topology network.
Specifically, the first management unit mainly packages the slave frames in the subsystems into ethernet data packets and transmits the ethernet data packets to the cloud server, and parses the ethernet data acquired from the cloud server into packet slave frames and transmits the packet slave frames to the second management unit.
Furthermore, ethernet packet definition as shown in fig. 5 below, a general ethernet format can be understood colloquially as: the method comprises the steps of frame header, application data and frame tail, and the first management unit is mainly used for customizing data of other subsystems in remote virtual connection in the application data.
In one case, when a local interface device in a subsystem is a bus little master, the second management unit can realize a master-slave polling mechanism for managing the bus of the local equipment, and transmit slave frames of equipment in the local subsystem to the first management unit, and the first management unit packs and transmits the slave frame data to the cloud system; in addition, the slave frame data acquired from the first management unit is combined with the main frame existing in the topological network of the local subsystem and is put into the topological network of the local subsystem, so that other equipment in the local subsystem can acquire the train data of the equipment accessed remotely from the topological network of the local subsystem.
When the local interface device is a bus secondary slave device, the second management unit transmits a slave frame of the local subsystem device to the first management unit, and the first management unit packages and transmits the slave frame data to the cloud system; in addition, the second management unit acquires the slave frame data from the first management unit, and when detecting that the master frame corresponding to the slave frame exists in the system MVB bus, puts the slave frame on the bus to respond to the master frame. The master frame is periodic, and the slave frame also has to be a periodic response, the second management unit needs to set a data simulation transmission mechanism, if the slave frame of a certain port is not obtained from the first management unit within the time T, the data obtained at the last moment is taken as the periodic response to the master frame in the topology network of the local subsystem within the time T, and when the data update of the first management unit is not received after the time T is exceeded, it is determined that the slave frame of the port is abnormal, the master frame of the port is still transmitted in the local bus topology but the slave frame is not released, and the data of the port by the remote system cannot be received by other local systems.
The master-slave polling mechanism of the MVB is realized based on the port address of the MVB, so that a corresponding port list needs to be configured for a local interface device, the port of a subsystem needs to be configured in advance, and the list supports manual configuration and can also be installed remotely through a cloud server. In addition, the ports of other remote subsystems are automatically identified by retrieving the ports in the data from the first management unit and support automatic addition to the list, which is downloadable in the second management unit.
A master frame polling mechanism of an MVB bus is described below, according to IEC 61375 standard, the MVB bus communication uses a communication mode in which a master frame polls a slave frame to respond, that is, a complete MVB message is composed of an MVB master frame and a slave frame, where the MVB master frame is sent by a bus management master device, the slave frame is sent by a device (called a source device for short, i.e., each subsystem, such as an air conditioner, a vehicle door, etc.) corresponding to a source port of the message, and when the source device receives the master frame sent by the bus management master device, it will immediately respond to the master frame and send a corresponding slave frame, and the slave frame contains communication data of the message, that is, one time of MVB communication is completed. Because the master frame is periodically polled, according to the IEC 61375 standard, a device in normal communication on the bus must reply one slave frame after detecting that the master frame sent by the bus management master device belongs to the master frame that the system needs to reply, and the reply interval between the master frame and the slave frame needs to respond within a specified time (microsecond level), so that the slave frame also replies in a period corresponding to the master frame, and the cycle is repeated and is continuously circulated, thereby realizing the data interaction of the MVB bus, and if the master frame is detected and the slave frame is not replied, the device belongs to an abnormal condition. Due to the master-slave frame communication mechanism of the MVB, a bus management master device must exist in any minimum MVB bus network, and the slave device does not need to do the requirement.
The MVB bus port refers to an MVB communication frame, and according to IEC 61375 standard, a field in the main frame represents the information, which can be understood in common as: the system connected to the bus distinguishes the master frame in the bus that requires the system to reply to the slave frame by identifying the MVB bus port in the master frame.
By applying the vehicle-mounted network debugging method based on the MVB bus, each subsystem based on MVB bus communication can realize remote ground joint debugging, and the problem that equipment in each subsystem needs to be intensively installed in the same space due to the limitation of the communication distance of the MVB bus in the prior art is solved. Moreover, by constructing the virtual remote connection system, the MVB communication among the subsystems can be realized by the subsystems in different areas without intensively installing equipment in the same space, so that the cost is reduced, and the resource waste is avoided.
EXAMPLE III
To solve the above technical problem, the present invention provides a computer device, as shown in fig. 6, including a memory 210, a processor 220 and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the method as described above.
The computer device can be a desktop computer, a notebook, a palm computer, a cloud server and other computing devices. The computer device may include, but is not limited to, a processor 220, a memory 210. Those skilled in the art will appreciate that fig. 6 is merely an example of a computing device and is not intended to be limiting of computing devices, and may include more or fewer components than shown, or some of the components may be combined, or different components, e.g., the computing device may also include input output devices, network access devices, buses, etc.
The Processor 220 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 210 may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. The memory 210 may also be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the computer device. Further, the memory 210 may also include both an internal storage unit and an external storage device of the computer device. The memory 210 is used for storing the computer program and other programs and data required by the computer device. The memory 210 may also be used to temporarily store data that has been output or is to be output.
Example four
The embodiment of the present application further provides a computer-readable storage medium, which may be a computer-readable storage medium contained in the memory in the foregoing embodiment; or it may be a separate computer readable storage medium not incorporated into the computer device. The computer readable storage medium stores one or more computer programs which, when executed by a processor, implement the method described above.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory 210, read-Only Memory (ROM), random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
For system or apparatus embodiments, since they are substantially similar to method embodiments, they are described in relative simplicity, and reference may be made to some descriptions of method embodiments for related points.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the present application. For the specific working processes of the units and modules in the system, reference may be made to the corresponding processes in the foregoing method embodiments, which are not described herein again.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
It is to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if the described condition or event is detected" may be interpreted to mean "upon determining" or "in response to determining" or "upon detecting the described condition or event" or "in response to detecting the described condition or event", depending on the context.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.

Claims (10)

1. A vehicle network debugging system based on MVB bus is characterized by comprising: the system comprises a cloud server and a plurality of subsystems located in different regions;
the cloud server has a virtual interface module corresponding to each local interface device of the plurality of subsystems;
each subsystem is connected with the cloud server by utilizing a wireless communication technology, and each subsystem carries out MVB bus vehicle-mounted network debugging on the basis of a virtual interface module in the cloud server and the subsystems in the corresponding regions.
2. The MVB bus based in-vehicle network debugging system of claim 1, wherein the cloud server comprises:
a separately located server or server cluster; alternatively, the first and second electrodes may be,
a server in a plurality of subsystems.
3. The MVB bus based in-vehicle network debugging system of claim 1, wherein said plurality of subsystems communicate with said cloud server via Ethernet or 4G/5G network.
4. The vehicle-mounted network debugging system based on MVB bus of claim 2, wherein said cloud server is provided with an MVB bus management master device, and said MVB bus management master device implements remote virtual access of said plurality of subsystems according to a polling mechanism.
5. The MVB bus based on-board network debugging system of claim 4, wherein the plurality of subsystems comprise subsystems located in two different regions, and a first device in the first subsystem is used as a bus management master device.
6. The MVB bus based vehicle network debugging system of claim 1, wherein the cloud server implements access and verification of the authority of each subsystem; managing interaction between data of each subsystem; carrying out visual interface display on statistical data of the system, and carrying out data simulation; supporting firewall and event audit log.
7. An MVB bus-based vehicle network debugging method applied to the system of any one of claims 1 to 6, comprising:
the method comprises the steps that communication connection between a cloud server and an MVB bus is established in advance;
the cloud server simulates local interface devices of a plurality of subsystems to obtain virtual interface modules corresponding to the local interface devices, wherein the subsystems are located in different regions;
and establishing communication connection between the subsystems and the cloud server, and performing vehicle-mounted network joint debugging based on a virtual test platform constructed by the cloud server and the virtual connection modules.
8. The vehicle-mounted network debugging method based on MVB bus of claim 7, wherein the local MVB bus topology is provided with a master frame, and the data transmitted to the cloud server by each local interface device is a slave frame responded by the slave device of each subsystem or a received bus slave frame of other subsystems.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to claim 7 or 8 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to claim 7 or 8.
CN202210803564.3A 2022-07-07 2022-07-07 Vehicle-mounted network debugging system and method based on MVB bus Pending CN115348199A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210803564.3A CN115348199A (en) 2022-07-07 2022-07-07 Vehicle-mounted network debugging system and method based on MVB bus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210803564.3A CN115348199A (en) 2022-07-07 2022-07-07 Vehicle-mounted network debugging system and method based on MVB bus

Publications (1)

Publication Number Publication Date
CN115348199A true CN115348199A (en) 2022-11-15

Family

ID=83947862

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210803564.3A Pending CN115348199A (en) 2022-07-07 2022-07-07 Vehicle-mounted network debugging system and method based on MVB bus

Country Status (1)

Country Link
CN (1) CN115348199A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117061518A (en) * 2023-10-11 2023-11-14 富钛字节车载软件(长春)有限公司 Cloud native virtual CAN communication system and method

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001040940A2 (en) * 1999-12-02 2001-06-07 Microsoft Corporation Method and apparatus for remotely debugging computer software over a serial bus
CN102419554A (en) * 2011-09-05 2012-04-18 中国北车股份有限公司大连电力牵引研发中心 Vehicle equipment simulating method and system as well as simulation debugging equipment
CN109871325A (en) * 2019-01-31 2019-06-11 广州视声智能股份有限公司 A kind of KNX remote debugging method and system
CN110868344A (en) * 2019-10-17 2020-03-06 北京全路通信信号研究设计院集团有限公司 Method, system, device and computer readable medium for simulating MVB
CN113085952A (en) * 2020-01-08 2021-07-09 株洲中车时代电气股份有限公司 Train monitoring system
DE102021109507A1 (en) * 2020-06-16 2021-12-16 Hewlett Packard Enterprise Development Lp Universal industrial I / O interface bridge
CN113821440A (en) * 2021-09-27 2021-12-21 中车株洲电力机车有限公司 VxWorks application software testing method, system and simulator

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001040940A2 (en) * 1999-12-02 2001-06-07 Microsoft Corporation Method and apparatus for remotely debugging computer software over a serial bus
CN102419554A (en) * 2011-09-05 2012-04-18 中国北车股份有限公司大连电力牵引研发中心 Vehicle equipment simulating method and system as well as simulation debugging equipment
CN109871325A (en) * 2019-01-31 2019-06-11 广州视声智能股份有限公司 A kind of KNX remote debugging method and system
CN110868344A (en) * 2019-10-17 2020-03-06 北京全路通信信号研究设计院集团有限公司 Method, system, device and computer readable medium for simulating MVB
CN113085952A (en) * 2020-01-08 2021-07-09 株洲中车时代电气股份有限公司 Train monitoring system
DE102021109507A1 (en) * 2020-06-16 2021-12-16 Hewlett Packard Enterprise Development Lp Universal industrial I / O interface bridge
CN113821440A (en) * 2021-09-27 2021-12-21 中车株洲电力机车有限公司 VxWorks application software testing method, system and simulator

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李洋;石丽;: "机车车辆的MVB-CAN总线网关设计", 铁路计算机应用, no. 08 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117061518A (en) * 2023-10-11 2023-11-14 富钛字节车载软件(长春)有限公司 Cloud native virtual CAN communication system and method
CN117061518B (en) * 2023-10-11 2024-01-12 富钛字节车载软件(长春)有限公司 Cloud native virtual CAN communication system and method

Similar Documents

Publication Publication Date Title
CN107547589B (en) Data acquisition processing method and device
CN111371638B (en) Intelligent equipment testing method and device, server and storage medium
US20120023206A1 (en) Address distributing method and device
CN105119793A (en) Identifier distribution method of sensor network CAN bus frame format
WO2019192343A1 (en) Vehicle diagnosis method, related device and system
CN112199266B (en) Log transmission method and system for vehicle-mounted machine system, vehicle and storage medium
CN115657553A (en) PCIE topology and PCIE equipment simulation method, device, equipment and medium
CN115348199A (en) Vehicle-mounted network debugging system and method based on MVB bus
CN112698838B (en) Multi-cloud container deployment system and container deployment method thereof
CN112733206A (en) Resource allocation method, device, server and medium
US20190296937A1 (en) Central Data Store in Vehicle Electrical System
US11373464B2 (en) Vehicle-mounted communications device, log collection method, and log collection program
CN112965463B (en) Remote diagnosis system and remote diagnosis method
Dekanic et al. Integration of CAN bus drivers and UDS on Aurix platform
CN106713030A (en) Software source management method based on safety management and control and software function management system
CN116723198A (en) Multi-node server host control method, device, equipment and storage medium
CN106713093B (en) A kind of avionics data distribution model and method
CN115514682A (en) Data transmission method, device, equipment and storage medium
CN115550427A (en) Equipment upgrading method, device, equipment and storage medium
CN212112213U (en) Quality analysis system based on big data
CN114006942A (en) Data processing method, system, electronic equipment and storage medium
CN107729059A (en) A kind of task loading method based on FC networks
CN109379211B (en) Network monitoring method and device, server and storage medium
CN116527555B (en) Cross-platform data intercommunication consistency test method
CN114640632B (en) Data aggregation method, system, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination