CN117931232A - Vehicle software upgrading method and device, gateway controller and vehicle - Google Patents

Abstract

The application relates to a vehicle software upgrading method and device, a gateway controller and a vehicle, and relates to the technical field of Internet of vehicles. The method comprises the following steps: reporting the software version information of the vehicle to the cloud; the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle; responding to a software upgrading instruction sent by the cloud based on the software version information, and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where a vehicle is located; and upgrading the software of each ECU by adopting a software upgrading package. By adopting the method, the software version information of the vehicle can be reported in real time, and the software of each ECU controller can be updated in time, so that vehicles in different batches can be updated to the latest ECU controller software version, and the gateway controller of the vehicle can directly acquire the software update package from the latest CDN server, thereby improving the efficiency of vehicle software update.

Description

Vehicle software upgrading method and device, gateway controller and vehicle

Technical Field

The application relates to the technical field of Internet of vehicles, in particular to a vehicle software upgrading method and device, a gateway controller and a vehicle.

Background

With the progress of technology and the improvement of living standard of people, intelligent service of automobiles has become an outstanding development direction in the field of automobiles.

At present, software versions of intelligent controllers of automobiles in different batches are inconsistent, and after the automobiles leave the factory, if the software versions of the intelligent controllers need to be updated, or repair and maintenance are carried out on the intelligent controllers, the automobiles need to be started to go to a repair shop for completion, so that part of the automobiles cannot be updated to the latest software version in time, and the latest intelligent service cannot be obtained.

Disclosure of Invention

Based on the above, it is necessary to provide a vehicle software upgrading method and device for timely updating software versions of different intelligent controllers, a gateway controller and a vehicle.

In a first aspect, the present application provides a vehicle software upgrade method, applied to a gateway controller, the method comprising:

reporting the software version information of the vehicle to the cloud; the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle;

Responding to a software upgrading instruction sent by the cloud based on the software version information, and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where a vehicle is located;

And upgrading the software of each ECU by adopting a software upgrading package.

In one embodiment, the software upgrading process for each ECU using a software upgrading package includes:

analyzing the software upgrading package to obtain an extensible markup language (XML) file and a software updating package;

running the XML file to extract the installation strategy file and the software update file of each ECU from the software update package;

and according to the installation strategy file, the software update file of each ECU is subjected to the refreshing processing.

In one embodiment, according to the installation policy file, the software update file of each ECU is subjected to a refreshing process, including:

Analyzing the XML file to obtain a unified diagnosis service UDS instruction set;

and executing the UDS instruction set according to the installation strategy file so as to transmit the software update file of each ECU to each corresponding ECU, and performing the refreshing processing on the software update file transmitted to each ECU.

In one embodiment, the method further comprises:

determining progress data of upgrading the software of each ECU according to the progress information of the refreshing processing of the software updating files transmitted to each ECU;

the progress data is displayed on a display device of the vehicle.

In one embodiment, reporting the software version information of the vehicle to the cloud comprises:

sending a vehicle login instruction to the cloud;

Responding to a version inquiry instruction sent by the cloud based on the vehicle login instruction, inquiring current software version information of the vehicle, and reporting the software version information to the cloud.

In one embodiment, obtaining a software upgrade package from an intranet delivery network CDN server in an area where a vehicle is located includes:

the CDN server of the area where the vehicle is connected through a TBOX of the remote communication terminal;

and downloading the software upgrade package from the CDN server.

In one embodiment, downloading the software upgrade package from the CDN server includes:

acquiring an electric quantity value of a vehicle;

and under the condition that the electric quantity value is larger than the electric quantity threshold value, downloading the software upgrade package from the CDN server.

In a second aspect, the present application further provides a vehicle software upgrade apparatus configured to a gateway controller, the apparatus comprising:

The reporting module is used for reporting the software version information of the vehicle to the cloud; the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle;

the acquisition module is used for responding to a software upgrading instruction sent by the cloud based on the software version information and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where the vehicle is located;

And the upgrading module is used for upgrading the software of each ECU by adopting the software upgrading package.

