Cross-domain registration mechanism full-stack deployment method, system and device and storage medium

Abstract

The invention provides a cross-domain registration full-stack deployment method, system and device and a storage medium, the cross-domain registration full-stack deployment method comprises the following steps: obtaining domain control board hardware parameters, and matching hardware corresponding to the hardware parameters; registering the hardware parameters and the hardware functions in a hardware library to obtain hardware information and hardware function information; the full-stack deployment system distributes and accesses function modules in the system to a domain control board through hardware information and hardware function information; and permutation and combination are carried out on the function modules accessed to the domain control board, and a program is operated according to the combined function modules. Through the full-stack deployment of the cross-domain registration mechanism, the scheme can be quickly deployed and transplanted in different domain control boards, hardware resources are fully utilized, and reasonable scheduling is performed, so that the resource utilization rate and scheme adaptation of the whole domain control board are improved, and the adaptation capability of the intelligent driving scheme is further improved.

Description

Technical Field

[0001] The present application relates to the field of autonomous driving technology, and in particular to a full-stack deployment method, system, device and storage medium for cross-domain registration. Background Art

[0002] Currently in the field of autonomous driving, domain control board resources are the core computing units in the field of autonomous driving, responsible for the core computing tasks of machine perception such as visual perception, laser, and ultrasound. The domain control boards provided by different manufacturers lack unified standards in computing speed, computing volume, and modular hardware support. Different manufacturers' domain control boards require a lot of time to evaluate and transplant solutions, adapt processes, reschedule hardware resources, etc., which affects the rapid iteration and adaptation of intelligent driving solutions.

[0003] Therefore, how to efficiently deploy intelligent driving solutions on multiple platforms, utilize as many hardware resources as possible, and adapt to better hardware features is a problem that needs to be solved in this field. Summary of the invention

[0004] In view of this, the embodiments of the present application are committed to providing a full-stack deployment method, system, device and storage medium for cross-domain registration, which is used to solve the problem that intelligent driving solutions cannot be quickly deployed on multiple platforms and cannot utilize more hardware resources and adapt to better hardware characteristics.

[0005] According to a first aspect of the present invention, the present invention provides a full-stack deployment method for cross-domain registration, characterized in that it includes:

[0006] Obtaining the domain control board hardware parameters and matching the hardware corresponding to the hardware parameters;

[0007] Registering the hardware parameters and the hardware functions into a hardware library to obtain the hardware information and the hardware function information;

[0008] The full-stack deployment system allocates and connects the functional modules in the system to the domain control board through the hardware information and the hardware function information;

[0009] The functional modules connected to the domain control board are arranged and combined, and a program is run according to the combined functional modules.

[0010] Preferably, the acquiring of the domain control board hardware parameters and matching of the hardware corresponding to the hardware parameters includes:

[0011] Determine whether there is hardware corresponding to the hardware parameters in the hardware library;

[0012] When hardware corresponding to the hardware parameters exists in the hardware library, verifying whether the hardware functions are complete;

[0013] When the hardware corresponding to the hardware parameter does not exist in the hardware library, hardware is acquired and updated to the hardware library.

[0014] Preferably, the verifying whether the hardware function is complete includes:

[0015] When each hardware function is complete, the functional module is connected;

[0016] When at least one hardware function is incomplete, verification failure information is recorded in the log module.

[0017] Preferably, the full-stack deployment system connects the functional modules in the system to the domain control board through the hardware information and the hardware function information, including:

[0018] Acquire a functional module corresponding to the hardware information through the hardware information;

[0019] The functions of the functional modules are allocated and connected to the domain control board according to the hardware function information.

[0020] Preferably, the acquiring a functional module corresponding to the hardware information through the hardware information includes:

[0021] Verify whether the functions of each functional module are complete;

[0022] When the functions of each of the functional modules are complete, each of the functional modules is connected to form a deployment link, and the deployment link is verified;

[0023] When the function of at least one of the functional modules is incomplete, the incomplete functional module is reacquired.

[0024] Preferably, the deployment link is verified, including:

[0025] Verify the deployment link through the ROS environment, and when the deployment link verification succeeds, allocate the functions of the functional module and connect them to the domain control board;

[0026] When the deployment link verification fails, the verification failure information is recorded in the log module.

