Cross-bus route detection method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a cross-bus route detection method and device, electronic equipment and a storage medium. The cross-bus route detection method comprises the steps of obtaining a source end and a destination end of each route link in a vehicle; determining a routing link of which the corresponding source end and target end do not belong to the same bus as a target link; simulating a source end of the target link to generate a test signal, and sending the test signal through a bus to which the source end of the target link belongs; and judging whether the to-be-detected signal received by the destination end of the target link is the same as the test signal, if so, judging that the routing detection result of the target link is normal, and if not, judging that the routing detection result of the target link is routing failure. According to the method, targeted detection is carried out on the cross-bus routing link, the limitation that the prior art is limited to a single bus detection scene is broken through, data interaction faults among different bus systems can be found in time, cooperative failure and functional abnormality of the systems of the vehicle are avoided, and potential safety hazards are reduced.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a cross-bus routing detection method, apparatus, electronic device, and storage medium. Background Technology

[0002] Vehicles are equipped with numerous systems, such as engine control systems, autonomous driving systems, and multimedia entertainment systems. These systems may be connected to different buses. Therefore, cross-bus routing is required to enable data interaction between different bus systems and ensure that all vehicle systems work together.

[0003] To ensure stable and reliable routing communication between different buses, communication detection is required for cross-bus routes. However, existing communication detection methods are typically limited to single-bus detection scenarios and cannot perform communication detection for cross-bus routes. This results in data interaction failures between different bus systems not being detected in a timely manner, potentially leading to systemic malfunctions, abnormal functions, and even safety hazards. Summary of the Invention

[0004] This application provides a cross-bus routing detection method, apparatus, electronic device, and storage medium, aiming to improve the problem that communication detection for cross-bus routes is not possible, resulting in the inability to detect data interaction faults between different bus systems in a timely manner.

[0005] This application provides a cross-bus route detection method, including:

[0006] Obtain the source and destination endpoints of each routing link in the vehicle;

[0007] The routing links that do not belong to the same bus as the source and destination are identified as the target links;

[0008] The test signal is generated by simulating the source end of the target link, and the test signal is sent through the bus to which the source end of the target link belongs;

[0009] Determine whether the signal to be detected received at the destination end of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is determined to be normal. If they are different, the routing detection result of the target link is determined to be a routing failure.

[0010] As can be seen from the above, the solution provided in this application obtains the source and destination ends of each routing link in the vehicle, filters out target links whose source and destination ends do not belong to the same bus, and then determines the routing detection result by simulating the target link source end to generate and send test signals and comparing whether the received signal at the destination end is consistent with the test signal. Targeted detection is performed on routing links across buses. Compared with the prior art, which only detects signal transmission between nodes within the same bus, this solution can perform cross-route detection and realize the detection of the complete link. At the same time, compared with the prior art, which only verifies the consistency of signals under the same protocol and does not involve the differences in communication protocols between different buses, this solution can also detect the correctness of conversion between different protocols corresponding to different buses. This breaks through the limitation of the prior art being limited to a single bus detection scenario, and can promptly detect data interaction faults between different bus systems, avoid the failure of coordination and function abnormalities of various vehicle systems, and reduce safety hazards.

[0011] Optionally, obtaining the source and destination ends of each routing link in the vehicle includes:

[0012] Obtain the vehicle's communication matrix, which includes the source and destination ends of each routing link.

[0013] Optionally, determining the routing link whose corresponding source and destination ends do not belong to the same bus as the target link includes:

[0014] Each routing link is sequentially used as a link to be identified, and it is determined whether the source and destination ends of the link to be identified belong to the same bus.

[0015] If they do not belong to the same bus, the link to be identified will be used as the target link;

[0016] If they belong to the same bus, the next routing link is taken as the new link to be identified, and the process returns to the step of determining whether the source and destination ends of the link to be identified belong to the same bus, until there is no next routing link.

[0017] Optionally, after designating the link to be identified as the target link, the method further includes:

[0018] Write the source and destination ends of the target link into the target file;

[0019] Before generating a test signal at the source end of the simulated target link and sending the test signal through the bus to which the source end of the target link belongs, the method further includes:

[0020] Obtain the target file, and read the source and destination ends of the target link from the target file.

[0021] Optionally, the step of simulating the source end of the target link to generate a test signal and sending the test signal through the bus to which the source end of the target link belongs includes:

