Vehicle AVM rendering and display method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, and provides an in-vehicle AVM rendering and display method, device, equipment and medium, which can respond to a target rendering request initiated to a target vehicle through a target application program, start an EVS rendering engine of the target vehicle, obtain a to-be-rendered image through the EVS rendering engine, and display the to-be-rendered image through the EVS rendering engine. The method comprises the following steps: acquiring a to-be-rendered image, preprocessing the to-be-rendered image to obtain a target image, transmitting the target image to a target algorithm library through an EVS rendering engine for rendering to obtain a rendered image, and sending the rendered image to a target application program for displaying, thereby decoupling a rendering logic and a display logic of the AVM based on the EVS rendering engine. The modularized processing mechanism effectively improves the performance and flexibility of the vehicle AVM system.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a rendering and display method, device, equipment and medium for an on-board automatic machine virtual machine (AVM). Background Art

[0002] In traditional Android native implementations, EVS (Extended View System) functions are usually integrated into a single EVSApp (EVS application), which is responsible for both rendering image data and the final image display and user interface interaction. Although this design pattern simplifies the development process, its drawbacks gradually become apparent as the system complexity increases:

[0003] 1) High coupling: The rendering logic and display logic are tightly bound to the same application, resulting in a complex code structure that is difficult to maintain and expand. Once the rendering algorithm needs to be adjusted or the display performance needs to be optimized, the entire application often needs to be modified on a large scale, increasing development costs and risks;

[0004] 2) Poor flexibility: As the market demand for personalization grows, a single application architecture is difficult to meet diverse display and interaction needs. For example, different car models may require customized UI (User Interface) and display logic, and these customizations often need to be achieved by recompiling the entire application under the traditional architecture. Summary of the invention

[0005] In view of the above, it is necessary to provide a rendering and display method, device, equipment and medium for the vehicle AVM, which can decouple the rendering logic and display logic of the vehicle AVM system, thereby improving system performance and flexibility.

[0006] A method for rendering and displaying an AVM of a vehicle, the method comprising:

[0007] In response to a target rendering request initiated by a target application to a target vehicle, starting an EVS rendering engine of the target vehicle;

[0008] Acquire the image to be rendered through the EVS rendering engine, and pre-process the image to be rendered to obtain a target image;

[0009] Initialize a target algorithm library, and transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image;

[0010] The rendered image is sent to the target application for display via the EVS rendering engine.

[0011] According to a preferred embodiment of the present invention, the EVS rendering engine includes at least one interface, each interface defining the format of data exchange, parameters of rendering requests and callback mechanism;

[0012] Each interface is used for the application to call the corresponding algorithm library;

[0013] Each algorithm library includes at least one algorithm for executing a preset function.

[0014] According to a preferred embodiment of the present invention, obtaining the image to be rendered by the EVS rendering engine includes:

[0015] The image data transmitted by the image acquisition device through the hardware abstraction layer is received by the EVS rendering engine as the image to be rendered.

[0016] According to a preferred embodiment of the present invention, before initializing the target algorithm library, the method further includes:

[0017] Acquire the interface called by the target application from the interface provided by the EVS rendering engine as the target interface;

[0018] An algorithm library corresponding to the target interface is obtained as the target algorithm library.

[0019] According to a preferred embodiment of the present invention, the step of transmitting the target image to the target algorithm library for rendering to obtain a rendered image through the EVS rendering engine includes:

[0020] The image Buffer corresponding to the target image is transmitted to the target algorithm library through the EVS rendering engine for rendering to obtain the rendered image.

[0021] According to a preferred embodiment of the present invention, sending the rendered image to the target application for display through the EVS rendering engine includes:

[0022] The rendered image is sent to the target application through the EVS rendering engine via a display queue for display.

[0023] According to a preferred embodiment of the present invention, the method further comprises:

[0024] When receiving a function extension request, determining a new algorithm library according to the function extension request;

[0025] An extended interface corresponding to the newly added algorithm library is configured for the EVS rendering engine.

[0026] A rendering and display device for an AVM of a vehicle, the rendering and display device for the AVM of a vehicle comprising:

[0027] A starting unit, configured to start an EVS rendering engine of a target vehicle in response to a target rendering request initiated by a target application to the target vehicle;

[0028] A preprocessing unit, used for acquiring an image to be rendered through the EVS rendering engine, and preprocessing the image to be rendered to obtain a target image;

[0029] A rendering unit, used for initializing a target algorithm library, and transmitting the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image;

[0030] A display unit is used to send the rendered image to the target application for display through the EVS rendering engine.

[0031] A computer device, comprising:

[0032] a memory storing at least one instruction; and

[0033] The processor executes the instructions stored in the memory to implement the rendering and display method of the vehicle AVM.

[0034] A computer-readable storage medium stores at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement the rendering and display method of the vehicle AVM.

[0035] It can be seen from the above technical scheme that the present invention can respond to a target rendering request initiated by a target application to a target vehicle, start the EVS rendering engine of the target vehicle, obtain the image to be rendered through the EVS rendering engine, and pre-process the image to be rendered to obtain the target image, transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image, and send the rendered image to the target application for display, thereby decoupling the rendering logic and display logic of the vehicle AVM based on the EVS rendering engine, and the modular processing mechanism effectively improves the performance and flexibility of the vehicle AVM system. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is a flow chart of a preferred embodiment of the rendering and display method of the vehicle AVM of the present invention.

[0037] Figure 2 It is a functional module diagram of a preferred embodiment of the rendering and display device of the vehicle AVM of the present invention.

[0038] Figure 3 It is a structural schematic diagram of a computer device of a preferred embodiment of the present invention for realizing the rendering and display method of the vehicle AVM. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solutions and advantages of the present invention more clear, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments.

[0040] like Figure 1 FIG. 1 is a flowchart of a preferred embodiment of the vehicle AVM rendering and display method of the present invention. According to different requirements, the order of the steps in the flowchart can be changed, and some steps can be omitted.

[0041] The rendering and display method of the vehicle AVM is applied to one or more computer devices, and the computer device is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0042] The computer device may be any electronic product that can perform human-computer interaction with a user, such as a personal computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a game console, an interactive network television (IPTV), a smart wearable device, etc.

[0043] The computer device may also include a network device and / or a user device, wherein the network device includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud consisting of a large number of hosts or network servers based on cloud computing.

[0044] The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms.

[0045] Among them, Artificial Intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0046] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0047] The network where the computer device is located includes but is not limited to the Internet, a wide area network, a metropolitan area network, a local area network, a virtual private network (VPN), etc.

[0048] S10, in response to a target rendering request initiated by a target application to a target vehicle, starting an EVS rendering engine (EvsRenderEngine) of the target vehicle.

[0049] In this embodiment, the target application may be an application with an EVS (Extended View System) function. For example, the target application may be an application with a function such as displaying a driving track line.

[0050] In this embodiment, the target vehicle is a vehicle equipped with an AVM (Around View Monitor, panoramic monitoring imaging system).

[0051] In this embodiment, the target rendering request may be triggered by an operation on the target application. For example, when it is detected that a button for triggering the function of displaying the driving track line on a designated interface of the target application is clicked, it is determined that the target rendering request is received.

[0052] In this embodiment, the EVS rendering engine includes at least one interface, each of which defines the format of data exchange, parameters of rendering requests, and callback mechanisms;

[0053] Each interface is used for the application to call the corresponding algorithm library;

[0054] Each algorithm library includes at least one algorithm for executing a preset function.

[0055] Among them, the format of data exchange, parameters of rendering requests and callback mechanism are defined through interfaces, which can ensure the accessibility and scalability of rendering services.

[0056] Among them, the EVS rendering engine is equivalent to a Native service that integrates a third-party algorithm library, and uses the corresponding interface of the third-party algorithm library to the EVS application program, so as to facilitate the EVS application program component to make related calls.

[0057] Among them, various algorithm libraries can be used to realize related rendering functions such as driving trajectory lines, auxiliary line rendering, 3D car model rotation, 3D car model real-time display of door and wheel status, and LDW (Lane Departure Warning, lane departure warning system), panoramic calibration and other functions.

[0058] S11, obtaining an image to be rendered through the EVS rendering engine, and preprocessing the image to be rendered to obtain a target image.

[0059] In this embodiment, obtaining the image to be rendered by the EVS rendering engine includes:

[0060] The image data transmitted by the image acquisition device through the hardware abstraction layer Hal layer is received by the EVS rendering engine as the image to be rendered.

[0061] For example: the image acquisition device may be a bottom-level camera, etc.

