Device for viewing content of automobile data recorder on screen of automobile infotainment device

Abstract

The invention discloses a device for checking the content of an automobile data recorder on a vehicle machine screen, which comprises a vehicle machine interface simulation module and an automobile data recorder communication module which are connected, the vehicle machine interface simulation module is connected with a vehicle machine, and the automobile data recorder communication module is connected with the automobile data recorder; wherein the vehicle machine interface simulation module is used for simulating a simulation intelligent equipment identity corresponding to a vehicle machine and performing data transmission with the vehicle machine, and the automobile data recorder communication module is used for acquiring video streaming data of an automobile data recorder and transmitting the video streaming data to the vehicle machine interface simulation module. The method has the advantage that the content of the automobile data recorder is presented on the vehicle machine.

Description

Technical Field

[0001] This invention relates to the field of intelligent vehicle electronics technology, and more specifically, to a device for viewing the contents of a dashcam on a vehicle's infotainment screen. Background Technology

[0002] With the continuous growth of car ownership, dashcams, as core in-vehicle electronic devices that ensure driving safety and preserve evidence of traffic scenarios, have become standard equipment in vehicles. To adapt to the interior space layout and aesthetic requirements, most dashcams on the market currently adopt a hidden installation design. They are usually not equipped with a visual display screen, or only have a very small and simple display module, and cannot directly realize video playback, preview, and export operations.

[0003] Due to the aforementioned hardware design limitations, existing dashcams generally adopt a "mobile app + Wi-Fi hotspot" interaction solution to meet users' needs for viewing recorded data. The standard operating procedure is as follows: First, activate the dashcam's Wi-Fi hotspot function. This hotspot is usually named with specific characters such as the device model or brand logo. Then, the user needs to access the Wi-Fi settings interface on their mobile phone, search for and connect to the aforementioned dedicated hotspot (a preset initial password is required). After successful connection, the user needs to open the dedicated mobile application that comes with the dashcam (such as the official app of the corresponding brand). Finally, through the interactive interface of this app, the user can complete operations such as browsing, playback, downloading, or exporting video files.

[0004] However, the existing solutions mentioned above have several technical shortcomings that urgently need to be addressed: First, the operation process is cumbersome and redundant, requiring users to switch between multiple scenarios such as device power on / off, mobile phone Wi-Fi settings, and app launch, resulting in a long interaction chain and a poor user experience; Second, the dashcam's accompanying app is a low-frequency application, used very infrequently by users, and is easily uninstalled or forgotten, requiring users to search for and download it again when needed, increasing operational costs; Third, when users change their mobile devices, they need to re-download and install the corresponding app, and some manufacturers of older dashcam models have stopped providing technical support for the accompanying app, causing the app to be incompatible with new system versions, and users to completely lose the ability to view data; Fourth, while driving, users need to be distracted by operating their mobile phones to connect to Wi-Fi and launch the app, which is not only inconvenient to operate but also poses a serious driving safety hazard, making it impossible to achieve safe and convenient viewing while driving. Furthermore, although some high-end car infotainment systems (hereinafter referred to as "vehicle infotainment systems") support USB video input, most mainstream vehicle infotainment systems only open specific protocol channels such as Apple CarPlay, Android Auto, Huawei HiCar, and Baidu CarLife, allowing only smart devices that comply with the protocol specifications to access. The USB video signals from ordinary dashcams cannot be directly recognized and displayed by the vehicle infotainment system, which prevents users from conveniently viewing the recorded content on the vehicle's large screen, further limiting the flexibility of existing dashcams. Summary of the Invention

[0005] To overcome the shortcomings of existing technologies, such as long app startup links, low application frequency, inconsistent app compatibility between new and old versions and dashcams and systems, and the inability of ordinary dashcam USB video signals to be directly recognized and displayed by the vehicle system, this invention provides a device for viewing dashcam content on a vehicle screen.

[0006] The technical solution of this invention is as follows: A device for viewing dashcam content on a vehicle infotainment screen includes a vehicle infotainment interface simulation module and a dashcam communication module connected together. The vehicle infotainment interface simulation module is connected to the vehicle infotainment system, and the dashcam communication module is connected to the dashcam. The vehicle interface simulation module is used to simulate the identity of the simulated smart device corresponding to the vehicle system and to transmit data with the vehicle system. The dashcam communication module is used to acquire the video stream data of the dashcam and transmit the video stream data to the vehicle interface simulation module.

[0007] Furthermore, in one embodiment, the vehicle interface simulation module is connected to the vehicle's infotainment system via a USB interface, which is either a USB Type-A interface or a USB Type-C interface, and the dashcam communication module is wirelessly connected to the dashcam.

[0008] Furthermore, in one embodiment, the vehicle interface simulation module has a built-in embedded processor and protocol stack firmware. Both the embedded processor and the protocol stack firmware are connected to the vehicle system via a USB interface, and are used to automatically identify the wired interaction protocols supported by the vehicle system and simulate the identity of the simulated smart device corresponding to the wired interaction protocol.