In a third aspect, the present application also provides a gateway controller comprising a memory storing a computer program and a processor implementing the steps of the method of the first aspect described above when the processor executes the computer program.

In a fourth aspect, the present application also provides a vehicle, which includes the gateway controller of the third aspect.

The vehicle software upgrading method, the vehicle software upgrading device, the gateway controller and the vehicle, wherein the gateway controller reports the software version information of the vehicle to the cloud; the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle; responding to a software upgrading instruction sent by the cloud based on the software version information, and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where a vehicle is located; and upgrading the software of each ECU by adopting a software upgrading package. According to the application, the software version information of the vehicle is reported in real time, and the software of each ECU controller is updated in time, so that vehicles in different batches can be updated to the latest ECU controller software version, and the gateway controller of the vehicle can directly acquire the software upgrading package from the latest CDN server, thereby improving the efficiency of vehicle software upgrading.

Drawings

FIG. 1 is an application scenario diagram of a vehicle software upgrade method in one embodiment;

FIG. 2 is a flow chart of a method of upgrading vehicle software in one embodiment;

FIG. 3 is a flow diagram of a software update file being written in one embodiment;

FIG. 4 is a flowchart of a software update file refreshing process according to another embodiment;

FIG. 5 is a flow chart showing progress data of a vehicle software upgrade in one embodiment;

FIG. 6 is a flow diagram of performing an upgrade task in one embodiment;

FIG. 7 is a flow chart of reporting software version information in one embodiment;

FIG. 8 is a flow diagram of an exemplary task issuing upgrade in an embodiment;

FIG. 9 is a flow chart of downloading a software upgrade package in one embodiment;

FIG. 10 is a flow chart of a method of upgrading vehicle software in another embodiment;

FIG. 11 is a block diagram of a vehicle software upgrade apparatus in one embodiment;

FIG. 12 is a block diagram of a vehicle software upgrade apparatus in another embodiment;

FIG. 13 is a block diagram of a vehicle software upgrade apparatus in yet another embodiment;

fig. 14 is a block diagram showing the construction of a vehicle software upgrading apparatus in still another embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

The vehicle software upgrading method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. The vehicle is provided with a gateway controller 101, and the gateway controller 101 can communicate with the cloud 102 in real time to complete steps of the vehicle software upgrading method. Specifically, the gateway controller 101 reports software version information of the vehicle to the cloud 102, where the software version information includes ECU version information of each ECU (Electronic Control Unit, electronic controller unit) on the vehicle, and when determining that there is software of the ECU to be upgraded on the vehicle based on the software version information, the cloud 102 sends a software upgrading instruction to the gateway controller 101, and correspondingly, the gateway controller 101 responds to the software upgrading instruction, obtains a software upgrading packet from a CDN (Content Delivery Network, intranet distribution network) server 103 in an area where the vehicle is located, and upgrades software of each ECU by adopting the software upgrading packet.

The gateway controller 101 contains a vehicle end component that can be used to download the software upgrade package by connecting to the CDN server 103 through a TBOX (TELEMATICS BOX, telecommunications terminal) on the vehicle.

The data storage system can store data to be processed by the cloud 102, and the data storage system can be integrated on the cloud 102 or placed on other network servers. Cloud 102 may be implemented as a stand-alone server or as a cluster of servers.

When the gateway controllers on a plurality of vehicles are communicated with the cloud end in real time to finish the steps of the vehicle software upgrading method, each gateway controller, the cloud end and each CDN server form a distributed application environment together, so that the vehicle software upgrading in the application environment is realized based on the same version of base line.

In one embodiment, as shown in fig. 2, there is provided a vehicle software upgrade method applied to a gateway controller, including the steps of:

s201, reporting the software version information of the vehicle to the cloud.