[0022] Each target link is sequentially used as the link to be tested. A test signal is generated by simulating the source end of the link to be tested, and the test signal is sent through the bus to which the source end of the link to be tested belongs.

[0023] If the results are the same, the routing detection result of the target link is determined to be normal; if they are different, the routing detection result of the target link is determined to be a routing failure. The process further includes:

[0024] The next target link is used as the new link to be tested. The process of generating a test signal at the source end of the simulated link to be tested is repeated until no next target link exists.

[0025] Optionally, determining that the routing detection result of the target link is normal includes:

[0026] After stopping the transmission of the test signal, it is determined whether the signal to be detected received by the destination end of the target link is the same as the preset timeout value. If it is the same as the preset timeout value, the routing detection result of the target link is determined to be normal.

[0027] If the result is different from the preset timeout value, the routing detection result of the target link is determined to be a timeout replacement failure.

[0028] This application also provides a cross-bus route detection method, applied to a link extraction subsystem, including:

[0029] Obtain the source and destination endpoints of each routing link in the vehicle;

[0030] The routing links that do not belong to the same bus as the source and destination are identified as the target links;

[0031] The source and destination ends of the target link are sent to the routing detection subsystem so that the routing detection subsystem can perform routing detection on the target link.

[0032] This application also provides a cross-bus route detection method, applied to a route detection subsystem, including:

[0033] Obtain the source and destination ends of at least one target link in the vehicle, wherein the source and destination ends of the target link do not belong to the same bus;

[0034] The test signal is generated by simulating the source end of the target link, and the test signal is sent through the bus to which the source end of the target link belongs;

[0035] Determine whether the signal to be detected received at the destination end of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is determined to be normal. If they are different, the routing detection result of the target link is determined to be a routing failure.

[0036] This application also provides a cross-bus routing detection device, applied to a test machine, including:

[0037] The link extraction subsystem is used to obtain the source and destination ends of each routing link in the vehicle; and to determine the routing links whose source and destination ends do not belong to the same bus, as the target links.

[0038] The routing detection subsystem is used to simulate the source end of the target link to generate a test signal and send the test signal through the bus to which the source end of the target link belongs; it determines whether the signal to be detected received by the destination end of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is determined to be normal. If they are different, the routing detection result of the target link is determined to be routing failure.

[0039] This application also provides an electronic device, including a processor and a memory, wherein:

[0040] Memory, used to store computer programs;

[0041] A processor for executing a program stored in memory to implement the method described in any of the preceding claims.

[0042] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements any of the methods described above. Attached Figure Description

[0043] Figure 1 This is a flowchart of a cross-bus route detection method provided in an embodiment of this application;

[0044] Figure 2 This is a flowchart of a cross-bus route detection method applied to a link extraction subsystem according to an embodiment of this application;

[0045] Figure 3 This is a flowchart of a cross-bus route detection method applied to a route detection subsystem according to an embodiment of this application;

[0046] Figure 4 This is a flowchart of a cross-bus route detection method provided in a specific embodiment of this application;

[0047] Figure 5This is a structural diagram of the cross-bus routing detection device provided in the embodiments of this application;

[0048] Figure 6 This is a structural diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0049] To make the technical problems, technical solutions, and beneficial effects solved by this application clearer, the following detailed description is provided in conjunction with embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0050] Vehicles are equipped with numerous systems that may connect to different buses. Cross-bus routing is necessary to enable data exchange between these systems and ensure coordinated operation. However, current communication detection methods often involve a node on a single bus generating a preset test signal, which is then received by other nodes within the bus to determine if each node can receive the signal correctly and if the received signal matches the transmitted signal. Due to limitations in design logic, detection scope, and technical difficulty, existing technologies are confined to single-bus detection scenarios. Cross-bus routing detection, on the other hand, requires attention to the integrity of routing links between different buses. These two methods differ significantly, making existing communication detection methods unsuitable for cross-bus scenarios and unable to perform communication detection for cross-bus routing. This results in data exchange failures between different bus systems going undetected, potentially leading to systemic malfunctions, abnormal functions, and even safety hazards.

[0051] Based on this, embodiments of this application provide a cross-bus route detection method to solve the above problems.

[0052] This application provides a cross-bus routing detection method applied to a test machine, comprising:

[0053] Obtain the source and destination endpoints of each routing link in the vehicle;