[0009] Furthermore, in one embodiment, the vehicle interface simulation module encapsulates the received video stream data into a media stream format supported by the wired interaction protocol, and pushes the media stream format to the vehicle system as the simulated smart device.

[0010] Furthermore, in one embodiment, the wired interaction protocol supported by the vehicle system includes at least one of Apple CarPlay, Android Auto, Huawei HiCar, and Baidu CarLife, and the vehicle system interface simulation module completes automatic protocol identification by parsing the USB handshake signal.

[0011] Furthermore, in one embodiment, the dashcam communication module has a built-in Wi-Fi chip and adopts a Wi-FiStation working mode. After the device is started, the dashcam communication module controls the Wi-Fi chip to automatically scan for nearby connectable dashcam Wi-Fi hotspots and simultaneously executes any of the following connection logics: firstly, it retrieves and calls the SSID and corresponding password of the last successfully connected device stored in its own memory, and automatically initiates a reconnection; if no historical connection record is stored or the reconnection fails, it scans and matches the dashcam Wi-Fi hotspot corresponding to the SSID preset by the device, and calls the preset password to automatically establish a wireless connection; if no preset SSID hotspot is matched, or the automatic connection fails, the device pushes a hotspot list to the vehicle's infotainment system through the vehicle interface simulation module, allowing the user to manually select the target dashcam Wi-Fi hotspot and enter the password to complete the connection; after the dashcam communication module establishes a wireless connection with the dashcam, it establishes a session with the dashcam through the IP layer communication protocol to obtain the video stream data.

[0012] Furthermore, in one embodiment, the dashcam communication module has a built-in Wi-Fi chip and adopts a Wi-Fi AP working mode. After the device is started, the dashcam communication module automatically creates a Wi-Fi hotspot with a fixed SSID and password. The dashcam adapted to the device has the fixed SSID and password of the device pre-written. After the dashcam is started, it periodically scans for surrounding hotspots through Wi-Fi. When it recognizes the Wi-Fi hotspot created by the device, it automatically initiates a connection request and completes authentication through the preset SSID and password. After the connection is established, the dashcam communication module establishes a session with the dashcam through the IP layer communication protocol and obtains the video stream data.

[0013] Furthermore, in one embodiment, the vehicle interface simulation module also includes a built-in video encoding unit, which is configured to: perform adaptive processing on the video stream data from the dashcam communication module; if the video stream data format already conforms to the requirements of the wired interaction protocol, then transmit the video stream data to the vehicle; if the video stream data format is incompatible with the wired interaction protocol, then first decode the video stream data to convert it into raw audio and video data, then optimize the raw audio and video data with H.264 or H.265 encoding according to the wired interaction protocol adaptation requirements, and finally encapsulate the processed video stream.

[0014] Furthermore, in one embodiment, the IP layer communication protocol includes at least one of the following: RTSP protocol, RTP protocol, HTTP protocol, a subset of ONVIF protocol, and other IP layer-based protocols.

[0015] Furthermore, in one embodiment, a user triggers an instruction through the vehicle-mounted infotainment interface. The instruction is transmitted via the vehicle-mounted infotainment system to the vehicle-mounted interface simulation module, where it is converted into a control signal recognizable by the dashcam. This signal is then transmitted to the dashcam via the dashcam communication module. After executing the instruction, the dashcam generates feedback data, which is sequentially sent to the dashcam communication module, the vehicle-mounted interface simulation module, and the vehicle-mounted infotainment system.

[0016] According to the above-described solution, the beneficial effects of this invention are as follows: by cooperating with the built-in vehicle interface simulation module and the dashcam communication module, it completely eliminates the reliance on a mobile phone as an intermediary, eliminating the need for cumbersome pairing and app operations, and achieving a minimalist experience of "direct access to dashcam content via vehicle system." Furthermore, the device can be plugged into the vehicle system via USB interface and automatically completes protocol recognition and Wi-Fi connection processes after power-on, making it extremely easy to adapt to. It is compatible with mainstream vehicle system protocols, adapting to existing commercially available dashcams and meeting the pre-installation customization needs of automakers, making it suitable for a wide range of scenarios. Users can directly perform operations such as previewing, playback, and screenshotting through the vehicle system interface without having to look down at their phones, significantly improving driving safety. Moreover, the hardware modification cost is low, making commercialization highly feasible, and it combines user experience with large-scale promotional value. Attached Figure Description

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

[0018] Figure 1 This is the framework of the device in this embodiment. Figure 1 ; Figure 2 This is the framework of the device in this embodiment. Figure 2 ; Figure 3 This is a schematic diagram of the working process of the device in this embodiment. Figure 1 ; Figure 4 This is a schematic diagram of the working process of the device in this embodiment. Figure 2 . Detailed Implementation

