CN117992088A

CN117992088A - Vehicle software flashing method, system, vehicle and readable medium

Info

Publication number: CN117992088A
Application number: CN202410224303.5A
Authority: CN
Inventors: 郭卫君
Original assignee: Qiji Automotive Technology Guangzhou Co ltd
Current assignee: Qiji Automotive Technology Guangzhou Co ltd
Priority date: 2024-02-28
Filing date: 2024-02-28
Publication date: 2024-05-07

Abstract

The application relates to a vehicle software flashing method, a system, a vehicle and a readable medium. The method comprises the following steps: downloading the flash file from the diagnostic instrument server through the remote information processor; and (5) adopting the file to be written, and carrying out software writing on the intelligent driving controller. The scheme provided by the application can greatly shorten the software refreshing time, improve the software refreshing success rate and bring great convenience for after-sale software refreshing.

Description

Vehicle software flashing method, system, vehicle and readable medium

Technical Field

The present application relates to the field of software flashing technology, and in particular, to a vehicle software flashing method, system, vehicle and readable medium.

Background

In an after-market repair scenario, it is generally necessary to perform software flashing operations on an ECU (Electronic Control Unit ) of the vehicle. With the increasing complexity of the ECU functions, the software is becoming larger, especially the software of the intelligent driving related control unit, which may even reach about 50M.

In the related art, a traditional CAN (Controller Area Network ) bus is adopted to carry out software refreshing on the ECU, however, the traditional CAN bus is adopted to carry out refreshing for too long, the refreshing failure rate is too high, and after-sale software refreshing is very inconvenient.

Disclosure of Invention

In order to solve or partially solve the problems in the related art, the application provides a vehicle software refreshing method, a system, a vehicle and a readable medium, which can greatly shorten the software refreshing time, improve the software refreshing success rate and bring great convenience to after-sale software refreshing.

The first aspect of the present application provides a vehicle software flashing method, the vehicle including an intelligent driving controller and a remote information processor, the intelligent driving controller being connected to a diagnostic apparatus server through the remote information processor, the method comprising:

Downloading, by the telematics processor, a swipe file from the diagnostic instrument server;

and adopting the file to be written, and carrying out software writing on the intelligent driving controller.

In one embodiment, the vehicle further comprises a vehicle diagnostic interface through which the intelligent driving controller is connected to a diagnostic apparatus; the downloading of the flash file from the diagnostic instrument server via the telematics processor includes:

receiving a brushing file downloading instruction sent by the diagnostic equipment through the vehicle diagnostic interface;

and downloading the flash file from the diagnostic instrument server by the remote information processor through the flash file downloading instruction.

In one embodiment, the telematics unit is communicatively connected to the diagnostic unit server via a first network, the intelligent driving controller is communicatively connected to the telematics unit via a second network, and the vehicle diagnostic interface is communicatively connected to the diagnostic unit device and the intelligent driving controller via a third network, wherein the first network and the second network have a time delay that is less than the time delay of the third network, respectively.

In one embodiment, the first network is a cellular network, the second network is an ethernet network, and the third network is a controller area network.

In one embodiment, the receiving, by the vehicle diagnostic interface, a swipe file download instruction sent by the diagnostic apparatus device includes:

receiving an MCU file downloading instruction and an SOC file downloading instruction which are sequentially transmitted by the diagnostic equipment through the vehicle diagnostic interface;

The downloading, by the telematics processor, the swipe file from the diagnostic instrument server using the swipe file download instruction, comprising:

Downloading an MCU file from the diagnostic instrument server by the remote information processor by adopting the MCU file downloading instruction;

And after the MCU file is successfully downloaded, the remote information processor downloads the SOC file from the diagnostic instrument server by adopting the SOC file downloading instruction.

In an embodiment, after the software flashing of the intelligent driving controller, the method further comprises:

receiving a consistency check instruction sent by the diagnostic equipment through the vehicle diagnostic interface;

checking whether the MCU file is matched with the SOC file or not by adopting the consistency checking instruction;

if the MCU file is matched with the SOC file, receiving a reset instruction sent by the diagnostic equipment through the vehicle diagnostic interface;

And resetting the intelligent driving controller by adopting the reset instruction.

In one embodiment, the method further comprises:

Detecting whether the vehicle meets a brushing condition;

if the vehicle meets the brushing condition, receiving a connection instruction sent by the diagnostic equipment through the vehicle diagnostic interface; wherein the connection instruction comprises an IP dynamic address of the diagnostic instrument server;

