Vehicle-mounted mobile phone interconnection diagnosis system and method thereof

Abstract

The application discloses a vehicle-mounted mobile phone interconnection diagnosis system and method in the technical field of vehicle-mounted mobile phone interconnection diagnosis, and relates to a mobile phone end and a vehicle machine end, wherein the mobile phone end and the vehicle machine end communicate through a protocol stack software layer of a virtual software channel, the mobile phone end and the vehicle machine end are connected through an interconnection unit, and the mobile phone end and the vehicle machine end are functionally diagnosed through a diagnosis software module architecture. The application can solve the problem positioning in the mobile phone interconnection development process, realize the production automation in the vehicle machine production process, especially the problem positioning and detailed process recording of the mobile phone interconnection abnormal fault in the after-sales process, greatly reduce the after-sales pressure of Tier1 and the vehicle factory, greatly improve the after-sales efficiency, and help the mobile phone manufacturers and the vehicle machine manufacturers improve the quality.

Description

Technical Field

[0001] This invention relates to a vehicle-mounted mobile phone interconnection diagnostic system and method in the field of vehicle-mounted mobile phone interconnection diagnostic technology. Background Technology

[0002] In recent years, the in-car smartphone connectivity technology has emerged in rapid succession, with various smartphone manufacturers launching their own connection technologies, such as Apple CarPlay, Baidu CarLife, Huawei HiCar, OV & Xiaomi CarLink, and Google Android Auto. Smartphone connectivity has become an important function of in-car entertainment systems, but in actual use, various problems frequently occur, such as connection anomalies, black screens, and silence. These problems severely impact the user experience, but the causes are varied; they could be issues on the smartphone, the in-car system, or even the data cable. Because these problems are not always reproducible, automakers often lack effective means to pinpoint whether the issue stems from the in-car system itself, based on user complaints.

[0003] Currently, various mobile phone manufacturers have certain diagnostic applications on their mobile phones, but their main purpose is to test the functionality and performance of the in-vehicle software. There are no specific diagnostic methods for potential problems on the mobile phone side. Summary of the Invention

[0004] The purpose of this invention is to provide a vehicle-mounted mobile phone interconnection diagnostic system and method, which solves the problem that there is no effective means to locate the cause when connection abnormalities occur in current mobile phone interconnection technology.

[0005] To achieve the above objectives, the present invention provides an in-vehicle mobile phone interconnection diagnostic system, including a mobile phone terminal and an in-vehicle terminal. The mobile phone terminal and the in-vehicle terminal communicate through a virtual software channel at the protocol stack software layer. The mobile phone terminal and the in-vehicle terminal connect their information through an interconnection unit. The mobile phone terminal and the in-vehicle terminal perform functional diagnostics through a diagnostic software module architecture.

[0006] As a further improvement of the present invention, the virtual software channel includes CMD commands, AudioIn channel, AudioOut channel, VideoOut channel, GNSS / GYRO / SPEED channel, and TouchData channel;

[0007] Among them, CMD commands are the most important basic information channel for establishing a connection between the vehicle and the mobile phone, including device discovery, network connection, connection authentication, channel establishment, handshake connection, and state switching. During the connection establishment phase, the mobile phone and the vehicle establish a connection through CMD commands, and after the connection is established, the CMD channel is used to transmit information on mode switching.

[0008] AudioIn Channel: A separate audio input channel, mainly used to send audio recorded by the car's microphone to the mobile phone for input functions including telephone uplink tones, VR input tones, etc.

[0009] AudioOut channel: A separate audio output channel that sends audio from the mobile phone to the vehicle's infotainment system for playback, including downlink toll for calls, music output, navigation audio, voice recognition feedback audio, and key presses.

[0010] VideoOut channel: A separate video output channel that compresses and encodes the mobile phone's interface before sending it to the vehicle's infotainment system for display;

[0011] GNSS / GYRO / SPEED Channel: A separate vehicle information sharing channel, including GNSS, GYRO, vehicle speed data, and gear data, used to improve the accuracy of mobile phone navigation positioning;

[0012] TouchData Channel: A separate touch data channel that transmits data from the vehicle's infotainment system to the mobile phone, including touchscreen data, steering wheel control data, and knob data, enabling control of mobile phone connectivity functions from the vehicle's infotainment system.