[0019] The present invention will now be further described with reference to the accompanying drawings and embodiments: like Figure 1 As shown, a device for viewing dashcam content on a vehicle infotainment screen includes a vehicle infotainment interface simulation module and a dashcam communication module connected together. The vehicle infotainment interface simulation module is connected to the vehicle infotainment system, and the dashcam communication module is connected to the dashcam. The vehicle infotainment interface simulation module is used to simulate the identity of the simulated smart device corresponding to the vehicle infotainment system and to transmit data with the vehicle infotainment system. The dashcam communication module is used to acquire video stream data from the dashcam and transmit the video stream data to the vehicle infotainment interface simulation module.

[0020] In this invention, the "simulated smart device identity" is simulated through a physical entity device (i.e., this device). Specifically, the vehicle interface simulation module constructs a "set of device identity identifiers that conforms to the vehicle's protocol requirements" through software configuration and protocol adaptation. Its core purpose is to allow the vehicle's infotainment system to recognize this device as a legitimate external smart device (such as a smartphone or dedicated screen mirroring device), thereby enabling data transmission and function calls. The specific structure and implementation process of this simulated identity are as follows: I. The simulated intelligent device identity consists of a set of standardized parameters stored in the Flash storage unit of the vehicle interface simulation module, and is bound one-to-one with the corresponding vehicle protocol, specifically including: Basic device identifiers: Simulate the model, brand, and hardware serial number (SN) of mainstream smart devices. For example, when adapting to the CarPlay protocol, simulate the device model, brand identifier, and unique hardware serial number of an iPhone; when adapting to the Huawei HiCar protocol, simulate the device model, brand identifier, and unique hardware serial number of a Huawei phone; ensure that the vehicle system recognizes the device in accordance with its preset device whitelist requirements.

[0021] Protocol adaptation parameters: The version number, communication rate, and data transmission port settings of the corresponding vehicle infotainment protocol are set to ensure compatibility with the vehicle infotainment protocol version.

[0022] Authentication Keys and Certificates: For encryption protocols, the built-in vehicle system uses compliant authentication keys or simulated certificates that are recognized by the vehicle system to avoid being identified as an illegal device through the vehicle system's authentication process.

[0023] Function Support List: Clearly inform the vehicle system of the function modules supported by this device, such as "video streaming", "command response", "status feedback", etc. For example, when adapting to the Baidu CarLife protocol, report the function identifiers of "video playback, screenshot storage, and historical file retrieval" so that the vehicle system can grant the corresponding operation permissions.

[0024] 2. Once the vehicle infotainment interface simulation module identifies the protocols supported by the vehicle infotainment system via the USB handshake signal, it will automatically call the corresponding protocol-bound simulation identity parameters. The specific process is as follows: After protocol recognition is complete, the embedded processor reads the simulated identity parameter set corresponding to the protocol from Flash and loads it into memory; it then sends a device authentication request to the vehicle's infotainment system, encapsulating the device's basic identifier, protocol adaptation parameters, and authentication key in the format required by the vehicle's protocol (e.g., CarPlay uses Apple's proprietary encryption format, and HiCar uses Huawei's proprietary encapsulation format). Upon receiving the authentication request, the vehicle's infotainment system verifies the legality of the identity parameters according to its own protocol logic (e.g., checking if the device model is in the supported list and if the authentication key matches). If the verification is successful, the vehicle's infotainment system marks this device as a "trusted external smart device" and opens the data transmission channel and function call permissions. During subsequent data transmission, the device continues to interact with the vehicle's infotainment system using this simulated identity, for example, by carrying the simulated device's identity identifier when pushing video streams, ensuring that the vehicle's infotainment system continuously recognizes the legality of the data source.

[0025] Third, to adapt to the protocol differences of different brands and models of vehicle infotainment systems, the simulated smart device identity supports dynamic parameter adjustment: The module has built-in identity parameter templates for multiple mainstream smart devices, and new device templates can be added through firmware upgrades (such as adding simulated identities adapted to "Xiaomi 14" and "Samsung Galaxy S24"), without modifying the hardware structure, thus ensuring compatibility with newly launched vehicle infotainment models. At the same time, the encapsulation format of the identity parameters strictly follows the publicly available specifications or industry-standard protocols of the corresponding vehicle infotainment systems, ensuring that the vehicle infotainment system can correctly parse the parameters and avoiding connection failures due to incompatible identity parameter formats.

