Intelligent cabin domain controller log remote acquisition system and method

Abstract

The invention belongs to the field of vehicle remote communication, and discloses an intelligent cabin area controller log remote acquisition system and method, and the system comprises a remote application interface which is used for obtaining a man-machine interaction interface for logs; the TSP remote service platform is used for managing the log pulling instruction network interface, the log uploading network interface and the storage of the uploaded logs; the intelligent cockpit domain controller CDC and the large screen are used for internally recording and storing system and application running logs of all modules running in the latest time period; and the 4G module is used for establishing mobile communication with the outside. According to the invention, the vehicle machine, voice, navigation, instrument and bus logs of the intelligent cockpit domain controller can be obtained under the condition of being far away from the vehicle, and development and test personnel are helped to analyze the intelligent cockpit problem. When a use problem occurs in the vehicle intelligent cockpit domain, the method can select different modes to obtain the intelligent cockpit domain controller log according to an actual scene, so as to help development and test personnel to remotely check the problem.

Description

Technical Field

[0001] The present invention belongs to but is not limited to the field of vehicle remote communication technology, and in particular relates to a system and method for remotely acquiring logs of a smart cockpit domain controller. Background Art

[0002] The intelligent cockpit controller log is a record of the working information and fault information of each module of the system. It is stored in the cockpit controller and provides an important basis for developers and testers to analyze problems. However, the current process of obtaining these logs is relatively cumbersome. It requires using a USB flash drive to connect to the vehicle's USB port, enter a dedicated system to copy, and then send it through a computer. This process is particularly time-consuming and laborious during development and testing.

[0003] As a comprehensive system integrating multiple functions, the electrical architecture of intelligent connected vehicles is evolving towards regional control and central integration, and the functions of vehicle electronic units are becoming increasingly complex. The design of electrical architectures such as the new generation of intelligent cockpit domains has increased vehicle functions and made internal programming more complex, which has put forward higher requirements for quality. Once quality problems occur in the later stage, it will not only affect the customer's driving experience, but also increase after-sales costs.

[0004] In the face of the need for log management of in-vehicle electronic equipment, each domain has its corresponding log system. In order to better manage logs and facilitate software developers to locate problems, different log files need to be collected and imported into mobile devices, merged, and even uploaded to the cloud for remote analysis and diagnosis. Therefore, the log system needs to have a variety of functional components to cope with different log processing scenarios. In summary, the acquisition and management of smart cockpit controller logs are currently cumbersome and inefficient, and the development of smart connected vehicles has made the need for log management more urgent. Therefore, we need a faster, simpler and user-insensitive method to obtain relevant system logs and optimize the log management function to meet the needs of different processing scenarios.

[0005] There are several major technical problems in the existing technology for processing smart cockpit domain controller logs:

[0006] 1) The log acquisition method is cumbersome:

[0007] Currently, obtaining the smart cockpit system log usually requires physical means, such as using a USB flash drive to connect to the vehicle's USB port and entering a dedicated system to copy the log. This process is not only cumbersome, but also becomes very time-consuming and laborious during the development and testing process when a large number of bugs need to be dealt with.

[0008] 2) Poor user experience:

[0009] When a user's vehicle has a problem, the consumer or after-sales staff is required to cooperate in obtaining logs, which increases the user's burden and may cause user dissatisfaction.

[0010] 3) Inconvenient log management:

[0011] As vehicles become more intelligent, the functions of onboard electronic devices become more complex, and each domain has its own corresponding log system. This makes log management difficult, especially during software development and testing, when problems need to be located, log files need to be collected and imported from multiple domains.

[0012] 4) Remote analysis and diagnosis are limited:

[0013] The existing log acquisition method limits the ability of remote analysis and diagnosis. Developers and testers cannot quickly and conveniently obtain logs, which affects the timely resolution of problems and the improvement of vehicle quality.

[0014] 5) Lack of flexible log processing mechanism:

[0015] Existing log systems may lack flexibility and scalability and cannot adapt to different log processing scenarios. For example, different log files may need to be merged or uploaded to the cloud for remote analysis, but existing technologies may not support these operations.

[0016] In summary, the existing technology has obvious technical problems in the acquisition and management of smart cockpit domain controller logs, which affect the improvement of vehicle quality, user experience and the efficiency of remote analysis and diagnosis. Therefore, a new technical solution is urgently needed to solve these problems. Summary of the invention

[0017] In view of the problems existing in the prior art, the present invention provides a system and method for remotely acquiring logs of a smart cockpit domain controller.