The vehicle is provided with a plurality of controllers including a gateway controller and a plurality of ECUs, the gateway controller can be used for managing the software upgrading of each controller on the vehicle, the ECUs are used for controlling the running state of the vehicle and providing different intelligent services for the vehicle, the ECUs comprise various types, such as EMS (ENGINE MANGEMENT SYSTEM, engine management system), TCU (Transmision Control Unit, automatic gearbox control unit) and BCM (Body Control Module, vehicle body control module), and the like, and the type of the ECUs is not limited in the embodiment.

Optionally, under the condition that the vehicle is electrified, the gateway controller reports the software version information of the vehicle to the cloud according to a preset period.

For example, when the vehicle is powered on, the gateway controller reports the software version information of the vehicle to the cloud end once, and further reports the software version information of the vehicle to the cloud end once every 10 minutes, so that the periodic reporting of the software version information of the vehicle is realized.

The software version information is the whole vehicle software version information of the vehicle, and comprises ECU version information of each ECU on the vehicle.

It can be understood that the ECUs set on the vehicles of different batches may not be consistent, and the software versions of the set ECUs may also be inconsistent, so that all the vehicles uniformly report the software version information including the ECU version information to the cloud end, so that the cloud end provides the same version baseline of the vehicle software upgrade for all the vehicles.

S202, responding to a software upgrading instruction sent by the cloud based on the software version information, and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where the vehicle is located.

After receiving the software version information reported by the vehicle, the cloud end analyzes the software version information of the vehicle based on the version base line to determine whether the software of each controller on the vehicle needs to be upgraded, and if the software of the controller needing to be upgraded exists, a software upgrading instruction is sent to a gateway controller of the vehicle so as to send an upgrading task to the vehicle.

Correspondingly, the gateway controller responds to the software upgrading instruction sent by the cloud, determines a CDN server corresponding to the current area of the vehicle, and obtains a corresponding software upgrading packet from the corresponding CDN server.

The CDN server obtains the software upgrading package under the version base line from the cloud in advance, and provides a software upgrading package downloading service for the vehicle in the coverage area. Different areas correspond to different CDN servers, and the CDN servers form a distributed network together, so that vehicles in different areas can acquire a software upgrading packet from the nearest CDN server, the vehicle software upgrading efficiency is improved, and the cloud load is reduced.

Specifically, the gateway controller downloads the software upgrade package from the corresponding CDN server through the vehicle-mounted component therein.

Optionally, the gateway controller responds to the upgrade task issued by the cloud based on the software version information, returns task acceptance information to the cloud, and further responds to a software upgrade instruction for executing the software upgrade sent by the cloud based on the task acceptance information, returns task execution information to the cloud, and returns completion information to end the task issuing process.

S203, adopting a software upgrading package to upgrade the software of each ECU.

Specifically, the gateway controller decrypts, checks and decompresses the software upgrading package through the vehicle-mounted component to obtain sub packages corresponding to the ECUs, and further, the gateway controller completes the step of upgrading the software of each ECU by adopting the sub packages corresponding to the ECUs through interaction with the ECUs. Alternatively, the in-vehicle component may be an OTA (Over the Air Technology, over-the-air technology) component.

For example, the gateway controller provides an external interface function for the OTA component therein, so that the OTA component can send instructions to each ECU through an API (Application Programming Interface ), and the step of upgrading the software of each ECU is completed through instruction interaction.

According to the scheme, the gateway controller reports the software version information of the vehicle to the cloud; the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle; responding to a software upgrading instruction sent by the cloud based on the software version information, and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where a vehicle is located; and upgrading the software of each ECU by adopting a software upgrading package. According to the method and the device for updating the software of the vehicle, the software version information of the vehicle is reported in real time, the software version of each ECU (electronic control unit) on the vehicle is effectively managed, the software of each ECU is timely repaired, vehicles of different batches can be timely updated to the latest ECU software version, the vehicle software updating flow is optimized, the gateway controller of the vehicle can directly acquire the software updating book from the latest CDN server, and the vehicle software updating efficiency can be improved.

In order to optimize the flow of performing the upgrade task at the vehicle end, based on the above embodiment, in one embodiment, as shown in fig. 3, the step S203 includes:

S301, analyzing the software upgrading package to obtain an extensible markup language (XML) file and a software upgrading package.