[0026] In one embodiment, the device features an integrated design with a rectangular structure measuring 2cm × 2cm × 3cm. The outer shell is made of high-temperature resistant and flame-retardant PC material with a non-slip texture for easy plugging and unplugging. The core components of the device are a vehicle interface simulation module and a dashcam communication module. The vehicle interface simulation module handles multiple tasks, including protocol parsing and data encapsulation, and stores protocol stack firmware, temporary video data, and device configuration information. The dashcam communication module's built-in power amplifier enhances wireless signal coverage, ensuring stable communication even in complex in-vehicle environments (such as seat obstructions or electronic device interference). In practical applications, the user connects the device's connector to the corresponding interface on the vehicle's infotainment system. The dashcam communication module then establishes a wireless connection with the dashcam, forming a complete data transmission link. Upon startup, the vehicle interface simulation module immediately enters operational mode. It authenticates with the vehicle's infotainment system using a preset communication protocol, simulating the identity of a compatible smart device (such as an iPhone or tablet), enabling the system to recognize and establish a data transmission channel. Simultaneously, the dashcam communication module wirelessly scans the target dashcam, initiates a connection request, completes authentication, and acquires real-time video stream data (including live feeds and historical stored videos). This data is then transmitted to the vehicle interface simulation module via the onboard bus. Upon receiving the data, the simulation module performs format adaptation processing on the video stream to ensure compatibility with the vehicle's data transmission protocol, ultimately achieving clear display of the dashcam content on the vehicle's screen. In this embodiment, the device is compatible with mainstream brand vehicle infotainment systems and dashcams, requiring no complex configuration from the user; only a physical connection is needed to achieve functionality, significantly improving ease of operation.

[0027] The vehicle infotainment interface simulation module connects to the vehicle infotainment system via a USB interface, which can be either a USB Type-A or USB Type-C interface. The dashcam communication module connects wirelessly to the dashcam.

[0028] In one embodiment, the output of the vehicle interface simulation module of the device is equipped with a dual-interface adapter unit, integrating a USB Type-A interface and a USB Type-C interface respectively. The two interfaces achieve adaptive connection through a switch, eliminating the need for manual selection by the user. The USB Type-A interface adopts a standard A-type male connector design with 50μm gold plating on the pins, providing good conductivity and wear resistance. It supports the USB 2.0 transmission protocol, with a data transfer rate of up to 480Mbps. The USB Type-C interface features a reversible plug-and-play design and incorporates an EMC electromagnetic shielding chip to effectively resist electromagnetic interference in the vehicle environment. It also supports the USB 3.2 Gen1 protocol and is compatible with fast charging protocols. It can provide a stable 5V / 2A power supply to the device through the vehicle's infotainment system, ensuring uninterrupted operation during extended periods. To adapt to the USB interface layout of different vehicle models, users can adjust the interface angle according to the installation location of the vehicle's USB interface (e.g., on the front, side, or inside the storage compartment) to ensure a secure connection. In vehicle connectivity verification, the device successfully adapted to mainstream models such as the 2024 Toyota Highlander (equipped with a USB Type-A interface), the 2024 BYD Song PLUS DSM-i (equipped with a USB Type-C interface), and the 2024 Volkswagen Lavida (equipped with both Type-A and Type-C interfaces), achieving a 100% connection success rate, with no issues such as looseness or poor contact after connection. The wireless communication module between the dashcam and the dashcam utilizes Wi-Fi 6 technology, developed based on the IEEE 802.11ax standard, supporting OFDMA (Orthogonal Frequency Division Multiple Access) and MU-MIMO (Multi-User Multiple Input Multiple Output) technologies. It can establish a stable connection with a single dashcam simultaneously, avoiding interference from multiple devices. The wireless communication frequency band can automatically switch according to the actual scenario, prioritizing the 5GHz band in unobstructed environments inside the vehicle, offering fast transmission speeds, strong anti-interference capabilities, longer transmission distances, and stronger penetration. In this embodiment, the wireless communication also uses the WPA2 / WPA3 encryption protocol to perform high-strength encryption on the transmitted data, preventing the video data from being stolen or tampered with, and ensuring user privacy and security.

[0029] The vehicle infotainment interface simulation module integrates an embedded processor and protocol stack firmware. Both the embedded processor and protocol stack firmware connect to the vehicle infotainment system via a USB interface. This allows for automatic identification of the wired interaction protocols supported by the vehicle infotainment system and the simulation of the corresponding intelligent device identity. In one embodiment, the embedded processor used in the vehicle infotainment interface simulation module is an ARM Cortex-A series SoC, possessing powerful digital signal processing capabilities and protocol parsing efficiency, enabling rapid response to communication requests from the vehicle infotainment system. The processor is peripherally configured with a USB 2.0 high-speed interface controller, an I2C communication interface, and an SPI interface for connecting to the vehicle infotainment system, the dashcam communication module, and other peripherals. The protocol stack firmware is developed based on the Linux real-time operating system and adopts a modular design, divided into three core layers: a protocol identification layer, a device simulation layer, and a data transmission layer. The protocol identification layer integrates the parsing logic of mainstream in-vehicle wired interaction protocols, enabling it to identify information such as protocol versions and function commands sent by the in-vehicle system. The device simulation layer stores the identity identifiers of different simulated intelligent devices (such as device model, hardware number, and communication port), and can dynamically switch simulated identities based on the identified in-vehicle system protocol. The data transmission layer is responsible for format conversion and transmission control of video stream data, ensuring data compatibility with the in-vehicle system protocol. The firmware supports online upgrades, allowing users to update the protocol library via the in-vehicle system's USB interface or wirelessly to adapt to newly released in-vehicle system models and protocol versions. After the device connects to the in-vehicle system via the USB interface, the embedded processor immediately initiates the protocol identification process: First, the processor sends a protocol probe signal to the in-vehicle system via the USB differential signal line. Upon receiving the signal, the in-vehicle system returns the identifier of the protocol type it supports. After receiving the feedback signal, the processor extracts the protocol identifier using the protocol stack firmware's parsing algorithm and matches it with the corresponding protocol parsing logic. Subsequently, the processor calls the corresponding simulated device identity parameters from the device simulation layer and sends a device authentication request to the in-vehicle system, including information such as device model, communication rate, and data format. The in-vehicle system verifies the authentication information, and upon successful verification, establishes a stable data transmission channel.

