ADAS rendering debugging signal sending method and device, equipment and medium

Abstract

The invention provides an ADAS rendering debugging signal sending method and device, equipment and a medium. The method comprises the steps that a pre-configured debugging signal configuration table is acquired; the debugging signal configuration table is used for storing ADAS rendering debugging signals and corresponding signal sending rules; reading first debugging signal configuration data which are not sent in the debugging signal configuration table; the debugging signal configuration data comprises a signal sending rule and at least one ADAS rendering debugging signal; the signal sending rule is used for limiting the sending times and the sending frequency of the ADAS rendering debugging signal; according to a signal sending rule, sending the ADAS rendering debugging signal to the ADAS; and jumping to read the first debugging signal configuration data which is not sent in the debugging signal configuration table. According to the application, the corresponding ADAS rendering debugging signal can be automatically sent based on the signal sending rule in the debugging signal configuration table, errors of the rendering debugging signal are avoided, and the rendering debugging efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle testing technology, and in particular to a method, device, equipment and medium for sending an ADAS rendering debugging signal. Background Art

[0002] ADAS rendering debugging refers to the process of debugging and optimizing the visual rendering part of the system when developing and testing the advanced driver assistance system ADAS. The traditional rendering debugging method is that the technician uses the Can tool to manually send all rendering debugging signals to ADAS. After receiving the rendering debugging signals, ADAS performs rendering to complete the debugging.

[0003] However, manually sending the rendering debugging signal increases the error rate of the rendering debugging signal and the ADAS rendering debugging efficiency is low. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide a method, device, equipment and medium for sending ADAS rendering debugging signals, which can automatically send corresponding ADAS rendering debugging signals based on the signal sending rules in the debugging signal configuration table, avoid errors in rendering debugging signals, and improve rendering debugging efficiency.

[0005] In a first aspect, an embodiment of the present application provides a method for sending an ADAS rendering debugging signal, the method comprising:

[0006] Obtain a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store ADAS rendering debugging signals and corresponding signal sending rules;

[0007] Reading the first unsent debug signal configuration data in the debug signal configuration table; the debug signal configuration data includes a signal sending rule and at least one ADAS rendering debug signal; the signal sending rule is used to limit the number of times and frequency of sending the ADAS rendering debug signal;

[0008] According to the signal sending rule, the ADAS rendering debug signal is sent to ADAS; and the process jumps to reading the first debug signal configuration data that has not been sent in the debug signal configuration table.

[0009] In a possible implementation, sending the ADAS rendering debugging signal to the ADAS according to the signal sending rule in the debugging signal configuration data includes:

[0010] If the configuration content at the first preset position in the debugging signal configuration data is the sending frequency information in the signal sending rule, the ADAS rendering debugging signal is sent to the ADAS once according to the sending frequency information.

[0011] In a possible implementation, sending the ADAS rendering debug signal to the ADAS according to the signal sending rule in the debug signal configuration data further includes:

[0012] If the configuration content at the first preset position in the debug signal configuration data is the repeated sending times information in the signal sending rules, and the configuration content at the second preset position in the debug signal configuration data is the sending frequency information in the signal sending rules, then the ADAS rendering debug signal is sent to the ADAS according to the repeated sending times information and the sending frequency information.

[0013] In a possible implementation, obtaining a preconfigured debugging signal configuration table includes:

[0014] After receiving the service binding request of ADAS rendering debugging, bind the rendering debugging service to ADAS;

[0015] After the binding is completed, the ADAS registration is completed based on the debug signal type sent by ADAS;

[0016] Gets a preconfigured debug signal configuration table.

[0017] In a possible implementation, the ADAS processes the ADAS rendering debugging signal, and sends the processed ADAS rendering debugging signal to the visualization module for rendering.

[0018] In a possible implementation manner, reading the first unsent debugging signal configuration data in the debugging signal configuration table includes:

[0019] Read the first debug signal configuration data that is not sent in the debug signal configuration table and corresponds to the debug signal type registered by the ADAS.

[0020] In a second aspect, an embodiment of the present application further provides a device for sending an ADAS rendering debugging signal, the device comprising:

[0021] An acquisition module is used to acquire a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store ADAS rendering debugging signals and corresponding signal sending rules;

