Remote debugging method and system for vehicle-mounted system

Abstract

The invention discloses a remote debugging method for a vehicle-mounted system, and the method comprises the steps: S100, generating an access token at a vehicle equipment end, and transmitting the access token to a cloud server; s200, the PC debugging end accesses the cloud server and obtains an access token of the vehicle-mounted equipment to be debugged after starting up; s300, the PC debugging end is connected with the vehicle machine equipment to be debugged after starting up according to the access token; and S400, the PC debugging end carries out online debugging on the vehicle-mounted system of the vehicle machine equipment. According to the invention, the processing capability and processing speed of the vehicle-mounted system fault are enhanced, the time from the occurrence of the fault to the start of troubleshooting is greatly shortened, the vehicle does not need to be returned to a factory, a large amount of time is saved for a user, and the influence on the travel of the user is greatly reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking remote control, and in particular to a remote debugging method and system for a vehicle-mounted system. Background Art

[0002] With the development of smart cockpits, smart in-vehicle systems are becoming increasingly popular due to their excellent human-computer interaction experience and comprehensive intelligent functionality. If problems arise during use, the typical solution is to contact the manufacturer and contact engineers to investigate the issues based on user feedback and video footage. However, sometimes the problem is more complex, and remote diagnosis and timely resolution are impossible. In these cases, the vehicle must be returned to the factory for repair, resulting in inconvenient and costly maintenance of smart in-vehicle equipment. Summary of the Invention

[0003] The main purpose of the present invention is to address the shortcomings of the prior art in that vehicle-mounted systems are inconvenient to maintain and require high maintenance costs by returning to the factory, and to provide a remote debugging method and system for a vehicle-mounted system, comprising step S100: the vehicle-mounted device generates an access token and transmits it to a cloud server; step S200: the PC debugging end accesses the cloud server to obtain the access token of the vehicle-mounted device that is powered on to be debugged; step S300: the PC debugging end connects to the vehicle-mounted device that is powered on to be debugged based on the access token; step S400: the PC debugging end performs online debugging of the vehicle-mounted system of the vehicle-mounted device.

[0004] Preferably, step S100 includes: the vehicle device receives the debugging feedback instruction, obtains the identity information, current display time, preset timeout period, and IP address of the vehicle device, packages and generates an access token data packet, and transmits it to the cloud server. The cloud server stores and parses the access token data packet, and after the parsing is completed, sends an identity information display signal to the vehicle device.

[0005] Preferably, step S200 includes: after the vehicle-mounted device receives the identity information display signal, the vehicle-mounted device provides the identity information of the vehicle-mounted device to the vehicle owner communication terminal in a visual display manner; the vehicle owner communication terminal transmits the identity information of the vehicle-mounted device to be debugged to the service communication terminal via base station transmission or Internet server transmission; the service communication terminal inputs the identity information of the vehicle-mounted device to be debugged into the PC debugging terminal; the PC debugging terminal accesses the cloud server by verifying the account password, and sends the identity information and query instructions to the cloud server; the cloud server queries and compares the identity information in the stored access token with the identity information transmitted by the PC debugging terminal to see whether they are consistent; if they are consistent, the IP address and identity information in the corresponding access token are transmitted to the PC debugging terminal.

[0006] Preferably, step S300 includes: the PC debugging end connects to the vehicle device end that is powered on and to be debugged according to the IP address in the access token, and transmits the identity information in the access token to the vehicle device end, and the vehicle device end determines whether the identity information of the access token is consistent with the identity information of the vehicle device obtained locally. If so, it further determines whether the connection time with the PC debugging end is greater than the preset timeout time. If not, the PC debugging end is authorized to initiate a data transmission request permission for authentication.

[0007] Preferably, step S400 includes: the PC debugging end initiates a data capture request to the vehicle device end, the vehicle device end collects log data and file data, and packages and transmits them to the PC debugging end, and the PC debugging end uses the debugging method obtained by analyzing the collected data to perform online debugging on the vehicle system of the vehicle device end.