The encrypted software upgrading package is downloaded from the CDN server, after the encrypted software upgrading package is decrypted, whether the signature carried by the software upgrading package is accurate or not is verified, if yes, the software upgrading package is analyzed, and an XML (Extensible Markup Language extensible markup language) file and the software upgrading package are obtained.

S302, running the XML file to extract the installation strategy file and the software update file of each ECU from the software update package.

And running the XML file in the software upgrading package to extract the installation strategy file and the software updating file from the software upgrading package. The software update file may include a task description file, a list of ECUs to be upgraded, software version information, address information of an ECU update file to be upgraded, a transmission data type, a transmission service, and the like.

The installation strategy file is used for indicating the flow of the updating process of the software of each ECU, the installation strategy file comprises a judging standard for judging whether the updating can be carried out or not, and is used for indicating the updating can be carried out or not, if the installation strategy file indicates that the updating can be carried out only when the electric quantity value of the vehicle is not lower than 50%, and indicates that the updating can be carried out only when the gear of the vehicle is in the P gear, the installation strategy file also comprises the detailed information of the vehicle.

The task description file includes an identification bit of a controller that needs to update software, e.g., the identification bit of the gateway controller is denoted as 1, the identification bit of the tbox controller is denoted as 2, and the identification bit of the ecu controller is denoted as 3. The ECU list to be upgraded includes the adjacency numbers of the ECU controllers that need to update the software. The software version information includes version specifications of version baselines, such as target version 2.0.

S303, according to the installation strategy file, the software update file of each ECU is subjected to the refreshing processing.

And according to the flow of the refreshing processing of the software update files of the ECUs indicated by the installation strategy files, the refreshing processing of the software update files of the ECUs is performed. Specifically, the gateway controller and each ECU complete the refreshing processing of the software update files of each ECU through instruction interaction.

In this embodiment, the software upgrade package is parsed to obtain the XML file and the software upgrade package, and then the XML file is run to extract the installation policy file and the software upgrade file of each ECU from the software upgrade package, and the software upgrade of each ECU is performed by performing the refresh processing on the software upgrade file of each ECU according to the installation policy file, so as to implement the software upgrade of each controller on the vehicle.

In order to implement the process of refreshing the software update file on different vehicles and upgrade the software update file for different ECUs, in one embodiment, as shown in fig. 4, the step S303 includes:

s401, analyzing the XML file to obtain a unified diagnosis service UDS instruction set.

And analyzing the XML file to generate a UDS (Unified Diagnostic Services, unified diagnostic service) instruction set, wherein the UDS instruction set comprises a plurality of UDS instructions, the UDS instructions are diagnostic instructions under a UDS diagnostic protocol, and the software upgrading can be completed according to the steps of executing and refreshing the software updating file of each UDS instruction in the UDS instruction set.

S402, executing a UDS instruction set according to the installation strategy file so as to transmit the software update file of each ECU to each corresponding ECU, and performing the refreshing processing on the software update file transmitted to each ECU.

Specifically, according to the flow of the software update file of each ECU, which is indicated by the installation policy file, the API interface of the gateway controller is sequentially called to send the corresponding UDS instruction in the UDS instruction set to each ECU. Specifically, the gateway controller sends a diagnosis request in the UDS instruction to each ECU through the OTA component, and accordingly, each ECU returns a corresponding diagnosis response.

For example, the diagnostic response returned by the ECU indicates that the software upgrade condition is satisfied, transmits a corresponding software update file to the ECU, and continues to send a diagnostic request in the UDS instruction to instruct the ECU to perform the flashing process using the software update file.

The software update file is adopted for the refreshing processing, namely the software update file is burnt into a specific address section of the internal memory of the ECU chip, so that the ECU can run the software update file.

In this embodiment, the XML file is parsed to obtain the UDS instruction set, and then the UDS instruction set is executed according to the installation policy file, so that the software update file of each ECU is transmitted to each corresponding ECU, and the software update file transmitted to each ECU is subjected to the refreshing processing, so that the software update of each ECU on the vehicle can be automatically implemented.

