CN115904447A - Version updating system, method, electronic equipment and storage medium - Google Patents
Version updating system, method, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115904447A CN115904447A CN202211696434.0A CN202211696434A CN115904447A CN 115904447 A CN115904447 A CN 115904447A CN 202211696434 A CN202211696434 A CN 202211696434A CN 115904447 A CN115904447 A CN 115904447A
- Authority
- CN
- China
- Prior art keywords
- version
- updating
- vehicle
- update
- updated
- 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
Links
Images
Abstract
The invention discloses a version updating system, a version updating method, electronic equipment and a storage medium. The system comprises: the system comprises a vehicle-mounted terminal, a main control device, a cloud end and at least one device to be updated, wherein application software is installed in the device to be updated; the main control equipment is used for acquiring the version updating request and sending the version updating request to the vehicle-mounted terminal; the vehicle-mounted terminal is used for determining at least one equipment identifier in the version updating request when receiving the version updating request sent by the main control equipment, acquiring a target updating file corresponding to the equipment identifier from the cloud when detecting that a preset updating condition is met, sending the target updating file to corresponding equipment to be updated and sending a version updating instruction to each equipment to be updated so as to enable each equipment to be updated to carry out application version updating and feed back an updating result based on the version updating instruction and the target updating file. The version updating cost is reduced, and the effects of improving the convenience and accuracy of version updating are achieved.
Description
Technical Field
The present invention relates to the field of computer processing technologies, and in particular, to a version update system, method, electronic device, and storage medium.
Background
At present, most of core functions of an automobile internal system are provided by an ECU (electronic control unit), and the ECU is upgraded along with the upgrading of the automobile functions.
The firmware upgrade of the ECU in the prior art is usually performed by driving the vehicle to a designated service point for off-line upgrade. The mode is not only time-consuming, but also inconvenient for upgrading, especially for the MCU connected with the CAN, the upgrading is usually completed by a serial port which may be hidden, and in the process of upgrading the MCU, the corresponding shell may need to be disassembled, and an upgrading interface is led out to complete the upgrading, so that the upgrading effect is poor.
Disclosure of Invention
The invention provides a version updating system, a version updating method, electronic equipment and a storage medium, which aim to achieve the technical effect of improving the convenience and the accuracy of software version updating while reducing the version updating cost.
According to an aspect of the present invention, there is provided a version update system including: the system comprises a vehicle-mounted terminal, a main control device, a cloud end and at least one device to be updated, wherein the main control device, the cloud end and the at least one device to be updated are communicated with the vehicle-mounted terminal, and application software is installed in the device to be updated; wherein the content of the first and second substances,
the main control equipment is used for acquiring a version updating request and sending the version updating request to the vehicle-mounted terminal;
the vehicle-mounted terminal is used for determining at least one device identifier in the version updating request when receiving the version updating request sent by the main control device, acquiring a target updating file corresponding to the at least one device identifier from the cloud end when detecting that a preset updating condition is met, sending the target updating file to the corresponding device to be updated to be applied, and sending a version updating instruction to each device to be updated so that each device to be updated to be applied performs application version updating based on the version updating instruction and the target updating file received in advance, and feeding back an updating result.
According to another aspect of the present invention, a version updating method is provided, which is applied to a version updating system, where the version updating system includes a vehicle-mounted terminal, and a main control device, a cloud terminal and at least one device to be updated, which are in communication with the vehicle-mounted terminal, and application software is installed in the device to be updated; the method comprises the following steps:
acquiring a version updating request based on the master control equipment, and sending the version updating request to the vehicle-mounted terminal;
when the vehicle-mounted terminal receives a version updating request sent by the main control device, at least one device identification in the version updating request is determined, when a preset updating condition is detected to be met, a target updating file corresponding to the at least one device identification is obtained from the cloud, the target updating file is sent to corresponding to-be-applied updating devices, a version updating instruction is sent to each to-be-applied updating device, so that each to-be-applied updating device can update the application version based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the version update method according to any one of the embodiments of the present invention.
According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a version update method according to any one of the embodiments of the present invention when the computer instructions are executed.
According to the technical scheme of the embodiment of the invention, the version updating request is obtained by using the main control equipment, and the version updating request is sent to the vehicle-mounted terminal; the method comprises the steps that when a vehicle-mounted terminal receives a version updating request sent by a main control device, at least one device identification in the version updating request is determined, when a preset updating condition is met, a target updating file corresponding to the at least one device identification is obtained from a cloud end, the target updating file is sent to corresponding devices to be updated to be applied, and a version updating instruction is sent to each device to be updated to enable each device to be updated to be applied to update the application version based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a version updating system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a vehicle-mounted terminal according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a version updating system according to a second embodiment of the present invention;
FIG. 4 is a diagram illustrating a version updating method according to a second embodiment of the present invention;
fig. 5 is a flowchart of a version updating method according to a third embodiment of the present invention;
fig. 6 is a schematic structural diagram of an electronic device implementing the version updating method according to the embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solutions of the present invention, 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.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example one
Fig. 1 is a schematic structural diagram of a version updating system according to an embodiment of the present invention, where this embodiment is applicable to a version updating situation, and referring to fig. 1, the version updating system provided in this embodiment includes: the system comprises a vehicle-mounted terminal 110, a main control device 120, a cloud 130 and at least one device to be updated 140, wherein the main control device 120, the cloud 130 and the at least one device to be updated are communicated with the vehicle-mounted terminal 110. The following describes the structural components of the application service system of the present embodiment in detail.
The main control device 120 is configured to obtain a version update request, and send the version update request to the vehicle-mounted terminal 110;
the vehicle-mounted terminal 110 is configured to, when receiving a version update request sent by the main control device 120, determine at least one device identifier in the version update request, and when detecting that a preset update condition is met, obtain a target update file corresponding to the at least one device identifier from the cloud 130, send the target update file to the corresponding to-be-applied update device 140, and send a version update instruction to each to-be-applied update device 140, so that each to-be-applied update device 140 performs application version update based on the version update instruction and the target update file received in advance, and feed back an update result.
The vehicle-mounted terminal 110 may be a T-BOX (Telematics BOX, vehicle network intelligent terminal). The main control device 120 may be disposed with an SoC (System on Chip). The cloud 130 may be a TSP (Telematics Service Provider). Vehicle terminal 110 and main control device 120 may communicate through media such as a USB network, a vehicle ethernet network, and a WIFI network. The in-vehicle terminal 110 and the cloud 130 can communicate through a network such as 5G, 4G, 3G, wiFi. The device to be updated 140 is a device that needs to be updated, and may be, for example, an ECU (Electronic Control Unit), an MCU (Micro Control Unit), or the like, where application software is installed in the device to be updated, and an application program runs in the application software. For example, a plurality of ECUs with different functions are usually installed in a vehicle, and when there is an update demand, the ECU can be used as one device to be updated 140 and update the application version of the application software in the device to be updated. The version update request refers to a program and code that requests a version update. The device identification may be used to identify the uniqueness of the device. The preset update condition may be a pre-configured factor that detects whether there is or is in an update environment. The version update instruction refers to code for instructing to perform a version update. The update result may include information such as update progress, update success, or update failure.
In this embodiment, the user may trigger the version update control on the system page of the main control device 120, and at this time, the main control device 120 is considered to receive the version update request, and may send the version update request to the vehicle-mounted terminal 110. When the vehicle-mounted terminal 110 receives the version update request sent by the main control device 120, the version update request may be analyzed to obtain at least one device identifier carried in the version update request, and devices (such as the ECU1, the ECU2, the ECU3, the MCU, and the like) corresponding to the device identifiers are the to-be-applied update device 140. In order to improve the accuracy of the version update, it may be detected whether the vehicle or the software has an update condition, for example, the vehicle running speed is detected, and if the running speed is within a preset range, the preset update condition is considered to be satisfied, or the operating state of the update-to-be-applied device 140 is detected, and if the operating state of the update-to-be-applied device 140 is normal, the preset update condition is considered to be satisfied. When it is detected that the preset update condition is met, a target update file corresponding to each device identifier may be acquired from the cloud 130, where the target update file is an update package to be used, and the format of the target update file may be a compressed package or a file. Each target update file can be sent to the corresponding device to be updated 140, and meanwhile, a version update instruction can be sent to each device to be updated 140, after each device to be updated 140 receives the version update instruction, the received target update file can be used to update the firmware of the installed application software, each device to be updated 140 can feed back the update result to the vehicle-mounted terminal 110, and the vehicle-mounted terminal 110 can send the update result to the main control device 120 or the mobile terminal corresponding to the vehicle user and display the update result, so that the user can know the installation condition of the software effectively in time.
On the basis of the foregoing embodiment, referring to fig. 2, fig. 2 is a schematic structural diagram of a vehicle-mounted terminal according to an embodiment of the present invention, where the vehicle-mounted terminal 110 further includes: the authentication module 210 may, among other things,
the authentication module 210 is configured to receive an access request of the main control device 120, the cloud 130, and/or the mobile terminal, and establish communication with the main control device 120, the cloud 130, and/or the mobile terminal when an authentication result corresponding to the access request passes; wherein the content of the first and second substances,
the mobile terminal is configured to receive a version upgrade request generated based on a user trigger operation, and send the version upgrade request to the vehicle-mounted terminal 110, so that the vehicle-mounted terminal 110 sends a target update file and a version update instruction to the corresponding device to be updated 140 based on the version upgrade request.
The mobile terminal refers to a computer device, and may be a mobile phone, a notebook, a tablet computer, and the like.
In order to improve the safety of the vehicle, the in-vehicle terminal 110 does not allow the device to be freely accessed. In this embodiment, the authentication module 210 may perform access authentication of each device. The main control device 120, the cloud 130, and/or the mobile terminal, etc. may request access from the in-vehicle terminal 110, and send the access request to the authentication module 210. The authentication module 210 may authenticate the identity and authority of the main control device 120, the cloud 130, and/or the mobile terminal, such as password authentication, and allow the requested device to access when the authentication result is passed, and may establish communication with the requested main control device 120, the cloud 130, and/or the mobile terminal through a network medium. It should be noted that, if communication is established between the vehicle-mounted terminal 110 and the mobile terminal, a user may query the ECU device connected to the vehicle-mounted terminal 110 in the vehicle through the mobile terminal, and may also query current version information, upgradable version information, and the like of the connected ECU device, and the user may also initiate a request for firmware upgrade of the ECU device to the vehicle-mounted terminal 110 through the mobile terminal, for example, a corresponding version upgrade APP may be pre-configured in the mobile terminal, and a version upgrade control is built in the APP, and when the user clicks or slides to trigger the control, the user considers that the mobile terminal has received the version upgrade request, and may send the version upgrade request to the vehicle-mounted terminal 110, and at this time, the vehicle-mounted terminal 110 may send a target update file and a version update instruction to the corresponding to-be-applied update device 140 based on the received version upgrade request, so that each to-be-applied update device 140 performs version update. In the version updating process, the updating result may also be pushed to the mobile terminal, and the mobile terminal displays the notification message pushed by the in-vehicle terminal 110.
On the basis of the above embodiment, the main control device 120 further includes: a display screen, wherein,
displaying a version updating configuration page on the display screen, wherein the version updating configuration page comprises at least one of an updating time editing control, a version query control, a software state query control and a request updating control;
the main control device 120 is specifically configured to generate a version update request when a trigger operation for requesting an update control is detected, and send the version update request to the in-vehicle terminal 110.
The Display screen may be an LCD (Liquid Crystal Display), and the update time editing control may be a touch-enabled component for setting the update time. The version query control can be a touch-controllable component for querying the version information of the software. The software state query control can be a touch-controllable component for querying the working state of the software. The request update control state may be a touchable component for requesting an update.
In practical application, a user may initiate a request for querying version information of software to vehicle-mounted terminal 110 by triggering a version query control, after receiving the request, vehicle-mounted terminal 110 may query an ECU device connected to a vehicle body, and feed back current version information, upgradable version information, and the like of the ECU device to main control device 120, and when receiving the information, main control device 120 may display the information on a display screen for the user to view, and the user may select an ECU device that needs to be updated according to the displayed information. The user may also initiate a version update request to vehicle-mounted terminal 110 by clicking or sliding the trigger request update control, and send the version update request to vehicle-mounted terminal 110. The user may also select the time of the version update by triggering the update time editing control in the version update configuration page displayed on the display screen, for example, at 7 am to 8 am, and may send the update time input by the user editing to the vehicle-mounted terminal 110 along with the request for the version update, so that the vehicle-mounted terminal 110 sends the version update instruction to the corresponding device to be updated 140 within the specified time. The upgrading of ECU firmware is controlled through the main control equipment 120, the operability and convenience of ECU upgrading are improved, and the use requirements of users are met.
On the basis of the above embodiment, with continued reference to fig. 2, the in-vehicle terminal 110 includes: a query module 220 and a receive module 230, wherein,
the query module 220 is configured to send a version query instruction to the at least one to-be-applied updating device 140 and/or the cloud 130, so that the at least one to-be-applied updating device 140 feeds back current version information to the receiving module 230 based on the version query instruction, and/or so that the cloud 130 feeds back upgrade version information of the at least one to-be-applied updating device 140 to the receiving module 230 based on the version query instruction;
the receiving module 230 is configured to receive current version information and/or upgrade version information of at least one device to be updated 140, and send the current version information and/or upgrade version information to the main control device 120, so that when the main control device 120 receives the current version information and/or upgrade version information, the version display list corresponding to the control is queried based on the current version information and/or upgrade version information.
The version query instruction refers to a query code for indicating execution version information.
In this embodiment, when the vehicle-mounted terminal 110 receives a version query request sent by the main control device 120, the cloud terminal 130 and/or the mobile terminal, a version query instruction may be sent to at least one to-be-applied updating device 140 and/or the cloud terminal 130 based on the query module 220, when the to-be-applied updating device 140 receives the version query instruction, current version information used by itself may be fed back to the receiving module 230, and when the cloud terminal 130 receives the version query instruction, upgrade version information of a device identifier carried in the version query instruction may be fed back to the receiving module 230. The receiving module 230 may send the current version information and/or the upgrade version information to the main control device 120 after receiving the current version information and/or the upgrade version information of the to-be-applied update device 140 that needs to be queried, and when receiving the current version information and/or the upgrade version information, the main control device 120 may update a version display list corresponding to the version query control based on the current version information and/or the upgrade version information and display the version display list on the display screen, so that the software version information queried by the user is the latest, and the user may also determine whether the software needs to be updated according to the queried information, thereby implementing unified management of the software.
On the basis of the foregoing embodiment, the receiving module 230 is further configured to receive an update result fed back by at least one to-be-applied update device 140, and send the update result to the master control device 120, so that the master control device 120 displays the update result on the display screen.
Specifically, after each device to be updated 140 performs application version update based on the version update instruction and the target update file, and feeds back the update result to the receiving module 230, the receiving module 230 may send the received update result fed back by at least one device to be updated 140 to the main control device 120, and the main control device 120 may display the update result on a display screen, so that the user can know the update condition in time.
On the basis of the foregoing embodiment, with continued reference to fig. 2, the in-vehicle terminal 110 further includes: the detection module 240 may be configured to, among other things,
the detecting module 240 is configured to determine an operating state of the to-be-applied update device 140 corresponding to at least one device identifier in the version update request, and determine that a preset update condition is met when the operating state is normal, so that the vehicle-mounted terminal 110 obtains a target update file corresponding to the at least one device identifier from the cloud 130 when it is detected that the preset update condition is met.
In this embodiment, when detecting whether the preset update condition is met, the operating state of the to-be-applied update device 140 corresponding to at least one device identifier in the version update request may be determined based on the detection module 240, and if the operating state is normal, it may be considered that the to-be-applied update device 140 may perform software update, that is, it is determined that the preset update condition is met, and the application version update may be performed on the to-be-applied update device 140. For example, during the driving of the vehicle, the vehicle-mounted terminal 110 should correctly identify and reject the upgrade request of part or all of the related devices to be updated 140, so as to improve the safety of driving and software updating. Or, the ECU connection channel state is tested, whether the ECU can normally communicate or not is confirmed, and whether the ECU is in a normal working state or not is confirmed, so that the target update file can be normally distributed.
On the basis of the foregoing embodiment, with continued reference to fig. 2, the vehicle-mounted terminal 110 further includes: a timing module 250 that, among other things,
the timing module 250 is configured to update the information receiving time when receiving the processing information sent by the main control device 120, the cloud 130, the at least one to-be-applied update device 140, and/or the mobile terminal, and disconnect communication with the main control device 120, the cloud 130, the at least one to-be-applied update device 140, and/or the mobile terminal when the accumulated time from the information receiving time reaches a preset time threshold, so as to establish network communication when receiving the processing information sent by the main control device 120, the cloud 130, the at least one to-be-applied update device 140, and/or the mobile terminal again.
Wherein the processing information includes at least one of a version update request, an update result, a target update file, a version upgrade request, current version information, and upgrade version information.
In order to ensure reasonable utilization of resources and reduce power consumption of the entire vehicle, the timing module 250 may update the information receiving time when receiving the processing information sent by the main control device 120, the cloud 130, the at least one to-be-applied updating device 140, and/or the mobile terminal, and ensure that the information receiving time is the latest time when receiving the processing information each time. If the accumulated time length from the time of receiving the information reaches the preset time length threshold, it may be considered that the main control device 120, the cloud 130, the at least one to-be-applied update device 140 and/or the mobile terminal does not send a message to the vehicle within a certain time range, at this time, communication with the main control device 120, the cloud 130, the at least one to-be-applied update device 140 and/or the mobile terminal may be disconnected, and when processing information sent by the main control device 120, the cloud 130, the at least one to-be-applied update device 140 and/or the mobile terminal is received again, network communication may be established with the processing information, so that disconnection of the inactive main control device 120, the cloud 130, the at least one to-be-applied update device 140 and/or the mobile terminal at regular time is achieved.
On the basis of the above embodiment, the system further includes: a micro-control unit, wherein,
the micro control unit communicates with the in-vehicle terminal 110 and the at least one device to be updated 140, respectively. The micro control unit refers to an MCU.
It should be noted that the vehicle-mounted terminal 110 may be directly or indirectly (via the MCU) connected to the vehicle ECU through the CAN bus to acquire the vehicle body information and control the vehicle body, and the MCU may be connected to the vehicle-mounted terminal 110 through the UART or the SPI, and communicate with the vehicle-mounted terminal 110 through the customized protocol bearer application protocol. The micro control unit can switch in and off the vehicle terminal 110 and inquire the version information that the MCU can upgrade. Requesting an ECU device upgrade, receiving a software version update request, uploading an update progress and an update status to the in-vehicle terminal 110, and the like. The user may also update the application version of the micro control unit by controlling the main control device 120, the cloud 130, and/or the mobile terminal.
On the basis of the foregoing embodiment, the vehicle-mounted terminal 110 is further configured to, when it is detected that the device identifier is consistent with the terminal identifier of the vehicle-mounted terminal 110, obtain a target upgrade file corresponding to the vehicle-mounted terminal 110 from the cloud 130, broadcast an upgrade message to the main control device 120, the cloud 130, and the at least one device to be updated 140, and perform application version upgrade based on the target upgrade file when it is detected that a preset upgrade condition is met.
It should be noted that, in the process of upgrading the vehicle-mounted terminal 110, a restart of the T-Box may be involved, and in order to ensure the safety of the vehicle, when the vehicle-mounted terminal 110 detects that the device identifier is consistent with the terminal identifier of the vehicle-mounted terminal 110, it is considered that the version of the vehicle-mounted terminal 110 needs to be updated at this time, a target upgrade file corresponding to the vehicle-mounted terminal 110 may be acquired from the cloud 130, and a message about to be upgraded of the vehicle-mounted terminal 110 may be broadcast to the main control device 120, the mobile terminal, the cloud 130, the at least one to-be-applied update device 140, and the like. And when the preset upgrading condition is met. The vehicle-mounted terminal 110 may perform application version upgrade based on the target upgrade file, and optionally broadcast a message to the connected main control device 120, the mobile terminal, the cloud 130, and/or the at least one device to be updated 140 after the update.
It should be further noted that, in order to ensure the security of the version update, before the in-vehicle terminal 110 is used, activation and binding settings may be performed on the in-vehicle terminal 110. For example, the activation may be performed according to a unique code (e.g., VIN and user information), which generally only needs to be performed once to ensure the validity of the vehicle-mounted terminal 110, and subsequently, the authentication may be performed based on the unique code. In order to improve convenience of version update, an upgrade package of the device to be updated 140 (such as an ECU) to be updated, which needs to be updated, may be obtained through a human-computer interaction interface on the main control device 120, such as a usb flash disk interface of the main control device 120, and sent to the vehicle-mounted terminal 110, so that the vehicle-mounted terminal 110 performs corresponding distribution.
The embodiment of the invention obtains the version updating request by using the main control equipment and sends the version updating request to the vehicle-mounted terminal; the method comprises the steps that when a vehicle-mounted terminal receives a version updating request sent by a main control device, at least one device identification in the version updating request is determined, when the condition that a preset updating condition is met is detected, a target updating file corresponding to the at least one device identification is obtained from a cloud, the target updating file is sent to corresponding devices to be updated to be applied, and a version updating instruction is sent to each device to be updated to be applied, so that each device to be updated to be applied performs application version updating based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
Example two
As an alternative embodiment of the foregoing embodiment, fig. 3 is a schematic structural diagram of a version updating system according to a second embodiment of the present invention, and specific details thereof can be found in the following.
The technical scheme provided by the invention can control the version updating of one or more ECUs by uniformly inquiring the current version information and the updatable version information (namely the upgraded version information) of the available ECUs on each vehicle. The version updating method can be realized on the main control equipment; the method can also be realized on a mobile terminal APP bound with the vehicle; and can also be realized on a TSP background system (namely a cloud). In order to realize multi-party control, one party is required to be used as a server side, and the other party is required to be used as a client side. The T-Box (i.e. the vehicle-mounted terminal) can be used as a server side, and other devices capable of being operated by a human machine can be used as a client side. The client and the server can realize unified control operation by defining an application layer protocol on the TCP/IP protocol. In addition, for a device which does not support TCP/IP protocol or has no network connection, such as a MCU connected to the T-Box through UART or SPI, the T-Box end can be specified to realize a custom protocol to carry the application layer protocol. The custom protocol is in a peer-to-peer position with the TCP/IP protocol. The application layer protocol can select Protobuf as a data format. For example, as shown in fig. 3, the version updating system provided in the embodiment of the present invention may be composed of a vehicle-mounted terminal, a main control device, a cloud, a mobile terminal, and at least one device to be updated, where the main control device, the cloud, the mobile terminal, and the at least one device to be updated are in communication with the vehicle-mounted terminal. The vehicle-mounted terminal is a T-Box and serves as a wireless communication network inlet of the vehicle networking, a 5G/4G/3G network of the vehicle is given, media such as USB, ethernet (including vehicle-mounted Ethernet), wiFi and the like CAN be used for providing a main control device and/or an electronic device sharing network carried by a vehicle user, the vehicle-mounted terminal CAN also be directly or indirectly (through a MCU) connected with a vehicle ECU through a CAN bus to acquire vehicle body information and control a vehicle body, and meanwhile, data CAN be uploaded to the TSP remotely or a management instruction issued by the TSP CAN be received remotely. The T-Box can realize the function of a server and is used for responding to a request from a client, wherein the client refers to a main control device, a cloud, a mobile terminal, at least one device to be updated to be applied and the like. The communication format between the server and the client can be uniform and extensible, and the transmission mode is based on an SSL/TLS communication framework. Before the vehicle-mounted terminal is used, the vehicle-mounted terminal can be activated and bound, for example, the vehicle-mounted terminal can be activated according to a unique code such as a VIN and user information, so as to be used for subsequent authentication. Due to the safety consideration, the vehicle-mounted terminal does not allow random equipment access, authentication is required when a client accesses, and the vehicle-mounted terminal can be used for client connection after the authentication passes. The vehicle-mounted terminal can also inquire the ECU equipment connected with the vehicle body, inquire the current version information and the upgradable version information of the connected ECU equipment, and also receive a version updating request, wherein the equipment object requesting updating comprises one to a plurality of ECU equipment. When the vehicle-mounted terminal receives the version updating request, it may determine whether a preset updating condition is met, for example, in the driving process of the vehicle, the server should correctly identify and reject some or all of the upgrading requests of the relevant ECUs, for example, in view of driving safety. And testing the connection channel state of each ECU, confirming whether the ECU can normally communicate or not and whether the ECU is in a normal working state or not, if so, determining that a preset updating condition is met, and issuing an updating instruction to the equipment to be updated. The vehicle-mounted terminal can also send an upgrading progress and an upgrading result to the connected client so that a user can check the upgrading condition. The vehicle-mounted terminal can also download update packages (including whole packages and/or differential packages) needing to be upgraded from a pre-configured server (such as a remote end) or a designated server. The vehicle-mounted terminal can also disconnect inactive clients at regular time. Has the advantages that: the reasonable utilization of resources is ensured, and the power consumption of the whole vehicle is reduced. The vehicle-mounted terminal can also inquire the network state (such as signal quality, the currently registered network mode and the like) and actively inform the client. And selecting an upgrading mode. Such as providing options of whole package upgrade and differential upgrade, whether the original version needs to be backed up, and the like. Besides comprehensively managing the vehicle body ECU, the main control equipment can also interact with a user through an LCD (liquid crystal display), and the user can control the ECU firmware upgrading through the main control equipment. The main control device is used as a client, and needs to perform binding and activation request operations in order to verify the validity of the client. The main control device can also be connected with and disconnected from the vehicle-mounted terminal, inquire the connected ECU devices, inquire the access states of the connected ECU devices, inquire the current version information and the upgradable version information of the connected ECU devices, request the upgrading of the ECU devices to the vehicle-mounted terminal, display the notification messages pushed by the vehicle-mounted terminal, inquire the states of the vehicle-mounted terminal devices, the network states and the like. The main control device may further provide personalized options such as selecting a designated time period for upgrading, and the user may select the designated time on the display interface of the main control device to reserve an upgrading scene. The MCU can also be used as a client to realize the access and disconnection of the vehicle-mounted terminal, the inquiry of version information which can be upgraded by the MCU, the request of firmware upgrade of the ECU equipment, the reception of a version updating request, the uploading of an upgrading progress and an upgrading state and the display of the state on a display screen of the main control equipment. The mobile terminal can be used as a substitute of the main control device and consistent with the functions realized by the main control device, and a user can inquire the connected ECU devices, inquire the access states of the connected ECU devices, inquire the current version information and the upgradable version information of the connected ECU devices, request the upgrading of the ECU devices to the vehicle-mounted terminal, display the notification messages pushed by the vehicle-mounted terminal, inquire the states of the vehicle-mounted terminal devices, the network state and the like through the APP on the mobile terminal. The cloud serves as the management role of the OTA and the Internet of vehicles, can provide storage and downloading of an online firmware package (namely an update file), and is accessed, inquired and downloaded by the vehicle-mounted terminal, responds to a control command and the like.
In order to clearly introduce the technical scheme, a specific implementation manner of the version updating system provided by the embodiment of the invention is provided in combination with a specific application scenario, and the downloading of the update file refers to downloading an entire upgrade package and/or a differential package of software through a cloud end in wireless network communication. The distribution of the update file refers to that after the update file is downloaded to the vehicle-mounted terminal, the server program of the vehicle-mounted terminal judges the upgrading equipment, and the update file is forwarded to the target ECU equipment needing to be upgraded through a local network or a UART interface or an SPI interface. (i.e., the device to be updated) may be represented as a schematic diagram of a version updating method, as shown in fig. 4, for example, the configuration of the server is initialized, and the configuration related to this step may include preset cloud server information, communication and authentication modes, device activation and binding information, client access restriction information, and the like. Further, the vehicle-mounted terminal receives requests from clients such as a cloud, a main control device and an MCU, and this step involves processing command requests sent by all possible clients, including requests issued from the TSP. Further, it is determined whether the received client request is a version update request. If the request is not a version updating request, other request commands are processed, such as commands of all non-firmware upgrading requests, classification processing is carried out in the step, and corresponding processing results can be returned to the client. If the version updating request is made, downloading the firmware (namely the target updating file) from the cloud according to the pre-configuration and request command information, and verifying the firmware, wherein the verified content comprises but is not limited to integrity, reliability and safety. And further, judging whether the target update file needs to be distributed, downloading the target update file to the vehicle-mounted terminal and after the target update file is verified, confirming whether the target update file needs to be independently transmitted to the appointed client side according to the equipment identifier carried in the version update request. If the target update file is of the vehicle-mounted terminal, the target update file does not need to be distributed, and when the T-Box is upgraded, the upgrading process may involve restarting the T-Box, and a message should be broadcast to the connected client before upgrading. Optionally broadcasting information to the connected client after upgrading; if the target update file is not the vehicle-mounted terminal, the version update command is distributed to the corresponding ECU, and after the target update file is sent, the version update command is issued to the target terminal equipment. It should be noted that, in the upgrading process, the vehicle body state needs to be judged, and whether an upgrading scene sent by the client exists is judged, so as to determine whether to upgrade immediately or within a reserved time period; the unified updating management of each software is realized, and the convenience of the updating operation is improved.
According to the technical scheme of the embodiment, the version updating request is obtained by the main control equipment and is sent to the vehicle-mounted terminal; the method comprises the steps that when a vehicle-mounted terminal receives a version updating request sent by a main control device, at least one device identification in the version updating request is determined, when a preset updating condition is met, a target updating file corresponding to the at least one device identification is obtained from a cloud end, the target updating file is sent to corresponding devices to be updated to be applied, and a version updating instruction is sent to each device to be updated to enable each device to be updated to be applied to update the application version based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
EXAMPLE III
Fig. 5 is a flowchart of a version updating method according to a third embodiment of the present invention, which may be applied to the version updating system provided in the foregoing embodiments, and referring to fig. 5, the method may include the following steps:
and S510, acquiring a version updating request based on the main control equipment, and sending the version updating request to the vehicle-mounted terminal.
S520, when the vehicle-mounted terminal receives the version updating request sent by the main control device, at least one device identifier in the version updating request is determined, when the condition that a preset updating condition is met is detected, a target updating file corresponding to the at least one device identifier is obtained from the cloud end, the target updating file is sent to the corresponding device to be updated, a version updating instruction is sent to each device to be updated, so that each device to be updated carries out application version updating based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
On the basis of the above technical solution, the vehicle-mounted terminal further includes: an authentication module, wherein,
the authentication module is used for receiving an access request of the main control device, the cloud and/or the mobile terminal, and establishing communication with the main control device, the cloud and/or the mobile terminal when an authentication result corresponding to the access request passes; wherein the content of the first and second substances,
the mobile terminal is used for receiving a version upgrading request generated based on user trigger operation and sending the version upgrading request to the vehicle-mounted terminal, so that the vehicle-mounted terminal sends a target updating file and a version updating instruction to corresponding equipment to be updated to be applied based on the version upgrading request.
On the basis of the above technical solution, the main control device further includes: a display screen, wherein,
displaying a version updating configuration page on the display screen, wherein the version updating configuration page comprises at least one of an updating time editing control, a version query control, a software state query control and a request updating control;
the main control device is specifically configured to generate a version update request when the trigger operation for the request update control is detected, and send the version update request to the vehicle-mounted terminal.
On the basis of the above technical solution, the vehicle-mounted terminal includes: a query module and a receiving module, wherein,
the query module is configured to send a version query instruction to the at least one device to be updated and/or the cloud, so that the at least one device to be updated feeds back current version information to the receiving module based on the version query instruction, and/or the cloud feeds back upgrade version information of the at least one device to be updated to the receiving module based on the version query instruction;
the receiving module is used for receiving the current version information and/or the upgrade version information of the at least one device to be updated to be applied and sending the current version information and/or the upgrade version information to the main control device, so that the main control device can query the version display list corresponding to the control on the basis of the current version information and/or the upgrade version information update version when receiving the current version information and/or the upgrade version information.
On the basis of the technical scheme, the receiving module is further configured to receive an update result fed back by the at least one device to be updated to be applied, and send the update result to the main control device, so that the main control device displays the update result on a display screen.
On the basis of the above technical solution, the vehicle-mounted terminal further includes: a detection module for detecting, wherein,
the detection module is configured to determine a working state of the to-be-applied update device corresponding to the at least one device identifier in the version update request, and determine that a preset update condition is met when the working state is normal, so that the vehicle-mounted terminal obtains a target update file corresponding to the at least one device identifier from the cloud when detecting that the preset update condition is met.
On the basis of the above technical solution, the vehicle-mounted terminal further includes: a timing module, wherein,
the timing module is used for updating the information receiving time when receiving the processing information sent by the main control device, the cloud, the at least one device to be updated and/or the mobile terminal, and disconnecting the communication with the main control device, the cloud, the at least one device to be updated and/or the mobile terminal when the accumulated time from the information receiving time reaches a preset time threshold value, so as to establish network communication when receiving the processing information sent by the main control device, the cloud, the at least one device to be updated and/or the mobile terminal again;
wherein the processing information includes at least one of a version update request, an update result, a target update file, a version upgrade request, current version information, and upgrade version information.
On the basis of the above technical solution, the system further includes: a micro-control unit, wherein,
the micro control unit is respectively communicated with the vehicle-mounted terminal and the at least one device to be updated.
On the basis of the technical scheme, the vehicle-mounted terminal is further used for acquiring a target upgrading file corresponding to the vehicle-mounted terminal from the cloud when the equipment identification is detected to be consistent with the terminal identification of the vehicle-mounted terminal, broadcasting upgrading information to the main control equipment, the cloud and at least one to-be-applied updating equipment, and upgrading an application version based on the target upgrading file when a preset upgrading condition is detected to be met.
According to the technical scheme of the embodiment, the version updating request is obtained by the main control equipment and is sent to the vehicle-mounted terminal; the method comprises the steps that when a vehicle-mounted terminal receives a version updating request sent by a main control device, at least one device identification in the version updating request is determined, when a preset updating condition is met, a target updating file corresponding to the at least one device identification is obtained from a cloud end, the target updating file is sent to corresponding devices to be updated to be applied, and a version updating instruction is sent to each device to be updated to enable each device to be updated to be applied to update the application version based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
Example four
Fig. 6 is a schematic structural diagram of an electronic device implementing the version updating method according to the embodiment of the present invention. The electronic device may be used to represent a vehicle-mounted terminal, a host device, a cloud, etc., or various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 6, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to the bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
In some embodiments, the version update method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the version update method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the version update method by any other suitable means (e.g. by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A version update system, the system comprising: the system comprises a vehicle-mounted terminal, a main control device, a cloud end and at least one device to be updated and applied, wherein the main control device, the cloud end and the at least one device to be updated and applied are communicated with the vehicle-mounted terminal, and application software is installed in the device to be updated and applied; wherein the content of the first and second substances,
the main control equipment is used for acquiring a version updating request and sending the version updating request to the vehicle-mounted terminal;
the vehicle-mounted terminal is used for determining at least one device identifier in the version updating request when receiving the version updating request sent by the main control device, acquiring a target updating file corresponding to the at least one device identifier from the cloud end when detecting that a preset updating condition is met, sending the target updating file to the corresponding device to be updated to be applied, and sending a version updating instruction to each device to be updated so that each device to be updated to be applied performs application version updating based on the version updating instruction and the target updating file received in advance, and feeding back an updating result.
2. The system of claim 1, wherein the vehicle-mounted terminal further comprises: an authentication module, wherein,
the authentication module is used for receiving an access request of the main control device, the cloud and/or the mobile terminal, and establishing communication with the main control device, the cloud and/or the mobile terminal when an authentication result corresponding to the access request passes; wherein the content of the first and second substances,
the mobile terminal is used for receiving a version upgrading request generated based on user trigger operation and sending the version upgrading request to the vehicle-mounted terminal, so that the vehicle-mounted terminal sends a target updating file and a version updating instruction to corresponding equipment to be updated based on the version upgrading request.
3. The system of claim 1, wherein the master device further comprises: a display screen, wherein,
a version updating configuration page is displayed on the display screen, and the version updating configuration page comprises at least one of an updating time editing control, a version query control, a software state query control and a request updating control;
the main control device is specifically configured to generate a version update request when the trigger operation for the request update control is detected, and send the version update request to the vehicle-mounted terminal.
4. The system according to claim 1, wherein the vehicle-mounted terminal comprises: a query module and a receiving module, wherein,
the query module is configured to send a version query instruction to the at least one device to be updated and/or the cloud, so that the at least one device to be updated feeds back current version information to the receiving module based on the version query instruction, and/or the cloud feeds back upgrade version information of the at least one device to be updated to the receiving module based on the version query instruction;
the receiving module is used for receiving the current version information and/or the upgrade version information of the at least one device to be updated to be applied and sending the current version information and/or the upgrade version information to the main control device, so that the main control device can query the version display list corresponding to the control on the basis of the current version information and/or the upgrade version information update version when receiving the current version information and/or the upgrade version information.
5. The system according to claim 3, wherein the receiving module is further configured to receive an update result fed back by the at least one device to be updated, and send the update result to the master device, so that the master device displays the update result on a display screen.
6. The system according to claim 1, wherein the in-vehicle terminal further comprises: a detection module, wherein,
the detection module is configured to determine a working state of the to-be-applied update device corresponding to the at least one device identifier in the version update request, and determine that a preset update condition is met when the working state is normal, so that the vehicle-mounted terminal obtains a target update file corresponding to the at least one device identifier from the cloud when detecting that the preset update condition is met.
7. The system of claim 1, wherein the vehicle-mounted terminal further comprises: a timing module, wherein,
the timing module is used for updating the information receiving time when receiving the processing information sent by the main control device, the cloud, the at least one device to be updated and/or the mobile terminal, and disconnecting the communication with the main control device, the cloud, the at least one device to be updated and/or the mobile terminal when the accumulated time from the information receiving time reaches a preset time threshold value, so as to establish network communication when receiving the processing information sent by the main control device, the cloud, the at least one device to be updated and/or the mobile terminal again;
wherein the processing information includes at least one of a version update request, an update result, a target update file, a version upgrade request, current version information, and upgrade version information.
8. The system of claim 1, further comprising: a micro-control unit, wherein,
the micro control unit is respectively communicated with the vehicle-mounted terminal and the at least one device to be updated.
9. The system of claim 1, wherein the vehicle-mounted terminal is further configured to, when it is detected that the device identifier is consistent with the terminal identifier of the vehicle-mounted terminal, obtain a target upgrade file corresponding to the vehicle-mounted terminal from the cloud, broadcast an upgrade message to the main control device, the cloud, and at least one device to be updated, and perform application version upgrade based on the target upgrade file when it is detected that a preset upgrade condition is met.
10. The version updating method is characterized by being applied to a version updating system, wherein the version updating system comprises a vehicle-mounted terminal, a main control device, a cloud terminal and at least one device to be updated, wherein the main control device is communicated with the vehicle-mounted terminal; the version updating method comprises the following steps:
acquiring a version updating request based on the main control equipment, and sending the version updating request to the vehicle-mounted terminal;
when the vehicle-mounted terminal receives a version updating request sent by the main control device, at least one device identifier in the version updating request is determined, when a preset updating condition is detected to be met, a target updating file corresponding to the at least one device identifier is obtained from the cloud end, the target updating file is sent to corresponding to-be-applied updating devices, a version updating instruction is sent to each to-be-applied updating device, so that each to-be-applied updating device carries out application version updating based on the version updating instruction and the target updating file received in advance, and an updating result is fed back.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211696434.0A CN115904447A (en) | 2022-12-28 | 2022-12-28 | Version updating system, method, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211696434.0A CN115904447A (en) | 2022-12-28 | 2022-12-28 | Version updating system, method, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115904447A true CN115904447A (en) | 2023-04-04 |
Family
ID=86471092
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211696434.0A Pending CN115904447A (en) | 2022-12-28 | 2022-12-28 | Version updating system, method, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115904447A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117424893A (en) * | 2023-12-19 | 2024-01-19 | 深圳竹云科技股份有限公司 | Data transmission method, device, computer equipment and storage medium |
-
2022
- 2022-12-28 CN CN202211696434.0A patent/CN115904447A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117424893A (en) * | 2023-12-19 | 2024-01-19 | 深圳竹云科技股份有限公司 | Data transmission method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10137906B2 (en) | Method and apparatus for persistent transferrable customizable vehicle settings | |
| CN110032382A (en) | A kind of vehicle electronic control unit upgrade method, system and terminal device | |
| CN108376079B (en) | Automatic application updates | |
| CN107438830B (en) | Upgrading method, upgrading device, upgrading equipment and upgrading system | |
| CN112099829A (en) | Vehicle upgrade control method and system, OTA background and vehicle | |
| CN109639692B (en) | Offline login method, device, equipment, system and storage medium | |
| CN112118318B (en) | Vehicle upgrading method, terminal device, vehicle and computer storage medium | |
| US20150088370A1 (en) | Systems and methods for identification of a compromised module | |
| CN112463190A (en) | Vehicle upgrading method and device | |
| JP2023052938A (en) | Program update system, program update server, information processing apparatus, vehicle, method, and program | |
| CN112804730B (en) | Equipment interconnection method, device, server, intelligent equipment and storage medium | |
| CN112995403B (en) | Vehicle control method and related device | |
| CN106339236A (en) | Software upgrading method, client, interphone and soft upgrading system | |
| CN110824948A (en) | Intelligent household control method and device based on IOT virtual service | |
| WO2024007987A1 (en) | Vehicle-end firmware upgrading method and apparatus for digital key system, and device and medium | |
| CN115904447A (en) | Version updating system, method, electronic equipment and storage medium | |
| CN115016805A (en) | Vehicle system upgrading method, device, system, equipment and medium | |
| US20240069906A1 (en) | Server, software update system, distribution method, and non-transitory storage medium | |
| CN113094064A (en) | Gateway software module upgrading method, device, equipment and storage medium | |
| WO2020119732A1 (en) | Adjusting and testing method and apparatus for communication device networking | |
| CN107171915B (en) | Communication protocol changing method and device | |
| CN115484158A (en) | Communication configuration method and device of vehicle-mounted equipment based on eSIM card | |
| CN113422791B (en) | Cloud service configuration method and device, electronic equipment and computer readable storage medium | |
| CN114546444A (en) | Vehicle upgrading method and device, electronic equipment, medium and automatic driving vehicle | |
| CN113596030A (en) | Equipment network distribution method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |