CN113535207B - Vehicle and updating method of vehicle-mounted software thereof and mobile terminal - Google Patents

Vehicle and updating method of vehicle-mounted software thereof and mobile terminal Download PDF

Info

Publication number
CN113535207B
CN113535207B CN202110844120.XA CN202110844120A CN113535207B CN 113535207 B CN113535207 B CN 113535207B CN 202110844120 A CN202110844120 A CN 202110844120A CN 113535207 B CN113535207 B CN 113535207B
Authority
CN
China
Prior art keywords
vehicle
mobile terminal
update
installation package
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110844120.XA
Other languages
Chinese (zh)
Other versions
CN113535207A (en
Inventor
姚巧丽
杨鹏
陈鹏
王树利
王本强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hisense Visual Technology Co Ltd
Original Assignee
Hisense Group Holding Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hisense Group Holding Co Ltd filed Critical Hisense Group Holding Co Ltd
Priority to CN202110844120.XA priority Critical patent/CN113535207B/en
Publication of CN113535207A publication Critical patent/CN113535207A/en
Application granted granted Critical
Publication of CN113535207B publication Critical patent/CN113535207B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a vehicle, an updating method of vehicle-mounted software of the vehicle and a mobile terminal, and relates to the technical field of vehicles. The mobile terminal can receive the update installation package of the vehicle-mounted software sent by the server through the first communication connection, and can send the update installation package to the target vehicle through the second communication connection, so that the target vehicle can update the vehicle-mounted software installed in the target vehicle based on the update installation package. Therefore, the vehicle software updating mode is enriched, and the flexibility of vehicle software updating is improved. In addition, in the application, the update installation package of the vehicle-mounted software sent by the mobile terminal is received by the target vehicle through the second communication connection, so that the flow charge is not generated, and the cost of updating the vehicle-mounted software of the target vehicle is effectively reduced.

Description

Vehicle and updating method of vehicle-mounted software thereof and mobile terminal
Technical Field
The application relates to the technical field of vehicles, in particular to a vehicle, an updating method of vehicle-mounted software of the vehicle and a mobile terminal.
Background
The vehicle-mounted software can be installed in the vehicle, and the vehicle can update the vehicle-mounted software so that the updated vehicle-mounted software meets the requirements of users.
In the related art, the vehicle may send an update request to a background server of the in-vehicle software. The backend server may send an update installation package of the in-vehicle software to the vehicle in response to the update request. After the vehicle receives the update installation package, the vehicle-mounted software installed in the vehicle can be updated based on the update installation package.
However, in the related art, the vehicle has a single mode of updating the on-board software.
Disclosure of Invention
The application provides a vehicle, an updating method of vehicle-mounted software thereof and a mobile terminal, which can solve the problem that the vehicle-mounted software updating mode of the vehicle in the related technology is single. The technical scheme is as follows:
in one aspect, a method for updating vehicle-mounted software of a vehicle is provided and is applied to a mobile terminal; the method comprises the following steps:
transmitting an update request of vehicle-mounted software of the target vehicle to the server through a first communication connection with the server;
receiving an update installation package of the vehicle-mounted software sent by the server in response to the update request;
and sending the update installation package to the target vehicle through a second communication connection with the target vehicle, wherein the update installation package is used for the target vehicle to update the vehicle-mounted software.
On the other hand, the updating method of the vehicle-mounted software of the vehicle is provided and is applied to the vehicle; the method comprises the following steps:
receiving an update installation package of vehicle-mounted software sent by a mobile terminal through second communication connection with the mobile terminal, wherein the update installation package is received by the mobile terminal through first communication connection with a server;
and updating the vehicle-mounted software based on the update installation package.
In yet another aspect, a mobile terminal is provided that includes a processor; the processor is configured to:
transmitting an update request of vehicle-mounted software of the target vehicle to the server through a first communication connection with the server;
receiving an update installation package of the vehicle-mounted software sent by the server in response to the update request;
and sending the update installation package to the target vehicle through a second communication connection with the target vehicle, wherein the update installation package is used for the target vehicle to update the vehicle-mounted software.
Optionally, the first communication connection is a mobile communication connection or a wireless fidelity connection;
the second communication connection is a wired connection, a Bluetooth connection or a wireless local area network connection.
Optionally, the processor is configured to:
and periodically sending an update request of the vehicle-mounted software of the target vehicle to the server.
Optionally, the server records a version number of the vehicle-mounted software installed in the target vehicle; the processor is further configured to:
receiving a first update completion instruction sent by the target vehicle;
and responding to the first updating completion instruction, and sending a second updating completion instruction to the server, wherein the second updating completion instruction is used for indicating the server to update the recorded version number of the vehicle-mounted software installed in the target vehicle to the version number of the updating installation package.
In yet another aspect, a vehicle is provided that includes a processor; the processor is configured to:
receiving an update installation package of vehicle-mounted software sent by a mobile terminal through second communication connection with the mobile terminal, wherein the update installation package is received by the mobile terminal through first communication connection with a server;
and updating the vehicle-mounted software based on the update installation package.
Optionally, the processor is configured to: if the update installation package passes the version verification, updating the vehicle-mounted software based on the update installation package;
The processor is further configured to:
if the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software are smaller than or equal to a first threshold value, sending first prompt information to the mobile terminal, wherein the first prompt information is used for indicating the mobile terminal to resend the update installation package of the vehicle-mounted software;
if the update installation package fails the version verification, the accumulated verification times are greater than the first threshold and smaller than or equal to a second threshold, second prompt information is sent to the mobile terminal, the second prompt information is used for indicating the mobile terminal to send an update request for the vehicle-mounted software to the server again, and the second threshold is greater than the first threshold;
if the update installation package fails the version verification and the accumulated verification times are greater than the second threshold, third prompt information is sent to the mobile terminal, wherein the third prompt information is used for indicating that the vehicle-mounted software update fails;
the accumulated verification times are the total times of performing version verification on the update installation package of the vehicle-mounted software after the vehicle-mounted software is updated last time.
In still another aspect, there is provided a mobile terminal including: the mobile terminal comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the updating method of the vehicle-mounted software applied to the mobile terminal when executing the computer program.
In yet another aspect, a vehicle is provided, the vehicle comprising: the system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the updating method of the vehicle-mounted software applied to the vehicle when executing the computer program.
In yet another aspect, a computer readable storage medium is provided, in which a computer program is stored, the computer program being loaded and executed by a processor to implement the method for updating vehicle software as described in the above aspect.
In yet another aspect, a computer program product is provided comprising instructions which, when run on the computer, cause the computer to perform the method of updating vehicle software of the above aspect.
In yet another aspect, there is provided an update system of on-board software of a vehicle, the system comprising:
the mobile terminal as described in the above aspect, and the vehicle as described in the above aspect.
The technical scheme provided by the application has the beneficial effects that at least:
the application provides a vehicle, an updating method of vehicle-mounted software of the vehicle and a mobile terminal. Therefore, the vehicle software updating mode is enriched, and the flexibility of vehicle software updating is improved.
In addition, in the application, the update installation package of the vehicle-mounted software sent by the mobile terminal is received by the target vehicle through the second communication connection, so that the flow charge is not generated, and the cost of updating the vehicle-mounted software of the target vehicle is effectively reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of an update system of vehicle-mounted software according to an embodiment of the present application;
FIG. 2 is a flowchart of an update of vehicle software provided by an embodiment of the present application;
FIG. 3 is a flow chart of another update of the in-vehicle software provided by an embodiment of the present application;
FIG. 4 is a schematic illustration of a configuration interface for a vehicle provided by an embodiment of the present application;
FIG. 5 is a schematic diagram of a vehicle display prompt box according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;
fig. 7 is a software architecture block diagram of a mobile terminal according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a vehicle according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
Fig. 1 is a schematic structural diagram of an update system of vehicle software according to an embodiment of the present application. Referring to fig. 1, the system may include: mobile terminal 110, vehicle 120, and server 130.
Wherein, the mobile terminal 110 establishes a first communication connection with the server 130, and the mobile terminal 110 also establishes a second communication connection with the vehicle 120. The second communication connection is different from the first communication connection, and no traffic tariffs are generated when the mobile terminal 110 and the vehicle 120 interact data through the second communication connection. The traffic tariff refers to the cost incurred by the interaction of data over the mobile communication connection.
The vehicle 120 may be an intelligent vehicle such as a car, a bus or a van, etc. that is equipped with on-board software, which may be system software or application software. The server 130 may be a background server of the in-vehicle software.
The mobile terminal 110 may be a mobile phone, a tablet, a notebook, a desktop, etc. For example, referring to fig. 1, the mobile terminal may be a mobile phone. The server 130 may be a firmware over-the-air (FOTA) server, which may be a server, or may be a server cluster formed by several servers, or may be a cloud computing service center.
Fig. 2 is a flowchart of a method for updating vehicle software according to an embodiment of the present application, where the method may be applied to a system for updating vehicle software, for example, the system shown in fig. 1. Referring to fig. 2, the method includes:
step 101, the mobile terminal sends an update request of the vehicle-mounted software of the target vehicle to the server through a first communication connection with the server.
The in-vehicle software may be system software or application software, for example, the in-vehicle software may be system software. The system software may refer to: and supporting the development and running of application software, and integrating various programs without user intervention. The first communication connection may be a mobile communication connection or a wireless fidelity (wireless fidelity, wi-Fi) connection.
Step 102, the server responds to the update request and sends an update installation package of the vehicle-mounted software to the mobile terminal through the first communication connection.
After receiving the update request sent by the target vehicle, the server may send an update installation package of the vehicle-mounted software to the mobile terminal through a first communication connection with the mobile terminal in response to the update request.
It will be appreciated that receiving the update package by the mobile terminal over the Wi-Fi connection does not generate traffic costs, and that the mobile terminal exchanges data with the server over the mobile communication connection generates less traffic costs than the target vehicle. Based on the analysis, the mobile terminal receives the update installation package through the first communication connection to generate less traffic charge or generate no traffic charge, so that the cost of updating the vehicle-mounted software by adopting the method provided by the embodiment of the application is lower.
Step 103, the mobile terminal sends the update installation package to the target vehicle through a second communication connection with the target vehicle.
Wherein the second communication connection may be a wired connection (e.g. via a data line connection), a bluetooth connection or a wireless local area network (wireless local area networks, WLAN) connection. And no traffic tariffs are generated by the interaction of data over the second communication connection.
Because the target vehicle does not generate flow charge in the process of receiving the update installation package of the vehicle-mounted software sent by the mobile terminal through the second communication connection, the cost of updating the vehicle-mounted software of the target vehicle can be effectively reduced.
Step 104, the target vehicle updates the vehicle-mounted software installed in the update installation package.
After receiving the update installation package, the target vehicle can update the vehicle-mounted software installed in the update installation package based on the update installation package.
In summary, the embodiment of the application provides a method for updating vehicle-mounted software, in which a mobile terminal may receive an update installation package of vehicle-mounted software sent by a server through a first communication connection, and may send the update installation package to a target vehicle through a second communication connection, so that the target vehicle updates the vehicle-mounted software installed in the target vehicle based on the update installation package. Therefore, the vehicle software updating mode is enriched, and the flexibility of vehicle software updating is improved.
In addition, in the embodiment of the application, the target vehicle receives the update installation package of the vehicle-mounted software sent by the mobile terminal through the second communication connection, so that the flow rate fee is not generated, and the cost of updating the vehicle-mounted software of the target vehicle is effectively reduced.
Fig. 3 is a flowchart of another method for updating vehicle software according to an embodiment of the present application, where the method may be applied to a system for updating vehicle software, for example, the system shown in fig. 1. Referring to fig. 3, the method may include:
step 201, the mobile terminal sends an update request of the vehicle-mounted software of the target vehicle to the server through a first communication connection with the server.
The in-vehicle software may be system software or application software, for example, the in-vehicle software may be system software. The first communication connection may be a mobile communication connection or a Wi-Fi connection.
In a first alternative implementation manner, after the mobile terminal is started, an update request for the vehicle-mounted software of the target vehicle may be sent to the server. The update request may include an identification of the target vehicle. The identification of the target vehicle may include: the vehicle identification code (vehicle identification number, VIN) of the target vehicle may also be referred to as a frame number. Optionally, the identification of the target vehicle may further include: a license plate number of the target vehicle and a user identification of an owner of the target vehicle. The user identification may be a mobile phone number of the vehicle owner.
In the embodiment of the application, the mobile terminal is provided with the vehicle management application, and after the mobile terminal runs the vehicle management application, the mobile terminal can send the update request to the server. It should be noted that, the identifier of the target vehicle may be obtained by the mobile terminal in response to the operation of inputting the identifier of the target vehicle in the vehicle binding interface of the vehicle management application after the vehicle management application is downloaded and installed for the first time.
In this implementation, the mobile terminal may periodically send an update request for the on-board software of the target vehicle to the server through the first communication connection with the server.
If the first communication connection is a mobile communication connection, that is, if the mobile terminal communicates with the server through the cellular network, the period for transmitting the update request to the server by the mobile terminal may be set to be longer, for example, may be 3 days, because the energy consumption for communication through the mobile communication connection is higher than that for communication through the Wi-Fi connection. That is, if the mobile terminal communicates with the mobile terminal through the cellular network, the mobile terminal may transmit an update request for the in-vehicle software of the target vehicle to the server every 3 days. Therefore, the power consumption of the mobile terminal can be reduced on the premise of ensuring the updating timeliness of the vehicle-mounted software.
If the first communication connection is a Wi-Fi connection, the period for the mobile terminal to send the update request to the server may be set to be short, for example, 5 hours (h), because the power consumption for communication via the Wi-Fi connection is lower than the power consumption for communication via the mobile communication connection. Therefore, the updating timeliness of the vehicle-mounted software can be effectively ensured under the condition of lower communication cost.
Or if the first communication connection is Wi-Fi connection, the mobile terminal can send an update request of the vehicle software of the target vehicle to the server after detecting that the signal strength of the Wi-Fi signal of the mobile terminal changes.
In a second alternative implementation, the mobile terminal has recorded therein the current version number of the in-vehicle software installed in the target vehicle. The server may send the latest version number of the on-board software of the target vehicle to the mobile terminal. And if the mobile terminal determines that the current version number is different from the latest version number, namely, the version of the vehicle-mounted software is updated, an update request of the vehicle-mounted software of the target vehicle can be sent to the server.
The current version number recorded in the mobile terminal may be transmitted to the mobile terminal by the target vehicle in response to a first version number acquisition request transmitted by the mobile terminal. For example, the target vehicle may include a Telematics Box (T-Box), which may also be referred to as a Telematics processor. The T-Box may receive a first version number acquisition request sent by the mobile terminal. Then, the T-Box may acquire a current version number of the on-vehicle software installed in the target vehicle and transmit the current version number to the mobile terminal.
By way of example, assume that the current version number of the in-vehicle software installed in the target vehicle: 4.6.12c, then referring to fig. 4, after obtaining the current version number through the T-Box, the mobile terminal may display the current version number 01 in a configuration interface of the vehicle management application.
As shown in fig. 4, the configuration interface also displays a program setting control 02, description information 02a of the program setting control 02, notification message control 03, description information 03a of the notification message control, vehicle viewing control 04, and description information 04a of the vehicle viewing control 04.
As can be seen from fig. 4, the description information 02a may be text: clicking can view the program details. The description information 03a may be text: clicking can look up the pending notification. The description information 04a may be text: clicking can view the information of the managed vehicles.
In a third alternative implementation, after determining that the current version of the vehicle-mounted software is different from the latest version, the server may send an update signal to the mobile terminal, where the update signal indicates that the version of the vehicle-mounted software is updated. After receiving the update signal, the mobile terminal may send an update request for the in-vehicle software of the target vehicle to the server.
For example, the server has recorded therein the current version number of the in-vehicle software installed in the target vehicle. If the server determines that the current version number is different from the version number of the latest version, it may be determined that the current version of the vehicle-mounted software is different from the latest version.
The current version number of the vehicle-mounted software recorded in the server may be stored in the server in advance. Alternatively, the current version number of the in-vehicle software recorded in the server may be transmitted to the server by the target vehicle in response to the second version number acquisition request transmitted by the server.
In addition, in this implementation, the server may also send the mobile terminal a main modification point of the latest version of the vehicle software compared to the current version. Correspondingly, after receiving the main modification point, the mobile terminal can display the main modification point for the user to view. Therefore, the user experience is effectively improved.
It can be appreciated that in the foregoing second and third implementations, after determining that the version of the vehicle-mounted software is updated, the mobile terminal may send a prompt message for prompting that the version of the vehicle-mounted software is updated, and update the control. And then, if the mobile terminal receives the touch operation of the user on the update control, the mobile terminal can send an update request of the vehicle-mounted software of the target vehicle to the server.
Alternatively, the mobile terminal may play the prompt message through a speaker. Or the mobile terminal can display the prompt information through a display screen. The embodiments of the present application are not limited in this regard.
Step 202, the server responds to the update request and sends an update installation package of the vehicle-mounted software to the mobile terminal through the first communication connection.
After receiving the update request sent by the target vehicle, the server may send an update installation package of the vehicle-mounted software to the mobile terminal through a first communication connection with the mobile terminal in response to the update request.
Because the mobile terminal receives the update installation package through the Wi-Fi connection and does not generate flow charge, and the flow charge generated by the mobile terminal through the interaction data of the mobile terminal and the server is less than that of the target vehicle, the flow charge generated by the mobile terminal receiving the update installation package through the first communication connection is less, or the flow charge is not generated, and therefore the cost of updating the vehicle-mounted software by adopting the method provided by the embodiment of the application is lower.
For the above-mentioned update request, the mobile terminal receives the update signal sent by the server, or the mobile terminal determines that the vehicle-mounted software of the target vehicle has a scene of being sent after being updated based on the latest version number of the vehicle-mounted software sent by the server, and after receiving the update request, the server can send an update installation package of the vehicle-mounted software to the mobile terminal directly through a first communication connection with the mobile terminal.
For the scenario that the update request carries the identifier of the target vehicle, after receiving the update request, the server may determine the current version number corresponding to the identifier of the target vehicle based on the correspondence between the identifier and the version number. And if the server detects that the current version number is the same as the version number of the latest version, that is, the version of the vehicle-mounted software is not updated, a prompt signal for indicating that the version is not updated can be sent to the mobile terminal through the first communication connection. If the server detects that the current version number is different from the version number of the latest version of the vehicle-mounted software, that is, the version of the vehicle-mounted software is updated, the update installation package of the vehicle-mounted software can be directly sent to the mobile terminal through the first communication connection. The version of the update package is the latest version.
Or if the server determines that the version of the vehicle-mounted software is updated, the update information can be sent to the mobile terminal for display by the mobile terminal. The update information may include: the latest version of the in-vehicle software is compared to the main modification point of the current version. And if the server receives a confirmation update instruction sent by the mobile terminal, the server sends an update installation package of the vehicle-mounted software to the mobile terminal through a first communication connection with the mobile terminal.
For example, referring to fig. 5, after receiving the update information sent by the server, the mobile terminal may display a prompt box 05. As shown in fig. 5, the prompt box includes a modification point 051, a confirmation control 052, and a cancel control 053. Wherein, the modification point 051 may be text: 1. some of the known problems of the previous version are remedied; 2. some experience is optimized.
If the mobile terminal receives the touch operation of the user on the cancel control 053, that is, the user determines that the vehicle-mounted software does not need to be updated, the mobile terminal can send an update cancel instruction to the server to instruct the server to finish the operation, and the subsequent procedure does not need to be executed. If the mobile terminal receives the touch operation of the user for the confirmation control 053, the mobile terminal can send a confirmation update instruction to the server. Accordingly, the server may send an update installation package of the vehicle-mounted software to the mobile terminal through the first communication connection in response to the confirmation update instruction.
Step 203, the mobile terminal sends an update installation package of the vehicle-mounted software to the target vehicle through a second communication connection with the target vehicle.
The second communication connection may be a wired connection (e.g., via a data line connection), a bluetooth connection, or a WLAN connection. And the mobile terminal and the server interact data through the second communication connection without generating flow tariffs.
Because the target vehicle does not generate flow charge in the process of receiving the update installation package of the vehicle-mounted software sent by the mobile terminal through the second communication connection, the cost of updating the vehicle-mounted software of the target vehicle can be effectively reduced.
Alternatively, the update package may be a Binary (BIN) file, i.e., a BIN file. Alternatively, the update package may be an IMG file, which is a file compression format.
In the embodiment of the application, for the scenario that the second communication connection is WLAN connection, both the WLAN hot spot of the mobile terminal and the WLAN hot spot of the target vehicle are in an on state. When the distance between the mobile terminal and the target vehicle is smaller than the distance threshold (for example, the mobile terminal is located in the target vehicle), the mobile terminal may be connected to the WLAN hotspot of the target vehicle, or the target vehicle may be connected to the WLAN hotspot of the mobile terminal, so that the mobile terminal and the target vehicle are located in the same WLAN, and then the second communication connection may be established.
Step 204, the target vehicle detects whether the update package passes the version verification.
After receiving and storing the update installation package sent by the mobile terminal, the target vehicle can carry out version verification on the update installation package stored locally to the target vehicle, and detect whether the update installation package passes the version verification. If the target vehicle determines that the update package passes the version verification, i.e., the version verification is successful, step 205 may be performed. If the target vehicle determines that the update package fails the version check, i.e., the version check fails, step 209 may be performed.
For example, the target vehicle may process the version file (i.e., the update installation package described above) using a preset algorithm to obtain a first hash value, and compare the first hash value with a second hash value in the update installation package. If the target vehicle determines that the first hash value is the same as the second hash value, then it may be determined that the update installation package passes the version check, and then step 205 may be performed. If the target vehicle determines that the first hash value is different from the second hash value, it may be determined that the update installation package fails the version check, and then step 209 may be performed.
Step 205, the target vehicle updates the vehicle-mounted software installed in the target vehicle based on the update installation package.
If the target vehicle determines that the update installation package of the vehicle-mounted software passes the version verification, the vehicle-mounted software installed in the target vehicle may be updated based on the update installation package, that is, the version of the updated vehicle-mounted software is updated from the current version to the latest version.
The target vehicle can carry out version verification on the update installation package before updating the vehicle-mounted software, and the vehicle-mounted software installed in the target vehicle is updated based on the update installation package after the update installation package passes the version verification, so that the reliability of vehicle-mounted software updating is ensured.
Step 206, the target vehicle sends a first update completion instruction to the mobile terminal through the second communication connection.
After the target vehicle completes the update of the vehicle-mounted software based on the update installation package, a first update completion instruction can be sent to the mobile terminal.
Optionally, the target vehicle may delete the received update installation package from the mobile terminal after the update of the vehicle software is completed. In this way, waste of storage resources of the target vehicle can be avoided.
Step 207, the mobile terminal responds to the first update completion instruction and sends a second update completion instruction to the server.
After receiving the first update completion instruction sent by the target vehicle, the mobile terminal may send a second update completion instruction to the server through a first communication connection with the server in response to the first update completion instruction.
And, the mobile terminal may further delete the received update installation package from the server in response to the first update completion instruction. In this way, waste of memory resources of the mobile terminal can be avoided.
And step 208, the server responds to the second updating completion instruction, and updates the recorded version number of the vehicle-mounted software installed in the target vehicle to the version number of the updating installation package.
After receiving the second update completion instruction sent by the mobile terminal, the server can respond to the second update completion instruction to update the recorded version number of the vehicle-mounted software installed in the target vehicle to the version number of the update installation package. I.e. the server may update the current version number of the record to the latest version number.
And the server can also record the updated state as successful update. Thus, the version updating of the vehicle-mounted software is completed.
Step 209, the target vehicle detects whether the accumulated verification number of the update installation package of the in-vehicle software is less than or equal to a first threshold value.
In the embodiment of the application, if the update installation package of the vehicle-mounted software fails the version verification, the mobile terminal may cause the abnormality of the update installation package received by the target vehicle due to the abnormality of the second communication connection in the process of sending the update installation package to the target vehicle; or, the server may send the update installation package to the mobile terminal, which is caused by the abnormal first communication connection in the process of sending the update installation package to the mobile terminal; or may be a server stored update installation package exception.
At this time, the target vehicle may first re-request the update installation package of the vehicle-mounted software from the mobile terminal, and if the target vehicle determines that the re-received update installation package still fails the version verification, the operation of re-requesting the update installation package of the vehicle-mounted software from the mobile terminal may be performed again until the accumulated verification number of the update installation package is equal to the first threshold value. Then if the re-received update installation package still fails the version verification, the target vehicle may determine that the update installation package is abnormal and not due to the second communication connection. Wherein, the accumulated check number of the update installation package may refer to: and after the vehicle-mounted software is updated last time, carrying out version verification on the update installation package of the vehicle-mounted software.
Thereafter, the target vehicle may instruct the mobile terminal to request an update installation package of the in-vehicle software from the server. If the target vehicle determines that the re-received update package fails the version verification, the operation of instructing the mobile terminal to request the update package of the vehicle-mounted software from the server may be performed again until the accumulated verification number reaches a second threshold. If the update package has not passed the version verification, the target vehicle may determine that the update package is abnormal not due to the first communication connection, but rather that the update package stored by the server is abnormal.
Based on the above description, in the embodiment of the present application, if the target vehicle determines that the update installation package fails the version check, that is, the version check fails, it may be detected whether the cumulative check number of times of the update installation package is less than or equal to the first threshold value. If the target vehicle determines that the cumulative check number is less than or equal to the first threshold, it cannot be determined whether the update installation package fails the version check due to the second communication connection at this time, so step 210 may be performed to determine whether the update installation package fails the version check due to the second communication connection. If the target vehicle determines that the cumulative check number is greater than the first threshold, then the target vehicle may determine that the update package fails the version check at this time, not due to the second communication connection, and may therefore perform step 211.
In the embodiment of the application, after the target vehicle determines that the update installation package fails the version verification, the update installation package stored locally can be deleted.
Step 210, the target vehicle sends first prompt information to the mobile terminal through the second communication connection.
If the target vehicle determines that the accumulated verification number of the update installation package is smaller than or equal to the first threshold value, the target vehicle can send first prompt information to the mobile terminal through second communication connection with the mobile terminal. After receiving the first prompt information, the mobile terminal can send the update installation package of the vehicle-mounted software to the target vehicle again. I.e. the target vehicle may request retransmission of the update installation package of the in-vehicle software to the mobile terminal.
Thereafter, if the target vehicle receives the update installation package retransmitted by the mobile terminal, step 204 may be performed again, i.e., it may be detected again whether the update installation package passes the version check.
Step 211, the target vehicle detects whether the accumulated verification number of the update installation package is less than or equal to a second threshold.
If the target vehicle determines that the accumulated verification number of the update installation package is greater than the first threshold, then the target vehicle may determine that the update installation package fails the version verification not due to the second communication connection, and may therefore detect whether the accumulated verification number is less than or equal to the second threshold. If the target vehicle determines that the accumulated number of checks of the update package is less than or equal to the second threshold, then the target vehicle cannot determine whether the update package fails the version check due to the first communication connection, and thus step 213 may be performed to determine whether the update package fails the version check due to the first communication connection. If the target vehicle determines that the number of checks of the update package is greater than the second threshold, then the target vehicle may determine that the update package fails the version check, not due to the first communication connection, and may therefore execute step 214.
Wherein the second threshold is greater than the first threshold, e.g., the second threshold is 2 and the second threshold is 1. Alternatively, the second threshold is 5 and the first threshold is 3.
Step 212, the target vehicle sends second prompt information to the mobile terminal through second communication connection.
If the target vehicle determines that the accumulated verification number of the updated installation package is smaller than or equal to a second threshold value, a second prompt message can be sent to the mobile terminal through a second communication connection with the mobile terminal. After receiving the second prompt message, the mobile terminal can send an update request for the vehicle-mounted software to the server again. I.e. the target vehicle may request the mobile terminal to re-request the update installation package of the in-vehicle software from the server at this time.
Thereafter, if the target vehicle receives the update installation packet retransmitted by the mobile terminal, step 204 may be performed again, i.e., it may be detected again whether the update installation packet passes the version check.
Optionally, after receiving the second prompt message, the mobile terminal may further delete the update package received from the server last time.
And 213, the target vehicle sends a third prompt message to the mobile terminal through the second communication connection.
If the target vehicle determines that the accumulated verification number of the update installation package is greater than the second threshold, it may be determined that the update installation package stored by the server is abnormal due to the failure of the version verification with the new installation package, and therefore third prompt information is sent to the mobile terminal through the second communication connection. The third prompt message is used for indicating that the vehicle-mounted software update fails.
After receiving the third prompt message, the mobile terminal can delete the locally stored update installation package and forward the third prompt message to the server. After receiving the third prompt information, the server can record the update state as update failure and keep the recorded current version number of the vehicle-mounted software unchanged.
In the related art, a mobile communication module is configured in a vehicle, and accordingly, the vehicle can send an update request to a background server of vehicle-mounted software through mobile communication connection, and receive an update installation package sent by the background server. However, since the traffic fee of the vehicle for data interaction through the mobile communication connection is higher than that of the mobile terminal, in the related art, the vehicle directly requests the update installation package from the acquired server, and receives the update installation package to generate more traffic fee, thereby resulting in higher update cost of the vehicle software.
In the method provided by the embodiment of the application, the mobile terminal can receive the update installation package of the vehicle-mounted software sent by the server through the first communication connection. Then, the mobile terminal can send the update installation package to the target vehicle through the second communication connection so as to enable the vehicle to update the vehicle-mounted software installed therein. The first communication connection may be a Wi-Fi connection or a mobile communication connection, the second communication connection may be a wired connection, a bluetooth connection or a wireless local area network connection, and no traffic tariffs may be generated by exchanging data through the second communication connection. Because the Wi-Fi connection does not consume traffic (namely traffic charge is not generated), and the traffic charge of the mobile terminal for exchanging data through the mobile communication connection is less than that of a vehicle, the method provided by the embodiment of the application can effectively reduce the updating cost of vehicle-mounted software.
It should be noted that, the sequence of the steps of the update method of the vehicle-mounted software provided by the embodiment of the application can be properly adjusted, and the steps can be correspondingly increased or decreased according to the situation. For example, step 204, and steps 209 to 211 may be deleted according to circumstances, that is, the target vehicle may update the vehicle-mounted software directly based on the update installation package after receiving the update installation package. Alternatively, steps 206 to 208 may be deleted as appropriate. Alternatively, step 209, and steps 211 to 213 may be deleted as appropriate. Still alternatively, steps 209 to 212 may be deleted as appropriate. Any method that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered in the protection scope of the present application, and thus will not be repeated.
In summary, the embodiment of the application provides a method for updating vehicle-mounted software, in which a mobile terminal may receive an update installation package of vehicle-mounted software sent by a server through a first communication connection, and may send the update installation package to a target vehicle through a second communication connection, so that the target vehicle updates the vehicle-mounted software installed in the target vehicle based on the update installation package. Therefore, the vehicle software updating mode is enriched, and the flexibility of vehicle software updating is improved.
In addition, in the embodiment of the application, the target vehicle receives the update installation package of the vehicle-mounted software sent by the mobile terminal through the second communication connection, so that the flow rate fee is not generated, and the cost of updating the vehicle-mounted software of the target vehicle is effectively reduced.
Fig. 6 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application, where the mobile terminal may be used to execute the method for updating the vehicle software applied to the mobile terminal according to the foregoing method embodiment. Referring to fig. 6, the mobile terminal 110 may include a processor 1101. The processor 1101 is configured to:
transmitting an update request of vehicle-mounted software of the target vehicle to the server through a first communication connection with the server;
Receiving an update installation package of the vehicle-mounted software sent by the server in response to the update request;
and sending an update installation package to the target vehicle through a second communication connection with the target vehicle, wherein the update installation package is used for updating the vehicle-mounted software by the target vehicle.
Optionally, the first communication connection is a mobile communication connection or a wireless fidelity connection;
the second communication connection is a wired connection, a bluetooth connection or a wireless local area network connection.
Optionally, the processor 1101 may be configured to:
and periodically sending an update request of the vehicle-mounted software of the target vehicle to the server.
Optionally, the server has recorded therein a version number of the on-board software installed in the target vehicle. The processor 1101 may also be configured to:
receiving a first updating completion instruction sent by a target vehicle;
and responding to the first updating completion instruction, sending a second updating completion instruction to the server, wherein the second updating completion instruction is used for indicating the server to update the recorded version number of the vehicle-mounted software installed in the target vehicle to the version number of the updating installation package.
In summary, the embodiment of the present application provides a mobile terminal, where the mobile terminal may receive, through a first communication connection, an update installation package of vehicle-mounted software sent by a server, and may send, through a second communication connection, the update installation package to a target vehicle, so that the target vehicle updates the vehicle-mounted software installed in the target vehicle based on the update installation package. Therefore, the vehicle software updating mode is enriched, and the flexibility of vehicle software updating is improved.
In addition, in the embodiment of the application, the target vehicle receives the update installation package of the vehicle-mounted software sent by the mobile terminal through the second communication connection, so that the flow rate fee is not generated, and the cost of updating the vehicle-mounted software of the target vehicle is effectively reduced.
As shown in fig. 6, the mobile terminal 110 provided in the embodiment of the present application may further include: display unit 1112, radio Frequency (RF) circuit 150, audio circuit 160, wi-Fi module 170, bluetooth module 180, power supply 190, camera 121, and the like.
Wherein camera 121 may be used to capture still pictures or video. The object generates an optical picture through the lens and projects the optical picture to the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then passed to the processor 1101 for conversion into a digital picture signal.
The processor 1101 is a control center of the mobile terminal 110, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the mobile terminal 110 and processes data by running or executing software programs stored in the memory 140, and calling data stored in the memory 140. In some embodiments, the processor 1101 may include one or more processing units; the processor 1101 may also integrate an application processor that primarily processes operating systems, user interfaces, applications, etc., and a baseband processor that primarily processes wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 1101. The processor 1101 in the present application may run an operating system and an application program, may control a user interface to display, and may implement the method for updating the vehicle software applied to the mobile terminal provided in the embodiment of the present application. In addition, the processor 1101 is coupled to an input unit and a display unit 1112.
The display unit 1112 may be used to receive input numeric or character information, generate signal inputs related to user settings and function control of the mobile terminal 110, and optionally the display unit 1112 may be used to display information entered by a user or provided to a user as well as a graphical user interface (graphical user interface, GUI) of various menus of the mobile terminal 110. The display unit 1112 may include a display 11121 disposed on a front side of the mobile terminal 110. The display 11121 may be configured as a liquid crystal display, a light emitting diode, or the like. The display unit 1112 may be used to display various graphical user interfaces described in the present application.
The display unit 1112 includes: a display 11121 and a touch screen 11122 disposed on the front side of the mobile terminal 110. The display 11121 may be used to display preview pictures. The touch screen 11122 may collect touch operations on or near the user, such as clicking a button, dragging a scroll box, and the like. The touch screen 11122 may cover the display screen 11121, or the touch screen 11122 may be integrated with the display screen 11121 to implement input and output functions of the mobile terminal 110, and after integration, the touch screen may be abbreviated as touch screen.
Memory 140 may be used to store software programs and data. The processor 1101 performs various functions of the mobile terminal 110 and data processing by running software programs or data stored in the memory 140. Memory 140 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. The memory 140 stores an operating system that enables the mobile terminal 110 to operate. The memory 140 in the present application may store an operating system and various application programs, and may also store codes for executing the method for updating the vehicle software applied to the mobile terminal provided in the embodiment of the present application.
The RF circuit 150 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communication, and may receive downlink data of the base station and then transmit the downlink data to the processor 1101 for processing; uplink data may be sent to the base station. Typically, RF circuitry includes, but is not limited to, antennas, at least one amplifier, transceivers, couplers, low noise amplifiers, diplexers, and the like.
Audio circuitry 160, speaker 161, and microphone 162 may provide an audio interface between the user and mobile terminal 110. The audio circuit 160 may transmit the received electrical signal converted from audio data to the speaker 161, and the speaker 161 converts the electrical signal into a sound signal and outputs the sound signal. The mobile terminal 110 may also be configured with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, which is output to the RF circuit 150 for transmission to, for example, another terminal, or to the memory 140 for further processing. The microphone 162 of the present application may acquire the voice of the user.
Wi-Fi, which is a short-range wireless transmission technology, can help users to send and receive e-mail, browse web pages, access streaming media, etc. through the Wi-Fi module 170, and provides wireless broadband internet access to users.
The bluetooth module 180 is configured to interact with other bluetooth devices having bluetooth modules through a bluetooth protocol. For example, the mobile terminal 110 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) also provided with a bluetooth module through the bluetooth module 180, thereby performing data interaction.
The mobile terminal 110 also includes a power supply 190 (e.g., a battery) that provides power to the various components. The power supply may be logically connected to the processor 1101 through a power management system, so that functions of managing charging, discharging, power consumption, etc. are implemented through the power management system. The mobile terminal 110 may also be configured with a power button for powering on and off the terminal, and for locking the screen.
The mobile terminal 110 may include at least one sensor 1110, such as a motion sensor 11101, a distance sensor 11102, a fingerprint sensor 11103, and a temperature sensor 11104. The mobile terminal 110 may also be configured with other sensors such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the mobile terminal and each device described above may refer to the corresponding process in the foregoing method embodiment, which is not repeated herein.
Fig. 7 is a software structure block diagram of a mobile terminal according to an embodiment of the present application. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Android Run Time (ART) and a system library, and a kernel layer, respectively.
The application layer may include a series of application packages. As shown in fig. 7, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc. The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.
As shown in fig. 7, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.
The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.
The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, pictures, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.
The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.
The telephony manager is operable to provide communication functions for mobile terminal 110. Such as the management of call status (including on, hung-up, etc.).
The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is presented in a status bar, a presentation sound is emitted, the communication terminal vibrates, and an indicator light blinks.
an android run includes a core library and virtual machines. android run is responsible for scheduling and management of android systems.
The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.
The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), etc.
The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.
Media libraries support a variety of commonly used audio, video format playback and recording, still picture files, and the like. The media library may support a variety of audio video encoding formats, such as: MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.
The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, picture rendering, synthesis, layer processing and the like.
The 2D graphics engine is a drawing engine for 2D drawing.
The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.
Fig. 8 is a schematic structural diagram of a vehicle according to an embodiment of the present application, where the vehicle may execute the method for updating the vehicle software applied to the vehicle according to the above method embodiment. Referring to fig. 8, the vehicle 120 may include a processor 1201. The processor 1201 is configured to:
receiving an update installation package of vehicle-mounted software sent by the mobile terminal through second communication connection with the mobile terminal, wherein the update installation package is received by the mobile terminal through first communication connection with a server;
the vehicle software is updated based on the update installation package.
Optionally, the processor 1201 is configured to: if the update installation package passes the version verification, updating the vehicle-mounted software based on the update installation package;
the processor 1201 is also configured to:
if the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software are smaller than or equal to a first threshold value, sending first prompt information to the mobile terminal, wherein the first prompt information is used for indicating the mobile terminal to resend the update installation package of the vehicle-mounted software;
If the update installation package fails the version verification, the accumulated verification times are larger than a first threshold and smaller than or equal to a second threshold, second prompt information is sent to the mobile terminal, the second prompt information is used for indicating the mobile terminal to send an update request for vehicle-mounted software to the server again, and the second threshold is larger than the first threshold;
if the update installation package fails the version verification and the accumulated verification times are greater than a second threshold, third prompt information is sent to the mobile terminal, and the third prompt information is used for indicating that the vehicle-mounted software update fails;
the accumulated verification times are the total times of performing version verification on the update installation package of the vehicle-mounted software after the vehicle-mounted software is updated last time.
In summary, the embodiment of the application provides a vehicle, which can receive an update installation package of vehicle-mounted software through a second communication connection with a mobile terminal, and then update the vehicle-mounted software based on the update installation package. The update installation package is received by the mobile terminal via a first communication connection with the server. Therefore, the vehicle software updating mode is enriched, and the flexibility of vehicle software updating is improved.
In addition, in the embodiment of the application, the target vehicle receives the update installation package of the vehicle-mounted software sent by the mobile terminal through the second communication connection, so that the flow rate fee is not generated, and the cost of updating the vehicle-mounted software of the target vehicle is effectively reduced.
The embodiment of the present application provides a vehicle, as shown in fig. 8, where the vehicle may include a memory 1202, a processor 1201 and a computer program stored in the memory 1202 and capable of running on the processor 1201, and when the processor 1201 executes the computer program, the updating method of the on-board software applied to the vehicle provided in the above embodiment is implemented, for example, a method executed by the target vehicle in fig. 2 or fig. 3.
An embodiment of the present application provides a computer-readable storage medium in which a computer program is stored, the computer program being loaded by a processor and executing the update method of on-board software applied to a vehicle provided in the above embodiment, for example, the method executed by the target vehicle in fig. 2 or 3.
An embodiment of the present application provides a computer readable storage medium storing a computer program loaded by a processor and executing the method for updating vehicle software applied to a mobile terminal provided in the above embodiment, for example, the method executed by the mobile terminal in fig. 2 or fig. 3.
The embodiment of the application also provides a computer program product containing instructions, which when run on a computer, cause the computer to execute the method for updating the vehicle-mounted software applied to the vehicle, provided by the method embodiment, for example, the method executed by the target vehicle in fig. 2 or fig. 3.
The embodiment of the application also provides a computer program product containing instructions, which when run on a computer, cause the computer to execute the method for updating the vehicle-mounted software applied to the mobile terminal provided by the above method embodiment, for example, the method executed by the mobile terminal in fig. 2 or fig. 3.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
It should be understood that references herein to "and/or" means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. Also, the meaning of the term "at least one" in the present application means one or more, and the meaning of the term "plurality" in the present application means two or more.
The terms "first," "second," and the like in this disclosure are used for distinguishing between similar elements or items having substantially the same function and function, and it should be understood that there is no logical or chronological dependency between the terms "first," "second," and "n," and that there is no limitation on the amount and order of execution. For example, a first threshold may be referred to as a second threshold, and similarly, a second threshold may be referred to as a first threshold, without departing from the scope of the various described examples.
The foregoing description of the exemplary embodiments of the application is not intended to limit the application to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application.

