CN111935199A - Vehicle-mounted software version information synchronization method, device and system and vehicle - Google Patents
Vehicle-mounted software version information synchronization method, device and system and vehicle Download PDFInfo
- Publication number
- CN111935199A CN111935199A CN201910391953.8A CN201910391953A CN111935199A CN 111935199 A CN111935199 A CN 111935199A CN 201910391953 A CN201910391953 A CN 201910391953A CN 111935199 A CN111935199 A CN 111935199A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- software
- version information
- server
- external terminal
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a vehicle-mounted software version information synchronization method, which comprises the following steps: monitoring a software refreshing event generated by updating vehicle-mounted software of an external terminal device; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment; in response to the monitoring of the software refreshing event, acquiring vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment; and uploading the vehicle-mounted software version information to a server for storage. The embodiment of the invention also discloses a vehicle-mounted software version information synchronization device, a vehicle-mounted software version information synchronization system and a vehicle. By adopting the embodiment of the invention, the version information can be synchronized in time, the influence on the vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted terminal is avoided, and the resource for sending and receiving the information by the vehicle-mounted terminal is not occupied too much.
Description
Technical Field
The invention relates to the technical field of vehicle-mounted software, in particular to a method, a device and a system for synchronizing version information of vehicle-mounted software and a vehicle.
Background
The vehicle-mounted software in the vehicle usually adopts an after-sales diagnostic apparatus to update the software, and after the vehicle finishes updating the vehicle-mounted software, the mode of synchronizing the version information of the vehicle-mounted software by the server is as follows: the server periodically sends an instruction to the vehicle-mounted terminal to obtain the version information, the vehicle-mounted terminal sends a diagnosis instruction to read the version information of each node of the vehicle-mounted software and uploads the version information to the server, the server compares the obtained version information with the locally stored version information, and if the version information is updated, the software upgrading package and the version information on the server are updated correspondingly. The vehicle-mounted terminal periodically reads the version information no matter whether the version is updated or not, and occupies the sending and receiving resources of the vehicle-mounted terminal; because of periodic query, version information cannot be synchronized timely, and only periodic synchronization is performed; and the periodic query brings certain load to the internal and external networks of the vehicle, influences the normal operation of the whole vehicle network, even leads to network breakdown, and brings certain potential safety hazard.
Disclosure of Invention
The embodiment of the invention aims to provide a method, a device and a system for synchronizing version information of vehicle-mounted software and a vehicle, which can synchronize the version information in time, avoid the influence on a vehicle-mounted network caused by the periodic reading of the version information by a vehicle-mounted terminal and avoid the excessive occupation of resources for sending and receiving information by the vehicle-mounted terminal.
In order to achieve the above object, an embodiment of the present invention provides a method for synchronizing version information of vehicle-mounted software, including:
monitoring a software refreshing event generated by updating vehicle-mounted software of an external terminal device; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
in response to the monitoring of the software refreshing event, acquiring vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment;
and uploading the vehicle-mounted software version information to a server for storage.
Compared with the prior art, the vehicle-mounted software version information synchronization method disclosed by the embodiment of the invention comprises the steps of monitoring a software refreshing event generated by updating vehicle-mounted software of an external terminal device; and then, when responding to the monitored software refreshing event, acquiring the vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment, and finally uploading the vehicle-mounted software version information to a server for storage, so that the server can synchronize the vehicle-mounted software version information in time. According to the embodiment of the invention, when the server needs to synchronize the version information of the vehicle-mounted software, the version information of the vehicle-mounted software does not need to be periodically inquired, but the corresponding version information of the vehicle-mounted software is directly acquired when the vehicle-mounted software is updated and is timely uploaded to the server, the vehicle-mounted terminal does not need to periodically read the version information of each vehicle-mounted software on the vehicle, the vehicle-mounted terminal is prevented from periodically reading the version information to influence a vehicle-mounted network, resources for sending and receiving information by the vehicle-mounted terminal are not excessively occupied, and the network flow is saved.
As an improvement of the above solution, the monitoring of the software refresh event generated by the external terminal device updating the onboard software of the vehicle includes:
monitoring an operation message in a vehicle-mounted network; the operation message is generated by the vehicle when the external terminal equipment operates the vehicle;
and when the operation message is monitored and the message is detected to carry the software refreshing event identification code, judging that the occurrence of the software refreshing event is monitored.
As an improvement of the above scheme, the acquiring, in response to monitoring the software refresh event, vehicle-mounted software version information after the external terminal device updates the vehicle-mounted software includes:
in response to monitoring the software refreshing event, uploading update identification information corresponding to the software refreshing event to the server;
and receiving a software version information acquisition instruction sent by the server according to the update identification information, and acquiring the vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment according to the software version information acquisition instruction.
As an improvement of the above scheme, the uploading, in response to the monitoring of the software refresh event, update identification information corresponding to the software refresh event to the server includes:
in response to monitoring the software refreshing event, setting a preset flag position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event;
and in response to monitoring that the flag position is a first value, uploading update identification information corresponding to the software refreshing event to the server, and setting the flag position to be a second value.
As an improvement of the above scheme, the timing for detecting the flag bit is set as follows:
when the whole vehicle is powered on.
As an improvement of the above scheme, the on-board software is ECU software, and the update identification information is an identification code of an ECU in the vehicle where the ECU software is updated.
As an improvement of the above, the timing at which the flag position is set to the second value is set as:
and when a response instruction returned by the server according to the received updating identification information is received.
In order to achieve the above object, another embodiment of the present invention provides an on-board software version information synchronization apparatus, including:
the software refreshing event monitoring module is used for monitoring a software refreshing event generated by updating vehicle-mounted software of the vehicle by external terminal equipment; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
the version information acquisition module is used for responding to the monitored software refreshing event and acquiring vehicle-mounted software version information after the vehicle-mounted software is updated by the external terminal equipment;
and the version information uploading module is used for uploading the version information of the vehicle-mounted software to a server for storage.
Compared with the prior art, the vehicle-mounted software version information synchronization device disclosed by the embodiment of the invention comprises the following steps that firstly, a software refreshing event monitoring module monitors a software refreshing event generated by the updating of vehicle-mounted software of an external terminal device; and then when the software refreshing event is monitored, the version information acquisition module acquires the vehicle-mounted software version information updated by the external terminal equipment to the vehicle-mounted software, and finally the version information uploading module uploads the vehicle-mounted software version information to a server for storage, so that the server can synchronize the vehicle-mounted software version information in time. According to the embodiment of the invention, when the server needs to synchronize the version information of the vehicle-mounted software, the version information of the vehicle-mounted software does not need to be periodically inquired, but the corresponding version information of the vehicle-mounted software is directly acquired when the vehicle-mounted software is updated and is timely uploaded to the server, and the version information of each vehicle-mounted software on a vehicle does not need to be periodically read by the vehicle-mounted software version information synchronizing device, so that the vehicle-mounted network is prevented from being influenced by the fact that the version information is periodically read by the vehicle-mounted software version information synchronizing device, resources for transmitting and receiving information by the vehicle-mounted software version information synchronizing device are not excessively.
To achieve the above object, another embodiment of the present invention provides a vehicle, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the in-vehicle software version information synchronization method according to any one of the above embodiments.
In order to achieve the above object, another embodiment of the present invention provides a vehicle-mounted software version information synchronization system, including a server and the vehicle as described in the above embodiment; and the server is used for storing the version information of the vehicle-mounted software.
Drawings
Fig. 1 is a flowchart of a method for synchronizing version information of onboard software according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating another method for synchronizing vehicle software version information according to an embodiment of the present invention;
fig. 3 is a block diagram illustrating a structure of an in-vehicle software version information synchronization apparatus according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a vehicle according to an embodiment of the present invention;
fig. 5 is a block diagram of a system for synchronizing version information of onboard software according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1, fig. 1 is a flowchart of a method for synchronizing version information of vehicle-mounted software according to an embodiment of the present invention; the method comprises the following steps:
s1, monitoring a software refreshing event generated by the update of the vehicle-mounted software of the external terminal equipment; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
s2, responding to the monitored software refreshing event, and acquiring vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment;
and S3, uploading the vehicle-mounted software version information to a server for storage.
It should be noted that the method for synchronizing version information of vehicle-mounted software according to the embodiment of the present invention can be implemented by a vehicle-mounted terminal in a vehicle, where the vehicle-mounted terminal is a front-end device of a vehicle monitoring and management system, integrates multiple functions such as data processing and data communication, and has a powerful service scheduling function and data processing capability. The external terminal device can be an automobile diagnostic instrument or other devices capable of updating on-board software in a vehicle.
When the external terminal equipment locally updates the vehicle-mounted software in the vehicle, the vehicle-mounted terminal responds to a software refreshing event generated by updating the vehicle-mounted software of the vehicle by the external terminal equipment, at the moment, the vehicle-mounted terminal acquires the vehicle-mounted software version information updated by the external terminal equipment, and finally, the vehicle-mounted software version information is uploaded to the server to be stored, so that the server can synchronize the vehicle-mounted software version information in time. According to the embodiment of the invention, when the server needs to synchronize the vehicle-mounted software version information, the vehicle-mounted software version information does not need to be inquired periodically, but the corresponding vehicle-mounted software version information is directly acquired when the vehicle-mounted software is updated, so that the resources for transmitting and receiving information by the vehicle-mounted terminal are not occupied too much, and the network flow is saved.
Specifically, in step S1, the monitoring of the software refresh event generated by the external terminal device updating the onboard software of the vehicle includes:
s11, monitoring an operation message in the vehicle-mounted network; the operation message is generated by the vehicle when the external terminal equipment operates the vehicle;
and S12, when the operation message is monitored and the message is detected to carry the software refreshing event identification code, judging that the occurrence of the software refreshing event is monitored.
Specifically, when the vehicle-mounted software in the vehicle is updated, the vehicle generates a message carrying a software refreshing event identification code, so that whether the software refreshing event is monitored can be determined by monitoring the operation message in the vehicle-mounted network.
Preferably, after monitoring the operation packet in the vehicle-mounted network, before the monitoring of the operation packet and the detection of the packet carrying the software refresh event identification code, the method further includes: when the operation message is monitored and the header of the message is detected to carry a diagnosis message identification code, judging that the current message is a diagnosis message; at this time, it is considered that a diagnostic instrument operation event is detected, that is, the external terminal device is operating the in-vehicle ECU. Step S12 specifically includes: and when detecting that the diagnostic message carries the software refreshing event identification code, judging that the occurrence of the software refreshing event is monitored. Preferably, the vehicle-mounted network and the vehicle-mounted terminal communicate by using a UDS protocol, and the diagnostic message identification code is 7 or 1. Of course, the diagnostic message identifier may also be other values, which are not described in detail here.
After the current message is determined to be a diagnostic message, since the diagnostic message covers a conventional diagnostic event and a software refresh event, it is necessary to further determine whether the diagnostic message indicates the occurrence of the software refresh event. At this time, whether the occurrence of the software refreshing event is monitored is determined by judging whether the operation message carries the software refreshing event identification code. Preferably, the software refresh event identification code is "6E F184", that is, the operation message may be "7 XX 6E F184 XX". It should be noted that the software refresh event identification code may also be replaced with other identification codes in the software refresh process, and the software refresh event identification code may also be set to other values, as long as the software refresh event can be uniquely identified, which is within the protection scope of the present invention.
Specifically, in step S2, the acquiring, in response to the monitoring of the software refresh event, vehicle-mounted software version information after the external terminal device updates the vehicle-mounted software includes:
s21, responding to the monitoring of the software refreshing event, and uploading updating identification information corresponding to the software refreshing event to the server;
and S22, receiving a software version information acquisition instruction sent by the server according to the update identification information, and acquiring vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment according to the software version information acquisition instruction.
Preferably, the vehicle-mounted software is ECU software, and the update identification information is an identification code of an ECU on the vehicle, which is updated by the vehicle-mounted ECU. Further, the identification code of the ECU whose on-board software is updated may be the identification code of the ECU carried in the operation message, for example, the identification code of the ECU is "7 XX" in the operation message. Referring to table 1, table 1 is a format definition of the software refresh event.
TABLE 1 Format definition of software Refresh events
| Length (Byte) | Description of the invention |
| 1 | Event number ID, fill 1 |
| 1 | Number of ECU |
| 1 | ECU code 1 |
| … | …… |
| 1 | ECU code n |
Preferably, step S21 specifically includes:
s211, in response to the monitoring of the software refreshing event, setting a preset flag position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event;
s212, in response to the fact that the flag position is monitored to be the first value, updating identification information corresponding to the software refreshing event is uploaded to the server, and the flag position is set to be the second value.
Specifically, the flag bit is a flag, the first value is 1, and the second value is 0. When the software refreshing event is monitored in response, setting a flag to be 1, and acquiring and storing updating identification information corresponding to the software refreshing event; and when the flag is monitored to be 1, uploading updating identification information corresponding to the software refreshing event to the server, and setting the flag to be 0.
In this embodiment, after a software refreshing event is monitored, by acquiring and storing corresponding update identification information and setting the flag position to a first value, even if an accident (for example, the vehicle cannot be normally networked with the server currently, or the vehicle is abnormally powered off) occurs in the vehicle, after the vehicle returns to a normal state, the server can still immediately respond to the monitoring that the flag position is the first value and upload the update identification information corresponding to the software refreshing event to the server in time, so that the server can finally and synchronously update the update version information of the vehicle-mounted software.
Preferably, the timing of detecting the flag bit is set as: when the whole vehicle is powered on. Specifically, in consideration of real-time performance, the update identification information may be uploaded to a server immediately after the update identification information is acquired. However, the traffic is used when the connection between the vehicle-mounted terminal and the server is established each time, and if the updated identification information is obtained by the vehicle-mounted terminal and then immediately uploaded to the server, the connection between the vehicle-mounted terminal and the server needs to be established for many times, which wastes the traffic of the vehicle-mounted terminal. Therefore, in order to achieve the purpose of saving current, the updated identification information can be sent to the server only when the whole vehicle is powered on, and international data needs to be uploaded to the server when the vehicle is powered on and started every time, so that the updated identification information can be uploaded to the server while the international data is uploaded, and the vehicle flow is saved.
Monitoring the flag bit when the whole vehicle is powered on, and when the flag bit is a first value, indicating that a software refreshing event occurs before the whole vehicle is powered on, uploading update identification information corresponding to the software refreshing event to the server; and when the flag position is a second value, the software refreshing event does not occur before the whole vehicle is powered on.
Preferably, the timing at which the flag position is set to the second value is set to: and when a response instruction returned by the server according to the received updating identification information is received. And the server returns a response instruction after receiving the updating identification information, and the flag position is set to be a second value when receiving the response instruction.
Further, the process of the above steps S1-S2 can refer to fig. 2.
Specifically, in step S3, the vehicle-mounted software version information is uploaded to a server and stored, so that the server synchronously updates the vehicle-mounted software version information in the database. Furthermore, the vehicle-mounted software version information can be uploaded to a server, and simultaneously a vehicle-mounted software upgrading package corresponding to the vehicle-mounted software version information can be uploaded, so that the server updates the vehicle-mounted software upgrading package in the database. Then, step S2 is: when the software refreshing event is monitored, acquiring vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment and a vehicle-mounted software upgrading package corresponding to the vehicle-mounted software version information; step S3 is: and uploading the vehicle-mounted software version information and the vehicle-mounted software upgrading package to a server for storage.
Compared with the prior art, the vehicle-mounted software version information synchronization method disclosed by the embodiment of the invention comprises the steps of monitoring a software refreshing event generated by updating vehicle-mounted software of an external terminal device; and then, when responding to the monitored software refreshing event, acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software, so that the vehicle-mounted software version information does not need to be periodically inquired when the server needs to synchronize the vehicle-mounted software version information, and finally uploading the vehicle-mounted software version information to the server for storage, so that the server can synchronize the vehicle-mounted software version information in time. According to the embodiment of the invention, when the server needs to synchronize the version information of the vehicle-mounted software, the version information of the vehicle-mounted software does not need to be periodically inquired, but the corresponding version information of the vehicle-mounted software is directly acquired when the vehicle-mounted software is updated and is timely uploaded to the server, the vehicle-mounted terminal does not need to periodically read the version information of each vehicle-mounted software on the vehicle, the vehicle-mounted terminal is prevented from periodically reading the version information to influence a vehicle-mounted network, resources for sending and receiving information by the vehicle-mounted terminal are not excessively occupied, and the network flow is saved.
Example two
Referring to fig. 3, fig. 3 is a block diagram of a structure of an in-vehicle software version information synchronization apparatus 10 according to an embodiment of the present invention; the method comprises the following steps:
the software refreshing event monitoring module 11 is used for monitoring a software refreshing event generated by updating vehicle-mounted software of the vehicle by external terminal equipment; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
the version information acquisition module 12 is configured to acquire vehicle-mounted software version information after the external terminal device updates the vehicle-mounted software in response to the monitored software refreshing event;
and the version information uploading module 13 is used for uploading the version information of the vehicle-mounted software to a server for storage.
It should be noted that the vehicle-mounted software version information synchronization apparatus 10 according to the embodiment of the present invention may be a vehicle-mounted terminal in a vehicle, where the vehicle-mounted terminal is a front-end device of a vehicle monitoring and management system, integrates multiple functions such as data processing and data communication, and has a strong service scheduling function and data processing capability. The external terminal device can be an automobile diagnostic instrument or other devices capable of updating on-board software in a vehicle.
Preferably, the software refresh event monitoring module 11 is specifically configured to:
monitoring an operation message in a vehicle-mounted network; the operation message is generated by the vehicle when the external terminal equipment operates the vehicle;
and when the operation message is monitored and the message is detected to carry the software refreshing event identification code, judging that the occurrence of the software refreshing event is monitored.
Specifically, when the vehicle-mounted software in the vehicle is updated, the vehicle may generate a message carrying a software refresh event identification code, and the software refresh event monitoring module 11 may determine whether the occurrence of the software refresh event is monitored by monitoring an operation message in the vehicle-mounted network.
Preferably, after monitoring the operation packet in the vehicle-mounted network, before the monitoring of the operation packet and the detection of the packet carrying the software refresh event identification code, the method further includes: when the operation message is monitored and the header of the message is detected to carry a diagnosis message identification code, judging that the current message is a diagnosis message; at this time, it is considered that a diagnostic instrument operation event is detected, that is, the external terminal device is operating the in-vehicle ECU. At this time, when it is detected that the diagnostic packet carries the software refresh event identification code, it is determined that the occurrence of the software refresh event is monitored. Preferably, the vehicle-mounted network and the vehicle-mounted terminal communicate by using a UDS protocol, and the diagnostic message identification code is 7 or 1.
After the current message is determined to be a diagnostic message, since the diagnostic message covers a conventional diagnostic event and a software refresh event, it is necessary to further determine whether the diagnostic message indicates the occurrence of the software refresh event. At this time, whether the operation message carries the software refreshing event identification code is judged, so that whether the occurrence of the software refreshing event is monitored is judged. Preferably, the software refresh event identification code is "6E F184", that is, the operation message may be "7 XX 6E F184 XX". It should be noted that the software refresh event identification code may also be replaced with other identification codes in the software refresh process, as long as the software refresh event can be uniquely identified, which is within the protection scope of the present invention.
Preferably, the version information obtaining module 12 is specifically configured to:
in response to monitoring the software refreshing event, uploading update identification information corresponding to the software refreshing event to the server;
and receiving a software version information acquisition instruction sent by the server according to the update identification information, and acquiring the vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment according to the software version information acquisition instruction.
Preferably, the vehicle-mounted software is ECU software, and the update identification information is an identification code of an ECU on the vehicle, which is updated by the vehicle-mounted ECU. Further, the identification code of the ECU whose on-board software is updated may be the identification code of the ECU carried in the operation message, for example, the identification code of the ECU is "7 XX" in the operation message.
Preferably, the uploading, in response to the monitoring of the software refresh event, update identification information corresponding to the software refresh event to the server specifically includes:
in response to monitoring the software refreshing event, setting a preset flag position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event;
and in response to monitoring that the flag position is a first value, uploading update identification information corresponding to the software refreshing event to the server, and setting the flag position to be a second value.
Specifically, the flag bit is a flag, the first value is 1, and the second value is 0. When the software refreshing event is monitored in response, setting a flag to be 1, and acquiring and storing updating identification information corresponding to the software refreshing event; and when the flag is monitored to be 1, uploading update identification information corresponding to the software refreshing event to the server, and setting the flag to be 0.
Preferably, the timing of detecting the flag bit is set as: when the whole vehicle is powered on. Specifically, in consideration of real-time performance, the update identification information may be uploaded to a server immediately after the update identification information is acquired. However, the traffic is used when the connection between the vehicle-mounted terminal and the server is established each time, and if the updated identification information is obtained by the vehicle-mounted terminal and then immediately uploaded to the server, the connection between the vehicle-mounted terminal and the server needs to be established for many times, which wastes the traffic of the vehicle-mounted terminal. Therefore, in order to achieve the purpose of saving current, the updated identification information can be sent to the server only when the whole vehicle is powered on, and international data needs to be uploaded to the server when the vehicle is powered on and started every time, so that the updated identification information can be uploaded to the server while the international data is uploaded, and the vehicle flow is saved.
Monitoring the flag bit when the whole vehicle is powered on, and when the flag bit is a first value, indicating that a software refreshing event occurs before the whole vehicle is powered on, uploading update identification information corresponding to the software refreshing event to the server; and when the flag position is a second value, the software refreshing event does not occur before the whole vehicle is powered on.
Preferably, the timing at which the flag position is set to the second value is set to: and when a response instruction returned by the server according to the received updating identification information is received. And the server returns a response instruction after receiving the updating identification information, and the flag position is set to be a second value when receiving the response instruction.
Specifically, the version information uploading module 13 uploads the vehicle-mounted software version information to a server for storage, so that the server synchronously updates the vehicle-mounted software version information in a database. Furthermore, the vehicle-mounted software version information can be uploaded to a server, and simultaneously a vehicle-mounted software upgrading package corresponding to the vehicle-mounted software version information can be uploaded, so that the server updates the vehicle-mounted software upgrading package in the database. At this time, when the software refreshing event is monitored, vehicle-mounted software version information obtained after the vehicle-mounted software is updated by the external terminal equipment and a vehicle-mounted software upgrading package corresponding to the vehicle-mounted software version information are obtained; and uploading the vehicle-mounted software version information and the vehicle-mounted software upgrading package to a server for storage.
Compared with the prior art, the vehicle-mounted software version information synchronization device 10 disclosed by the embodiment of the invention firstly monitors a software refreshing event generated by the vehicle-mounted software updating of the external terminal equipment by the software refreshing event monitoring module 11; then, when the software refreshing event is monitored, the version information acquisition module 12 acquires the vehicle-mounted software version information updated by the external terminal device on the vehicle-mounted software, and finally the version information uploading module 13 uploads the vehicle-mounted software version information to the server for storage, so that the server can synchronize the vehicle-mounted software version information in time. According to the embodiment of the invention, when the server needs to synchronize the version information of the vehicle-mounted software, the version information of the vehicle-mounted software does not need to be periodically inquired, but the corresponding version information of the vehicle-mounted software is directly acquired when the vehicle-mounted software is updated and is timely uploaded to the server, the version information of each vehicle-mounted software on a vehicle does not need to be periodically read by the vehicle-mounted software version information synchronizing device 10, the vehicle-mounted network is prevented from being influenced by the periodic reading of the version information by the vehicle-mounted software version information synchronizing device 10, the resources for sending and receiving the information by the vehicle-mounted software version information synchronizing device 10 are not excessively occupied, and.
EXAMPLE III
Referring to fig. 4, fig. 4 is a schematic structural diagram of a vehicle 20 according to an embodiment of the present invention; the vehicle 20 of the embodiment includes: a processor 21, a memory 22 and a computer program stored in said memory 22 and executable on said processor 21. The processor 21, when executing the computer program, implements the steps in each of the above-mentioned embodiments of the synchronization method for vehicle software version information, such as steps S1-S3 shown in fig. 1. Alternatively, the processor 21, when executing the computer program, implements the functions of the modules/units in the above-mentioned device embodiments, such as the software refresh event monitoring module 11.
Illustratively, the computer program may be divided into one or more modules/units, which are stored in the memory 22 and executed by the processor 21 to accomplish the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program in the vehicle 20. For example, the computer program may be divided into a software refresh event monitoring module 11, a version information obtaining module 12, and a version information uploading module 13, and the specific functions of each module are as follows:
the software refreshing event monitoring module 11 is used for monitoring a software refreshing event generated by updating vehicle-mounted software of the vehicle by external terminal equipment; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
the version information acquisition module 12 is configured to acquire vehicle-mounted software version information after the external terminal device updates the vehicle-mounted software in response to the monitored software refreshing event;
and the version information uploading module 13 is used for uploading the version information of the vehicle-mounted software to a server for storage.
The Processor 21 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and the processor 21 is the control center of the vehicle 20 and connects the various parts of the entire vehicle 20 using various interfaces and lines.
The memory 22 may be used to store the computer programs and/or modules, and the processor 21 may implement various functions of the vehicle 20 by running or executing the computer programs and/or modules stored in the memory 22 and invoking data stored in the memory 22. The memory 22 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. In addition, the memory 22 may include a high speed random access memory, and may also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
Wherein the integrated modules/units of the vehicle 20, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the above embodiments may be implemented by a computer program, which may be stored in a computer readable storage medium and used by the processor 21 to implement the steps of the above embodiments of the method. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
Example four
Referring to fig. 5, fig. 5 is a block diagram illustrating a structure of an in-vehicle software version information synchronization system 30 according to an embodiment of the present invention; comprises a server 31 and the vehicle 20 as described in the third embodiment; the server 31 is configured to store the vehicle-mounted software version information.
For the specific working process of the vehicle 20 and the server 31, please refer to the working process of the above embodiment, which is not described herein again.
Compared with the prior art, the vehicle-mounted software version information synchronization system 30 disclosed by the invention has the advantages that firstly, the vehicle 20 monitors a software refreshing event generated by the vehicle-mounted software updating of the external terminal equipment; then, when responding to the monitored software refreshing event, the vehicle 20 acquires the vehicle-mounted software version information updated by the external terminal device to the vehicle-mounted software, and finally the vehicle 20 uploads the vehicle-mounted software version information to the server for storage, so that the server 31 timely synchronizes the vehicle-mounted software version information. In the embodiment of the invention, when the server 31 needs to synchronize the version information of the vehicle-mounted software, the vehicle 20 does not need to periodically inquire the version information of the vehicle-mounted software, but directly obtains the version information of the corresponding vehicle-mounted software when the vehicle-mounted software is updated and uploads the version information to the server in time, and the vehicle-mounted terminal does not need to periodically read the version information of each vehicle-mounted software on the vehicle, thereby avoiding the influence on a vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted terminal, avoiding the excessive occupation of the resource for sending and receiving the information by the vehicle-mounted terminal and.
It should be noted that the above-described device embodiments are merely illustrative, where the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. In addition, in the drawings of the embodiment of the apparatus provided by the present invention, the connection relationship between the modules indicates that there is a communication connection between them, and may be specifically implemented as one or more communication buses or signal lines. One of ordinary skill in the art can understand and implement it without inventive effort.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (10)
1. A vehicle-mounted software version information synchronization method is characterized by comprising the following steps:
monitoring a software refreshing event generated by updating vehicle-mounted software of an external terminal device; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
in response to the monitoring of the software refreshing event, acquiring vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment;
and uploading the vehicle-mounted software version information to a server for storage.
2. The method for synchronizing the vehicle-mounted software version information according to claim 1, wherein the step of monitoring the software refreshing event generated by the external terminal device for the vehicle-mounted software updating comprises the following steps:
monitoring an operation message in a vehicle-mounted network; the operation message is generated by the vehicle when the external terminal equipment operates the vehicle;
and when the operation message is monitored and the message is detected to carry the software refreshing event identification code, judging that the occurrence of the software refreshing event is monitored.
3. The method for synchronizing vehicle-mounted software version information according to claim 1, wherein the acquiring vehicle-mounted software version information after the vehicle-mounted software is updated by the external terminal device in response to the monitoring of the software refresh event comprises:
in response to monitoring the software refreshing event, uploading update identification information corresponding to the software refreshing event to the server;
and receiving a software version information acquisition instruction sent by the server according to the update identification information, and acquiring the vehicle-mounted software version information of the vehicle-mounted software updated by the external terminal equipment according to the software version information acquisition instruction.
4. The method for synchronizing the vehicle-mounted software version information according to claim 3, wherein the uploading of the update identification information corresponding to the software refresh event to the server in response to the monitoring of the software refresh event comprises:
in response to monitoring the software refreshing event, setting a preset flag position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event;
and in response to monitoring that the flag position is a first value, uploading update identification information corresponding to the software refreshing event to the server, and setting the flag position to be a second value.
5. The vehicle-mounted software version information synchronization method according to claim 4, wherein the time for detecting the flag bit is set as follows:
when the whole vehicle is powered on.
6. The method according to claim 3, wherein the onboard software is ECU software, and the update identification information is an identification code of an ECU on the vehicle in which the ECU software is updated.
7. The vehicle-mounted software version information synchronization method according to claim 4, wherein the timing at which the flag position is set to the second value is set as:
and when a response instruction returned by the server according to the received updating identification information is received.
8. An in-vehicle software version information synchronization device, characterized by comprising:
the software refreshing event monitoring module is used for monitoring a software refreshing event generated by updating vehicle-mounted software of the vehicle by external terminal equipment; the external terminal equipment is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance by the external terminal equipment;
the version information acquisition module is used for responding to the monitored software refreshing event and acquiring vehicle-mounted software version information after the vehicle-mounted software is updated by the external terminal equipment;
and the version information uploading module is used for uploading the version information of the vehicle-mounted software to a server for storage.
9. A vehicle comprising a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, the processor implementing the on-board software version information synchronization method of any one of claims 1 to 7 when executing the computer program.
10. An on-board software version information synchronization system, characterized by comprising a server and the vehicle of claim 9; and the server is used for storing the version information of the vehicle-mounted software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910391953.8A CN111935199B (en) | 2019-05-13 | 2019-05-13 | Vehicle-mounted software version information synchronization method, device and system and vehicle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910391953.8A CN111935199B (en) | 2019-05-13 | 2019-05-13 | Vehicle-mounted software version information synchronization method, device and system and vehicle |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111935199A true CN111935199A (en) | 2020-11-13 |
| CN111935199B CN111935199B (en) | 2023-07-25 |
Family
ID=73282520
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910391953.8A Active CN111935199B (en) | 2019-05-13 | 2019-05-13 | Vehicle-mounted software version information synchronization method, device and system and vehicle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111935199B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113194147A (en) * | 2021-04-29 | 2021-07-30 | 东风汽车集团股份有限公司 | Vehicle equipment information synchronization method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102902552A (en) * | 2011-07-26 | 2013-01-30 | 福特全球技术公司 | Method and apparatus for automatic module upgrade |
| CN104639600A (en) * | 2013-11-06 | 2015-05-20 | 通用汽车有限责任公司 | System and method for preparing vehicle for remote reflash event |
| CN105025058A (en) * | 2014-04-28 | 2015-11-04 | 广州汽车集团股份有限公司 | Vehicle remote diagnosis method, vehicle remote monitoring method and vehicle-mounted terminal |
| US9575743B1 (en) * | 2015-09-21 | 2017-02-21 | Hyundai Motor Company | Apparatus for updating software of vehicle terminal and software providing server |
| CN106484455A (en) * | 2015-09-02 | 2017-03-08 | 腾讯科技（深圳）有限公司 | A kind of methods, devices and systems of the installation data of more new application |
| CN107656752A (en) * | 2017-10-31 | 2018-02-02 | 北京新能源汽车股份有限公司 | A kind of method, apparatus and vehicle of vehicle control device software upgrading |
| CN108025684A (en) * | 2015-09-29 | 2018-05-11 | 日立汽车系统株式会社 | The information update system of on-vehicle control apparatus and on-vehicle control apparatus |
-
2019
- 2019-05-13 CN CN201910391953.8A patent/CN111935199B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102902552A (en) * | 2011-07-26 | 2013-01-30 | 福特全球技术公司 | Method and apparatus for automatic module upgrade |
| CN104639600A (en) * | 2013-11-06 | 2015-05-20 | 通用汽车有限责任公司 | System and method for preparing vehicle for remote reflash event |
| CN105025058A (en) * | 2014-04-28 | 2015-11-04 | 广州汽车集团股份有限公司 | Vehicle remote diagnosis method, vehicle remote monitoring method and vehicle-mounted terminal |
| CN106484455A (en) * | 2015-09-02 | 2017-03-08 | 腾讯科技（深圳）有限公司 | A kind of methods, devices and systems of the installation data of more new application |
| US9575743B1 (en) * | 2015-09-21 | 2017-02-21 | Hyundai Motor Company | Apparatus for updating software of vehicle terminal and software providing server |
| CN108025684A (en) * | 2015-09-29 | 2018-05-11 | 日立汽车系统株式会社 | The information update system of on-vehicle control apparatus and on-vehicle control apparatus |
| CN107656752A (en) * | 2017-10-31 | 2018-02-02 | 北京新能源汽车股份有限公司 | A kind of method, apparatus and vehicle of vehicle control device software upgrading |
Non-Patent Citations (1)
| Title |
|---|
| 陈铭军，王天军，叶则南，毛晨轩: "工厂模式下模块化整车在线刷新技术", 《上海汽车》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113194147A (en) * | 2021-04-29 | 2021-07-30 | 东风汽车集团股份有限公司 | Vehicle equipment information synchronization method and system |
| CN113194147B (en) * | 2021-04-29 | 2022-04-29 | 东风汽车集团股份有限公司 | Vehicle equipment information synchronization method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111935199B (en) | 2023-07-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108011904B (en) | Information sending method, receiving method, device and information receiving and sending system | |
| CN111930407B (en) | Vehicle ECU software upgrading method and system, vehicle TBOX microcontroller and SOC terminal | |
| US11032300B2 (en) | Intrusion detection system based on electrical CAN signal for in-vehicle CAN network | |
| US9705699B2 (en) | Method and apparatus for reducing load in can communication | |
| US20220156057A1 (en) | In-vehicle update device, update processing program, and program update method | |
| CN111010415A (en) | Data transmission method and device for Internet of vehicles | |
| US11288054B2 (en) | Vehicular communication system | |
| US11444891B2 (en) | Electronic control unit, abnormality determination program, and abnormality determination method | |
| CN113285861A (en) | Vehicle data acquisition method based on intelligent central gateway | |
| CN110731089B (en) | Data transmission device, data transmission method for vehicle and vehicle | |
| CN113872840A (en) | CAN data acquisition and transmission method, device and vehicle-mounted terminal | |
| CN111301317A (en) | Event generation method, event generation device and vehicle-mounted equipment | |
| CN111935199B (en) | Vehicle-mounted software version information synchronization method, device and system and vehicle | |
| CN113409488A (en) | Data processing method and device, vehicle-mounted terminal and automobile | |
| CN112929251A (en) | CAN-based slave station data refreshing method, device and system | |
| CN116456301A (en) | Program refreshing method, device, equipment and storage medium | |
| CN114463930B (en) | Alarm event processing method and device, electronic equipment and medium | |
| CN112003867B (en) | Communication method of vehicle-mounted T-BOX and cloud server and related equipment | |
| CN110177032B (en) | Message routing quality monitoring method and gateway controller | |
| CN114170705A (en) | Vehicle data uploading method, device and equipment | |
| US20210370961A1 (en) | Ecu, monitoring ecu, and can system | |
| CN113806131A (en) | Access control method and device for fault code library, electronic equipment and storage medium | |
| WO2020105657A1 (en) | Onboard relay device and relay method | |
| CN115412588B (en) | Method and device for remotely updating configuration file and electronic equipment | |
| CN116896745A (en) | Information acquisition method, system, device and electronic equipment |
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 |