[0054] The routing links that do not belong to the same bus as the source and destination are identified as the target links;

[0055] The test signal is generated by simulating the source end of the target link, and the test signal is sent through the bus to which the source end of the target link belongs;

[0056] Determine whether the signal to be detected received at the destination end of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is determined to be normal. If they are different, the routing detection result of the target link is determined to be a routing failure.

[0057] As can be seen from the above, the solution provided in this application obtains the source and destination ends of each routing link in the vehicle, filters out target links whose source and destination ends do not belong to the same bus, and then determines the routing detection result by simulating the target link source end to generate and send test signals and comparing whether the received signal at the destination end is consistent with the test signal. Targeted detection is performed on routing links across buses. Compared with the prior art, which only detects signal transmission between nodes within the same bus, this solution can perform cross-route detection and realize the detection of the complete link. At the same time, compared with the prior art, which only verifies the consistency of signals under the same protocol and does not involve the differences in communication protocols between different buses, this solution can also detect the correctness of conversion between different protocols corresponding to different buses. This breaks through the limitation of the prior art being limited to a single bus detection scenario, and can promptly detect data interaction faults between different bus systems, avoid the failure of coordination and function abnormalities of various vehicle systems, and reduce safety hazards.

[0058] Example 1

[0059] This application provides a cross-bus routing detection method applied to a test machine. Please refer to [link / reference]. Figure 1 This includes the following steps:

[0060] S110: Obtain the source and destination ends of each routing link in the vehicle.

[0061] It is understandable that there are many systems inside a vehicle, and these systems interact with each other through different routing links. Therefore, we can first obtain the source and destination of each routing link in the vehicle, that is, the starting sending end (source end) and the receiving end (destination end) of each routing link. This will provide data support for subsequent screening of cross-bus links, ensuring that all possible routing relationships in the vehicle are covered and avoiding omission of critical links.

[0062] S120: Identify the corresponding routing links where the source and destination ends do not belong to the same bus, and use them as the target links.

[0063] In this step, after obtaining all routing link information, the cross-bus links that truly need to be detected are filtered out by determining whether the source and destination ends of each link are located on different buses. In other words, routing links whose source and destination ends do not belong to the same bus can be identified as target links.

[0064] This eliminates routing links within the same bus, making subsequent detection more targeted and avoiding unnecessary detection that wastes resources.

[0065] S130: Simulates the source end of the target link to generate a test signal and sends the test signal through the bus to which the source end of the target link belongs.

[0066] In this step, standardized test signals can be constructed for the selected target links by simulating the signal generation logic of the source node. For example, if the source is an "engine ECU on the CAN bus", test signals of the engine ECU can be simulated and sent on the CAN bus, instead of directly controlling the engine ECU to send signals.

[0067] Then, the test signal can be sent according to the predetermined route using the transmission channel of the bus to which the source belongs, in order to test the transmission capability of the target link.

[0068] S140: Determine whether the signal to be detected received at the destination end of the target link is the same as the test signal. If they are the same, the route detection result of the target link is determined to be normal. If they are different, the route detection result of the target link is determined to be route failure.

[0069] In this step, after the test signal is transmitted through the target link to the destination, the received signal to be detected is compared with the initially generated test signal. This can directly verify the accuracy of the signal transmission across the bus link. Specifically, it can be determined whether the signal to be detected received at the destination of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is considered normal; if they are different, the routing is considered to have failed.

[0070] This effectively identifies anomalies in cross-bus communication, providing a clear basis for ensuring the reliability of data interaction between different bus systems.

[0071] As can be seen from the above, the solution provided in this application obtains the source and destination ends of each routing link in the vehicle, filters out target links whose source and destination ends do not belong to the same bus, and then determines the routing detection result by simulating the target link source end to generate and send test signals and comparing whether the received signal at the destination end is consistent with the test signal. Targeted detection is performed on routing links across buses. Compared with the prior art, which only detects signal transmission between nodes within the same bus, it can perform cross-route detection and realize the detection of the complete link. At the same time, compared with the prior art, which only verifies the consistency of signals under the same protocol and does not involve the differences in communication protocols between different buses, it can also detect the correctness of conversion between different protocols corresponding to different buses. It breaks through the limitation of the prior art being limited to a single bus detection scenario, can timely detect data interaction faults between different bus systems, avoid the failure of coordination and function abnormalities of various vehicle systems, and reduce safety hazards.