[0018] The present invention is implemented as follows: a smart cockpit domain controller log remote acquisition system, characterized in that the smart cockpit domain controller log remote acquisition system specifically includes:

[0019] Remote application interface, used to provide a human-computer interaction interface for log acquisition;

[0020] TSP remote service platform, used to manage the log pull instruction network interface, upload log network interface, and storage of uploaded logs;

[0021] The intelligent cockpit domain controller CDC and large screen are used to internally record and store the system and application operation logs of each module running in the recent period;

[0022] 4G module is used for the intelligent cockpit domain controller CDC to establish mobile communication with the outside world.

[0023] Furthermore, the remote application interface establishes a connection with the TSP remote service platform, and a 4G Internet of Things card is built into the smart cockpit domain controller for establishing mobile communication between the smart cockpit domain controller and the outside. The smart cockpit domain controller establishes a wireless communication connection with the TSP remote service platform through the 4G module, and the 4G module establishes internal communication with the smart cockpit controller SOC system. The MCU module establishes internal communication with the SOC system. The MCU system is used for power management of the smart cockpit domain controller, CAN transceiver management, sleep and wake-up, bus data acquisition, etc. The SOC is the smart cockpit domain controller system chip, and the APK application is deployed on the SOC system.

[0024] Furthermore, the remote application interface is a log acquisition human-computer interaction interface, which is used by developers and testers to download uploaded logs according to vehicle model, VIN, log type, and time.

[0025] Furthermore, the log is used for developers and testers to understand the system operation status and view and analyze various problems that arise. The APK is deployed on the smart cockpit domain controller SOC system to obtain, package, and upload logs of each system module.

[0026] Another object of the present invention is to provide a method for remotely acquiring logs of a smart cockpit domain controller, the method specifically comprising:

[0027] S1: If there is a service personnel on the vehicle, the service personnel log in to APK from the smart cockpit screen, select the log type: vehicle computer, voice, navigation, instrument, bus, and then select upload. After APK completes log packaging, it calls the "log file upload" API network interface of the TSP platform to upload. APK displays the packaging and upload progress on the large screen. After the log upload is completed, APK calls the "log upload completion message report" API network interface to report the "log upload completed" message. The development and test personnel log in to the remote application interface, enter the corresponding vehicle VIN number, select the log uploaded at the corresponding time, and download it;

[0028] S2: If there is no available service personnel for the vehicle, the developer or tester logs in to the remote application interface, enters the corresponding vehicle VIN number, selects the log type: vehicle computer, voice, navigation, instrument, bus, and clicks the pull log function;

[0029] S3: After clicking the "pull log" button, the remote log application interface calls the log acquisition HTTPS interface of the TSP platform, attaches the vehicle type, VIN number, and log type parameters, and notifies the TSP platform. The TSP platform first determines whether the 4G module of the smart cockpit domain controller is online. If not, the TSP platform first sends a wake-up SMS to the IoT card number built into the 4G module. After receiving the wake-up SMS, the 4G module starts to wake up as a whole and initiates a connection login to the TSP platform. After the TSP platform confirms the login information and verifies it and replies with an ACK response, the 4G module initiates a heartbeat connection to the TSP (once every 30 seconds) to establish a TCP long connection with the TSP platform;

[0030] S4: After the TCP long connection is established, the TSP platform sends a TCP command to pull the log of the smart cockpit domain controller. After the 4G module obtains the TCP command, it returns an ACK response to the TSP platform;

[0031] S5: After the APK application packaging log is completed, the log package is first stored in the SOC system. Then the SOC system calls the "log file upload" API network interface of the TSP platform to start uploading the log compression package until the upload is completed;

[0032] S6: The TSP platform saves the smart cockpit controller log to the database according to the VIN, and the development and testing personnel download the corresponding log for viewing in the remote application interface.

[0033] Further, in S4, after the 4G module obtains the TCP instruction, the 4G module first detects the current 4G network signal. If the RSRP signal value is less than -100dbm, it directly determines that the current mobile network signal does not meet the requirements, and replies to the TSP platform "Log pulling failed due to weak vehicle environment network signal";

[0034] If the signal meets the requirements, the 4G module wakes up the SOC system. After the SOC starts working, it sends the log pull instruction message to the smart cockpit domain controller SOC system through serial port communication;

[0035] The SOC system first detects the vehicle status through the MCU module. If the vehicle power gear is in the ON gear, it replies to the 4G module "The current vehicle is in the ON gear, which does not meet the log pulling status." The 4G module then replies the message to the TSP platform for prompting;

