Navigation map generation method and device, vehicle and storage medium

Abstract

The invention relates to the technical field of 3D rendering, and discloses a navigation map generation method and device, a vehicle and a storage medium, and the method comprises the steps: isolating a memory region from a memory, dividing the memory region into a plurality of memory sub-regions based on different data types, and collecting camera data, driving guidance and driving route data; and a lane-level software development kit obtains rendering related data from the memory sub-regions to perform data fusion, generates 3D rendering data, stores the 3D rendering data in a fourth memory sub-region, and stores the 3D rendering data in the third memory sub-region. The lane-level software development kit obtains the rendering related data from the first memory sub-region, the second memory sub-region and the third memory sub-region. And the 3D rendering engine acquires the driving guide data and the 3D rendering data from the second memory sub-region and the fourth memory sub-region, and performs lane-level 3D rendering, so that rendering related data is directly stored in an intelligent cabin domain memory, the data transmission process is reduced, the rendering related data is stored in a partitioned manner according to types and purposes, the data processing process is avoided, and the data processing efficiency is improved. And the time consumption of the whole 3D rendering process is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of 3D rendering, and particularly relates to a navigation map generation method and device, a vehicle and a storage medium. BACKGROUND

[0002] As shown in the figure, the 3D rendering in the traditional intelligent cockpit includes the following links: 3D rendering original data generation, the data sources are vehicle camera, route data generated by a map software development kit (SDK); in the data processing process, the vehicle camera data is first parsed into a data format that can be transmitted in the intelligent cockpit, the data is formatted in the intelligent driving domain and then transmitted to the intelligent cockpit domain through a transmission protocol, the route generation is generated by the map SDK, the route data and the vehicle front camera data transmitted from the intelligent driving domain are fused and then transmitted to the lane-level SDK, and the lane-level SDK generates 3D rendering data. Figure 1

[0003] It can be known that, in the process of executing 3D rendering, the real-time acquired original data needs to be transmitted across domains from the intelligent driving domain to the intelligent cockpit domain, and the data needs to be formatted before being transmitted for 3D rendering, which will increase data delay and the system stability is poor, and it is difficult to meet the high requirements of the intelligent cockpit on the real-time, accuracy and fluency of 3D rendering. SUMMARY

[0004] Therefore, the present application provides a navigation map generation method and device, a vehicle and a storage medium to solve the problem that real-time acquisition of rendering related data will increase data delay and the system stability is poor.

[0005] In a first aspect, the present application provides a navigation map generation method, which includes: isolating a first memory area of a preset size in the memory of the intelligent cockpit domain, and dividing the first memory area into a plurality of memory sub-areas based on different data types of rendering related data; collecting camera data by a camera device and storing the camera data in a first memory sub-area, and collecting driving guide data and driving route data by a map software development kit and storing the driving guide data and the driving route data in a second memory sub-area and a third memory sub-area respectively; acquiring the camera data, the driving guide data and the driving route data from the first memory sub-area, the second memory sub-area and the third memory sub-area; performing data fusion on the acquired camera data, driving guide data and driving route data to generate 3D rendering data, and storing the 3D rendering data in a corresponding fourth memory sub-area; acquiring the driving guide data and the 3D rendering data from the second memory sub-area and the fourth memory sub-area, and performing 3D rendering based on the driving guide data and the 3D rendering data to generate a 3D navigation map. ​

[0006] The navigation map generation method provided in this embodiment isolates a first memory region in the intelligent cockpit domain memory and divides the first memory region into multiple memory sub-regions based on different data types of rendering-related data. Camera data is collected by a camera device and stored in the first memory sub-region. Driving guidance data and driving route data are collected by a map software development kit and stored in the second and third memory sub-regions respectively. The lane-level software development kit retrieves rendering-related data from the corresponding memory sub-regions, performs data fusion to generate 3D rendering data, and stores the 3D rendering data in the corresponding fourth memory sub-region. The 3D rendering engine retrieves driving guidance data and 3D rendering data from the second and fourth memory sub-regions, performs lane-level 3D rendering, and generates a 3D navigation map. This method directly stores rendering-related data in the intelligent cockpit domain memory, reducing data transmission processes. Furthermore, by partitioning and storing rendering-related data according to type and purpose, it allows for retrieval based on type and purpose, avoiding data fusion, processing, and separation processes, thus reducing the overall time consumption of 3D rendering and improving the real-time performance, accuracy, and smoothness of 3D rendering in the intelligent cockpit domain.