[0013] As a further improvement of the present invention, the interconnection unit includes a Driver, an OS, a Phonelink Communication Framework, and an App.

[0014] Driver: This includes drivers for both the mobile phone and the vehicle's infotainment system, covering USB, Wi-Fi, and Bluetooth. OS: This includes the operating systems for both the vehicle and the mobile phone, including Linux, Android, and QNX. Phonelink CommunicationFramework: This is the core service for mobile phone connectivity, divided into mobile phone and vehicle-mounted components. Its core function is to establish a connection between the vehicle and the mobile phone, and to implement display, audio recording, audio playback, touch data, GNSS and Gyro data transmission and processing.

[0015] App: This module consists of application software. Mobile applications include phone, navigation, music player, video player, and voice recognition applications; in-vehicle applications demonstrate the functions of mobile phone interconnection and provide interaction logic with other in-vehicle applications, ensuring the integrity of the functions.

[0016] As a further improvement of the present invention, the diagnostic software module architecture includes two parts: a mobile terminal and a vehicle terminal. It is used to diagnose mobile phone interconnection functions. Through this diagnostic module, abnormal points in the interconnection and the location where the abnormality occurs can be quickly located.

[0017] To achieve the above objectives, the present invention also provides a diagnostic method for in-vehicle mobile phone interconnection, comprising the following steps:

[0018] Step 1: Enter diagnostic mode on your mobile device;

[0019] Step 1.1: After the mobile phone and the vehicle's infotainment system establish a physical connection, the vehicle's infotainment system actively sends a diagnostic start command to the mobile phone. This command can be initiated through the vehicle's HMI interface or through the vehicle's automation protocol. After the start command is initiated, the vehicle's infotainment system enters the mobile phone interconnection diagnostic mode.

[0020] Step 1.2: After receiving the diagnostic start request from the vehicle's infotainment system, the mobile device needs to initialize the diagnostic interface and enter diagnostic mode.

[0021] Step 2, Connection status detection;

[0022] Step 3, bandwidth test;

[0023] Step 4, Video Consistency Test;

[0024] Step 5, Audio Consistency Test;

[0025] Step 6: Diagnosis complete, report diagnostic test results.

[0026] As a further improvement to the present invention, step 2 is specifically described below.

[0027] Step 2.1: After the mobile diagnostic interface is initialized, the current connection status is summarized and sent to the vehicle terminal. The connection status includes whether it is a wired or wireless connection, whether the connection is established normally, the duration of the connection establishment, the current audio and video working mode, and the list of functions supported by the current connection.

[0028] Step 2.2: After receiving the connection status feedback from the mobile phone, the vehicle terminal will compare it with the current connection status recorded by the vehicle terminal. If the connection status is consistent, it will continue to the next step. If an anomaly is found in the comparison, it will enter the anomaly handling process and report the anomaly error and the specific cause of the fault.

[0029] As a further improvement to the present invention, step 3 is specifically described below.

[0030] Step 3.1: After the connection status detection is completed, the vehicle will send a connection status normal message to the mobile phone and send a bandwidth test command to the mobile phone.

[0031] Step 3.2: The mobile phone receives the bandwidth test command and starts the bandwidth test. Whether it is a WIFI or USB connection, the protocol layer connection is based on the UDP / TCP protocol. The standard iperf command is used to test the four indicators: TCP response latency, TCP bandwidth, UDP bandwidth, and UDP packet loss rate. After the test is completed, the results are sent to the vehicle terminal.

[0032] Step 3.3: After receiving the test results from the mobile phone, the vehicle-mounted system needs to make a comprehensive judgment based on the current connection method and different display resolutions to obtain the bandwidth test results, since different connection methods and resolutions have different requirements for bandwidth, latency, and packet loss rate. If the test fails, the system will directly enter the exception handling process and report the detailed results. If the test is OK, the system will continue to execute.

[0033] As a further improvement to the present invention, step 4 is specifically described below.

[0034] Step 4.1: After the bandwidth test is completed, the vehicle will send the bandwidth test results to the mobile phone and simultaneously send a video test command to the mobile phone.

