Software upgrading method and system for vehicle intelligent key

Abstract

The application is suitable for the field of automobile electronic technology, and provides a software upgrading method and system for a vehicle intelligent key, which comprises the following steps: when the intelligent key and a lifting mechanism establish a communication connection, the intelligent key sends a version number of a software system installed in the intelligent key to the lifting mechanism; the lifting mechanism generates a version check request according to the version number and sends the version check request to a TSP server; the TSP server judges whether the software system of the intelligent key needs to be upgraded according to the version number in the version check request, and if the software system needs to be upgraded, sends an installation package of the latest version of the software system to the intelligent key, so that the intelligent key automatically upgrades the software system installed in the intelligent key. The application can automatically upgrade the software system in the vehicle intelligent key.

Description

Technical Field

[0001] This invention belongs to the field of automotive electronics technology, and in particular relates to a software upgrade method and system for vehicle smart keys. Background Technology

[0002] With the rapid development of the automobile industry, automobiles have gradually become the main means of transportation for people's daily travel, and vehicle keys have also evolved from the initial mechanical keys to today's smart remote control keys.

[0003] Currently, more advanced vehicle smart keys not only perform basic functions such as locking and unlocking the vehicle, starting the vehicle, and locking and unlocking the trunk, but also feature an LCD screen that displays real-time vehicle status information, allowing owners to monitor their car's condition at any time. These smart keys typically have an internal software system. Because software systems are constantly being improved, the software system in vehicle smart keys needs to be upgraded to obtain a version with better performance than the original. Currently, there is no method for automatically upgrading the software system in vehicle smart keys. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a software upgrade method and system for a vehicle smart key, so as to automatically upgrade the software system in the vehicle smart key.

[0005] The first aspect of the present invention provides a software upgrade method for a vehicle smart key, wherein the vehicle is provided with a lifting mechanism for holding the vehicle smart key, and when the smart key is placed on the lifting mechanism, the smart key establishes a communication connection with the lifting mechanism.

[0006] The software upgrade methods for vehicle smart keys include:

[0007] When the smart key establishes a communication connection with the lifting mechanism, the smart key sends the version number of the software system installed in the smart key to the lifting mechanism;

[0008] The lifting mechanism generates a version check request based on the version number and sends it to the TSP server.

[0009] The TSP server determines whether the smart key's software system needs to be upgraded based on the version number in the version check request. If so, it sends the latest version of the software system installation package to the smart key so that the smart key can automatically upgrade its installed software system.

[0010] Optionally, when the smart key establishes a communication connection with the lifting mechanism:

[0011] The smart key also sends its device information to the lifting mechanism;

[0012] Correspondingly, the lifting mechanism generates a version check request according to the version number, including:

[0013] The lifting mechanism obtains the identity information of the vehicle, and generates a version check request according to the version number, the device information, and the identity information of the vehicle.

[0014] Optionally, before the TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request, the TSP server further includes:

[0015] The TSP server authenticates the device information and the identity information in the version check request;

[0016] If the authentication is passed, the TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request;

[0017] If the authentication is not passed, the TSP server does not upgrade the software system of the smart key.

[0018] Optionally, the TSP server authenticates the device information and the identity information in the version check request, including:

[0019] The TSP server determines whether the target vehicle information exists in the pre-stored vehicle information table; wherein the vehicle information table stores vehicle information of a plurality of vehicles, and the vehicle information of each vehicle includes the identity information of the vehicle and the device information of the smart key corresponding to the vehicle, and the target vehicle information is the vehicle information containing the device information and the identity information in the version check request;

[0020] If the target vehicle information exists in the vehicle information table, the authentication is passed;

[0021] If the target vehicle information does not exist in the vehicle information table, the authentication is not passed.

[0022] Optionally, the TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request, including:

[0023] The TSP server determines whether the version number in the version check request is consistent with the version number of the latest version of the software system, and if so, determines that the software system of the smart key does not need to be upgraded;

[0024] If not, it is determined that the software system of the smart key needs to be upgraded.

[0025] Optionally, after it is determined that the software system of the smart key needs to be upgraded, further including:

[0026] The TSP server sends the version information of the latest version of the software system to the smart key;

[0027] The smart key displays version information of the latest version of the software system, and sends an upgrade confirmation instruction to the TSP server;

[0028] If the upgrade confirmation instruction is to agree to upgrade, the TSP server sends an installation package of the latest version of the software system to the smart key; if the upgrade confirmation instruction is to refuse to upgrade, the TSP server does not send the installation package of the latest version of the software system to the smart key.

[0029] Optionally, when the smart key is not placed on the lifting mechanism, the lifting mechanism is in a raised state; when the smart key is placed on the lifting mechanism, the lifting mechanism is in a sunken state.

[0030] In the process of upgrading the software system installed by the smart key, further comprising:

[0031] Locking the state of the lifting mechanism to the sunken state;

[0032] Locking the power mode of the vehicle to the on mode;

[0033] And locking the ignition switch of the vehicle to the invalid mode, the ignition switch of the vehicle cannot control the ignition or the extinguishing of the vehicle in the invalid mode.

[0034] Optionally, before the smart key automatically upgrades the software system installed by the smart key, further comprising:

[0035] The smart key backs up the version of the currently installed software system;

[0036] In the process of automatically upgrading the software system installed by the smart key, further comprising:

[0037] If the upgrade fails, the smart key installs the backed up version of the software system and deletes the installation package of the latest version of the software system.

[0038] Optionally, the device information is the MAC address of the smart key, and the identity information is the VIN number of the vehicle.

[0039] The second aspect of the embodiment of the application provides a software upgrading system of a vehicle smart key, comprising:

[0040] The smart key, the TSP server and the lifting mechanism located on the vehicle;

[0041] The lifting mechanism is used for placing the smart key of the vehicle, and when the smart key is placed on the lifting mechanism, the smart key establishes a communication connection with the lifting mechanism;

[0042] The smart key is used for sending the version number of the software system installed in the smart key to the lifting mechanism when the smart key establishes the communication connection with the lifting mechanism;

[0043] The lifting mechanism is used for generating a version check request according to the version number and sending to the TSP server.

[0044] The TSP server is used for judging whether the software system of the smart key needs to be upgraded according to the version number in the version check request, and if so, sending an installation package of the latest version of the software system to the smart key, so that the smart key automatically upgrades the installed software system.

[0045] Compared with the prior art, the embodiment of the present application has the beneficial effects that:

[0046] The embodiment of the present application establishes a communication connection between the smart key and the lifting mechanism, so that the smart key can send the version number of the installed software system in the smart key to the lifting mechanism, and then the lifting mechanism can generate a version check request according to the version number and send it to the TSP server, and the TSP server sends an installation package of the latest version of the software system to the smart key to upgrade the software system of the smart key. The present application establishes a communication link between the smart key, the lifting mechanism and the TSP server, so that the TSP server can automatically detect whether the software system of the smart key is the latest version, and can send an installation package of the latest version of the software system to the smart key, thereby realizing automatic upgrading of the software system of the smart key. BRIEF DESCRIPTION OF DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0048] Figure 1 is the implementation process schematic of the software upgrading method of the vehicle smart key provided by the embodiment of the present application Figure 1 ;

[0049] Figure 2 is the implementation process schematic of the software upgrading method of the vehicle smart key provided by the embodiment of the present application Figure 2 ;

[0050] Figure 3 is the structure schematic of the software upgrading system of the vehicle smart key provided by the embodiment of the present application. DETAILED DESCRIPTION

[0051] In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application can be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known methods, devices, circuits, and

[0052] In order to illustrate the technical solutions of the present application, the following will be described through specific embodiments.