[0036] If the SOC system detects that the vehicle power gear is in the OFF gear, it will continue to detect whether the current vehicle power voltage is greater than 12V. If the power voltage is less than 12V, it will reply to the 4G module "The current vehicle power voltage is insufficient, and the log pulling will fail";

[0037] The 4G module uniformly replies the above command execution failure message to the TSP platform to complete the pull command connection.

[0038] If the power supply voltage is greater than 12V, the log pulling status is met, and the SOC system continues to detect the APK application status;

[0039] If the APK application is not started, the SOC system starts the APK application, and then goes to the next step after the APK application is started;

[0040] After the APK application obtains the pulled log message, it first confirms the type of log obtained in the message (vehicle computer, voice, navigation, instrument, bus), obtains different log types as needed, and APK performs log packaging work respectively. It can be packaged separately, in any combination, or all logs can be packaged. The packaging type is rar format;

[0041] After detecting that the APK application is working, the SOC system replies to the 4G module with a notification message of "execution and sending are successful". The 4G module then replies this message to the TSP platform to complete the log pulling TCP instruction connection.

[0042] Further, in the S5, during the remote log pulling and uploading process, the vehicle CAN bus is not awakened, and the large screen, instrument and other display screens are not awakened. After the log upload is completed, the APK continues to call the "log upload completion message reporting" API network interface to report the "log upload completed" message. If the following abnormal conditions exist during the remote log process, the APK application calls the "log upload completion message reporting" API network interface and feedbacks the specific abnormal message according to the specific abnormality:

[0043] (1) Log packaging failed

[0044] (2) Log upload failed

[0045] (3) Internal communication abnormality

[0046] (4)Other abnormal circumstances.

[0047] The present invention also provides a log remote acquisition software system for an intelligent cockpit domain controller, the software system comprising the following functional modules:

[0048] Log capture module: Log in to the log capture application through the smart cockpit screen in the vehicle, select the log type, perform log packaging and upload operations, and display the packaging and upload progress;

[0049] Remote log acquisition module: log in to the remote log platform, enter the VIN number of the corresponding vehicle, select the log type and initiate a log pull request to obtain and download the corresponding log file;

[0050] TSP platform interface module: provides communication interface with TSP platform, including "log file upload" API network interface and "log upload completion message reporting" API network interface, supports log upload and upload completion status reporting;

[0051] 4G module wake-up and connection module: detects 4G network signals and sends wake-up SMS messages to wake up the 4G module as needed, establishes a TCP long connection with the TSP platform, and processes ACK responses and heartbeat connections during the connection process;

[0052] Log processing and storage module: Pack and store log files in the SOC system of the smart cockpit domain controller, and upload the log compression package through the API interface of the TSP platform;

[0053] Exception handling module: Detects and handles various exceptions during the log upload process, such as log packaging failure, log upload failure, internal communication exceptions, etc., and reports specific exception messages.

[0054] In combination with the above technical solutions and the technical problems solved, the advantages and positive effects of the technical solutions to be protected by the present invention are as follows:

[0055] First, the present invention can obtain the vehicle computer, voice, navigation, instrument, and bus logs of the smart cockpit domain controller when away from the vehicle, helping developers and testers analyze smart cockpit problems. When a problem occurs in the vehicle's smart cockpit domain, the present invention can select different methods to obtain the smart cockpit domain controller logs according to the actual scenario to help developers and testers view the problem remotely.

[0056] The smart cockpit controller log records the working information and fault information of each module of the system produced by the smart cockpit system, and is saved in the cockpit controller for developers and testers to analyze problems. In actual work, it is usually necessary to connect a USB flash drive to the vehicle's USB interface and enter a dedicated system copy, and then send it using a computer. The process is cumbersome, especially when there are a large number of bugs during the development and testing process. It is time-consuming and laborious. Moreover, when such problems occur in the user's vehicle, consumers or after-sales personnel are required to cooperate with this work, and the process is cumbersome. A quick, simple, and user-insensitive method is urgently needed to obtain relevant system logs.

[0057] Through this solution, testers can quickly upload system logs without tools, and developers can directly download system logs based on the vehicle VIN in the background and quickly locate problems without any intermediate links. For problems with the user's vehicle smart cockpit, the vehicle-side smart cockpit system logs can be obtained from the background without disturbing the user or requiring service personnel to come to the site to handle the problem. The TSP platform can store past logs for developers to review historical problems.

[0058] Second, the technical solution of the present invention solves the technical problems that people have been eager to solve but have never been able to solve successfully:

[0059] 1. The present invention solves the problem of quickly acquiring logs during the development and testing of the intelligent cockpit system without any additional tools, which is simple and convenient.

