Automobile ECU remote debugging method and system

Abstract

The embodiment of the present invention provides a method and system for remote debugging of an automobile ECU, and relates to the field of automobile technology. The method comprises: upon receiving a successful login instruction sent by a local server, obtaining information of a vehicle to be debugged according to the current state of the vehicle to be debugged, judging whether the information of the vehicle to be debugged matches the vehicle information pre-stored in the local server, and if so, obtaining port information sent by the cloud server based on a debugging instruction containing the information of the vehicle to be debugged sent by the local server to a cloud server, sending a login instruction containing the port information to the T-BOX of the vehicle to be debugged through the cloud server, and upon receiving a successful login instruction sent by the T-BOX of the vehicle to be debugged, sending a login instruction to the ECU to be debugged, and upon receiving a successful login instruction sent by the ECU to be debugged, performing remote debugging on the ECU to be debugged. The embodiment of the present invention realizes rapid maintenance and debugging of software defects of automobile ECUs.

Description

Technical Field

[0001] The present invention relates to the field of automobile technology, and in particular to a method and system for remote debugging of an automobile ECU. Background Art

[0002] After a car is launched on the market, if a certain electronic component of the car, such as the car's ECU (Electronic Control Unit), is found to have a software defect, it will lead to major functional safety issues, so batch maintenance will be required, or even batch recalls will occur. In addition, if a vehicle fails during driving or a traffic accident occurs, professionals are required to respond quickly and make a detailed analysis. If the analysis involves a software defect in the car's ECU, professionals are also required to follow up at a designated location and perform debugging and maintenance.

[0003] The above-mentioned debugging and maintenance process for software defects in automobile ECUs requires high maintenance costs such as time, location, and manpower. There are also problems such as long maintenance cycles, long distances between vehicles and maintenance points, and difficulty in debugging and maintenance due to the absence of professionals on site. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide a remote debugging method and system for an automobile ECU, so as to solve the problem that the automobile ECU needs rapid maintenance and debugging when software defects occur after mass production.

[0005] In order to achieve the above purpose, the technical solution adopted by the embodiment of the present invention is as follows:

[0006] In a first aspect, an embodiment of the present invention provides an automobile ECU remote debugging method, which is applied to a local client of an ECU remote debugging system, wherein the ECU remote debugging system further includes a local server and a cloud server, wherein the local client is communicatively connected to the local server and the cloud server, wherein the cloud server is communicatively connected to a T-BOX of a vehicle to be debugged, wherein the vehicle to be debugged is further provided with a plurality of ECUs, and each of the ECUs is communicatively connected to the T-BOX of the vehicle to be debugged;

[0007] The method comprises:

[0008] Upon receiving a successful login instruction sent by the local server, obtaining information of the vehicle to be debugged according to the current state of the vehicle to be debugged;

[0009] Determining whether the information of the vehicle to be debugged matches the information of the vehicle pre-stored in the local server;

[0010] If yes, based on the debugging instruction including the information of the vehicle to be debugged sent by the local server to the cloud server, obtaining the port information sent by the cloud server; wherein the port information represents the configuration port in the cloud server bound to the T-BOX of the vehicle to be debugged;

[0011] Sending a login instruction including the port information to the T-BOX of the vehicle to be debugged through the cloud server;

[0012] Upon receiving a successful login instruction sent by the T-BOX of the vehicle to be debugged, sending a login instruction to the ECU to be debugged;

[0013] When a successful login instruction is received from the ECU to be debugged, a remote debugging action is performed on the ECU to be debugged.

[0014] In an optional implementation, before the step of obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged upon receiving the successful login sent by the local server, the method further includes:

[0015] Determine whether the account and password required to log in to the local server are obtained;

[0016] If so, send a login instruction to the local server based on the account and password.

[0017] In an optional implementation manner, the step of acquiring information of the vehicle to be debugged according to the current state of the vehicle to be debugged includes:

[0018] Determining whether the current state of the vehicle to be debugged is an after-sales state;

[0019] If not, obtain the VIN code and ICCID code of the vehicle to be debugged as the vehicle information to be debugged;

[0020] If so, obtain the VIN code and ICCID code of the vehicle to be debugged, and the user information corresponding to the vehicle to be debugged as the vehicle information to be debugged.

[0021] In an optional implementation, the step of sending, through the cloud server, a login instruction including the port information to the T-BOX of the vehicle to be debugged includes:

[0022] Determine whether the T-BOX login password required to log in to the T-BOX of the vehicle to be debugged is obtained;

[0023] If so, a login instruction is sent to the T-BOX of the vehicle to be debugged based on the port information, the T-BOX login password, and the IP address of the cloud server.

[0024] In an optional implementation, the step of sending a login instruction to the ECU to be debugged includes:

[0025] Determine whether the ECU login password required to log in to the ECU to be debugged is obtained;

[0026] If so, a login instruction is sent to the ECU to be debugged based on the ECU login password and the IP address of the ECU to be debugged.

[0027] In an optional implementation, after the step of performing remote debugging on the ECU to be debugged upon receiving a successful login instruction sent by the ECU to be debugged, the method further includes:

[0028] Send a debugging end instruction to the local server, so that the local server sends an unbinding instruction to the cloud server based on the debugging end instruction, so that the configuration port of the cloud server is unbound from the T-BOX of the vehicle to be debugged.

[0029] In a second aspect, an embodiment of the present invention provides an automobile ECU remote debugging method, which is applied to a cloud server of an ECU remote debugging system, wherein the ECU remote debugging system further includes a local client and a local server, wherein the local client is communicatively connected to the local server and the cloud server, and the cloud server is communicatively connected to a T-BOX of a vehicle to be debugged, wherein the vehicle to be debugged is further provided with a plurality of ECUs, and each of the ECUs is communicatively connected to the T-BOX of the vehicle to be debugged;