[0072] Step S110 includes: obtaining the source and destination ends of each routing link in the vehicle, including:

[0073] Obtain the vehicle's communication matrix, which includes the source and destination ends of each routing link.

[0074] In this implementation, the source and destination of each routing link can be obtained by acquiring the vehicle's communication matrix. The various systems within the vehicle rely on numerous routing links for data exchange, and the communication matrix comprehensively records the source and destination information of each routing link in matrix form. It is a digital representation of the vehicle's communication architecture, encompassing not only the start and end points of data transmission between different systems but also reflecting the position and relationship of each link within the entire communication network.

[0075] By retrieving the communication matrix, the source and destination ends of all routing links can be systematically and accurately extracted, including links across buses and links within the same bus. The source and destination of their signals can be fully presented through the communication matrix, thereby ensuring the comprehensiveness of information acquisition, avoiding the omission of any potential routing link, and providing a standardized and structured data foundation for screening target links across buses in subsequent steps.

[0076] Step S120 includes: determining the corresponding routing links where the source and destination ends do not belong to the same bus, and using these links as the target links, including:

[0077] Each routing link is treated as a link to be identified in turn, and it is determined whether the source and destination ends of the link to be identified belong to the same bus.

[0078] If they do not belong to the same bus, the link to be identified will be the target link.

[0079] If they belong to the same bus, the next routing link is taken as the new link to be identified, and the process returns to the step of determining whether the source and destination of the link to be identified belong to the same bus, until there is no next routing link.

[0080] In this implementation, a polling mechanism can be used to accurately filter out the cross-bus links that need to be detected from all routing links. Specifically, each routing link in the vehicle can be treated as a link to be identified in turn, and its source and destination buses can be checked one by one to see if they belong to the same bus.

[0081] When the source and destination ends of a link to be identified belong to different buses, it means that the link involves cross-bus signal transmission, which meets the detection requirements, and is therefore identified as the target link. If they belong to the same bus, it means that the link does not need to be included in the cross-bus detection range. In this case, the next route link is taken as the new link to be identified, and the above judgment process is repeated. This cycle continues until all route links have been checked, ensuring that no link is missed.

[0082] In this way, step S120 can accurately locate the target link across the bus from a massive number of routing links, clarifying the target for subsequent targeted detection. This not only ensures the accuracy of the detection range but also avoids invalid processing of links on the same bus, thus improving the efficiency of the overall detection process.

[0083] In one implementation, after designating the link to be identified as the target link, the method further includes:

[0084] Write the source and destination ends of the target link into the target file;

[0085] Before generating a test signal at the source end of the simulated target link and sending the test signal through the bus to which the source end of the target link belongs, the process also includes:

[0086] Obtain the target file and read the source and destination ends of the target link from the target file.

[0087] In this implementation, after the target links are selected, the target link information can be stored in a structured manner, writing the source and destination information of each identified target link into a target file. This operation solidifies the critical link information across the bus in file form, which not only achieves clear archiving of the detection objects, but also provides a traceable data source for subsequent detection steps, avoiding the risk of link information being lost or confused during process flow.

[0088] Furthermore, before entering the test signal simulation and transmission stage, the stored source and destination information can be read from the target file. By retrieving the structured data archived in the early stage, it can be ensured that the link targeted by the subsequent detection is completely consistent with the selected target link. This not only makes the detection process more standardized, but also allows for the rapid identification of the detection object by directly calling the target file in scenarios of multi-link parallel detection or repeated detection. This reduces the redundancy of repeated information processing, improves the overall detection efficiency, and ensures the accuracy and consistency of the link information.

[0089] Step S130 includes: generating a test signal at the source end of the simulated target link, and sending the test signal through the bus to which the source end of the target link belongs, including:

[0090] Each target link is treated as a link to be tested in turn. The test signal is generated by simulating the source end of the link to be tested, and the test signal is sent through the bus to which the source end of the link to be tested belongs.

[0091] If they are the same, the route detection result of the target link is determined to be normal; if they are different, the route detection result of the target link is determined to be a route failure. This also includes:

[0092] The next target link is then used as the new link to be tested. The process of generating a test signal at the source end of the simulated link to be tested is repeated until no next target link exists.