[0008] In addition, to achieve the above-mentioned purpose, the present invention also provides a remote debugging system for a vehicle-mounted system, including: a generation module for generating an access token; a transmission module for transmitting the access token to a voice provider end, for outputting application instruction information to a smart device; an access module for accessing a cloud server; an acquisition module for acquiring an access token for a vehicle-mounted device that is powered on and waiting to be debugged; a connection module for connecting with the vehicle-mounted device that is powered on and waiting to be debugged according to the access token; a debugging module for performing online debugging of the vehicle-mounted system of the vehicle-mounted device; the generation module and the transmission module are located in the vehicle-mounted device end, the access module, the acquisition module, and the debugging module are located in the PC debugging end, and the connection module is located between the vehicle-mounted device end and the PC debugging end.

[0009] Preferably, the remote debugging system also includes a receiving module, a storage module, and a parsing module. The receiving module is located in the vehicle device end, the storage module and the parsing module are located in the cloud server, the acquisition module is also located in the PC debugging end, and the transmission module is also located in the cloud server; the acquisition module is also used to obtain the identity information, current display time, preset timeout period, and IP address of the vehicle device; the receiving module is used to receive debugging feedback instructions; the storage module is used to store access token data packets; the parsing module is used to parse access token data packets; the transmission module is also used to send identity information display signals to the vehicle device end.

[0010] Preferably, the remote debugging system also includes a display module and a query and comparison module. The display module is located in the vehicle device end, and the query and comparison module is located in the cloud server; the display module is used to visually display the identity information of the vehicle device; the query and comparison module is used to query and compare whether the identity information in the stored access token is consistent with the identity information transmitted by the PC debugging end; the receiving module is also used to receive the identity information display signal; the transmission module is also located in the vehicle owner communication end, and the transmission module is also used to transmit the identity information of the vehicle device to be debugged to the service communication end through base station transmission or Internet server transmission, and transmit the IP address and identity information in the corresponding access token to the PC debugging end.

[0011] Preferably, the remote debugging system also includes a judgment module and an authorization authentication module, and the judgment module and the authorization authentication module are located in the vehicle device end; the judgment module is used to judge whether the identity information of the access token is consistent with the identity information of the vehicle device obtained locally, and to judge whether the connection time with the PC debugging end is greater than the preset timeout time; the authorization authentication module is used to authorize and authenticate the data transmission request permission initiated by the PC debugging end; the transmission module is also located in the PC debugging end, and the transmission module is also used to transmit the identity information in the access token to the vehicle device end.

[0012] Preferably, the remote debugging system also includes a collection module, which is located in the vehicle-mounted device end, and the collection module is used to collect log data and file data; the transmission module is also used to initiate a data capture request to the vehicle-mounted device end, and transmit the log data and file data to the PC debugging end, and the debugging module is also used to use the debugging method obtained by analyzing the collected data to perform online debugging on the vehicle-mounted system of the vehicle-mounted device end.

[0013] A remote debugging method for an in-vehicle system provided by the present invention has the following beneficial effects: when the vehicle owner reports a fault, the vehicle-mounted device automatically generates an access token, which serves as a credential for the remote debugging end to connect to the vehicle-mounted device, thereby realizing remote connection to the vehicle-mounted device. After the connection, the log data and file data in the in-vehicle system can be obtained, and the log data, file data and debugging process can be shared synchronously with multiple people, thereby enhancing the processing capability and speed of in-vehicle system faults, greatly shortening the time from the occurrence of a fault to the start of fault troubleshooting, eliminating the need for the vehicle to be returned to the factory, saving users a lot of time, and greatly reducing the impact on users' travel. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only embodiments of the present invention. Those skilled in the art can also derive other drawings based on the provided drawings without inventive work.

[0015] Figure 1 FIG2 is a flow chart of a remote debugging method for an in-vehicle system provided by an embodiment of the present invention.

[0016] Figure 2 FIG2 is a schematic diagram showing the structure of system modules of a remote debugging system for an in-vehicle system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0017] To facilitate understanding of the present invention, the present invention will be described more fully below with reference to the accompanying drawings. The drawings illustrate exemplary embodiments of the present invention. However, the present invention may be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and comprehensive understanding of the present invention.