[0062] In this embodiment, the image to be rendered may be preprocessed according to actual rendering requirements to obtain the target image, so as to facilitate subsequent rendering processing.

[0063] S12, initializing a target algorithm library, and transmitting the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image.

[0064] In this embodiment, before initializing the target algorithm library, the method further includes:

[0065] Acquire the interface called by the target application from the interface provided by the EVS rendering engine as the target interface;

[0066] An algorithm library corresponding to the target interface is obtained as the target algorithm library.

[0067] Through the above embodiments, the EVS rendering engine can specifically call the corresponding algorithm library to facilitate rendering.

[0068] In this embodiment, the step of transmitting the target image to the target algorithm library for rendering to obtain a rendered image through the EVS rendering engine includes:

[0069] The image Buffer corresponding to the target image is transmitted to the target algorithm library through the EVS rendering engine for rendering to obtain the rendered image.

[0070] In the above embodiment, the rendering task is separated from the traditional EVS application and handed over to a dedicated EVS rendering engine for processing, so that the rendering logic and the display logic are independent of each other, the coupling between systems is reduced, and the maintainability and reusability of the code are improved.

[0071] S13, sending the rendered image to the target application for display through the EVS rendering engine.

[0072] In this embodiment, sending the rendered image to the target application for display through the EVS rendering engine includes:

[0073] The rendered image is sent to the target application through the EVS rendering engine via a display queue for display.

[0074] In this embodiment, the EVS rendering engine and the target application work together through an efficient communication mechanism. For example, when the target application needs to display an image, the target application sends a rendering request to the EVS rendering engine and receives the rendered image frame for display; when the factory performs calibration, the target application sends a relevant calibration signal to the EVS rendering engine after receiving the signal, and returns the calibration result to the calibration instrument. This collaborative approach ensures the smooth progress of the rendering process and the display process.

[0075] In this embodiment, the method further includes:

[0076] When receiving a function extension request, determining a new algorithm library according to the function extension request;

[0077] An extended interface corresponding to the newly added algorithm library is configured for the EVS rendering engine.

[0078] In the above embodiment, the EVS rendering engine provides an extended interface to support the integration of a third-party algorithm library, so that the system can cope with new requirements that may arise in the future. In addition, through the above embodiment, different third-party algorithm libraries can be selected for the EVS rendering engine according to the personalized needs of different car models and users. For example, different algorithm engines can be selected for different car models to meet different rendering requirements; the integrated algorithm library can be directly replaced for specific user groups, etc.

[0079] This embodiment uses an independent rendering engine to make resource allocation more reasonable, avoid the problem of competing resources that may be caused by rendering tasks and display tasks in the same process, realize the decoupling and efficient collaboration of rendering and display, and bring a smoother and higher-quality multimedia experience to the vehicle system. At the same time, it supports flexible and customizable function expansion, improves development efficiency, and reduces maintenance costs.

[0080] It can be seen from the above technical scheme that the present invention can respond to a target rendering request initiated by a target application to a target vehicle, start the EVS rendering engine of the target vehicle, obtain the image to be rendered through the EVS rendering engine, and pre-process the image to be rendered to obtain the target image, transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image, and send the rendered image to the target application for display, thereby decoupling the rendering logic and display logic of the vehicle AVM based on the EVS rendering engine, and the modular processing mechanism effectively improves the performance and flexibility of the vehicle AVM system.

[0081] like Figure 2 As shown, it is a functional module diagram of a preferred embodiment of the rendering and display device of the vehicle AVM of the present invention. The rendering and display device 11 of the vehicle AVM includes a startup unit 110, a preprocessing unit 111, a rendering unit 112, and a display unit 113. The module / unit referred to in the present invention refers to a series of computer program segments that can be executed by a processor and can complete fixed functions, which are stored in a memory. In this embodiment, the functions of each module / unit will be described in detail in subsequent embodiments.

[0082] The starting unit 110 is used to start the EVS rendering engine of the target vehicle in response to a target rendering request initiated by a target application to the target vehicle;

[0083] The preprocessing unit 111 is used to obtain the image to be rendered through the EVS rendering engine, and preprocess the image to be rendered to obtain a target image;

[0084] The rendering unit 112 is used to initialize the target algorithm library, and transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image;

[0085] The display unit 113 is used to send the rendered image to the target application for display through the EVS rendering engine.