[0035] Step 4.2: After receiving the video test command, the mobile terminal needs to send the comparison video data to the vehicle's infotainment system. Based on the original video encoding, an H.264 robust watermarking algorithm combining a residual block quantization hierarchical coefficient model and a "cross-shaped region" motion vector is added to the sent video. This watermark gives the vehicle's infotainment system a basis for judging the video's integrity and consistency.

[0036] Step 4.3: After receiving the video data from the mobile phone, the vehicle-mounted system needs to verify the integrity and consistency of the received video. Since the video sent from the mobile phone has been watermarked, the vehicle-mounted system performs several processes, including extraction of the authentication code, embedding of identification information, tamper detection, and location, to verify the integrity and consistency of the video. If the video data is found to be inconsistent, the system will directly enter the exception handling process and save the video frames for detailed diagnosis of the problem and reporting of detailed results. If the test is OK, the system will continue to the next step.

[0037] As a further improvement to the present invention, step 5 is specifically described below.

[0038] Step 5.1. After the video consistency test is completed, the vehicle will send the video consistency test results to the mobile phone and simultaneously send the audio test command to the mobile phone.

[0039] Step 5.2: After receiving the audio test command, the mobile phone needs to send the comparison audio data to the vehicle's infotainment system. To simplify the audio consistency verification, the mobile phone will send a 1kHz, 2kHz, or 3kHz sine wave to the vehicle's infotainment system.

[0040] Step 5.3: After receiving the audio data from the mobile phone, the vehicle-mounted system performs spectrum analysis on the audio data using Fourier transform to determine the correctness of the audio. At the same time, it counts the frames of the PCM data to determine the integrity of the audio data. If there are problems with the consistency and integrity of the data verification, it directly enters the exception handling process and saves the audio PCM data for easy investigation of the cause of the problem later. If the test is OK, it continues to the next step.

[0041] As a further improvement to the present invention, step 6 is specifically described below.

[0042] Step 6.1 After the audio consistency test is completed, the vehicle will send the audio consistency test results to the mobile phone and send a Touch data test command. In this command, the vehicle will send fixed touch data directly to the mobile phone according to the protocol.

[0043] Step 6.2: After receiving the touch data command from the vehicle's infotainment system, the mobile phone needs to convert the touch coordinates according to the vehicle's screen resolution and the mobile phone's own screen resolution, and then send the converted coordinates to the vehicle's infotainment system.

[0044] Step 6.3: The vehicle system receives the converted touch data from the mobile phone and needs to verify it synchronously according to the conversion algorithm to confirm the correctness of the converted data. If an anomaly occurs, it directly enters the anomaly handling process and reports detailed anomaly data; if the data is normal, the automated diagnostic process ends at this time and the diagnostic test OK result is reported.

[0045] Compared with existing technologies, the advantages of this invention lie in its ability to solve problems in the development of mobile phone connectivity, the automation of production in the manufacturing process of vehicle infotainment systems, and especially the problem location and detailed process recording of abnormal mobile phone connectivity faults during after-sales service. This significantly reduces the after-sales burden on Tier 1 suppliers and car manufacturers, greatly improves after-sales efficiency, and helps mobile phone manufacturers and vehicle infotainment system manufacturers improve quality. Attached Figure Description

[0046] Figure 1 This is a block diagram illustrating the interconnection between the mobile phone and the vehicle system in this invention.

[0047] Figure 2 This is a block diagram showing the connection of multiple virtual software channels in this invention.

[0048] Figure 3 This is a diagram illustrating the architecture of the mobile phone interconnection system and diagnostic software module of the present invention.

[0049] Figure 4 This is a flowchart of the interconnection diagnostic logic. Implementation

[0050] The present invention will be further described below with reference to the accompanying drawings:

[0051] like Figure 1-3 The system illustrates an in-vehicle mobile phone interconnection diagnostic system, which includes a mobile phone terminal and an in-vehicle terminal. The mobile phone terminal and the in-vehicle terminal communicate through a virtual software channel at the protocol stack software layer. The mobile phone terminal and the in-vehicle terminal connect their information through an interconnection unit. The mobile phone terminal and the in-vehicle terminal perform functional diagnostics through a diagnostic software module architecture.

[0052] The virtual software channels include CMD commands, AudioIn channel, AudioOut channel, VideoOut channel, GNSS / GYRO / SPEED channel, and TouchData channel;

[0053] Among them, CMD commands are the most important basic information channel for establishing a connection between the vehicle and the mobile phone, including device discovery, network connection, connection authentication, channel establishment, handshake connection, and state switching. During the connection establishment phase, the mobile phone and the vehicle establish a connection through CMD commands, and after the connection is established, the CMD channel is used to transmit information on mode switching.

[0054] AudioIn Channel: A separate audio input channel, mainly used to send audio recorded by the car's microphone to the mobile phone for input functions including telephone uplink tones, VR input tones, etc.

[0055] AudioOut channel: A separate audio output channel that sends audio from the mobile phone to the vehicle's infotainment system for playback, including downlink toll for calls, music output, navigation audio, voice recognition feedback audio, and key presses.

[0056] VideoOut channel: A separate video output channel that compresses and encodes the mobile phone's interface before sending it to the vehicle's infotainment system for display;

[0057] GNSS / GYRO / SPEED Channel: A separate vehicle information sharing channel, including GNSS, GYRO, vehicle speed data, and gear data, used to improve the accuracy of mobile phone navigation positioning;

[0058] TouchData Channel: A separate touch data channel that transmits data from the vehicle's infotainment system to the mobile phone, including touchscreen data, steering wheel control data, and knob data, enabling control of mobile phone connectivity functions from the vehicle's infotainment system.

[0059] The interconnection unit includes a Driver, an OS, a Phonelink Communication Framework, and an App. The Driver is the driver for both the mobile phone and the vehicle's infotainment system, including USB, Wi-Fi, and Bluetooth drivers. The OS includes the operating systems for both the vehicle's infotainment system and the mobile phone, including Linux, Android, and QNX.

[0060] Phonelink Communication Framework: This is the core service for mobile phone connectivity, consisting of two parts: the mobile phone and the vehicle's infotainment system. Its core function is to establish a connection between the vehicle's infotainment system and the vehicle's infotainment system, and to implement display, audio recording, audio playback, touch data, GNSS and gyro data transmission and processing.

[0061] App: This module consists of application software. Mobile applications include phone, navigation, music player, video player, and voice recognition applications; in-vehicle applications demonstrate the functions of mobile phone interconnection and provide interaction logic with other in-vehicle applications, ensuring the integrity of the functions.

[0062] The diagnostic software module architecture consists of two parts: a mobile terminal and a vehicle terminal. It is used to diagnose mobile phone interconnection functions. Through this diagnostic module, abnormal points in the interconnection and the location where the abnormality occurs can be quickly located.

[0063] like Figure 4 The method for diagnosing in-vehicle mobile phone connectivity, as shown, is characterized by including the following steps:

[0064] Step 1: Enter diagnostic mode on your mobile device;

[0065] Step 1.1: After the mobile phone and the vehicle's infotainment system establish a physical connection, the vehicle's infotainment system actively sends a diagnostic start command to the mobile phone. This command can be initiated through the vehicle's HMI interface or through the vehicle's automation protocol. After the start command is initiated, the vehicle's infotainment system enters the mobile phone interconnection diagnostic mode.

[0066] Step 1.2: After receiving the diagnostic start request from the vehicle's infotainment system, the mobile device needs to initialize the diagnostic interface and enter diagnostic mode.

[0067] Step 2, Connection status detection;

[0068] Step 2.1: After the mobile diagnostic interface is initialized, the current connection status is summarized and sent to the vehicle terminal. The connection status includes whether it is a wired or wireless connection, whether the connection is established normally, the duration of the connection establishment, the current audio and video working mode, and the list of functions supported by the current connection.

[0069] Step 2.2: After receiving the connection status feedback from the mobile phone, the vehicle terminal will compare it with the current connection status recorded by the vehicle terminal. If the connection status is consistent, it will continue to the next step. If an anomaly is found in the comparison, it will enter the anomaly handling process and report the anomaly error and the specific cause of the fault.

[0070] Step 3, bandwidth test;

[0071] Step 3.1: After the connection status detection is completed, the vehicle will send a connection status normal message to the mobile phone and send a bandwidth test command to the mobile phone.