[0007] In one optional implementation, dividing the first memory region into multiple memory sub-regions includes: determining the address of the memory sub-region corresponding to each data type based on the number of data types of the rendering-related data; establishing a mapping relationship between the address of each memory sub-region and each data type, so as to store the acquired rendering-related data based on the mapping relationship.

[0008] This invention divides memory regions based on addresses, ensuring overall memory space is controllable and ensuring that data storage locations are unique, avoiding address conflicts and data chaos. Furthermore, it establishes a mapping relationship between data types and addresses, achieving a clear data mapping relationship and improving the efficiency of data storage and access.

[0009] In an optional implementation, the method further includes: monitoring the current scene type of the vehicle; when the current scene type of the vehicle matches the scene type of the preset elastic memory, isolating a second memory area of ​​the preset elastic memory size in the smart cockpit domain; and allocating the second memory area as a data storage area corresponding to the camera data, driving guidance data, or driving route data based on the current scene type of the vehicle.

[0010] This invention enables dynamic allocation of memory region resources based on different vehicle scenarios, avoiding excessive occupation of other memory sub-regions or failure to fully store rendering-related data in memory sub-regions, which would affect the accuracy of subsequent 3D rendering.

[0011] In one optional implementation, the rendering-related data includes data to be rendered and corresponding storage timestamps. The step of obtaining the camera data, driving guidance data, and driving route data from the first memory sub-region, the second memory sub-region, and the third memory sub-region includes: obtaining the camera data, driving guidance data, and driving route data respectively in ascending order of the storage timestamps stored in the first memory sub-region, the second memory sub-region, and the third memory sub-region.

[0012] The lane-level SDK of this invention obtains the corresponding rendering-related data in real time according to the ascending time order of the storage timestamps stored in the memory sub-region, ensuring the temporal consistency of the rendering data, improving the continuity and accuracy of the lane-level navigation screen, simplifying data association and fusion, and improving the efficiency of 3D rendering.

[0013] In one optional implementation, the method further includes: marking the rendering-related data already acquired in each memory sub-region; and deleting the marked rendering-related data in all memory sub-regions after 3D rendering is completed.

[0014] This invention deletes the acquired rendering-related data, which can release invalid data in memory in a timely manner and add rendering-related data in real time, thus ensuring the continuity of 3D rendering.

[0015] In an alternative implementation, the method further includes: providing path guidance based on the 3D navigation map.

[0016] This invention utilizes 3D navigation maps for route guidance, making the real road scene more realistic and the spatial perception more intuitive.

[0017] In one alternative implementation, the method further includes: terminating the 3D rendering process in response to information indicating a failure to acquire rendering-related data; and switching to a standard precision navigation mode for path guidance.

[0018] When the present invention receives a message indicating a failure to acquire rendering-related data, it can terminate the 3D rendering process and switch to standard precision navigation mode for path guidance, ensuring uninterrupted navigation service and maintaining driving continuity.