[0022] A reading module is used to read the first unsent debugging signal configuration data in the debugging signal configuration table; the debugging signal configuration data includes a signal sending rule and at least one ADAS rendering debugging signal; the signal sending rule is used to limit the number of times and frequency of sending the ADAS rendering debugging signal;

[0023] The sending jump module is used to send the ADAS rendering debugging signal to the ADAS according to the signal sending rule; and jump to read the first debugging signal configuration data that has not been sent in the debugging signal configuration table.

[0024] In a possible implementation, the sending jump module is specifically configured to send an ADAS rendering debugging signal to the ADAS once according to the sending frequency information if the configuration content at the first preset position in the debugging signal configuration data is the sending frequency information in the signal sending rule.

[0025] In one possible implementation, a sending jump module is specifically used to send an ADAS rendering debug signal to ADAS according to the repeated sending number information and the sending frequency information if the configuration content at the first preset position in the debug signal configuration data is the repeated sending number information in the signal sending rule, and the configuration content at the second preset position in the debug signal configuration data is the sending frequency information in the signal sending rule.

[0026] In a possible implementation, the acquisition module is specifically used to bind the rendering debugging service to the ADAS after receiving a service binding request for ADAS rendering debugging; after the binding is completed, complete the registration of the ADAS based on the debugging signal type sent by the ADAS; and obtain a pre-configured debugging signal configuration table.

[0027] In a possible implementation, the ADAS processes the ADAS rendering debugging signal, and sends the processed ADAS rendering debugging signal to the visualization module for rendering.

[0028] In a possible implementation, the reading module is specifically configured to read the first debugging signal configuration data that is not sent in the debugging signal configuration table and corresponds to the debugging signal type registered by the ADAS.

[0029] In a third aspect, an embodiment of the present application further provides an electronic device comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to perform the steps of the method for sending an ADAS rendering debug signal as described in any one of the first aspects.

[0030] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for sending an ADAS rendering debugging signal as described in any one of the first aspects are executed.

[0031] The embodiment of the present application provides a method, device, equipment and medium for sending an ADAS rendering debug signal, the method comprising: obtaining a pre-configured debug signal configuration table; the debug signal configuration table is used to store the ADAS rendering debug signal and the corresponding signal sending rules; reading the first unsent debug signal configuration data in the debug signal configuration table; the debug signal configuration data includes signal sending rules and at least one ADAS rendering debug signal; the signal sending rules are used to limit the number of times and frequency of sending the ADAS rendering debug signal; according to the signal sending rules, the ADAS rendering debug signal is sent to ADAS; and jumping to reading the first unsent debug signal configuration data in the debug signal configuration table. The present application can automatically send the corresponding ADAS rendering debug signal based on the signal sending rules in the debug signal configuration table, avoid errors in the rendering debug signal, and improve the efficiency of rendering debugging. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 A flowchart of a method for sending an ADAS rendering debugging signal provided in an embodiment of the present application is shown;

[0034] Figure 2 A schematic diagram of a debug signal configuration table provided in an embodiment of the present application is shown;

[0035] Figure 3 A schematic diagram of the structure of a device for sending an ADAS rendering debugging signal provided in an embodiment of the present application is shown;

[0036] Figure 4 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0037] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0038] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0039] In order to enable those skilled in the art to use the contents of this application, the following implementation is provided in conjunction with a specific application scenario, "the field of vehicle testing technology". For those skilled in the art, the general principles defined herein may be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application is mainly described around the field of vehicle testing technology, it should be understood that this is only an exemplary embodiment.

[0040] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0041] The following is a detailed description of a method for sending an ADAS rendering debugging signal provided in an embodiment of the present application.

[0042] Reference Figure 1 As shown, it is a flow chart of a method for sending an ADAS rendering debugging signal provided in an embodiment of the present application, and the specific execution process of the method is as follows:

[0043] S101, obtaining a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store ADAS rendering debugging signals and corresponding signal sending rules.

[0044] S102, reading the first unsent debugging signal configuration data in the debugging signal configuration table; the debugging signal configuration data includes a signal sending rule and at least one ADAS rendering debugging signal.

[0045] S103 . Send the ADAS rendering debugging signal to ADAS according to the signal sending rule; and jump to reading the first debugging signal configuration data that has not been sent in the debugging signal configuration table.