[0060] 2. The present invention solves the problem of managing the logs of the smart cockpit system. The logs are stored on the platform for a long time and can be viewed, downloaded and retrieved at any time.

[0061] 3. The present invention solves the problem of obtaining the smart cockpit system log without disturbing the user or requiring service personnel when a type of fault occurs in the user's vehicle and the cause of the problem needs to be analyzed. It does not affect the use of the vehicle.

[0062] Third, the log acquisition method for the intelligent cockpit domain controller of the present invention significantly improves the efficiency of log acquisition and management. First, wireless transmission technology (such as Bluetooth, Wi-Fi or cellular network) is used to realize the automatic collection and transmission of log data, reducing the manual operation steps. Secondly, the event triggering and scheduled task functions are integrated to ensure the real-time and integrity of the log data, which is convenient for developers and testers to conduct real-time monitoring and analysis. By providing a unified log management platform, log data from different modules can be centrally stored, merged and analyzed, greatly simplifying the complexity of log management.

[0063] The present invention significantly improves the efficiency of development, testing and after-sales service of intelligent connected vehicles. During the development and testing phase, the automated log acquisition and management system helps engineers quickly discover and solve problems, improving the work efficiency of development and testing. In after-sales service, system logs can be automatically acquired without user intervention, supporting remote diagnosis and maintenance, reducing the workload of on-site services and reducing after-sales costs. At the same time, by retrieving historical logs to review and analyze historical problems, the efficiency of problem solving is further improved.

[0064] The present invention not only improves technical efficiency, but also significantly enhances user experience and data security. By reducing the operational burden of users in the process of log acquisition, the user experience is optimized and the user satisfaction with intelligent connected vehicles is improved. Data encryption and access control measures are adopted to ensure the security and privacy protection of log data during transmission and storage, providing a strong guarantee for the efficient and safe operation of the intelligent cockpit system. These technological advances have provided a solid foundation for the development of intelligent connected vehicles and promoted technological progress in the entire industry. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 This is a diagram of the architecture of a smart cockpit domain controller log remote acquisition system provided by an embodiment of the present invention;

[0066] Figure 2 is a flow chart of a method for remotely acquiring logs of a smart cockpit domain controller provided by an embodiment of the present invention;

[0067] Figure 3 It is a detailed architecture diagram of the intelligent cockpit domain controller log remote acquisition system provided by an embodiment of the present invention;

[0068] Figure 1 In: 1. Remote application interface; 2. TSP remote service platform; 3. 4G module; 4. Smart cockpit domain controller CDC and large screen. DETAILED DESCRIPTION

[0069] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0070] like Figure 2 As shown, an embodiment of the present invention provides a method for remotely acquiring logs based on a smart cockpit domain controller, comprising the following steps:

[0071] S1: If there is a service person on the vehicle, the service person logs in to APK from the smart cockpit screen (APK is Android Application package), select the log type: car machine, voice, navigation, instrument, bus, and then select upload. After APK completes log packaging, call the "log file upload" API network interface of the TSP platform to upload (TSP platform is a remote service platform). APK displays the packaging and upload progress on the large screen. After the log upload is completed, APK calls the "log upload completion message report" API network interface (API is the application program interface) to report the "log upload completed" message. Development and testing personnel log in to the remote log platform, enter the corresponding vehicle VIN number (VIN is the vehicle identification number), select the corresponding uploaded log, and download it;

[0072] S2: If there is no available service personnel for the vehicle, the development and testing personnel log in to the remote log platform, enter the corresponding vehicle VIN number, select the log type: vehicle computer, voice, navigation, instrument, bus, and click to pull the log;

[0073] S3: After clicking the "pull log" button, the remote log application interface calls the log acquisition HTTPS interface of the TSP platform, attaches the vehicle type, VIN number, and log type parameters, and notifies the TSP platform. The TSP platform first determines whether the 4G module of the smart cockpit domain controller is online. If not, the TSP platform first sends a wake-up SMS to the IoT card number built into the 4G module. After receiving the wake-up SMS, the 4G module starts to wake up as a whole and initiates a connection login to the TSP platform. After the TSP platform confirms the login information and verifies it and replies with an ACK response, the 4G module initiates a heartbeat connection to the TSP (once every 30 seconds) to establish a TCP long connection with the TSP platform;

[0074] S4: After the TCP long connection is established, the TSP platform sends a TCP command to pull the log of the smart cockpit domain controller. After the 4G module obtains the TCP command, it returns an ACK response to the TSP platform;

