Patent Description:
Modem cars/vehicles are equipped with hundreds of electronic devices from different manufacturers. Each electronic device is different, and performs a specific operation. Software in the electronic device controls the operation.

A supplier of electronic device(s) submits a software patch to an over-the-air (OTA) server. The OTA server forwards the software patch to the vehicle. The corresponding electronic device in the vehicle installs the software patch. Currently, the OTA sever does not have a mechanism for monitoring and maintaining software for the electronic devices in the vehicle.

Document <CIT> discloses autonomous global software update, wherein a computer-implemented method includes subscribing to a first topic tree topic associated with an installed vehicle software component version; identifying a desired software component version based on a published notification retrieved from the first topic; and when the desired version and the installed version differ, updating a software component using a software update retrieved from a second topic tree topic associated with software updates to the installed version.

Document <CIT> discloses a vehicle-mounted software configuration upgrading management method, a server, a client and a processing terminal comprise the steps of receiving version configuration packages, analyzing all the version configuration packages to obtain and store version attribute data, and updating the version attribute data according to preset logic; receiving upgrade path data, updating the version tree according to the upgrade path data to obtain version tree information, and sending the version tree information; receiving upgrade device data, selecting upgrading equipment according to the upgrading equipment data; and setting upgrading plan data according to the version tree and the version attribute data.

Embodiments of this application provide a method for managing software versions of electronic device(s) in a vehicle and a relevant device. The technical solution provides a lightweight solution for software version control of the electronic devices in a vehicle. The present application is defined in the appended independent claims. Further implementations are disclosed in the pending independent claims. In the following, implementations not falling within the scope of the claims are to be understood as examples useful for understanding the claims.

The above-mentioned technical solution provides a lightweight and efficient version control mechanism for maintaining the software versions for each the electronic devices in a vehicle.

<FIG> is a flowchart of the embodiment of a method for managing software versions of electronic device(s) in a vehicle according to the present invention.

<NUM>, an OTA server receives M patches from M providers. Correspondingly, the M providers transmit the M patches to the OTA server.

The M patches are in one-to-one correspondence with M electronic devices in a vehicle of a target model, M is a positive integer greater than or equal to <NUM>.

In some embodiments, the patch mentioned in the present application may also be referred as an update, an update packet or the like.

The target model refers to one particular type of car model. For example, the target model is BMW-series-<NUM>-<NUM> Q1. All cars of the target model have exactly same electronic devices.

The process of receiving a patch from a provider will be described in detail later.

<NUM>, the OTA server stores the M patches.

<NUM>, the OTA server updates a global version tree (GVT) corresponding to the vehicle of the target model according to the M patches to obtain an updated GVT.

Each car model has a corresponding GVT. For example, BMW-series-<NUM>-<NUM> Q1 corresponds to GVT <NUM>, BMW-series-<NUM>-<NUM> Q2 corresponds to GVT <NUM>. Different car models have different electronic devices. Therefore, GVTs corresponding to different car models include different information.

A piece of the second software information include identity information of an electronic device in the vehicle of the target model and a software version numbers of the electronic device in the vehicle of the target model.

In some embodiments, the software mentioned in the present application may also be referred as a firmware.

For example, a format of the piece of the second software information may be [MFR_ID: Version], where MFR_ID is the ID to identify the type of the electronic device and manufacturer, and Version is the current software version of the electronic device.

For the GVT corresponding to the target model, the GVT has different versions. For example, the GVT that need to be updated in step <NUM> is version <NUM>, and the updated GVT is version <NUM>. For ease of description, the GVT that need to be updated in step <NUM> is referred to as GVT v1, and the updated GVT is referred to as GVT v2. Under this condition, step <NUM> can be interpreted as the OTA server updates GVT v1 according to the M patches to obtain GVT v2.

GVT v1 includes multiple pieces of a second software information. GVT v2 includes multiple pieces of the second software information. In some embodiments, For example, GVT v1 includes K pieces of the second software information, and GVT v2 includes K pieces of the second software information, K is a positive integer and greater than or equal to M.

For the GVT v1 and GVT v2, the software version numbers of the M electronic devices included in GVT v2 are different from the software version numbers of the M electronic devices included in GVT v1. The software version numbers of the M electronic devices included in GVT v2 is the latest software version numbers, and the software version numbers of the M electronic devices included in GVT v1 is the previous one. If K is greater than M, the software version numbers of the K-M electronic devices included in GVT v2 will be the same as the software version numbers of the K-M electronic devices included in GVT v1.