[0027] Preferably, the allocating the functions of the functional modules according to the hardware function information and connecting them to the domain control board includes:

[0028] When the access is successful, the functional modules are arranged and combined, and the program is run according to the combined functional modules;

[0029] When access fails, the access failure information is recorded in the log module.

[0030] According to a second aspect of the present invention, a full-stack deployment system for cross-domain registration is also provided, including:

[0031] An acquisition module is used to acquire the hardware parameters of the domain control board and match the hardware corresponding to the hardware parameters;

[0032] A registration module, used to register the hardware parameters and the hardware functions into a hardware library, and obtain the hardware information and the hardware function information;

[0033] An access module, used for the full-stack deployment system to allocate and access the functional modules in the system to the domain control board through the hardware information and the hardware function information;

[0034] The running module is used to arrange and combine the functional modules connected to the domain control board, and run the program according to the combined functional modules.

[0035] According to a third aspect of the present invention, an electronic device is also provided, comprising a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the full-stack deployment method for cross-domain registration.

[0036] According to a fourth aspect of the present invention, a computer-readable storage medium is also provided, wherein the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the full-stack deployment method for cross-domain registration.

[0037] The effects provided in the content of the invention are only the effects of the embodiments, not all the effects of the invention. One of the above technical solutions has the following advantages or beneficial effects:

[0038] According to the first aspect of the present invention, the present invention can ensure the compatibility of the hardware and domain control boards used in the deployment system by acquiring and matching hardware parameters. The registration of hardware parameters and functions ensures that the system can acquire and update hardware information in real time and maintain the integrity and accuracy of the hardware library. At the same time, the allocation and access process of functional modules is automated, which reduces human operational errors and improves the efficiency and stability of the system. At the same time, through the full-stack deployment of the cross-domain registration mechanism, the solution can be quickly deployed and transplanted on different domain control boards, making full use of hardware resources and performing reasonable scheduling, thereby improving the overall domain control board resource utilization and solution adaptation, and further improving the adaptability of the intelligent driving solution. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic flow chart of a full-stack deployment method for cross-domain registration according to an embodiment of the present invention is shown;

[0040] Figure 2 The present invention shows Figure 1 A schematic flow chart of the hardware matching method in step S100;

[0041] Figure 3 The present invention shows Figure 2 A schematic flowchart of verifying whether the hardware functions are complete in step S120;

[0042] Figure 4 The present invention shows Figure 1 A schematic flow chart of the method for connecting the functional module to the domain control board in step S300;

[0043] Figure 5 The present invention shows Figure 4 A schematic flow chart of the method for obtaining functional modules in step S310;

[0044] Figure 6 A full-stack deployment operation flow chart of cross-domain registration according to an embodiment of the present invention is shown;

[0045] Figure 7 A schematic diagram of a full-stack deployment module for cross-domain registration according to an embodiment of the present invention is shown;

[0046] Figure 8 A schematic flow chart of a full-stack deployment system for cross-domain registration according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0047] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below in conjunction with the accompanying drawings. It is to be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only some structures related to the present application are shown in the accompanying drawings, rather than all structures. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0048] The terms "including" and "having" and any variations thereof in this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0049] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0050] This patent is mainly aimed at full-link decoupling of the intelligent driving solution on multiple domain control platforms, abstracting the respective computing modules, verification modules, time modules, memory modules, hardware modules, etc., and adopting a unified registration and verification mechanism to quickly verify and iterate the solution transplantation and deployment.

[0051] Figure 1 A schematic flow chart of a full-stack deployment method for cross-domain registration according to an embodiment of the present invention is shown. Figure 1 As shown, the present invention provides a full-stack deployment method for cross-domain registration, including:

[0052] Step S100, obtaining the domain control board hardware parameters, and matching the hardware corresponding to the hardware parameters;

[0053] Step S200, registering hardware parameters and hardware functions into a hardware library to obtain hardware information and hardware function information;

[0054] Step S300, the full-stack deployment system allocates and connects the functional modules in the system to the domain control board through the hardware information and hardware function information;

[0055] Step S400, arranging and combining the functional modules connected to the domain control board, and running the program according to the combined functional modules.