[0019] Secondly, the present invention provides a navigation map generation device, the device comprising: a memory region partitioning module, used to isolate a first memory region of a preset size in the intelligent cockpit domain memory, and to divide the first memory region into multiple memory sub-regions based on different data types of rendering-related data; a data storage module, used to collect camera data through a camera device and store it in the first memory sub-region, and to collect driving guidance data and driving route data through a map software development kit and store them in a second memory sub-region and a third memory sub-region, respectively; a data acquisition module, used to acquire the camera data, driving guidance data, and driving route data from the first memory sub-region, the second memory sub-region, and the third memory sub-region; a data fusion module, used to fuse the acquired camera data, driving guidance data, and driving route data to generate 3D rendering data, and to store the 3D rendering data in a corresponding fourth memory sub-region; and a 3D rendering module, used to acquire the driving guidance data and the 3D rendering data from the second memory sub-region and the fourth memory sub-region, and to perform 3D rendering based on the driving guidance data and the 3D rendering data to generate a 3D navigation map.

[0020] Thirdly, the present invention provides a vehicle including an intelligent cockpit domain, the intelligent cockpit domain including a controller, the controller including a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the navigation map generation method of the first aspect or any corresponding embodiment described above.

[0021] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to perform the navigation map generation method of the first aspect or any corresponding embodiment thereof.

[0022] The present invention has the following technical effects:

[0023] This invention isolates a first memory region within the intelligent cockpit domain memory and divides it into multiple sub-regions based on different data types related to rendering. Camera data is collected and stored in the first sub-region. Driving guidance and route data are collected and stored in the second and third sub-regions respectively using a map software development kit (MDK). A lane-level MSDK retrieves rendering-related data from the corresponding sub-regions, performs data fusion to generate 3D rendering data, and stores this data in a corresponding fourth sub-region. A 3D rendering engine retrieves driving guidance and 3D rendering data from the second and fourth sub-regions, performs lane-level 3D rendering, and generates a 3D navigation map. This allows rendering-related data to be directly stored in the intelligent cockpit domain memory, reducing data transmission. Furthermore, by partitioning and storing rendering-related data according to type and purpose, it allows for retrieval based on type and purpose, avoiding data fusion, processing, and separation processes, thus reducing the overall time spent on 3D rendering and improving the real-time performance, accuracy, and smoothness of 3D rendering in the intelligent cockpit domain. Attached Figure Description

[0024] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0025] Figure 1 This is a schematic diagram of traditional intelligent cockpit domain navigation map generation in the background technology;

[0026] Figure 2 This is a flowchart illustrating a navigation map generation method according to an embodiment of the present invention;

[0027] Figure 3 This is an example diagram of the first memory region division according to an embodiment of the present invention;

[0028] Figure 4 This is a flowchart illustrating a navigation map generation method according to an embodiment of the present invention;

[0029] Figure 5 This is a flowchart illustrating another navigation map generation method according to an embodiment of the present invention;

[0030] Figure 6 This is a structural example diagram of a vehicle according to an embodiment of the present invention;

[0031] Figure 7 This is a structural block diagram of a navigation map generation method apparatus according to an embodiment of the present invention;

[0032] Figure 8 This is a schematic diagram of the hardware structure of the controller according to an embodiment of the present invention. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0034] According to an embodiment of the present invention, a method for generating navigation maps is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0035] This embodiment provides a navigation map generation method that can be used in a controller within a smart cockpit domain. Figure 2 This is a flowchart of a navigation map generation method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps:

[0036] Step S201: Isolate a first memory region of a preset size in the intelligent cockpit domain memory, and divide the first memory region into multiple memory sub-regions based on the different data types of rendering-related data.

[0037] In this embodiment of the invention, the vehicle's infotainment system is the one with memory hardware within the intelligent cockpit domain. A first memory region of a preset size can be isolated within the infotainment system's memory. Since lane-level navigation renders a route preceding and following the vehicle's current position, the size of the isolated memory region can be the sum of the memory sizes of all data types related to rendering within a preset time period. In this embodiment, the rendering-related data of different data types includes at least camera data (video stream data), driving guidance data, driving route data, and 3D rendering data (this is just an example and can be adjusted according to the type of data required for actual lane-level 3D rendering). Then, a 2-minute route can be taken. The data corresponds to the size of the first memory area, which is the size of the camera data memory within 3 minutes + the size of the driving guidance data memory + the size of the driving route data + the size of the 3D rendering data. This is just an example, and the memory address of this first memory area can be fixed, storing only the data required for 3D rendering. This saves the computational overhead caused by address translation when accessing data during 3D rendering, and avoids sharing dynamic memory with other data, ensuring the correctness of the rendering results. Furthermore, rendering-related data is directly stored in the intelligent cockpit domain memory and read when needed, reducing the processing of data transmission protocols. By sharing the data storage area across multiple platforms, the data storage space can be reduced.