[0093] In this implementation, a polling mechanism is used to process each target link sequentially when simulating and transmitting test signals. Specifically, each selected target link can be used as a link to be tested in turn. For the current link to be tested, a test signal is constructed by simulating the signal generation logic at its source end, and the test signal is sent out using the bus to which the source end belongs.

[0094] After completing the signal transmission and result determination (whether it is determined to be normal or routing failure) of the current target link, the next target link can be automatically selected as the new target link to be tested, and the operation of generating and sending test signals at the simulated source end can be performed again. This loop process will continue until all target links have been tested, ensuring that each cross-bus target link can be tested independently and completely.

[0095] This ensures comprehensive coverage of all target links while avoiding signal interference between different links during single link detection, so that the detection results of each link can accurately reflect its actual communication status.

[0096] In one implementation, determining that the routing detection result of the target link is normal includes:

[0097] After stopping the transmission of test signals, determine whether the signal to be detected received at the destination end of the target link is the same as the preset timeout value. If it is the same as the preset timeout value, the routing detection result of the target link is determined to be normal.

[0098] If the result is different from the preset timeout value, the route detection result of the target link is determined to be a timeout replacement failure.

[0099] In this implementation, when determining the routing detection result of the target link, not only is the accuracy of normal signal transmission considered, but the link's ability to handle anomalies after signal interruption can also be further verified.

[0100] Specifically, when the signal to be detected is confirmed to be the same as the test signal through preliminary comparison, it is not directly determined that the link is normal. Instead, verification of the timeout mechanism is added on this basis:

[0101] After stopping the transmission of test signals, the system observes whether the signal received at the destination end of the target link automatically switches to the preset timeout value. If the destination signal matches the preset timeout value, it indicates that the link can not only transmit signals normally, but also trigger the timeout handling mechanism as expected when the signal is interrupted. Therefore, the routing detection result of the target link is judged to be normal. Conversely, if the destination signal does not switch to the preset timeout value after stopping transmission, it indicates that the timeout replacement function of the link is abnormal, and the timeout replacement is judged to have failed.

[0102] This approach enables the assessment of link reliability from two dimensions: normal transmission and abnormal interruption handling. This makes the detection results more consistent with the complex communication conditions that vehicles may encounter in actual operation, further enhancing the comprehensiveness and rigor of cross-bus routing detection.

[0103] Example 2

[0104] In this embodiment, the cross-bus routing detection process can be divided into a link extraction subsystem and a routing detection subsystem. This architecture not only meets the actual needs of the vehicle bus system, but also improves the scalability of the system through modular design (such as the extraction logic or detection algorithm can be optimized separately in the future), and finally achieves accurate, efficient and comprehensive detection of cross-bus routing communication.

[0105] On the one hand, embodiments of this application also provide a cross-bus route detection method, applied to a link extraction subsystem, such as... Figure 2 As shown, it includes:

[0106] Step 210: Obtain the source and destination ends of each routing link in the vehicle;

[0107] Step 220: Determine the routing links where the source and destination ends do not belong to the same bus, and designate them as target links;

[0108] Step 230: Send the source and destination ends of the target link to the routing detection subsystem so that the routing detection subsystem can perform routing detection on the target link.

[0109] In other words, the link extraction subsystem can accurately filter out the cross-bus target links that need to be detected from the complex routing links of the vehicle, and pass the key information to the routing detection subsystem.

[0110] First, a complete link information database is established by acquiring the source and destination information of all routing links in the vehicle (e.g., extracted from the communication matrix) to ensure coverage of all possible signal transmission paths in the vehicle. Next, each link in the link information database is filtered to identify those links whose source and destination belong to different buses as target links. Finally, the source and destination information of the selected target links is sent to the routing detection subsystem to provide a basis for detection.

[0111] In this way, by focusing on link selection through the link extraction subsystem, the detection process is prevented from being interfered with by redundant information, ensuring that subsequent detection is only for cross-bus scenarios that truly need verification, thus improving detection efficiency from the source.

[0112] On the other hand, embodiments of this application also provide a cross-bus route detection method, applied to a route detection subsystem, such as... Figure 3 As shown, it includes:

[0113] Step 310: Obtain the source and destination ends of at least one target link in the vehicle, wherein the source and destination ends of the target link do not belong to the same bus;

[0114] Step 320: Simulate the source end of the target link to generate a test signal, and send the test signal through the bus to which the source end of the target link belongs;