[0056] By obtaining and matching hardware parameters, the compatibility of the hardware and domain control boards used in the deployment system can be ensured. The registration of hardware parameters and functions ensures that the system can obtain and update hardware information in real time and maintain the integrity and accuracy of the hardware library. At the same time, the allocation and access process of functional modules is automated, which reduces human operation errors and improves the efficiency and stability of the system. At the same time, through the full-stack deployment of the cross-domain registration mechanism, the solution can be quickly deployed and transplanted on different domain control boards, making full use of hardware resources and performing reasonable scheduling, thereby improving the overall domain control board resource utilization and solution adaptation, and further improving the adaptability of the intelligent driving solution.

[0057] Figure 2 The present invention shows Figure 1 A schematic flow chart of the hardware matching method in step S100 is shown in FIG. Figure 2As shown, in step S100, the hardware parameters of the domain control board are obtained, and the hardware corresponding to the hardware parameters is matched, including:

[0058] Step S110, determining whether there is hardware corresponding to the hardware parameters in the hardware library;

[0059] Step S120, when there is hardware corresponding to the hardware parameters in the hardware library, verify whether the hardware functions are complete;

[0060] Step S130: when the hardware corresponding to the hardware parameter does not exist in the hardware library, the hardware is acquired and updated to the hardware library.

[0061] In this step, by determining whether there are matching hardware parameters in the hardware library, the system ensures that the hardware resources are fully understood before deployment. Verifying the integrity of hardware functions avoids incomplete or faulty hardware from being connected to the system, improving the reliability and stability of system operation. If the required hardware does not exist in the hardware library, it can be updated in a timely manner to ensure the timeliness and integrity of the hardware library information.

[0062] Figure 3 The present invention shows Figure 2 A schematic flow chart of verifying whether the hardware function is complete in step S120, as shown in FIG. Figure 3 As shown, in step S120, verifying whether the hardware function is complete includes:

[0063] Step S121, when each hardware function is complete, access the functional module;

[0064] Step S122: When at least one hardware function is incomplete, verification failure information is recorded in a log module.

[0065] In this step, the verification of hardware functional integrity ensures that each hardware component in the system has its proper function, thereby avoiding system function loss or operation errors due to hardware problems. If the verification fails, the system can record logs in time to facilitate problem tracking and resolution, improving the maintainability and traceability of the system.

[0066] Figure 4 The present invention shows Figure 1 A schematic flow chart of the method for connecting the functional module to the domain control board in step S300 is shown in FIG. Figure 4 As shown, in step S300, the full-stack deployment system connects the functional modules in the system to the domain control board through hardware information and hardware function information, including:

[0067] Step S310, obtaining a functional module corresponding to the hardware information through the hardware information;

[0068] Step S320: distribute the functions of the functional modules according to the hardware function information and connect them to the domain control board.

[0069] In this step, the function modules are automatically acquired and allocated through hardware information, making the access process of the function modules more efficient and intelligent. Function allocation is performed according to the hardware function information, ensuring that each function module can fully utilize the hardware resources, improving the utilization rate of system resources and the operating efficiency of the function modules.

[0070] Figure 5 The present invention shows Figure 4 A schematic flow chart of the method for obtaining the functional module in step S310 is shown in FIG. Figure 5 As shown, in step S310, the functional module corresponding to the hardware information is obtained through the hardware information, including:

[0071] Step S311, verifying whether the function of each functional module is complete;

[0072] Step S312: When the functions of each functional module are complete, each functional module is connected to form a deployment link, and the deployment link is verified;

[0073] Step S313: when the function of at least one functional module is incomplete, the incomplete functional module is reacquired.

[0074] In this step, the function of the functional module is verified before access, ensuring the integrity of the module, thereby ensuring that the system will not have problems due to module defects during execution. The formation and verification of the deployment link further ensures the overall operation logic and functional consistency of the system, preventing system function failures due to link errors.

[0075] In step S312, the link is deployed for verification, including:

[0076] The deployment link is verified through the ROS environment (Robot Operating System). When the deployment link verification is successful, the functions of the functional modules are allocated and connected to the domain control board.

[0077] When the deployment link verification fails, the verification failure information is recorded in the log module.

[0078] In this step, the introduction of the ROS environment provides a standardized verification platform for the verification of the deployment link, ensuring the accuracy and effectiveness of the link verification. When the verification is successful, the functional module can be smoothly connected to the domain control board, which improves the success rate of deployment. If the verification fails, the system will record relevant information to facilitate the analysis and improvement of the problem and reduce the failure rate in subsequent system operation.