[0086] It can be seen from the above technical scheme that the present invention can respond to a target rendering request initiated by a target application to a target vehicle, start the EVS rendering engine of the target vehicle, obtain the image to be rendered through the EVS rendering engine, and pre-process the image to be rendered to obtain the target image, transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image, and send the rendered image to the target application for display, thereby decoupling the rendering logic and display logic of the vehicle AVM based on the EVS rendering engine, and the modular processing mechanism effectively improves the performance and flexibility of the vehicle AVM system.

[0087] like Figure 3 , which is a schematic diagram of the structure of a computer device of a preferred embodiment of the present invention for implementing the rendering and display method of the vehicle AVM.

[0088] The computer device 1 may include a memory 12 , a processor 13 and a bus, and may also include a computer program stored in the memory 12 and executable on the processor 13 , such as a rendering and display program of the vehicle AVM.

[0089] Those skilled in the art will appreciate that the schematic diagram is merely an example of the computer device 1 and does not constitute a limitation on the computer device 1. The computer device 1 may be a bus-type structure or a star-type structure. The computer device 1 may also include more or less other hardware or software than shown in the diagram, or a different arrangement of components. For example, the computer device 1 may also include input and output devices, network access devices, etc.

[0090] It should be noted that the computer device 1 is only an example, and other existing or future electronic products that are suitable for the present invention should also be included in the protection scope of the present invention and included here by reference.

[0091] Among them, the memory 12 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 12 can be an internal storage unit of the computer device 1, such as a mobile hard disk of the computer device 1. In other embodiments, the memory 12 can also be an external storage device of the computer device 1, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the computer device 1. Further, the memory 12 can also include both an internal storage unit of the computer device 1 and an external storage device. The memory 12 can not only be used to store application software and various types of data installed in the computer device 1, such as the code of the rendering and display program of the vehicle AVM, but also can be used to temporarily store data that has been output or is to be output.

[0092] In some embodiments, the processor 13 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and a combination of various control chips. The processor 13 is the control core (Control Unit) of the computer device 1, and uses various interfaces and lines to connect the various components of the entire computer device 1, and executes or executes the programs or modules stored in the memory 12 (for example, the rendering and display programs of the vehicle AVM, etc.), and calls the data stored in the memory 12 to execute various functions of the computer device 1 and process data.

[0093] The processor 13 executes the operating system of the computer device 1 and various installed applications. The processor 13 executes the applications to implement the steps of the above-mentioned rendering and display method embodiments of the vehicle AVM, for example Figure 1 Steps shown.

[0094] Exemplarily, the computer program may be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 13 to implement the present invention. The one or more modules / units may be a series of computer-readable instruction segments capable of implementing specific functions, which are used to describe the execution process of the computer program in the computer device 1. For example, the computer program may be divided into a startup unit 110, a preprocessing unit 111, a rendering unit 112, and a display unit 113.

[0095] The above-mentioned integrated unit implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, and includes a number of instructions for enabling a computer device (which can be a personal computer, a computer device, or a network device, etc.) or a processor to execute the part of the rendering and display method of the vehicle AVM described in each embodiment of the present invention.

[0096] If the module / unit integrated in the computer device 1 is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware devices through a computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of each of the above-mentioned method embodiments can be implemented.

[0097] The computer program includes computer program code, which may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory, etc.

[0098] Furthermore, the computer-readable storage medium may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to the use of the blockchain node, etc.

[0099] The blockchain referred to in this invention is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0100] The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 The bus is represented by only one straight line, but it does not mean that there is only one bus or one type of bus. The bus is configured to realize the connection and communication between the memory 12 and at least one processor 13, etc.

[0101] Although not shown, the computer device 1 may also include a power source (such as a battery) for supplying power to each component. Preferably, the power source may be logically connected to the at least one processor 13 through a power management device, so that the power management device can realize functions such as charging management, discharging management, and power consumption management. The power source may also include any components such as one or more DC or AC power sources, recharging devices, power failure detection circuits, power converters or inverters, power status indicators, etc. The computer device 1 may also include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

[0102] Furthermore, the computer device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is usually used to establish a communication connection between the computer device 1 and other computer devices.

[0103] Optionally, the computer device 1 may further include a user interface, which may be a display, an input unit (such as a keyboard), or a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touch device. The display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the computer device 1 and to display a visual user interface.

[0104] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited to this structure.

