Remote read-write control method for new energy automobile

Abstract

The invention discloses a remote read-write control method for a new energy vehicle, which comprises the following steps: connecting a cloud platform to a TBOX in the vehicle to establish network connection, issuing an instruction to the TBOX through the cloud platform after the network connection with the TBOX of the vehicle is established on the cloud platform, and executing the instruction by the TBOX of the vehicle to complete the operation of reading and writing a VIN code or a vehicle configuration code. According to the invention, the defect of shortage of diagnostic equipment resources caused by read-write operation of a diagnostic instrument in the prior art is overcome, the read-write operation of the VI N code and the configuration code is completed by adopting a remote read-write mode, the cost is low, and the operation is simple; the method can be adapted to multiple and batch read-write operations, and the read-write operations are realized without being limited by vehicle positions and diagnosis resources.

Description

Technical Field

[0001] This invention relates to the field of remote diagnostic control for new energy vehicles, and in particular to a control method for remotely reading and writing VIN codes and configuration codes for new energy vehicles. Background Technology

[0002] In existing technologies, the reading and writing of vehicle configuration codes and VIN codes are completed through dedicated diagnostic equipment via diagnostic commands. For example, patent application number 202410941389.3 discloses a VIN code reading and writing system and method based on new energy commercial vehicles. This system includes a VIN code writing system placed within the vehicle controller. The VIN code writing system records and stores the vehicle's VIN code through the UDS protocol or memory variables. When the diagnostic tool connects successfully, the VIN code writing system of the vehicle controller adaptively identifies and responds to the request IDs of different diagnostic tools. The VIN code writing system sends out the VIN code as a periodic message or an event-triggered message according to specific protocol rules. When the vehicle rolls off the production line, the OEM records the VIN code through the VIN writing system, and the vehicle controller stores the VIN code in the underlying layer. When the diagnostic tool connects, adaptive identification is enabled, the request source address of different diagnostic tools is parsed, and a positive response is made according to the standard process.

[0003] The aforementioned patent discloses a VIN code reading and writing system that utilizes a diagnostic tool connected to the vehicle to complete the data writing and reading work. However, during the current trial and manufacturing stage of new energy vehicles, there are few readily available diagnostic devices and diagnostic tools. Furthermore, it is not possible to have a diagnostic tool for each customer during the writing and reading process. In particular, the limited availability of diagnostic tools during the after-sales stage leads to low efficiency and difficulty in operation during the reading and writing process. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a remote read / write control method for new energy vehicles, which solves the defects caused by the read / write operation of the existing diagnostic instrument and completes the read / write operation of VIN code and configuration code by means of remote read / write.

[0005] To achieve the above objectives, the technical solution adopted by the present invention is as follows: a remote read / write control method for new energy vehicles, which establishes a network connection by connecting to the TBOX in the vehicle through a cloud platform. After establishing a network connection between the cloud platform and the vehicle's TBOX, the cloud platform sends instructions to the TBOX, which then executes the instructions to complete the read / write operation of the VIN code or vehicle configuration code.

[0006] The cloud platform generates corresponding read and write instructions based on the UDS diagnostic service. The read and write instructions include the diagnostic ID, diagnostic service, and diagnostic data stream. After receiving the diagnostic instructions, the TBOX executes the corresponding instructions to complete the read and write functions corresponding to the diagnostic instructions.

[0007] After receiving the read / write command, the TBOX sends the corresponding command to the controller associated with the command in the vehicle via CAN data to execute the corresponding function.

[0008] When reading and writing VIN codes, the VIN code information required by the vehicle is obtained through the cloud platform. Then, a session mode is initiated between the cloud platform and the vehicle's TBOX to realize data interaction and complete security verification. After the security verification is completed between the cloud platform and the TBOX, the instruction to write the vehicle's VIN code is sent to the TBOX. The TBOX completes the writing of the VIN code according to the writing instruction and returns the writing result.

[0009] Before writing the vehicle's VIN code, it is determined whether a negative response has been received; the VIN code writing process is only allowed if no negative response is received.

[0010] After the VIN code is written, the VIN code writing confirmation is initiated. At this time, TBOX reads the VIN code from the controller that wrote the VIN code and compares the read VIN code with the VIN code queried from the cloud platform. If the two match, a notification is sent that the VIN code writing was successful and the process is complete; otherwise, a notification signal is sent that the VIN code writing failed.