[0075] S5: After the APK application packaging log is completed, the log package is first stored in the SOC system (SOC intelligent cockpit domain controller system-level chip). Then the SOC system calls the "log file upload" API network interface of the TSP platform to start uploading the log compression package until the upload is completed;

[0076] S6: The TSP platform saves the smart cockpit controller log to the database according to the VIN, and the development and testing personnel download the corresponding log on the remote application terminal for viewing.

[0077] In step S4, the 4G module first detects the current 4G network signal. If the RSRP signal value is less than -100dbm, it is directly determined that the current mobile network signal does not meet the requirements, and the TSP platform is replied that "the log pulling failed due to the weak network signal in the vehicle environment"; if the signal meets the requirements, the 4G module wakes up the SOC system. After the SOC starts working, it sends the log pulling instruction message to the smart cockpit domain controller SOC system through serial communication; the SOC system first detects the status of the vehicle through the MCU module (the MCU module is the microcontroller unit of the smart cockpit domain controller). If the vehicle power gear is in the ON gear state, it replies to the 4G module "the current vehicle is in the ON gear and does not meet the log pulling status", and the 4G module replies the message to the TSP platform for prompting; if the SOC system detects that the current vehicle power gear is in the OFF gear state, it continues to detect whether the current vehicle power voltage is greater than 12V, If the power supply voltage is less than 12V, the 4G module is replied with "the current vehicle power supply voltage is insufficient and log pulling will fail"; if the power supply voltage is greater than 12V, the log pulling status is met, and the SOC system continues to detect the APK application status; if the APK application is not started, the SOC system starts the APK application, and goes to the next step after the APK application is started; after the APK application obtains the log pulling message, it first confirms the type of log to be obtained (vehicle computer, voice, navigation, instrument, 4G module, bus), and obtains different log types as needed. APK performs log log packaging work separately, which can be packaged separately, in any combination, or all logs can be packaged, and the packaging type is rar format; after detecting that the APK application is working, the SOC system replies to the 4G module with the "execution sending is successful" notification message, and the 4G module then replies this message to the TSP platform to complete the log pulling TCP instruction connection.

[0078] In step S5, during the remote log pulling and uploading process, the vehicle CAN bus, large screen, instrument and other display screens will not be awakened. After the log upload is completed, the log capture APK continues to call the "log upload completion message report" API network interface to report the "log upload completed" message. If the following abnormal conditions occur during the remote log process, the APK application calls the "log upload completion message report" API network interface and feedbacks the specific abnormal message according to the specific abnormality:

[0079] (1) Log packaging failed;

[0080] (2) Log upload failed;

[0081] (3) Internal communication abnormalities;

[0082] (4)Other abnormal circumstances.

[0083] like Figure 1 , 3As shown, an embodiment of the present invention provides a system for remotely acquiring logs of a smart cockpit domain controller, and the system specifically includes:

[0084] Remote application interface 1, TSP remote service platform 2, smart cockpit domain controller CDC and large screen 4, 4G module 3;

[0085] Remote application interface 1, used to obtain the human-computer interaction interface for the log;

[0086] TSP remote service platform 2, used to manage the log pull instruction network interface, upload log network interface, and storage of uploaded logs;

[0087] The intelligent cockpit domain controller CDC and large screen 4 are used to internally record and store the system and application operation logs of each module running in the recent period;

[0088] The 4G module 3 is used to establish mobile communication with the outside.

[0089] The remote application interface establishes a connection with the TSP remote service platform, and a 4G Internet of Things card is built into the smart cockpit domain controller for establishing mobile communication between the smart cockpit domain controller and the outside. The smart cockpit domain controller establishes a wireless communication connection with the TSP remote service platform through the 4G module, and the 4G module establishes internal communication with the smart cockpit controller SOC system. The MCU module establishes internal communication with the SOC system. The MCU system is used for power management, CAN transceiver management, sleep and wake-up, etc. of the smart cockpit domain controller. The SOC is the system chip of the smart cockpit domain controller, and the log capture APK application is deployed on the SOC system.

[0090] The remote application interface is a log acquisition human-computer interaction interface, which is used by developers and testers to download uploaded logs according to vehicle model, VIN, log type, and time.

[0091] The logs are used by developers and testers to understand the system operation status and view and analyze various problems that arise. The APK is deployed on the smart cockpit domain controller SOC system and is used to obtain, package, and upload logs of each system module.

[0092] The present invention is mainly used in the development, testing and after-sales of intelligent connected vehicles, as an important part of the software development tools of vehicle manufacturers. Specific application areas and related products include:

[0093] 1) Intelligent connected vehicle development:

[0094] Provide automakers and suppliers with more efficient log acquisition and management tools to support the development of vehicle electronic systems and smart cockpit systems.

[0095] Provides real-time log monitoring and analysis capabilities in the development environment to help engineers quickly discover and solve problems.

[0096] 2) Intelligent connected vehicle testing:

[0097] During the testing phase, various test logs can be easily obtained and analyzed, supporting automated testing and regression testing.

[0098] The integrated testing platform allows testers to remotely access and analyze test data, improving test efficiency and coverage.

[0099] 3) After-sales service of intelligent connected vehicles:

[0100] In after-sales service, the vehicle's system logs can be automatically obtained without user intervention, supporting remote diagnosis and maintenance.

[0101] It reduces the workload of on-site service personnel, reduces after-sales costs, and improves customer satisfaction.

[0102] Evidence of the technical effects obtained by the embodiments of the present invention

[0103] 1. Improve log acquisition efficiency

[0104] Automated log collection: Log data is automatically collected through wireless transmission (such as Bluetooth, Wi-Fi, or cellular networks), reducing manual operation steps and improving the efficiency of log acquisition.

[0105] Event triggering and scheduled tasks: Automatically trigger log upload when an abnormality occurs in the system, or upload logs regularly through scheduled tasks to ensure the real-time and integrity of log data.

[0106] 2. Facilitate log management for development and test engineers

[0107] Integrated management platform: Provides a unified log management platform that supports centralized storage, merging, and analysis of log data, making it easier for developers and testers to locate and resolve problems.

[0108] Historical log review: Ability to retrieve historical logs to facilitate review and analysis of historical issues and improve problem-solving efficiency.

[0109] 3. Improve the convenience of after-sales service

[0110] Reduce user intervention: During the after-sales service process, system logs can be automatically obtained without user cooperation, which reduces the user's operation burden and improves the user experience.

[0111] Remote diagnosis and maintenance: Developers can remotely access log data to perform problem diagnosis and maintenance without having to arrange service personnel to capture logs on site, thus reducing after-sales costs.

[0112] 4. Rich integration functions

[0113] Multi-module log management: supports log data collection and merging of multiple electronic units, unified management, and reduces the complexity of data processing.

[0114] Secure transmission and storage: Data encryption and access control measures are used to ensure the security and privacy of log data.

[0115] Through the above analysis, the present invention provides an efficient and convenient method for obtaining logs of intelligent cockpit domain controllers, which solves the problems of cumbersomeness, time-consuming and poor user experience in the prior art. The method has broad application prospects in the development, testing and after-sales fields of intelligent connected vehicles, and can significantly improve the efficiency of log acquisition and management, optimize the development and testing process, reduce after-sales costs, and improve user satisfaction.

[0116] Embodiment 1:

[0117] In order to improve the development and after-sales efficiency of intelligent connected vehicles, a certain automobile manufacturer adopted the remote acquisition system of the intelligent cockpit domain controller log of the present invention. When the developers were developing the intelligent cockpit system of the new model, they encountered an occasional fault that was difficult to reproduce. In order to quickly locate and solve the problem, the developers entered the VIN number of the faulty vehicle through the remote log acquisition module, selected the "car" and "voice" log types, and initiated a log pull request. After receiving the request, the TSP platform interface module woke up the 4G module of the faulty vehicle through the 4G module wake-up and connection module, and established a TCP long connection with the TSP platform. The log processing and storage module packaged the relevant log files in the SOC system of the intelligent cockpit domain controller, and uploaded the log compression package through the API interface of the TSP platform. The developer then downloaded the log file, successfully analyzed the cause of the failure, and fixed the problem in time.

[0118] Embodiment 2:

[0119] An after-sales service center for smart connected vehicles received a complaint from a user about the slow operation of the smart cockpit system. In order to quickly respond to users and solve problems, after-sales personnel used the remote acquisition system for the smart cockpit domain controller log of the present invention. The after-sales staff entered the VIN number of the user's vehicle through the remote log acquisition module and selected all log types for pulling. The TSP platform interface module and the 4G module wake-up and connection module collaborated to successfully wake up the 4G module of the user's vehicle and establish a connection. The log processing and storage module packages and uploads all log files of the smart cockpit domain controller. After the after-sales staff downloaded the log files, they found through log analysis that the reason for the slow operation of the system was that a background service abnormality occupied a large amount of resources. The after-sales staff then guided the user to restart the smart cockpit system and cleared the abnormal background service, successfully solving the problem and improving user satisfaction.