<FIG> shows the GVT v1 and the GVT v2. TB, CC, DC (including DC1 to DC <NUM>) and E (including E1 to E9) shown in <FIG> represent the telematics box, the central controller, the domain controller and the Electronic Control Units in the vehicle respectively.

Referring to <FIG>, the software information corresponding to the DC1 included in the GVT v1 is different from the software information corresponding to the DC1 included in the GVT v2. More specifically, the software version numbers of the DC1 included in the GVT v1 is different from the software version numbers of the DC1 included in the GVT v2. The software version numbers of the DC <NUM> included in the GVT v1 is V4, and the software version numbers of the DC1 included in the GVT v2 is V6. Larger software version numbers indicate newer software version. Therefore, the software version of DC1 included in the GVT v1 is older than the software version of DC1 included in the GVT v2.

Similarly, the software version numbers of the E2 and E8 included in the GVT v1 are different from the software version numbers of the E2 and E8 included in the GVT v2.

<NUM>, the OTA server determines an update bundle according to the updated GVT, wherein the update bundle includes N patches N is a positive integer greater than or equal to <NUM>.

Optionally, in some embodiments, according to the updated GVT, the OTA server determines that the software version numbers of M electronic devices have changed. Therefore, the OTA server may determines that the update bundle includes the M patches corresponding to the M electronics devices received in step <NUM>. Under this condition, N equals M.

<FIG> is taken as an example. The update bundle include <NUM> patches which are used to update DC <NUM>, E2 and E8.

Optionally, in some embodiments, according to the updated GVT, the OTA server determines that software version numbers of N critical electronic devices have changed. The OTA server also determines that software version numbers of M-N non-critical electronic devices have changed as well. Under this condition, the OTA server may determine that the update bundle includes the patches corresponding to the critical electronic devices. M is greater than N.

<FIG> is taken as an example. It is assumed that DC1 and E2 are critical electronic devices and E8 is a non-critical electronic device. The update bundle include <NUM> patches which are used to update DC1 and E2.

Optionally, in some embodiments, the OTA server may determines the update bundle according to the updated GVT and a vehicle version tree (VVT) corresponding to a target vehicle.

The OTA server stores a plurality of VVTs. The plurality of VVTs are in one-to-one correspondence with a plurality of vehicles. The model of the plurality of vehicles is the target model. The target vehicle is one of the plurality of vehicles.

The VVT corresponding to the target vehicle includes a plurality of pieces of a first software information. A piece of the first software information includes identity information of an electronic device in the target vehicle and a current software version numbers of the electronic device in the target vehicle. A format of the piece of the first software information is similar to the format of the piece of the second software information. For example, the format of the piece of the first software information may be [MFR_ID, DEV_ID: Version], where MFR_ID is the ID to identify the type of the electronic device and manufacturer, DEV_ID is the unique ID of the electronic device, and Version is the current software version of the electronic device.

Optionally, in some embodiments, the determining, by the OTA server, the update bundle according to the updated GVT and the VVT corresponding to a target vehicle including: determining, by the OTA sever, N electronic devices, wherein the software version numbers of the N electronic devices in the updated GVT and the VVT are different; determining, by the OTA sever, the update bundle, wherein the updated bundle including N patches which are used to update the N electronic devices. If the N patches are installed successfully, the software version numbers of the N electronic device in the target vehicle will be the same as the software version numbers of the N electronic device in the updated GVT. In this case, N equals M.

Optionally, in some embodiments, the determining, by the OTA server, the update bundle according to the updated GVT and the VVT corresponding to a target vehicle including: determining, by the OTA sever, M electronic devices include N critical electronic devices, wherein the software version numbers of the M electronic devices in the updated GVT and the VVT are different; determining, by the OTA sever, the update bundle, wherein the updated bundle including N patches which are used to update the N critical electronic devices. If the N patches are installed successfully, the software version numbers of the N electronic device in the target vehicle will be the same as the software version numbers of the N electronic device in the updated GVT. In this case, N is less than or equal to M.

Optionally, in some embodiments, the OTA server may periodically check the difference between the updated GVT and the VVT of the target vehicle. If there is any difference between the updated GVT and the VVT of the target vehicle, the OTA server may determine the update bundle.

Optionally, in some embodiments, the OTA server may check if there is at least one critical patch in the M patches. If the M patches include one or more critical patches, the OTA server may determine the update bundle and the update bundle includes the one or more critical patches. If the M patches do not include the one or more critical patches, the OTA server will not determine the update bundle. In other words, the OTA server may only determine the update bundle after receiving at least one critical patch from the provider.

<NUM>, the OTA server transmits the update bundle to the target vehicle. Correspondingly, the target vehicle receives the update bundle from the OTA server.