[0018] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0019] The general idea of the present invention is: to address the shortcomings of the existing technology that the vehicle-mounted system is inconvenient to maintain and has high maintenance costs when it needs to be returned to the factory, a remote debugging method and system for the vehicle-mounted system are provided. When the owner reports a fault, the vehicle-mounted device automatically generates an access token, which serves as a credential for the remote debugging end to connect to the vehicle-mounted device, thereby realizing remote connection to the vehicle-mounted device. After the connection, the log data and file data in the vehicle-mounted system can be obtained, and the log data, file data and debugging process can be shared synchronously with multiple people, thereby enhancing the processing capability and speed of vehicle-mounted system faults, greatly shortening the time from the occurrence of a fault to the start of fault investigation, eliminating the need for the vehicle to be returned to the factory, saving users a lot of time, and greatly reducing the impact on users' travel.

[0020] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the drawings and specific implementation methods of the specification. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present application, rather than limitations on the technical solution of the present application. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0021] Reference Figure 1 , Figure 1 FIG. 1 is a flow chart of a remote debugging method for an in-vehicle system provided by one embodiment of the present invention. In this embodiment, a remote debugging method for an in-vehicle system includes:

[0022] Step S100: The vehicle device generates an access token and transmits it to the cloud server.

[0023] When the vehicle-mounted device requires maintenance and debugging, it automatically generates a credential that allows external devices to connect to the device. This credential is an access token. Only when the external debugging device transmits the access token and the vehicle-mounted device verifies the access token will it be allowed to connect and perform remote control. Each vehicle-mounted device generates an access token when maintenance and debugging is required. These access tokens need to be stored and filed on the cloud server. This allows the debugging end to find the corresponding access token and connect to the corresponding vehicle-mounted device for maintenance and debugging.

[0024] Specifically, step S100 includes: the vehicle device receives the debugging feedback instruction, obtains the identity information, current display time, preset timeout period, and IP address of the vehicle device, packages and generates an access token data packet, and transmits it to the cloud server. The cloud server stores and parses the access token data packet. After the parsing is completed, the identity information display signal is sent to the vehicle device.

[0025] When the owner of the vehicle is using the vehicle and finds that the vehicle computer system has a fault, he can make a one-click feedback through the warranty feedback function module in the vehicle computer system. After the vehicle computer device receives the debugging feedback instruction, it retrieves the VIN code of the vehicle computer device as the identity information of the vehicle computer device. The VIN code of the vehicle computer device is the unique identification code of the vehicle computer device, such as LDPXXXXXX001. It has been set in the vehicle computer system when the vehicle computer leaves the factory and can be obtained by directly retrieving it from the vehicle computer system. The vehicle computer system is the operating system of the vehicle computer device. The vehicle system can store multiple applications. The failure of the vehicle system is usually the problem of using the vehicle system application software and the control problem of the system itself. The vehicle-mounted device has a timer, and the current time can be displayed on the vehicle system, which can be directly obtained. The preset timeout duration data is preset by the manufacturer in the vehicle-mounted system, such as half an hour or an hour, and the vehicle-mounted system can directly retrieve it from the storage area. For IP address information, such as 192.168.xxx.xxx, each vehicle-mounted device has a network physical address. The external network connects to it through the IP address. It is set when the vehicle leaves the factory, and the vehicle-mounted system can directly obtain it from the internal system. After obtaining the vehicle's VIN code, current display time, set timeout duration and IP address, this data is bundled together and packaged in a data packet and transmitted to the vehicle network's backend cloud server via the wireless network. After receiving the access token data packet, the cloud server first stores it for record, then parses it, and places the parsed data in the same storage area as the access data packet. After completion, the cloud server sends a signal to inform the vehicle-mounted device to display the identity information in the access token - the VIN code of the vehicle-mounted device.

[0026] Step S200: The PC debugging terminal accesses the cloud server to obtain an access token for the vehicle device to be powered on and debugged.