[0105] It can be understood by those skilled in the art that Figure 3 The structure shown does not constitute a limitation on the computer device 1, and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0106] Combination Figure 1 The memory 12 in the computer device 1 stores a plurality of instructions to implement a method for rendering and displaying a vehicle AVM, and the processor 13 can execute the plurality of instructions to implement:

[0107] In response to a target rendering request initiated by a target application to a target vehicle, starting an EVS rendering engine of the target vehicle;

[0108] Acquire the image to be rendered through the EVS rendering engine, and pre-process the image to be rendered to obtain a target image;

[0109] Initialize a target algorithm library, and transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image;

[0110] The rendered image is sent to the target application for display via the EVS rendering engine.

[0111] Specifically, the specific implementation method of the processor 13 for the above instructions can refer to Figure 1 The description of the relevant steps in the corresponding embodiments will not be repeated here.

[0112] It should be noted that the data involved in this case were all obtained legally.

[0113] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.

[0114] The present invention can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present invention can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present invention can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0115] 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 modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0116] In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional modules.

[0117] It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0118] Therefore, no matter from which point of view, the embodiments should be regarded as illustrative and non-restrictive, and the scope of the present invention is limited by the appended claims rather than the above description, so it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims are included in the present invention. Any attached figure mark in the claims should not be regarded as limiting the claims involved.

[0119] In addition, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the present invention can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

[0120] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solution of the present invention can be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present invention.

Claims

1. A method for rendering and displaying an AVM of a vehicle, characterized in that: The rendering and display method of the vehicle AVM includes: In response to a target rendering request initiated by a target application to a target vehicle, starting an EVS rendering engine of the target vehicle; Acquire the image to be rendered through the EVS rendering engine, and pre-process the image to be rendered to obtain a target image; Initialize a target algorithm library, and transmit the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image; The rendered image is sent to the target application for display via the EVS rendering engine.

2. The method for rendering and displaying the vehicle AVM according to claim 1, characterized in that: The EVS rendering engine includes at least one interface, each of which defines the format of data exchange, parameters of rendering requests and callback mechanism; Each interface is used for the application to call the corresponding algorithm library; Each algorithm library includes at least one algorithm for executing a preset function.

3. The vehicle AVM rendering and display method as claimed in claim 1, characterized in that: The obtaining of the image to be rendered by the EVS rendering engine comprises: The image data transmitted by the image acquisition device through the hardware abstraction layer is received by the EVS rendering engine as the image to be rendered.

4. The vehicle AVM rendering and display method as claimed in claim 1, characterized in that: Before initializing the target algorithm library, the method further includes: Acquire the interface called by the target application from the interface provided by the EVS rendering engine as the target interface; An algorithm library corresponding to the target interface is obtained as the target algorithm library.

5. The vehicle AVM rendering and display method as claimed in claim 1, characterized in that: The step of transmitting the target image to the target algorithm library for rendering to obtain a rendered image through the EVS rendering engine includes: The image Buffer corresponding to the target image is transmitted to the target algorithm library through the EVS rendering engine for rendering to obtain the rendered image.

6. The vehicle AVM rendering and display method as claimed in claim 1, characterized in that: The sending the rendered image to the target application for display through the EVS rendering engine includes: The rendered image is sent to the target application through the EVS rendering engine via a display queue for display.

7. The vehicle AVM rendering and display method as claimed in claim 1, characterized in that: The method further comprises: When receiving a function extension request, determining a new algorithm library according to the function extension request; An extended interface corresponding to the newly added algorithm library is configured for the EVS rendering engine.

8. A rendering and display device for an on-board AVM, characterized in that: The rendering and display device of the vehicle AVM includes: A starting unit, configured to start an EVS rendering engine of a target vehicle in response to a target rendering request initiated by a target application to the target vehicle; A preprocessing unit, used for acquiring an image to be rendered through the EVS rendering engine, and preprocessing the image to be rendered to obtain a target image; A rendering unit, used for initializing a target algorithm library, and transmitting the target image to the target algorithm library through the EVS rendering engine for rendering to obtain a rendered image; A display unit is used to send the rendered image to the target application for display through the EVS rendering engine.

9. A computer device, characterized in that: The computer device comprises: a memory storing at least one instruction; and A processor executes instructions stored in the memory to implement the rendering and display method of the vehicle AVM 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 at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement the rendering and display method of the vehicle AVM as described in any one of claims 1 to 7.

Images