[0079] In step S320, the functions of the functional modules are allocated and connected to the domain control board according to the hardware function information, including:

[0080] When the access is successful, the functional modules are arranged and combined, and the program is run according to the combined functional modules;

[0081] When access fails, the access failure information is recorded in the log module.

[0082] In this step, the arrangement and combination of functional modules after access enables the system to flexibly adjust the configuration of functional modules according to actual needs, improving the flexibility and adaptability of the system. By running the program through the combined modules, the system can make full use of the functions of each module and optimize the overall performance. If the access fails, the system will record the failure information in time to facilitate subsequent debugging and maintenance, reducing potential risks in system operation.

[0083] Figure 6 FIG. 4 shows a full-stack deployment operation flow chart of cross-domain registration according to an embodiment of the present invention; Figure 6 As shown in the figure, the full-stack deployment operation process of cross-domain registration is as follows:

[0084] First, the system needs to be loaded, and the startup program inside the domain control board needs to be loaded to start the domain control board. At this point, the domain control board is in the "started" state. Then, hardware query adaptation is performed to obtain the hardware parameters of the domain control board, including CPU, memory, GPU, operating system, camera and image sensor, data interface, etc. Matching is performed in the hardware library based on these parameters. If relevant hardware already exists in the hardware library, hardware verification is performed.

[0085] Verify whether the basic functions and core functions of the hardware can be used normally. If the verification is successful, go to step 4 link self-test, otherwise go to step 8 and record the verification failure information in the log system.

[0086] When there is no relevant hardware in the hardware library, hardware registration and function registration are performed: the parameters and functions of the new hardware are registered in the system hardware library.

[0087] After hardware and function registration, link self-test is required: for each connected module, functional integrity test is performed first. After all modules have completed functional verification, functional verification mainly verifies whether the module functions are complete and the test output meets certain accuracy requirements. If the self-test is successful, link verification is started.

[0088] Link verification: Link verification mainly connects all modules, inputs the specified vehicle status, images, etc. through the ROS environment, verifies the results obtained through the cross-platform deployment link, and automatically verifies the results. If the verification is successful, resources are allocated, otherwise, the verification failure information is recorded in the log system.

[0089] Figure 7 FIG. 4 shows a schematic diagram of a full-stack deployment module for cross-domain registration according to an embodiment of the present invention; Figure 7 As shown, resource allocation is then performed: resource allocation and adaptation are performed according to the domain empty board information. If the allocation is successful, dynamic link adaptation is performed: according to the modules with different resource allocations, dynamic modules are automatically arranged and combined, and the optimal deployment link is determined by verifying link performance and output and combining log analysis. Otherwise, the allocation failure information is recorded in the log system.

[0090] When the dynamic modules are arranged and combined, the system is running. At this time, the system enters the running state. The system calls of various functional modules support the normal operation of the car. Any abnormal information during the operation will be recorded in the log system. Finally, the system operation ends.

[0091] Figure 8 A schematic flow chart of a full-stack deployment system for cross-domain registration according to an embodiment of the present invention is shown. Figure 8 As shown, a full-stack deployment system for cross-domain registration is also provided, including:

[0092] The acquisition module 810 is used to acquire the hardware parameters of the domain control board and match the hardware corresponding to the hardware parameters;

[0093] A registration module 820, used to register hardware parameters and hardware functions into a hardware library to obtain hardware information and hardware function information;

[0094] Access module 830, used for the full-stack deployment system to allocate and access the functional modules in the system to the domain control board through hardware information and hardware function information;

[0095] The running module 840 is used to arrange and combine the functional modules of the access domain control board and run the program according to the combined functional modules.

[0096] In particular, an electronic device is also provided, the electronic device includes a processor and a memory, the memory stores computer executable instructions that can be executed by the processor, and the processor executes the computer executable instructions to implement a full-stack deployment method for cross-domain registration, for example, to execute the above-described Figure 1 Steps S100 to S400 of the method described above are also performed. Figure 5 Method steps S311 to S313.