[0072] Step 3.2: The mobile phone receives the bandwidth test command and starts the bandwidth test. Whether it is a WIFI or USB connection, the protocol layer connection is based on the UDP / TCP protocol. The standard iperf command is used to test the four indicators: TCP response latency, TCP bandwidth, UDP bandwidth, and UDP packet loss rate. After the test is completed, the results are sent to the vehicle terminal.

[0073] Step 3.3: After receiving the test results from the mobile phone, the vehicle-mounted system needs to make a comprehensive judgment based on the current connection method and different display resolutions to obtain the bandwidth test results, since different connection methods and resolutions have different requirements for bandwidth, latency, and packet loss rate. If the test fails, the system will directly enter the exception handling process and report the detailed results. If the test is OK, the system will continue to execute.

[0074] Step 4, Video Consistency Test;

[0075] Step 4.1: After the bandwidth test is completed, the vehicle will send the bandwidth test results to the mobile phone and simultaneously send a video test command to the mobile phone.

[0076] Step 4.2: After receiving the video test command, the mobile terminal needs to send the comparison video data to the vehicle's infotainment system. Based on the original video encoding, an H.264 robust watermarking algorithm combining a residual block quantization hierarchical coefficient model and a "cross-shaped region" motion vector is added to the sent video. This watermark gives the vehicle's infotainment system a basis for judging the video's integrity and consistency.

[0077] Step 4.3: After receiving the video data from the mobile phone, the vehicle-mounted system needs to verify the integrity and consistency of the received video. Since the video sent from the mobile phone has been watermarked, the vehicle-mounted system performs several processes, including extraction of the authentication code, embedding of identification information, tamper detection, and location, to verify the integrity and consistency of the video. If the video data is found to be inconsistent, the system will directly enter the exception handling process and save the video frames for detailed diagnosis of the problem and reporting of detailed results. If the test is OK, the system will continue to the next step.

[0078] Step 5, Audio Consistency Test;

[0079] Step 5.1. After the video consistency test is completed, the vehicle will send the video consistency test results to the mobile phone and simultaneously send the audio test command to the mobile phone.

[0080] Step 5.2: After receiving the audio test command, the mobile phone needs to send the comparison audio data to the vehicle's infotainment system. To simplify the audio consistency verification, the mobile phone will send a 1kHz, 2kHz, or 3kHz sine wave to the vehicle's infotainment system.

[0081] Step 5.3: After receiving the audio data from the mobile phone, the vehicle-mounted system performs spectrum analysis on the audio data using Fourier transform to determine the correctness of the audio. At the same time, it counts the frames of the PCM data to determine the integrity of the audio data. If there are problems with the consistency and integrity of the data verification, it directly enters the exception handling process and saves the audio PCM data for easy investigation of the cause of the problem later. If the test is OK, it continues to the next step.

[0082] Step 6: Diagnosis complete, report diagnostic test results.

[0083] Step 6.1 After the audio consistency test is completed, the vehicle will send the audio consistency test results to the mobile phone and send a Touch data test command. In this command, the vehicle will send fixed touch data directly to the mobile phone according to the protocol.

[0084] Step 6.2: After receiving the touch data command from the vehicle's infotainment system, the mobile phone needs to convert the touch coordinates according to the vehicle's screen resolution and the mobile phone's own screen resolution, and then send the converted coordinates to the vehicle's infotainment system.

[0085] Step 6.3: The vehicle system receives the converted touch data from the mobile phone and needs to verify it synchronously according to the conversion algorithm to confirm the correctness of the converted data. If an anomaly occurs, it directly enters the anomaly handling process and reports detailed anomaly data; if the data is normal, the automated diagnostic process ends at this time and the diagnostic test OK result is reported.

[0086] In this invention, mobile phone interconnection is achieved between the mobile phone and the vehicle's infotainment system via USB or BT / WIFI. The software is divided into mobile phone software and vehicle infotainment system software. The main function of mobile phone interconnection is to utilize the resources and computing power of the mobile phone to provide the vehicle's infotainment system with more connected car services such as phone calls, voice recognition, navigation, online music, and online video. Communication between the vehicle's infotainment system and the mobile phone is achieved at the underlying level via USB or Wi-Fi, while the protocol at the software layer requires virtualizing the underlying physical channel into multiple software channels.

