CN112040443A - Multi-client OTA upgrade processing method and system - Google Patents

Multi-client OTA upgrade processing method and system Download PDF

Info

Publication number
CN112040443A
CN112040443A CN202010895320.3A CN202010895320A CN112040443A CN 112040443 A CN112040443 A CN 112040443A CN 202010895320 A CN202010895320 A CN 202010895320A CN 112040443 A CN112040443 A CN 112040443A
Authority
CN
China
Prior art keywords
client
server
clients
vehicle
ota
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.)
Pending
Application number
CN202010895320.3A
Other languages
Chinese (zh)
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.)
Jingwei Hengrun Tianjin Research And Development Co ltd
Original Assignee
Jingwei Hengrun Tianjin Research And Development 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 Jingwei Hengrun Tianjin Research And Development Co ltd filed Critical Jingwei Hengrun Tianjin Research And Development Co ltd
Priority to CN202010895320.3A priority Critical patent/CN112040443A/en
Publication of CN112040443A publication Critical patent/CN112040443A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • 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/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • H04W8/245Transfer of terminal data from a network towards a terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention provides a multi-client OTA (over the air) upgrading method and a multi-client OTA upgrading system. The upgrading information is synchronously displayed through the plurality of client sides, so that a driver can conveniently grasp the upgrading process, and the user experience is improved. Different clients have different priorities, and after receiving different reply messages returned by different clients in the plurality of clients aiming at the same OTA upgrade message, the server executes the processing process corresponding to the reply message returned by the client with the highest priority, so that each client displays the same progress or state.

Description