And the remote information processor is connected with the diagnostic instrument server by adopting the IP dynamic address.

A second aspect of the present application provides a vehicle software flashing system comprising an intelligent driving controller and a telematics processor, the intelligent driving controller being connected to a diagnostic instrument server through the telematics processor,

The remote information processor is used for downloading the refreshing file from the diagnostic instrument server under the control of the intelligent driving controller;

and the intelligent driving controller is used for performing software refreshing by adopting the refreshing file downloaded by the remote information processor.

A third aspect of the application provides a vehicle comprising a vehicle software flashing system as claimed in claim 8.

A fourth aspect of the application provides a computer readable storage medium having stored thereon executable code which, when executed by a vehicle software flashing system of a vehicle, causes the vehicle software flashing system to perform a method as described above.

The technical scheme provided by the application can comprise the following beneficial effects:

According to the scheme provided by the application, the remote information processor downloads the brush writing file from the diagnostic instrument server; and (5) adopting the file to be written, and carrying out software writing on the intelligent driving controller. According to the application, the remote information processor is used as a platform, so that the intelligent driving controller can remotely download software from the diagnostic instrument server, thereby greatly shortening the software refreshing time, improving the software refreshing success rate and bringing great convenience to after-sale software refreshing.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The foregoing and other objects, features and advantages of the application will be apparent from the following more particular descriptions of exemplary embodiments of the application as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts throughout the exemplary embodiments of the application.

FIG. 1 is a flow chart of a vehicle software flashing method according to an embodiment of the application;

FIG. 2 is another flow chart of a vehicle software flashing method according to an embodiment of the application;

FIG. 3 is a schematic diagram of interactions of a vehicle software flashing system, a diagnostic server, a diagnostic device, and a diagnostic device, as shown in an embodiment of the present application;

FIG. 4 is a flow chart of a vehicle software flashing as shown in an embodiment of the application;

FIG. 5 is a schematic diagram of a vehicle software flashing system according to an embodiment of the application;

Fig. 6 is a schematic structural view of a vehicle according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While embodiments of the present application are illustrated in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

In the related art, a traditional CAN bus is adopted to carry out software refreshing on the ECU, for example, a maintenance personnel after sale manually selects a refreshing file of a designated ECU, and because the refreshing file of the ECU is too large, the refreshing file CAN only be split into a plurality of small files in the related art so as to ensure that the size of each small file is in a reasonable range. However, as the intelligent driving functions are more and more abundant, the space occupied by the software of the intelligent driving controller is increased continuously, the size of the software CAN even reach about 50M, and the writing time of writing files with more than 10M is often needed to be more than half an hour, so that the writing time of the traditional CAN bus is too long in the related technology, for example, more than 1 hour is often needed, the writing failure rate is higher as the writing time is longer, so that after-sales maintenance personnel CAN write successfully only by writing for many times, and after-sales software writing is very inconvenient.

In view of the above problems, the embodiment of the application provides a vehicle software refreshing method, which uses a remote information processor as a platform, so that an intelligent driving controller can remotely download software from a diagnostic instrument server, thereby greatly shortening the software refreshing time, improving the software refreshing success rate and bringing great convenience to after-sale software refreshing.

The following describes the technical scheme of the embodiment of the present application in detail with reference to the accompanying drawings.

Fig. 1 is a flow chart of a vehicle software flashing method according to an embodiment of the present application. The vehicle comprises an intelligent driving controller and a remote information processor, wherein the intelligent driving controller is connected with a diagnostic instrument server through the remote information processor.

Referring to fig. 1, the vehicle software flashing method of the present application includes:

S110, downloading the flash file from the diagnostic instrument server through the remote information processor.

The vehicle may be configured with an intelligent drive controller and a telematics processor, and the vehicle software flashing method may be applied to the intelligent drive controller, wherein the intelligent drive controller may be communicatively coupled to the telematics processor.

The intelligent driving controller is intelligent equipment integrating various sensors, chips and algorithms and is mainly responsible for sensing, decision making, executing and other works, so that the intelligent driving controller has great potential in the aspects of improving driving safety, relieving traffic pressure, improving driving experience and the like.