[0115] Step 330: Determine whether the signal to be detected received at the destination end of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is determined to be normal. If they are different, the routing detection result of the target link is determined to be a routing failure.

[0116] In other words, the route detection subsystem focuses on the actual verification of cross-bus communication functions based on the target link information provided by the link extraction subsystem.

[0117] First, the target link information transmitted by the receiving link extraction subsystem is received to identify the target links that need to be tested. Next, for each target link, a test signal is generated by simulating the source node and sent using the bus to which the source node belongs. Finally, the link status is determined by comparing the signal received at the destination with the sent test signal. If they are consistent, it indicates that the target link can reliably transmit signals and is considered normal. If they are inconsistent, it indicates that the target link has a transmission fault and is considered a routing failure.

[0118] In this way, by focusing on functional verification through the routing detection subsystem, resources can be concentrated on detecting communication across bus links, thereby improving the reliability of the detection results.

[0119] Example 3

[0120] To facilitate understanding, the cross-bus route detection method provided in this application is described below through several specific implementation methods, such as... Figure 4 The diagram shown is a flowchart of this embodiment, which specifically includes the following steps:

[0121] Import the communication matrix into the link extraction subsystem;

[0122] Perform round-robin processing on each routing link in the communication matrix:

[0123] Determine whether the destination and source of the current routing link are on the same bus. If they are, extract the destination and source of the current routing link and write them to "Cross-bus Routing Link.excel" (target file), and then proceed to the next step. If not, proceed directly to the next step.

[0124] Determine if the current routing link is the last routing link in the communication matrix. If it is, import the "Cross-bus Routing Link.excel" file into the routing detection subsystem. If not, continue polling the routing links in the communication matrix.

[0125] The route detection subsystem performs a round-robin process on each cross-bus route link (target link) in "Cross-bus Route Links.excel":

[0126] Simulate and send test signals on the bus at the source end of the current target link using bus tools, and attempt to receive signals on the bus at the destination end of the same target link.

[0127] Determine whether the value of the signal to be detected received at the destination is equal to the value of the test signal simulated and sent by the source.

[0128] If the detected signal value is equal to the test signal value, record that the cross-bus routing of the current target link is normal, and stop sending the test signal on the bus where the source is located through the bus tool. After stopping the transmission, determine whether the detected signal value received by the destination is replaced with the preset timeout value. If yes, record that the cross-bus routing timeout replacement of the current target link is normal. If no, record that the cross-bus routing timeout replacement of the current target link fails.

[0129] If not (the value of the signal to be detected is not equal to the value of the test signal), record that the current target link cross-bus routing has failed;

[0130] Determine whether all target links have been detected. If yes, output the detection result; otherwise, continue polling the target links.

[0131] Example 4

[0132] This application embodiment also provides a cross-bus routing detection device 40, such as Figure 5 As shown, it includes:

[0133] The link extraction subsystem 401 is used to obtain the source and destination ends of each routing link in the vehicle; and to determine the routing links whose source and destination ends do not belong to the same bus, as the target links.

[0134] The routing detection subsystem 402 is used to simulate the source end of the target link to generate a test signal and send the test signal through the bus to which the source end of the target link belongs; determine whether the signal to be detected received by the destination end of the target link is the same as the test signal. If they are the same, the routing detection result of the target link is determined to be normal. If they are different, the routing detection result of the target link is determined to be routing failure.

[0135] This application also provides an electronic device 90, please refer to... Figure 6 It includes a processor 910 and a memory 920, wherein the memory 910 is used to store computer programs; the processor 920 is used to execute the programs stored in the memory 910 to implement the cross-bus routing detection method described in any embodiment of this application.

[0136] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the cross-bus routing detection method described in any embodiment of this application.

[0137] In this application, "multiple" refers to two or more.

[0138] In this application, unless otherwise expressly defined, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0139] The terms “first,” “second,” “third,” “fourth,” etc., in this application (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0140] In this application, the term "and / or" merely describes the relationship between associated objects, indicating that three relationships can exist. For example, cross-bus routing detection and / or B can represent: cross-bus routing detection alone, cross-bus routing detection and B simultaneously, or B alone. Additionally, in this application, the character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0141] Unless otherwise specified, all steps in this application may be performed sequentially or randomly. For example, the method includes steps cross-bus routing detection and B, indicating that the method may include steps cross-bus routing detection and B performed sequentially, or it may include steps B and cross-bus routing detection performed sequentially. For example, the method may also include step C, indicating that step C may be added to the method in any order. For example, the method may include steps cross-bus routing detection, B, and C, or it may include steps cross-bus routing detection, C, and B, or it may include steps C, cross-bus routing detection, and B, etc.