Multi-client OTA upgrade processing method and system
Technical Field
The invention relates to the technical field of vehicle Over The Air (OTA) upgrading, in particular to a multi-client OTA upgrading processing method and system.
Background
OTA vehicle upgrade refers to a mode of upgrading a vehicle system by downloading a data packet through a wireless network. An existing vehicle OTA upgrading scheme is that a vehicle-mounted Telematics (TBOX) is directly connected with an OTA cloud server, and is specifically shown in fig. 1; an upgraded version of an Electronic Control Unit (ECU) is downloaded to TBOX, and then an upgrade of the EC U is performed. According to the existing upgrading scheme, the upgrading version of the ECU is directly downloaded to the vehicle-mounted TBOX, a vehicle with a Human Machine Interface (HMI) displays upgrading information through the HMI, a driver can control the upgrading progress and process in the vehicle, but the driver cannot control the upgrading progress and process when the vehicle without the HMI or the driver is not in the vehicle, and user experience is poor.
Disclosure of Invention
In view of this, the present invention provides a multi-client OTA upgrade processing method and system, which are intended to perform OTA upgrade processing by multiple clients, so as to facilitate drivers to grasp the upgrade process and improve user experience.
In order to achieve the above object, the following solutions are proposed:
in a first aspect, a multi-client OTA upgrade processing method is provided, including:
after receiving OTA upgrading information uploaded by a vehicle-mounted TBOX, a server respectively sends the OTA upgrading information to a plurality of clients corresponding to the same vehicle, wherein the plurality of clients comprise at least two clients of a vehicle client, a mobile client and a web client, and different clients have different priorities;
and after receiving different reply messages returned by different clients aiming at the same OTA upgrading message, the server executes a processing process corresponding to the reply message returned by the client with the highest priority.
Optionally, the OTA upgrade message includes:
downloading progress, downloading result, flashing progress and flashing result.
Optionally, the server and the plurality of clients and/or the server and the vehicle-mounted TBOX communicate with each other through two communication links, one of the two communication links is used for transmitting files, and the other is used for transmitting control instructions.
Optionally, the server and the plurality of clients, and/or the server and the vehicle-mounted TBOX ensure that the communication link is alive through a heartbeat synchronization mechanism.
Optionally, the server and the plurality of clients, and the server and the vehicle-mounted TBOX, perform remote communication using a request response model or a subscription push model.
In a second aspect, a multi-client OTA upgrade processing system is provided, including: the system comprises a server and a plurality of clients corresponding to the same vehicle, wherein the clients comprise at least two clients of a vehicle machine client, a mobile client and a web client, and different clients have different priorities;
the server is used for respectively sending the OTA upgrading information to the plurality of clients after receiving the OTA upgrading information uploaded by the vehicle-mounted TBOX;
and executing a processing process corresponding to the reply information returned by the client with the highest priority after receiving different reply information returned by different clients in the plurality of clients aiming at the same OTA upgrade information.
Optionally, the OTA upgrade message includes:
downloading progress, downloading result, flashing progress and flashing result.
Optionally, the server and the plurality of clients and/or the server and the vehicle-mounted TBOX communicate with each other through two communication links, one of the two communication links is used for transmitting files, and the other is used for transmitting control instructions.
Optionally, the server and the plurality of clients, and/or the server and the vehicle-mounted TBOX ensure that the communication link is alive through a heartbeat synchronization mechanism.
Optionally, the server and the plurality of clients, and the server and the vehicle-mounted TBOX, perform remote communication using a request response model or a subscription push model.
Compared with the prior art, the technical scheme of the invention has the following advantages:
according to the technical scheme, the multi-client OTA upgrading processing method and system comprise the steps that after receiving OTA upgrading information uploaded by a vehicle-mounted TBOX, a server sends the OTA upgrading information to a plurality of clients corresponding to the same vehicle respectively, and the clients comprise at least two clients of a vehicle machine client, a mobile client and a web client. The upgrading information is synchronously displayed through the plurality of client sides, so that a driver can conveniently grasp the upgrading process, and the user experience is improved. Different clients have different priorities, and after receiving different reply messages returned by different clients in the plurality of clients aiming at the same OTA upgrade message, the server executes a processing process corresponding to the reply message returned by the client with the highest priority. Therefore, when the progress or the state displayed by different clients is not uniform due to the external communication environment or other conditions, the server can display the same progress or state according to the processing process corresponding to the reply information returned by the client with the highest priority.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic diagram of an OTA upgrade scheme for a vehicle according to an embodiment of the present invention;
fig. 2 is a flowchart of a multi-client OTA upgrade processing method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of two communication links provided by an embodiment of the present invention;
FIG. 4 is a schematic diagram of interaction logic between a server and a client according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an OTA cloud processing upgrade progress provided in the embodiment of the present invention;
fig. 6 is a schematic diagram of an OTA upgrade process of a mobile client 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.
Referring to fig. 2, the multi-client OTA upgrade processing method provided in this embodiment includes the following steps:
s21: and after receiving the OTA upgrading information uploaded by the vehicle-mounted TBOX, the server respectively sends the OTA upgrading information to a plurality of clients corresponding to the same vehicle.
In the invention, the vehicle-mounted TBOX is in communication connection with the server, and the vehicle-mounted TBOX downloads the upgraded version of the relevant ECU from the server so as to upgrade the ECU. The vehicle-mounted TBOX sends a downloading progress to a server in the process of downloading the upgrading version of the ECU; after the vehicle-mounted TBOX finishes downloading, the downloading result is sent to a server; in the process of flashing the ECU by using the downloaded upgrade version, sending the flashing progress to a server; and after the flash is finished, sending the flash result to the server.
In the invention, the OTA upgrading information comprises a downloading progress, a downloading result, a flashing progress, a flashing result and the like, and the server sends the received OTA upgrading information to a plurality of clients corresponding to the same vehicle, so that the OTA upgrading information is displayed by the clients, and a driver can conveniently grasp the upgrading process. The multiple clients comprise at least two clients of a vehicle client, a mobile client and a web client, and different clients have different priorities. The vehicle machine client is a client installed on the vehicle-mounted HMI; the mobile client is a client installed on a mobile phone or a tablet computer; the web client is a web browser in a computer such as a desktop computer or a notebook computer.
In the invention, each vehicle corresponds to a plurality of clients. The method comprises the steps that mapping relations between a vehicle and a plurality of corresponding clients are established in a server in advance; for a plurality of clients corresponding to a certain vehicle, each client has a different priority. When the on-vehicle TBOX uploads the OTA upgrade information, the identification information of the vehicle is uploaded at the same time, so that the server can match a plurality of corresponding clients according to the identification information of the vehicle, where the plurality of matched clients are the clients corresponding to the same vehicle in step S21.
S22: and after receiving different reply messages returned by different clients aiming at the same OTA upgrading message, the server executes a processing process corresponding to the reply message returned by the client with the highest priority.
Specifically, when the server sends the OTA upgrade information to the clients as a download progress or a flash progress, the reply information returned by the clients is the progress information displayed by the clients, and if the progress information displayed by the clients is different, the progress information returned by the client with the highest priority is sent to the clients, so that the progress information displayed by the clients is synchronized.
When the server sends OTA upgrading information to a plurality of clients as a downloading result or a flashing result, the client receiving the information can display a plurality of options to a user; and if the instruction information returned by different clients is different, the server carries out corresponding processing according to the instruction information returned by the client with the highest priority. For example, when the download result is received as a successful download, the client displays options such as 'confirm', 'cancel', and 'delay' for the user to select, so that the user can confirm the upgrade, cancel the upgrade, or delay the upgrade; the instruction information returned by different clients may be the same or different, if the returned instruction information is not completely consistent, and the instruction information returned by the client with the highest priority is 'confirmed', an upgrade starting instruction is sent to the vehicle-mounted TBOX, and the instruction information returned by the clients with other priorities is not executed.
In addition, currently, if reply messages of different upgrading messages are uploaded by a plurality of clients, the server inserts the messages into a message queue according to time and then triggers the messages in sequence.
In some embodiments, the server communicates with the plurality of clients and with the onboard TBOX via two communication links, one of the two communication links being used to transfer files, e.g., the onboard TBOX downloads an upgraded version of the relevant ECU from the server via the communication link that transfers files; the other communication link is used for transmitting a control command, for example, the on-board TBOX sends OTA upgrade information such as a download progress, a download result, a refresh progress and a refresh result to the server through the communication link for transmitting the control command, which is specifically shown in fig. 3. It is ensured that the transmission of the download data and the transmission of the control instructions do not influence each other.
In some embodiments, the communication link is guaranteed to survive by a heartbeat synchronization mechanism between the server and the plurality of clients, and/or between the server and the onboard TBOX. When the request response model is adopted for remote communication, the specific steps of ensuring the survival of the communication link through the heartbeat synchronization mechanism are as follows: and after the communication verification is completed between the client and the server, the client sends heartbeat messages according to the configured period to keep the communication link alive. If the heartbeat message is sent, service communication is carried out by suspending the heartbeat message sending process if service communication requirements exist, and the heartbeat message is sent according to a configured period to keep the communication link alive after the service communication is finished. And the client side performs timing after sending the heartbeat message, judges whether the server responds to the heartbeat message within preset time, and if the server does not respond, the client side is connected with the server again to ensure that the client side does not lose contact. And if the server does not respond within the preset time when the client and the server are in service communication, the client resends the request message.
When a subscription push model is adopted for remote communication, the specific steps of ensuring the survival of a communication link through a heartbeat synchronization mechanism are as follows: after the server pushes a message to the client, the client needs to reply a confirmation message to ensure that the pushed message arrives accurately; the server starts timing after sending the push message to the client, records the push failure if the confirmation message replied by the client is not received within the preset time, and then carries out the push again after delaying for a certain time.
The process of ensuring the survival of the communication link between the server and the vehicle-mounted TBOX through the heartbeat synchronization mechanism is consistent with the process of ensuring the survival of the communication link between the server and the client through the heartbeat synchronization mechanism, which is not described in detail herein. The remote communication in the invention comprises two communication models, wherein a subscription pushing model is used when the server pushes the new upgrade task reminder, and other communication processes use a request response model.
In some embodiments, the remote communication protocol is an application layer protocol in OSI (Open System interconnection Reference Model), and the network protocol carrying the application layer protocol is a standard protocol such as TCP/IP or HTTP. When no special indication is given in the related message transmission in the OTA upgrading process, a Big end (Big Endian) mode is adopted and Bit0 is LSB (Least Significant Bit) in a Byte. The entity of the remote communication message in the OTA upgrade process is JSON (JavaScript Object notification, a lightweight data exchange format), which contains two major parts, signal and payload. The SIGNATURE part represents a SIGNATURE to verify that the message has not been altered throughout the process, and it can also verify the true identity of the sender for a token signed with a private key. The payload part contains a message header and data; the payload section is used to describe the information to be declared using a JSON-formatted string, and is classified into three categories, registered, public, and private.
The server mainly executes the following processes in the OTA upgrading process:
1) and receiving network connection of a plurality of clients and the vehicle-mounted TBOX, wherein the plurality of clients comprise a vehicle machine client, a mobile client, a web client and the like.
2) Receiving application messages sent by a vehicle-mounted TBOX and a client; for example, when the OTA is upgraded, OTA upgrading information sent by the vehicle-mounted TBOX comprises a downloading progress, a downloading result, a flashing progress, a flashing result and the like.
3) Requests to subscribe and unsubscribe to clients are processed. The client subscription means that after the server and the client establish connection, the client subscribes a communication topic which is interested in the client; and canceling the subscription, namely, not accepting the message sent by the previously subscribed topic.
4) The application message is forwarded to the clients meeting the conditions, namely after the server receives OTA upgrading information uploaded by the vehicle-mounted TBOX, the OTA upgrading information is respectively sent to the clients meeting the conditions; referring to fig. 4, after the vehicle state information is uploaded by the vehicle-mounted TBOX, the server verifies the uploaded information, and after the verification is passed, the information is respectively sent to the three clients, and the clients display corresponding control options for the user to select after receiving the vehicle state information; and the server receives the control command returned by each client. After the vehicle-mounted TBOX uploads the brushing progress information, the server verifies the uploaded information, the information is respectively sent to the three client sides after the verification is passed, and the client sides can display the brushing progress information after receiving the brushing progress information; and the server receives the display state of the brushing progress returned by each client.
After the OTA upgrading information is uploaded to the server by the vehicle-mounted TBOX, the server checks the information format, including checking whether the uploaded vin information is valid, checking the data format in the uploaded information, checking the data field format and the number in the uploaded information, checking whether the uploaded ECU information content is valid, checking whether the uploaded ECU version has a scalable version, and the like, and after the verification is qualified, the OTA upgrading information is uploaded to a streaming processing platform, and meanwhile, a new state is marked. And after uploading the OTA upgrading information to the streaming processing platform, the server creates an upgrading package installation state resetting command and sends the resetting state command to the vehicle-mounted TBOX. The streaming processing platform receives the OTA upgrading information, firstly stores the OTA upgrading information in a non-relational database, and then sends the OTA upgrading information to a front-end working platform. The front-end working platform is a plurality of clients such as a vehicle machine client, a mobile client, a web client and the like, and each client can refresh and display the OTA upgrading information received and store the OTA upgrading information in a respective database. The specific process is shown in FIG. 5.
The non-relational database is a set of data unstructured storage methods, stores data by using key value pairs, has high processing concurrency and high query speed, supports distributed clusters, and is more suitable for data processing and transmission of multiple clients.
5) The server stores the priorities of different clients; the priority of the client can be manually set in advance, and the server can grant the priority of different clients according to a preset priority setting rule. The server side can monitor the return state of each client side in real time, and distributes instructions according to the priority, and the messages in the same upgrading state or the messages in the same control instruction can be distributed to each client side by selecting the messages with high priority as processing results. The upgrading state message or the upgrading instruction is processed according to the priority, so that the display synchronization and instruction unification state can be recovered when display asynchronization or control instruction unification occurs in a plurality of clients. For example, the web client has the highest priority, and the priorities of the car machine client and the collection client are sequentially reduced. Firstly, a system administrator has the highest authority and can control the issuing of each upgrading task. In addition, safety is considered as the most main factor in the upgrading process, so that the state and the instruction of the driver client side can be processed preferentially in the upgrading process, each state of the vehicle machine can be obtained in real time, and the vehicle machine can be issued to other client sides. In addition, the setting of the priority is also configurable.
The client mainly executes the following processes in the OTA upgrading process:
1) the plurality of clients are connected to the server through network communication and establish two-way communication links, and the clients need to analyze the downloaded connection configuration file after logging in the OTA platform successfully and initiate connection according to the URL (Uniform Resource Locator) and the related configuration information of the server obtained from the client.
2) Subscribe to Topic, i.e. request to receive the relevant application message. After the client subscribes, the server can push related application messages to the client in time.
3) The client implements a polling policy. And each client periodically reports checksum to the server according to the appointed time. If the ECU upgrading task is reported once a month, whether a new ECU upgrading task exists is inquired, and meanwhile, the time period can be configured. checksum refers to information integrity check, if the transmitted data is not actual data, the data can be converted into md5 value, and then communication is performed; the server checks and judges whether the current ECU is effective or not and whether a new version needing to be upgraded exists or not according to the uploaded information, and if the new version needs to be upgraded, the server pushes the current upgrading task.
4) And the client queries an upgrading task according to pushing triggering, namely the server sends a pushing message to the corresponding client when detecting that the ECU needs upgrading.
5) Unsubscribing requests to remove received application messages while supporting disconnection from the server
6) And the server side communicates in real time and feeds back the current state to ensure that the progress of a plurality of clients is uniform.
Referring to fig. 6, taking a mobile client as an example, an OTA upgrade process is introduced, which specifically includes the following steps:
1) the mobile client sends a request for logging in an authorization server to a TSP (Telematics Service Provider) authority management cloud.
2) And the TSP permission management cloud terminal issues a successful login notification to the mobile client terminal.
3) The mobile client sends a request to the server to check if there is an update.
4) And after receiving a request for checking whether the updating is available or not, the server determines which ECUs corresponding to the current vehicle upgradable are available, and feeds back a list of the corresponding current vehicle upgradable ECUs to the mobile client.
5) And after the mobile client receives the current upgradable ECU list, displaying options for confirming upgrading for a user to select, and after the user selects upgrading, sending a request for confirming upgrading to the server by the mobile client.
6) And when receiving a request for confirming the upgrading of the mobile client, the server issues an upgrading task to the vehicle-mounted TBOX.
7) And after receiving the upgrading task issued by the server, the vehicle-mounted TBOX sends a notice indicating that the upgrading task exists to the vehicle-mounted client, so that the vehicle-mounted client indicates that the upgrading task exists, and a driver in the vehicle can know that the upgrading task exists through the vehicle-mounted client.
8) And after the vehicle-mounted TBOX receives the upgrading task issued by the server, the vehicle-mounted TBOX also feeds back vehicle-mounted information to the server.
9) And the server issues an upgraded version of the current upgradable ECU to the vehicle-mounted TBOX.
10) The server issues the downloading progress to the mobile client in real time, and the client displays the downloading progress in real time after receiving the downloading progress.
11) And after the vehicle-mounted TBOX finishes downloading the upgrade version of the current upgradable ECU, sending a downloading finish notice to the server.
12) And after receiving a download completion notification sent by the vehicle-mounted TBOX, the server sends an upgrade prompt to the mobile client.
13) And after receiving the upgrade prompt of the server, the mobile client sends a request for checking the vehicle state to the server.
14) The server sends an instruction for vehicle status check to the onboard TBOX.
15) The vehicle-mounted TBOX feeds back the current vehicle state to the server.
16) And the server transmits the current vehicle state to the mobile client.
17) When the current vehicle state is suitable for upgrading, the user can send an instruction for confirming the upgrading to the server through the mobile client.
18) The server sends an instruction to the TBOX to inform the OTA main program to start upgrading.
19) And the vehicle-mounted TBOX sends an instruction for displaying the upgrading progress to the vehicle-mounted client, and the vehicle-mounted client displays the upgrading progress in real time.
20) And uploading the upgrading progress to the server in real time by the vehicle-mounted TBOX.
21) And the server issues the upgrading progress to the mobile client in real time, and the mobile client displays the upgrading progress in real time.
22) And when the upgrade fails, the vehicle-mounted TBOX uploads a notice of the upgrade failure to the server.
23) And the server issues an upgrading failure instruction to the mobile client.
24) And after the user selects the upgrade rollback, the mobile client sends an upgrade rollback instruction to the server.
25) And the server issues an upgrade rollback instruction to the vehicle-mounted TBOX.
26) And after receiving the upgrading rollback instruction, the vehicle-mounted TBOX starts to execute the rollback operation, rolls back to the original version of the ECU, and uploads a rollback success notice to the server after the rollback is successful.
27) And the server transmits a notice of successful update rollback to the mobile client, and the mobile client displays that the rollback is successful.
Referring to fig. 3, the multi-client OTA upgrade processing system provided in this embodiment includes: the system comprises a server, a vehicle machine client, a mobile client and a web client, wherein different clients have different priorities.
And after receiving the OTA upgrading information uploaded by the vehicle-mounted TBOX, the server respectively sends the OTA upgrading information to the vehicle-mounted client, the mobile client and the web client. And after receiving different reply messages returned by different clients in the plurality of clients according to the same OTA upgrading message, the server executes a processing process corresponding to the reply message returned by the client with the highest priority.
An OTA upgrade message comprising: downloading progress, downloading result, flashing progress, flashing result and the like.
The server is communicated with the vehicle machine client, the mobile client and the web client, and/or the vehicle TBOX by two communication links, wherein one of the two communication links is used for transmitting files, and the other one is used for transmitting control instructions.
And ensuring the survival of communication links among the server, the vehicle machine client, the mobile client and the web client and/or among the vehicle TBOX of the server through a heartbeat synchronization mechanism.
And the server is remotely communicated with the vehicle machine client, the mobile client and the web client, and is remotely communicated with the vehicle-mounted TBOX by adopting a request response model or a subscription push model.
In this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are mainly described as different from other embodiments, the same and similar parts in the embodiments may be referred to each other, and the features described in the embodiments in the present description may be replaced with each other or combined with each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A multi-client OTA upgrade processing method is characterized by comprising the following steps:
after receiving OTA upgrading information uploaded by a vehicle-mounted TBOX, a server respectively sends the OTA upgrading information to a plurality of clients corresponding to the same vehicle, wherein the plurality of clients comprise at least two clients of a vehicle client, a mobile client and a web client, and different clients have different priorities;
and after receiving different reply messages returned by the plurality of clients aiming at the same OTA upgrading message, the server executes a processing process corresponding to the reply message returned by the client with the highest priority.
2. The method of claim 1, wherein the OTA upgrade message comprises:
downloading progress, downloading result, flashing progress and flashing result.
3. The multi-client OTA upgrade processing method according to claim 1, wherein the server communicates with the plurality of clients and/or the onboard TBOX via two communication links, one for transmitting files and the other for transmitting control commands.
4. The multi-client OTA upgrade processing method according to claim 1, wherein a heartbeat synchronization mechanism is used between the server and the plurality of clients and/or between the server and the on-board TBOX to ensure communication link survivability.
5. The multi-client OTA upgrade processing method according to claim 1, wherein remote communication between the server and the plurality of clients, and between the server and the onboard TBOX, is performed using a request-response model or a subscription-push model.
6. A multi-client OTA upgrade processing system is characterized by comprising: the system comprises a server and a plurality of clients corresponding to the same vehicle, wherein the clients comprise at least two clients of a vehicle machine client, a mobile client and a web client, and different clients have different priorities;
the server is used for respectively sending the O TA upgrading information to the plurality of clients after receiving OTA upgrading information uploaded by the vehicle-mounted TBOX;
and after receiving different reply messages returned by the plurality of clients aiming at the same OTA upgrading message, executing a processing process corresponding to the reply message returned by the client with the highest priority.
7. The client OTA upgrade processing system of claim 6, wherein said OTA upgrade message comprises:
downloading progress, downloading result, flashing progress and flashing result.
8. The multi-client OTA upgrade processing system according to claim 6, wherein the server communicates with the plurality of clients and/or the server communicates with the onboard TBOX via two communication links, one for transferring files and the other for transferring control commands.
9. The multi-client OTA upgrade processing system according to claim 6, wherein a heartbeat synchronization mechanism is used between the server and the plurality of clients and/or between the server and the onboard TBOX to ensure communication link survivability.
10. The multi-client OTA upgrade processing system according to claim 6, wherein remote communication between the server and the plurality of clients, and between the server and the onboard TBOX, is performed using a request response model or a subscription push model.
CN202010895320.3A 2020-08-31 2020-08-31 Multi-client OTA upgrade processing method and system Pending CN112040443A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010895320.3A CN112040443A (en) 2020-08-31 2020-08-31 Multi-client OTA upgrade processing method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010895320.3A CN112040443A (en) 2020-08-31 2020-08-31 Multi-client OTA upgrade processing method and system