As described above, the update bundle includes N patches. The N patches are in one-to-one correspondence with the N electronic devices in the target vehicle, each patch of the N patches is used to update software of a corresponding electronic device.

Optionally, in some embodiments, the OTA server may establish secure channel with the target vehicle. More specifically, the OTA server may establish a channel with the target vehicle based on a security technique or protocol (e.g., Transport Layer Security (TLS), Secure Sockets Layer (SSL), Hypertext Transfer Protocol Secure (HTTPs), etc.). The update bundle may be transmitted on the secure channel.

Optionally, in some embodiments, before transmitting the update bundle to the target vehicle, the OTA sever may transmit notification information to the target vehicle. Corresponding, the target vehicle receives the notification information. The notification information is used to indicate the target vehicle receives the update bundle. Optionally, the target vehicle may transmits notification response information to the OTA server. The notification response information is used to indicate that the target vehicle received the notification information and the target vehicle is ready to receive the update bundle. The OTA server transmits the update bundle to the target vehicle after receiving the notification response information.

The target vehicle include a plurality of electronic devices. The plurality of electronic devices includes the N electronic devices. In some embodiments, the plurality of electronic devices include one telematics box (TBox), one central controller (CC), a plurality of domain controllers (DC) and a plurality of Electronic Control Units (ECU).

<FIG> is a schematic structural diagram of the target vehicle of the present invention.

Referring to <FIG>, the target vehicle includes TBox <NUM>, CC <NUM>, DC <NUM>, DC <NUM> and DC <NUM>. The target vehicle further includes ECU <NUM>, ECU <NUM>, ECU <NUM>, ECU <NUM>, ECU <NUM>, ECU <NUM>, ECU <NUM>, ECU <NUM>, and ECU <NUM>. TBox <NUM> connects to CC <NUM>. DC <NUM>, DC <NUM> and DC <NUM> connect to CC <NUM>. ECU <NUM>, ECU <NUM> and ECU <NUM> connect to DC <NUM>; ECU <NUM> and ECU <NUM> connect to DC <NUM>; ECU <NUM>, ECU <NUM>, ECU <NUM> and ECU <NUM> connect to DC <NUM>.

The TBox incorporates a wireless communication module. The TBox may communicates with the OTA server over any of wireless communication methods like Wireless Fidelity (WiFi), Long Term Evolution (LTE), <NUM> and the like.

The TBox of the target vehicle receives the update bundle and transmits the update bundle to the CC.

Optionally, in some embodiments, a message carrying the update bundle may be protected by using a private key/public key pair of the TBox. For example, the OTA server may use the public key of the TBox to encrypt the message carrying the update bundle and transmit the encrypted message to the target vehicle. The TBox of the target vehicle may decrypt the encrypted message using a private key of the TBox to obtain the update bundle.

Optionally, in some embodiments, in addition to carrying the update bundle, the message may carry a Nonce. The TBox may check the Nonce carried in the message to verify the message is sent by the OTA server.

Optionally, in some embodiments, the message carrying the notification information may carry a Nonce. The TBox may check the Nonce carried in the message to verify the message is sent by the OTA server.

Optionally, in some embodiments, the message carrying the notification response information may carry a Nonce. The OTA server may check the Nonce carried in the message to verify the message is sent by the target vehicle.

Optionally, in some embodiments, the TBox may use a symmetric key KTBox_CC to encrypt the update bundle and transmit the encrypted update bundle to the CC. The CC may use the symmetric key KTBox_CC to decrypt the encrypted update bundle to obtain the N patches.

Optionally, in some embodiments, the TBox may forward the update bundle directly to the CC. In another word, the update bundle transmitted by the TBox is not encrypted.

Optionally, in some embodiments, the CC may use a symmetric key KCC_DC to encrypt each of the N patches and transmit the encrypted patch to the corresponding electronic device. The corresponding electronic device may use the symmetric key KCC_DC to decrypt the encrypted patch to obtain a corresponding patch.

Optionally, in some embodiments, the CC may forward the N patches directly to the corresponding electronic devices. In another word, the patch transmitted by the CC is not encrypted.

After receiving the patch, the electronic device may install the patch while the target vehicle is charging, parking or the like.

For example, the update bundle includes <NUM> patches. The <NUM> patches are used to update DC <NUM>, ECU <NUM> and ECU <NUM> respectively. Under this condition, the CC may transmit the patches which are used to update DC <NUM> and ECU <NUM> to DC <NUM>, and may transmit the patch which is used to update ECU <NUM> to DC <NUM>. DC <NUM> may transmit the patch which is used to update ECU <NUM> to ECU <NUM>. DC <NUM> may transmit the patch which is used to update ECU <NUM> to ECU <NUM>. DC <NUM>, ECU <NUM> and ECU <NUM> may install the received patch.