[0053] First, the lifting mechanism in the present application is introduced. In the present application, a lifting mechanism is installed in the cab of the vehicle, which is used to place the smart key. The smart key and the lifting mechanism can be fixed by magnetic attraction, and in the fixed state, the two interact through four metal contact structures, two of which are used for the lifting mechanism to charge the smart key, and the other two are used for data communication between the smart key and the lifting mechanism, which can use UART serial communication, etc. The communication content includes device authentication, vehicle condition data, key control vehicle instruction, etc. The lifting mechanism obtains the engine state, vehicle speed, gear state in real time through the CAN network, and synchronizes the engine state, vehicle speed, gear state to the smart key in real time after protocol conversion. When the smart key is not placed in the lifting mechanism, the lifting mechanism remains raised, and its surface is flush with the interior trim of the vehicle. When the smart key is placed in the lifting mechanism and fixed by magnetic attraction, after the communication authentication between the two is completed, the lifting mechanism drives the smart key to automatically descend, and after descending to the position, the plane surface of the smart key is flush with the interior trim, preventing the key from being touched or knocked off. When the smart key is not connected with the lifting mechanism, the smart key only displays the unlock, lock, and find car function keys related to the key function; when the smart key is connected with the lifting mechanism, the smart key can display the START, STOP interface, and the owner can realize the start and stop or other control of the vehicle by clicking the START, STOP icons on the screen of the smart key.

[0054] Referring to Figure 1 The software upgrading method of the vehicle smart key of the embodiment includes the following steps.

[0055] Step one, when the smart key and the lifting mechanism establish a communication connection, the smart key sends the version number of the software system installed in the smart key to the lifting mechanism.

[0056] Step two, the lifting mechanism generates a version check request according to the version number and sends it to the TSP server.

[0057] Step three, the TSP server judges whether the software system of the smart key needs to be upgraded according to the version number in the version check request, and if so, sends the installation package of the latest version of the software system to the smart key, so that the smart key automatically upgrades the installed software system.

[0058] Most vehicle smart keys do not have networking functions, and only realize the unlocking and locking control of the vehicle through high-frequency or low-frequency or Bluetooth short-distance communication mode, so it is difficult to upgrade the software system of the smart key, and over time, the software system version of the smart key is backward, which greatly affects the user experience. Adding networking function to the smart key will greatly increase the cost, and the cost performance is low.

[0059] In view of the above problems, the embodiment of the present application designs a personalized and intelligent vehicle key, which has a display / touch screen and an operating system. When it is placed on the lifting mechanism of the vehicle, it can establish a communication connection with the lifting mechanism. Since the vehicle generally has networking function, after the vehicle communication module TBOX is connected with the vehicle networking background server TSP, the vehicle networking related services can be obtained.

[0060] The vehicle networking background TSP server has the functions of storing the software version number of the smart key, software storage, pushing, checking and issuing. Under the condition that the communication link of the smart key-lifting mechanism-TBOX-TSP is established, the TSP server can provide software update checking, pushing and downloading services. That is:

[0061] The smart key sends the version number of the software system installed in the smart key to the lifting mechanism;

[0062] The lifting mechanism generates a version check request according to the version number and sends it to the TSP server through the TBOX;

[0063] The TSP server judges whether the software system of the smart key needs to be upgraded according to the version number in the version check request, and if so, sends the installation package of the latest version of the software system to the smart key through the TBOX and the lifting mechanism, so as to automatically upgrade the software system of the smart key;

[0064] If the software system of the smart key is already the latest version, no installation package is sent.

[0065] It can be seen that the embodiment of the application establishes a communication connection between the smart key and the lifting mechanism, so that the smart key can send the version number of the software system installed by the smart key to the lifting mechanism, and then the lifting mechanism can generate a version check request according to the version number and send it to the TSP server, and the TSP server sends the installation package of the latest version of the software system to the smart key to upgrade the software system of the smart key. The application establishes a communication link between the smart key, the lifting mechanism and the TSP server, so that the TSP server can automatically detect whether the software system of the smart key is the latest version, and can send the installation package of the latest version of the software system to the smart key, thereby realizing the automatic upgrading of the software system of the smart key. Moreover, since the smart key needs to be connected to the lifting mechanism every time the owner gets into the car, the embodiment of the application can automatically check and upgrade the software system of the smart key every time the owner gets into the car.

[0066] As a possible implementation manner, referring to FIG. 1, Figure 2 As shown in FIG. 1, when the smart key establishes a communication connection with the lifting mechanism, the smart key also sends its device information to the lifting mechanism. The device information can be the MAC address of the smart key, and all key MAC addresses are unique and fixed.