[0097] In particular, a computer-readable storage medium is also provided, the computer-readable storage medium storing computer-executable instructions, when the computer-executable instructions are called and executed by the processor, the computer-executable instructions prompt the processor to implement a full-stack deployment method for cross-domain registration, for example, to execute the above-described Figure 1Steps S100 to S400 of the method described above are also performed. Figure 5 Method steps S311 to S313.

[0098] The processor is used to complete various control logics of the device, which can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a single-chip microcomputer, an ARM (Acorn RISCMachine) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination of these components. In addition, the processor can also be any traditional processor, microprocessor or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP and / or any other such configuration.

[0099] The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0100] As an example, non-volatile storage media can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) as external cache memory. By way of illustration and not limitation, RAM can be obtained in many forms such as synchronous RAM (SRAM), dynamic RAM, (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The disclosed memory components or memories of the operating environment described herein are intended to include one or more of these and / or any other suitable types of memory.

[0101] Of course, those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware (such as a processor, a controller, etc.) through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium, and the computer program can include the processes of the above-mentioned method embodiments when executed. The storage medium can be a memory, a disk, a floppy disk, a flash memory, an optical storage device, etc.

[0102] The above are only some specific implementation methods of the present application, and any other improvements made based on the concept of the present application are deemed to be within the protection scope of the present application.

Claims

1. A full-stack deployment method for cross-domain registration, characterized in that: include: Obtaining the domain control board hardware parameters and matching the hardware corresponding to the hardware parameters; Registering the hardware parameters and the hardware functions into a hardware library to obtain the hardware information and the hardware function information; The full-stack deployment system allocates and connects the functional modules in the system to the domain control board through the hardware information and the hardware function information; The functional modules connected to the domain control board are arranged and combined, and a program is run according to the combined functional modules.

2. The method according to claim 1, characterized in that The obtaining of the domain control board hardware parameters and matching the hardware corresponding to the hardware parameters includes: Determine whether there is hardware corresponding to the hardware parameters in the hardware library; When hardware corresponding to the hardware parameters exists in the hardware library, verifying whether the hardware functions are complete; When the hardware corresponding to the hardware parameter does not exist in the hardware library, hardware is acquired and updated to the hardware library.

3. The method according to claim 2, characterized in that The verifying whether the hardware function is complete includes: When each hardware function is complete, the functional module is connected; When at least one hardware function is incomplete, verification failure information is recorded in the log module.

4. The method according to claim 1, characterized in that: The full-stack deployment system connects the functional modules in the system to the domain control board through the hardware information and the hardware function information, including: Acquire a functional module corresponding to the hardware information through the hardware information; The functions of the functional modules are allocated and connected to the domain control board according to the hardware function information.

5. The method according to claim 4, characterized in that The acquiring, through the hardware information, a functional module corresponding to the hardware information, comprises: Verify whether the functions of each functional module are complete; When the functions of each of the functional modules are complete, each of the functional modules is connected to form a deployment link, and the deployment link is verified; When the function of at least one of the functional modules is incomplete, the incomplete functional module is reacquired.

6. The method according to claim 5, characterized in that The deployment link is verified, including: Verify the deployment link through the ROS environment, and when the deployment link verification succeeds, allocate the functions of the functional module and connect them to the domain control board; When the deployment link verification fails, the verification failure information is recorded in the log module.

7. The method according to claim 4, characterized in that The allocating the functions of the functional modules according to the hardware function information and connecting them to the domain control board includes: When the access is successful, the functional modules are arranged and combined, and the program is run according to the combined functional modules; When access fails, the access failure information is recorded in the log module.

8. A full-stack deployment system for cross-domain registration, characterized in that: include: An acquisition module is used to acquire the hardware parameters of the domain control board and match the hardware corresponding to the hardware parameters; A registration module, used to register the hardware parameters and the hardware functions into a hardware library, and obtain the hardware information and the hardware function information; An access module, used for the full-stack deployment system to allocate and access the functional modules in the system to the domain control board through the hardware information and the hardware function information; The running module is used to arrange and combine the functional modules connected to the domain control board, and run the program according to the combined functional modules.

9. An electronic device, characterized in that: The electronic device includes a processor and a memory, the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the full-stack deployment method for cross-domain registration as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are called and executed by the processor, the computer-executable instructions prompt the processor to implement the full-stack deployment method for cross-domain registration as described in any one of claims 1 to 7.

Images