[0030] The method comprises:

[0031] In response to a debugging instruction including information of a vehicle to be debugged sent by the local server, searching for a T-BOX of the vehicle to be debugged according to the information of the vehicle to be debugged;

[0032] Bind the found T-BOX of the vehicle to be debugged to the configuration port and generate port information;

[0033] The port information is sent to the local client, so that the local client logs in to the T-BOX of the vehicle to be debugged based on the port information, and logs in to the ECU to be debugged to perform remote debugging.

[0034] In an optional implementation manner, the information of the vehicle to be debugged includes the ICCID code of the vehicle to be debugged, and the step of searching the T-BOX of the vehicle to be debugged according to the information of the vehicle to be debugged includes:

[0035] The T-BOX corresponding to the vehicle to be debugged is searched according to the ICCID code of the vehicle to be debugged.

[0036] In an optional embodiment, the method further comprises:

[0037] In response to the unbinding instruction sent by the local server, the configuration port is unbound from the T-BOX of the vehicle to be debugged.

[0038] In a third aspect, an embodiment of the present invention provides an automobile ECU remote debugging system, comprising a local client, a local server and a cloud server, wherein the local client is communicatively connected to the local server and the cloud server, and the cloud server is communicatively connected to a T-BOX of a vehicle to be debugged, wherein the vehicle to be debugged is further provided with a plurality of ECUs, and each of the ECUs is communicatively connected to the T-BOX of the vehicle to be debugged;

[0039] The local client is used to implement the automobile ECU remote debugging method provided in the above-mentioned first aspect embodiment and / or in combination with the above-mentioned first aspect embodiment possible implementation method, so as to log in to the ECU to be debugged and perform the remote debugging action;

[0040] The local server pre-stores vehicle information, and the local server is used to send a debugging instruction containing the vehicle information to be debugged to the cloud server, so that the local client obtains the port information of the vehicle to be debugged sent by the cloud server; wherein the port information represents the configuration port in the cloud server bound to the T-BOX of the vehicle to be debugged;

[0041] The cloud server is used to implement the automobile ECU remote debugging method provided in the above-mentioned second aspect embodiment and / or a possible implementation method in combination with the above-mentioned second aspect embodiment, so that the local client logs in to the T-BOX of the vehicle to be debugged based on the port information sent by it, and logs in to the ECU to be debugged to perform remote debugging actions.

[0042] The beneficial effects of the embodiments of the present invention include, for example:

[0043] An embodiment of the present invention provides an automobile ECU remote debugging method and system, which obtains vehicle information to be debugged through the current state of the vehicle to be debugged, and when the vehicle information to be debugged matches the vehicle information pre-stored in the local server, based on the debugging instruction containing the vehicle information to be debugged sent by the local server to the cloud server, obtains the port information sent by the cloud server, and sends the login instruction containing the port information to the T-BOX of the vehicle to be debugged through the cloud server, so that the local client can log in to the T-BOX of the vehicle to be debugged, and log in to the ECU to be debugged to perform remote debugging.

[0044] The above solution solves the problem of rapid maintenance and debugging of automotive ECUs when software defects occur after mass production. This solution is not restricted by time and space. No matter where the car is, this method and the corresponding debugging system can respond in time to achieve remote debugging. It can not only solve the problem of remote debugging, but also solve the problems of ECU system upgrades, log extraction and big data upload based on this link.

[0045] At the same time, during the entire process of remote debugging of the ECU, it is necessary to obtain the vehicle information to be debugged when a successful login instruction is received from the local server, and only when a successful login instruction is sent from the T-BOX of the vehicle to be debugged and when a successful login instruction is received from the ECU to be debugged, can the ECU to be debugged be logged in and further remotely debugged. The whole process ensures the information security of the corresponding server and the car.

[0046] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0048] Figure 1a An exemplary structural block diagram of an automobile ECU remote debugging system provided by an embodiment of the present invention is shown;

[0049] Figure 1b The second exemplary structural block diagram of an automobile ECU remote debugging system provided by an embodiment of the present invention is shown;

[0050] Figure 2 An exemplary structural block diagram of a local client in an automobile ECU remote debugging system provided by an embodiment of the present invention is shown;

[0051] Figure 3 A schematic diagram of a flow chart of a remote debugging method for an automobile ECU provided by an embodiment of the present invention is shown;

[0052] Figure 4 The second flowchart of a remote debugging method for an automobile ECU provided by an embodiment of the present invention is shown;

[0053] Figure 5The third flowchart of a remote debugging method for an automobile ECU provided by an embodiment of the present invention is shown;

[0054] Figure 6 A fourth flow chart of a method for remote debugging of an automobile ECU provided by an embodiment of the present invention is shown;

[0055] Figure 7 A fifth flow chart of a method for remote debugging of an automobile ECU provided by an embodiment of the present invention is shown;

[0056] Figure 8 The schematic diagram shows a process of a remote debugging method for an automobile ECU provided by an embodiment of the present invention. Figure 6 ;

[0057] Fig. 9 A schematic diagram showing a flow chart of another automobile ECU remote debugging method provided by an embodiment of the present invention;

[0058] Fig.10 A second flow chart of another automobile ECU remote debugging method provided by an embodiment of the present invention is shown;

[0059] Fig.11 A third flow chart of another automobile ECU remote debugging method provided by an embodiment of the present invention is shown.