[0027] The PC debugging end needs to remotely connect to the vehicle-mounted device to debug the corresponding vehicle-mounted device. To remotely connect to the vehicle-mounted device, it is necessary to know the IP address of the vehicle-mounted device and the vehicle-mounted device needs to verify the identity information of the vehicle-mounted device. At this time, the PC debugging end needs to have an access token, and the access token is stored in the cloud server. The PC debugging end needs to access the cloud server and obtain the corresponding access token from the cloud server.

[0028] Specifically, step S200 includes: after the vehicle-mounted device receives the identity information display signal, the identity information of the vehicle-mounted device is provided to the vehicle owner communication terminal in a visual display manner; the vehicle owner communication terminal transmits the identity information of the vehicle-mounted device to be debugged to the service communication terminal via base station transmission or Internet server transmission; the service communication terminal inputs the identity information of the vehicle-mounted device to be debugged into the PC debugging terminal; the PC debugging terminal accesses the cloud server by verifying the account password, and sends the identity information and query instructions to the cloud server; the cloud server queries and compares the identity information in the stored access token with the identity information transmitted by the PC debugging terminal to see whether they are consistent; if they are consistent, the IP address and identity information in the corresponding access token are transmitted to the PC debugging terminal.

[0029] After receiving the identity information display signal sent by the cloud server, the vehicle device retrieves the VIN code of the vehicle and displays it visually through the display screen of the vehicle system. The owner transmits it to the service communication terminal through the vehicle owner communication terminal. The vehicle owner communication terminal here refers to the communication media used by the vehicle owner, such as mobile phones, online instant messaging software, etc. The service communication terminal refers to the communication media used by the debugging service personnel, such as mobile phones, online instant messaging software, etc. The vehicle owner communication terminal informs the debugging service personnel by calling the base station or through the instant messaging software Internet server. After knowing the VIN code of the vehicle to be debugged, the debugging service personnel enters it into the PC debugging terminal to search for the access token corresponding to the vehicle VIN code. After receiving the VIN code of the vehicle computer, the PC debugging terminal requests access to the cloud server. After passing the account password verification, it establishes a data transmission connection with the cloud server. The PC debugging terminal transmits the vehicle computer's VIN to the cloud server and simultaneously issues a query command to the cloud server. The cloud server retrieves the access token in the storage area based on the command and compares the identity information in the access token with the vehicle computer device's VIN code transmitted by the PC debugging terminal. If they are consistent, the access token is the access token of the vehicle computer device currently powered on and waiting to be debugged. The cloud server extracts the IP address and identity information of the vehicle computer device from the access token and transmits them back to the PC debugging terminal. The account password of the PC debugging terminal is the personal account password of the debugging service personnel in the background.

[0030] Step S300: The PC debugging terminal connects to the vehicle device to be debugged based on the access token.

[0031] The PC debugging end is connected to the vehicle equipment to realize data interactive transmission, thereby providing the PC debugging end with various data for fault analysis, and also realizing remote control of the vehicle system to repair the fault.

[0032] Specifically, step S300 includes: the PC debugging end connects to the vehicle device end that is powered on and to be debugged according to the IP address in the access token, and transmits the identity information in the access token to the vehicle device end, and the vehicle device end determines whether the identity information of the access token is consistent with the identity information of the vehicle device obtained locally. If so, it further determines whether the connection time with the PC debugging end is greater than the preset timeout time. If not, the PC debugging end is authorized to initiate a data transmission request permission for authentication.

[0033] The PC debugging end uses network routing to find the vehicle device end with the IP address in the access token and establishes a connection with it. Furthermore, the PC debugging end transmits the identity information in the access token for its authorization and authentication to the vehicle device. After receiving the identity information in the access token, the vehicle device retrieves the stored VIN code of the vehicle device and compares them. If they match, it proves that the PC debugging end is connected to the vehicle device. To further accurately and securely perform docking and debugging, the PC debugging end needs to dock with the powered-on vehicle device to be debugged at a specified time. At this time, the vehicle device needs to determine whether the connection time of the PC debugging end with it exceeds a preset specified time. The vehicle device retrieves the current connection time and the generation time of the access token before, calculates the duration of the two times, and compares them with the preset timeout duration. If the duration is less than the timeout duration, the PC debugging end is considered accurate and secure. At this time, the vehicle device authorizes the PC debugging end to obtain data from the vehicle device, and the PC debugging end can initiate data capture from the vehicle device.