[0067] Correspondingly, the lifting mechanism generates a version check request according to the version number, which can be detailed as follows:

[0068] The lifting mechanism obtains the identity information of the vehicle, which can be the VIN number of the vehicle, and generates a version check request according to the version number, the device information and the identity information of the vehicle.

[0069] Correspondingly, before the TSP server judges whether the software system of the smart key needs to be upgraded according to the version number in the version check request, the TSP server further includes:

[0070] The TSP server authenticates the device information and the identity information in the version check request;

[0071] If the authentication is passed, the TSP server judges whether the software system of the smart key needs to be upgraded according to the version number in the version check request;

[0072] If the authentication is not passed, the TSP server does not upgrade the software system of the smart key.

[0073] In this embodiment, by combining the MAC address of the smart key and the VIN number of the vehicle to generate a version check request, accurate identity authentication and recording of the request can be realized, and the connection security is improved.

[0074] As a possible implementation manner, the TSP server authenticates the device information and the identity information in the version check request, which can be detailed as follows:

[0075] The TSP server determines whether the target vehicle information exists in the pre-stored vehicle information table; wherein the vehicle information table stores vehicle information of a plurality of vehicles, the vehicle information of each vehicle includes identity information of the vehicle and device information of the smart key corresponding to the vehicle, and the target vehicle information is vehicle information containing the device information and the identity information in the version check request;

[0076] If the target vehicle information exists in the vehicle information table, the authentication is passed;

[0077] If the target vehicle information does not exist in the vehicle information table, the authentication is not passed.

[0078] In the embodiment, during the vehicle production and the smart key matching process, the production line data reading device binds the vehicle VIN and the smart key MAC address and uploads them to the production system server. The production system server forwards the bound vehicle VIN and key MAC to the TSP server and stores them.

[0079] When the smart key is put into the lifting mechanism, the lifting mechanism is lowered, the vehicle power mode is automatically switched from OFF to ON, at this time the smart key sends the MAC address and the software system version number to the lifting mechanism, after the lifting mechanism receives the MAC address and the version number sent by the smart key, it simultaneously obtains the vehicle VIN number from the gateway, and packs the VIN number, the MAC address and the version number to generate a version check request and sends it to the vehicle communication module TBOX, the TBOX forwards the above version check request to the TSP server. After the TSP server receives the version check request, it parses the VIN number, MAC address and version number in the request, and authenticates the VIN number and MAC address through the pre-stored vehicle information table, to ensure that the vehicle and the smart key are matched and the vehicle is the recorded vehicle in the TSP server, and to ensure the safety and reliability of software upgrading.

[0080] After the verification is passed, the TSP server determines whether the software system of the smart key needs to be upgraded, specifically, the TSP server determines whether the version number in the version check request is consistent with the version number of the latest version of the software system, if they are consistent, it is determined that the software system of the smart key does not need to be upgraded, the TSP server does not feedback, and the process is ended; if they are not consistent, it is determined that the software system of the smart key needs to be upgraded.

[0081] In the embodiment, each version of the software system of the smart key has a unique version number, the TSP server stores the version number and installation package of the latest version of the software system, and the TSP server can determine whether the software system of the smart key needs to be upgraded through consistency checking of the new and old version numbers. In a possible implementation manner, the TSP server can also determine how many versions are different between the current version and the latest version according to the version number of the software system of the smart key, and determine the importance of the upgrade, such as suggesting upgrade, strongly suggesting upgrade, etc. The above suggestions can be sent synchronously when the TSP server sends the version information to the smart key, so as to guide the user to upgrade and improve the user experience.

[0082] As a possible implementation manner, referring to FIG. 8, after determining that the software system of the smart key needs to be upgraded, the TSP server sends the installation package, and the process further includes the following steps: Figure 2

[0083] The TSP server sends the version information of the latest version of the software system to the TBOX;

[0084] The TBOX sends the version information to the lifting mechanism through CAN;