[0060] Icon: 100 - Automobile ECU remote debugging system; 110 - Local client; 1101 - Memory; 1102 - Processor; 1103 - Communication interface; 111 - PC; 112 - Mobile phone; 120 - Local server; 130 - Cloud server. DETAILED DESCRIPTION

[0061] The following will be combined with the accompanying drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0062] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present invention.

[0063] It should be noted that relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0064] It should be noted that, in the absence of conflict, the features in the embodiments of the present invention may be combined with each other.

[0065] After a car is launched on the market, if a certain electronic component of the car, such as the car's ECU (Electronic Control Unit), is found to have a software defect, it will lead to major functional safety issues, so batch maintenance will be required, or even batch recalls will occur. In addition, if a vehicle fails during driving or a traffic accident occurs, professionals are required to respond quickly and make a detailed analysis. If the analysis involves a software defect in the car's ECU, professionals are also required to follow up at a designated location and perform debugging and maintenance.

[0066] There are two traditional solutions for maintaining software defects in automobile ECUs: Solution 1: Establish a connection between the server and T-BOX, and forward the corresponding debugging instructions from the server to the specified ECU through T-BOX. After receiving the instructions, the ECU will feedback the "seed" information to the server via T-BOX. The server uses this "seed" to solve the key and send it to the ECU. After matching the key calculated by the ECU, the debugging function is enabled; Solution 2: After the remote debugging is triggered locally, the vehicle-mounted device will establish a first remote connection with the remote debugging server. Based on this connection, the local device can receive information from the vehicle-mounted device, and the local debugger can establish a second remote connection with the remote debugger based on this information. The first remote connection and the second remote connection are interoperable, so as to achieve the purpose of establishing a debugging connection between the local debugger and the remote automobile ECU.

[0067] The above two solutions have the following defects: For Solution 1, the method of using "seed" to calculate the key uses the same algorithm on the ECU and the server. Since the algorithm itself is fixed, once the algorithm is leaked, the coerced car ECU is likely to be logged in, resulting in security risks such as data leakage or system modification.

[0068] For solution 2, the car ECU and the remote server are used as the first connection, and the remote server and the local debugger are used as the second connection. The debugging connection between the local and remote car ECUs is established based on the device identification and device connection confirmation information. This disassembled connection method cannot actually be supported on high concurrency, that is, when there are a large number of debugging connection requests in the background, this connection method may cause connection confusion or failure. At the same time, the above solution has almost no consideration and implementation of corresponding measures in terms of security. As long as there is a trigger request, ECU information can be fed back and a remote debugging connection can be established.

[0069] Based on this, an embodiment of the present invention provides a remote debugging method for an automobile ECU to solve the above problems.

[0070] Please refer to Figure 1a and Figure 1b , Figure 1a FIG. 1 shows an exemplary structural block diagram of an automobile ECU remote debugging system 100 provided by an embodiment of the present invention. Figure 1b FIG. 2 shows a second exemplary structural block diagram of an automotive ECU remote debugging system 100 provided by an embodiment of the present invention. Figure 1a and Figure 1b As shown, the system includes a local client 110, a local server 120 and a cloud server 130. The local client 110 is connected to the local server 120 and the cloud server 130 in communication. The cloud server 130 is connected to the T-BOX 140 of the vehicle to be debugged. The vehicle to be debugged is also provided with a plurality of ECUs (for example, Figure 1a and Figure 1b ECU1, ECU2 and ECU3 in the system), each ECU is communicatively connected with the T-BOX 140 of the vehicle to be debugged.

[0071] Among them, the local client 110 can obtain the vehicle information to be debugged according to the current status of the vehicle to be debugged when successfully logging into the local server 120. For example, if the vehicle to be debugged is in an after-sales status, the VIN code and ICCID code of the vehicle to be debugged and the corresponding user information can be obtained.

[0072] Furthermore, after obtaining the information of the vehicle to be debugged, the local client 110 can match it with the vehicle information pre-stored in the local server 120. If the match is successful, the local server 120 will send a debugging instruction containing the information of the vehicle to be debugged to the cloud server 130.

[0073] In an embodiment of the present invention, after receiving the above debugging instruction, the cloud server 130 will search for the T-BOX 140 of the vehicle to be debugged, bind the found T-BOX 140 of the vehicle to be debugged to its configured port, and return the T-BOX of the vehicle to be debugged and the bound port information to the local client 110.

[0074] Based on this, the local client 110 can log in to the T-BOX 140 of the vehicle to be debugged through the cloud server 130 based on the acquired T-BOX 140 of the vehicle to be debugged and the bound port information, and further log in to the ECU to be debugged of the vehicle to be debugged for remote debugging and maintenance.

[0075] After debugging is completed, the local client 110 will also send a debugging end instruction to the local server 120, so that the local server 120 will send an unbinding instruction to the cloud server 130 based on the debugging end instruction. Finally, the configuration port of the cloud server 130 will be unbound from the T-BOX 140 of the vehicle to be debugged, thus completing the entire remote debugging of the ECU software defect.

[0076] Based on the above-mentioned automobile ECU remote debugging system 100, the embodiment of the present invention further provides a local client 110, please refer to Figure 2 , Figure 2 FIG. 1 shows an exemplary structural block diagram of a local client 110 in an automobile ECU remote debugging system 100 provided by an embodiment of the present invention, such as Figure 2 As shown, the local client 110 includes: a memory 1101, a processor 1102 and a communication interface 1103. The memory 1101, the processor 1102 and the communication interface 1103 are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines.