[0038] This invention can divide a first memory region into multiple memory sub-regions based on different data types of rendering-related data. The memory size of all sub-regions can be equal, or historical rendering data or actual driving scenarios can be used as a benchmark to configure appropriate memory sizes for different sub-regions. This is merely an example. Figure 3 As shown, different memory sub-regions are used to store rendering-related data of different data types. For example, camera data is stored in region a, driving guidance data is stored in region b, driving route data is stored in region c, and 3D rendering data is stored in region d. This allows rendering-related data to be stored in partitions according to type and purpose. When needed, it can be read according to type and purpose, avoiding the process of data fusion, processing, and separation, and reducing the time consumed in the entire 3D rendering process. Furthermore, a unique region identifier can be set for each memory sub-region, and the region identifier of each memory sub-region can be mapped to its corresponding data type. This makes it convenient for the subsequent data acquisition end to store rendering-related data in the corresponding memory sub-region based on the region identifier mapped to the data type.

[0039] Step S202: Collect camera data through the camera device and store it in the first memory sub-area; collect driving guidance data and driving route data through the map software development kit and store them in the second memory sub-area and the third memory sub-area, respectively.

[0040] like Figure 4As shown, embodiments of the present invention can collect video data through a camera device (such as a vehicle-mounted camera), collect driving route data for 2 minutes before and after the current vehicle location through a map software development kit (SDK), and obtain driving guidance data through the map SDK as the vehicle moves. The obtained rendering-related data can be stored in its corresponding memory sub-region according to the area identifier mapped by different data types.

[0041] Step S203: Obtain camera data, driving guidance data, and driving route data from the first memory sub-region, the second memory sub-region, and the third memory sub-region.

[0042] like Figure 4 As shown, the embodiments of the present invention can utilize a lane-level SDK to perform data fusion and generate 3D rendering. The lane-level SDK can obtain camera data from a first memory sub-region, driving guidance data from a second memory sub-region, and driving route data from a third memory sub-region.

[0043] Step S204: The acquired camera data, driving guidance data and driving route data are fused to generate 3D rendering data, and the 3D rendering data is stored in the corresponding fourth memory sub-region.

[0044] The lane-level SDK of this invention can fuse acquired camera data, driving guidance data and driving route data to generate 3D rendering data, and can store the generated 3D rendering data in a corresponding fourth memory sub-region.

[0045] Step S205: Obtain driving guidance data and 3D rendering data from the second memory sub-region and the fourth memory sub-region, and perform 3D rendering based on the driving guidance data and 3D rendering data to generate a 3D navigation map.

[0046] In this embodiment of the invention, a 3D rendering engine can be used to perform lane-level 3D rendering operations. The 3D rendering engine can obtain driving guidance data from the second memory sub-region and 3D rendering data from the fourth memory sub-region. The obtained driving guidance data and 3D rendering data can then be 3D rendered into a lane-level navigation scene. The data processing processes of the camera device, map SDK, lane-level SDK, and 3D rendering engine are performed simultaneously.

