CN111935199B - 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 PDF

Info

Publication number
CN111935199B
CN111935199B CN201910391953.8A CN201910391953A CN111935199B CN 111935199 B CN111935199 B CN 111935199B CN 201910391953 A CN201910391953 A CN 201910391953A CN 111935199 B CN111935199 B CN 111935199B
Authority
CN
China
Prior art keywords
vehicle
software
version information
mounted software
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
CN201910391953.8A
Other languages
Chinese (zh)
Other versions
CN111935199A (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.)
Guangzhou Automobile Group Co Ltd
Original Assignee
Guangzhou Automobile Group 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 Guangzhou Automobile Group Co Ltd filed Critical Guangzhou Automobile Group Co Ltd
Priority to CN201910391953.8A priority Critical patent/CN111935199B/en
Publication of CN111935199A publication Critical patent/CN111935199A/en
Application granted granted Critical
Publication of CN111935199B publication Critical patent/CN111935199B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • 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 
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (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 a vehicle by external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance; responding to the monitoring of the software refreshing event, and acquiring the updated vehicle-mounted software version information of the vehicle-mounted software by the external terminal equipment; and uploading the version information of the vehicle-mounted software 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 timely synchronized, the influence on the vehicle-mounted network caused by the periodical reading of the version information by the vehicle-mounted terminal is avoided, and excessive occupation of resources for transmitting and receiving information by the vehicle-mounted terminal is not required.

Description

Vehicle-mounted software version information synchronization method, device and system and vehicle
Technical Field
The present invention relates to the field of vehicle software technologies, and in particular, to a method, an apparatus, a system, and a vehicle for synchronizing version information of vehicle software.
Background
The software update of the vehicle-mounted software in the vehicle is usually carried out by adopting an after-sales diagnostic apparatus, and after the vehicle updates the vehicle-mounted software, the mode of synchronizing version information of the vehicle-mounted software by the server is as follows: the server periodically sends instructions to the vehicle-mounted terminal to acquire version information, the vehicle-mounted terminal sends diagnosis commands to read the version information of each node of the vehicle-mounted software and upload the version information to the server, and the server compares the acquired version information with locally stored version information and correspondingly updates the software upgrading package and the version information on the server if updating exists. The vehicle-mounted terminal periodically reads version information no matter whether the version is updated or not, so that the transmission and receiving resources of the vehicle-mounted terminal are occupied; because of periodic inquiry, version information synchronization cannot be performed timely, and only periodic synchronization is possible; and the periodic inquiry brings certain load to the network inside and outside the vehicle, influences the normal operation of the whole vehicle network, even causes network paralysis and brings certain potential safety hazard.
Disclosure of Invention
The embodiment of the invention aims to provide a vehicle-mounted software version information synchronization method, device and system and a vehicle, which can timely synchronize version information, avoid the influence on a vehicle-mounted network caused by periodic reading of version information by a vehicle-mounted terminal, and avoid excessive occupation of resources for transmitting 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 software, including:
monitoring a software refreshing event generated by updating vehicle-mounted software of a vehicle by external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
responding to the monitoring of the software refreshing event, and acquiring the updated vehicle-mounted software version information of the vehicle-mounted software by the external terminal equipment;
and 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 method disclosed by the embodiment of the invention is characterized in that firstly, a software refreshing event generated by updating the vehicle-mounted software of the vehicle by the external terminal equipment is monitored; and then when the software refreshing event is responded, acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software, and finally uploading the vehicle-mounted software version information to a server for storage, so that the server can timely synchronize the vehicle-mounted software version information. 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 is not required to be periodically queried, but the corresponding version information of the vehicle-mounted software is directly acquired and uploaded to the server in time when the vehicle-mounted software is updated, the version information of each vehicle-mounted software on the vehicle is not required to be periodically read by the vehicle-mounted terminal, the influence on the vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted terminal is avoided, the resources for transmitting and receiving the information by the vehicle-mounted terminal are not required to be excessively occupied, and the network flow is saved.
As an improvement of the above solution, the monitoring the software refreshing event generated by the update of the vehicle software by the external terminal device 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 carrying the software refreshing event identification code is detected, judging that the occurrence of the software refreshing event is monitored.
As an improvement of the above solution, the responding to the detection of the software refreshing event, obtaining the vehicle software version information updated by the external terminal device for the vehicle 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 updating identification information, and acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software according to the software version information acquisition instruction.
As an improvement of the above solution, 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:
responding to the monitoring of the software refreshing event, taking a preset mark 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 mark position is a first value, uploading updated identification information corresponding to the software refreshing event to the server, and enabling the mark position to be a second value.
As an improvement of the above scheme, the timing of detecting the flag bit is set as follows:
when the whole car is electrified.
As an improvement of the above scheme, the vehicle-mounted software is ECU software, and the updated identification information is an identification code of an ECU of the vehicle, which is updated by the ECU software.
As an improvement of the above-described aspect, the timing of setting the flag position to the second value is set as:
and when receiving a response instruction returned by the server according to the received updated identification information.
In order to achieve the above object, another embodiment of the present invention provides a vehicle-mounted software version information synchronization device, 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 the external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
the version information acquisition module is used for responding to the detection of the software refreshing event and acquiring the version information of the vehicle-mounted software 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 has the advantages that firstly, the software refreshing event monitoring module monitors a software refreshing event generated by updating vehicle-mounted software of a vehicle by external terminal equipment; and then when the software refreshing event is monitored, the version information acquisition module acquires the version information of the vehicle-mounted software updated by the external terminal equipment, and finally the version information uploading module uploads the version information of the vehicle-mounted software to a server for storage, so that the server can timely synchronize the version information of the vehicle-mounted software. 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 is not required to be periodically queried, but the corresponding version information of the vehicle-mounted software is directly acquired and timely uploaded to the server when the vehicle-mounted software is updated, the version information of each vehicle-mounted software on the vehicle is not required to be periodically read by the vehicle-mounted software version information synchronizing device, the influence on the vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted software version information synchronizing device is avoided, the resources for transmitting and receiving the information by the vehicle-mounted software version information synchronizing device are not required to be excessively occupied, and the network flow is saved.
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, where the processor executes the computer program to implement the method for synchronizing version information of on-board software according to any one of the embodiments.
In order to achieve the above object, another embodiment of the present invention provides a vehicle-mounted software version information synchronization system, which includes a server and a vehicle as described in the above embodiment; 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 vehicle-mounted software according to an embodiment of the present invention;
FIG. 2 is a flowchart of another method for synchronizing version information of vehicle-mounted software according to an embodiment of the present invention;
FIG. 3 is a block diagram of a device for synchronizing version information of vehicle-mounted software according to an embodiment of the present invention;
FIG. 4 is a schematic view of a vehicle according to an embodiment of the present invention;
fig. 5 is a block diagram of a vehicle software version information synchronization system according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Example 1
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; comprising the following steps:
s1, monitoring a software refreshing event generated by updating vehicle-mounted software of a vehicle by external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
s2, responding to the monitoring of the software refreshing event, and acquiring the version information of the vehicle-mounted software updated by the external terminal equipment;
and S3, uploading the version information of the vehicle-mounted software to a server for storage.
It should be noted that, the method for synchronizing version information of vehicle-mounted software in the embodiment of the invention can be implemented by a vehicle-mounted terminal in a vehicle, wherein the vehicle-mounted terminal is front-end equipment of a vehicle monitoring 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 may be an automotive diagnostic instrument or other device capable of updating on-board software in the 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 the external terminal equipment for updating the vehicle-mounted software of the vehicle, 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 a server for storage, so that the server can timely synchronize the vehicle-mounted software version information. 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 queried, but the corresponding version information of the vehicle-mounted software is directly acquired when the vehicle-mounted software is updated, so that the resources for transmitting and receiving the information of the vehicle-mounted terminal are not occupied too much, and the network flow is saved.
Specifically, in step S1, the monitoring the software refreshing event generated by the update of the vehicle software of the vehicle by the external terminal device includes:
s11, 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 S12, when the operation message is monitored and the message carrying the software refreshing event identification code is detected, judging that the occurrence of the software refreshing event is monitored.
Specifically, when the vehicle has the vehicle-mounted software in the vehicle and is updated, the vehicle generates a message carrying the software refreshing event identification code, so that whether the occurrence of the software refreshing event is monitored can be determined by monitoring the operation message in the vehicle-mounted network.
Preferably, after the operation message in the vehicle-mounted network is monitored, before the operation message is monitored and the operation message is detected to carry the software refreshing event identification code, the method further includes: when the operation message is monitored and the head in the message is detected to carry a diagnosis message identification code, judging the current message as 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 the diagnosis message is detected to carry 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 adopting a UDS protocol, and the identification code of the diagnosis message is 7 or 1. Of course, the diagnostic message identifier may be other values, which are not described in detail herein.
After the current message is determined to be a diagnostic message, since the diagnostic message covers a conventional diagnostic event and a software refreshing event, it is necessary to further determine whether the diagnostic message indicates the occurrence of the software refreshing 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 "6EF1 84", that is, the operation message may be "7XX XX 6E F1 84XX XX XX XX". It should be noted that, the software refreshing event identification code may be replaced by other identification codes in the software refreshing process, and the software refreshing event identification code may also be set to other values, so long as the software refreshing event can be uniquely identified, which is within the protection scope of the present invention.
Specifically, in step S2, the responding to the monitoring of the software refreshing event, obtaining the vehicle software version information updated by the external terminal device for the vehicle software, includes:
s21, in response to the detection of the software refreshing event, uploading update identification information corresponding to the software refreshing event to the server;
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 updated by the external terminal equipment on the vehicle-mounted software according to the software version information acquisition instruction.
Preferably, the vehicle-mounted software is ECU software, and the updated identification information is an identification code of an ECU updated by the vehicle-mounted ECU on the vehicle. Further, the identification code of the ECU updated by the vehicle software may be the identification code of the ECU carried in the operation message, for example, the identification code of the ECU is "7XX" in the operation message. Referring to table 1, table 1 is a format definition for the software refresh event.
Table 1 Format definition for software refresh event
Length (Byte) Description of the invention
1 Event number ID, fill 1
1 Number of ECUs
1 ECU coding 1
……
1 ECU encodes n
Preferably, step S21 specifically includes:
s211, responding to the monitoring of the software refreshing event, taking a preset mark position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event;
and S212, in response to the fact that the mark position is detected to be a first value, uploading updated identification information corresponding to the software refreshing event to the server, and enabling the mark position to be a second value.
Specifically, the flag bit is flag, the first value is 1, and the second value is 0. When the software refreshing event is responded and monitored, setting the flag to be 1, and acquiring and storing update identification information corresponding to the software refreshing event; and in response to the fact that the flag is 1, uploading updated identification information corresponding to the software refreshing event to the server, and setting the flag to 0.
In this embodiment, after the software refreshing event is monitored, by acquiring and storing the corresponding update identification information and setting the flag position to the first value, even if an accident occurs to the vehicle (for example, the vehicle cannot be normally connected with the server at present, or the vehicle is abnormally powered down, etc.), after the vehicle is recovered to be normal, the user can 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 be effectively ensured to update the updated version information of the vehicle-mounted software synchronously.
Preferably, the timing of detecting the flag bit is set as follows: when the whole car is electrified. Specifically, in view of real-time performance, the update identification information may be immediately uploaded to the server after the update identification information is acquired. However, the traffic is used every time the connection between the vehicle-mounted terminal and the server is established, if the updated identification information is immediately uploaded to the server after the vehicle-mounted terminal acquires the updated identification information, the connection between the vehicle-mounted terminal and the server needs to be established for a plurality of times, and the traffic of the vehicle-mounted terminal is wasted. Therefore, in order to achieve the purpose of saving current, the update identification information can be sent to the server only when the whole vehicle is electrified, and the national standard data are required to be uploaded to the server when the vehicle is electrified and started each time, so that the update identification information can be uploaded to the server while the international data are uploaded, and the traffic of the vehicle is saved.
When the whole vehicle is powered on, monitoring the marker bit, and when the marker bit is a first value, indicating that a software refreshing event occurs before the whole vehicle is powered on, and uploading update identification information corresponding to the software refreshing event to the server; and when the mark position is a second value, the fact that a software refreshing event does not occur before the whole vehicle is powered on is indicated.
Preferably, the timing of setting the flag position to the second value is set as: and when receiving a response instruction returned by the server according to the received updated identification information. And after receiving the updated identification information, the server returns a response instruction, and when receiving the response instruction, the server sets the mark position as a second value.
Further, the process of steps S1 to S2 may refer to fig. 2.
Specifically, in step S3, the version information of the vehicle-mounted software is uploaded to a server for storage, so that the server synchronously updates the version information of the vehicle-mounted software in the database. Further, the vehicle-mounted software version information can be uploaded to a server, and meanwhile, the vehicle-mounted software upgrading package corresponding to the vehicle-mounted software version information can be uploaded together, so that the server can update the vehicle-mounted software upgrading package in the database together. Then step S2 is: when the software refreshing event is responded, acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software and a vehicle-mounted software upgrading packet corresponding to the vehicle-mounted software version information; the step S3 is as follows: uploading the version information of the vehicle-mounted software and the upgrading package of the vehicle-mounted software 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 is characterized in that firstly, a software refreshing event generated by updating the vehicle-mounted software of the vehicle by the external terminal equipment is monitored; and then, when the software refreshing event is monitored, 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 queried 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 timely synchronize the vehicle-mounted software version information. 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 is not required to be periodically queried, but the corresponding version information of the vehicle-mounted software is directly acquired and uploaded to the server in time when the vehicle-mounted software is updated, the version information of each vehicle-mounted software on the vehicle is not required to be periodically read by the vehicle-mounted terminal, the influence on the vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted terminal is avoided, the resources for transmitting and receiving the information by the vehicle-mounted terminal are not required to be excessively occupied, and the network flow is saved.
Example two
Referring to fig. 3, fig. 3 is a block diagram of a vehicle-mounted software version information synchronization device 10 according to an embodiment of the present invention; comprising 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 the external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
the version information acquisition module 12 is configured to acquire version information of the vehicle-mounted software updated by the external terminal device in response to the detection of the 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 device 10 in 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 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 may be an automotive diagnostic instrument or other device capable of updating on-board software in the 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 carrying the software refreshing event identification code is detected, judging that the occurrence of the software refreshing event is monitored.
Specifically, when the vehicle has the vehicle-mounted software, the vehicle generates a message carrying the software refreshing event identification code when the vehicle is updated, and the software refreshing event monitoring module 11 can determine whether the occurrence of the software refreshing event is monitored by monitoring the operation message in the vehicle-mounted network.
Preferably, after the operation message in the vehicle-mounted network is monitored, before the operation message is monitored and the operation message is detected to carry the software refreshing event identification code, the method further includes: when the operation message is monitored and the head in the message is detected to carry a diagnosis message identification code, judging the current message as 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. And when the diagnosis message is detected to carry 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 adopting a UDS protocol, and the identification code of the diagnosis message 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 refreshing event, it is necessary to further determine whether the diagnostic message indicates the occurrence of the software refreshing event. At this time, whether the operation message carries a 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 "6EF1 84", that is, the operation message may be "7XX XX 6E F1 84XX XX XX XX". It should be noted that, the software refreshing event identification code may be replaced by other identification codes in the software refreshing process, so long as the software refreshing 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 updating identification information, and acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software according to the software version information acquisition instruction.
Preferably, the vehicle-mounted software is ECU software, and the updated identification information is an identification code of an ECU updated by the vehicle-mounted ECU on the vehicle. Further, the identification code of the ECU updated by the vehicle software may be the identification code of the ECU carried in the operation message, for example, the identification code of the ECU is "7XX" in the operation message.
Preferably, the responding to the monitoring of the software refreshing event uploads the update identification information corresponding to the software refreshing event to the server, and specifically includes:
responding to the monitoring of the software refreshing event, taking a preset mark 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 mark position is a first value, uploading updated identification information corresponding to the software refreshing event to the server, and enabling the mark position to be a second value.
Specifically, the flag bit is flag, the first value is 1, and the second value is 0. When the software refreshing event is responded and monitored, setting the flag to be 1, and acquiring and storing update identification information corresponding to the software refreshing event; and in response to the detection of flag=1, uploading update identification information corresponding to the software refreshing event to the server, and setting flag to 0.
Preferably, the timing of detecting the flag bit is set as follows: when the whole car is electrified. Specifically, in view of real-time performance, the update identification information may be immediately uploaded to the server after the update identification information is acquired. However, the traffic is used every time the connection between the vehicle-mounted terminal and the server is established, if the updated identification information is immediately uploaded to the server after the vehicle-mounted terminal acquires the updated identification information, the connection between the vehicle-mounted terminal and the server needs to be established for a plurality of times, and the traffic of the vehicle-mounted terminal is wasted. Therefore, in order to achieve the purpose of saving current, the update identification information can be sent to the server only when the whole vehicle is electrified, and the national standard data are required to be uploaded to the server when the vehicle is electrified and started each time, so that the update identification information can be uploaded to the server while the international data are uploaded, and the traffic of the vehicle is saved.
When the whole vehicle is powered on, monitoring the marker bit, and when the marker bit is a first value, indicating that a software refreshing event occurs before the whole vehicle is powered on, and uploading update identification information corresponding to the software refreshing event to the server; and when the mark position is a second value, the fact that a software refreshing event does not occur before the whole vehicle is powered on is indicated.
Preferably, the timing of setting the flag position to the second value is set as: and when receiving a response instruction returned by the server according to the received updated identification information. And after receiving the updated identification information, the server returns a response instruction, and when receiving the response instruction, the server sets the mark position as a second value.
Specifically, the version information uploading module 13 uploads the version information of the vehicle-mounted software to a server for saving, so that the server synchronously updates the version information of the vehicle-mounted software in the database. Further, the vehicle-mounted software version information can be uploaded to a server, and meanwhile, the vehicle-mounted software upgrading package corresponding to the vehicle-mounted software version information can be uploaded together, so that the server can update the vehicle-mounted software upgrading package in the database together. Then, when the software refreshing event is responded and monitored, vehicle-mounted software version information updated by the external terminal equipment and a vehicle-mounted software upgrading packet corresponding to the vehicle-mounted software version information are acquired; uploading the version information of the vehicle-mounted software and the upgrading package of the vehicle-mounted software 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 is characterized in that firstly, the software refreshing event monitoring module 11 monitors a software refreshing event generated by updating vehicle-mounted software of a vehicle by external terminal equipment; then, when the software refreshing event is detected, the version information obtaining module 12 obtains the version information of the vehicle-mounted software updated by the external terminal device, and finally the version information uploading module 13 uploads the version information of the vehicle-mounted software to a server for storage, so that the server can timely synchronize the version information of the vehicle-mounted software. 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 is not required to be periodically queried, but the corresponding version information of the vehicle-mounted software is directly acquired and timely uploaded to the server when the vehicle-mounted software is updated, the version information of each vehicle-mounted software on the vehicle is not required to be periodically read by the vehicle-mounted software version information synchronization device 10, the influence on a vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted software version information synchronization device 10 is avoided, the resources for transmitting and receiving the information by the vehicle-mounted software version information synchronization device 10 are not required to be excessively occupied, and the network flow is saved.
Example III
Referring to fig. 4, fig. 4 is a schematic structural view of a vehicle 20 according to an embodiment of the present invention; the vehicle 20 of this 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 implements the steps of the above-described embodiments of the method for synchronizing version information of the on-vehicle software, such as steps S1 to S3 shown in fig. 1, when executing the computer program. Alternatively, the processor 21 may perform the functions of the modules/units of the apparatus embodiments described above, such as the software refresh event monitoring module 11, when executing the computer program.
Illustratively, the computer program may be partitioned into one or more modules/units that are stored in the memory 22 and executed by the processor 21 to complete the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions for describing 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 acquisition module 12 and a version information uploading module 13, each of which specifically functions 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 the external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
the version information acquisition module 12 is configured to acquire version information of the vehicle-mounted software updated by the external terminal device in response to the detection of the 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 (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and the processor 21 is a control center of the vehicle 20, connecting various parts of the entire vehicle 20 using various interfaces and lines.
The memory 22 may be used to store the computer program and/or module, and the processor 21 may implement various functions of the vehicle 20 by executing or executing the computer program and/or module stored in the memory 22 and invoking data stored in the memory 22. The memory 22 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, the memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), at least one disk storage device, a Flash memory device, or other volatile solid-state storage device.
Wherein the integrated modules/units of the vehicle 20 may be stored in a computer readable storage medium if implemented in the form of software functional units and sold or used as a stand alone product. Based on such understanding, the present invention may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and the computer program may implement the steps of each of the method embodiments described above when executed by the processor 21. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth.
Example IV
Referring to fig. 5, fig. 5 is a block diagram illustrating a configuration of an on-board software version information synchronization system 30 according to an embodiment of the present invention; comprising a server 31 and a vehicle 20 as described in the third embodiment above; the server 31 is configured to store the version information of the vehicle-mounted software.
The working processes of the vehicle 20 and the server 31 refer to the working processes of the above embodiments, and are not described herein.
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 updating the vehicle-mounted software of the vehicle by the external terminal equipment; then, in response to the monitoring of the software refreshing event, the vehicle 20 acquires the vehicle-mounted software version information updated by the external terminal device on the vehicle-mounted software, and finally the vehicle 20 uploads the vehicle-mounted software version information to a server for storage, so that the server 31 timely synchronizes the vehicle-mounted software version information. According to the embodiment of the invention, when the server 31 needs to synchronize version information of the vehicle-mounted software, the vehicle 20 does not need to periodically query version information of the vehicle-mounted software, but directly acquires the corresponding version information of the vehicle-mounted software and uploads the version information to the server in time when the vehicle-mounted software is updated, the vehicle-mounted terminal does not need to periodically read the version information of each vehicle-mounted software on the vehicle, the influence on a vehicle-mounted network caused by the periodic reading of the version information by the vehicle-mounted terminal is avoided, the resources for transmitting and receiving the information by the vehicle-mounted terminal are not excessively occupied, and the network flow is saved.
It should be noted that the above-described apparatus embodiments are merely illustrative, and the units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, in the drawings of the embodiment of the device provided by the invention, the connection relation between the modules represents that the modules have communication connection, and can be specifically implemented as one or more communication buses or signal lines. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that changes and modifications may be made without departing from the principles of the invention, such changes and modifications are also intended to be within the scope of the invention.

Claims (7)

1. The vehicle-mounted software version information synchronization method is characterized by comprising the following steps of:
monitoring a software refreshing event generated by updating vehicle-mounted software of a vehicle by external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
responding to the monitoring of the software refreshing event, and acquiring the updated vehicle-mounted software version information of the vehicle-mounted software by the external terminal equipment;
uploading the version information of the vehicle-mounted software to a server for storage;
the responding to the monitoring of the software refreshing event, obtaining the vehicle-mounted software version information updated by the external terminal device on the vehicle-mounted software, includes:
responding to the monitoring of the software refreshing event, taking a preset mark position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event; the vehicle-mounted software is ECU software, and the updated identification information is an identification code of an ECU updated by the ECU software on the vehicle;
in response to monitoring that the flag position is a first value, uploading updated identification information corresponding to the software refreshing event to the server, and taking the flag position as a second value;
and receiving a software version information acquisition instruction sent by the server according to the updating identification information, and acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software according to the software version information acquisition instruction.
2. The method for synchronizing version information of vehicle-mounted software according to claim 1, wherein the monitoring the event of refreshing the vehicle-mounted software of the vehicle by the external terminal device comprises:
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 carrying the software refreshing event identification code is detected, judging that the occurrence of the software refreshing event is monitored.
3. The method for synchronizing version information of vehicle-mounted software according to claim 1, wherein the timing of detecting the flag bit is set as follows:
when the whole car is electrified.
4. The method for synchronizing version information of vehicle-mounted software according to claim 1, wherein the timing for setting the flag position to the second value is set as:
and when receiving a response instruction returned by the server according to the received updated identification information.
5. An on-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 the external terminal equipment; the external terminal device is used for locally updating the vehicle-mounted software of the vehicle through a vehicle-mounted software updating program stored in advance;
the version information acquisition module is used for responding to the detection of the software refreshing event and acquiring the version information of the vehicle-mounted software updated by the external terminal equipment;
the version information uploading module is used for uploading the version information of the vehicle-mounted software to a server for storage;
the version information acquisition module is specifically configured to:
responding to the monitoring of the software refreshing event, taking a preset mark position as a first value, and acquiring and storing update identification information corresponding to the software refreshing event; the vehicle-mounted software is ECU software, and the updated identification information is an identification code of an ECU updated by the ECU software on the vehicle;
in response to monitoring that the flag position is a first value, uploading updated identification information corresponding to the software refreshing event to the server, and taking the flag position as a second value;
and receiving a software version information acquisition instruction sent by the server according to the updating identification information, and acquiring the vehicle-mounted software version information updated by the external terminal equipment on the vehicle-mounted software according to the software version information acquisition instruction.
6. 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 according to any one of claims 1 to 4 when executing the computer program.
7. A vehicle-mounted software version information synchronization system, which is characterized by comprising a server and the vehicle according to claim 6; the server is used for storing the version information of the vehicle-mounted software.
CN201910391953.8A 2019-05-13 2019-05-13 Vehicle-mounted software version information synchronization method, device and system and vehicle Active CN111935199B (en)

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 CN111935199A (en) 2020-11-13
CN111935199B true 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)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113194147B (en) * 2021-04-29 2022-04-29 东风汽车集团股份有限公司 Vehicle equipment information synchronization method and system