[0077] The memory 1101 may be used to store software programs and modules, and the processor 1102 executes various functional applications and data processing by executing the software programs and modules stored in the memory 1101. The communication interface 1103 may be used to communicate signaling or data with other node devices.

[0078] Among them, the memory 1101 can be but is not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-only memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.

[0079] The processor 1102 may be an integrated circuit chip with signal processing capability. The processor 1102 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0080] It should be noted that the local client 110 may be a tablet computer, a PC (for example, Figure 1a and Figure 1b The local client 110 shown in FIG. 1 includes a PC 111 ), a mobile device (e.g., Figure 1a The local client 110 shown in the figure may include a mobile phone 112 or other smart terminal. The local client 110 may interact with the local server 120 and the cloud server 130 of the automotive ECU remote debugging system 100 in an embodiment of the present invention through wireless communication (for example, using communication protocols such as HTTP, HTPS, and MQTT).

[0081] Based on the above-mentioned automobile ECU remote debugging system 100, the following takes the local client 110 of the automobile ECU remote debugging system 100 as the execution subject to exemplarily illustrate an automobile ECU remote debugging method provided by an embodiment of the present invention. Figure 3 , Figure 3 A schematic flow chart of a remote debugging method for an automobile ECU provided by an embodiment of the present invention is shown.

[0082] like Figure 3 As shown, the above-mentioned automobile ECU remote debugging method is applied to the local client 110 of the automobile ECU remote debugging system 100. The ECU remote debugging system also includes a local server 120 and a cloud server 130. The local client 110 is communicatively connected with the local server 120 and the cloud server 130. The cloud server 130 is communicatively connected with the T-BOX 140 of the vehicle to be debugged. The vehicle to be debugged is also provided with multiple ECUs, and each ECU is communicatively connected with the T-BOX 140 of the vehicle to be debugged.

[0083] The above-mentioned automobile ECU remote debugging method may include the following steps:

[0084] S210, when a successful login instruction sent by the local server is received, information of the vehicle to be debugged is obtained according to the current state of the vehicle to be debugged.

[0085] S220, determining whether the information of the vehicle to be debugged matches the information of the vehicle pre-stored in the local server.

[0086] S230: If yes, based on the debugging instruction including the vehicle information to be debugged sent by the local server to the cloud server, obtain the port information sent by the cloud server.

[0087] If not, it will show no permission.

[0088] The port information represents the configuration port in the cloud server that is bound to the T-BOX of the vehicle to be debugged.

[0089] S240, sending a login instruction including port information to the T-BOX of the vehicle to be debugged through the cloud server;

[0090] S250, when receiving a successful login instruction sent by the T-BOX of the vehicle to be debugged, sending a login instruction to the ECU to be debugged;

[0091] S260, when receiving a successful login instruction sent by the ECU to be debugged, executing a remote debugging action on the ECU to be debugged.

[0092] The above steps implement the process in which the local client logs in to the T-BOX of the vehicle to be debugged through the cloud server based on the vehicle information to be debugged and the port information obtained from the cloud server, and further logs in to the ECU to be debugged for remote debugging.

[0093] Specifically, step S210 is a process of obtaining information of the vehicle to be debugged after the local client successfully logs in to the local server. The local client will access the local server through HTTPS (Hypertext Transfer Protocol Secure) to perform a series of configurations before remote connection.

[0094] It should be noted that whether the local client successfully logs in to the local server can be realized based on the administrator account and password provided by the user, that is, the administrator account and password obtained by the local client, and whether the administrator account and password successfully log in to the local server. If the local server is successfully logged in based on the above administrator account and password, the local client will receive a successful login instruction sent by the local server, and at this time, the vehicle information to be debugged can be obtained according to the current status of the vehicle to be debugged.

[0095] Furthermore, the specific process of obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged is to determine whether the vehicle to be debugged is in the production, testing, pre-sale or after-sale state. If the state of the vehicle to be debugged is in the production, testing or pre-sale state, only the VIN code of the vehicle to be debugged and the unique identification code ICCID code (Integrate circuit card identity) of the SIM card (Subscriber Identity Module) can be obtained as the information of the vehicle to be debugged. If the state of the vehicle to be debugged is in the after-sale state, the VIN code and ICCID code of the vehicle to be debugged and the corresponding user information can be obtained as the information of the vehicle to be debugged.

[0096] In the embodiment of the present invention, after the vehicle information to be debugged is obtained according to the current state of the vehicle to be debugged, step S220 is continued to be executed to determine whether the vehicle information to be debugged matches the vehicle information pre-stored in the local server.

[0097] Specifically, in step S220, the database of the local server pre-stores vehicle information, which may include user information, basic vehicle information VIN code and ICCID code. Therefore, after the information of the vehicle to be debugged is obtained in step S210, it can be matched with the above vehicle information pre-stored in the local server. If the match is successful, the local server configuration can be implemented, and a remote connection with the T-BOX of the vehicle to be debugged can be established subsequently. This process can prevent the local client from directly connecting to the T-BOX of the car using the valid VIN code and ICCID code.

[0098] After the vehicle information to be debugged successfully matches the vehicle information pre-stored in the local server, step S230 is continued to be executed, and the port information sent by the cloud server is obtained based on the debugging instruction containing the vehicle information to be debugged sent by the local server to the cloud server.

[0099] Specifically, in step S230, after the local server sends a debugging instruction including the information of the vehicle to be debugged to the cloud server, the cloud server will search for the T-BOX corresponding to the vehicle to be debugged based on the information of the vehicle to be debugged. For example, the information of the vehicle to be debugged may include the ICCID code of the vehicle to be debugged. Since the cloud server is connected to the T-BOX of all vehicles, the cloud server can search for the T-BOX corresponding to the vehicle to be debugged based on the ICCID code of the vehicle to be debugged.

[0100] Furthermore, after the cloud server finds the T-BOX corresponding to the vehicle to be debugged, it binds the T-BOX of the vehicle to be debugged to its configured port and returns the bound port information to the local client. Since the local client and the cloud server can be connected via Ethernet TCP / IP, at this time, the local client will obtain the port information sent by the cloud server.

[0101] After obtaining the port information sent by the cloud server, continue to execute steps S240 to S260, and send a login instruction containing the port information to the T-BOX of the vehicle to be debugged through the cloud server. After successfully logging into the T-BOX of the vehicle to be debugged and subsequently successfully logging into the ECU to be debugged, remote debugging is performed on the ECU to be debugged.

[0102] Specifically, in step S240, the local client logs in to the T-BOX of the vehicle to be debugged, which is achieved through the cloud server. Since the T-BOX of all vehicles contains a Sim card, the T-BOX of all vehicles can be connected to Ethernet through the 4G / 5G network of the network operator, that is, a communication connection is established with the cloud server, and the local client and the cloud server can be connected through Ethernet TCP / IP. Based on this, the local client can log in to the T-BOX of the vehicle to be debugged through SSH (Secure Shell, Secure Shell Protocol) carrying the IP of the cloud server and the port information obtained in step S230, and then log in to the ECU to be debugged in the vehicle to be debugged through SSH again, which requires remote debugging, and finally realizes remote rapid maintenance and debugging of ECU software defects.

[0103] An embodiment of the present invention provides an automobile ECU remote debugging method, which obtains vehicle information to be debugged through the current state of the vehicle to be debugged, and when the vehicle information to be debugged matches the vehicle information pre-stored in a local server, based on a debugging instruction containing the vehicle information to be debugged sent by the local server to a cloud server, obtains port information sent by the cloud server, and sends a login instruction containing the port information to the T-BOX of the vehicle to be debugged through the cloud server, so that a local client can log in to the T-BOX of the vehicle to be debugged, and log in to the ECU to be debugged to perform remote debugging.

[0104] The above solution solves the problem of rapid maintenance and debugging of automotive ECUs when software defects occur after mass production. This solution is not restricted by time and space. No matter where the car is, this method and the corresponding debugging system can respond in time to achieve remote debugging. It can not only solve the problem of remote debugging, but also solve the problems of ECU system upgrades, log extraction and big data upload based on this link.

[0105] At the same time, during the entire process of remote debugging of the ECU, it is necessary to obtain the vehicle information to be debugged when a successful login instruction is received from the local server, and only when a successful login instruction is sent from the T-BOX of the vehicle to be debugged and when a successful login instruction is received from the ECU to be debugged, can the ECU to be debugged be logged in and further remotely debugged. The whole process ensures the information security of the corresponding server and the car.

[0106] Optionally, before obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged in step S210, it is also necessary to determine whether the account and password required to log in to the local server are obtained, and log in to the server based on the account and password. The above specific process can be implemented by the following steps:

[0107] exist Figure 3 Based on Figure 4 , Figure 4 The second flow chart of the automobile ECU remote debugging method provided by an embodiment of the present invention is shown. In step S210, before the step of obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged, upon receiving a successful login sent by the local server, the automobile ECU remote debugging method further includes:

[0108] S200, determining whether the account and password required to log in to the local server are obtained.

[0109] S201, if yes, send a login instruction to the local server based on the account and password.

[0110] If not, it will show no permission.

[0111] The above steps implement the process of sending a login instruction to the local server when the account and password required to log in to the local server are obtained.

[0112] In an embodiment of the present invention, the account and password required for logging into the local server can be implemented based on input. If the user enters the account and password required for logging into the local server, the local client obtains the account and password. If the account and password are not obtained, the subsequent operation of logging into the local server cannot be performed. This process makes access to the local server safer.

[0113] Furthermore, when a local client logs in to a local server, it is also necessary to ensure that the local client is in a local area network, that is, external network access to the local server is prohibited, and the local server can also set a firewall to filter improper operations or unsafe services to further reduce risks.

[0114] Optionally, the specific process of obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged in step S210 can be implemented by the following steps:

[0115] exist Figure 3 Based on Figure 5 , Figure 5 The third flow chart of a method for remote debugging of an automobile ECU provided by an embodiment of the present invention is shown. The step of obtaining information of the vehicle to be debugged according to the current state of the vehicle to be debugged in step S210 includes:

[0116] S211, determining whether the current state of the vehicle to be debugged is an after-sales state.

[0117] S212: If not, obtain the VIN code and ICCID code of the vehicle to be debugged as the vehicle information to be debugged.

[0118] S213: If yes, obtain the VIN code and ICCID code of the vehicle to be debugged, and the user information corresponding to the vehicle to be debugged as the vehicle information to be debugged.

[0119] The above steps implement a process of obtaining corresponding information of the vehicle to be debugged based on different states of the vehicle to be debugged.

[0120] Optionally, the specific process of sending the login instruction containing the port information to the T-BOX of the vehicle to be debugged through the cloud server in step S240 can be implemented by the following steps:

[0121] exist Figure 3 Based on Figure 6 , Figure 6The fourth flow chart of the automobile ECU remote debugging method provided by an embodiment of the present invention is shown. The step of sending a login instruction including port information to the T-BOX of the vehicle to be debugged through the cloud server in step S240 includes:

[0122] S241, determining whether a T-BOX login password required for logging into the T-BOX of the vehicle to be debugged is obtained.

[0123] S242: If yes, send a login instruction to the T-BOX of the vehicle to be debugged based on the port information, the T-BOX login password, and the IP address of the cloud server.

[0124] If not, it will show no permission.

[0125] The above steps implement the process of sending a login instruction to the T-BOX of the vehicle to be debugged when the T-BOX login password required for logging into the T-BOX of the vehicle to be debugged is obtained.

[0126] It should be noted that the process of the above-mentioned local client logging in to the T-BOX of the remote vehicle to be debugged through the cloud server can be specifically achieved through SSH (Secure Shell) carrying the IP address of the cloud server and the corresponding port during configuration. Since the T-BOX login password is required before logging in, the information security of each server and the vehicle to be debugged is guaranteed.

[0127] Optionally, the specific process of sending the login instruction to the ECU to be debugged in step S250 can be implemented by the following steps:

[0128] exist Figure 3 Based on Figure 7 , Figure 7 The fifth flow chart of the automobile ECU remote debugging method provided by the embodiment of the present invention is shown, and the step of sending a login instruction to the ECU to be debugged in step S250 includes:

[0129] S251, determining whether the ECU login password required to log in to the ECU to be debugged is obtained.

[0130] S252: If yes, send a login instruction to the ECU to be debugged based on the ECU login password and the IP address of the ECU to be debugged.

[0131] If not, it will show no permission.

[0132] The above steps implement the process of sending a login instruction to the ECU to be debugged when the ECU login password required to log in to the ECU to be debugged is obtained.

[0133] In the embodiment of the present invention, since each ECU inside the vehicle to be debugged can be connected to the T-BOX of the vehicle to be debugged through a gateway (Switch / Gateway) to realize in-vehicle networking, that is, each ECU inside the vehicle to be debugged can be connected to the outside world through the T-BOX of the vehicle to be debugged as a "bridge".

[0134] Based on this, after successfully logging into the T-BOX of the vehicle to be debugged, you can log into the ECU to be debugged of the vehicle to be debugged for the second time through SSH to perform subsequent debugging operations. Therefore, before successfully logging into the above ECU to be debugged, the local client needs to obtain the ECU login password and send a login instruction to the ECU to be debugged based on the ECU login password and the IP address of the ECU to be debugged. Since the ECU login password needs to be obtained to finally log in to the ECU to be debugged, the information security of each server and the vehicle to be debugged is further guaranteed.

[0135] Optionally, after performing remote debugging on the ECU to be debugged in step S260, the cloud server needs to unbind the configuration port bound to the T-BOX of the vehicle to be debugged in step S230. The specific process can be achieved by the following steps:

[0136] exist Figure 3 Based on Figure 8 , Figure 8 The sixth flow chart of a remote debugging method for an automobile ECU provided by an embodiment of the present invention is shown. In step S260, after receiving a successful login instruction sent by the ECU to be debugged, the remote debugging method for the automobile ECU further includes:

[0137] S270, sending a debugging end instruction to the local server, so that the local server sends an unbinding instruction to the cloud server based on the debugging end instruction, so that the configuration port of the cloud server is unbound from the T-BOX of the vehicle to be debugged.

[0138] The above steps implement a process in which the local client sends a debugging end instruction to the local server after the debugging is completed, so as to finally unbind the configuration port of the cloud server from the T-BOX of the vehicle to be debugged.

[0139] Based on the above-mentioned automobile ECU remote debugging system 100, the embodiment of the present invention also provides another automobile ECU remote debugging method, which uses the cloud server 130 of the automobile ECU remote debugging system 100 as the execution body, please refer to Fig. 9 , Fig. 9 A flow chart of another automobile ECU remote debugging method provided by an embodiment of the present invention is shown.

[0140] The method is applied to a cloud server 130 of an automobile ECU remote debugging system 100. The automobile ECU remote debugging system 100 also includes a local client 110 and a local server 120. The local client 110 is communicatively connected to the local server 120 and the cloud server 130. The cloud server 130 is communicatively connected to a T-BOX 140 of a vehicle to be debugged. The vehicle to be debugged is also provided with a plurality of ECUs, and each ECU is communicatively connected to the T-BOX 140 of the vehicle to be debugged.

[0141] The method includes:

[0142] S280, in response to the debugging instruction including the information of the vehicle to be debugged sent by the local server, searching for the T-BOX of the vehicle to be debugged according to the information of the vehicle to be debugged.

[0143] S281, binding the T-BOX of the vehicle to be debugged found to the configuration port, and generating port information.

[0144] S282, sending the port information to the local client, so that the local client logs in to the T-BOX of the vehicle to be debugged based on the port information, and logs in to the ECU to be debugged to perform remote debugging.

[0145] The above steps realize the process of finding the T-BOX of the vehicle to be debugged according to the information of the vehicle to be debugged when receiving the debugging instruction containing the vehicle information to be debugged sent by the local server, binding the T-BOX of the vehicle to be debugged to the configuration port, and sending the generated port information to the local client.

[0146] In an embodiment of the present invention, since the cloud server and the local client can be connected via Ethernet TCP / IP, after the cloud server binds its configuration port to the T-BOX of the vehicle to be debugged, the generated port information can be sent to the local client, so that the local client can log in to the T-BOX of the vehicle to be debugged through the cloud server based on the port information.

[0147] Optionally, the specific process of searching the T-BOX of the vehicle to be debugged according to the information of the vehicle to be debugged in step S280 can be implemented by the following steps:

[0148] exist Fig. 9 Based on Fig.10 , Fig.10 The second flow chart of another automobile ECU remote debugging method provided by an embodiment of the present invention is shown. The vehicle information to be debugged includes the ICCID code of the vehicle to be debugged. The step of searching the T-BOX of the vehicle to be debugged according to the vehicle information to be debugged in step S280 includes:

[0149] S2801, searching for the T-BOX corresponding to the vehicle to be debugged according to the ICCID code of the vehicle to be debugged.

[0150] The above steps implement the process of searching for the T-BOX corresponding to the vehicle to be debugged according to the ICCID code of the vehicle to be debugged, so as to perform subsequent binding operations based on the found T-BOX of the vehicle to be debugged.

[0151] Optionally, after the local client completes debugging the ECU of the vehicle to be debugged, the local client will send instructions to the local server, so that the cloud server will receive the corresponding instructions and unbind its configuration port from the T-BOX of the vehicle to be debugged. Therefore, the above specific process can be implemented through the following steps:

[0152] exist Fig. 9 Based on Fig.11 , Fig.11 A third flow chart of another automobile ECU remote debugging method provided by an embodiment of the present invention is shown, and the other automobile ECU remote debugging method further includes:

[0153] S290, in response to the unbinding instruction sent by the local server, unbinding the configuration port from the T-BOX of the vehicle to be debugged.

[0154] The above steps realize the process of unbinding the configuration port from the T-BOX of the vehicle to be debugged after receiving the unbinding instruction sent by the local server (that is, indicating that the local client has completed the debugging of the ECU of the vehicle to be debugged).

[0155] Based on the same inventive concept, an embodiment of the present invention also provides an automobile ECU remote debugging system, in which a local client in the automobile ECU remote debugging system is used to execute each process step from step S210 to step S260 in the above embodiment, and a cloud server in the automobile ECU remote debugging system is used to execute each process step from step S280 to step S290 in the above embodiment, and achieve corresponding technical effects.

[0156] For details, please refer to Figure 1a and Figure 1b The automobile ECU remote debugging system 100 includes a local client 110, a local server 120 and a cloud server 130. The local client 110 is connected to the local server 120 and the cloud server 130 in communication. The cloud server 130 is connected to the T-BOX 140 of the vehicle to be debugged. The vehicle to be debugged is also provided with a plurality of ECUs (for example, Figure 1a and Figure 1b ECU1, ECU2 and ECU3 in the figure), each ECU is connected to the T-BOX of the vehicle to be debugged for communication.

[0157] The local client 110 is used to implement a remote debugging method for an automobile ECU as provided in the above embodiment, so as to log in to the ECU to be debugged and perform remote debugging.

[0158] The local server 120 pre-stores the vehicle information, and the local server 120 is used to send a debugging instruction containing the vehicle information to be debugged to the cloud server 130, so that the local client 110 obtains the port information of the vehicle to be debugged sent by the cloud server 130. The port information represents the configuration port bound to the T-BOX 140 of the vehicle to be debugged in the cloud server 130.

[0159] The cloud server 130 is used to implement another automobile ECU remote debugging method as provided in the above embodiment, so that the local client 110 logs in to the T-BOX 140 of the vehicle to be debugged based on the port information sent by it, and logs in to the ECU to be debugged to perform remote debugging.

[0160] It should be noted that the above-mentioned local servers and cloud servers can interact using HTTPS, and TLS / SSL encryption technology can be used to further ensure the security authentication of data requests.

[0161] In an embodiment of the present invention, the ECU networked in the automobile realizes remote debugging without being affected by time and space through an automobile ECU remote debugging method, another automobile ECU remote debugging method and an automobile ECU remote debugging system provided by an embodiment of the present invention. The above-mentioned automobile ECU remote debugging method and another automobile ECU remote debugging method are applicable to electronic units of any Internet of Things platform / machine that requires remote debugging. The embodiment of the present invention can not only solve the problem of remote debugging, but also solve the problems of ECU system upgrade, log extraction and big data upload based on this link.

[0162] It should be noted that the application of the method and system of the embodiments of the present invention is not limited to traditional and new energy vehicles, but can also be applied to IoT machines such as drones, robots, and automatic transportation systems.

[0163] Furthermore, the automobile ECU remote debugging method and system provided by the embodiment of the present invention can not only be used for debugging after remotely logging into the ECU of the vehicle to be debugged, but the method and system can also be applied to a series of remote communication functions such as system upgrade OTA (Over-the-Air Technology) of the ECU of the vehicle to be debugged, log collection, and big data uploading.

[0164] At the same time, the third-party protocol or software involved in the above embodiments is not the only option for the embodiments of the present invention. Using the link but replacing it with other protocols or software also belongs to the alternative or variation of the embodiments of the present invention.

[0165] In addition, the local client in the automobile ECU remote debugging system is not limited to the platform and system, and the local server is not limited to the system and database form. The networking method of the ECU of the vehicle to be debugged for remote debugging includes but is not limited to the method of connecting to the external network using T-BOX in the process of explaining the embodiment of the present invention. It can also be connected to the external network through other devices in the vehicle Ethernet such as IVI (In-Vehicle Infotainment, vehicle infotainment system), or through WIFI hotspots, etc. The embodiment of the present invention does not impose any restrictions on this.

[0166] Based on the same inventive concept, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by the processor 1102, an automobile ECU remote debugging method provided in the above embodiment is implemented.

[0167] Among them, the steps executed when the aforementioned computer program is running will not be described one by one here, and reference may be made to the explanation of the aforementioned automobile ECU remote debugging method in the previous text.

[0168] In several embodiments provided in the present application, it should be understood that the disclosed system and method can also be implemented in other ways. The system embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible implementation architecture, functions and operations of the methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0169] In addition, the functional modules in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0170] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program codes.