[0046] The embodiment of the present application provides a method for sending an ADAS rendering debug signal, the method comprising: obtaining a pre-configured debug signal configuration table; the debug signal configuration table is used to store the ADAS rendering debug signal and the corresponding signal sending rules; reading the first unsent debug signal configuration data in the debug signal configuration table; the debug signal configuration data includes signal sending rules and at least one ADAS rendering debug signal; the signal sending rules are used to limit the number of times and frequency of sending the ADAS rendering debug signal; according to the signal sending rules, the ADAS rendering debug signal is sent to ADAS; and jumping to reading the first unsent debug signal configuration data in the debug signal configuration table. The present application can automatically send the corresponding ADAS rendering debug signal based on the signal sending rules in the debug signal configuration table, avoid errors in the rendering debug signal, and improve the rendering debugging efficiency.

[0047] The following is a description of the exemplary steps of the present application embodiment:

[0048] S101, obtaining a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store ADAS rendering debugging signals and corresponding signal sending rules.

[0049] In an implementation manner of the present application, after receiving a service binding request for ADAS rendering debugging, a rendering debugging service is bound to ADAS; after the binding is completed, the registration of ADAS is completed based on the type of debugging signal sent by ADAS; and a pre-configured debugging signal configuration table is obtained.

[0050] The debugging personnel will manually configure at least one ADAS rendering debugging signal configuration data in the debugging signal configuration table of the signal service module; each debugging signal configuration data includes a signal sending rule and at least one ADAS rendering debugging signal. The signal sending rule is used to limit the sending frequency and number of times the ADAS rendering debugging signal is sent. The ADAS rendering debugging signal is a signal sent to ADAS for rendering. The ADAS rendering debugging signal includes the type of ADAS rendering debugging signal and the corresponding attribute information. The writing format of the ADAS rendering debugging signal is pre-agreed with unity so that unity can obtain the content of the ADAS rendering debugging signal.

[0051] Among them, different types of ADAS rendering debugging signals correspond to different attribute information. For example, lane line signals can include lane line color, lane line type (solid line, dotted line, etc.), distance between lane line and vehicle, lane line curvature, lane line heading angle, etc.; zebra crossing signals can include coordinates of the four corner points of the zebra crossing, etc.; lane change signals can include manual lane change or automatic lane change, lane change status (lane change in progress, lane change preparation, lane change completed, lane change failed), etc.; vehicle signals can include vehicle color, whether there is a spare tire, whether the turn signal is on, whether the brake light is on, whether the low beam is on, whether the high beam is on, etc.

[0052] Reference Figure 2 As shown, it is a schematic diagram of the debugging signal configuration table provided in an embodiment of the present application; wherein, the character string "SIGNAL" and the adjacent numbers constitute the sending frequency information in the signal sending rule; for example, SIGNAL30 means the sending frequency is once every 30 seconds. The character string "REPEAT" and the adjacent numbers constitute the repeated sending times information in the signal sending rule; for example, REPEAT50 means repeated sending 50 times. The content between the "|" and the "|" after the character string "SIGNAL" and the adjacent numbers is an ADAS rendering debugging signal. The "SIGNAL" that is in front of and closest to the ADAS rendering debugging signal or the "SIGNAL" that is in front of and closest to the ADAS rendering debugging signal and the adjacent numbers "REPEAT" and the adjacent numbers constitute the signal sending rule of the ADAS rendering debugging signal.

[0053] There are two forms of debug signal configuration data. Here, the string "REPEAT" before the string "ENDREPEAT" and the adjacent strings "REPEAT" and "ENDREPEAT" are regarded as a repeating block. The first form: the content in a repeating block, the string "REPEAT" and the string "ENDREPEAT" corresponding to the repeating block constitute a debug signal configuration data. The second form: the content that is not in the repeating block and between the string "SIGNAL" and the adjacent numbers and the "|" and "|", the string "SIGNAL" and the adjacent numbers after the string "SIGNAL constitute a debug signal configuration data.

[0054] In each ADAS rendering debugging signal, the string "msgid" is an identifier used to identify various types of ADAS rendering debugging signals; 902002, 903002, 904002, and 1101 are the identifiers of the types of ADAS rendering debugging signals (such as lane line signals, zebra crossing signals, lane change signals, and vehicle signals); the string "msgbody" is the message body, which is a JSON formatted data containing multiple key-value pairs, each of which describes an attribute information of the ADAS rendering debugging signal (such as "info_obj1ld": 1, "info_obj1Type": 49, "info_obj1DistX": 0, "info_obj1DistY": 3.5, etc.); Figure 2 The "info_obj1ld", "info_obj1Type", etc. are the English representations of the attribute information.