[0087] CMD commands: CMD commands are the most important basic information channel for establishing a connection between the vehicle's infotainment system and the mobile phone. They mainly include device discovery, network connection, connection authentication, channel establishment, handshake connection, and state switching. During the connection establishment phase, the connection is primarily established through CMD commands. After the connection is established, information such as mode switching is transmitted through the CMD channel.

[0088] AudioIn Channel: A separate audio input channel, mainly used to send audio recorded by the car's mic to the mobile phone for functions such as telephone uplink tones and VR input tones.

[0089] AudioOut channel: A separate audio output channel, mainly used to send audio from the mobile phone to the vehicle's infotainment system for playback, including downlink toll for calls, music output, navigation audio, voice recognition feedback audio, and key presses.

[0090] VideoOut channel: A separate video output channel, mainly used to compress and encode the mobile phone interface before sending it to the vehicle's infotainment system for display.

[0091] GNSS / GYRO / SPEED Channel: A separate vehicle information sharing channel, mainly including GNSS (location information), GYRO (gyroscope data), vehicle speed data, gear data, etc., to improve the accuracy of mobile phone navigation and positioning.

[0092] TouchData Channel: A separate touch data channel that transmits data from the vehicle's infotainment system to the mobile phone, including touchscreen data, steering wheel control data, and knob data, enabling control of mobile phone connectivity functions from the vehicle's infotainment system.

[0093] As mobile internet technology and functions iterate and update, the number of software channels will increase, but the basic architecture and methods will remain unchanged.

[0094] Once the entire diagnostic process is complete, the implementation of this process and method can fully realize the abnormal diagnosis of mobile phone interconnection function, output the diagnostic results, and locate the cause of the abnormality.

[0095] Specific application scenarios are illustrated below:

[0096] Scenario 1: When mobile connectivity developers encounter a black screen during vehicle infotainment software development, and are unsure whether the phone is sending the correct data, this diagnostic method can be used to first check if the display bandwidth is normal, and to check if the problem lies with the connection cable or link. If the bandwidth test passes, then check if the video stream test passes. If the video stream test reports an error, the cause of the error needs to be investigated. If the video stream sent by the phone does not meet the requirements, then the problem is on the phone side. If the phone's bitrate is normal, but the vehicle infotainment system displays abnormally, then the problem is on the vehicle infotainment system's display, thus quickly locating the cause of the problem.

[0097] Scenario 2: During the production of in-vehicle infotainment systems, manufacturers need to test the mobile phone connectivity function. However, it is difficult to ensure product consistency through functional testing. Using this patented method, automated testing of the mobile phone connectivity function on the production line can be quickly achieved. It is only necessary to call the automated testing instructions for mobile phone connectivity of the in-vehicle infotainment system during the automated testing process on the production line to see if each test can be passed. If it fails, an error is directly reported to the host computer to ensure the consistency of product production.

[0098] Scenario 3: When car owners encounter connection problems or abnormal usage issues (black screen, no sound, touch unresponsive) while using mobile phone connectivity, they can access the connectivity diagnostic page themselves or through a 4S store, click on the connectivity diagnostic function, and quickly locate whether the problem is caused by the car's system or the phone by using the generated diagnostic error information.

[0099] This invention can solve problems in mobile phone connectivity development, automate production processes in vehicle infotainment systems, and especially in locating and recording detailed faults related to mobile phone connectivity during after-sales service. It significantly reduces the after-sales burden on Tier 1 suppliers and car manufacturers, greatly improves after-sales efficiency, and helps mobile phone and vehicle infotainment system manufacturers improve quality.

[0100] This invention is not limited to the above embodiments. Based on the technical solutions disclosed herein, those skilled in the art can make some substitutions and modifications to some of the technical features without creative effort, and all such substitutions and modifications are within the protection scope of this invention.

Claims