[0034] Step S400: The PC debugging terminal performs online debugging on the vehicle-mounted system of the vehicle equipment.

[0035] After the connection authorization is successful, the PC debugging end can debug and repair the vehicle equipment, thus realizing remote debugging.

[0036] Specifically, step S400 includes: the PC debugging end initiates a data capture request to the vehicle device end, the vehicle device end collects log data and file data, and packages and transmits them to the PC debugging end, and the PC debugging end uses the debugging method obtained by analyzing the collected data to perform online debugging on the vehicle system of the vehicle device end.

[0037] Before debugging a vehicle-mounted device, it's necessary to understand the cause of the fault and develop a debugging method. This requires targeted analysis of the device's log data and file data. Log data refers to the data that needs to be output in real time, with the vehicle-mounted device directly sending key text information to the PC debugging terminal. File data refers to Android logcat log files stored by the vehicle-mounted device and audio data files stored by voice applications. For example, after enabling debugging, a command can be sent to start saving audio to the vehicle-mounted device, which can then be sent to the PC debugging terminal for audio troubleshooting. After collecting data from the vehicle-mounted device, if the debugger is unable to resolve the fault independently, they can promptly report and forward the debug log. The debugging process and logs can be shared synchronously with multiple people, enhancing fault handling capabilities. After analyzing the cause of the fault and obtaining a debugging method, this method can be used to debug the vehicle system online.

[0038] Based on the above method, the present invention provides a remote debugging method for a vehicle-mounted system. When the car owner reports a fault, the vehicle-mounted device automatically generates an access token, which serves as a credential for the remote debugging end to connect to the vehicle-mounted device, thereby realizing remote connection to the vehicle-mounted device. After the connection, the log data and file data in the vehicle-mounted system can be obtained, and the log data, file data and debugging process can be shared synchronously with multiple people, thereby enhancing the processing capability and speed of vehicle-mounted system faults, greatly shortening the time from the occurrence of a fault to the start of fault troubleshooting, and eliminating the need for the vehicle to be returned to the factory, saving users a lot of time and greatly reducing the impact on users' travel.

[0039] Accordingly, the present invention also provides a remote debugging system for a vehicle-mounted system, referring to Figure 2 , Figure 2 The figure shows a schematic diagram of the system module structure of a remote debugging system for a vehicle-mounted system provided by an embodiment of the present invention. The system remotely debugs the vehicle-mounted system through the remote debugging method described above, and includes: a generation module for generating an access token; a transmission module for transmitting the access token to the voice provider end, for outputting application instruction information to the smart device; an access module for accessing the cloud server; an acquisition module for acquiring the access token of the vehicle-mounted device that is powered on and waiting for debugging; a connection module for connecting with the vehicle-mounted device that is powered on and waiting for debugging according to the access token; a debugging module for online debugging of the vehicle-mounted system of the vehicle-mounted device; the generation module and the transmission module are located in the vehicle-mounted device end, the access module, the acquisition module, and the debugging module are located in the PC debugging end, and the connection module is located between the vehicle-mounted device end and the PC debugging end.

[0040] Preferably, the remote debugging system also includes a receiving module, a storage module, and a parsing module. The receiving module is located in the vehicle device end, the storage module and the parsing module are located in the cloud server, the acquisition module is also located in the PC debugging end, and the transmission module is also located in the cloud server; the acquisition module is also used to obtain the identity information, current display time, preset timeout period, and IP address of the vehicle device; the receiving module is used to receive debugging feedback instructions; the storage module is used to store access token data packets; the parsing module is used to parse access token data packets; the transmission module is also used to send identity information display signals to the vehicle device end.