[0120] It should be noted that the embodiments of the present invention can be implemented by hardware, software, or a combination of software and hardware. The hardware part can be implemented using dedicated logic; the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated design hardware. A person of ordinary skill in the art will appreciate that the above-mentioned devices and methods can be implemented using computer executable instructions and / or contained in a processor control code, such as a carrier medium such as a disk, CD or DVDROM, a programmable memory such as a read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. Such code is provided on the carrier medium. The device and its modules of the present invention can be implemented by hardware circuits such as very large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., can also be implemented by software executed by various types of processors, and can also be implemented by a combination of the above-mentioned hardware circuits and software, such as firmware.

[0121] The above description is only a specific implementation mode of the present invention, but the protection scope of the present invention is not limited thereto. Any modifications, equivalent substitutions and improvements made by any technician familiar with the technical field within the technical scope disclosed by the present invention and within the spirit and principle of the present invention should be covered by the protection scope of the present invention.

Claims

1. A remote acquisition system for intelligent cockpit domain controller logs, characterized in that: The system includes: Remote application interface, used to obtain the human-computer interaction interface for logs; TSP remote service platform, used to manage the log pull instruction network interface, upload log network interface, and storage of uploaded logs; The intelligent cockpit domain controller CDC and large screen are used to internally record and store the system and application operation logs of each module running in the recent period; 4G module, used to establish mobile communication with the outside world.

2. The intelligent cockpit domain controller log remote acquisition system as claimed in claim 1, characterized in that: The remote application interface establishes a connection with the TSP remote service platform, and a 4G Internet of Things card is built into the smart cockpit domain controller for establishing mobile communication between the smart cockpit domain controller and the outside. The smart cockpit domain controller establishes a wireless communication connection with the TSP remote service platform through the 4G module. The 4G module establishes internal communication with the smart cockpit controller SOC system, and the MCU module establishes internal communication with the SOC system. The MCU system is used for power management, CAN transceiver management, and sleep and wake-up of the smart cockpit domain controller. The SOC is the system chip of the smart cockpit domain controller, and the log capture APK application is deployed on the SOC system.

3. The intelligent cockpit domain controller log remote acquisition system as claimed in claim 1, characterized in that: The remote application interface is a log acquisition human-computer interaction interface, which is used by developers and testers to download uploaded logs according to vehicle model, VIN, log type, and time.

4. The intelligent cockpit domain controller log remote acquisition system as claimed in claim 1, characterized in that: The logs are used by developers and testers to understand the system operation status and view and analyze various problems that arise. The APK is deployed on the smart cockpit domain controller SOC system and is used to obtain, package, and upload logs of each system module.

5. A method for remotely acquiring logs of a smart cockpit domain controller according to claims 1 to 4, characterized in that: The following steps are involved: S1: If there is a service personnel on the vehicle, the service personnel log in to the log on the smart cockpit screen to grab the APK, select the log type: car machine, voice, navigation, instrument, bus, and then select upload. After the APK completes the log packaging, it calls the "log file upload" API network interface of the TSP platform to upload. The APK displays the packaging and upload progress on the large screen. After the log upload is completed, the APK calls the "log upload completion message report" API network interface to report the "log upload completed" message. The development and test personnel log in to the remote log platform, enter the corresponding vehicle VIN number, select the corresponding uploaded log, and download it; S2: If there is no available service personnel for the vehicle, the development and testing personnel log in to the remote log platform, enter the corresponding vehicle VIN number, select the log type: vehicle computer, voice, navigation, instrument, bus, and click to pull the log; S3: After clicking the "pull log" button, the remote log application interface calls the log acquisition HTTPS interface of the TSP platform, attaches the vehicle type, VIN number, and log type parameters, and notifies the TSP platform. The TSP platform first determines whether the 4G module of the smart cockpit domain controller is online. If not, the TSP platform first sends a wake-up SMS to the IoT card number built into the 4G module. After receiving the wake-up SMS, the 4G module starts to wake up as a whole and initiates a connection login to the TSP platform. After the TSP platform confirms the login information and verifies it and replies with an ACK response, the 4G module initiates a heartbeat connection to the TSP (once every 30 seconds) to establish a TCP long connection with the TSP platform; S4: After the TCP long connection is established, the TSP platform sends a TCP command to pull the log of the smart cockpit domain controller. After the 4G module obtains the TCP command, it returns an ACK response to the TSP platform; S5: After the APK application packaging log is completed, the log package is first stored in the SOC system. Then the SOC system calls the "log file upload" API network interface of the TSP platform to start uploading the log compression package until the upload is completed; S6: The TSP platform saves the smart cockpit controller log to the database according to the VIN, and the development and testing personnel download the corresponding log on the remote application terminal for viewing.