[0055] S102, reading the first unsent debugging signal configuration data in the debugging signal configuration table; the debugging signal configuration data includes a signal sending rule and at least one ADAS rendering debugging signal.

[0056] In an embodiment of the present application, the debug signal configuration table includes at least one debug signal configuration data. The signal sending rule is used to limit the number of times and frequency of sending the ADAS rendering debug signal; the ADAS rendering debug signal contains the specific content of the ADAS rendering. The signal sending rule may include the sending frequency information and the number of repeated sending information.

[0057] Among them, the first preset position and the second preset position in the debug signal configuration data are positions pre-set by the debug signal configuration data for configuring the signal sending rules in the debug signal configuration data; if the configuration content at the first preset position is the sending frequency information in the signal sending rules, then the debug signal configuration data only includes one ADAS rendering debug signal; if the configuration content at the first preset position is the repeated sending times information in the signal sending rules, then the debug signal configuration data may include one or more ADAS rendering debug signals.

[0058] Optionally, if the first debugging signal configuration data that is not sent in the debugging signal configuration table and corresponds to the debugging signal type registered by the ADAS is read.

[0059] In the implementation manner of the present application, the debugger may register at least one debug signal type for ADAS rendering debugging through ADAS.

[0060] S103 . Send the ADAS rendering debugging signal to ADAS according to the signal sending rule; and jump to reading the first debugging signal configuration data that has not been sent in the debugging signal configuration table.

[0061] Specifically, if the configuration content at the first preset position in the debugging signal configuration data is the sending frequency information in the signal sending rule, the ADAS rendering debugging signal is sent to the ADAS once according to the sending frequency information.

[0062] For example, the debug signal configuration data includes ADAS rendering debug signal 1, and the sending frequency information is once every 30 seconds. Then, ADAS rendering debug signal 1 is sent to ADAS rendering debug signal after 30 seconds, and execution continues to proceed after the sending is completed (i.e., jumps to read the first debug signal configuration data that has not been sent in the debug signal configuration table).

[0063] Specifically, if the configuration content at the first preset position in the debug signal configuration data is the repeated sending times information in the signal sending rules, and the configuration content at the second preset position in the debug signal configuration data is the sending frequency information in the signal sending rules, then the ADAS rendering debug signal is sent to the ADAS according to the repeated sending times information and the sending frequency information.

[0064] In the implementation manner of the present application, each ADAS rendering debugging signal corresponds to a transmission frequency information, and the repeated transmission times information of all ADAS rendering debugging signals of the debugging signal configuration data is the same.

[0065] For example, the debugging signal configuration data includes ADAS rendering debugging signal 2 and ADAS rendering debugging signal 3 in sequence. The sending frequency information of ADAS rendering debugging signal 2 is once every 50 seconds, the sending frequency information of ADAS rendering debugging signal 3 is once every 30 seconds, and the number of repeated transmissions is repeated 3 times. Then, ADAS rendering debugging signal 2 is sent to ADAS after 50 seconds; after the first sending of ADAS rendering debugging signal 2, ADAS rendering debugging signal 2 is sent to ADAS after 50 seconds; after the second sending of ADAS rendering debugging signal 2, ADAS rendering debugging signal 2 is sent to ADAS after 50 seconds. DAS rendering debug signal 2 is sent to ADAS; 30s after the third sending of ADAS rendering debug signal 2, ADAS rendering debug signal 3 is sent to ADAS; 30s after the first sending of ADAS rendering debug signal 3, ADAS rendering debug signal 3 is sent to ADAS; 30s after the second sending of ADAS rendering debug signal 3, ADAS rendering debug signal 3 is sent to ADAS; after the third sending of ADAS rendering debug signal 3, execution continues downward (i.e., jumps to reading the first debug signal configuration data that has not been sent in the debug signal configuration table).

[0066] Further, the ADAS processes the ADAS rendering debugging signal and sends the processed ADAS rendering debugging signal to the visualization module for rendering.