All above-mentioned embodiments assume that the N patches do not include a patch for the TBox and/or the CC. If the N patches include the patch for the TBox, the TBox will transmit an update bundle without the patch for the TBox to the CC. Similarly, if the updated bundle received by the CC includes the patch for the CC, the CC will transmit the patches for updating the DC and the ECU to the corresponding electronic devices.

<NUM>, the target vehicle transmits an update response to the OTA sever, wherein the update response is used to indicate one or more patches which have been successfully installed among the N patches.

After completing the patch installation process, the electronic device may send an update result to the upper electronic device. The update result is used to indicate if the electronic device successfully installed the received patch.

The upper electronic device of the ECU is the DC, the upper electronic device of the DC is the CC, and the upper electronic device of the CC is the TBox. Referring to <FIG>, the upper electronic device of ECU <NUM>, ECU <NUM> and ECU <NUM> is DC <NUM>, the upper electronic device of ECU <NUM> and ECU <NUM> is DC <NUM>, the upper electronic device of DC <NUM>, DC <NUM> and DC <NUM> is CC <NUM>, and the upper electronic device of CC <NUM> is TBox <NUM>. The TBox may collect all update results and determine the update response. In some embodiments, the update response may indicate an electronic device which successfully installed the received patch and/or an electronic device which failed to install the received patch.

Optionally, in some embodiments, the update result transmitted by the ECU, the DC and or the CC may be encrypted by the transmitter. For example, the transmitter may encrypt the update result by using a symmetric key. After receiving the encrypted update result, the receiver may use the symmetric key to decrypt the encrypted update result.

Optionally, in some embodiments, the update response may be used to indicate whether the N patches have been successfully installed.

For example, in some embodiments, if the update response includes a first preset value (e.g. <NUM>), the OTA server may determine that each of the N electronic devices successfully installed the corresponding patch; if the update response includes a second preset value (e.g. <NUM>), the OTA server may determine that none of the N electronic devices successfully installed the corresponding patch.

In some embodiments, if the update response includes identity information of at least one electronic device (e.g. DEV_ID), the OTA server may determine that the at least one electronic device successfully installed the received patches, and may determine other electronic devices failed to install the received patches.

For example, the update bundle include <NUM> patches which are used to update DC <NUM>, E2 and E8. If update response includes 0x03 and 0x008 (that is, the DEV_IDs of DC <NUM> and E8), the OTA server may determine that DC <NUM> and E8 successfully installed the received patches and E2 failed to install the received patch.

In some other embodiments, if the update response includes identity information of at least one electronic device, the OTA server may determine that the at least one electronic device failed to installed the received patches, and may determine other electronic devices successfully installed the received patches.

For example, the update bundle include <NUM> patches which are used to update DC <NUM>, E2 and E8. If update response includes 0x03 and 0x008 (that is, the DEV_IDs of DC <NUM> and E8), the OTA server may determine that DC <NUM> and E8 failed to install the received patches and E2 successfully installed the received patch.

<NUM>, the OTA updates the VVT corresponding to the target vehicle according to the update response to obtain an updated VVT.

For ease of description, the VVT that need to be updated in step <NUM> is referred to as VVT v1, and the updated VVT is referred to as VVT v2. Under this condition, the VVT is used to determine the update bundle is the VVT v1.

<FIG> shows the GVT v2, the VVT v1 and the VVT v2. TB, CC, DC (including DC1 to DC <NUM>) and E (including E1 to E9) shown in <FIG> represent the telematics box, the central controller, the domain controller and the ECU respectively.

It is assumed that the updated bundle includes the patches for updating DC1, E2 and E8 and all of these electronic devices successfully installed the corresponding patches. Referring to <FIG>, the software version numbers of DC1 in the VVT v1 is V4, the software version numbers of DC1 in GVT v2 is V6. Under this condition, the patch corresponding to DC1 included in the update bundle is used to update DC1 from version V4 to version V6. After installing the patch corresponding to DC1, the software version numbers of DC1 is updated to V6. Therefore, the current software version numbers of DC1 is V6. According to the update response, the OTA server may change the software version numbers of DC1 from V4 to V6. Therefore, the software version numbers of DC1 in the VVT v2 shown in <FIG> is V6.