Publications (1)

Publication Number Publication Date
CN112040443A true CN112040443A (en) 2020-12-04

Family

ID=73587758

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010895320.3A Pending CN112040443A (en) 2020-08-31 2020-08-31 Multi-client OTA upgrade processing method and system

Country Status (1)

Country Link
CN (1) CN112040443A (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112673586A (en) * 2020-12-08 2021-04-16 华为技术有限公司 Data packet processing method and device
CN112817631A (en) * 2021-01-29 2021-05-18 一汽解放汽车有限公司 Vehicle-mounted controller upgrading method, device, equipment and storage medium
CN112835616A (en) * 2021-02-26 2021-05-25 百度在线网络技术(北京)有限公司 Version upgrading method and device, electronic equipment and storage medium
CN113472884A (en) * 2021-06-30 2021-10-01 潍柴动力股份有限公司 OTA (over the air) upgrading method and device
CN113515247A (en) * 2021-05-19 2021-10-19 宝能(广州)汽车研究院有限公司 Upgrade progress display method, device, equipment and medium
CN113590164A (en) * 2021-08-31 2021-11-02 重庆长安汽车股份有限公司 Method and system for upgrading vehicle control unit software
CN114297259A (en) * 2021-12-28 2022-04-08 苏州智行畅联科技有限公司 Method and system for off-line query of vehicle-mounted system version, central control vehicle and storage medium
CN114546445A (en) * 2022-02-24 2022-05-27 重庆长安汽车股份有限公司 Finished automobile OTA controller upgrading system and method based on micro-service architecture
CN114979206A (en) * 2022-05-20 2022-08-30 重庆长安汽车股份有限公司 Vehicle OTA (over the air) upgrading system and method based on subscription and release mode
CN116382744A (en) * 2023-06-05 2023-07-04 成都赛力斯科技有限公司 Method, device, system and storage medium for parallel refreshing of multiple ECUs

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014173256A1 (en) * 2013-08-19 2014-10-30 中兴通讯股份有限公司 Download processing method and apparatus, client, and computer storage medium
WO2014177115A1 (en) * 2013-09-30 2014-11-06 中兴通讯股份有限公司 Mobile terminal application batch management method and system, and upgrade server
CN105653318A (en) * 2015-12-24 2016-06-08 北京奇虎科技有限公司 Software upgrade method, device and system
CN105959613A (en) * 2016-05-27 2016-09-21 山西百得科技开发股份有限公司 Digital conference equipment and system
CN107493186A (en) * 2016-12-23 2017-12-19 宝沃汽车(中国)有限公司 The remote update system and its control method of vehicle
CN108769226A (en) * 2018-06-05 2018-11-06 北京智行者科技有限公司 The OAT upgrade methods and car-mounted terminal of vehicle
CN109189419A (en) * 2018-07-27 2019-01-11 广州视源电子科技股份有限公司 Method for upgrading system, apparatus and system, server-side and client
CN109673001A (en) * 2019-02-12 2019-04-23 Oppo广东移动通信有限公司 Data transfer control method and Related product
CN110505124A (en) * 2018-05-17 2019-11-26 北京和居智能窗业科技有限公司 A kind of control method of intelligent window
CN110673864A (en) * 2019-08-28 2020-01-10 绿驰汽车科技集团有限公司 Upgrading monitoring method and system for vehicle-mounted software
CN111415007A (en) * 2020-03-26 2020-07-14 中科寒武纪科技股份有限公司 Method and device for calculating data, board card and computer readable storage medium

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014173256A1 (en) * 2013-08-19 2014-10-30 中兴通讯股份有限公司 Download processing method and apparatus, client, and computer storage medium
WO2014177115A1 (en) * 2013-09-30 2014-11-06 中兴通讯股份有限公司 Mobile terminal application batch management method and system, and upgrade server
CN105653318A (en) * 2015-12-24 2016-06-08 北京奇虎科技有限公司 Software upgrade method, device and system
CN105959613A (en) * 2016-05-27 2016-09-21 山西百得科技开发股份有限公司 Digital conference equipment and system
CN107493186A (en) * 2016-12-23 2017-12-19 宝沃汽车(中国)有限公司 The remote update system and its control method of vehicle
CN110505124A (en) * 2018-05-17 2019-11-26 北京和居智能窗业科技有限公司 A kind of control method of intelligent window
CN108769226A (en) * 2018-06-05 2018-11-06 北京智行者科技有限公司 The OAT upgrade methods and car-mounted terminal of vehicle
CN109189419A (en) * 2018-07-27 2019-01-11 广州视源电子科技股份有限公司 Method for upgrading system, apparatus and system, server-side and client
CN109673001A (en) * 2019-02-12 2019-04-23 Oppo广东移动通信有限公司 Data transfer control method and Related product
CN110673864A (en) * 2019-08-28 2020-01-10 绿驰汽车科技集团有限公司 Upgrading monitoring method and system for vehicle-mounted software
CN111415007A (en) * 2020-03-26 2020-07-14 中科寒武纪科技股份有限公司 Method and device for calculating data, board card and computer readable storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
王兰;郝成龙;许茜;: "车载通信终端OTA升级方案", 汽车实用技术, no. 06 *

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112673586B (en) * 2020-12-08 2022-10-28 华为技术有限公司 Data packet processing method and device
CN112673586A (en) * 2020-12-08 2021-04-16 华为技术有限公司 Data packet processing method and device
CN112817631A (en) * 2021-01-29 2021-05-18 一汽解放汽车有限公司 Vehicle-mounted controller upgrading method, device, equipment and storage medium
CN112835616A (en) * 2021-02-26 2021-05-25 百度在线网络技术(北京)有限公司 Version upgrading method and device, electronic equipment and storage medium
CN113515247A (en) * 2021-05-19 2021-10-19 宝能(广州)汽车研究院有限公司 Upgrade progress display method, device, equipment and medium
CN113472884A (en) * 2021-06-30 2021-10-01 潍柴动力股份有限公司 OTA (over the air) upgrading method and device
CN113590164A (en) * 2021-08-31 2021-11-02 重庆长安汽车股份有限公司 Method and system for upgrading vehicle control unit software
CN113590164B (en) * 2021-08-31 2024-03-22 重庆长安汽车股份有限公司 Method and system for upgrading software of whole vehicle controller
CN114297259A (en) * 2021-12-28 2022-04-08 苏州智行畅联科技有限公司 Method and system for off-line query of vehicle-mounted system version, central control vehicle and storage medium
CN114546445A (en) * 2022-02-24 2022-05-27 重庆长安汽车股份有限公司 Finished automobile OTA controller upgrading system and method based on micro-service architecture
CN114546445B (en) * 2022-02-24 2024-05-24 重庆长安汽车股份有限公司 Whole-vehicle OTA controller upgrading system and method based on micro-service architecture
CN114979206A (en) * 2022-05-20 2022-08-30 重庆长安汽车股份有限公司 Vehicle OTA (over the air) upgrading system and method based on subscription and release mode
CN114979206B (en) * 2022-05-20 2023-05-26 重庆长安汽车股份有限公司 Vehicle OTA upgrading system and method based on subscription and release mode
CN116382744A (en) * 2023-06-05 2023-07-04 成都赛力斯科技有限公司 Method, device, system and storage medium for parallel refreshing of multiple ECUs
CN116382744B (en) * 2023-06-05 2023-08-04 成都赛力斯科技有限公司 Method, device, system and storage medium for parallel refreshing of multiple ECUs

Similar Documents

Publication Publication Date Title
CN112040443A (en) Multi-client OTA upgrade processing method and system
EP3726806A1 (en) Method for remotely controlling vehicle on the basis of smart apparatus
CN111190633B (en) OTA (over the air) upgrading system and method for whole electric control unit
US20170344355A1 (en) Updating vehicle system modules
US20120167071A1 (en) Software update apparatus and method of vehicle
US8918492B2 (en) Field panel with embedded webserver and method of accessing the same
JP7225596B2 (en) Program update system, program update server and vehicle
JP6654738B1 (en) Processing telemetry data based on the operating state of the data source
CN109561159B (en) Data processing method and system based on Websocket long connection
WO2011006328A1 (en) System and method for updating device firmware, device management server and mobile terminal
CN112286171A (en) Remote diagnosis method, device, vehicle and storage medium
WO2017076109A1 (en) Software upgrading method and device
CN111866063A (en) Online updating system, method and device for industrial Internet of things AI algorithm
CN112202639A (en) Performance test method for realizing Internet of vehicles remote control service through LoadRunner tool
CN108282177B (en) Upgrading method based on fault-tolerant design of vehicle-mounted OTA terminal
CN114124842B (en) Data transmission method, system, electronic equipment and storage medium
CN115016805A (en) Vehicle system upgrading method, device, system, equipment and medium
KR101704319B1 (en) Parameter configuration system, program management device, and information process device
CN202004788U (en) Vehicle-mounted information push service system
US20230300213A1 (en) Information transmission method and communication device
CN116546056A (en) Remote calibration method and device based on vehicle-mounted communication terminal
US11665619B2 (en) Data and connectivity management systems and methods thereof
JP7415726B2 (en) In-vehicle information processing device, information processing method, and server program
US9049180B2 (en) Method for providing a signal output on the basis of a main file and at least one secondary file, and motor vehicle
CN112654012A (en) Vehicle control solution under network-free condition

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
CB02 Change of applicant information
CB02 Change of applicant information

Address after: Room 601, Building 4, Jingwei Hengrun R&D Center, No. 2, Huixiang Road, Zhangjiawo Town, Xiqing District, Tianjin, 300380

Applicant after: Jingwei Hengrun (Tianjin) research and Development Co.,Ltd.

Address before: Room 308, No.9 Fengze Road, automobile industrial zone, Xiqing District, Tianjin (Zhangjiawo Industrial Zone), 300380

Applicant before: Jingwei Hengrun (Tianjin) research and Development Co.,Ltd.