Citations (7)

* Cited by examiner, † Cited by third party
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

Patent Citations (7)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
Title
工厂模式下模块化整车在线刷新技术;陈铭军,王天军,叶则南,毛晨轩;《上海汽车》;20180910(第9期);全文 *

Also Published As

Publication number Publication date
CN111935199A (en) 2020-11-13

Similar Documents

Publication Publication Date Title
CN108537916B (en) Block chain-based driving record information processing method and device
CN108011904B (en) Information sending method, receiving method, device and information receiving and sending system
DE112019004032T5 (en) CENTRAL DEVICE, DISTRIBUTION PACKAGE GENERATION METHOD AND DISTRIBUTION PACKAGE GENERATION PROGRAM
CN112233278A (en) Remote fault analysis method, vehicle-mounted terminal, server, device and medium
US11288054B2 (en) Vehicular communication system
US11282541B2 (en) Record control apparatus
CN110731089B (en) Data transmission device, data transmission method for vehicle and vehicle
JP2006256457A (en) On-vehicle data management device, and vehicular information supplying system
CN111935199B (en) Vehicle-mounted software version information synchronization method, device and system and vehicle
CN110995823B (en) Vehicle-mounted terminal offline processing method, device, storage medium and device
CN113872840A (en) CAN data acquisition and transmission method, device and vehicle-mounted terminal
CN104104568A (en) Method, device and system for acquiring data from communication bus
CN114667502A (en) In-vehicle update device, program, and update method for program
CN104331948B (en) Tachographs upgrade information sending method, method of reseptance, apparatus and system
CN111049717A (en) Variable acquisition method and equipment
CN110177032B (en) Message routing quality monitoring method and gateway controller
JP2023519510A (en) Method and system for collecting and managing vehicle-generated data
KR20220139759A (en) System for managing update of ecu in vehicle and method thereof
CN112991573B (en) Data opening method and related device for automobile data recorder
CN116434375B (en) Combined bus data recorder and automobile
CN110377309B (en) Data recovery method, system and equipment
CN115242575B (en) Packet processing method, device, equipment and storage medium based on CANFD network
CN116405882B (en) Vehicle position tracking method and device, storage medium and vehicle
CN110472001B (en) Information sharing method, device, equipment and storage medium
CN118316706A (en) Vehicle data acquisition method, device and system, gateway equipment and vehicle

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