[0171] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A remote debugging method for an automobile ECU, characterized in that: A local client applied to an ECU remote debugging system, wherein the ECU remote debugging system further comprises a local server and a cloud server, wherein the local client is communicatively connected to the local server and the cloud server, wherein the cloud server is communicatively connected to a T-BOX of a vehicle to be debugged, wherein the vehicle to be debugged is further provided with a plurality of ECUs, and each of the ECUs is communicatively connected to a T-BOX of the vehicle to be debugged; The method comprises: Upon receiving a successful login instruction sent by the local server, obtaining information of the vehicle to be debugged according to the current state of the vehicle to be debugged; Determining whether the information of the vehicle to be debugged matches the information of the vehicle pre-stored in the local server; If yes, based on the debugging instruction including the information of the vehicle to be debugged sent by the local server to the cloud server, obtaining the port information sent by the cloud server; wherein the port information represents the configuration port in the cloud server bound to the T-BOX of the vehicle to be debugged; Sending a login instruction including the port information to the T-BOX of the vehicle to be debugged through the cloud server; Upon receiving a successful login instruction sent by the T-BOX of the vehicle to be debugged, sending a login instruction to the ECU to be debugged; Upon receiving a successful login instruction sent by the ECU to be debugged, performing a remote debugging operation on the ECU to be debugged; Send a debugging end instruction to the local server, so that the local server sends an unbinding instruction to the cloud server based on the debugging end instruction, so that the configuration port of the cloud server is unbound from the T-BOX of the vehicle to be debugged.