In order to visually perform a software upgrade of an ECU on a vehicle, in one embodiment, as shown in fig. 5, the method for upgrading a vehicle software further includes:

S501, determining progress data of the update processing of the software of each ECU based on the progress information of the update processing of the software update file transferred to each ECU.

For each ECU, the corresponding process of the ECU is operated to perform the refreshing process on the software update file transmitted to the ECU. Meanwhile, process information corresponding to the ECU is acquired, and progress data of the ECU for refreshing the software update file is determined according to the process information. Wherein the progress data may be used to represent a percentage of progress of the brushing process on the software update file.

S502, displaying progress data on a display device of the vehicle.

The display device of the vehicle may be an on-vehicle device with a display screen, such as a center control screen, a handrail screen, etc., mounted on the vehicle, or may be an off-vehicle device with a display screen, such as a mobile phone, a tablet computer, etc., connected to the vehicle.

And displaying the progress data on the display device in real time, for example, monitoring the corresponding processes of each ECU, calculating the progress data according to the monitored process information, and transmitting the progress data to the display device in real time for display on the display device. Specifically, according to the SOME/IP (Scalable service-Oriented Middleware over IP, IP-based extensible service-oriented middleware) protocol, current progress data is presented to a user as an upgrade progress through an HMI (Human MACHINE INTERFACE, human-machine interface).

In the embodiment, the progress data of the software upgrading of each ECU on the vehicle is displayed on the display device, so that a user can check the condition of the vehicle software upgrading conveniently, a visual man-machine interaction path is provided, and the vehicle software upgrading effect is improved.

As an alternative implementation in this embodiment, the software flashing procedure may be accomplished using the 34 and 36 services of UDS or the 38 services of DOIP (Diagnostic communication over Internet Protocol, IP network based diagnostic communications).

As shown in fig. 6, the software upgrade package is parsed to obtain an XML file, and then the XML file is parsed to generate a UDS instruction set, further, a transmission mode is determined, if the transmission mode is a CAN transmission mode, a transmission task is directly executed, and if the transmission mode is a DOIP transmission mode, a TCP connection is established first, and then the transmission task is executed.

The software refreshing process is completed by adopting 34 and 36 services of the UDS, and comprises the following steps: and placing all the UDS instructions into a UDS instruction set list according to the execution sequence, sequentially executing the UDS instructions in the UDS instruction set list, and ending the software refreshing flow after all the UDS instructions are executed.

The software flashing process is completed by adopting the service DOIP, which comprises the following steps: establishing TCP connection, completing DOIP protocol initialization, sequentially executing UDS instructions to complete software update file transmission, waiting for software update file installation to complete, reading installation progress, further exiting UDS diagnostic flashing, restarting the ECU, and ending the software flashing flow.

Therefore, the OTA component in the gateway controller performs diagnosis interaction with each ECU on the vehicle according to the gateway external interface, so that the software upgrading of each ECU is realized, and the software updating file refreshing can be flexibly performed in at least two modes, and the method is suitable for different ECUs and different diagnosis refreshing flows.

In order to check the software version of each controller on the vehicle in time, upgrade and maintain the software of all controllers on the vehicle, in an embodiment, the vehicle end may periodically report the software version information of the whole vehicle to the cloud end, as shown in fig. 7, and S201 includes:

S701, a vehicle login instruction is sent to the cloud.

Under the condition that the vehicle is electrified, the gateway controller sends a login instruction to the cloud according to a preset period. For example, when the vehicle is powered on, the gateway controller sends a vehicle login instruction to the cloud end once, and then sends the vehicle login instruction to the cloud end once every 10 minutes. The vehicle login instruction is used for prompting that the vehicle is in a power-on state currently, and the vehicle software upgrading method can be executed.

S702, responding to a version inquiry instruction sent by the cloud based on a vehicle login instruction, inquiring current software version information of the vehicle, and reporting the software version information to the cloud.

