Video data transmission and display method and device, equipment and storage medium

Abstract

The invention discloses a video data transmission and display method and device, equipment and a storage medium. When an Android system container generates video data to be projected, in the container, a Graloc module is used for creating a graphic buffer area, and the video data is written into the graphic buffer area. And if the video data is instrument information, exporting the video data in the buffer area as a DMA-BUF object. And storing the object into a shared memory, and sharing the object in the shared memory into a Linux system container which shares bottom hardware resources and a Linux kernel with the Android system container through a DRM (Digital Rights Management) interface by utilizing a central control system. And in the Linux system container, decoding and rendering the DMA-BUF object to obtain a display video frame, and outputting the display video frame to a corresponding instrument screen for display. According to the invention, redundant configuration is eliminated, the cost and the system load are reduced, and meanwhile, the cross-system video data transmission efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent cockpit, in particular to a video data transmission and display method and device, equipment and storage medium. BACKGROUND

[0002] With the rapid development of the intelligent automobile industry, the vehicle-mounted cockpit has evolved into a highly integrated comprehensive service platform, integrating multi-core functions such as central control entertainment, navigation guidance, voice interaction, instrument data display, etc., and puts forward higher requirements for multi-system collaborative operation and data transmission efficiency. Under such background, the traditional technical scheme exposes many limitations: in order to meet the independent operation requirements of different functions, the industry generally adopts a separated architecture of "multiple independent operating systems + dedicated hardware platform", that is, each core function corresponds to a set of independent operating system and is deployed on a dedicated hardware, which directly leads to the problem of repeated configuration of hardware resources and overall resource redundancy of the system. At the same time, the lack of unified underlying collaborative foundation among independent operating systems makes the communication link design between systems complicated, further restricting the overall operation efficiency of the cockpit system.

[0003] Therefore, how to improve the multi-system collaborative operation efficiency, reduce hardware resource redundancy, and at the same time improve the cross-system video data transmission efficiency and reduce system load is a technical problem that needs to be solved by those skilled in the art. SUMMARY

[0004] Based on the above problems, the present application provides a video data transmission and display method, device, equipment and storage medium, which can improve the transmission efficiency of cross-system video data, effectively reduce the system load and hardware resource redundancy, and at the same time improve the multi-system collaborative operation efficiency.

[0005] The embodiments of the present application disclose the following technical solutions:

[0006] A video data transmission and display method applied to a vehicle-mounted intelligent system of a target vehicle, the vehicle-mounted intelligent system comprising a central control system and a pre-built vehicle-mounted dual-system collaborative architecture, the vehicle-mounted dual-system collaborative architecture comprising an Android system container and a Linux system container, the Android system container and the Linux system container sharing underlying hardware resources and a Linux kernel, the method comprising:

[0007] When the Android system container generates video data to be projected, a graphics buffer is created in the Android system container using a graphics memory allocator (Gralloc) module, and the video data to be projected is written into the graphics buffer;

[0008] If the video data to be projected is instrument information, the video data in the graphic buffer is exported as a direct memory access buffer (DMA-BUF) object;

[0009] The DMA-BUF object is stored in shared memory, and the DMA-BUF object in the shared memory is shared to the Linux system container through a digital rights management (DRM) interface by the central control system;

[0010] In the Linux system container, the DMA-BUF object is decoded and rendered to obtain a display video frame;

[0011] In the Linux kernel, the Linux system container-bound instrument screen is determined, and the display video frame is output to the Linux system container-bound instrument screen for display; the instrument screen has been bound to the Linux system container through an instrument screen display device node, and the binding relationship is realized by relying on the Linux kernel.

[0012] In a possible implementation, the process of building the vehicle-mounted dual-system collaborative architecture includes:

[0013] An initial Android system container and an initial Linux system container are virtually generated on a Linux kernel in a host computer of the target vehicle; the host computer is deployed in a vehicle-mounted intelligent cockpit of the target vehicle;

[0014] The initial Android system container is system-installed and service-configured to obtain the Android system container, and the initial Linux system container is system-installed and service-configured to obtain the Linux system container;

[0015] A communication network between the Android system container and the Linux system container is configured to obtain the vehicle-mounted dual-system collaborative architecture.

[0016] In a possible implementation, the process of system-installing and service-configuring the initial Android system container to obtain the Android system container includes:

[0017] An Android system image is installed in the initial Android system container, and a graphic display service is configured to obtain the Android system container.

[0018] In a possible implementation, the process of system-installing and service-configuring the initial Linux system container to obtain the Linux system container includes:

[0019] installing a lightweight Linux system in the initial Linux system container and configuring a display service to obtain the Linux system container.

[0020] In a possible implementation, the method further includes:

[0021] If the video data to be projected is entertainment content, determining an entertainment screen bound to the Android system container in the Linux kernel, and outputting the video data to the entertainment screen bound to the Android system container for display; the entertainment screen has been bound to the Android system container through an entertainment screen display device node, and the binding relationship is implemented by relying on the Linux kernel.

[0022] A video data transmission and display apparatus, the apparatus comprising:

[0023] A buffer creation unit configured to, when the Android system container generates video data to be projected, create a graphics buffer in the Android system container using a Gralloc module, and write the video data to be projected into the graphics buffer;

[0024] An export unit configured to, if the video data to be projected is instrument information, export the video data in the graphics buffer as a DMA-BUF object;

[0025] A storage unit configured to store the DMA-BUF object into shared memory;

[0026] A sharing unit configured to share the DMA-BUF object in the shared memory to the Linux system container through a DRM interface by the central control system;

[0027] A decoding and rendering unit configured to, in the Linux system container, decode and render the DMA-BUF object to obtain display video frames;

[0028] A first display unit configured to determine an instrument screen bound to the Linux system container in the Linux kernel, and output the display video frames to the instrument screen bound to the Linux system container for display; the instrument screen has been bound to the Linux system container through an instrument screen display device node, and the binding relationship is implemented by relying on the Linux kernel.

[0029] In a possible implementation, the apparatus further includes:

[0030] A container virtual unit is configured to use LXC technology on a Linux kernel in a host computer of the target vehicle to virtually generate an initial Android system container and an initial Linux system container; the host computer is deployed in an in-vehicle intelligent cockpit of the target vehicle.

[0031] A first system configuration unit is configured to perform system installation and service configuration on the initial Android system container to obtain the Android system container.

[0032] A second system configuration unit is configured to perform system installation and service configuration on the initial Linux system container to obtain the Linux system container.

[0033] A communication network configuration unit is configured to configure a communication network between the Android system container and the Linux system container to obtain the in-vehicle dual-system collaborative architecture.

[0034] In a possible implementation, the first system configuration unit is specifically configured to:

[0035] The initial Android system container is installed with an Android system image and configured with a graphical display service to obtain the Android system container.

[0036] A video data transmission and display device includes a memory, a processor, and a computer program stored in the memory and executable on the processor; when the processor executes the computer program, the video data transmission and display method described above is implemented.

[0037] A computer readable storage medium stores instructions; when the instructions are executed on a terminal device, the terminal device performs the video data transmission and display method described above.

[0038] Compared with the prior art, the present application has the following beneficial effects:

[0039] The application provides a video data transmission and display method, device, equipment and storage medium. Specifically, the method is applied to a vehicle-mounted intelligent system of a target vehicle, the system core comprising a central control system and a pre-built vehicle-mounted dual-system cooperative architecture, the architecture being composed of an Android system container and a Linux system container, and the two containers sharing underlying hardware resources and a same Linux kernel, while realizing efficient utilization of resources and guaranteeing system independence. When the video data transmission and display method provided in the application is executed, after the Android system container generates video data to be projected, a dedicated graphics buffer is first created in the container through a Graphics Memory Allocator (Gralloc) module, and the video data to be projected is written into the graphics buffer. If the video data to be projected is determined to be instrument information, the video data in the graphics buffer is further exported as a Direct Memory Access Buffer (DMA-BUF) object. Then, the DMA-BUF object is stored in a shared memory, and the central control system shares the DMA-BUF object in the shared memory to the Linux system container by means of a Digital Rights Management (DRM) interface. After receiving, the Linux system container decodes and renders the DMA-BUF object to generate a video frame that can be directly displayed. Finally, the generated display video frame is directly output to a corresponding instrument screen for display, and efficient transmission and accurate display of the video data are realized throughout the process. The application shares the underlying hardware resources and the Linux kernel through the vehicle-mounted dual-system cooperative architecture, without the need to configure independent hardware platforms for different functions, thereby eliminating the redundancy problem of repeated configuration of hardware resources and greatly reducing the hardware cost. At the same time, for cross-system video data transmission, a Gralloc module is used to create a graphics buffer and export a DMA-BUF object, and the shared memory and the DRM interface are combined to realize direct sharing of data, thereby significantly improving the cross-system video data transmission efficiency and effectively reducing the system load. BRIEF DESCRIPTION OF DRAWINGS