[0030] The vehicle interface simulation module encapsulates the received video stream data into a media stream format supported by the wired interaction protocol and pushes the media stream format to the vehicle's infotainment system as an analog smart device. In one embodiment, a mainstream dashcam is selected. Its output video stream is acquired by the dashcam communication module and transmitted to the processor of the vehicle interface simulation module via the onboard bus. The module calls the corresponding media stream encapsulation algorithm according to the identified vehicle protocol, converting it to a compatible format for different vehicle protocols to ensure audio and video synchronization. After encapsulation, the module, acting as an analog smart device, pushes the media stream to the vehicle's infotainment system via USB interface, ensuring stable data transmission during the push process. Taking a vehicle model supporting mainstream protocols as an example, the vehicle's infotainment system can clearly display the dashcam's real-time footage after receiving the data, with convenient switching between historical videos and efficient playback response, achieving a smooth viewing experience without any additional operation.

[0031] The in-vehicle infotainment system supports at least one of the following wired interaction protocols: Apple CarPlay, Android Auto, Huawei HiCar, and Baidu CarLife. The in-vehicle interface simulation module automatically identifies the protocol by parsing USB handshake signals. In one embodiment, the in-vehicle interface simulation module supports four major wired interaction protocols: Apple CarPlay, Android Auto, Huawei HiCar, and Baidu CarLife, all of which are automatically identified through USB handshake signal parsing. Specifically, after the device connects to the in-vehicle infotainment system, the module's embedded processor sends a USB handshake signal to the system. The system responds with a signal containing the corresponding protocol identifier. The processor parses the identifier through the protocol stack firmware, loads the matching protocol stack, and simulates the identity of the corresponding brand of smart device to complete authentication and establish a data transmission channel. Specifically, CarPlay is adapted to simulate corresponding Apple devices, Android Auto to simulate Android devices, Huawei HiCar establishes an encrypted channel through a proprietary authentication algorithm, and Baidu CarLife supports functions such as video screenshots and local storage. The entire identification process requires no manual user operation and can automatically switch between adaptation modes, covering the protocol requirements of mainstream vehicle models. This effectively solves the adaptation problems caused by the closed nature of in-vehicle infotainment protocols in existing technologies, offering broad compatibility and efficient identification.

[0032] like Figure 2-3 As shown, the dashcam communication module has a built-in Wi-Fi chip and uses the Wi-FiStation working mode. After the device is turned on, the dashcam communication module controls the Wi-Fi chip to automatically scan for nearby connectable dashcam Wi-Fi hotspots and simultaneously executes any of the following connection logics: First, it retrieves and calls up the SSID and corresponding password of the last successfully connected device stored in its own memory, and automatically initiates a reconnection; if no historical connection record is stored or the reconnection fails, it scans and matches the dashcam Wi-Fi hotspot corresponding to the device's preset SSID, and calls the preset password to automatically establish a wireless connection; if no preset SSID hotspot is matched, or the automatic connection fails, the device pushes a hotspot list to the vehicle's infotainment system through the vehicle interface simulation module, allowing the user to manually select the target dashcam Wi-Fi hotspot and enter the password to complete the connection; After the dashcam communication module establishes a wireless connection with the dashcam, it establishes a session with the dashcam through the IP layer communication protocol to obtain video stream data.