1. A diagnostic method for vehicle-mounted mobile phone interconnection, characterized in that: Includes the following steps, Step 1: Enter diagnostic mode on your mobile device; Step 1.1: After the mobile phone and the vehicle's infotainment system establish a physical connection, the vehicle's infotainment system actively sends a diagnostic start command to the mobile phone. This command can be initiated through the vehicle's HMI interface or through the vehicle's automation protocol. After the start command is initiated, the vehicle's infotainment system enters the connected diagnostic mode. Step 1.2: After receiving the diagnostic start command from the vehicle's infotainment system, the mobile device needs to initialize the diagnostic interface and enter diagnostic mode. Step 2, Connection status detection; Step 2.1: After the mobile diagnostic interface is initialized, the current connection status is summarized and sent to the vehicle terminal. The connection status includes whether it is a wired or wireless connection, whether the connection is established normally, the duration of the connection establishment, the current audio and video working mode, and the list of functions supported by the current connection. Step 2.2: After receiving the connection status feedback from the mobile phone, the vehicle terminal will compare it with the current connection status recorded on the vehicle terminal. If the connection status is consistent, the process will continue. If an anomaly is found during the comparison, the anomaly handling process will be initiated, and the anomaly error and the specific cause of the fault will be reported. Step 3, bandwidth test; Step 3.1: After the connection status detection is completed, the vehicle terminal will send a connection status normal message to the mobile terminal, and at the same time send a bandwidth test command to the mobile terminal. Step 3.2: The mobile terminal receives the bandwidth test command and starts the bandwidth test. After the test is completed, the command is sent to the vehicle terminal. Step 3.3: After receiving the test results from the mobile phone, the vehicle terminal obtains the bandwidth test results. If the test fails, it directly enters the exception handling process and reports the detailed results. If the test is successful, continue execution. Step 4, Video Consistency Test; Step 4.1: After the bandwidth test is completed, the vehicle terminal will send the bandwidth test results to the mobile terminal and send a video test command to the mobile terminal at the same time. Step 4.2: After receiving the video test command, the mobile phone needs to send the comparison video data to the vehicle's infotainment system. Step 4.3: After receiving the video data from the mobile phone, if the video data is inconsistent, the vehicle-mounted system will directly enter the exception handling process and report the detailed results; if the test is OK, the system will continue to the next step. Step 5, Audio Consistency Test; Step 5.

1. After the video consistency test is completed, the vehicle terminal will send the video consistency test results to the mobile terminal, and at the same time send the audio test command to the mobile terminal; Step 5.2: After receiving the audio test command, the mobile phone needs to send the comparison audio data to the vehicle's infotainment system. Step 5.3: After the vehicle-mounted system receives the audio data from the mobile phone, if there are any issues with data consistency and integrity, it will directly enter the exception handling process. If the test is OK, continue to the next step; Step 6: Diagnosis complete, report diagnostic test results.

2. The in-vehicle mobile phone interconnection diagnostic method according to claim 1, characterized in that: In step 3.2, the mobile device receives the bandwidth test command and starts the bandwidth test. Whether it is a WIFI or USB connection, the protocol layer connection is based on the UDP / TCP protocol. The standard iperf command is used to test the four indicators: TCP response latency, TCP bandwidth, UDP bandwidth, and UDP packet loss rate. In step 3.3, after the vehicle terminal receives the test results from the mobile terminal, since different connection methods and resolutions have different requirements for bandwidth, latency, and packet loss rate, the vehicle terminal needs to make a comprehensive judgment based on the current connection method and different display resolutions of the vehicle terminal to obtain the bandwidth test results.

3. The in-vehicle mobile phone interconnection diagnostic method according to claim 2, characterized in that: In step 4.2, after the mobile terminal receives the video test command, it adds an H264 robust watermarking algorithm based on the residual block quantization layered coefficient model and the "cross region" motion vector to the original video encoding, and adds an identifier to the sent video. With a watermark, the vehicle terminal has a basis for judging the integrity and consistency of the video. In step 4.3, after the vehicle-mounted system receives the video data from the mobile phone, it needs to verify the integrity and consistency of the received video. Since the video sent from the mobile phone has been watermarked, the vehicle-mounted system performs several processes, including extraction of the authentication code, embedding of identification information, tamper detection and location, to verify the integrity and consistency of the video.