The remote information processor is used as a wireless gateway, has the functions of 4G remote wireless communication, GPS satellite positioning, acceleration sensing, CAN communication and the like, provides a remote communication interface for the whole vehicle, and provides services including driving data acquisition, driving track recording, vehicle fault monitoring, vehicle remote inquiry and control (locking and unlocking, air conditioner control, window control, transmitter torque limitation, engine starting and stopping), driving behavior analysis, 4G wireless hot spot sharing and the like. The intelligent drive controller may be connected to the diagnostic server via a telematics processor.

The diagnostic instrument server can be deployed at the cloud end, and the flash file aiming at the intelligent driving controller is also placed in the diagnostic instrument server for maintenance, so that the intelligent driving controller can remotely download the flash file from the diagnostic instrument server through the remote information processor.

S111, performing software refreshing on the intelligent driving controller by adopting a refreshing file.

The update file maintained by the diagnostic instrument server belongs to the latest software version, so that the intelligent driving controller can adopt the update file downloaded from the diagnostic instrument server to update the software of the intelligent driving controller, namely, update the software of the intelligent driving controller. According to the embodiment of the application, the software version in the intelligent driving controller can be updated by transmitting the flash file downloaded by the remote information processor to the intelligent driving controller, so that the purpose of improving the vehicle performance is achieved, for example, the vehicle power can be improved, the vehicle oil consumption can be reduced, and new functions can be added for the vehicle.

It should be noted that, in the embodiment of the present application, the software flashing operation is performed in an after-sales maintenance scenario, which is only opened to after-sales maintenance personnel and not to clients (such as vehicle owners) in order to ensure vehicle safety.

As can be seen from this example, the solution provided by the present application downloads the swipe file from the diagnostic instrument server via the telematics processor; and (5) adopting the file to be written, and carrying out software writing on the intelligent driving controller. According to the application, the remote information processor is used as a platform, so that the intelligent driving controller can remotely download software from the diagnostic instrument server, thereby greatly shortening the software refreshing time, improving the software refreshing success rate and bringing great convenience to after-sale software refreshing.

FIG. 2 is another flow chart of a vehicle software flashing method according to an embodiment of the application. The vehicle comprises an intelligent driving controller, a remote information processor and a vehicle diagnosis interface, wherein the intelligent driving controller is connected with a diagnosis instrument server through the remote information processor, and the intelligent driving controller is connected with diagnosis instrument equipment through the vehicle diagnosis interface.

Referring to fig. 2, the vehicle software flashing method of the present application includes:

s210, receiving a flash file downloading instruction sent by the diagnostic equipment through the vehicle diagnostic interface.

The embodiment of the application performs software flashing operation on an after-sales maintenance scene, and relates to a vehicle software flashing system, a diagnostic instrument server and diagnostic instrument equipment, wherein the vehicle software flashing system can be deployed at a vehicle end, and the diagnostic instrument server can be deployed at a cloud end.

FIG. 3 is an interactive schematic diagram of a vehicle software flashing system, a diagnostic server, a diagnostic device, wherein the vehicle software flashing system may include an intelligent drive controller, a T-box (TELEMATICS BOX, telematics) and an OBD interface (On-Board Diagnostics, vehicle diagnostic interface), wherein the OBD interface is a standard harness connector through which the intelligent drive controller may connect with the diagnostic device.

The remote information processor (T-box) is used as a wireless gateway, has the functions of 4G remote wireless communication, GPS satellite positioning, acceleration sensing, CAN communication and the like, provides a remote communication interface for the whole vehicle, and provides services including driving data acquisition, driving track recording, vehicle fault monitoring, vehicle remote inquiry and control (unlocking and locking, air conditioner control, vehicle window control, transmitter torque limitation, engine starting and stopping), driving behavior analysis, 4G wireless hot spot sharing and the like. The intelligent drive controller may thus be connected to the diagnostic server via a telematics processor (T-box).

Since the configurations of vehicles of different vehicle types may be different, for example, some vehicle types are not configured with an intelligent driving controller, or a dual-Chip architecture of an MCU (Micro Control Unit, micro-control unit) and an SOC (System On Chip) is not adopted, the requirements for the writing of vehicles of different vehicle types may be different. In this regard, the diagnostic device may first scan vehicle information after being connected to the OBD interface, where the vehicle information may include vehicle type information through which it may be identified whether the vehicle is configured with an intelligent driving controller or whether a dual MCU and SOC architecture is employed. If the vehicle is provided with an intelligent driving controller or the vehicle adopts an architecture of an MCU and an SOC, the file to be written is often larger, for example, more than 10M, so that the embodiment of the application does not need to walk the downloading channel of the diagnostic equipment, the CAN bus and the intelligent driving controller, but walks the downloading channel of the diagnostic equipment server, the remote information processor and the intelligent driving controller, namely, the diagnostic equipment only needs to send related communication instructions to the intelligent driving controller, and does not need to send the file to be written to the intelligent driving controller. For example, the diagnostic device sends a swipe file download instruction to the intelligent driving controller via the OBD interface.