[0067] In the implementation manner of the present application, ADAS parses the ADAS rendering debugging signal to obtain ADAS rendering debugging data; and performs data cleaning, data packaging, data caching and other processing on the ADAS rendering debugging data. The ADAS rendering debugging data that has been verified and processed is sent to the visualization module for rendering at a regular interval. The visualization module can be included in the ADAS or outside the ADAS. The visualization module can be unity. Unity is a widely used cross-platform game development engine used to create a virtual driving environment.

[0068] The embodiment of the present application provides a method for sending an ADAS rendering debug signal, the method comprising: obtaining a pre-configured debug signal configuration table; the debug signal configuration table is used to store the ADAS rendering debug signal and the corresponding signal sending rules; reading the first unsent debug signal configuration data in the debug signal configuration table; the debug signal configuration data includes signal sending rules and at least one ADAS rendering debug signal; the signal sending rules are used to limit the number of times and frequency of sending the ADAS rendering debug signal; according to the signal sending rules, the ADAS rendering debug signal is sent to ADAS; and jumping to reading the first unsent debug signal configuration data in the debug signal configuration table. The present application can automatically send the corresponding ADAS rendering debug signal based on the signal sending rules in the debug signal configuration table, avoid errors in the rendering debug signal, and improve the rendering debugging efficiency.

[0069] Based on the same inventive concept, an ADAS rendering debug signal sending device corresponding to the ADAS rendering debug signal sending method is also provided in an embodiment of the present application. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned ADAS rendering debug signal sending method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0070] Reference Figure 3 , which is a schematic diagram of a device for sending an ADAS rendering debugging signal provided in an embodiment of the present application, wherein the device for sending an ADAS rendering debugging signal includes:

[0071] The acquisition module 301 is used to acquire a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store the ADAS rendering debugging signal and the corresponding signal sending rules;

[0072] A reading module 302 is used to read the first unsent debugging signal configuration data in the debugging signal configuration table; the debugging signal configuration data includes a signal sending rule and at least one ADAS rendering debugging signal; the signal sending rule is used to limit the number of times and frequency of sending the ADAS rendering debugging signal;

[0073] The sending jump module 303 is used to send the ADAS rendering debugging signal to the ADAS according to the signal sending rule; and jump to read the first debugging signal configuration data that has not been sent in the debugging signal configuration table.

[0074] In a possible implementation, the sending jump module 303 is specifically configured to send an ADAS rendering debugging signal to the ADAS once according to the sending frequency information if the configuration content at the first preset position in the debugging signal configuration data is the sending frequency information in the signal sending rule.

[0075] In one possible implementation, the sending jump module 303 is specifically used to send an ADAS rendering debug signal to ADAS according to the repeated sending number information and the sending frequency information if the configuration content at the first preset position in the debug signal configuration data is the repeated sending number information in the signal sending rule, and the configuration content at the second preset position in the debug signal configuration data is the sending frequency information in the signal sending rule.

[0076] In a possible implementation, the acquisition module 301 is specifically used to bind a rendering debugging service to the ADAS after receiving a service binding request for ADAS rendering debugging; after the binding is completed, the registration of the ADAS is completed based on the debugging signal type sent by the ADAS; and a pre-configured debugging signal configuration table is obtained.

[0077] In a possible implementation, the ADAS processes the ADAS rendering debugging signal, and sends the processed ADAS rendering debugging signal to the visualization module for rendering.

[0078] In a possible implementation, the reading module 302 is specifically configured to read the first debugging signal configuration data that is not sent in the debugging signal configuration table and corresponds to the debugging signal type registered by the ADAS.

[0079] The embodiment of the present application provides a sending device for ADAS rendering debug signal, the method comprising: an acquisition module 301, for obtaining a pre-configured debug signal configuration table; the debug signal configuration table is used to store ADAS rendering debug signals and corresponding signal sending rules; a reading module 302, for reading the first unsent debug signal configuration data in the debug signal configuration table; the debug signal configuration data includes signal sending rules and at least one ADAS rendering debug signal; the signal sending rules are used to limit the number of times and frequency of sending the ADAS rendering debug signal; a sending jump module 303, for sending the ADAS rendering debug signal to ADAS according to the signal sending rules; and jumping to reading the first unsent debug signal configuration data in the debug signal configuration table. The present application can automatically send the corresponding ADAS rendering debug signal based on the signal sending rules in the debug signal configuration table, avoid errors in the rendering debug signal, and improve the rendering debugging efficiency.