[0040] To make the technical solutions in the present application or prior art clearer, the accompanying drawings needed in the description of the embodiments or prior art will be briefly introduced. Obviously, the accompanying drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative effort based on these drawings.

[0041] Figure 1 A method flowchart of a video data transmission and display method provided in an embodiment of the present application;

[0042] Figure 2A structural schematic diagram of a video data transmission and display device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0043] To facilitate understanding of the technical solutions provided by the embodiments of the present application, the background art related to the embodiments of the present application will be described first.

[0044] With the continuous progress of intelligent automobile technology, the functions of the vehicle cabin system are increasingly rich, covering central control entertainment, navigation, voice interaction, instrument display and other applications. However, the traditional solution usually relies on multiple independent operating systems running on different hardware platforms, which leads to a series of problems, including redundant waste of resources, complexity of inter-system communication and low data transmission efficiency.

[0045] To solve this problem, a video data transmission and display method, device, equipment and storage medium are provided in the embodiments of the present application. The method is applied to a vehicle-mounted intelligent system of a target vehicle, the vehicle-mounted intelligent system includes a central control system and a pre-built vehicle-mounted dual-system collaborative architecture, the vehicle-mounted dual-system collaborative architecture includes an Android system container and a Linux system container, and the Android system container and the Linux system container share underlying hardware resources and a Linux kernel. Specifically, after the Android system container generates video data to be projected, a graphics buffer is first created in the container by a Gralloc module, and the video data to be projected is written into the graphics buffer. If it is determined that the video data to be projected is instrument information, the video data in the graphics buffer is further exported as a DMA-BUF object. Subsequently, the DMA-BUF object is first stored in shared memory, and then the DMA-BUF object in the shared memory is shared to the Linux system container by the central control system through a DRM interface. After receiving, the Linux system container performs decoding and rendering processing on the DMA-BUF object to generate a video frame that can be directly displayed. Finally, the generated display video frame is directly output to the corresponding instrument screen for display. The vehicle-mounted dual-system collaborative architecture proposed in the present application shares the underlying hardware resources and the Linux kernel, avoiding the need to configure independent hardware platforms for different functional modules, fundamentally eliminating the redundancy problem caused by repeated configuration of hardware resources, and significantly reducing hardware costs. In addition, in terms of cross-system video data transmission, the Gralloc module is used to create a graphics buffer and export a DMA-BUF object, and shared memory and a DRM interface are used to realize efficient direct sharing of data. This innovative method not only significantly improves the cross-system video data transmission efficiency, but also effectively reduces system load and improves overall performance.

[0046] With reference to the drawings of the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described, obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all the other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0047] Referring to Figure 1 , the figure is a method flowchart of a video data transmission and display method provided by the embodiments of the present application, the method is applied to a vehicle-mounted intelligent system of a target vehicle. The vehicle-mounted intelligent system takes a central control system as a collaborative core, and is equipped with a pre-built vehicle-mounted dual-system collaborative architecture. The core design of the architecture is to build an Android system container and a Linux system container which are independent of each other and work collaboratively by using Linux container (LXC) technology. The two system containers do not occupy independent hardware resources and kernels respectively, but share the same underlying hardware platform (such as a system on chip (SOC) chip, memory, storage, etc.) and unified Linux kernel based on the virtualization characteristics of LXC technology, without the need to configure dedicated hardware and independent kernels for central control functions and instrument display functions. This architecture design not only guarantees the resource isolation and independent stability of the two system containers in the running process by means of the Namespaces and Cgroups technologies of the Linux kernel, but also avoids the problems of repeated configuration of hardware resources and redundant occupation of kernels in traditional multi-system solutions, laying a foundation for efficient cross-system transmission of subsequent video data.

[0048] As Figure 1 indicated, the video data transmission and display method can include steps S101-S105:

[0049] S101: When the Android system container generates video data to be projected, a graphics buffer is created in the Android system container using a Gralloc module, and the video data to be projected is written into the graphics buffer.

[0050] To realize efficient storage and subsequent cross-system zero-copy transmission of video data, when the Android system container (as the main control entertainment system host) completes the collection and rendering of the to-be-screened video data (such as navigation map, driving assistance prompt, and other contents that need to be synchronized to the instrument screen), it will start the core component Gralloc module inside the container. As a key tool responsible for the management of the graphics buffer in the Android system, the module can accurately create an adapted graphics buffer according to the resolution, pixel format, frame rate, and other core parameters of the to-be-screened video data, ensuring that the buffer and the data characteristics are perfectly matched, and laying a hardware-level adaptation foundation for subsequent zero-copy transmission. After the creation of the graphics buffer is completed, the Android system container will directly write the rendered to-be-screened video data into the exclusive buffer, completing the preliminary solidification storage of the data. This process does not require reliance on external storage media or additional data format conversion steps, which can maximize the preservation of the original integrity of the video data, avoid quality loss or delay caused by format conversion during transmission, and prepare for the subsequent export of DMA-BUF objects and the realization of cross-system direct sharing, thereby reducing intermediate data transmission losses from the source and ensuring the efficiency of the overall transmission link.

[0051] S102: If the to-be-screened video data is instrument information, the video data in the graphics buffer is exported as a DMA-BUF object.

[0052] To realize cross-system zero-copy transmission of video data and avoid the efficiency loss and load pressure caused by traditional data copying, after the Android system container completes the storage of the to-be-screened video data, it will first accurately determine the data type. If the to-be-screened video data is identified as instrument information (such as navigation path, driving status prompt, vehicle core parameters, etc.) that needs to be synchronized to the instrument screen, the DMA-BUF export process will be started, and the video data stored in the graphics buffer created by the Gralloc module will be directly encapsulated and exported as a DMA-BUF object. The DMA-BUF object can serve as a "bridge" for data sharing, allowing video data to be directly accessed across systems without format conversion or intermediate storage, thereby avoiding the low efficiency and high system load caused by multiple memory copying in traditional transmission methods, and laying a solid foundation for subsequent data sharing through shared memory and DRM interface to the Linux system container.

[0053] S103: Store the DMA-BUF object in the shared memory, and share the DMA-BUF object in the shared memory to the Linux system container through the digital rights management (DRM) interface of the main control system.

[0054] To open up an efficient data transmission link between the Android system container and the Linux system container, after completing the export of the DMA-BUF object, the object is first stored in a memory space shared by the two systems. This shared memory serves as a special cross-container data transfer area, avoiding the problem of data stored in a single container private memory being inaccessible across systems, and laying a storage foundation for subsequent direct sharing. Subsequently, the central control system plays a coordinating and scheduling core role, starting the data sharing process through the DRM interface: as a standardized communication channel for adapting the underlying hardware and system container, the DRM interface can accurately identify the access permissions and communication needs of the Linux system container, and directly map the DMA-BUF object stored in the shared memory to the process address space of the Linux system container. The entire process does not require secondary copying or format conversion of the video data, achieving centralized storage and fast access of data through shared memory, and ensuring the security and compatibility of data transmission through the DRM interface, ensuring that the complete video data carried by the DMA-BUF object can be efficiently and losslessly transmitted to the Linux system container, providing high-quality data input for subsequent decoding and rendering.

[0055] S104: In the Linux system container, the DMA-BUF object is decoded and rendered to obtain a display video frame.

[0056] To ensure that the video data can accurately adapt to the display requirements of the instrument screen, when the Linux system container obtains the DMA-BUF object in the shared memory through the DRM interface, a targeted decoding and rendering process is started. First, the Linux system container uses the built-in decoding module in combination with its own adapted display service (such as Wayland) to decode the video data encapsulated in the DMA-BUF object. Since the DMA-BUF object maintains the original storage format of the video data, the decoding process does not require additional format conversion, and can quickly restore the original video stream, avoiding data loss and efficiency waste. Subsequently, based on the resolution, refresh rate, and other hardware parameters of the instrument screen, the rendering module optimizes the decoded video data, including picture adaptation, frame rate synchronization, and other operations, converting it into a display video frame that meets the display standards of the instrument screen. The entire process relies on the real-time optimization mechanism of the Linux system container configured for the instrument display scenario, ensuring efficient and stable operation of the decoding and rendering links, which not only guarantees the clear quality and format adaptation of the display video frame, but also meets the real-time requirements of video data display in the vehicle-mounted scenario, preparing for subsequent accurate output to the instrument screen.