According to the invention, the OTA server determines. VVT information according to the updated VVT (that is, the VVT v2) and transmits the VVT information to the target vehicle. The VVT information is used to indicate the multiple pieces of the first software information included in the VVT v2. Correspondingly, the target vehicle receives the VVT information and stores the VVT information.

For example, the VVT information is a string with all pieces of the first software information in lexicographical order at each level. The VVT v2 shown in <FIG> is taken as an example. The VVT information M determined according to the VVT v2 shown in <FIG> is {[MFR_AA, 0x01: V4] ∥ [MFR_BB, 0x02: V3] ∥ [MFR_CC, 0x03: V6] ∥ [MFR_DD, 0x001: V2] ∥ [MFR_EE, 0x002: V2] ∥ [MFR_FF, 0x003: V4] ∥ [MFR_GG, 0x04: V3] ∥ [MFR_HH, 0x004: V3] ∥ [MFR_II, 0x005: V3] ∥ [MFR_JJ, 0x05: V5] ∥ [MFR_KK, 0x005: V5] ∥ [MFR_LL, 0x007: V2] ∥ [MFR_MM, 0x008: V6] ∥ [MFR_N, 0x009: V4] }.

Optionally, in some embodiments, a Persistent Segment Tree (PST) may be used to show the new and old versions of the VVT or the GVT.

The VVT v1 and VVT v2 in <FIG> are taken as an example. <FIG> shows a PST corresponding to the VVT v1 and VVT v2. For ease of description, it is assumed that the software versions included in the VVT v1 are the software versions of the software installed in the factory. In other words, the target vehicle has never received an update packet before receiving the update packet including <NUM> patches for updating DC <NUM>, E2, and E8.

Referring to <FIG>, the PST includes Tree v1 and Tree v2. The Tree v1 corresponds to the VVT v1 shown in <FIG>. The TB shown in the Tree v1 represents the first software information of the TBox in the VVT v1, the CC shown in the Tree v1 represents the first software information of the CC in the VVT v1, and so on.

The Tree v2 shown in <FIG> corresponds to the VVT v2 shown in <FIG>. The CC shown in the Tree v2 represents the first software information of the CC in the VVT v1 shown in <FIG>, the DC1 shown in the Tree v2 represents the first software information of the DC1 in the VVT v2 shown in <FIG>, the DC3 shown in the Tree v2 represents the first software information of the DC3 in the VVT v1 shown in <FIG>, the E2 shown in the Tree v2 represents the first software information of the E2 in the VVT v2 shown in <FIG>, the E8 shown in the Tree v2 represents the first software information of the E8 in the VVT v2 shown in <FIG>.

Tree v2 shown in <FIG> is another embodiment of the updated VVT. The updated VVT includes multiple pieces of the first software information. The multiple pieces of the first software information are in one-to-one correspondence with multiple electronic devices of the target vehicle. The multiple electronic devices include at least one first electronic device and at one second electronic device. The first electronic device is an electronic device of the target vehicle which has successfully installed a patch included in the update bundle received in step <NUM>. The second electronic device is the upper electronic device of the first electronic device. For example, DC1, E2 and E3 are the first electronic devices, and CC and DC3 are the second electronic devices.

The OTA server may determine VVT information according to the Tree v2. In some embodiments, the VVT information is a string with the first information included in the Tree v2. Under this condition, the VVT information M is {[MFR_BB, 0x02: V3] ∥ [MFR_CC, 0x03: V6] ∥ [MFR_EE, 0x002: V2] ∥ [MFR_JJ, 0x05: V5] ∥ [MFR_MM, 0x008: V6]}. In some other embodiments, the VVT information is a string with the first software information of the updated electronic devices. Under this condition, the VVT information M s {[MFR_CC, 0x03: V6] ∥ [MFR_EE, 0x002: V2] ∥ [MFR_MM, 0x008: V6]}.

Similar to a VVT, the updated GVT includes multiple pieces of the second software information. The multiple pieces of the first software information are in one-to-one correspondence with multiple electronic devices of the vehicle of the target model. The multiple electronic devices include at least one third electronic device and at one fourth electronic device. The M patches include a patch for the third electronic device. The fourth electronic device is the upper electronic device of the third electronic device. Under this condition, the number of software information included in GVT v2 is different from the number of software information included in GVT v1.

Optionally, in some embodiments, the OTA server may store the VVT information. The VVT information may be stored in a log book or a table.

Optionally, in some embodiments, the OTA server may determine a time stamp corresponding to the VVT information and transmit the time stamp to the target vehicle. Correspondingly, the target vehicle receives the time stamp and store the time stamp with the corresponding VVT information.