Correspondingly, after receiving the vehicle login instruction, the cloud end sends a version inquiry instruction to the gateway controller of the vehicle to instruct the gateway controller to inquire the current software version information of all controllers on the vehicle, namely, inquire the current gateway version information of the gateway controller, inquire the current TBOX version information of the TBOX controller and inquire the current ECU version information of each ECU.

Further, the queried current software version information of all controllers on the vehicle is merged and reported to the cloud.

It can be understood that the vehicle-side gateway controller periodically sends a vehicle login instruction, receives a version inquiry instruction fed back by the cloud, and finishes periodically reporting the software version information of the vehicle to the cloud.

On the basis of the present embodiment, an optional task issuing process is provided, as shown in fig. 8, including: the gateway controller of the vehicle end sends a vehicle login instruction to the cloud end based on the OTA component, and then the cloud end sends a version inquiry instruction to the gateway controller of the vehicle end so that the gateway controller of the vehicle end returns the software version information of the whole vehicle, the cloud end sends a vehicle upgrading task after receiving the software version information, and the gateway controller of the vehicle end returns task acceptance information correspondingly. Further, the cloud end issues an upgrade execution instruction, the gateway controller of the vehicle end returns an execution acceptance result of the vehicle upgrade task, and the cloud end replies finish information.

In this embodiment, a vehicle login instruction is sent to the cloud end first, and under the condition that a version inquiry instruction sent by the cloud end based on the vehicle login instruction is received, current software version information of the vehicle is inquired and reported to the cloud end, so that the problem that when the vehicle cannot perform software upgrading, the software version information is reported to the cloud end and a large load pressure is brought to the cloud end can be avoided.

In order to improve the efficiency of vehicle software upgrade and reduce the load pressure of the cloud server, in one embodiment, the latest CDN server may be accessed through the TBOX, and the corresponding software upgrade package may be downloaded from the latest CDN server, as shown in fig. 9, where S202 includes:

S901, connecting a CDN server of an area where the vehicle is located through a remote communication terminal TBOX.

The TBOX integrates a body network and a wireless communication function and is used for providing networking services for vehicles, and the gateway controller accesses the nearest CDN server through the TBOX.

Specifically, the gateway controller sends an acquisition request for the software upgrade package through the TBOX, the acquisition request is directed to the CDN server closest to the gateway controller, and the CDN server closest to the gateway controller responds to the acquisition request for the software upgrade package.

S902, downloading the software upgrade package from the CDN server.

The CDN server responds to the acquisition request for the software upgrade package, determines the corresponding software upgrade package according to the acquisition request, and issues the corresponding software upgrade package for the vehicle.

Optionally, the software upgrade package is downloaded through HTTP (Hypertext Transfer Protocol )/HTTPs (Hypertext Transfer Protocol Secure, hypertext transfer security protocol), and breakpoint continuous transmission and power-off continuous transmission are supported in the downloading process.

Optionally, the CDN server obtains software upgrade packages of different sizes under the version baseline from the cloud in advance, for example, the software upgrade package a includes software upgrade files of two ECUs, and the software upgrade package B includes software upgrade files of three ECUs. The gateway controller carries the software upgrading packet identifier in the acquisition request sent by the TBOX, and the CDN server can analyze the software upgrading packet identifier to obtain the corresponding software upgrading packet.

Further, after the gateway controller downloads the software upgrade package from the CDN server, the downloaded software upgrade package is stored in the gateway memory.

In an alternative embodiment, a power value of the vehicle is obtained; and under the condition that the electric quantity value is larger than the electric quantity threshold value, downloading the software upgrade package from the CDN server.

Downloading the software upgrade package requires that the vehicle have a download condition, i.e., that the electric quantity value Of the vehicle battery SOC (State Of Charge) is greater than a preset electric quantity threshold.

For example, the vehicle is allowed to download the software upgrade package from the CDN server only when the power value is greater than 50%.

Under the condition that the vehicle meets the downloading condition, the gateway controller can automatically download the software upgrade package through the TBOX without manual confirmation.