[0057] S105: In the Linux kernel, determine the instrument screen bound to the Linux system container, and output the display video frame to the instrument screen bound to the Linux system container for display.

[0058] To ensure that the display video frame can be accurately and efficiently output to the instrument screen, the present application completes the core configuration based on the hardware management capability of the Linux kernel during the system initialization phase: relying on the device driver framework of the Linux kernel, a dedicated display device node (such as / dev / dri / card1) is allocated for the instrument screen, and the node is associated with the underlying DRM driver corresponding to the instrument screen, and then through the namespace permission mapping mechanism of the kernel, the device node is brought into the legal access range of the Linux system container, thereby establishing a fixed binding relationship between the Linux system container and the instrument screen. With the help of the hardware communication link maintained by the kernel, the binding relationship realizes the specialization and stabilization of data transmission, and avoids path conflicts or hardware adaptation problems from the root. When the Linux system container completes decoding and rendering of the DMA-BUF object, generates a display video frame that meets the display standard of the instrument screen, and initiates a display request directly through the pre-bound device node, the Linux kernel quickly responds and schedules hardware resources through the DRM driver, so that the video frame data does not need to go through additional forwarding or adaptation links, and reaches the instrument screen in the optimal path and is displayed in real time, fully meeting the core needs of real-time display and stability in the vehicle-mounted scenario.

[0059] Among them, the instrument screen has been bound with the Linux system container through the instrument screen display device node, and the binding relationship relies on the Linux kernel, and the Linux kernel completes the registration of the instrument screen display device node and the association with the DRM driver, and through the Namespaces technology, the Linux system container is given access permission to the device node, and the Cgroups technology is used to guarantee resource isolation and stable scheduling when the container accesses the device node.

[0060] Based on the content of S101-S105, it can be known that the method is applied to a vehicle-mounted intelligent system of a target vehicle, the system is composed of a central control system and a preset vehicle-mounted dual-system collaborative architecture, and the latter includes an Android system container and a Linux system container. The architecture realizes an efficient data processing flow by sharing underlying hardware resources and a Linux kernel. When the Android system container generates video data to be projected, a Gralloc module is used to create a graphic buffer and write the video data. If the data is instrument information, the instrument information is exported as a DMA-BUF object and stored in shared memory. Then, the central control system shares the DMA-BUF object to the Linux system container through a DRM interface, and the Linux system container subsequently decodes and renders the object, and finally outputs generated display video frames to a bound instrument screen for display. The vehicle-mounted dual-system collaborative architecture is adopted in the application, underlying hardware resources and a Linux kernel are shared, the need for configuring independent hardware platforms for different functions is avoided, thereby eliminating the repeated configuration of hardware resources and greatly reducing hardware costs. In addition, for cross-system video data transmission, a graphic buffer is created through a Gralloc module and a DMA-BUF object is exported, and shared memory and a DRM interface are combined to realize direct data sharing, which significantly improves the video data transmission efficiency and effectively reduces the system load.

[0061] In a possible implementation, the process of building the vehicle-mounted dual-system collaborative architecture includes steps A1-A3.

[0062] A1: An initial Android system container and an initial Linux system container are virtually deployed on a Linux kernel in a host computer in the target vehicle by using LXC technology; the host computer is deployed in a vehicle-mounted intelligent cabin of the target vehicle.

[0063] In the process of building the vehicle-mounted dual-system collaborative architecture, the host computer deployed in the vehicle-mounted intelligent cabin of the target vehicle is taken as the basis, and two independent initial system containers, namely, an initial Android system container and an initial Linux system container, are virtually deployed on the original Linux kernel of the host computer by relying on LXC technology. The two initial containers do not occupy independent kernel resources, but share the same Linux kernel of the host computer based on the light-weight virtualization feature of LXC technology, and do not need to configure an independent kernel for each container, thereby reducing kernel redundancy from the root of the architecture. Meanwhile, the two containers share the underlying hardware resources of the host computer, including SOC chips, memories, storage devices and other core hardware, and do not need to separately deploy dedicated hardware platforms for the central control and instrument functions.