Claims (9)

1. The updating method of the vehicle-mounted software of the vehicle is characterized by being applied to the mobile terminal; the method comprises the following steps:
transmitting an update request of vehicle-mounted software of the target vehicle to the server through a first communication connection with the server; the update request is sent by the mobile terminal after receiving an update signal sent by the server, the update signal is sent to the mobile terminal after the server determines that the current version of the vehicle-mounted software is different from the latest version, and the current version number of the vehicle-mounted software is recorded in the server;
receiving an update installation package of the vehicle-mounted software sent by the server in response to the update request;
transmitting the update installation package to the target vehicle through a second communication connection with the target vehicle, wherein the update installation package is used for the target vehicle to detect whether the version verification is passed;
If the update installation package passes the version verification, updating the vehicle-mounted software installed in the target vehicle based on the update installation package;
if the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software detected by the target vehicle are smaller than or equal to a first threshold value, the target vehicle sends first prompt information to the mobile terminal through second communication connection between the target vehicle and the mobile terminal, wherein the first prompt information is used for enabling the mobile terminal to send the update installation package of the vehicle-mounted software to the target vehicle again;
if the update installation package fails the version verification, and the accumulated verification times of the update installation package of the vehicle-mounted software detected by the target vehicle are greater than the first threshold and less than or equal to the second threshold, the target vehicle sends second prompt information to the mobile terminal through second communication connection with the mobile terminal, wherein the second prompt information is used for enabling the mobile terminal to delete the update installation package from the server, which is received last time, and send an update request for the vehicle-mounted software to the server again;
If the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software detected by the target vehicle are greater than the second threshold, the target vehicle sends third prompt information to the mobile terminal through second communication connection with the mobile terminal, the third prompt information is used for indicating the mobile terminal to delete the locally stored update installation package and forwarding the third prompt information to the server, and the server records that the vehicle-mounted software update fails based on the third prompt information;
the second threshold is larger than the first threshold, and the accumulated verification times are the total times of performing version verification on the update installation package of the vehicle-mounted software after the vehicle-mounted software is updated last time.
2. The method of claim 1, wherein the first communication connection is a mobile communication connection or a wireless fidelity connection;
the second communication connection is a wired connection, a Bluetooth connection or a wireless local area network connection.
3. The method of claim 1, wherein the sending an update request to the server for the on-board software of the target vehicle comprises:
And periodically sending an update request of the vehicle-mounted software of the target vehicle to the server.
4. A method according to any one of claims 1 to 3, wherein the server has recorded therein a version number of the on-vehicle software installed in the target vehicle; after the sending the update installation package to the target vehicle, the method further includes:
receiving a first update completion instruction sent by the target vehicle;
and responding to the first updating completion instruction, and sending a second updating completion instruction to the server, wherein the second updating completion instruction is used for indicating the server to update the recorded version number of the vehicle-mounted software installed in the target vehicle to the version number of the updating installation package.
5. The updating method of the vehicle-mounted software of the vehicle is characterized by being applied to the vehicle; the method comprises the following steps:
receiving an update installation package of vehicle-mounted software sent by a mobile terminal through second communication connection with the mobile terminal, wherein the update installation package is received from a server after the mobile terminal sends an update request of the vehicle-mounted software of a target vehicle to the server through first communication connection with the server, the update request is sent by the mobile terminal after receiving an update signal sent by the server, and the update signal is sent to the mobile terminal after the server determines that the current version of the vehicle-mounted software is different from the latest version;
If the update installation package passes the version verification, updating the vehicle-mounted software based on the update installation package;
if the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software are smaller than or equal to a first threshold value, a first prompt message is sent to the mobile terminal through a second communication connection with the mobile terminal, and the first prompt message is used for indicating the mobile terminal to resend the update installation package of the vehicle-mounted software;
if the update installation package fails the version verification, the accumulated verification times are greater than the first threshold and smaller than or equal to a second threshold, and a second prompt message is sent to the mobile terminal through a second communication connection with the mobile terminal, wherein the second prompt message is used for indicating the mobile terminal to delete the update installation package from the server, which is received last time, and send an update request for the vehicle-mounted software to the server again, and the second threshold is greater than the first threshold;
if the update installation package fails the version verification and the accumulated verification times are greater than the second threshold, third prompt information is sent to the mobile terminal through second communication connection between the server and the mobile terminal, the third prompt information is used for indicating the mobile terminal to delete the locally stored update installation package and forwarding the third prompt information to the server, and the server records that the vehicle-mounted software update fails based on the third prompt information;
The accumulated verification times are the total times of performing version verification on the update installation package of the vehicle-mounted software after the vehicle-mounted software is updated last time.
6. A mobile terminal, the mobile terminal comprising a processor; the processor is configured to:
transmitting an update request of vehicle-mounted software of the target vehicle to the server through a first communication connection with the server; the update request is sent by the mobile terminal after receiving an update signal sent by the server, and the update signal is sent to the mobile terminal after the server determines that the current version of the vehicle-mounted software is different from the latest version;
receiving an update installation package of the vehicle-mounted software sent by the server in response to the update request;
transmitting the update installation package to the target vehicle through a second communication connection with the target vehicle, wherein the update installation package is used for the target vehicle to detect whether the version verification is passed;
if the update installation package passes the version verification, updating the vehicle-mounted software installed in the target vehicle based on the update installation package;
If the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software detected by the target vehicle are smaller than or equal to a first threshold value, the target vehicle sends first prompt information to the mobile terminal through second communication connection between the target vehicle and the mobile terminal, wherein the first prompt information is used for enabling the mobile terminal to send the update installation package of the vehicle-mounted software to the target vehicle again;
if the update installation package fails the version verification, and the accumulated verification times of the update installation package of the vehicle-mounted software detected by the target vehicle are greater than the first threshold and less than or equal to the second threshold, the target vehicle sends second prompt information to the mobile terminal through second communication connection with the mobile terminal, wherein the second prompt information is used for enabling the mobile terminal to delete the update installation package from the server, which is received last time, and send an update request for the vehicle-mounted software to the server again;
if the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software detected by the target vehicle are greater than the second threshold, the target vehicle sends third prompt information to the mobile terminal through second communication connection with the mobile terminal, the third prompt information is used for indicating the mobile terminal to delete the locally stored update installation package and forwarding the third prompt information to the server, and the server records that the vehicle-mounted software update fails based on the third prompt information;
The second threshold is larger than the first threshold, and the accumulated verification times are the total times of performing version verification on the update installation package of the vehicle-mounted software after the vehicle-mounted software is updated last time.
7. The mobile terminal of claim 6, wherein the processor is configured to:
and periodically sending an update request of the vehicle-mounted software of the target vehicle to the server.
8. A vehicle, the vehicle comprising a processor; the processor is configured to:
receiving an update installation package of vehicle-mounted software sent by a mobile terminal through second communication connection with the mobile terminal, wherein the update installation package is received from a server after the mobile terminal sends an update request of the vehicle-mounted software of a target vehicle to the server through first communication connection with the server, the update request is sent by the mobile terminal after receiving an update signal sent by the server, and the update signal is sent to the mobile terminal after the server determines that the current version of the vehicle-mounted software is different from the latest version;
if the update installation package passes the version verification, updating the vehicle-mounted software based on the update installation package;
If the update installation package fails the version verification and the accumulated verification times of the update installation package of the vehicle-mounted software are smaller than or equal to a first threshold value, a first prompt message is sent to the mobile terminal through a second communication connection with the mobile terminal, and the first prompt message is used for indicating the mobile terminal to resend the update installation package of the vehicle-mounted software;
if the update installation package fails the version verification, the accumulated verification times are greater than the first threshold and smaller than or equal to a second threshold, and a second prompt message is sent to the mobile terminal through a second communication connection with the mobile terminal, wherein the second prompt message is used for indicating the mobile terminal to delete the update installation package from the server, which is received last time, and send an update request for the vehicle-mounted software to the server again, and the second threshold is greater than the first threshold;
if the update installation package fails the version verification and the accumulated verification times are greater than the second threshold, third prompt information is sent to the mobile terminal through second communication connection between the server and the mobile terminal, the third prompt information is used for indicating the mobile terminal to delete the locally stored update installation package and forwarding the third prompt information to the server, and the server records that the vehicle-mounted software update fails based on the third prompt information;
The accumulated verification times are the total times of performing version verification on the update installation package of the vehicle-mounted software after the vehicle-mounted software is updated last time.
9. An update system for on-board software of a vehicle, the system comprising:
a mobile terminal as claimed in claim 6 or claim 7, and a vehicle as claimed in claim 8.
CN202110844120.XA 2021-07-26 2021-07-26 Vehicle and updating method of vehicle-mounted software thereof and mobile terminal Active CN113535207B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110844120.XA CN113535207B (en) 2021-07-26 2021-07-26 Vehicle and updating method of vehicle-mounted software thereof and mobile terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110844120.XA CN113535207B (en) 2021-07-26 2021-07-26 Vehicle and updating method of vehicle-mounted software thereof and mobile terminal