[0085] The lifting mechanism sends the version information to the smart key after protocol conversion, and the smart key displays a pop-up window on the screen after receiving the new version message, and the user selects whether to upgrade;

[0086] The smart key sends an upgrade confirmation instruction to the TSP server through the lifting mechanism and the TBOX;

[0087] If the upgrade confirmation instruction is to agree to upgrade, the TSP server sends the installation package of the latest version of the software system to the smart key; if the upgrade confirmation instruction is to refuse to upgrade, the TSP server does not send the installation package of the latest version of the software system to the smart key.

[0088] In this way, the user can freely choose whether to upgrade, fully meeting the user's wishes. Moreover, the upgrade can be performed at an appropriate time, reducing the impact of the upgrade process on the user's use of the vehicle.

[0089] In the embodiment, when the smart key is not placed on the lifting mechanism, the lifting mechanism is in a raised state; when the smart key is placed on the lifting mechanism, the lifting mechanism is in a sunken state.

[0090] As a possible implementation manner, in the process of upgrading the version information of the software system installed by the smart key, the process further includes:

[0091] Locking the state of the lifting mechanism to the sunken state;

[0092] ​locking the power mode of the vehicle as an on mode;

[0093] locking the ignition switch of the vehicle as an invalid mode, in which the ignition switch of the vehicle cannot control the vehicle to start or stop.

[0094] In the embodiment, during the upgrading process, the data link needs to be ensured to be in normal communication to prevent the upgrading process from being interrupted and causing the software system to be abnormal. Therefore, the state of the lifting mechanism is locked as the sinking state, and the lifting mechanism is not allowed to be lifted to take out the smart key, so as to ensure the connection between the smart key and the lifting mechanism to be normal. Meanwhile, the power mode of the vehicle is locked as the on mode, and the ignition switch of the vehicle is locked as the invalid mode, so as to ensure the data link to be in normal communication. The above-mentioned locking is always continued until the upgrading is completed or failed.

[0095] During the upgrading process, various unexpected situations may cause the upgrading to fail, for example, the installation memory of the smart key is insufficient, the network signal is interrupted, and the like. In order not to affect the normal use of the smart key, in an embodiment, before the smart key upgrades the version information of the software system installed by the smart key, the method further includes:

[0096] The smart key backs up the version of the software system currently installed;

[0097] During the process in which the smart key upgrades the version information of the software system installed by the smart key, the method further includes:

[0098] If the upgrading fails, the smart key prompts the installation to fail, and automatically installs the software system version that has been backed up, and deletes the installation package of the latest version of the software system.

[0099] Therefore, whether the software system of the smart key is upgraded successfully or not, the smart key can be normally used, and the situation that the smart key cannot be used due to the upgrading failure is avoided. Generally, the upgrading failure is caused by the network interruption or the abnormal data of the installation package. Therefore, the installation package of the latest version of the software system is incomplete or cannot be installed, and the installation package is deleted, so as to avoid the invalid installation package from occupying the storage space of the smart key.

[0100] It should be understood that the size of the serial number of each step in the above-mentioned embodiment does not mean the order of execution, and the execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0101] Referring to Figure 3 The embodiment of the present application provides a software upgrading system of a vehicle smart key, and the system includes:

[0102] The smart key, a TSP server and a lifting mechanism located on the vehicle;

[0103] The lifting mechanism is used for placing a smart key of a vehicle, and the smart key establishes a communication connection with the lifting mechanism when the smart key is placed on the lifting mechanism;

[0104] The smart key is configured to send a version number of a software system installed in the smart key to the lifting mechanism when the smart key establishes the communication connection with the lifting mechanism;

[0105] The lifting mechanism is configured to generate a version check request according to the version number and send the version check request to a TSP server;

[0106] The TSP server is configured to determine whether the software system of the smart key needs to be upgraded according to the version number in the version check request, and if so, send an installation package of the latest version of the software system to the smart key, so that the smart key automatically upgrades the software system installed therein.

[0107] As a possible implementation manner, when the smart key establishes the communication connection with the lifting mechanism, the smart key is configured to:

[0108] The smart key is further configured to send device information of the smart key to the lifting mechanism.