[0064] A2: system installation and service configuration are performed on the initial Android system container to obtain the Android system container, and system installation and service configuration are performed on the initial Linux system container to obtain the Linux system container.

[0065] After the two initial system containers are virtualized, customized configuration needs to be performed on the two virtualized initial system containers respectively: for the initial Android system container, installation and deployment of an Android operating system image are completed, a graphic display service (such as SurfaceFlinger), necessary drivers and a central control entertainment related application are configured, a system startup process is optimized to reduce resource occupation, and finally an Android system container capable of stably running a central control function is formed; for the initial Linux system container, a lightweight Linux operating system image is installed, a real-time display service (such as Wayland) and related drivers and applications suitable for instrument display are configured, and the system is ensured to have high stability and real-time response capability, and finally a Linux system container for instrument display is obtained. In this configuration process, the two containers always maintain a shared state of underlying hardware resources and a Linux kernel, and only functional differentiation is achieved through configuration, without changing the underlying logic of resource sharing.

[0066] A3: a communication network between the Android system container and the Linux system container is configured to obtain the vehicle-mounted dual-system collaborative architecture.

[0067] Finally, to realize collaborative communication between the two system containers, a communication network between the two containers can also be configured, including a data transmission channel based on a named pipe, shared memory and other mechanisms, and a network link for guaranteeing command transmission and state synchronization, to ensure that the central control system and the instrument system can efficiently interact. At this point, through LXC technology construction, customized configuration and communication network construction, a vehicle-mounted dual-system collaborative architecture is formed, which shares underlying resources and a kernel, has independent functions and collaborative communication, realizes efficient use of resources, and guarantees running isolation and stability of the two containers through Linux kernel Namespaces and Cgroups technology.

[0068] In a possible implementation, in step A2, system installation and service configuration are performed on the initial Android system container to obtain the Android system container, including:

[0069] An Android system image is installed in the initial Android system container, and a graphic display service (such as SurfaceFlinger) is configured to obtain the Android system container.

[0070] In a possible implementation, the system installation and service configuration on the initial Linux system container in step A2 obtain the Linux system container, including:

[0071] In the initial Linux system container, a lightweight Linux system is installed and a display service (such as Wayland) is configured, to obtain the Linux system container.

[0072] In a possible implementation, the method further includes a dedicated display logic for entertainment video data, to implement functional differentiation adaptation and efficient output.

[0073] When the Android system container generates video data to be projected, after completing data type determination, if the video data is identified as entertainment content (such as multimedia films, music visual screen, entertainment application interface, etc.), a cross-system sharing process does not need to be performed, and a local display output mechanism is directly started in the Linux kernel to determine an entertainment screen bound to the Android system container. The entertainment screen has a fixed binding relationship with the Android system container through a dedicated entertainment screen display device node (such as / dev / dri / card0), and the binding relationship is implemented by relying on a shared Linux kernel, and the Linux kernel completes registration and DRM driver association of the entertainment screen display device node, gives the Android system container access permission to the device node by using a Namespaces technology, and guarantees resource isolation and stable scheduling of the container when accessing the device node by using a Cgroups technology, and at the same time, hardware adaptation and permission configuration are completed.

[0074] Based on this, the Android system container directly outputs the generated entertainment video data to the corresponding entertainment screen through the pre-bound device node. This design fully utilizes the functional attribute of the Android system container as a central control entertainment system host, avoids unnecessary loss caused by cross-container transmission of entertainment data, and guarantees the fluency and real-time performance of entertainment content display. In addition, through the dedicated binding mode of the device node, the display link separation of the entertainment screen and the instrument screen is implemented by relying on the underlying support of the Linux kernel, to ensure the independence and accuracy of video data transmission and display in the two types of scenes.

[0075] Referring to Figure 2 , Figure 2 FIG. 1 is a structural schematic diagram of a video data transmission and display device provided by an embodiment of the present application. As shown in Figure 2 FIG. 1, the video data transmission and display device includes:

[0076] The buffer creating unit 201 is configured to create a graphic buffer in the Android system container by using a Gralloc module when the Android system container generates video data to be projected, and write the video data to be projected into the graphic buffer.