In some embodiments, the time stamp may be incorporated in the VVT information. For example, the VVT information M determined according to the VVT v2 shown in <FIG> is {[MFR_AA, 0x01: V4] ∥ [MFR_BB, 0x02: V3] ∥ [MFR_CC, 0x03: V6] ∥ [MFR_DD, 0x001: V2] ∥ [MFR_EE, 0x002: V2] ∥ [MFR_FF, 0x003: V4] ∥ [MFR_GG, 0x04: V3] ∥ [MFR_HH, 0x004: V3] ∥ [MFR_II, 0x005: V3] ∥ [MFR_JJ, 0x05: V5] ∥ [MFR_KK, 0x005: V5] ∥ [MFR_LL, 0x007: V2] ∥ [MFR_MM, 0x008: V6] ∥ [MFR_N, 0x009: V4] ∥ Tv}, the VVT information M determined according to the Tree V2 shown in <FIG> is {[MFR_BB, 0x02: V3] ∥ [MFR_CC, 0x03: V6] ∥ [MFR_EE, 0x002: V2] ∥ [MFR_JJ, 0x05: V5] ∥ [MFR_MM, 0x008: V6] ∥ Tv}, wherein Tv is the time stamp. In another word, the time stamp is a part of the VVT information.

In some other embodiments, the time stamp is independent of the VVT information. In another word, the time stamp is not a part of the VVT information.

In some embodiments, the OTA server may use the public key of the target vehicle to encrypt the VVT information and transmit the encrypted VVT information to the target vehicle. The target vehicle may use the private key of the target vehicle to decrypt the encrypted VVT information to obtain the VVT information. Similarity, if the time stamp is independent of the VVT information, the OTA server may use the public key of the target vehicle to encrypt the time stamp and transmit the encrypted time stamp to the target vehicle. The target vehicle may use the private key of the target vehicle to decrypt the encrypted time stamp to obtain the time stamp.

In some embodiments, the OTA server may do not transmit the time stamp to the target vehicle. The target vehicle may the time stamp based on the time at which the VVT information was received and store the determined time stamp.

The above-mentioned technical solution provides a lightweight solution for software version control of the electronic devices in a vehicle. The OTA sever stores the current software information of the vehicle (that is, the VVT). Meanwhile, the OTA server and the vehicle store the update history (that is the VVT information). In addition, in some embodiments of the technical solution, the information transmitted between the OTA server and the vehicle is encrypted by using a public key of the receiver. Therefore, the technical solution provides a secure mechanism for maintaining the software of the electronic devices in the vehicle.

<FIG> is a flowchart of the embodiment of a method for receiving a patch from a provider according to the present invention.

<NUM>, an OTA server may establish secure channel with a provider.

For example, the OTA server may establish a channel with the provider based on a security technique or protocol (e.g., Transport Layer Security (TLS), Secure Sockets Layer (SSL), Hypertext Transfer Protocol Secure (HTTPs), etc.). The message transmitted by the OTA server or the provider may be transmitted on the secure channel.

<NUM>, the provider transmits a patch which is used to update software of an electronic device in a vehicle to the OTA server.

Optionally, in some embodiments, the patch transmitted by the provider may be protected by using a public key of the OTA server. For example, the provider may use the public key of the OTA server to encrypt the patch. The OTA server may decrypt the encrypted patch using a private key of the OTA server to obtain the patch.

Optionally, in some embodiments, in addition to carrying the patch, the message may carry a Nonce. The OTA server may check the Nonce carried in the message to verify the message is sent by the provider.

Optionally, in some embodiments, before transmitting the patch to the OTA server, the provider may transmit notification information to the OTA server. Corresponding, the OTA server receives the notification information. The notification information is used to indicate the OTA server receives the patch. Optionally, the OTA server may transmits notification response information to the provider. The notification response information is used to indicate that the OTA server received the notification information and the OTA server is ready to receive the patch. The provider transmits the patch to the OTA server after receiving the notification response information.

Optionally, in some embodiments, the message carrying the notification information may carry a Nonce. The OTA sever may check the Nonce carried in the message to verify the message is sent by the provider.

Optionally, in some embodiments, the message carrying the notification response information may carry a Nonce. The provider may check the Nonce carried in the message to verify the message is sent by the OTA server.

Optionally, in some embodiments, the notification information may be encrypted by using the public key of the OTA server. The OTA may use the private key of the OTA server to decrypt the encrypted notification information.

Optionally, in some embodiments, the notification response information may be encrypted by using a public key of the provider. The provider may use a private key of the provider to decrypt the encrypted notification response information.