[0109] Correspondingly, the lifting mechanism is specifically configured to: obtain identity information of the vehicle, and generate the version check request according to the version number, the device information, and the identity information of the vehicle.

[0110] As a possible implementation manner, before determining whether the software system of the smart key needs to be upgraded according to the version number in the version check request, the TSP server is further configured to:

[0111] authenticate the device information and the identity information in the version check request;

[0112] If the authentication is passed, the TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request;

[0113] If the authentication is not passed, the TSP server does not upgrade the software system of the smart key.

[0114] As a possible implementation manner, the TSP server is specifically configured to:

[0115] The TSP server determines whether target vehicle information exists in a vehicle information table pre-stored by the TSP server; the vehicle information table stores vehicle information of a plurality of vehicles, the vehicle information of each vehicle includes identity information of the vehicle and device information of a smart key corresponding to the vehicle, and the target vehicle information is vehicle information containing the device information and the identity information in the version check request;

[0116] If the target vehicle information exists in the vehicle information table, the authentication is passed;

[0117] If the target vehicle information does not exist in the vehicle information table, the authentication fails.

[0118] As a possible implementation, the TSP server is specifically configured to:

[0119] determine whether the version number in the version check request is consistent with the version number of the latest version of the software system, and if so, determine that the software system of the smart key does not need to be upgraded;

[0120] if not, determine that the software system of the smart key needs to be upgraded.

[0121] As a possible implementation, after determining that the software system of the smart key needs to be upgraded:

[0122] the TSP server is further configured to send the version information of the latest version of the software system to the smart key;

[0123] the smart key is further configured to display the version information of the latest version of the software system and send an upgrade confirmation instruction to the TSP server; if the upgrade confirmation instruction is to agree to upgrade, the TSP server is further configured to send the installation package of the latest version of the software system to the smart key; if the upgrade confirmation instruction is to refuse to upgrade, the TSP server does not send the installation package of the latest version of the software system to the smart key.

[0124] As a possible implementation, during the process of upgrading the software system installed by the smart key:

[0125] locking the state of the lifting mechanism to the sinking state;

[0126] locking the power mode of the vehicle to the on mode;

[0127] and locking the ignition switch of the vehicle to the invalid mode, in which the ignition switch of the vehicle cannot control the ignition or the extinguishing of the vehicle.

[0128] As a possible implementation, before the smart key automatically upgrades the software system installed by the smart key, the smart key is further configured to back up the currently installed software system version.

[0129] During the process of automatically upgrading the software system installed by the smart key:

[0130] if the upgrade fails, the smart key is further configured to install the backed up software system version and delete the installation package of the latest version of the software system.

[0131] As a possible implementation, the device information is the MAC address of the smart key, and the identity information is the VIN number of the vehicle.