[0080] like Figure 4 As shown, an electronic device 400 provided in an embodiment of the present application includes: a processor 401, a memory 402 and a bus, wherein the memory 402 stores machine-readable instructions executable by the processor 401. When the electronic device is running, the processor 401 communicates with the memory 402 through the bus, and the processor 401 executes the machine-readable instructions to perform the steps of the method for sending the ADAS rendering debug signal as described above.

[0081] Specifically, the memory 402 and the processor 401 can be general-purpose memories and processors, which are not specifically limited here. When the processor 401 runs the computer program stored in the memory 402, the method for sending the ADAS rendering debugging signal can be executed.

[0082] Corresponding to the above-mentioned method for sending ADAS rendering debugging signals, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned method for sending ADAS rendering debugging signals are executed.

[0083] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0084] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0085] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0086] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the information processing method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0087] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for sending an ADAS rendering debugging signal, characterized in that: The method comprises: Obtain a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store ADAS rendering debugging signals and corresponding signal sending rules; Reading the first unsent debug signal configuration data in the debug signal configuration table; the debug signal configuration data includes a signal sending rule and at least one ADAS rendering debug signal; the signal sending rule is used to limit the number of times and frequency of sending the ADAS rendering debug signal; According to the signal sending rule, the ADAS rendering debugging signal is sent to ADAS; and the method jumps to reading the first debugging signal configuration data that has not been sent in the debugging signal configuration table.

2. The method for sending an ADAS rendering debugging signal according to claim 1, characterized in that: The step of sending the ADAS rendering debugging signal to ADAS according to the signal sending rule in the debugging signal configuration data includes: If the configuration content at the first preset position in the debugging signal configuration data is the sending frequency information in the signal sending rule, the ADAS rendering debugging signal is sent to the ADAS once according to the sending frequency information.

3. The method for sending an ADAS rendering debugging signal according to claim 2, characterized in that: The step of sending the ADAS rendering debugging signal to ADAS according to the signal sending rule in the debugging signal configuration data further includes: If the configuration content at the first preset position in the debug signal configuration data is the repeated sending times information in the signal sending rules, and the configuration content at the second preset position in the debug signal configuration data is the sending frequency information in the signal sending rules, then the ADAS rendering debug signal is sent to the ADAS according to the repeated sending times information and the sending frequency information.

4. The method for sending an ADAS rendering debugging signal according to any one of claims 1 to 3, characterized in that: The step of obtaining a pre-configured debugging signal configuration table includes: After receiving a service binding request for ADAS rendering debugging, binding a rendering debugging service for the ADAS; After the binding is completed, the registration of the ADAS is completed based on the type of the debugging signal sent by the ADAS; Gets a preconfigured debug signal configuration table.

5. The method for sending an ADAS rendering debugging signal according to claim 4, characterized in that: The ADAS processes the ADAS rendering debugging signal, and sends the processed ADAS rendering debugging signal to a visualization module for rendering.

6. The method for sending an ADAS rendering debugging signal according to claim 1, characterized in that: The step of reading the first unsent debugging signal configuration data in the debugging signal configuration table includes: The first debugging signal configuration data which is not sent in the debugging signal configuration table and corresponds to the debugging signal type registered by the ADAS is read.

7. A device for sending ADAS rendering debugging signals, characterized in that: The device comprises: An acquisition module is used to acquire a pre-configured debugging signal configuration table; the debugging signal configuration table is used to store ADAS rendering debugging signals and corresponding signal sending rules; A reading module, used for reading the first unsent debugging signal configuration data in the debugging signal configuration table; the debugging signal configuration data includes a signal sending rule and at least one ADAS rendering debugging signal; the signal sending rule is used to limit the number of times and frequency of sending the ADAS rendering debugging signal; The sending jump module is used to send the ADAS rendering debugging signal to the ADAS according to the signal sending rule; and jump to the reading of the first debugging signal configuration data that has not been sent in the debugging signal configuration table.

8. The device for sending ADAS rendering debugging signals according to claim 7, characterized in that: The sending jump module is specifically used for: If the configuration content at the first preset position in the debugging signal configuration data is the sending frequency information in the signal sending rule, the ADAS rendering debugging signal is sent to the ADAS once according to the sending frequency information.

9. An electronic device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to perform the steps of the method for sending an ADAS rendering debugging signal as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for sending an ADAS rendering debugging signal according to any one of claims 1 to 6 are executed.

Images