In an embodiment, the method may further include:

Detecting whether the vehicle meets a brushing condition; if the vehicle meets the brushing condition, receiving a connection instruction sent by diagnostic equipment through a vehicle diagnostic interface; the connection instruction comprises an IP dynamic address of the diagnostic instrument server; the remote information processor is connected with the diagnostic instrument server by adopting an IP dynamic address.

When the vehicle is identified to be provided with the intelligent driving controller or is in a framework of adopting an MCU and an SOC, a brushing flow can be started. After entering a brushing flow, the embodiment of the application can firstly detect whether the vehicle meets the brushing condition, wherein the brushing condition can comprise at least one of a vehicle power-on condition and a vehicle electric quantity condition. If the vehicle does not meet the brushing condition, the vehicle can be indicated to have a fault, so that the vehicle can be firstly subjected to fault elimination, and then the brushing flow is restarted; if the vehicle meets the brushing condition, the vehicle can be indicated that no fault exists in the vehicle, and therefore the diagnostic equipment can send a connection instruction to the intelligent driving controller through the OBD interface.

In one example, an embodiment of the present application may detect whether a vehicle is in a powered-on state. If the vehicle is in a power-down state, namely the vehicle is not in a power-up state, software refreshing operation cannot be executed for the vehicle, so that the vehicle can be controlled to be powered up first, and then the refreshing flow is restarted when the vehicle is in the power-up state; if the vehicle is in a powered-on state, a software flashing operation can be performed for the vehicle, so the diagnostic device can send a connection instruction to the intelligent driving controller through the OBD interface.

In another example, the embodiment of the present application may acquire battery power information of a vehicle, and then detect whether the battery power information is greater than a preset power threshold. If the battery power information is smaller than a preset power threshold, in order to prevent the vehicle from suddenly losing power in the brushing process and causing the brushing failure, the embodiment of the application can charge the battery of the vehicle first, and then restart the brushing flow after the battery power information reaches the preset power threshold; if the battery power information is greater than or equal to a preset power threshold, the battery power of the vehicle is indicated to be capable of supporting the power required in the brushing process, and therefore the diagnostic equipment can send a connection instruction to the intelligent driving controller through the OBD interface.

The connection instruction may include, among other things, an IP dynamic address of the diagnostic instrument server. After the intelligent driving controller receives the connection instruction, the connection instruction can be adopted to control the remote information processor to actively connect with the diagnostic instrument server, for example, the intelligent driving controller can send the connection instruction to the remote information processor, and the remote information processor extracts an IP dynamic address from the connection instruction and then actively connects with the diagnostic instrument server by adopting the IP dynamic address.

Then, the intelligent driving controller can detect whether the network connection between the remote information processor and the diagnostic instrument server is normal. If the network connection between the remote information processor and the diagnostic instrument server is abnormal, the remote information processor can be controlled to re-connect the diagnostic instrument server by adopting the IP dynamic address, or the connection failure information can be sent to the diagnostic instrument equipment through the OBD interface, so that the diagnostic instrument equipment can send a new connection instruction. After the intelligent driving controller receives the new connection instruction through the OBD interface, the new connection instruction can be adopted to control the remote information processor to actively connect with the diagnostic instrument server again, for example, the intelligent driving controller can send the new connection instruction to the remote information processor, the remote information processor extracts a new IP dynamic address from the new connection instruction, and then the diagnostic instrument server is actively connected again by adopting the new IP dynamic address. If the network connection of the telematics unit to the diagnostic instrument server is normal, step 210 described above may be performed.

In one embodiment, the telematics processor is communicatively coupled to the diagnostic instrument server based on a first network, the intelligent drive controller is communicatively coupled to the telematics processor based on a second network, and the vehicle diagnostic interface is communicatively coupled to the diagnostic instrument device and the intelligent drive controller, respectively, based on a third network, wherein the delays of the first network and the second network are less than the delays of the third network, respectively.