[0047] The navigation map generation method provided in this embodiment isolates a first memory region in the intelligent cockpit domain memory and divides the first memory region into multiple memory sub-regions based on different data types of rendering-related data. Camera data is collected by a camera device and stored in the first memory sub-region. Driving guidance data and driving route data are collected by a map software development kit and stored in the second and third memory sub-regions respectively. The lane-level software development kit retrieves rendering-related data from the corresponding memory sub-regions, performs data fusion to generate 3D rendering data, and stores the 3D rendering data in the corresponding fourth memory sub-region. The 3D rendering engine retrieves driving guidance data and 3D rendering data from the second and fourth memory sub-regions, performs lane-level 3D rendering, and generates a 3D navigation map. This method directly stores rendering-related data in the intelligent cockpit domain memory, reducing data transmission processes. Furthermore, by partitioning and storing rendering-related data according to type and purpose, it allows for retrieval based on type and purpose, avoiding data fusion, processing, and separation processes, thus reducing the overall time consumption of 3D rendering and improving the real-time performance, accuracy, and smoothness of 3D rendering in the intelligent cockpit domain.

[0048] This embodiment provides a navigation map generation method that can be used in a controller within a smart cockpit domain. Figure 5 This is a flowchart of a navigation map generation method according to an embodiment of the present invention, such as... Figure 5 As shown, the process includes the following steps:

[0049] Step S501: Isolate a first memory region of a preset size in the intelligent cockpit domain memory, and divide the first memory region into multiple memory sub-regions based on the different data types of rendering-related data.

[0050] Specifically, step S501 includes:

[0051] Step S5011: Based on the number of data types of the rendering-related data, determine the address of the memory sub-region corresponding to each data type.

[0052] Step S5012: Establish the mapping relationship between the address of each memory sub-region and each data type, so as to store the acquired rendering-related data based on the mapping relationship.

[0053] In this embodiment of the invention, when isolating the first memory region, the memory size and fixed address of the first memory region are pre-calculated. Correspondingly, when dividing the memory into sub-regions, the starting address of the first memory region can be used as the starting address of the first memory sub-region. For example, the starting address of the region storing vehicle camera data is 0xFFFa. Based on the memory size of the first memory sub-region, the address of the second memory sub-region is determined. For example, the starting address of the region storing driving guidance data is 0xFFFb. Then, the ending address of the corresponding first memory sub-region can be 0xFFFb, and the address range of the corresponding first memory sub-region is 0xFFFa to 0xFFFb. This is just an example. Then, the starting address of the third memory sub-region is determined to be 0xFFFc, and the starting address of the fourth memory sub-region is 0xFFFd. Its ending address is the memory ending address of the first memory region. This is just an example.

[0054] The embodiments of the present invention can establish a mapping relationship between the addresses of each memory sub-region and each data type, so that after obtaining the rendering-related data, the rendering-related data of each data type can be accurately stored in the corresponding memory sub-region based on the mapped address. When storing the rendering-related data in the memory sub-region, it can be arranged according to the order of storage, so as to realize efficient "sliding window" type data management.

[0055] In one alternative implementation, after isolating a first memory region of a preset size in the smart cockpit domain memory, the data in the isolated first memory region is cleared.

[0056] When the lane-level navigation of this embodiment of the invention starts, the first memory region can be isolated from the smart cockpit domain memory based on the configured memory size and starting address of the first memory region, and the residual data in the first memory region can be cleared to ensure that the first memory region only includes rendering-related data, thereby improving the accuracy of lane-level navigation 3D rendering.

[0057] In one optional implementation, the current scene type of the vehicle is monitored; when the current scene type of the vehicle is detected to match the scene type of the preset elastic memory, a second memory area of ​​the preset elastic memory size is isolated in the smart cockpit domain; based on the current scene type of the vehicle, the second memory area is allocated as a data storage area corresponding to the camera data, driving guidance data, or driving route data.

[0058] This invention can monitor the current environment of a vehicle using devices such as high-precision maps, surround-view cameras, and radar, and determine whether the current scene type of the vehicle is in is within a set of scene types in a preset elastic memory (including but not limited to complex intersections, parking lots, and highway navigation scenarios). When the current scene type of the vehicle is detected to match the scene type in the preset elastic memory, a second memory area of ​​a preset elastic memory size can be isolated in the intelligent cockpit domain. The preset elastic memory size can be set according to the vehicle's memory space and the actual scene. Based on the current scene type of the vehicle, the second memory area can be allocated to the data storage area corresponding to the camera data, driving guidance data, or driving route data. For example, if the vehicle is in a parking lot, the second memory area can be allocated to the data storage area corresponding to the camera data, and the address information corresponding to the second memory area can be updated to the address of the memory sub-area corresponding to the camera data, facilitating the subsequent storage of the camera data in the second memory area. This is just an example.