In this embodiment, the efficiency of acquiring the software upgrade package by the vehicle can be improved by downloading the software upgrade package from the CDN server through the TBOX, so that the efficiency of upgrading the vehicle software is improved as a whole, and the load pressure of the cloud can be relieved to a mobile extent by downloading the software upgrade package from the CDN server instead of acquiring the software upgrade package from the cloud.

In one embodiment, an alternative example of a vehicle software upgrade method is provided, as shown in fig. 10, comprising the steps of:

s1001, a vehicle login instruction is sent to the cloud.

S1002, responding to a version inquiry instruction sent by the cloud based on a vehicle login instruction, inquiring current software version information of a vehicle, and reporting the software version information to the cloud.

Wherein the software version information includes ECU version information of each electronic controller unit ECU on the vehicle.

S1003, responding to a software upgrading instruction sent by the cloud based on the software version information, and connecting a CDN server of an area where the vehicle is located through a TBOX (remote communication terminal).

S1004, downloading the software upgrade package from the CDN server.

Optionally, acquiring an electric quantity value of the vehicle, and downloading the software upgrade package from the CDN server if the electric quantity value is greater than the electric quantity threshold.

S1005, analyzing the software upgrading package to obtain an extensible markup language (XML) file and a software upgrading package.

S1006, running the XML file to extract the installation strategy file and the software update file of each ECU from the software update package.

And S1007, analyzing the XML file to obtain a unified diagnosis service UDS instruction set.

And S1008, executing a UDS instruction set according to the installation strategy file so as to transmit the software update file of each ECU to each corresponding ECU, and performing the refreshing processing on the software update file transmitted to each ECU.

Optionally, determining progress data of upgrading the software of each ECU according to the progress information of the refreshing process of the software update file transmitted to each ECU; the progress data is displayed on a display device of the vehicle.

The specific process of the above steps may refer to the description of the above method embodiments, and its implementation principle and technical effects are similar, and are not repeated herein.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a vehicle software upgrading device for realizing the vehicle software upgrading method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the vehicle software upgrading device provided below may refer to the limitation of the vehicle software upgrading method hereinabove, and will not be repeated here.

In one embodiment, as shown in fig. 11, there is provided a vehicle software upgrade apparatus 1, including a reporting module 10, an acquiring module 20, and an upgrade module 30, wherein:

and the reporting module 10 is used for reporting the software version information of the vehicle to the cloud.

Wherein the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle.

The acquiring module 20 is configured to respond to a software upgrade instruction sent by the cloud based on the software version information, and acquire a software upgrade package from an intranet distribution network CDN server in an area where the vehicle is located.

And the upgrading module 30 is used for upgrading the software of each ECU by adopting the software upgrading package.

In one embodiment, on the basis of fig. 11, as shown in fig. 12, the upgrade module 30 may include:

The parsing unit 31 is configured to parse the software upgrade package to obtain an XML file and a software upgrade package.

An extraction unit 32 for running the XML file to extract the installation policy file and the software update file of each ECU from the software update package.

And a refreshing unit 33 for refreshing the software update file of each ECU according to the installation policy file.

In one embodiment, the above-mentioned brushing unit 33 may include:

and the analysis subunit is used for analyzing the XML file to obtain a unified diagnosis service UDS instruction set.

And the refreshing subunit is used for executing the UDS instruction set according to the installation strategy file so as to transmit the software update file of each ECU to the corresponding ECU and perform refreshing processing on the software update file transmitted to each ECU.

In one embodiment, the vehicle software upgrade apparatus 1 may further include:

and the determining module is used for determining the progress data of the upgrading processing of the software of each ECU according to the progress information of the refreshing processing of the software updating file transmitted to each ECU.

And the display module is used for displaying the progress data on the display equipment of the vehicle.

In one embodiment, on the basis of fig. 11, as shown in fig. 13, the reporting module 10 may include:

And the sending unit 11 is used for sending the vehicle login instruction to the cloud.

And the reporting unit 12 is used for responding to the version inquiry instruction sent by the cloud based on the vehicle login instruction, inquiring the current software version information of the vehicle and reporting the software version information to the cloud.