As shown in fig. 3, the communication network used by the connection of the telematics processor and the diagnostic apparatus server, the communication network used by the connection of the intelligent driving controller and the telematics processor, and the communication network used by the connection of the OBD interface and the diagnostic apparatus device or the intelligent driving controller are all different. For example, the remote information processor is connected with the diagnostic instrument server through a first network, the intelligent driving controller is connected with the remote information processor through a second network, and the OBD interface is connected with the diagnostic instrument device and the intelligent driving controller through a third network respectively, wherein the first network, the second network and the third network are different.

In the embodiment of the application, the time delay of the first network is smaller than the time delay of the third network, and the time delay of the second network is also smaller than the time delay of the third network. Where delay refers to the time required for data to travel from one end of a network or link to the other, the smaller the delay, the shorter the travel time.

Therefore, the embodiment of the application uses the first network and the second network with small time delay to remotely download the refreshing file from the diagnostic instrument server, thereby greatly shortening the software refreshing time and improving the success rate of the software refreshing.

In an embodiment of the present application, the first network may be a cellular network, the second network may be an ethernet network, and the third network may be a controller area network. The cellular network may include a 4G network, a 5G network, etc., which is not limited by the embodiments of the present application. The controller area network may refer to a network that communicates through a CAN bus.

S211, downloading the flash file from the diagnostic instrument server by adopting a flash file downloading instruction through the remote information processor.

The diagnostic instrument server is deployed at the cloud end, and the flashing file for the intelligent driving controller is also placed in the diagnostic instrument server for maintenance, so that after receiving the flashing file downloading instruction, the intelligent driving controller can adopt the flashing file downloading instruction to control the remote information processor to remotely download the flashing file from the diagnostic instrument server, for example, the intelligent driving controller can send the flashing file downloading instruction to the remote information processor, and the remote information processor adopts the flashing file downloading instruction to download the flashing file from the diagnostic instrument server.

In an embodiment, receiving, through the vehicle diagnostic interface, a swipe file download instruction sent by the diagnostic apparatus device may include:

And receiving the MCU file downloading instruction and the SOC file downloading instruction which are sequentially transmitted by the diagnostic equipment through the vehicle diagnostic interface.

In one embodiment, downloading the swiped file from the diagnostic instrument server via the telematics processor using a swiped file download instruction may include:

Downloading an MCU file from a diagnostic instrument server by adopting an MCU file downloading instruction through a remote information processor; after the MCU file is successfully downloaded, the SOC file is downloaded from the diagnostic instrument server by adopting an SOC file downloading instruction through the remote information processor.

The vehicle configured with the intelligent driving controller generally adopts a dual-chip architecture of an MCU and an SOC, so that the refreshing file downloading instruction can comprise an MCU file downloading instruction and an SOC file downloading instruction, and the refreshing file can comprise an MCU file and an SOC file.

In practical application, under the condition that the network connection between the remote information processor and the diagnostic instrument server is normal, the diagnostic instrument device can send an MCU file downloading instruction to the intelligent driving controller through the OBD interface, the intelligent driving controller can adopt the MCU file downloading instruction to control the remote information processor to download the MCU file from the diagnostic instrument server, for example, the intelligent driving controller can send the MCU file downloading instruction to the remote information processor, and the remote information processor adopts the MCU file downloading instruction to download the MCU file from the diagnostic instrument server. During this time, the diagnostic apparatus device may query the MCU file download progress in real time and determine the download result. When the downloading result represents that the downloading of the MCU file fails, the vehicle can be indicated to have a fault, for example, the network suddenly drops off in the downloading process to cause the downloading of the MCU file to fail, so that the vehicle can be firstly subjected to fault elimination, and then the brushing flow can be restarted; when the download result represents that the MCU file is successfully downloaded, the vehicle can be indicated that no fault exists, so that the MCU file can be adopted to carry out software brushing on the intelligent driving controller, and the diagnostic equipment can send an SOC file download instruction to the intelligent driving controller through the OBD interface. The intelligent driving controller may use the SOC file downloading instruction to control the remote information processor to download the SOC file from the diagnostic apparatus server, for example, the intelligent driving controller may send the SOC file downloading instruction to the remote information processor, and the remote information processor uses the SOC file downloading instruction to download the SOC file from the diagnostic apparatus server. During this time, the diagnostic apparatus can query the SOC file download progress in real time and judge the download result. When the download result represents that the download of the SOC file fails, the vehicle can be indicated to have a fault, for example, the download of the SOC file fails due to sudden network disconnection in the download process, so that the vehicle can be firstly subjected to fault elimination, and then the refreshing flow can be restarted; when the download result represents that the SOC file is successfully downloaded, the vehicle can be indicated that no fault exists, so that the SOC file can be adopted to carry out software refreshing on the intelligent driving controller.