[0132] The above-described embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit the present application; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. A software upgrade method of a vehicle smart key, characterized by, The vehicle is provided with a lifting mechanism for placing a smart key of the vehicle; when the smart key is not placed on the lifting mechanism, the lifting mechanism remains in a raised state, and the surface of the lifting mechanism is flush with the interior trim of the vehicle; when the smart key is placed on the lifting mechanism, the smart key establishes a communication connection with the lifting mechanism, and the lifting mechanism charges the smart key, and the lifting mechanism automatically lowers the smart key to the surface of the smart key flush with the interior trim of the vehicle, at which time the lifting mechanism is in a sunken state; The method comprises: When the smart key establishes a communication connection with the lifting mechanism, the smart key sends a version number of a software system installed in the smart key to the lifting mechanism; The lifting mechanism generates a version check request according to the version number and sends it to a TSP server; The TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request, and if so, sends an installation package of the latest version of the software system to the smart key, so that the smart key automatically upgrades the software system installed therein; During the process of upgrading the software system installed in the smart key, further comprising: locking the state of the lifting mechanism as a sunken state; locking the power mode of the vehicle as an on mode; and locking the ignition switch of the vehicle as an invalid mode, in which the ignition switch of the vehicle cannot control the ignition or the extinguishing of the vehicle. 2.The software upgrade method of a vehicle smart key according to claim 1, wherein When the smart key establishes a communication connection with the lifting mechanism: The smart key also sends device information of the smart key to the lifting mechanism; Correspondingly, the lifting mechanism generates a version check request according to the version number, comprising: The lifting mechanism obtains the identity information of the vehicle and generates the version check request according to the version number, the device information and the identity information of the vehicle. 3.The software upgrade method of a vehicle smart key according to claim 2, wherein Before the TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request, further comprising: The TSP server authenticates the device information and the identity information in the version check request; If the authentication is passed, the TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request; If the authentication is not passed, the TSP server does not upgrade the software system of the smart key. 4.The software upgrade method of a vehicle smart key according to claim 3, wherein The TSP server authenticates the device information and the identity information in the version check request, comprising: The TSP server determines whether the target vehicle information exists in the pre-stored vehicle information table; wherein the vehicle information table stores vehicle information of a plurality of vehicles, and the vehicle information of each vehicle comprises the identity information of the vehicle and the device information of the smart key corresponding to the vehicle, and the target vehicle information is the vehicle information containing the device information and the identity information in the version check request; If the target vehicle information exists in the vehicle information table, the authentication is passed; If the target vehicle information does not exist in the vehicle information table, the authentication fails. 5.The software upgrade method of a vehicle smart key according to claim 1, wherein The TSP server determines whether the software system of the smart key needs to be upgraded according to the version number in the version check request, including: The TSP server determines whether the version number in the version check request is consistent with the version number of the latest version of the software system, and if so, determines that the software system of the smart key does not need to be upgraded. If not, it is determined that the software system of the smart key needs to be upgraded. 6.The software upgrade method of a vehicle smart key according to claim 1, wherein After determining that the software system of the smart key needs to be upgraded, further comprising: The TSP server sends the version information of the latest version of the software system to the smart key; The smart key displays the version information of the latest version of the software system and sends an upgrade confirmation instruction to the TSP server; If the upgrade confirmation instruction is to agree to upgrade, the TSP server sends the installation package of the latest version of the software system to the smart key; if the upgrade confirmation instruction is to refuse to upgrade, the TSP server does not send the installation package of the latest version of the software system to the smart key.

7. The software upgrade method of a vehicle smart key according to claim 1, wherein Before the smart key automatically upgrades the software system installed thereon, further comprising: The smart key backs up the currently installed software system version; During the process of the smart key automatically upgrading the software system installed thereon, further comprising: If the upgrade fails, the smart key installs the backed up software system version and deletes the installation package of the latest version of the software system. 8.The software upgrade method of a vehicle smart key according to claim 2, wherein The device information is the MAC address of the smart key, and the identity information is the VIN number of the vehicle.

9. A software upgrade system for a vehicle key fob, the system comprising: Comprising: A smart key, a TSP server and a lifting mechanism located on the vehicle; The lifting mechanism is used to place the smart key of the vehicle; When the smart key is not placed in the lifting mechanism, the lifting mechanism remains in a raised state, and the surface of the lifting mechanism is flush with the interior trim of the vehicle; when the smart key is placed on the lifting mechanism, the smart key establishes a communication connection with the lifting mechanism, and the lifting mechanism charges the smart key, and the lifting mechanism automatically lowers the smart key to the surface of the smart key flush with the interior trim of the vehicle, at this time the lifting mechanism is in a sunken state; The smart key is used to send the version number of the software system installed in the smart key to the lifting mechanism when establishing a communication connection with the lifting mechanism; The lifting mechanism is used to generate a version check request according to the version number and send it to the TSP server; The TSP server is used to determine whether the software system of the smart key needs to be upgraded according to the version number in the version check request, and if so, to send the installation package of the latest version of the software system to the smart key to enable the smart key to automatically upgrade the software system installed thereon; During the process of the smart key upgrading the software system installed thereon, the software upgrade system is further used for: Locking the state of the lifting mechanism to the sunken state; Locking the power mode of the vehicle to the on mode; and the ignition switch of the vehicle is locked in an inoperative mode in which the vehicle cannot be controlled to be ignited or turned off.

Images