<FIG> is a schematic block diagram of a server <NUM> according to an embodiment of this application. As shown in <FIG>, the server <NUM> includes: a transmitting module <NUM>, a receiving module <NUM> and a determining module <NUM>.

The transmitting module701 is configured to transmit an update bundle to a target vehicle.

The update bundle includes N patches. The N patches are in one-to-one correspondence with N electronic devices in the target vehicle. Each patch of the N patches is used to update software of a corresponding electronic device. N is a positive integer greater than or equal to <NUM>.

The receiving module <NUM> is configured to receive an update response from the target vehicle.

The update response is used to indicate one or more patches which have been successfully installed among the N patches.

The determining module <NUM> is configured to update a VVT corresponding to the target vehicle according to the update response to obtain an updated VVT.

The updated VVT includes multiple pieces of a first software information. A piece of the first software information includes identity information of an electronic device in the target vehicle and a current software version numbers of the electronic device in the target vehicle.

According to the invention, the determining module <NUM> is further configured to determine VVT information according to the updated VVT, wherein the VVT information is used to indicate the multiple pieces of the first software information included in the updated VVT; and the transmitting module <NUM> is further configured to transmit the VVT information to the target vehicle.

Optionally, the determining module <NUM> is further configured to determine a time stamp corresponding to the VVT information; and the transmitting module <NUM> is further configured to transmit the time stamp to the target vehicle.

Optionally, the identity information of the electronic device in the target vehicle includes: a first identity information, a second identity information and a third identity information, wherein the first identity information is used to indicate an identity of a manufacturer of the electronic device in the target vehicle, the second identity information is used to indicate an identity of a type of the electronic device in the target vehicle, and the third identity information is used to indicate the electronic device in the target vehicle.

Optionally, the receiving module <NUM> is further configured to receive the M patches from M providers, wherein the M patches are in one-to-one correspondence with M electronic devices in a vehicle of a target model, M is a positive integer greater than or equal to <NUM>; and the determining module <NUM> is further configured to: store the M patches; update a global version tree, GVT, corresponding to the vehicle of the target model according to the M patches to obtain an updated GVT, wherein the updated GVT includes multiple pieces of a second software information, a piece of the second software information includes identity information of an electronic device in the vehicle of the target model and a latest software version numbers of the electronic device in the vehicle of the target model, the model of the target vehicle is the target model; and determine the update bundle according to the updated GVT, wherein the M patches include the N patches.

Optionally, the determining module <NUM> is configured to determine the N electronic devices according to the VVT and the updated GVT, wherein software version numbers of any one of the N electronic devices in the VVT is different from software version numbers of the any one of the N electronic devices in the updated GVT; and determine the update bundle, wherein software version numbers of the N electronic device in the VVT and in the updated GVT are different.

Optionally, the determining module <NUM> is further configured to determine the M patches include at least one critical patch, and the determining module <NUM> is specifically configured to determine that the update bundle includes the at least one critical patch.

Optionally, the identity information of an electronic device in the vehicle of the target model includes: a fourth identity information, a fifth identity information and a sixth identity information, wherein the fourth identity information is used to indicate an identity of a manufacturer of the electronic device in the vehicle of the target model, the fifth identity information is used to indicate an identity of a type of the electronic device in the vehicle of the target model, and the sixth identity information is used to indicate the electronic device in the vehicle of the target model.

It should be understood that the server <NUM> in this embodiment of this application may correspond to the OTA server in the above-mentioned embodiments, and the foregoing and other management operations and/or functions of the modules in the server <NUM> are separately used to implement corresponding steps of the foregoing methods. For brevity, details are not described herein again.

In this embodiment of this application, the transmitting module <NUM> and the receiving module <NUM> may be implemented by a transceiver, and the determining module <NUM> may be implemented by a processor.

As shown in <FIG>, a server <NUM> may include a transceiver <NUM>, a processor <NUM>, and a memory <NUM>. The memory <NUM> may be configured to store code, instructions, and the like executed by the processor <NUM>.

<FIG> is a schematic block diagram of a vehicle <NUM> according to an embodiment of this application. As shown in <FIG>, the vehicle <NUM> includes: a transmitting module <NUM>, a receiving module <NUM> and a determining module <NUM>.

The receiving module <NUM> is configured to receive an update bundle from a server.

The update bundle includes N patches. The N patches are in one-to-one correspondence with N electronic devices. N is a positive integer greater than or equal to <NUM>.

The determining module <NUM> is configured to transmit the N patches to the N electronic devices.

The determining module <NUM> is further configured to receive N pieces of update feedback information.

A piece of update feedback information is used to indicate whether an electronic device which transmits the piece of update feedback information installed a patch corresponding to the electronic device.