S212, software refreshing is carried out on the intelligent driving controller by adopting the refreshing file.

The MCU file and the SOC file maintained by the diagnostic instrument server belong to the latest software version, so that the intelligent driving controller can sequentially adopt the MCU file and the SOC file downloaded from the diagnostic instrument server to carry out software refreshing on the intelligent driving controller, namely, carry out software refreshing on the intelligent driving controller. According to the embodiment of the application, the MCU file and the SOC file which are successively downloaded by the remote information processor are sequentially transmitted to the intelligent driving controller, so that the software version in the intelligent driving controller can be updated, the purpose of improving the vehicle performance is achieved, for example, the vehicle power can be improved, the vehicle oil consumption can be reduced, and new functions can be added for the vehicle.

In an embodiment, after the software flashing of the intelligent driving controller, the method may further include:

Receiving a consistency check instruction sent by diagnostic equipment through a vehicle diagnostic interface; adopting a consistency check instruction to check whether the MCU file is matched with the SOC file; if the MCU file is matched with the SOC file, receiving a reset instruction sent by diagnostic equipment through a vehicle diagnostic interface; and resetting the intelligent driving controller by adopting a reset instruction.

After software refreshing is performed on the intelligent driving controller, that is, after the intelligent driving controller is sequentially subjected to MCU file refreshing and SOC file refreshing, in order to check whether the MCU file and the SOC file can normally operate, the embodiment of the application can perform consistency check on the intelligent driving controller, for example, the diagnostic apparatus equipment can send a consistency check instruction to the intelligent driving controller through an OBD interface, and the intelligent driving controller can use the consistency check instruction to check whether the MCU file and the SOC file are matched.

If the MCU file is not matched with the SOC file, the vehicle can be indicated to have faults, for example, the MCU file and the SOC file are not matched with the intelligent driving controller, so that the updated software cannot normally run, the vehicle can be firstly subjected to fault elimination, and then the brushing flow is restarted; if the MCU file is matched with the SOC file, the fact that the vehicle has no fault can be indicated, and therefore the diagnostic equipment can send a reset instruction to the intelligent driving controller through the OBD interface, the intelligent driving controller can adopt the reset instruction to reset the intelligent driving controller, and updated software can be operated on the intelligent driving controller.

Compared with the downloading channel of the diagnostic equipment, the CAN bus and the intelligent driving controller in the related art, the method has the advantages that the CAN network delay is large, and the brushing file of the intelligent driving controller is often large, so that the traditional CAN bus is used for excessively long brushing time in the related art, the brushing failure rate is excessively high, and after-sale software brushing is very inconvenient. In this regard, in the embodiment of the application, the remote information processor and the intelligent driving controller are used as the downloading channels, and the remote information processor has the functions of a cellular network and an ethernet, so that the remote information processor is used as a platform, the intelligent driving controller can remotely download software from the diagnostic device server, and the diagnostic device only needs to send related communication instructions to the intelligent driving controller, thereby greatly shortening the software writing time, improving the software writing success rate and bringing great convenience to after-sale software writing.

As can be seen from this example, the scheme provided by the present application receives, through the vehicle diagnostic interface, a swipe file download instruction sent by the diagnostic instrument device; downloading the flash file from the diagnostic instrument server by adopting a flash file downloading instruction through the remote information processor; and (5) adopting the file to be written, and carrying out software writing on the intelligent driving controller. The application does not need to walk the downloading channel of the diagnostic apparatus equipment, the CAN bus and the intelligent driving controller, but walks the downloading channel of the diagnostic apparatus server, the remote information processor and the intelligent driving controller, namely, the application uses the remote information processor as a platform, so that the intelligent driving controller CAN remotely download software from the diagnostic apparatus server, and the diagnostic apparatus equipment only needs to send related communication instructions to the intelligent driving controller, thereby greatly shortening the software refreshing time, improving the software refreshing success rate and bringing great convenience for after-sale software refreshing.

In order that those skilled in the art may better understand the embodiments of the present application, the embodiments of the present application will be described by the following examples.

FIG. 4 is a flow chart of vehicle software flashing, specifically as follows:

s401, detecting whether a vehicle meets a brushing condition; if not, jumping to step S415; if yes, the process proceeds to step S402.

S402, if the vehicle meets the brushing condition, receiving a connection instruction sent by the diagnostic equipment through an OBD interface (vehicle diagnostic interface); wherein the connection instruction includes an IP dynamic address of the diagnostic instrument server.

S403, connecting the diagnostic instrument server by adopting an IP dynamic address through a T-box (remote information processor).

S404, receiving an MCU file downloading instruction sent by the diagnostic equipment through the OBD interface under the condition that the network connection between the T-box and the diagnostic equipment server is normal.

S405, downloading the MCU file from the diagnostic instrument server by adopting an MCU file downloading instruction through the T-box.

S406, detecting whether the MCU file is successfully downloaded; if not, jumping to step S415; if yes, the process proceeds to step S407.

And S407, if the MCU file is successfully downloaded, adopting the MCU file to perform software refreshing on the intelligent driving controller.

S408, receiving an SOC file downloading instruction sent by the diagnostic equipment through the OBD interface.

S409, detecting whether the SOC file is downloaded successfully; if not, jumping to step S415; if yes, go to step S410.

S410, if the SOC file is downloaded successfully, the SOC file is adopted to carry out software refreshing on the intelligent driving controller.

S411, receiving a consistency check instruction sent by the diagnostic equipment through the OBD interface.

S412, checking whether the MCU file is matched with the SOC file or not by adopting a consistency check instruction; if not, jumping to step S415; if yes, the flow goes to step S413.

S413, if the MCU file is matched with the SOC file, receiving a reset instruction sent by the diagnostic equipment through the OBD interface.

S414, resetting the intelligent driving controller by adopting a reset instruction, and ending the brushing flow.

S415, the vehicle is removed, after the fault is removed, the process returns to S401 to restart the brushing flow.

Corresponding to the embodiment of the application function implementation method, the application also provides a vehicle software flashing system, a vehicle, a computer readable storage medium and corresponding embodiments.

Fig. 5 is a schematic structural diagram of a vehicle software flashing system according to an embodiment of the present application.

Referring to fig. 5, the vehicle software flashing system 50 provided by the application includes an intelligent driving controller 502 and a remote information processor 501, wherein the intelligent driving controller 502 is connected with a diagnostic server through the remote information processor 501.

The remote information processor 501 is configured to download the swipe file from the diagnostic instrument server under the control of the intelligent driving controller 502.

The intelligent driving controller 502 is configured to perform software flashing by using the flashing file downloaded by the telematics processor 501.

In one embodiment, the vehicle software flashing system 50 may further include a vehicle diagnostic interface 503, and the intelligent drive controller 502 may be coupled to the diagnostic instrument device via the vehicle diagnostic interface 503.

The vehicle diagnosis interface 503 is configured to receive a download instruction of the flash file sent by the diagnostic apparatus.

The intelligent driving controller 502 may include a swipe file download control module 5021, among other things.

The flashing file download control module 5021 is configured to control the telematics processor 501 to download a flashing file from the diagnostic apparatus server by using a flashing file download instruction.

The telematics processor 501 may include, among other things, a swipe file download module 5011.

The swipe file downloading module 5011 is configured to download the swipe file from the diagnostic apparatus server under the control of the swipe file downloading control module 5021.

In one embodiment, the telematics processor 501 is communicatively coupled to the diagnostic server via a first network, the intelligent drive controller 502 is communicatively coupled to the telematics processor 501 via a second network, and the vehicle diagnostic interface 503 is communicatively coupled to the diagnostic device and the intelligent drive controller 502 via a third network, wherein the first network and the second network each have a latency less than the latency of the third network.

In an embodiment, the vehicle diagnosis interface 503 is further configured to receive an MCU file downloading instruction and an SOC file downloading instruction sequentially sent by the diagnostic apparatus device.

The brush file download control module 5021 may include an MCU file download control sub-module and an SOC file download control sub-module.

The MCU file download control sub-module is configured to control the telematics processor 501 to download the MCU file from the diagnostic apparatus server using the MCU file download instruction.

And the SOC file downloading control sub-module is used for controlling the remote information processor 501 to download the SOC file from the diagnostic instrument server by adopting an SOC file downloading instruction after the MCU file is successfully downloaded.

The swipe file downloading module 5011 may include an MCU file downloading sub-module and an SOC file downloading sub-module.