[0077] The exporting unit 202 is configured to export the video data in the graphic buffer as a DMA-BUF object if the video data to be projected is instrument information.

[0078] The storing unit 203 is configured to store the DMA-BUF object into a shared memory.

[0079] The sharing unit 204 is configured to share the DMA-BUF object in the shared memory to the Linux system container by using a DRM interface of the central control system.

[0080] The decoding and rendering unit 205 is configured to decode and render the DMA-BUF object to obtain display video frames in the Linux system container.

[0081] The first display unit 206 is configured to determine an instrument screen bound to the Linux system container in a Linux kernel, and output the display video frames to the instrument screen bound to the Linux system container for display. The instrument screen has been bound to the Linux system container through an instrument screen display device node, and the binding relationship is realized by relying on the Linux kernel.

[0082] In a possible implementation, the apparatus further includes:

[0083] The container virtualizing unit is configured to virtually create an initial Android system container and an initial Linux system container by using an LXC technology on a Linux kernel in a host computer of the target vehicle. The host computer is deployed in an in-vehicle intelligent cockpit of the target vehicle.

[0084] The first system configuring unit is configured to perform system installation and service configuration on the initial Android system container to obtain the Android system container.

[0085] The second system configuring unit is configured to perform system installation and service configuration on the initial Linux system container to obtain the Linux system container.

[0086] The communication network configuring unit is configured to configure a communication network between the Android system container and the Linux system container to obtain the in-vehicle dual-system cooperative architecture.

[0087] In a possible implementation, the first system configuration unit is specifically configured to:

[0088] The Android system image is installed in the initial Android system container, and a graphic display service is configured, to obtain the Android system container.

[0089] In a possible implementation, the system installation and service configuration on the initial Linux system container to obtain the Linux system container comprises:

[0090] The lightweight Linux system is installed in the initial Linux system container, and a display service is configured, to obtain the Linux system container.

[0091] In a possible implementation, the apparatus further comprises:

[0092] The second display unit is configured to, if the video data to be projected is entertainment content, determine an entertainment screen to which the Android system container is bound in the Linux kernel, and output the video data to the entertainment screen to which the Android system container is bound for display; the entertainment screen is bound to the Android system container through an entertainment screen display device node, and the binding relationship is implemented based on the Linux kernel.

[0093] In addition, an embodiment of the present application further provides a video data transmission and display device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the video data transmission and display method as described above when executing the computer program.

[0094] In addition, an embodiment of the present application further provides a computer readable storage medium, which stores instructions, and the instructions enable a terminal device to perform the video data transmission and display method as described above when the instructions are executed on the terminal device.

[0095] The vehicle-mounted dual-system cooperative architecture is adopted in the embodiment of the present application, the underlying hardware resources and the Linux kernel are shared, the need for configuring independent hardware platforms for different functions is avoided, the problem of repeated configuration of hardware resources is effectively eliminated, and the hardware cost is greatly reduced. In addition, for the cross-system video data transmission problem, the Gralloc module is adopted to create a graphic buffer, and the video data is exported as a DMA-BUF object. In combination with the shared memory and DRM interface technology, the data is directly shared, the cross-system video data transmission efficiency is significantly improved, and the system load is effectively reduced.

[0096] The video data transmission and display method, apparatus, device, and storage medium provided in the present application are described in detail above. The embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts of each embodiment can be understood by referring to each other. For the apparatus disclosed in the embodiments, the description is relatively simple because it corresponds to the method disclosed in the embodiments. For the related parts, refer to the description of the method. It should be noted that, for those skilled in the art, some improvements and modifications can be made to the present application without departing from the principles of the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

[0097] It should be understood that, in the present application, “at least one” refers to one or more, and “multiple” refers to two or more. “And / or” is used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, “A and / or B” can represent three cases of only A, only B, and A and B existing at the same time, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the front and rear associated objects. “At least one of the following” or similar expressions means any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c can represent a, b, c, “a and b”, “a and c”, “b and c”, or “a and b and c”, where a, b, and c can be single or multiple.

[0098] It should also be noted that, in this document, relationship terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms “include”, “contain” or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement “including a…” does not exclude the presence of another identical element in the process, method, article or device including the element.

Claims