The determining module <NUM> is further configured to determine an update response according to the N pieces of update feedback information.

The transmitting module <NUM> is configured to transmit the update response to the server.

Optionally, the receiving module <NUM> is further configured to obtain VVT information from the server, wherein the software information is used to indicate wherein the VVT information is used to indicate at least one piece of a first software information, a piece of the first software information is used to indicate identity information of an electronic device and a current software version numbers of the electronic device; the determining module <NUM> is further configured to store the VVT information.

Optionally, the receiving module <NUM> is further configured to obtain a time stamp corresponding to the VVT information; the determining module <NUM> is further configured to store the time stamp.

Optionally, the identity information of the electronic device includes: a first identity information, a second identity information and a third identity information, wherein the first identity information is used to indicate an identity of a manufacturer of the electronic device, the second identity information is used to indicate an identity of a type of the electronic device, and the third identity information is used to indicate the electronic device.

It should be understood that the vehicle <NUM> in this embodiment of this application may correspond to the target vehicle in the above-mentioned embodiments, and the foregoing and other management operations and/or functions of the modules in the vehicle <NUM> are separately used to implement corresponding steps of the foregoing methods. For brevity, details are not described herein again.

As shown in <FIG>, a vehicle <NUM> may include a transceiver <NUM>, a processor <NUM>, and a memory <NUM>. The memory <NUM> may be configured to store code, instructions, and the like executed by the processor <NUM>.

It should be understood that the processor <NUM> or the processor <NUM> may be an integrated circuit chip and has a signal processing capability. In an implementation process, steps of the foregoing method embodiments may be completed by using a hardware integrated logic circuit in the processor, or by using instructions in a form of software. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor may implement or perform the methods, the steps, and the logical block diagrams that are disclosed in the embodiments of the present invention. The general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to the embodiments of the present invention may be directly performed and completed by a hardware decoding processor, or may be performed and completed by using a combination of hardware in the decoding processor and a software module. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads information in the memory and completes the steps of the foregoing methods in combination with hardware in the processor.

It may be understood that the memory <NUM> or the memory <NUM> in the embodiments of the present invention may be a volatile memory or a nonvolatile memory, or may include both a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM) and is used as an external cache. By way of example rather than limitation, many forms of RAMs may be used, and are, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchronous link dynamic random access memory (Synchronous link DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DR RAM).

It should be noted that the memory in the systems and the methods described in this specification includes but is not limited to these memories and a memory of any other appropriate type.

An embodiment of this application further provides a system chip, where the system chip includes an input/output interface, at least one processor, at least one memory, and a bus. The at least one memory is configured to store instructions, and the at least one processor is configured to invoke the instructions of the at least one memory to perform operations in the methods in the foregoing embodiments.

<FIG> shows a system <NUM> according to an embodiment of this application. The system <NUM> includes: the server <NUM> in the embodiment shown in <FIG>, the vehicle <NUM> in the embodiment shown in <FIG> and a provider server <NUM>.

The provider server <NUM> correspond to the provider in the above-mentioned embodiments, and the foregoing and other management operations and/or functions of the provider server <NUM> are separately used to implement corresponding steps of the foregoing methods. For brevity, details are not described herein again.

An embodiment of this application further provides a computer storage medium, where the computer storage medium may store a program instruction for performing any of the foregoing methods.

Optionally, the storage medium may be specifically the memory <NUM> or the memory <NUM>.

Claim 1:
A method for managing software versions of electronic device(s) in a vehicle (<NUM>), comprising:
transmitting, by a server (<NUM>, <NUM>), an update bundle to a target vehicle, wherein the update bundle comprises N patches, the N patches being in one-to-one correspondence with N electronic devices in the target vehicle, each patch of the N patches being used to update software of a corresponding electronic device, N being a positive integer greater than or equal to <NUM>;
receiving, by the server (<NUM>, <NUM>), an update response from the target vehicle, the update response being used to indicate one or more patches which have been successfully installed among the N patches;
updating, by the server (<NUM>, <NUM>), a vehicle version tree, VVT, corresponding to the target vehicle according to the update response to obtain an updated VVT, wherein the updated VVT comprises multiple pieces of a first software information, a piece of the first software information comprises identity information of an electronic device in the target vehicle and a current software version numbers of the electronic device in the target vehicle, and
determining, by the server (<NUM>, <NUM>), VVT information according to the updated VVT, wherein the VVT information is used to indicate the multiple pieces of the first software information comprised in the updated VVT;
transmitting, by the server (<NUM>, <NUM>), the VVT information to the target vehicle.