2. The automotive ECU remote debugging method according to claim 1, characterized in that: Before the step of obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged when receiving the successful login instruction sent by the local server, the method further includes: Determine whether the account and password required to log in to the local server are obtained; If so, send a login instruction to the local server based on the account and password.

3. The automotive ECU remote debugging method according to claim 1, characterized in that: The step of obtaining the information of the vehicle to be debugged according to the current state of the vehicle to be debugged comprises: Determining whether the current state of the vehicle to be debugged is an after-sales state; If not, obtain the VIN code and ICCID code of the vehicle to be debugged as the vehicle information to be debugged; If so, obtain the VIN code and ICCID code of the vehicle to be debugged, and the user information corresponding to the vehicle to be debugged as the vehicle information to be debugged.

4. The automotive ECU remote debugging method according to claim 1, characterized in that: The step of sending the login instruction including the port information to the T-BOX of the vehicle to be debugged through the cloud server includes: Determine whether the T-BOX login password required to log in to the T-BOX of the vehicle to be debugged is obtained; If so, a login instruction is sent to the T-BOX of the vehicle to be debugged based on the port information, the T-BOX login password, and the IP address of the cloud server.

5. The automobile ECU remote debugging method according to claim 1, characterized in that: The step of sending a login instruction to the ECU to be debugged includes: Determine whether the ECU login password required to log in to the ECU to be debugged is obtained; If so, a login instruction is sent to the ECU to be debugged based on the ECU login password and the IP address of the ECU to be debugged.