1. A video data transmission and display method, characterized in that, An in-vehicle intelligent system applied to a target vehicle, the in-vehicle intelligent system including a central control system and a pre-built in-vehicle dual-system collaborative architecture, the in-vehicle dual-system collaborative architecture including an Android system container and a Linux system container, the Android system container and the Linux system container sharing underlying hardware resources and the Linux kernel, the method including: When the Android system container generates video data to be projected, a graphics buffer is created in the Android system container using the Gralloc module of the graphics memory allocator, and the video data to be projected is written into the graphics buffer. If the video data to be projected is instrument information, then the video data in the graphics buffer is exported as a Direct Memory Access Buffer (DMA-BUF) object; The DMA-BUF object is stored in shared memory, and the central control system uses the Digital Rights Management (DRM) interface to share the DMA-BUF object in the shared memory to the Linux system container. In the Linux system container, the DMA-BUF object is decoded and rendered to obtain the displayed video frames; The instrument panel bound to the Linux system container is determined in the Linux kernel, and the display video frame is output to the instrument panel bound to the Linux system container for display; the instrument panel has been bound to the Linux system container through the instrument panel display device node, and this binding relationship is implemented based on the Linux kernel.

2. The method according to claim 1, characterized in that, The process of building the in-vehicle dual-system collaborative architecture includes: Using LXC technology on the Linux kernel of the host machine in the target vehicle, an initial Android system container and an initial Linux system container are virtualized; the host machine is deployed in the in-vehicle smart cockpit of the target vehicle; The initial Android system container is installed and service configured to obtain the Android system container, and the initial Linux system container is installed and service configured to obtain the Linux system container. Configure the communication network between the Android system container and the Linux system container to obtain the in-vehicle dual-system collaborative architecture.

3. The method according to claim 2, characterized in that, The process of installing and configuring services on the initial Android system container to obtain the Android system container includes: The Android system container is obtained by installing the Android system image and configuring the graphics display service in the initial Android system container.

4. The method according to claim 2, characterized in that, The process of installing and configuring services on the initial Linux system container to obtain the Linux system container includes: A lightweight Linux system is installed and a display service is configured in the initial Linux system container to obtain the Linux system container.

5. The method according to claim 1, characterized in that, The method further includes: If the video data to be projected is entertainment content, the entertainment screen bound to the Android system container is determined in the Linux kernel, and the video data is output to the entertainment screen bound to the Android system container for display; the entertainment screen has been bound to the Android system container through the entertainment screen display device node, and this binding relationship is implemented based on the Linux kernel.

6. A video data transmission and display device, characterized in that, The device includes: The buffer creation unit is used to create a graphics buffer in the Android system container using the Gralloc module when the Android system container generates video data to be projected, and to write the video data to be projected into the graphics buffer. The export unit, if the video data to be projected is instrument information, is used to export the video data in the graphics buffer as a DMA-BUF object; A storage unit is provided for storing the DMA-BUF object into shared memory. A shared unit is used to share the DMA-BUF object in the shared memory to the Linux system container via the DRM interface using the central control system; The decoding and rendering unit is used to decode and render the DMA-BUF object in the Linux system container to obtain display video frames; The first display unit is used to determine the instrument panel bound to the Linux system container in the Linux kernel and output the display video frame to the instrument panel bound to the Linux system container for display; the instrument panel has been bound to the Linux system container through the instrument panel display device node, and the binding relationship is implemented based on the Linux kernel.

7. The apparatus according to claim 6, characterized in that, The device further includes: A container virtualization unit is used to virtualize an initial Android system container and an initial Linux system container using LXC technology on the Linux kernel of the host machine in the target vehicle; the host machine is deployed in the in-vehicle smart cockpit of the target vehicle; The first system configuration unit is used to perform system installation and service configuration on the initial Android system container to obtain the Android system container; The second system configuration unit is used to perform system installation and service configuration on the initial Linux system container to obtain the Linux system container; The communication network configuration unit is used to configure the communication network between the Android system container and the Linux system container to obtain the in-vehicle dual-system collaborative architecture.

8. The apparatus according to claim 7, characterized in that, The first system configuration unit is specifically used for: The Android system container is obtained by installing the Android system image and configuring the graphics display service in the initial Android system container.

9. A video data transmission and display device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the video data transmission and display method as described in any one of claims 1-5.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the video data transmission and display method as described in any one of claims 1-5.

Images