And the MCU file downloading sub-module is used for downloading the MCU file from the diagnostic instrument server under the control of the MCU file downloading control sub-module.

And the SOC file downloading sub-module is used for downloading the SOC file from the diagnostic instrument server under the control of the SOC file downloading control sub-module.

In one embodiment, the vehicle diagnostic interface 503 is also configured to receive a compliance check instruction sent by the diagnostic instrument device after the intelligent drive controller 502 is software-flushed.

The intelligent drive controller 502 may also include a consistency check module 5022, among other things.

And the consistency checking module 5022 is used for checking whether the MCU file is matched with the SOC file or not by adopting a consistency checking instruction.

If the consistency checking module 5022 checks that the MCU file is matched with the SOC file, the vehicle diagnostic interface 503 is further configured to receive a reset instruction sent by the diagnostic apparatus device.

The intelligent driving controller 502 may further include a reset module 5023.

The reset module 5023 is configured to reset the intelligent driving controller 502 by using a reset instruction.

In an embodiment, intelligent drive controller 502 may also include a swipe condition detection module 5024.

The brushing condition detection module 5024 is configured to detect whether the vehicle satisfies the brushing condition.

If the flashing condition detection module 5024 detects that the vehicle meets the flashing condition, the vehicle diagnosis interface 503 is further configured to receive a connection instruction sent by the diagnostic apparatus device; wherein the connection instruction includes an IP dynamic address of the diagnostic instrument server.

The intelligent driving controller 502 may further include a connection control module 5025.

A connection control module 5025 for controlling the telematics processor 501 to connect with the diagnostic apparatus server by using a connection instruction; wherein the connection instruction includes an IP dynamic address of the diagnostic instrument server.

The telematics processor 501 may also include a connection module 5012, among other things.

The connection module 5012 is configured to connect to the diagnostic apparatus server using an IP dynamic address under the control of the connection control module 5025.

The specific manner in which the various modules perform the operations in relation to the systems of the above embodiments have been described in detail in relation to the embodiments of the method and will not be described in detail herein.

In addition, the embodiment of the application also provides a vehicle, which can comprise the vehicle software flashing system.

Furthermore, the method according to the application may also be implemented as a computer program or computer program product comprising computer program code instructions for performing part or all of the steps of the above-described method of the application.

Or the application may also be embodied as a computer-readable storage medium (or non-transitory machine-readable storage medium or machine-readable storage medium) having stored thereon executable code (or a computer program or computer instruction code) that, when executed by a vehicle software flashing system of a vehicle, causes the vehicle software flashing system to perform some or all of the steps of the above-described method according to the application.

The foregoing description of embodiments of the application has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the improvement of technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method for flashing vehicle software, wherein the vehicle comprises an intelligent driving controller and a telematics processor, wherein the intelligent driving controller is connected with a diagnostic instrument server through the telematics processor, the method comprising:

2. The method of claim 1, wherein the vehicle further comprises a vehicle diagnostic interface through which the intelligent drive controller is connected to a diagnostic instrument device; the downloading of the flash file from the diagnostic instrument server via the telematics processor includes:

3. The method of claim 2, wherein the telematics processor is communicatively coupled to the diagnostic instrument server based on a first network, the intelligent drive controller is communicatively coupled to the telematics processor based on a second network, and the vehicle diagnostic interface is communicatively coupled to the diagnostic instrument device and the intelligent drive controller, respectively, based on a third network, wherein the first network and the second network each have a time delay that is less than a time delay of the third network.

4. A method according to claim 3, wherein the first network is a cellular network, the second network is an ethernet network, and the third network is a controller area network.

5. The method of claim 2, wherein receiving, via the vehicle diagnostic interface, a swipe file download instruction sent by the diagnostic instrument device, comprises:

6. The method of claim 5, wherein after the software flashing of the intelligent drive controller, the method further comprises:

7. The method according to claim 1, wherein the method further comprises:

Detecting whether the vehicle meets a brushing condition;

8. A vehicle software flashing system is characterized by comprising an intelligent driving controller and a remote information processor, wherein the intelligent driving controller is connected with a diagnostic instrument server through the remote information processor,

9. A vehicle comprising the vehicle software flashing system of claim 8.

10. A computer readable storage medium having stored thereon executable code which, when executed by a vehicle software flashing system of a vehicle, causes the vehicle software flashing system to perform the method of any of claims 1-7.