[0059] This invention enables dynamic allocation of memory region resources based on different vehicle scenarios, avoiding excessive occupation of other memory sub-regions or failure to fully store rendering-related data in memory sub-regions, which would affect the accuracy of subsequent 3D rendering.

[0060] Step S502: Collect camera data through the camera device and store it in the first memory sub-area; collect driving guidance data and driving route data through the map software development kit and store them in the second memory sub-area and the third memory sub-area, respectively.

[0061] Specifically, the rendering-related data includes the data to be rendered and the corresponding storage timestamp. Step S502 includes:

[0062] Step S5021: Acquire camera data, driving guidance data, and driving route data respectively according to the ascending time order of the storage timestamps stored in the first memory sub-region, the second memory sub-region, and the third memory sub-region.

[0063] The lane-level SDK of this invention obtains the corresponding rendering-related data in real time according to the ascending time order of the storage timestamps stored in the memory sub-region, ensuring the temporal consistency of the rendering data, improving the continuity and accuracy of the lane-level navigation screen, simplifying data association and fusion, and improving the efficiency of 3D rendering.

[0064] In one alternative implementation, the rendering-related data already acquired in each memory sub-region is marked; after 3D rendering is completed, the marked rendering-related data in all memory sub-regions is deleted.

[0065] After the lane-level SDK and 3D rendering engine of this embodiment of the invention obtain the corresponding rendering-related data, they can mark the obtained rendering-related data, such as marking it as an identifier to be deleted or marking it as "read". This is just an example. After the 3D rendering is completed or within a preset period, the marked rendering-related data in all memory sub-regions can be deleted.

[0066] This invention deletes the acquired rendering-related data, which can release invalid data in memory in a timely manner and add rendering-related data in real time, thus ensuring the continuity of 3D rendering.

[0067] Step S503: Mark the rendering-related data already acquired in each memory sub-region; after 3D rendering is completed, delete the marked rendering-related data in all memory sub-regions. For details, please refer to... Figure 2 Step S203 of the illustrated embodiment will not be described again here.

[0068] Step S504 involves fusing the acquired camera data, driving guidance data, and driving route data to generate 3D rendering data, which is then stored in the corresponding fourth memory sub-region. For details, please refer to [link to relevant documentation]. Figure 2 Step S204 of the illustrated embodiment will not be described again here.

[0069] Step S505: Obtain driving guidance data and 3D rendering data from the second and fourth memory sub-regions, and perform 3D rendering based on the driving guidance data and 3D rendering data to generate a 3D navigation map. For details, please refer to [link to relevant documentation]. Figure 2 Step S205 of the illustrated embodiment will not be described again here.

[0070] The method also includes: after generating a 3D navigation map through the above steps, route guidance can be performed based on the 3D navigation map.

[0071] This invention utilizes 3D navigation maps for route guidance, making the real road scene more realistic and the spatial perception more intuitive.

[0072] During the execution of the above navigation map generation method, in response to the information that the rendering-related data failed to be obtained, the 3D rendering process is terminated; and the standard precision navigation mode is switched to guide the path.

[0073] If the lane-level SDK or 3D rendering engine fails to read rendering-related data from the memory area in this embodiment of the invention, it can prompt a message indicating that the lane-level navigation is not supported or the existing conditions do not meet the conditions for lane-level navigation rendering. In this case, the lane-level navigation 3D rendering process can be terminated and the path guidance can be switched to the standard definition navigation (SD) mode.

