A debugging test method and system for a camera interface of an in-vehicle infotainment system
By generating and sending LVDS data in the infotainment system through a camera simulation device, the problems of high cost of real cameras and expensive simulation equipment are solved, enabling efficient debugging and testing, and reducing equipment costs and time.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA FAW CO LTD
- Filing Date
- 2022-09-28
- Publication Date
- 2026-06-02
AI Technical Summary
During the debugging of infotainment systems, using real cameras is costly and simulation equipment is expensive, making it difficult to effectively debug multi-camera systems.
A camera simulation device is used to generate LVDS data by sending configuration information to a host computer, and then send it to the channel of the in-vehicle infotainment system to simulate the data information of a real camera.
It reduces the use of real cameras, lowers equipment costs, improves debugging and testing efficiency, and can simulate real-world environments, thus shortening debugging and testing time.
Smart Images
Figure CN115589479B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of in-vehicle infotainment system technology, specifically to a debugging and testing method and system for the camera interface of an in-vehicle infotainment system. Background Technology
[0002] During infotainment system debugging, if real cameras are used, the images output to the system will be realistic, and the output will be affected by the camera placement, failing to achieve the desired effect as a real vehicle. If camera system simulation devices are used, these devices are expensive, and as system requirements increase, the number of cameras also increases, further driving up the cost of simulation equipment.
[0003] Therefore, there is a need for a technical solution to address or at least mitigate the aforementioned shortcomings of existing technologies. Summary of the Invention
[0004] The purpose of this invention is to provide a debugging and testing method for the camera interface of an in-vehicle infotainment system to at least solve one of the above-mentioned technical problems.
[0005] One aspect of the present invention provides a debugging and testing method for a camera interface of an in-vehicle infotainment system, the debugging and testing method for the camera interface of the in-vehicle infotainment system comprising:
[0006] The host computer sends configuration information for each channel to the camera simulation device;
[0007] The camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel;
[0008] The camera simulation device sends each LVDS data to be transmitted to the corresponding channel of the in-vehicle infotainment system.
[0009] Optionally, the debugging and testing method for the camera interface of the in-vehicle infotainment system further includes:
[0010] The host computer obtains the channel configuration of the video channel configured by the user or obtains the pre-stored channel configuration as the configuration information.
[0011] Optionally, the camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel, including:
[0012] The camera simulation device acquires the configuration information of each channel transmitted by the host computer;
[0013] The camera simulation device loads the corresponding video file for each channel;
[0014] The camera simulation device processes the video file loaded for each channel to form LVDS data to be sent.
[0015] The camera simulation device sends each LVDS data to be transmitted to the corresponding channel according to the configuration information of each channel.
[0016] Optionally, the camera simulation device processes the video file loaded for each channel to form LVDS data to be sent, including:
[0017] The camera simulation device decodes the acquired video file to obtain streaming media data;
[0018] The camera simulation device performs secondary encoding on the decoded streaming media data to form LVDS total video data, which includes channel information;
[0019] The camera simulation device processes the total LVDS video data to obtain each LVDS data to be sent.
[0020] Optionally, the camera simulation device processes the total LVDS video data to obtain each LVDS data to be transmitted, including:
[0021] The camera simulation device decodes the total LVDS video data to obtain the video stream;
[0022] The camera simulation device splits the video stream according to the channel information to form LVDS data to be sent for each channel.
[0023] Optionally, the debugging and testing method for the camera interface of the in-vehicle infotainment system further includes:
[0024] The host computer obtains the changed configuration information;
[0025] The host computer reconfigures itself based on the changed configuration information to obtain the configuration information.
[0026] Optionally, the camera simulation device loads a corresponding video file for each channel, which is a real historical video file acquired by the car during its driving process.
[0027] This application also provides a debugging and testing system for a camera interface of an in-vehicle infotainment system. The debugging and testing system for the camera interface of an in-vehicle infotainment system includes a host computer and a camera simulation device. The camera simulation device is connected to the host computer. The debugging and testing system for the camera interface of an in-vehicle infotainment system includes the host computer and the camera simulation device working together to implement the debugging and testing method for the camera interface of an in-vehicle infotainment system as described above.
[0028] Optionally, the camera simulation device communicates with the host computer through one or more of the following methods:
[0029] The camera simulation device communicates with the host computer via a single / multi-channel PCI-e interface;
[0030] The camera simulation device communicates with the host computer via a single / multi-channel high-speed Ethernet.
[0031] The camera simulation device communicates with the host computer via single / multi-channel high-speed USB.
[0032] Optionally, the camera simulation device includes a simulation device SDK and a simulation device, wherein the simulation device SDK is used to implement the following functions:
[0033] Obtain the configuration information of each channel transmitted by the host computer;
[0034] Load the corresponding video file for each channel;
[0035] The video files loaded for each channel are processed to form LVDS data to be sent;
[0036] The simulation device is used to decode the secondary encoded data;
[0037] The secondary decoded data is split according to the channel information to form video data corresponding to each channel.
[0038] Beneficial effects
[0039] The debugging and testing method for the camera interface of the in-vehicle infotainment system in this application has the following advantages:
[0040] (1) Applications can be debugged or tested without using actual cameras, which can reduce the camera consumption of the debugging or testing bench and improve the debugging and testing efficiency of camera applications.
[0041] (2) This method simulates the data information of a real camera. The video data that has been recorded or edited in advance can be sent to the infotainment system according to the actual situation. This can simulate the actual environment, reduce the debugging and testing time in the environment, and improve the debugging and testing efficiency.
[0042] (3) Compared with existing technologies, this method can reduce equipment costs and can be reused. Attached Figure Description
[0043] Figure 1 This is a flowchart illustrating a debugging and testing method for a camera interface of an in-vehicle infotainment system according to an embodiment of this application.
[0044] Figure 2 This is a schematic diagram of an electronic device capable of implementing a video transmission method for an in-vehicle infotainment system according to an embodiment of this application.
[0045] Figure 3 This is a schematic diagram illustrating the specific process of a debugging and testing method for a camera interface of an in-vehicle infotainment system according to an embodiment of this application.
[0046] Figure 4 This is a schematic diagram of a debugging and testing system for a camera interface of an in-vehicle infotainment system according to an embodiment of this application. Detailed Implementation
[0047] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below with reference to the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are some, but not all, embodiments of this application. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.
[0048] Figure 1 This is a flowchart illustrating a debugging and testing method for a camera interface of an in-vehicle infotainment system according to an embodiment of this application.
[0049] like Figure 1 The debugging and testing methods for the camera interface of the in-vehicle infotainment system shown include:
[0050] Step 1: The host computer sends the configuration information of each channel to the camera simulation device;
[0051] Step 2: The camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel;
[0052] Step 3: The camera simulation device sends each LVDS data to be sent to the corresponding channel of the in-vehicle infotainment system.
[0053] The debugging and testing method for the camera interface of the in-vehicle infotainment system in this application has the following advantages:
[0054] (1) Applications can be debugged or tested without using actual cameras, which can reduce the camera consumption of the debugging or testing bench and improve the debugging and testing efficiency of camera applications.
[0055] (2) This method simulates the data information of a real camera. The video data that has been recorded or edited in advance can be sent to the infotainment system according to the actual situation. This can simulate the actual environment, reduce the debugging and testing time in the environment, and improve the debugging and testing efficiency.
[0056] (3) Compared with existing technologies, this method can reduce equipment costs and can be reused.
[0057] In this embodiment, the debugging and testing method for the in-vehicle infotainment system camera interface further includes:
[0058] The host computer obtains the channel configuration of the video channel configured by the user or obtains the pre-stored channel configuration as the configuration information.
[0059] In this embodiment, the camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel, including:
[0060] The camera simulation device acquires the configuration information of each channel transmitted by the host computer;
[0061] The camera simulation device loads the corresponding video file for each channel;
[0062] The camera simulation device processes the video file loaded for each channel to form LVDS data to be sent.
[0063] The camera simulation device sends each LVDS data to be transmitted to the corresponding channel according to the configuration information of each channel.
[0064] In this embodiment, the camera simulation device processes the video file loaded for each channel to form LVDS data to be sent, including:
[0065] The camera simulation device decodes the acquired video file to obtain streaming media data;
[0066] The camera simulation device performs secondary encoding on the decoded streaming media data to form LVDS total video data, which includes channel information;
[0067] The camera simulation device processes the total LVDS video data to obtain each LVDS data to be sent.
[0068] In this embodiment, the camera simulation device processes the total LVDS video data to obtain each LVDS data to be sent, including:
[0069] The camera simulation device decodes the total LVDS video data to obtain the video stream;
[0070] The camera simulation device splits the video stream according to the channel information to form LVDS data to be sent for each channel.
[0071] In this embodiment, the debugging and testing method for the in-vehicle infotainment system camera interface further includes:
[0072] The host computer obtains the changed configuration information;
[0073] The host computer reconfigures itself based on the changed configuration information to obtain the configuration information.
[0074] In this embodiment, the camera simulation device loads a corresponding video file for each channel, which is a real historical video file acquired by the car during its driving process.
[0075] See Figure 4 This application also provides a debugging and testing system for a camera interface of an in-vehicle infotainment system. The system includes a host computer and a camera simulation device connected to the host computer. The host computer and the camera simulation device work together to implement the debugging and testing method for the camera interface of an in-vehicle infotainment system as described above.
[0076] In this embodiment, the camera simulation device communicates with the host computer through one or more of the following methods:
[0077] The camera simulation device communicates with the host computer via a single / multi-channel PCI-e interface;
[0078] The camera simulation device communicates with the host computer via a single / multi-channel high-speed Ethernet.
[0079] The camera simulation device communicates with the host computer via single / multi-channel high-speed USB.
[0080] Specifically, the camera simulation device of this application mainly functions to send real-time camera data streams to the in-vehicle infotainment system.
[0081] See Figure 4 The camera simulation device of this application communicates with the host computer through the high-speed communication module of the camera simulation device. It can be understood that the high-speed communication module of the camera simulation device is a logical proxy device of the camera simulation device on the host computer (PC). The communication methods of the module include, but are not limited to, the following: single / multi-channel PCI-e interface communication, single / multi-channel high-speed Ethernet, and single / multi-channel high-speed USB.
[0082] In this embodiment, the camera simulation device includes a simulation device SDK and a simulation device, wherein the simulation device SDK is used to implement the following functions:
[0083] Obtain the configuration information of each channel transmitted by the host computer;
[0084] Load the corresponding video file for each channel;
[0085] The video files loaded for each channel are processed to form LVDS data to be sent;
[0086] The simulation device is used to decode the secondary encoded data;
[0087] The secondary decoded data is split according to the channel information to form video data corresponding to each channel.
[0088] See Figure 3 In this embodiment, the debugging and testing method of the in-vehicle infotainment system camera interface of this application includes three processes: video channel configuration process, simulation start process, and simulation stop process.
[0089] In this embodiment, the video channel configuration process includes the host computer obtaining the channel configuration of the video channel configured by the user or obtaining the pre-stored channel configuration as the configuration information, and the host computer sending the configuration information of each channel to the camera simulation device.
[0090] In this embodiment, the simulation process includes the camera simulation device generating the LVDS data to be sent for each channel based on the configuration information of each channel. Specifically, after the user starts the simulation, the SDK loads the configured video files for multiple channels; decodes the corresponding video files and re-encodes the streaming media data, with the re-encoded data containing channel information; and sends the multi-channel data to the simulation device. After receiving the data, the simulation device decodes the multi-channel data, splits the data, re-encodes it into LVDS data, and sends it to the LVDS output interface of the corresponding channel.
[0091] In this embodiment, the process of stopping the simulation includes: after the user stops the simulation, the SDK will stop data transmission and secondary encoding of the data.
[0092] Understandably, during the simulation of debugging and testing methods for the camera interface of an in-vehicle infotainment system, if the number of camera simulation channels is increased or decreased, the three basic processes mentioned above can be flexibly combined, namely:
[0093] Reconfigure simulation information (Process 1) -> Stop simulation process (Process 3) -> Start simulation process (Process 2)
[0094] This application also provides a video transmission method for an in-vehicle infotainment system, which includes: a camera simulation device generating LVDS data to be transmitted for each channel based on the configuration information of each channel.
[0095] The camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel, including:
[0096] The camera simulation device acquires the configuration information of each channel transmitted by the host computer;
[0097] The camera simulation device loads the corresponding video file for each channel;
[0098] The camera simulation device processes the video file loaded for each channel to form LVDS data to be sent.
[0099] The camera simulation device sends each LVDS data to be transmitted to the corresponding channel according to the configuration information of each channel.
[0100] It is understandable that the above description of the method also applies to the description of the apparatus.
[0101] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to implement the above-described video transmission method for an in-vehicle infotainment system.
[0102] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, enables the implementation of the video transmission method for an in-vehicle infotainment system as described above.
[0103] Figure 2 This is an exemplary structural diagram of an electronic device capable of implementing the video transmission method for an in-vehicle infotainment system according to an embodiment of this application.
[0104] like Figure 2 As shown, the electronic device includes an input device 501, an input interface 502, a central processing unit 503, a memory 504, an output interface 505, and an output device 506. The input interface 502, central processing unit 503, memory 504, and output interface 505 are interconnected via a bus 507. The input device 501 and output device 506 are connected to the bus 507 via the input interface 502 and output interface 505, respectively, and thus connected to other components of the electronic device. Specifically, the input device 504 receives input information from the outside and transmits it to the central processing unit 503 via the input interface 502. The central processing unit 503 processes the input information based on computer-executable instructions stored in the memory 504 to generate output information, temporarily or permanently storing the output information in the memory 504, and then transmitting the output information to the output device 506 via the output interface 505. The output device 506 outputs the output information to the outside of the electronic device for user use.
[0105] In other words, Figure 2 The illustrated electronic device may also be implemented as including: a memory storing computer-executable instructions; and one or more processors, which can be coupled when executing the computer-executable instructions. Figure 1 The video transmission method described in the in-vehicle infotainment system.
[0106] In one embodiment, Figure 2 The electronic device shown can be implemented to include: a memory 504 configured to store executable program code; and one or more processors 503 configured to run the executable program code stored in the memory 504 to execute the video transmission method for the in-vehicle infotainment system in the above embodiments.
[0107] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0108] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0109] Computer-readable media include both permanent and non-permanent, removable and non-removable media, and information storage can be achieved by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, DVD or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.
[0110] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0111] Furthermore, it is clear that the word "comprising" does not exclude other units or steps. Multiple units, modules, or devices recited in the apparatus claims may also be implemented by a single unit or overall apparatus via software or hardware.
[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutively marked blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or the overall flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0113] In this embodiment, the processor may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.
[0114] Memory can be used to store computer programs and / or modules. The processor implements various functions of the device / terminal equipment by running or executing the computer programs and / or modules stored in the memory, and by accessing data stored in the memory. Memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area can store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). In addition, memory can include high-speed random access memory, and can also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0115] In this embodiment, if the modules / units integrated into the device / terminal equipment are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. Although this application discloses preferred embodiments as described above, it is not intended to limit this application. Any person skilled in the art can make possible changes and modifications without departing from the spirit and scope of this application. Therefore, the scope of protection of this application should be determined by the scope defined in the claims of this application.
[0116] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0117] Furthermore, it is clear that the word "comprising" does not exclude other units or steps. Multiple units, modules, or devices recited in the apparatus claims may also be implemented by a single unit or overall apparatus via software or hardware.
[0118] Although the present invention has been described in detail above with general descriptions and specific embodiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.
Claims
1. A method for debugging and testing the camera interface of an in-vehicle infotainment system, characterized in that, The debugging and testing methods for the camera interface of the in-vehicle infotainment system include: The host computer sends configuration information for each channel to the camera simulation device; The camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel; The camera simulation device sends each LVDS data to be transmitted to the corresponding channel of the in-vehicle infotainment system; The debugging and testing method for the camera interface of the in-vehicle infotainment system further includes: The host computer obtains the channel configuration of the video channel configured by the user or obtains the pre-stored channel configuration as the configuration information; The camera simulation device generates the LVDS data to be transmitted for each channel based on the configuration information of that channel, including: The camera simulation device acquires the configuration information of each channel transmitted by the host computer; The camera simulation device loads the corresponding video file for each channel; The camera simulation device processes the video file loaded in each channel to form LVDS data to be sent. The camera simulation device sends each LVDS data to be transmitted to the corresponding channel according to the configuration information of each channel; The camera simulation device processes the video file loaded in each channel to form LVDS data to be sent, including: The camera simulation device decodes the acquired video file to obtain streaming media data; The camera simulation device performs secondary encoding on the decoded streaming media data to form LVDS total video data, which includes channel information; The camera simulation device processes the total LVDS video data to obtain each LVDS data to be sent; The camera simulation device processes the total LVDS video data to obtain each LVDS data to be sent, including: The camera simulation device decodes the total LVDS video data to obtain the video stream; The camera simulation device splits the video stream according to the channel information to form LVDS data to be sent for each channel; The debugging and testing method for the camera interface of the in-vehicle infotainment system further includes: The host computer obtains the changed configuration information; The host computer reconfigures itself based on the changed configuration information to obtain the updated configuration information. The camera simulation device loads a corresponding video file for each channel, which is a real historical video file acquired during the car's driving process.
2. A debugging and testing system for a camera interface of an in-vehicle infotainment system, characterized in that, The debugging and testing system for the camera interface of the in-vehicle infotainment system includes a host computer and a camera simulation device. The camera simulation device is connected to the host computer, and the host computer and the camera simulation device work together to implement the debugging and testing method for the camera interface of the in-vehicle infotainment system as described in claim 1.
3. The debugging and testing system for the camera interface of an in-vehicle infotainment system as described in claim 2, characterized in that, The camera simulation device communicates with the host computer through one or more of the following methods: The camera simulation device communicates with the host computer via a single / multi-channel PCI-e interface; The camera simulation device communicates with the host computer via a single / multi-channel high-speed Ethernet. The camera simulation device communicates with the host computer via single / multi-channel high-speed USB.