[0011] During configuration read / write operations, the cloud platform calls the configuration code corresponding to the vehicle model, and then initiates a session mode between the cloud platform and the vehicle's TBOX to achieve data interaction and complete security verification. After the security verification is completed between the cloud platform and the TBOX, the cloud platform sends the configuration information to the TBOX, and the vehicle's TBOX interacts with the corresponding controller ECU to complete the writing of the configuration information.

[0012] When the cloud platform sends instructions to the vehicle's TBOX, the communication connection between the cloud platform and the TBOX is monitored in real time. When a communication timeout, signal interruption, or connection failure is detected between the cloud platform and the TBOX, the cloud platform issues a communication timeout reminder signal and resends instructions to the TBOX after a delay.

[0013] When the TBOX sends commands to the vehicle controller ECU, it monitors in real time whether a communication timeout occurs between the TBOX and the vehicle controller ECU. If no response signal is received within a set time after the TBOX sends the command to the ECU, it is determined that the controller communication has timed out. At this time, the TBOX sends a controller communication timeout reminder signal to the cloud platform.

[0014] After receiving the write command, the vehicle controller ECU performs the write operation and determines whether the write operation has failed based on the data detected during the write process, and sends a reminder signal indicating whether the write operation has failed.

[0015] The advantages of this invention are: it solves the defects of existing diagnostic instruments in reading and writing operations, and completes the reading and writing operations of VIN code and configuration code by means of remote reading and writing, which is low cost and simple to operate; it can adapt to multiple and batch reading and writing operations, and can realize reading and writing operations without being limited by vehicle location or diagnostic resources. Attached Figure Description

[0016] The following is a brief explanation of the contents of each of the accompanying drawings and the markings in the drawings:

[0017] Figure 1 The remote read / write control method of this invention involves a system signal transmission diagram. Detailed Implementation

[0018] The specific embodiments of the present invention will be further described in detail below with reference to the accompanying drawings and the description of the preferred embodiments.

[0019] Example 1

[0020] This invention provides a control method for reading and writing VIN and configuration codes of a vehicle without being limited by vehicle location or diagnostic resources. One such method for remote control of an electric vehicle based on UDS diagnostic services includes a diagnostic ID, diagnostic service, and diagnostic data stream.

[0021] like Figure 1 As shown, a remote read / write control method for a new energy vehicle establishes a network connection by connecting to the vehicle's TBOX via a cloud platform. After establishing the network connection with the vehicle's TBOX on the cloud platform, commands are sent to the TBOX, which then executes the commands to read or write the VIN code or vehicle configuration code. When executing read / write commands, the vehicle's TBOX sends corresponding read / write commands to the controller ECU, and the required read / write operations are completed through interaction between the TBOX and the vehicle's controller ECU.

[0022] The process of remotely writing VIN and configuration codes is as follows: The ASP platform sends instructions to the TBOX. Upon receiving the instructions, the TBOX sends diagnostic instructions to each controller via CAN data and executes the corresponding functions. The ASP cloud platform generates corresponding read / write instructions based on the UDS diagnostic service. These instructions include the diagnostic ID, diagnostic service, and diagnostic data stream. After receiving the diagnostic instructions, the TBOX executes the corresponding instructions to complete the read / write functions associated with the diagnostic instructions.

[0023] After receiving a read / write command, the TBOX sends the corresponding command to the associated ECU in the vehicle via CAN data to execute the corresponding function. Since there are many ECUs in the vehicle, the read / write operation is performed based on the ECU corresponding to the command.

[0024] During VIN code reading and writing, the required VIN code information for the vehicle is obtained through the cloud platform. Then, a session mode is initiated between the cloud platform and the vehicle's TBOX to facilitate data interaction and complete security verification. After security verification between the cloud platform and TBOX, a command to write the entire vehicle's VIN code is sent to the TBOX. The TBOX completes the VIN code writing according to the command and provides feedback on the writing result. Before writing the entire vehicle's VIN code, a negative response is checked. The VIN code writing process is only allowed if no negative response is received. If a negative response is received, the writing of the entire vehicle's VIN code is stopped and an alarm signal is issued. After the VIN code writing is completed, a VIN code writing confirmation is initiated. At this time, the TBOX reads the VIN code from the controller that is writing the VIN code and compares it with the VIN code queried from the cloud platform. If they match, a notification of successful VIN code writing and completion is provided; otherwise, a notification of VIN code writing failure is provided. The data flow during writing is shown in the table below:

[0025]

[0026] During configuration read / write operations, the cloud platform calls the configuration code corresponding to the vehicle model, and then initiates a session mode between the cloud platform and the vehicle's TBOX to achieve data interaction and complete security verification. After the security verification is completed between the cloud platform and the TBOX, the cloud platform sends the configuration information to the TBOX. The vehicle TBOX interacts with the corresponding controller ECU to complete the writing of the configuration information. After the writing is completed, the configuration information confirmation process begins. The configuration information in the controller ECU is read and compared with the vehicle model configuration code called by the cloud platform. If they match, the configuration writing is considered complete; otherwise, the configuration writing is considered to have failed, and a confirmation signal for the configuration writing is sent back to the cloud platform. The data flow is shown in the table below:

[0027]

[0028]

[0029] The data flow diagram above defines the communication methods between various ECUs in the vehicle and between the TBOX and the platform. The enterprise management platform sends corresponding instructions to the TBOX, which then sends the corresponding information to each ECU. The ECUs receive the information and process it on the vehicle side, thus achieving the invention's objective. When the cloud platform sends instructions to the vehicle's TBOX, the communication connection between the cloud platform and the TBOX is monitored in real time. If a communication timeout, signal interruption, or connection failure is detected between the cloud platform and the TBOX, the cloud platform issues a communication timeout warning signal and resends the instructions to the TBOX after a delay.

[0030] When the TBOX sends commands to the vehicle controller ECU, it monitors in real time whether a communication timeout occurs between the TBOX and the vehicle controller ECU. If no response signal is received within a set time after the TBOX sends the command to the ECU, it is determined that the controller communication has timed out. At this time, the TBOX sends a controller communication timeout reminder signal to the cloud platform. After receiving the write command, the vehicle controller ECU performs the write operation and determines whether the write operation has failed based on the data detected during the write process, and sends back a reminder signal indicating whether the write operation has failed.

[0031] There are three main reasons why a write operation might fail, as detailed below:

[0032] 1. Platform delivery failure: Server connection failure (platform not connected to the network, poor signal, etc.), TBOX communication timeout (if the platform does not receive a response within 5 seconds after sending a request command to the TBOX, the platform should provide a message "TBOX communication timeout".

[0033] 2. TBOX failed to send: Controller communication timeout (If no response is received within 3 seconds after the TBOX sends a request command to the controller, the platform should display the message "Controller communication timeout").

[0034] 3. Controller write failure: If the requested information length is incorrect, the flashing conditions are not met, the ECU does not support the requested data identifier or the identifier is read-only, the data after the data identifier is unavailable, security access is not unlocked, the ECU detects an error when writing to memory, or the current service session does not support the service, then the controller ECU write failure is determined, and a feedback signal of ECU write failure is sent to TBOX, which then uploads the feedback to the cloud platform.

[0035] The following table (Table 1) analyzes the reasons for controller write failures:

[0036]

[0037] Example 2:

[0038] This embodiment, based on embodiment 1, considers the user's right to know and the confirmation of the flashed information brought about by remote flashing. In a preferred embodiment of this application, different confirmation methods are required during the flashing of the configuration code due to different vehicle states. When the vehicle is in an unsold state, flashing the configuration code does not require confirmation and can be directly upgraded and flashed by the OEM or 4S store. However, once the vehicle has been sold, flashing its configuration code requires the user's consent. Otherwise, arbitrary flashing without the user's knowledge can easily lead to disputes and the modification of vehicle configuration information can also cause changes in the user's control of the vehicle, affecting driving safety. Therefore, the read / write control method of this application determines the sold status of the vehicle. The vehicle's TBOX has a pre-set vehicle sale status flag, which indicates the sale status: 0 for sold and 1 for sold. This flag is written to the TBOX by the sales network or dedicated equipment after a vehicle sale. The default flag value in the TBOX is 0, and it is modified after a sale via the sales network, vehicle networking, or offline diagnostic equipment. During each configuration code flash, the TBOX first obtains the flag value and determines whether the vehicle is currently sold. If not, it directly executes the flashing command, sending the configuration information flashing instruction to the corresponding ECU for the configuration information flashing process. If the vehicle is sold, it indicates that the vehicle is currently in a sold state. In the "sold" status, owner authorization is required before any flashing operation can proceed. Owner authorization is completed via the vehicle network, where the in-vehicle TBOX sends an authorization confirmation message to the owner's mobile app or phone number linked to the vehicle network. It then receives confirmation messages sent to the in-vehicle TBOX via the mobile app or SMS through the vehicle network in real time. Upon receiving the owner's confirmation, the flashing process continues; otherwise, it pauses and sends an unauthorized flashing warning signal to the cloud platform. When sending confirmation messages to the owner's vehicle network mobile app, the content and reason for the flashing are also communicated to the user, who confirms the flashing via a button on the app. Since ECU configuration flashing involves vehicle function settings, the owner's right to know must be guaranteed to prevent unauthorized upgrades that could lead to user complaints or even safety hazards.

[0039] Obviously, the specific implementation of this invention is not limited to the above-described methods. Any non-substantial improvements made using the inventive concept and technical solution of this invention are within the protection scope of this invention.

Claims

1. A remote read-write control method for a new energy vehicle, characterized in that The network connection is established by connecting to the TBOX in the vehicle through the cloud platform. After the network connection between the cloud platform and the TBOX in the vehicle is established, the cloud platform sends instructions to the TBOX, and the TBOX executes the instructions to complete the reading and writing of the VIN code or vehicle configuration code.

2. The new energy vehicle remote read-write control method of claim 1, wherein: The cloud platform generates corresponding reading and writing instructions based on the UDS diagnostic service, and the reading and writing instructions include diagnostic ID, diagnostic service and diagnostic data flow. After receiving the diagnostic instructions, the TBOX executes the corresponding instructions to complete the reading and writing functions corresponding to the diagnostic instructions.

3. The new energy vehicle remote read-write control method according to claim 1 or 2, characterized in that: After receiving the reading and writing instructions, the TBOX sends corresponding instructions to the controller associated with the instructions in the vehicle through CAN data to execute the corresponding functions.

4. The new energy vehicle remote read-write control method according to claim 1 or 2, characterized in that: When reading and writing the VIN code, the cloud platform obtains the required VIN code information of the vehicle, and then starts the session mode between the cloud platform and the TBOX to realize data interaction to complete security verification. After the security verification between the cloud platform and the TBOX is completed, the instruction for writing the VIN code of the whole vehicle is sent to the TBOX, and the TBOX completes the writing of the VIN code according to the writing instruction and feeds back the writing result.

5. The new energy vehicle remote read-write control method of claim 4, characterized in that: Before writing the VIN code of the whole vehicle, it is judged whether negative response appears or not. Only when no negative response appears, the VIN code writing process is allowed to enter.

6. The new energy vehicle remote read-write control method of claim 4, characterized in that: After completing the writing of the VIN code, the VIN code writing confirmation is entered. At this time, the TBOX reads the VIN code in the controller where the VIN code is written, compares the read VIN code with the VIN code queried by the cloud platform, and if the two are consistent, it feeds back the VIN code writing success and ends the prompt; Otherwise, a prompt signal of VIN code writing failure is fed back.

7. The new energy vehicle remote read-write control method according to claim 1 or 2, characterized in that: When reading and writing the configuration, the cloud platform calls the corresponding configuration code of the vehicle type, and then starts the session mode between the cloud platform and the TBOX to realize data interaction to complete security verification. After the security verification between the cloud platform and the TBOX is completed, the cloud platform sends the configuration information to the TBOX, and the TBOX interacts with the corresponding controller ECU to complete the writing of the configuration information.

8. The new energy vehicle remote read-write control method according to claim 1 or 2, characterized in that: When the cloud platform sends instructions to the TBOX of the vehicle, the communication connection between the cloud platform and the TBOX is monitored in real time. When it is detected that the communication between the cloud platform and the TBOX is timed out, the signal is interrupted, or the connection fails, the cloud platform sends a communication timeout reminder signal and re-sends instructions to the TBOX after a delay.

9. The new energy vehicle remote read-write control method according to claim 1 or 2, characterized in that: When the TBOX sends instructions to the vehicle controller ECU, whether the communication between the TBOX and the vehicle ECU is timed out is monitored in real time. If no response signal is received within a set time after the TBOX sends instructions to the ECU, it is judged that the controller communication is timed out, and the TBOX sends a controller communication timeout reminder signal to the cloud platform.

10. The new energy vehicle remote read-write control method according to claim 1 or 2, characterized in that: After receiving the writing instruction, the vehicle controller ECU performs the writing operation and judges whether the writing fails according to the data detected in the writing process and feeds back the reminder signal of whether the writing fails.

Images