[0074] When the present invention receives a message indicating a failure to acquire rendering-related data, it can terminate the 3D rendering process and switch to standard precision navigation mode for path guidance, ensuring uninterrupted navigation service and maintaining driving continuity.

[0075] This embodiment also provides a vehicle, such as Figure 6 As shown, the vehicle includes an intelligent cockpit domain 61, which includes a controller. The controller includes a memory and a processor. The memory and the processor are interconnected. The memory stores computer instructions. The processor executes the computer instructions to perform the navigation map generation method described in the above embodiments. For detailed description, please refer to the above embodiments, which will not be repeated here.

[0076] This embodiment also provides a navigation map generation device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0077] This embodiment provides a navigation map generation device, such as... Figure 7As shown, the system includes: a memory region partitioning module 701, used to isolate a first memory region of a preset size in the intelligent cockpit domain memory, and to divide the first memory region into multiple memory sub-regions based on different data types of rendering-related data; a data storage module 702, used to collect camera data through a camera device and store it in the first memory sub-region, and to collect driving guidance data and driving route data through a map software development kit and store them in the second and third memory sub-regions respectively; a data acquisition module 703, used to acquire camera data, driving guidance data, and driving route data from the first, second, and third memory sub-regions; a data fusion module 704, used to fuse the acquired camera data, driving guidance data, and driving route data to generate 3D rendering data, and to store the 3D rendering data in the corresponding fourth memory sub-region; and a 3D rendering module 705, used to acquire driving guidance data and 3D rendering data from the second and fourth memory sub-regions, and to perform 3D rendering based on the driving guidance data and 3D rendering data to generate a 3D navigation map.

[0078] In some optional implementations, the memory region partitioning module 701 includes: an address calculation unit, used to determine the address of the memory sub-region corresponding to each data type based on the number of data types of rendering-related data; and an address mapping unit, used to establish a mapping relationship between the address of each memory sub-region and each data type, so as to store the acquired rendering-related data based on the mapping relationship.

[0079] In some optional implementations, the navigation map generation device further includes: a scene monitoring module for monitoring the scene type currently in which the vehicle is located; an elastic memory isolation module for isolating a second memory area of ​​a preset elastic memory size in the smart cockpit domain when the scene type currently in which the vehicle is located is detected to match the scene type of the preset elastic memory; and a storage area update module for allocating the second memory area as a data storage area corresponding to the camera data, driving guidance data, or driving route data based on the scene type currently in which the vehicle is located.

[0080] In some optional implementations, the rendering-related data includes data to be rendered and corresponding storage timestamps. The data acquisition module 703 includes a time sequence acquisition unit, which is used to acquire camera data, driving guidance data and driving route data respectively in ascending time order of storage timestamps stored in the first memory sub-region, the second memory sub-region and the third memory sub-region.

[0081] In some optional implementations, the navigation map generation apparatus further includes: a data marking module for marking the rendering-related data acquired in each memory sub-region; and a data deletion module for deleting the marked rendering-related data in all memory sub-regions after 3D rendering is completed.

[0082] In some alternative implementations, the navigation map generation apparatus further includes a path guidance module for providing path guidance based on the 3D navigation map.

[0083] In some optional implementations, the navigation map generation apparatus further includes: a rendering termination module for terminating the 3D rendering process in response to information indicating a failure to acquire rendering-related data; and a mode switching module for switching to a standard precision navigation mode for path guidance.

[0084] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0085] In this embodiment, the navigation map generation device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0086] This invention also provides a controller in a smart cockpit domain, having the above-described features. Figure 7 The navigation map generation device shown.

[0087] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of a controller provided in an optional embodiment of the present invention, such as... Figure 8 As shown, the controller includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise as required. The processors can process instructions executed within the controller, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple controllers can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 8 Take a processor 10 as an example.

[0088] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0089] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0090] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the controller. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the controller via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0091] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0092] The controller also includes an input device 30 and an output device 40. The processor 10, memory 20, input device 30, and output device 40 can be connected via a bus or other means. Figure 8 Taking the example of a connection between China and Israel via a bus.