6. A remote debugging method for an automobile ECU, characterized in that: A cloud server applied to an ECU remote debugging system, wherein the ECU remote debugging system further comprises a local client and a local server, wherein the local client is communicatively connected to the local server and the cloud server, and the cloud server is communicatively connected to a T-BOX of a vehicle to be debugged, wherein the vehicle to be debugged is further provided with a plurality of ECUs, and each of the ECUs is communicatively connected to a T-BOX of the vehicle to be debugged; The method comprises: In response to a debugging instruction including information of a vehicle to be debugged sent by the local server, searching for a T-BOX of the vehicle to be debugged according to the information of the vehicle to be debugged; Bind the found T-BOX of the vehicle to be debugged to the configuration port and generate port information; Sending the port information to the local client, so that the local client logs in to the T-BOX of the vehicle to be debugged based on the port information, and logs in to the ECU to be debugged to perform remote debugging; In response to the unbinding instruction sent by the local server, the configuration port is unbound from the T-BOX of the vehicle to be debugged.

7. The automobile ECU remote debugging method according to claim 6, characterized in that: The vehicle information to be debugged includes the ICCID code of the vehicle to be debugged, and the step of searching the T-BOX of the vehicle to be debugged according to the vehicle information to be debugged includes: The T-BOX corresponding to the vehicle to be debugged is searched according to the ICCID code of the vehicle to be debugged.

8. An automotive ECU remote debugging system, characterized in that: It includes a local client, a local server and a cloud server, wherein the local client is connected to the local server and the cloud server in communication, and the cloud server is connected to the T-BOX of the vehicle to be debugged, and the vehicle to be debugged is also provided with a plurality of ECUs, and each of the ECUs is connected to the T-BOX of the vehicle to be debugged in communication; The local client is used to execute the automobile ECU remote debugging method according to any one of claims 1 to 5, so as to log in to the ECU to be debugged and perform remote debugging; The local server pre-stores vehicle information, and the local server is used to send a debugging instruction containing the vehicle information to be debugged to the cloud server, so that the local client obtains the port information of the vehicle to be debugged sent by the cloud server; wherein the port information represents the configuration port in the cloud server bound to the T-BOX of the vehicle to be debugged; The cloud server is used to execute the automobile ECU remote debugging method as described in any one of claims 6-7, so that the local client logs in to the T-BOX of the vehicle to be debugged based on the port information sent by it, and logs in to the ECU to be debugged to perform remote debugging actions.

Images