[0033] In one embodiment, the device's dashcam communication module has a built-in Wi-Fi chip, operating in Wi-Fi Station mode, primarily for compatibility with existing commercially available dashcams. After the user connects the device to the vehicle's infotainment system and starts it up, the Wi-Fi chip automatically enters scanning mode, accurately identifying dashcam Wi-Fi hotspots that match the device's preset SSID, avoiding interference from irrelevant networks. Subsequently, the dashcam communication module uses its own preset password, uniquely corresponding to the SSID, to automatically establish a wireless connection with the dashcam, eliminating the need for manual password input by the user. Once the connection is established, the module establishes a stable session with the dashcam via IP layer communication protocols, acquiring real-time video stream data captured by the dashcam and quickly transmitting it to the vehicle's infotainment interface simulation module. The entire process is fully automated, requiring no mobile phone intervention, compatible with most mainstream brand dashcams, meeting the needs of aftermarket users, and offering convenient operation and stable connection.

[0034] like Figure 2 and Figure 4 As shown, the dashcam communication module has a built-in Wi-Fi chip and uses Wi-Fi AP working mode. After the device is turned on, the dashcam communication module automatically creates a Wi-Fi hotspot with a fixed SSID and password. The dashcams that are compatible with the device have the fixed SSID and password pre-written into the device. After the dashcam is turned on, it periodically scans for surrounding hotspots through Wi-Fi. When it recognizes the Wi-Fi hotspot created by the device, it automatically initiates a connection request and completes authentication through the preset SSID and password. After the connection is established, the dashcam communication module establishes a session with the dashcam through the IP layer communication protocol to obtain video stream data.

[0035] In one embodiment, the dashcam communication module is pre-configured with Wi-Fi AP operating mode parameters at the factory. After the user connects the device to the vehicle's infotainment system via USB and powers it on, the module automatically starts and creates a Wi-Fi hotspot with a fixed SSID and password without any manual operation. The hotspot parameters are standardized to ensure consistency between devices from different batches and the dashcam, avoiding connection conflicts. The dashcam itself has the SSID and password of this hotspot pre-written into its storage unit at the factory, forming a dedicated pairing relationship. After the dashcam starts, it continuously detects the surrounding wireless environment through its built-in periodic Wi-Fi scanning function. The scanning interval is optimized for in-vehicle scenarios, ensuring rapid identification without excessive power consumption. When the dashcam detects a target hotspot created by the device, it immediately and automatically extracts the pre-configured matching parameters and initiates a connection request, completing authentication and link establishment without user intervention. Once the connection is stable, the dashcam communication module establishes a dedicated data session with the dashcam via an IP layer communication protocol, specifically for transmitting video stream data. In this mode, data transmission is confined to the vehicle's local area network throughout the entire process, avoiding the security risks and latency issues caused by public network transmission. At the same time, users do not need to perform cumbersome operations such as hotspot search and password input. It is perfectly adapted to the needs of large-scale pre-installation production by car manufacturers. Whether it is pre-installed in a new car or retrofitted in batches, it can achieve seamless linkage between the device and the recorder, ensuring stable acquisition of video stream data.

[0036] The vehicle-mounted interface simulation module also has a built-in video encoding unit. The video encoding unit is configured to: adaptively process the video stream data from the bicycle dashcam communication module; if the video stream format conforms to the requirements of the wired interaction protocol, then transmit the video stream data to the vehicle-mounted system; if the video stream format is incompatible with the wired interaction protocol, then first decode the video stream data to convert it into raw audio and video data, then optimize the raw audio and video data with H.264 or H.265 encoding according to the wired interaction protocol adaptation requirements, and finally encapsulate the processed video stream.

[0037] In one embodiment, the device integrates a high-performance dedicated video encoding unit in the vehicle interface simulation module. This unit works in conjunction with the embedded processor and protocol stack firmware to form a complete "reception-encoding-encapsulation" processing link, enabling video stream optimization without the need for additional external devices. When the dashcam communication module transmits the acquired raw video stream data to the vehicle interface simulation module, the encoding unit immediately starts working. First, it parses the raw video stream to identify its encoding type, bitrate, resolution, and other key parameters. Then, based on the actual application scenario and the vehicle's performance, it automatically selects either H.264 or H.265 encoding for optimization—H.264 encoding prioritizes compatibility, adapting to older vehicle models; H.265 encoding prioritizes efficient compression, reducing bandwidth usage while maintaining image quality. During the encoding optimization process, the unit intelligently compresses redundant data in the video stream and adjusts the frame rate and bitrate to ensure that the processed video stream meets the vehicle's hardware processing capabilities while reducing the load on the USB transmission channel. After encoding, the vehicle interface simulation module calls the encapsulation algorithm of the corresponding vehicle protocol to encapsulate the optimized video stream into a media stream format supported by the vehicle, completely solving problems such as stuttering, screen tearing, and inability to display caused by incompatibility of the original video stream format, so that video content from dashcams of different specifications can be displayed smoothly on the vehicle.