[0093] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the controller, such as a touch screen, keypad, mouse, trackpad, touchpad, joystick, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touch screen.

[0094] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0095] A portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0096] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for generating a navigation map, characterized in that, The method includes: In the intelligent cockpit domain memory, a first memory region of a preset size is isolated, and based on the different data types of rendering-related data, the first memory region is divided into multiple memory sub-regions. Video data is collected by a camera device and stored in the first memory sub-area; driving guidance data and driving route data are collected by a map software development kit and stored in the second and third memory sub-areas, respectively. The camera data, driving guidance data, and driving route data are obtained from the first memory sub-region, the second memory sub-region, and the third memory sub-region; The acquired camera data, driving guidance data, and driving route data are fused together to generate 3D rendering data, and the 3D rendering data is stored in the corresponding fourth memory sub-region. The driving guidance data and the 3D rendering data are obtained from the second memory sub-region and the fourth memory sub-region, and 3D rendering is performed based on the driving guidance data and the 3D rendering data to generate a 3D navigation map.

2. The method according to claim 1, characterized in that, The step of dividing the first memory region into multiple memory sub-regions includes: Based on the number of data types of the rendering-related data, determine the address of the memory sub-region corresponding to each data type; Establish a mapping relationship between the addresses of each memory sub-region and each data type, so that the acquired rendering-related data can be stored based on the mapping relationship.

3. The method according to claim 1, characterized in that, The method further includes: Monitor the current scene type of the vehicle; When it is detected that the current scene type of the vehicle matches the scene type of the preset elastic memory, a second memory area of ​​the preset elastic memory size is isolated in the smart cockpit domain. Based on the current scene type of the vehicle, the second memory area is allocated as the data storage area corresponding to the camera data, driving guidance data, or driving route data.

4. The method according to claim 1, characterized in that, The rendering-related data includes the data to be rendered and the corresponding storage timestamp. The step of obtaining the camera data, driving guidance data, and driving route data from the first memory sub-region, the second memory sub-region, and the third memory sub-region includes: The camera data, driving guidance data, and driving route data are obtained in ascending order of the timestamps stored in the first memory sub-region, the second memory sub-region, and the third memory sub-region, respectively.

5. The method according to claim 1, characterized in that, The method further includes: Mark the rendering-related data that has been acquired in each memory sub-region; After 3D rendering is complete, all marked rendering-related data in all memory sub-regions are deleted.

6. The method according to claim 1, characterized in that, The method further includes: Path guidance is provided based on the 3D navigation map.

7. The method according to claim 6, characterized in that, The method further includes: In response to a failure to obtain rendering-related data, the 3D rendering process is terminated. Switch to standard precision navigation mode for path guidance.

8. A navigation map generation device, characterized in that, The device includes: The memory region partitioning module is used to isolate a first memory region of a preset size in the intelligent cockpit domain memory, and to divide the first memory region into multiple memory sub-regions based on different data types of rendering-related data. The data storage module is used to collect camera data through the camera device and store it in the first memory sub-area, and to collect driving guidance data and driving route data through the map software development kit and store them in the second memory sub-area and the third memory sub-area, respectively. The data acquisition module is used to acquire the camera data, driving guidance data, and driving route data from the first memory sub-region, the second memory sub-region, and the third memory sub-region; The data fusion module is used to fuse the acquired camera data, driving guidance data and driving route data to generate 3D rendering data, and store the 3D rendering data in the corresponding fourth memory sub-region. The 3D rendering module is used to obtain driving guidance data and 3D rendering data from the second memory sub-region and the fourth memory sub-region, and perform 3D rendering based on the driving guidance data and the 3D rendering data to generate a 3D navigation map.

9. A vehicle, characterized in that, The vehicle includes an intelligent cockpit domain, which includes a controller. The controller includes a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the navigation map generation method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the navigation map generation method according to any one of claims 1 to 7.

Images