In one embodiment, on the basis of fig. 11, as shown in fig. 14, the acquiring module 20 may include:

A connection unit 21 for connecting the CDN server of the area where the vehicle is located through a remote communication terminal TBOX.

And a downloading unit 22, configured to download the software upgrade package from the CDN server.

In one embodiment, the downloading unit 22 may include:

and the acquisition subunit is used for acquiring the electric quantity value of the vehicle.

And the downloading subunit is used for downloading the software upgrade package from the CDN server under the condition that the electric quantity value is larger than the electric quantity threshold value.

The respective modules in the above-described vehicle software upgrade apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a gateway controller is provided that includes a processor, a memory, and a communication interface connected by a system bus. Wherein the processor of the gateway controller is configured to provide computing and control capabilities. The memory of the gateway controller comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the gateway controller is used for carrying out wired or wireless communication with other controllers on the vehicle, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a vehicle software upgrade method.

In one embodiment, a vehicle is provided with a gateway controller configured to implement the steps of the vehicle software upgrade method described above.

In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, implements the steps of the vehicle software upgrade method described above.

In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, implements the steps of the vehicle software upgrade method described above.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims (10)

1. A method of upgrading vehicle software for a gateway controller, the method comprising:

reporting the software version information of the vehicle to the cloud; wherein the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle;

responding to a software upgrading instruction sent by the cloud based on the software version information, and acquiring a software upgrading packet from an intranet distribution network CDN server of an area where the vehicle is located;

and upgrading the software of each ECU by adopting the software upgrading package.

2. The method according to claim 1, wherein the step of performing an upgrade process on the software of each ECU using the software upgrade package includes:

analyzing the software upgrading package to obtain an extensible markup language (XML) file and a software updating package;

running an XML file to extract an installation strategy file and a software update file of each ECU from the software update package;

And according to the installation strategy file, the software update file of each ECU is subjected to the refreshing processing.

3. The method according to claim 2, wherein the performing a brushing process on the software update file of each ECU according to the installation policy file includes:

analyzing the XML file to obtain a unified diagnosis service UDS instruction set;

And executing a UDS instruction set according to the installation strategy file so as to transmit the software update file of each ECU to each corresponding ECU, and performing the refreshing processing on the software update file transmitted to each ECU.

4. A method according to claim 3, characterized in that the method further comprises:

determining progress data of upgrading the software of each ECU according to the progress information of the refreshing processing of the software updating files transmitted to each ECU;

The progress data is displayed on a display device of the vehicle.

5. The method of claim 1, wherein the reporting the software version information of the vehicle to the cloud comprises:

sending a vehicle login instruction to the cloud;

Responding to a version inquiry instruction sent by the cloud based on the vehicle login instruction, inquiring current software version information of the vehicle, and reporting the software version information to the cloud.

6. The method of claim 1, wherein the obtaining the software upgrade package from the CDN server of the intranet in the area where the vehicle is located comprises:

Connecting a CDN server of the area where the vehicle is located through a TBOX (tunnel boring oxide) of a remote communication terminal;

and downloading a software upgrade package from the CDN server.

7. The method of claim 6, wherein the downloading of the software upgrade package from the CDN server comprises:

Acquiring an electric quantity value of the vehicle;

and downloading a software upgrade package from the CDN server under the condition that the electric quantity value is larger than the electric quantity threshold value.

8. A vehicle software upgrade apparatus configured in a gateway controller, the apparatus comprising:

the reporting module is used for reporting the software version information of the vehicle to the cloud; wherein the software version information comprises ECU version information of each electronic controller unit ECU on the vehicle;

The acquisition module is used for responding to a software upgrading instruction sent by the cloud based on the software version information and acquiring a software upgrading packet from an intranet distribution network CDN server of the area where the vehicle is located;

And the upgrading module is used for upgrading the software of each ECU by adopting the software upgrading package.

9. A gateway controller comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1-7 when executing the computer program.

10. A vehicle comprising the gateway controller of claim 9.