[0038] IP layer communication protocols include at least one of the following: RTSP, RTP, HTTP, a subset of ONVIF, and other IP layer-based protocols. In one embodiment, the dashcam communication module of the device integrates RTSP, RTP, HTTP, a subset of ONVIF, and other IP layer-based protocols to form a multi-protocol adaptation system. This system can flexibly switch according to the dashcam model and transmission scenario requirements, maximizing the stability and compatibility of data transmission. In practical applications, protocol selection adopts a combination of automatic adaptation and manual configuration: the module first detects the communication protocol types supported by the dashcam, and then selects the optimal solution based on transmission requirements. Specifically, the RTSP protocol is mainly used for real-time video stream transmission control, supporting users to trigger video preview start / stop, fast forward, slow motion, and other operations via the vehicle's infotainment system. The command response is timely, adapting to the core scenario of real-time viewing during driving. The RTP protocol focuses on real-time transmission of audio and video data, possessing a powerful timing synchronization mechanism that effectively ensures the consistency of video and audio, avoiding audio-visual desynchronization issues. The HTTP protocol is used for retrieving and transmitting historical video files. When users need to play back past videos stored by the dashcam, the module reliably transmits video files via HTTP, supports resume playback, and improves the playback experience. The ONVIF protocol subset is specifically designed to improve compatibility between the device and dashcams from different brands, covering the standardized interfaces of most mainstream brands on the market, eliminating the need to develop separate adaptation logic for specific dashcams. This multi-protocol system design allows the device to adapt without distinguishing between the dashcam's protocol type, significantly expanding the device's applicability and lowering the barrier to entry for users.

[0039] User-triggered commands via the vehicle's infotainment interface are transmitted to the vehicle's interface simulation module, where they are converted into control signals recognizable by the dashcam. These signals are then transmitted to the dashcam via its communication module. After executing the commands, the dashcam generates feedback data, which is sequentially sent to the dashcam communication module, the vehicle's interface simulation module, and the vehicle's infotainment system. In this embodiment, users do not need to look down at their phones or the dashcam while driving. They can trigger various operation commands through convenient interactive interfaces such as the vehicle's touchscreen and steering wheel buttons, including commonly used functions such as real-time video preview start / stop, historical video playback, screenshot saving, and recording pause. User-triggered commands are first received by the vehicle's infotainment system, which then transmits the commands to the vehicle interface simulation module according to its own protocol format. The module has a built-in dedicated command conversion logic that can quickly identify the meaning of the vehicle's protocol commands and convert them into standardized control signals recognizable by the dashcam. This conversion process requires no manual intervention, has low response latency, and ensures the immediacy of the operation. The converted control signals are transmitted to the dashcam communication module via onboard circuitry, and then sent to the dashcam via a stable wireless link. After receiving the control signals, the dashcam immediately executes the corresponding operation commands and generates feedback data containing information such as operation results (e.g., successful screenshot, playback started) and device status (e.g., remaining storage space, battery level). Feedback data is transmitted in reverse along the original transmission path. After being received by the dashcam's communication module, it is transmitted to the vehicle's infotainment interface simulation module. The module converts it into a display format that the vehicle's infotainment system can recognize, and finally pushes it to the vehicle's screen for intuitive display. The entire interaction process is completed inside the vehicle without relying on an external network, which not only improves driving safety but also makes user operation more convenient, achieving a "what you see is what you get" interactive experience.

[0040] This invention discloses a device for viewing dashcam content on a car infotainment screen. Through the organic collaboration of a car infotainment interface simulation module and a dashcam communication module, it constructs a "plug-and-play, widely compatible" in-vehicle video viewing solution that eliminates the need for mobile phone intervention, completely resolving core pain points in existing technologies such as reliance on mobile apps, cumbersome operation, and difficulty in protocol adaptation. Based on an integrated design, the device innovatively adopts dual Wi-Fi working modes: Wi-Fi Station mode for compatibility with existing commercially available dashcams, meeting aftermarket upgrade needs; and Wi-Fi AP mode for adaptation to OEM customized scenarios, supporting large-scale pre-installation applications by automakers and achieving full-scenario coverage. The protocol stack firmware and video encoding unit built into the car infotainment interface simulation module are not only compatible with the four major car infotainment protocols but also ensure efficient video stream adaptation to different car infotainment systems and smooth playback through encoding optimization and format encapsulation. Simultaneously, the complete command interaction loop and in-vehicle local area network transmission design enhance driving safety while strengthening data privacy protection. The core value of this invention lies in its user-centric approach, balancing convenience, compatibility, and stability: it requires no complex configuration; users can simply plug it in and use it. It breaks down brand barriers between in-vehicle systems and dashcams, offering broad compatibility. Automated protocol identification, connection, and data processing lower the barriers to technology implementation. Whether for aftermarket upgrades by ordinary users or intelligent integration by car manufacturers, this device provides an efficient solution. In summary, this invention, through deep integration of hardware and software optimization, promotes the interconnectivity of in-vehicle electronic devices, providing a better option for in-vehicle video viewing scenarios. Its mature and reliable technical solution has strong commercial applicability and is expected to be widely adopted in the automotive electronics field, bringing users a safer and more convenient in-vehicle intelligent experience and contributing to the sustainable development of the automotive intelligentization industry.