[0041] Preferably, the remote debugging system also includes a display module and a query and comparison module. The display module is located in the vehicle device end, and the query and comparison module is located in the cloud server; the display module is used to visually display the identity information of the vehicle device; the query and comparison module is used to query and compare whether the identity information in the stored access token is consistent with the identity information transmitted by the PC debugging end; the receiving module is also used to receive the identity information display signal; the transmission module is also located in the vehicle owner communication end, and the transmission module is also used to transmit the identity information of the vehicle device to be debugged to the service communication end through base station transmission or Internet server transmission, and transmit the IP address and identity information in the corresponding access token to the PC debugging end.

[0042] Preferably, the remote debugging system also includes a judgment module and an authorization authentication module, and the judgment module and the authorization authentication module are located in the vehicle device end; the judgment module is used to judge whether the identity information of the access token is consistent with the identity information of the vehicle device obtained locally, and to judge whether the connection time with the PC debugging end is greater than the preset timeout time; the authorization authentication module is used to authorize and authenticate the data transmission request permission initiated by the PC debugging end; the transmission module is also located in the PC debugging end, and the transmission module is also used to transmit the identity information in the access token to the vehicle device end.

[0043] Preferably, the remote debugging system also includes a collection module, which is located in the vehicle-mounted device end, and the collection module is used to collect log data and file data; the transmission module is also used to initiate a data capture request to the vehicle-mounted device end, and transmit the log data and file data to the PC debugging end, and the debugging module is also used to use the debugging method obtained by analyzing the collected data to perform online debugging on the vehicle-mounted system of the vehicle-mounted device end.

[0044] In the description provided herein, numerous specific details are described. However, it is understood that embodiments of the present invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.

[0045] Similarly, it should be understood that in order to streamline the present disclosure and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as reflected in the claims below, inventive aspects lie in less than all the features of the individual embodiments disclosed above. Accordingly, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of the invention.

[0046] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition may be divided into multiple submodules or subunits or subcomponents. All features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed herein may be combined in any combination, except that at least some of such features and / or processes or units are mutually exclusive. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0047] Furthermore, those skilled in the art will appreciate that although some embodiments herein include certain features included in other embodiments but not other features, combinations of features from different embodiments are intended to be within the scope of the present invention and to form different embodiments. For example, in the claims below, any of the claimed embodiments may be used in any combination.

[0048] The various component embodiments of the present invention can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all of the functions of some or all of the components in accordance with the embodiments of the present invention. The present invention can also be implemented as a device or apparatus program (e.g., a computer program and a computer program product) for executing a portion or all of the methods described herein. Such a program implementing the present invention can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0049] It should be noted that the above embodiments illustrate rather than limit the invention, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between brackets should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising several different elements and by means of appropriately programmed computers. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.

Claims

1. A remote debugging method for an in-vehicle system, characterized in that: The following steps are involved: Step S100: The vehicle device generates an access token and transmits it to the cloud server; Step S200: The PC debugging terminal accesses the cloud server to obtain an access token for the vehicle device to be debugged; Step S300: The PC debugging terminal connects to the vehicle device to be debugged based on the access token; Step S400: The PC debugging terminal performs online debugging on the vehicle-mounted system of the vehicle equipment.

2. The remote debugging method of the vehicle-mounted system as claimed in claim 1, characterized in that: The step S100 includes: The vehicle device receives the debugging feedback instruction, obtains the identity information of the vehicle device, the current display time, the preset timeout period, and the IP address, packages it to generate an access token data packet, and transmits it to the cloud server. The cloud server stores and parses the access token data packet. After the parsing is completed, it sends an identity information display signal to the vehicle device.

3. The remote debugging method of the vehicle-mounted system as claimed in claim 2, characterized in that: The step S200 includes: After the vehicle device receives the identity information display signal, it provides the identity information of the vehicle device to the vehicle owner communication terminal in a visual display manner. The vehicle owner communication terminal transmits the identity information of the vehicle device that is powered on and waiting for debugging to the service communication terminal through base station transmission or Internet server transmission. The service communication terminal inputs the identity information of the vehicle device that is powered on and waiting for debugging into the PC debugging terminal. The PC debugging terminal accesses the cloud server by verifying the account password, and sends the identity information and query instructions to the cloud server. The cloud server queries and compares the identity information in the stored access token with the identity information transmitted by the PC debugging terminal to see if they are consistent. If they are consistent, the IP address and identity information in the corresponding access token are transmitted to the PC debugging terminal.