4. The in-vehicle mobile phone interconnection diagnostic method according to claim 3, characterized in that: In step 5.2, after receiving the audio test command, the mobile phone needs to send the comparison audio data to the vehicle's infotainment system. To simplify the audio consistency verification, the mobile phone will send a 1k, 2k, or 3k Hz sine wave to the vehicle's infotainment system. In step 5.3, after the vehicle-mounted system receives the audio data from the mobile phone, it performs spectrum analysis on the audio data through Fourier transform to determine the correctness of the audio. At the same time, it counts the number of frames in the PCM data to determine the integrity of the audio data.

5. The in-vehicle mobile phone interconnection diagnostic method according to claim 4, characterized in that: Step 6 details are as follows: Step 6.1 After the audio consistency test is completed, the vehicle terminal will send the audio consistency test results to the mobile phone side, and at the same time send a Touch data test command. In this command, the vehicle terminal will directly send fixed touch data to the mobile phone according to the protocol. Step 6.2: After receiving the touch data command from the vehicle's infotainment system, the mobile device needs to convert the touch coordinates according to the resolution of the vehicle's infotainment system and the mobile device's own resolution, and then send the converted coordinates to the vehicle's infotainment system. Step 6.3: The vehicle's infotainment system receives the converted touch data from the mobile phone and needs to verify it synchronously according to the conversion algorithm to confirm the correctness of the converted data. If an anomaly occurs, the system directly enters the anomaly handling process and reports detailed anomaly data. If the data is normal, the automated diagnostic process ends and the diagnostic test OK result is reported.

6. A vehicle-mounted mobile phone interconnection diagnostic system, applied to the vehicle-mounted mobile phone interconnection diagnostic method according to any one of claims 1-5, comprising a mobile phone terminal and a vehicle terminal, characterized in that: The mobile phone and the vehicle's infotainment system communicate through a virtual software channel at the protocol stack software layer. They also connect via an interconnection unit and perform functional diagnostics through a diagnostic software module. The diagnostic software module consists of two parts: the mobile phone and the vehicle's infotainment system, enabling the diagnostics of the interconnection function between the two devices. The virtual software channels include CMD commands, AudioIn channel, AudioOut channel, VideoOut channel, GNSS / GYRO / SPEED channel, and TouchData channel; Among them, CMD commands are the most important basic information channel for establishing a connection between the vehicle terminal and the mobile terminal, including device discovery, network connection, connection authentication, channel establishment, handshake connection, and state switching. During the connection establishment phase, the mobile terminal and the vehicle terminal establish a connection through CMD commands, and after the connection is established, the CMD channel is used to transmit information on mode switching. AudioIn Channel: A separate audio input channel, mainly used to send audio recorded by the in-vehicle microphone to the mobile phone for input functions including telephone uplink tones, VR input tones, etc. AudioOut channel: A separate audio output channel that sends audio from the mobile phone to the vehicle's infotainment system for playback, including downlink toll for calls, music output, navigation audio, voice recognition feedback audio, and key presses. VideoOut channel: A separate video output channel that compresses and encodes the mobile phone's interface before sending it to the vehicle's infotainment system for display; GNSS / GYRO / SPEED Channel: A separate vehicle information sharing channel, including GNSS, GYRO, vehicle speed data, and gear data, used to improve the accuracy of navigation and positioning on mobile devices; TouchData Channel: A separate touch data channel that transmits data from the vehicle's infotainment system to the mobile phone, including touchscreen data, steering wheel control data, and knob data, enabling control of mobile phone connectivity functions from the vehicle's infotainment system. The interconnect unit includes the Driver, OS, Phonelink Communication Framework, and App. Driver: refers to the drivers for both the mobile phone and the vehicle's infotainment system, including USB, WIFI, and Bluetooth drivers; OS: This includes the operating system for both in-vehicle systems and mobile devices, including Linux, Android, and QNX; Phonelink Communication Framework: This is the core service for mobile phone connectivity, consisting of two parts: mobile phone and vehicle-mounted system. Its core function is to establish a connection between the mobile phone and vehicle-mounted system, and to implement display, audio recording, audio playback, touch data, GNSS and gyro data transmission and processing. App: This module consists of application software. Mobile applications include phone, navigation, music player, video player, and voice recognition applications. In-vehicle applications are for displaying functions that enable interconnection with mobile applications and providing interaction logic with other in-vehicle applications, ensuring the integrity of the functions.

Images