[0041] It should be understood that those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

[0042] The present invention has been described above with reference to the accompanying drawings. Obviously, the implementation of the present invention is not limited to the above-described manner. Any improvements made using the inventive concept and technical solution of the present invention, or the direct application of the inventive concept and technical solution of the present invention to other situations without modification, are all within the protection scope of the present invention.

Claims

1. An apparatus for viewing content of a driving recorder on a screen of a car machine, characterized in that, The device comprises a connected car interface simulation module and a car DVR communication module, wherein the car interface simulation module is connected with a car machine, and the car DVR communication module is connected with a car DVR. The car interface simulation module simulates the identity of a simulated smart device corresponding to the car machine and transmits data with the car machine, and the car DVR communication module acquires video stream data of the car DVR and transmits the video stream data to the car interface simulation module.

2. The device of claim 1, wherein, The car interface simulation module is connected with the car machine through a USB interface, the USB interface is a USB Type-A interface or a USB Type-C interface, and the car DVR communication module is wirelessly connected with the car DVR.

3. The device of claim 1, wherein the device is a car screen that views the content of the car recorder. The car interface simulation module is internally provided with an embedded processor and a protocol stack firmware, both of which are connected with the car machine through the USB interface, for automatically identifying a wired interactive protocol supported by the car machine and simulating the identity of the simulated smart device corresponding to the wired interactive protocol.

4. The device of claim 3, wherein, The car interface simulation module encapsulates the received video stream data into a media stream format supported by the wired interactive protocol and pushes the media stream format to the car machine in the identity of the simulated smart device.

5. The device of claim 3, wherein, The wired interactive protocol supported by the car machine includes at least one of Apple CarPlay, Android Auto, Huawei HiCar and Baidu CarLife, and the car interface simulation module automatically identifies the protocol through USB handshake signal analysis.

6. The device of claim 1, wherein the device is a car screen that views the content of the car recorder. The car DVR communication module is internally provided with a Wi-Fi chip and adopts a Wi-Fi Station working mode; after the device is started, the car DVR communication module controls the Wi-Fi chip to automatically scan a connectable car DVR Wi-Fi hotspot around and synchronously executes any one of the following connection logics: preferentially searching and calling an SSID and a corresponding password of a last successful connection stored by itself, and automatically initiating a reconnection; if no historical connection record is stored or the reconnection fails, scanning and matching a car DVR Wi-Fi hotspot corresponding to a preset SSID of the device, and calling a preset password to automatically establish a wireless connection; if no preset SSID hotspot is matched or the automatic connection fails, the device pushes a hotspot list to the car machine through the car interface simulation module, so that a user manually selects a target car DVR Wi-Fi hotspot and inputs a password to complete the connection; after the car DVR communication module establishes the wireless connection with the car DVR, a session is established with the car DVR through an IP layer communication protocol, and the video stream data is acquired.

7. The device of claim 1, wherein the device is a car screen that views the content of the car recorder. The car recorder communication module is built-in with a Wi-Fi chip and adopts a Wi-Fi AP working mode, the car recorder communication module automatically creates a Wi-Fi hot spot with a fixed SSID and password after the device is started, the car recorder matched with the device has been pre-written with the fixed SSID and password of the device, the car recorder detects the surrounding hot spots through periodic Wi-Fi scanning after being started, and automatically initiates a connection request and completes identity authentication through the preset SSID and password when the Wi-Fi hot spot created by the device is identified; after the connection is established, the car recorder communication module establishes a session with the car recorder through an IP layer communication protocol and acquires the video stream data.

8. The device of claim 3, wherein the device is a car screen that views the content of the car recorder. The car machine interface simulation module is also built-in with a video encoding unit, which is configured to: adaptively process the video stream data from the car recorder communication module, if the video stream data format has met the requirements of the wired interaction protocol, the video stream data is transmitted to the car machine; if the video stream data format is incompatible with the wired interaction protocol, the video stream data is first decoded and processed to be converted into original audio and video data, then the original audio and video data is encoded and optimized according to the requirements of the wired interaction protocol adaptation, and finally the processed video stream is encapsulated.

9. The device of claim 6 or 7, wherein, The IP layer communication protocol includes at least one of an RTSP protocol, an RTP protocol, an HTTP protocol, an ONVIF protocol subset, and other IP layer-based protocols.

10. The device of claim 1, wherein the device is a car screen that views the content of the event data recorder. The instructions triggered by the user through the car machine interaction interface are transmitted to the car machine interface simulation module by the car machine, converted into control signals recognizable by the car recorder by the car machine interface simulation module, and then transmitted to the car recorder through the car recorder communication module; the car recorder generates feedback data after executing the instructions, and the feedback data is sequentially transmitted to the car recorder communication module, the car machine interface simulation module and the car machine.

Images