Publications (2)

Publication Number Publication Date
CN113535207A CN113535207A (en) 2021-10-22
CN113535207B true CN113535207B (en) 2023-10-31

Family

ID=78089049

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110844120.XA Active CN113535207B (en) 2021-07-26 2021-07-26 Vehicle and updating method of vehicle-mounted software thereof and mobile terminal

Country Status (1)

Country Link
CN (1) CN113535207B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114379573B (en) * 2022-01-10 2024-05-24 海信集团控股股份有限公司 Vehicle and control method thereof
CN114374680A (en) * 2022-01-17 2022-04-19 上海极豆科技有限公司 Vehicle-mounted device control method and device, electronic device and readable storage medium
CN114523919B (en) * 2022-02-14 2024-04-05 海信集团控股股份有限公司 Vehicle and control method thereof
CN115174623A (en) * 2022-06-29 2022-10-11 重庆长安汽车股份有限公司 Vehicle application management method and system, electronic device and readable storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867916A (en) * 2009-04-16 2010-10-20 深圳市赛格导航科技股份有限公司 Method for realizing air update of vehicle terminal
CN104978206A (en) * 2014-04-11 2015-10-14 比亚迪股份有限公司 Method, device and system for updating vehicle body control module of vehicle
CN106383757A (en) * 2016-10-31 2017-02-08 北京新能源汽车股份有限公司 Vehicle-mounted software updating method and device
CN106790330A (en) * 2015-11-23 2017-05-31 上海汽车集团股份有限公司 The method for remote updating of vehicle-mounted ECU, vehicle-mounted ECU and vehicle
CN110659038A (en) * 2018-06-29 2020-01-07 比亚迪股份有限公司 Vehicle-mounted millimeter wave radar upgrading method and device, computer equipment and storage medium
CN112230948A (en) * 2019-06-30 2021-01-15 比亚迪股份有限公司 Software upgrading method, device, system, vehicle and storage medium
CN112988191A (en) * 2021-03-17 2021-06-18 摩登汽车有限公司 Vehicle over-the-air download upgrade management system and method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101548953B1 (en) * 2013-12-24 2015-09-01 현대자동차주식회사 Method and apparatus for updating information for vehicle

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867916A (en) * 2009-04-16 2010-10-20 深圳市赛格导航科技股份有限公司 Method for realizing air update of vehicle terminal
CN104978206A (en) * 2014-04-11 2015-10-14 比亚迪股份有限公司 Method, device and system for updating vehicle body control module of vehicle
CN106790330A (en) * 2015-11-23 2017-05-31 上海汽车集团股份有限公司 The method for remote updating of vehicle-mounted ECU, vehicle-mounted ECU and vehicle
CN106383757A (en) * 2016-10-31 2017-02-08 北京新能源汽车股份有限公司 Vehicle-mounted software updating method and device
CN110659038A (en) * 2018-06-29 2020-01-07 比亚迪股份有限公司 Vehicle-mounted millimeter wave radar upgrading method and device, computer equipment and storage medium
CN112230948A (en) * 2019-06-30 2021-01-15 比亚迪股份有限公司 Software upgrading method, device, system, vehicle and storage medium
CN112988191A (en) * 2021-03-17 2021-06-18 摩登汽车有限公司 Vehicle over-the-air download upgrade management system and method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Improving the RISS/GNSS Land-Vehicles Integrated Navigation System Using Magnetic Azimuth Updates;Ashraf Abosekeen等;《IEEE Transactions on Intelligent Transportation Systems》;1-14 *
基于车联网的MP2P资源定位技术研究与实现;姜超;《中国优秀硕士学位论文全文数据库 (工程科技Ⅱ辑)》;C034-243 *