[0142] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A cross-bus routing detection method, characterized by, The method comprises the following steps: acquiring the source end and the destination end of each routing link in a vehicle; determining the routing link corresponding to the source end and the destination end not belonging to the same bus as a target link; generating a test signal at the source end of the target link and sending the test signal through the bus to which the source end of the target link belongs; judging whether the test signal received by the destination end of the target link is the same as the test signal, if yes, determining that the routing detection result of the target link is normal, if not, determining that the routing detection result of the target link is routing failure.

2. The method of claim 1, wherein, The acquisition of the source end and the destination end of each routing link in a vehicle comprises: acquiring a communication matrix of the vehicle, wherein the source end and the destination end of each routing link are included in the communication matrix.

3. The method of claim 1, wherein, The determination of the routing link corresponding to the source end and the destination end not belonging to the same bus as a target link comprises: judging whether the source end and the destination end of each routing link belong to the same bus; if not, determining the routing link as a target link; if yes, taking the next routing link as a new to-be-identified link and returning to the step of judging whether the source end and the destination end of the to-be-identified link belong to the same bus until there is no next routing link.

4. The method of claim 3, wherein, After the determination of the routing link corresponding to the source end and the destination end not belonging to the same bus as a target link, the method further comprises: writing the source end and the destination end of the target link into a target file. Before the generation of a test signal at the source end of the target link and the sending of the test signal through the bus to which the source end of the target link belongs, the method further comprises: acquiring the target file and reading the source end and the destination end of the target link from the target file.

5. The method of claim 1, wherein, The generation of a test signal at the source end of the target link and the sending of the test signal through the bus to which the source end of the target link belongs comprises: taking each target link as a to-be-detected link in turn, generating a test signal at the source end of the to-be-detected link and sending the test signal through the bus to which the source end of the to-be-detected link belongs. After the judgment of whether the test signal received by the destination end of the target link is the same as the test signal, if yes, determining that the routing detection result of the target link is normal, if not, determining that the routing detection result of the target link is routing failure, the method further comprises: taking the next target link as a new to-be-detected link and returning to the step of generating a test signal at the source end of the to-be-detected link until there is no next target link.

6. The method according to claim 1 or 5, characterized in that, The determination of the routing detection result of the target link as normal comprises: after the stop of the sending of the test signal, judging whether the test signal received by the destination end of the target link is the same as a preset timeout value, if yes, determining that the routing detection result of the target link is normal; if not, determining that the routing detection result of the target link is timeout replacement failure.

7. A cross bus routing detection method, characterized by, The method is applied to a link extraction subsystem and comprises the following steps: acquiring the source end and the destination end of each routing link in a vehicle; determining the routing link corresponding to the source end and the destination end not belonging to the same bus as a target link; sending the source end and the destination end of the target link to a route detection subsystem to make the route detection subsystem perform route detection on the target link.

8. A cross bus routing detection method, characterized by, Applied to a route detection subsystem, comprising: obtaining the source end and the destination end of at least one target link in a vehicle, the source end and the destination end corresponding to the target link not belonging to the same bus; generating a test signal by simulating the source end of the target link and sending the test signal through the bus to which the source end of the target link belongs; judging whether the test signal received by the destination end of the target link is the same as the test signal, if yes, determining that the route detection result of the target link is normal, if not, determining that the route detection result of the target link is route failure.

9. A cross bus routing detection apparatus, characterized by, Comprising: a link extraction subsystem for obtaining the source end and the destination end of each route link in a vehicle; determining the route link corresponding to the source end and the destination end not belonging to the same bus as a target link; a route detection subsystem for generating a test signal by simulating the source end of the target link and sending the test signal through the bus to which the source end of the target link belongs; judging whether the test signal received by the destination end of the target link is the same as the test signal, if yes, determining that the route detection result of the target link is normal, if not, determining that the route detection result of the target link is route failure.

10. An electronic device, comprising: comprising a processor and a memory, wherein: the memory is used for storing computer programs; the processor is used for executing the programs stored on the memory to realize the method of any one of claims 1-6 or 7 or 8.

Images