4. The remote debugging method of the vehicle-mounted system as claimed in claim 1, characterized in that: The step S300 includes: The PC debugging end connects to the vehicle device that is powered on and waiting for debugging based on the IP address in the access token, and transmits the identity information in the access token to the vehicle device. The vehicle device determines whether the identity information of the access token is consistent with the identity information of the vehicle device obtained locally. If so, it further determines whether the connection time with the PC debugging end is greater than the preset timeout period. If not, the PC debugging end is authorized to initiate a data transmission request.

5. The remote debugging method of the vehicle-mounted system as claimed in claim 4, characterized in that: The step S400 includes: The PC debugging end initiates a data capture request to the vehicle device end. The vehicle device end collects log data and file data, packages and transmits them to the PC debugging end. The PC debugging end uses the debugging method obtained by analyzing the collected data to perform online debugging on the vehicle system of the vehicle device end.

6. A remote debugging system for an in-vehicle system, characterized in that: include: Generate module, used to generate access token; A transmission module, configured to transmit the access token to the voice provider, and output the application instruction information to the smart device; Access module, used to access the cloud server; The acquisition module is used to obtain the access token of the vehicle device to be powered on and debugged; A connection module is used to connect to the vehicle equipment to be debugged based on the access token; Debugging module, used for online debugging of the vehicle-mounted system of the vehicle equipment; The generation module and the transmission module are located in the vehicle device end, the access module, the acquisition module and the debugging module are located in the PC debugging end, and the connection module is located in the vehicle device end and the PC debugging end.

7. The remote debugging system of the vehicle-mounted system as claimed in claim 6, characterized in that: The remote debugging system also includes a receiving module, a storage module, and a parsing module. The receiving module is located in the vehicle device end, the storage module and the parsing module are located in the cloud server, the acquisition module is also located in the PC debugging end, and the transmission module is also located in the cloud server; the acquisition module is also used to obtain the identity information, current display time, preset timeout period, and IP address of the vehicle device; the receiving module is used to receive debugging feedback instructions; the storage module is used to store access token data packets; the parsing module is used to parse access token data packets; the transmission module is also used to send identity information display signals to the vehicle device end.

8. The remote debugging system for an in-vehicle system as claimed in claim 7, characterized in that: The remote debugging system further includes a display module and a query comparison module. The display module is located in the vehicle device and the query comparison module is located in the cloud server. The display module is used to visually display the identity information of the vehicle device. The query and comparison module is used to query and compare whether the identity information in the stored access token is consistent with the identity information transmitted by the PC debugging end; the receiving module is also used to receive the identity information display signal; the transmission module is also located in the vehicle owner's communication end, and the transmission module is also used to transmit the identity information of the vehicle device to be debugged to the service communication end through base station transmission or Internet server transmission, and transmit the IP address and identity information in the corresponding access token to the PC debugging end.

9. The remote debugging system for an in-vehicle system as claimed in claim 8, characterized in that: The remote debugging system further includes a judgment module and an authorization authentication module, wherein the judgment module and the authorization authentication module are located in the vehicle-mounted device. The judgment module is used to judge whether the identity information of the access token is consistent with the identity information of the vehicle-mounted device obtained locally, and to judge whether the connection duration with the PC debugging terminal is greater than a preset timeout duration. The authorization and authentication module is used to authorize and authenticate the data transmission request permission initiated by the PC debugging terminal; The transmission module is also located in the PC debugging end, and the transmission module is also used to transmit the identity information in the access token to the vehicle device end.

10. The remote debugging system of the vehicle-mounted system as claimed in claim 9, characterized in that: The remote debugging system also includes a collection module, which is located in the vehicle-mounted device end and is used to collect log data and file data; the transmission module is also used to initiate a data capture request to the vehicle-mounted device end, and transmit the log data and file data to the PC debugging end. The debugging module is also used to use the debugging method obtained by analyzing the collected data to perform online debugging on the vehicle-mounted system of the vehicle-mounted device end.

Images