6. The method for remotely acquiring logs of a smart cockpit domain controller according to claim 5, characterized in that: In the step S4, the 4G module first detects the current 4G network signal. If the RSRP signal value is less than -100dbm, it is directly determined that the current mobile network signal does not meet the requirements, and the TSP platform is replied "Log pulling failed due to weak vehicle environment network signal"; if the signal meets the requirements, the 4G module wakes up the SOC system, and after the SOC starts working, the log pulling instruction message is sent to the smart cockpit domain controller SOC system through serial communication; the SOC system first detects the status of the vehicle through the MCU module. If the vehicle power gear is in the ON gear state, it replies to the 4G module "The current vehicle is in the ON gear and does not meet the log pulling state", and the 4G module replies the message to the TSP platform for prompting; If the SOC system detects that the current vehicle power gear is in the OFF gear state, it will continue to detect whether the current vehicle power voltage is greater than 12V. If the power voltage is less than 12V, it will reply to the 4G module "the current vehicle power voltage is insufficient, and pulling logs will fail"; if the power voltage is greater than 12V, the state of pulling logs is satisfied, and the SOC system will continue to detect the APK application state; if the APK application is not started, the SOC system will start the APK application, and go to the next step after the APK application starts; after the APK application obtains the pull log message, it first confirms the type of log to be obtained, and obtains different log types as needed. The APK performs log log packaging work separately, which can be packaged separately, in any combination, or all logs can be packaged, and the packaging type is rar format; After detecting that the APK application is working, the SOC system replies to the 4G module with a notification message of "execution and sending are successful". The 4G module then replies this message to the TSP platform to complete the log pulling TCP instruction connection.

7. The method for remotely acquiring logs of a smart cockpit domain controller according to claim 5, characterized in that: In the step S5, during the remote log pulling and uploading process, the vehicle CAN, large screen, and instrument display screen are not awakened. After the log upload is completed, the log capture APK continues to call the "log upload completion message report" API network interface to report the "log upload completed" message. If the following abnormal conditions occur during the remote log process, the APK application calls the "log upload completion message report" API network interface and feedbacks the specific abnormal message according to the specific abnormality: (1) Log packaging failed; (2) Log upload failed; (3) Internal communication abnormalities; (4)Other abnormal circumstances.

8. A log remote acquisition software system for a smart cockpit domain controller, characterized in that: The software system includes the following functional modules: Log capture module: Log in to the log capture application through the smart cockpit screen in the vehicle, select the log type, perform log packaging and upload operations, and display the packaging and upload progress; Remote log acquisition module: log in to the remote log platform, enter the VIN number of the corresponding vehicle, select the log type and initiate a log pull request to obtain and download the corresponding log file; TSP platform interface module: provides communication interface with TSP platform, including "log file upload" API network interface and "log upload completion message reporting" API network interface, supporting log upload and upload completion status reporting; 4G module wake-up and connection module: detects 4G network signals and sends wake-up SMS messages to wake up the 4G module as needed, establishes a TCP long connection with the TSP platform, and processes ACK responses and heartbeat connections during the connection process; Log processing and storage module: Pack and store log files in the SOC system of the smart cockpit domain controller, and upload the log compression package through the API interface of the TSP platform; Exception handling module: Detects and handles various exceptions during the log upload process, including log packaging failure, log upload failure, internal communication exceptions, and reports specific exception messages.

9. A log remote acquisition software system for a cockpit domain controller based on the system of claim 1, characterized in that: The software system has the following functional features: Automatic log packaging and uploading: It can automatically complete the log type selection, log packaging and uploading operations according to the selection of service personnel or remote users, and display the progress on the large screen; Real-time network status detection: It can detect the 4G network signal strength in real time to determine whether the log pulling conditions are met. If the signal is insufficient, the corresponding failure message will be reported; Intelligent wake-up and connection: Wake up the 4G module by sending a wake-up SMS, establish a TCP long connection with the TSP platform, and ensure the stability of the connection process; Dynamic log processing: It can intelligently determine whether to pull logs based on the vehicle's power status and voltage level, and start the corresponding APK application to package the logs; Support for multiple types of logs: supports the capture and packaging of multiple types of logs, including vehicle computer, voice, navigation, instrument, and bus. The packaged log types can be selected individually or in combination, and supports log compression packages up to 1G; Exception handling and reporting: During the log packaging or uploading process, various exceptions can be detected and handled, and specific exception messages can be reported through the API interface to ensure system stability and the reliability of log acquisition.

Images