Also Published As

Publication number Publication date
CN113535207A (en) 2021-10-22

Similar Documents

Publication Publication Date Title
CN113535207B (en) Vehicle and updating method of vehicle-mounted software thereof and mobile terminal
CN110865837B (en) Method and terminal for system upgrade
CN113489700B (en) Method, server and terminal equipment for acquiring media asset data
CN113432619A (en) Navigation route display method, vehicle and mobile terminal
CN113709026B (en) Method, device, storage medium and program product for processing instant communication message
CN113835928A (en) Application backup and recovery method, device, storage medium, and program product
CN114374813A (en) Multimedia resource management method, recorder and server
CN111158735B (en) Hot patch file processing method and communication terminal
CN112825072B (en) Communication terminal and data sharing method
CN114371895B (en) Terminal equipment, mail marking method and storage medium
CN113696852B (en) Vehicle, locking method thereof and mobile terminal
CN113642010B (en) Method for acquiring data of extended storage device and mobile terminal
CN110852717A (en) Travel updating method and intelligent communication terminal
CN112114885B (en) Terminal, control equipment and service processing method
CN112000411B (en) Mobile terminal and display method of recording channel occupation information thereof
CN112668061B (en) Electronic equipment and equipment code reporting method thereof
CN115470778A (en) Method for adjusting language type of vehicle interaction system, vehicle and mobile terminal
CN113253905B (en) Touch method based on multi-finger operation and intelligent terminal
CN115250261B (en) Information display method and electronic equipment
CN111142648B (en) Data processing method and intelligent terminal
CN114501389A (en) Mobile terminal, network sharing method and storage medium
CN112925545A (en) Mobile terminal and application updating method thereof
CN112312509A (en) Mobile terminal and network access method thereof
CN115334604A (en) Terminal device, network control method and storage medium
CN115146257A (en) Terminal device, function screening method and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20240429

Address after: 266555, No. 218, Bay Road, Qingdao economic and Technological Development Zone, Shandong

Patentee after: Hisense Video Technology Co.,Ltd.

Country or region after: China

Address before: 266555, No. 218, Bay Road, Qingdao economic and Technological Development Zone, Shandong

Patentee before: Hisense Group Holding Co.,Ltd.

Country or region before: China

TR01 Transfer of patent right