Vehicle function updating method, server and vehicle

Abstract

The invention relates to the technical field of intelligent vehicles, and provides a vehicle function updating method, a server and a vehicle, and the method applied to the server comprises the steps: sending a software updating package to a target vehicle end; receiving an update result of the software update package fed back by the target vehicle end, and obtaining current version number information of the vehicle end software of the target vehicle end in response to the update result of successful update; determining a target function item updated by the target vehicle end according to the current version number information and the vehicle information of the target vehicle end; and sending the target function item to a target client paired with the target vehicle end, so that the target client sets corresponding configuration information according to the target function item. According to the scheme, the accuracy, the timeliness and the function updating efficiency when the vehicle function is configured on the client are improved, and the use experience of a user after the new function of the vehicle is updated is also improved.

Description

Technical Field

[0001] The present application relates to the field of smart vehicle technology, and in particular to a vehicle function updating method, a server and a vehicle. Background Art

[0002] With the progress of society and the development of intelligent transportation technology, motor vehicles are becoming more and more popular among users due to their advantages such as high driving freedom. How to improve the user experience of vehicles has become the focus of research by technicians in related fields.

[0003] Currently, users attach great importance to the upgrade and maintenance of vehicle software by manufacturers. There are objective differences in software functions between different models, and there are also subjective differences between different users on whether to upgrade the software, which makes it difficult for manufacturers to upgrade and maintain the software used by different users. Summary of the invention

[0004] In view of this, the purpose of the present application is to propose a vehicle function updating method, a server and a vehicle to solve the problem of poor accuracy and efficiency in configuring vehicle functions on a client.

[0005] Based on the above purpose, the present application provides a vehicle function update method, which is applied to a server and includes:

[0006] Send software update package to target vehicle;

[0007] Receive the update result of the software update package fed back by the target vehicle;

[0008] In response to the update result being that the update is successful, obtaining current version number information of the vehicle-side software of the target vehicle-side;

[0009] Determine the target function item to be updated on the target vehicle side according to the current version number information and the vehicle information on the target vehicle side;

[0010] The target function item is sent to the target client paired with the target vehicle end, so that the target client sets the corresponding configuration information according to the target function item.

[0011] Based on the same purpose as above, the present application also provides a method for updating vehicle functions, which is applied to the vehicle side, including:

[0012] Receive and install software update packages sent by the server;

[0013] The update result of the successful software update package and the current version number information of the vehicle-side software are fed back to the server.

[0014] Corresponding to the above-mentioned vehicle function updating method applied to the server, the embodiment of the present application further provides a vehicle function updating device, which is applied to the server, comprising:

[0015] An update package sending module is used to send a software update package to a target vehicle;

[0016] An update result receiving module, used to receive the update result of the software update package fed back by the target vehicle end;

[0017] A current version acquisition module, configured to acquire current version number information of the vehicle-side software of the target vehicle-side in response to an update result indicating that the update is successful;

[0018] A function item determination module, used to determine a target function item to be updated on the target vehicle side according to the current version number information and the vehicle information of the target vehicle side;

[0019] The function item sending module is used to send the target function item to the target client paired with the target vehicle end, so that the target client sets the corresponding configuration information according to the target function item.

[0020] Corresponding to the above-mentioned vehicle function updating method applied to the vehicle side, the embodiment of the present application further provides a vehicle function updating device, which is applied to the vehicle side, and includes:

[0021] An update package receiving module, used to receive and install the software update package sent by the server;

[0022] The update result feedback module is used to feed back the update result of the successful update of the software update package and the current version number information of the vehicle-side software to the server.

[0023] Based on the same purpose, the present application also provides a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the vehicle function updating method provided in any embodiment of the present application is implemented.

[0024] Based on the same purpose, the present application also provides a vehicle, the vehicle comprising:

[0025] A memory for storing executable program codes;

[0026] A processor is used to call and run the executable program code from the memory so that the vehicle executes the vehicle function updating method provided in any embodiment of the present application.

[0027] As can be seen from the above, in the technical solution of the embodiment of the present application, the server sends a software update package to the target vehicle end and receives the update result of the software update package fed back by the target vehicle end. Based on the update result, it is determined whether it is necessary to configure the function items of the user's client. This enables the server to accurately identify which vehicles' corresponding clients need to be configured with functions, thereby improving the accuracy of synchronization between the server and the client of the vehicle software. In response to the update result being a successful update, the current version number information of the vehicle-side software of the target vehicle end is obtained, and the target function items to be updated by the target vehicle end are determined based on the current version number information and the vehicle information of the target vehicle end. When the vehicle end is updated successfully, the updated version information of the vehicle end is obtained. These version information helps the server determine the function items that need to be configured on the client side for the new function, so as to improve the accuracy of the client synchronizing these function items. The target function items are sent to the target client paired with the target vehicle, so that the target client sets the corresponding configuration information according to the target function items, and the accurate target function items corresponding to the new functions of the target vehicle are synchronized to the accurate target client paired with the target vehicle, so that users who have successfully upgraded the vehicle can use the corresponding function options of the client in time, thereby improving the accuracy, timeliness and function update efficiency of vehicle function configuration on the client, and also improving the user experience after updating the new vehicle functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0029] Figure 1 A flowchart of a method for updating vehicle functions provided in an embodiment of the present application;

[0030] Figure 2 A schematic flow chart of another method for updating vehicle functions provided in an embodiment of the present application;

[0031] Figure 3 A schematic diagram of the interaction between the cloud and the vehicle during a software update process provided in an embodiment of the present application;

[0032] Figure 4 A schematic diagram of the structure of a vehicle function updating device provided in an embodiment of the present application;

[0033] Figure 5 A schematic diagram of the structure of another vehicle function updating device provided in an embodiment of the present application;

[0034] Figure 6A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0036] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0037] Before describing the various embodiments and implementation methods of the present application, some basic situations are introduced first. At present, after the vehicle is upgraded by OTA (Over The Air, air update / remote update), if a new remote control function is released, the application corresponding to the mobile terminal used by the user needs to support the user to use the new function, such as the appearance of the function options corresponding to the new function. Since the initiative of upgrading the vehicle software is controlled by the user, there are many users who do not upgrade the new function, then the unupgraded vehicles do not have new functions, and the corresponding applications in the mobile terminals of these users do not support the implementation of the new function, such as the appearance of the function options corresponding to the new function. At present, the management method of the manufacturer is that the technicians export the vehicle information of the upgraded new function in the management system every night, and then adjust the function permissions and configuration files in the application for the users of these vehicles. The process of technicians' adjustment is prone to errors, and it is not possible to let users enjoy the new function at the fastest speed, resulting in poor accuracy and timeliness when the new function is updated, which makes the efficiency of the whole process from the issuance of the new function to the user's enjoyment poor. In this regard, various embodiments and implementation methods of the present application are proposed to overcome the above problems.

[0038] Figure 1A vehicle function update method provided in an embodiment of the present application can be applied to a situation where a vehicle and a corresponding client remotely upgrade software through a cloud server, and the method can be applied to a server. The vehicle function update method provided in an embodiment of the present application can be executed by a vehicle function update device, which can be integrated in an electronic device by means of hardware and / or software, and the electronic device can be set in a server. Figure 1 , the method provided in the embodiment of the present application comprises the following steps:

[0039] S110: Send a software update package to the target vehicle.

[0040] The target vehicle can be any vehicle used by the user, and the software update package can be a data installation package for updating the software in the vehicle (such as the vehicle system), and the software update package can include an installation program, an executable file, registration information, and resource files, etc. It is understandable that when the software on the vehicle needs to be updated, such as upgrading a new version of the software or installing an old version of the software, the software update package is developed and debugged in advance by relevant technical personnel and pre-configured in the cloud server, and the software update package is sent to the vehicle when an update is required.

[0041] S120: receiving the update result of the software update package fed back by the target vehicle.

[0042] When the vehicle receives the software update package sent by the server, the software update package is installed, and the result of the success or failure of the installation can be the update result, including update success and update failure. The update result of the software update package is fed back to the server, and the server can directly receive the update result.

[0043] S130. In response to the update result being a successful update, obtain the current version number information of the vehicle-side software of the target vehicle-side.

[0044] Among them, the current version number information can be the version information of all files of the current vehicle-side software, for example, it can include the software version number, the matrix version number of the vehicle CAN communication, etc. It can be understood that different configuration files or resource files have different version numbers, and their file contents generally differ.

[0045] If the software update package on the vehicle side is successfully installed, the server can obtain the current version number information of the vehicle side software after the successful installation. On the contrary, if the software update package on the vehicle side fails to be installed, no subsequent operations are required, but the software update package can be obtained again to try to update.

[0046] S140: Determine the target function item to be updated on the target vehicle side according to the current version number information and the vehicle information of the target vehicle side.

[0047] The target function item may be configuration information that matches the vehicle-side function in the client used by the user (e.g., an application in a mobile terminal). It should be noted that after the vehicle-side installs the software update package, new functions may be given to the vehicle. In order for the user to start or link these new functions through the client, the client also needs to set the configuration information corresponding to these new functions, so as to ensure that the client and the vehicle-side can normally enable these functions.

[0048] The vehicle information may be the identity information of the vehicle corresponding to the target vehicle, for example, the vehicle model and vehicle identification number of the target vehicle. It is understandable that different vehicle models generally have different hardware, and the corresponding functions that can be achieved using these hardware are not exactly the same. Even different models of the same vehicle have hardware and functional differences due to different options selected by users during the purchase stage. It can be seen that obtaining vehicle information to determine the specific identity of the vehicle has positive significance for upgrading and maintaining vehicle functions.

[0049] Corresponding to the vehicle information, the client used by the user has been pre-paired (or bound) with the vehicle. The acquisition of vehicle information can help determine the identity of the client used by the user, that is, which client corresponding to the target vehicle needs to set the configuration information corresponding to the new function. The current version number information can help confirm which new functions have been updated in the vehicle. Through these two pieces of information, the user's client and the corresponding target function items that need to be set can be confirmed respectively.

[0050] S150: Send the target function item to the target client paired with the target vehicle end, so that the target client sets the corresponding configuration information according to the target function item.

[0051] The target client can be a client used by a user who has paired with the target vehicle, and the target client can respond to or link with the functions of the target vehicle. The cloud server sends the target function items determined in the above steps to the user's client, so that the user can install and set them accordingly according to the configuration information carried in these target function items, so that the linkage function between the target client and the target vehicle can operate normally.

[0052] In a specific example, when a vehicle is sold from the factory, the hardware is often assembled, but the relevant software functions have not been fully developed, so users expect the manufacturer to upgrade the functions after purchasing the vehicle. After the relevant technicians develop new functions to adapt to the vehicle hardware, they package the relevant installation files of the new functions to form a software update package, which is sent to each vehicle through the cloud server. Users can get prompts for function updates through the car computer and choose whether to update according to personal needs. If the user chooses to update, the car side downloads and installs the software update package, and feeds back the message of successful installation and update of the software update package to the cloud server. The cloud confirms that the user's vehicle has installed new functions. In order to enable the user's mobile application to interact with the car computer and implement remote operation functions (such as remote control, remote air conditioning, etc.), the cloud can actively send the function items corresponding to these new functions to the user's mobile application, so that it can synchronize functions with the car side without the need for users to update them themselves. Then, after the cloud confirms that the user's vehicle has installed a new function, it is necessary to obtain the current version number information and vehicle information of the user's vehicle software.

[0053] It should be noted that since users have the option to update the vehicle-side software, different users have different situations in which their vehicles update software, so the manufacturer's maintenance of user mobile applications will be correspondingly different. If all users' mobile applications are provided with functional items corresponding to new functions in a one-size-fits-all manner, it will easily lead to user usage problems, and then lead to customer complaints. In this case, it is critical for the cloud to identify which mobile applications need to be configured with functional items. The current version number information can determine what new functions are installed in the vehicle. Since the functional items (configuration information) corresponding to these new functions are pre-stored in the cloud server, once the vehicle's identity information is determined, the vehicle can be accurately matched to the user's target client, and these functional items can be issued to the user's target client. This will prevent the situation where the software version on the user's vehicle does not correspond to the functional items in the user's mobile application.

[0054] In the technical solution of the embodiment of the present application, the server sends a software update package to the target vehicle end and receives the update result of the software update package fed back by the target vehicle end. Based on the update result, it is determined whether it is necessary to configure the function items of the user's client, which enables the server to accurately identify which vehicles' corresponding clients need to perform function configuration, thereby improving the accuracy of the server's synchronization between the vehicle software and the client. In response to the update result being a successful update, the current version number information of the vehicle-side software of the target vehicle end is obtained, and the target function items to be updated by the target vehicle end are determined based on the current version number information and the vehicle information of the target vehicle end. When the vehicle end is successfully updated, the updated version information of the vehicle end is obtained. These version information helps the server determine the function items that need to be configured on the client side for the new function, so as to improve the accuracy of the client synchronizing these function items. The target function items are sent to the target client paired with the target vehicle, so that the target client sets the corresponding configuration information according to the target function items, and the accurate target function items corresponding to the new functions of the target vehicle are synchronized to the accurate target client paired with the target vehicle, so that users who have successfully upgraded the vehicle can use the corresponding function options of the client in time, thereby improving the accuracy, timeliness and function update efficiency of vehicle function configuration on the client, and also improving the user experience after updating the new vehicle functions.

[0055] In an optional implementation, the current version number information includes a software version number; the vehicle information includes a vehicle identification code;

[0056] Determining the target function items to be updated for each target vehicle terminal according to the current version number information and the vehicle information of the target vehicle terminal in S140 may include:

[0057] S141, determining the target client corresponding to each vehicle identification code.

[0058] The vehicle identification number (VIN) can be the unique identification information of the vehicle, and each vehicle is marked with a unique vehicle identification number. It is understandable that after purchasing a vehicle, the user pairs the mobile terminal (such as a mobile phone, tablet computer, etc.) used by the user with the vehicle so as to control and use the vehicle functions through the client on the mobile terminal. Therefore, the server can confirm the user client paired with the vehicle, that is, the target client, based on the vehicle identification code.

[0059] S142. Obtain a target feature value carried by the software version number; the target feature value is at least one of the feature values.

[0060] Among them, the software version number can be the version information of the software program installed in the software update package downloaded by the vehicle. The characteristic value can be the code or code of each function in the vehicle, and can be in the form of a combination of letters and / or numbers. Correspondingly, the target characteristic value can be the characteristic value corresponding to the new function installed by this software update package. If the software update package upgrades the vehicle side with a new function, it will definitely carry the target characteristic value corresponding to the new function. It should be noted that the characteristic values ​​corresponding to all developed functions are pre-stored in the cloud server, and the target characteristic values ​​corresponding to the new functions installed by this software update package can be found in the characteristic values ​​stored in the server.

[0061] S143: Filter at least one target functional node corresponding to the target feature value in the association relationship between the pre-configured feature value and the functional node of the target client.

[0062] Among them, the function node can be a file or program in the client that needs to be configured accordingly to the corresponding vehicle function. It is understandable that each vehicle function has a corresponding configuration file or program, and the correspondence between the vehicle function and these configuration files and data can be reflected by the association between the characteristic value of the vehicle function and the functional node of the client. After developing the configuration files or programs of the vehicle function and the client, the relevant staff will pre-store the association between them in the server in the cloud. Therefore, based on the target characteristic value determined in the aforementioned steps, multiple corresponding target function nodes are screened out in the association relationship. It should be noted that a vehicle function may correspond to multiple configuration files or programs in the client, that is, the target characteristic value can correspond to multiple target function nodes.

[0063] S144. Each target function node is used as a target function item.

[0064] These target function nodes are used as target function items that need to be configured on the client.

[0065] In the above implementation, the target client is determined by the vehicle identification code, which helps to accurately find the function items that the target client needs to configure according to the target feature value. Then, based on the target feature value carried by the software version number when the vehicle-side software is updated, multiple target function nodes corresponding to the target feature value are screened out from the association relationship between the feature value pre-configured in the server and the function node of the target client as the target function item, which is used to set the client corresponding to the new function. In this way, the files or programs that the user's client needs to configure can be accurately screened out, which helps to improve the accuracy and efficiency of the vehicle software when the client is updated.

[0066] In the above embodiments, after the user chooses to update the vehicle software, the server will synchronize the function items that need to be configured in the new version of the software on the user's client, so that the user can control and use the new functions of the vehicle software through the client, ensuring the user's experience after the software is updated. Similarly, not only does the client need to be configured accordingly, but the vehicle also needs to synchronize the original software or communication method of the vehicle to adapt to the addition of new functions.

[0067] In another optional implementation, the version number information includes a communication matrix version number; the vehicle information includes vehicle model information; and the method may further include:

[0068] A1. Determine the historical communication matrix and historical communication matrix version number of the target vehicle according to the vehicle model information.

[0069] The communication matrix may be a set of rules for sending signals between all electronic control units in the vehicle, such as a CAN (Controller Area Network) communication matrix. The communication matrix may include the position and signal length of signals sent between the electronic control units, such as sending a signal from bit0 to bit1.

[0070] Then, the historical communication matrix can be the communication matrix used before the software update package is installed on the vehicle side. Since different vehicle computer versions may correspond to different signal sending rules, the communication matrix version number is used to distinguish different sets of signal sending rules. Then, the historical communication matrix version number can be the version information of the communication matrix used before the software update package is installed on the vehicle side.

[0071] Since the vehicle and the server can communicate in real time, the server can directly obtain the vehicle model information of the target vehicle. It should be noted that the same vehicle model usually uses the same communication matrix. Therefore, according to the vehicle model, the communication matrix used by the target vehicle before the software update package is installed is found, and the version number of this communication matrix is ​​determined, that is, the historical communication matrix and the historical communication matrix version number are obtained.

[0072] A2. In response to the current communication matrix version number being different from the historical communication matrix version number, a target acquisition scheme is determined according to the correspondence between the historical communication matrix and the historical signal acquisition scheme.

[0073] The current communication matrix version number may be the version information of the new communication matrix carried in the software update package. It is understandable that when the vehicle software is updated, the new communication matrix carried in the software update package may also be updated to the vehicle side to adapt to the implementation of the new function. However, there is also a situation in reality where the new function is updated but the communication matrix is ​​not changed.

[0074] Therefore, first check the current communication matrix version number and the historical communication matrix version number. If the current communication matrix version number and the historical communication matrix version number are the same, it means that the signal transmission rules between the electronic controllers in the target vehicle have not changed, and no other processing is required. If the current communication matrix version number and the historical communication matrix version number are different, it means that the signal transmission rules between the electronic controllers in the target vehicle have changed. It should be noted that after developing new functions, the relevant technicians will readjust the communication matrix according to the use of the new functions, and attach the new communication matrix to the software update package and send it to the vehicle.

[0075] The collection scheme can be the rule for the vehicle to upload the signals generated by its own electronic controllers to the server. Since the electronic controllers themselves send and receive signals according to the communication matrix, and the cloud does not need all the signals in the communication matrix to collect vehicle signals, the collection scheme is a subset of the communication matrix. It can be understood that even for the same vehicle model, the collection scheme is different in the case of different communication matrices. Then, the historical collection scheme can be the collection scheme corresponding to the historical communication matrix used before the vehicle installed the software update package, and the target collection scheme can be the collection scheme corresponding to the current communication matrix. In other words, after the software update package is installed, the rules for sending and receiving signals between the various electronic control units inside the vehicle have changed, and the corresponding rules for uploading signals to the cloud have also changed.

[0076] Since the acquisition plan is a subset of the communication matrix, there is a corresponding relationship between the historical communication matrix and the historical acquisition plan. Similarly, there is a corresponding relationship between the current communication matrix and the target acquisition plan. The same vehicle model has the same signal acquisition situation, so the two corresponding relationships mentioned above are the same. Therefore, according to the corresponding relationship between the historical communication matrix and the historical acquisition plan, the target acquisition plan corresponding to the current communication matrix is ​​obtained.

[0077] A3. Send the target acquisition plan to the target vehicle end, so that the target vehicle end sets the target sending position and target signal length when uploading the vehicle end signal according to the target acquisition plan.

[0078] As mentioned above, the communication matrix may include the position and signal length of signals sent between each electronic control unit, and the acquisition plan is a subset of the communication matrix, which means that the content of the acquisition plan is actually the sending position and signal length of each signal. Therefore, the server sends the target acquisition plan to the target vehicle end, and the target vehicle end can determine the target acquisition plan in the above steps and set the target sending position and target signal length of the corresponding vehicle end signal in the plan.

[0079] In the above implementation, due to the subset relationship between the communication matrix and the acquisition scheme, the corresponding relationship between the historical communication matrix and the historical acquisition scheme, that is, the corresponding relationship between the current communication matrix and the target acquisition scheme, the target acquisition scheme is determined according to the current communication matrix. The target acquisition scheme is directly determined by the corresponding relationship between the historical communication matrix and the historical acquisition scheme that already exists in the server, which improves the efficiency of determining the target acquisition scheme, and also helps to improve the timeliness of the adaptation of the vehicle end to signal acquisition after the new function is updated, and improves the user experience of the vehicle after the function is upgraded.

[0080] In a further optional implementation manner, determining the target acquisition scheme according to the correspondence between the historical communication matrix and the historical signal acquisition scheme in A2 may include:

[0081] A21. According to the correspondence between the historical communication matrix and the historical signal collection scheme, determine the historical sending position and historical signal length of the vehicle-side signal upload, and the signal transmission rules between the historical communication matrix.

[0082] It can be understood that the historical communication matrix includes the sending rules of all vehicle-side signals (including sending position and signal length) before the new function is installed on the vehicle-side. The historical signal acquisition scheme is a subset of the historical communication matrix. The correspondence between the two is actually the transmission rules of some signals selected by the historical signal acquisition scheme from the historical communication matrix, that is, the above-mentioned signal transmission rules. These signal transmission rules correspond to the historical sending positions and historical signal lengths of vehicle-side signals in the historical communication matrix.

[0083] A22. According to the signal transmission rules, determine the target sending position and target signal length corresponding to the current communication matrix.

[0084] The signal transmission rules show which specific signals the server has collected from the vehicle, and based on these specific signals, find their corresponding sending positions and signal lengths in the current communication matrix, that is, determine the target sending position and target signal length.

[0085] A23. Use the target sending position and target signal length as the target acquisition plan.

[0086] The target sending position and target signal length determined in the above steps are used as a collection scheme for the vehicle-side signal uploaded to the server by the vehicle-side after the software update package is installed.

[0087] In the above implementation, by determining the historical sending position and the historical signal length, and the signal transmission rules between the historical communication matrix, the new signal acquisition scheme of the vehicle after installing the software update package is further determined, which can help the server to synchronize the target acquisition scheme to the vehicle in a timely manner, thereby ensuring communication and normal interaction between the vehicle and the server.

[0088] In a further optional implementation, in A21, according to the correspondence between the historical communication matrix and the historical signal acquisition scheme, the historical sending position and the historical signal length of the vehicle-side signal upload are determined, and the signal transmission rules between the historical communication matrix and the historical communication matrix may include:

[0089] A211. According to the correspondence between the historical communication matrix and the historical signal acquisition scheme, different signal flags when uploading signals from different vehicle ends are determined respectively; each signal flag is associated with a signal sending position and a signal length of at least one bit.

[0090] The signal flag may be a mark for a certain collected signal.

[0091] A212. The association between each signal flag bit and the signal sending position and signal length is used as a signal transmission rule.

[0092] The combination of the historical sending position and the historical signal length represents the collection method of a certain vehicle-side signal before the software update package is installed, and this collection method has a corresponding signal mark (that is, signal flag bit) in the historical communication matrix. For example, the air-conditioning signal of the vehicle is collected (the signal flag bits of different vehicle-side signals are different, and the air-conditioning signal is taken as an example here). In the historical communication matrix, the historical sending position corresponding to the air-conditioning signal is bit 5 (that is, one signal flag bit is associated with one signal sending position), and the historical signal length is bit 5 to bit 6 (that is, one signal flag bit is associated with at least one bit of signal length). The corresponding rules of recording the signal flag bits of the air-conditioning signal in the historical communication matrix are used as signal transmission rules.

[0093] Continuing with the previous example, after the software update package is installed, the air conditioning signal still needs to be collected in the current communication matrix, and the sending position of the air conditioning signal in the current matrix is ​​bit 6, and the signal length is bit 6 to bit 8. The transmission rules of the air conditioning signal will not change because the relevant technicians change the sending position and signal length. The signal flag bit of the air conditioning signal is still called to correspond to bit 6, which is the target sending position, and the length of bit 6 to bit 8 is the target signal length.

[0094] Correspondingly, in A22, according to the signal transmission rule, determining the target transmission position and the target signal length corresponding to the current communication matrix may include:

[0095] A221. Use the signal sending position corresponding to the signal flag bit in the current communication matrix as the target sending position.

[0096] A222. Use the signal length corresponding to the signal flag bit in the current communication matrix as the target signal length.

[0097] According to the signal flag determined in the previous steps, the corresponding signal sending position and signal length are determined in the current communication matrix as the target sending position and target signal length, respectively, thereby helping the server determine the target acquisition plan after installing the software update package.

[0098] It should be noted that there is no difference in the order of execution between A221 and A222. The steps here are only used to illustrate the solution and cannot be understood as a limitation on the execution order.

[0099] In the above implementation, the signal flags of different vehicle-end signals collected are determined through the correspondence between the historical communication matrix and the historical signal collection scheme, and the collection methods of these different vehicle-end signals are determined from the current communication matrix based on the signal flags. This enables the server to automatically convert the old version of the signal collection scheme into the new version of the signal collection scheme, and based on the signal flags, the accuracy of the position and length of the signal collection during the conversion process can be guaranteed, thereby helping to ensure the stability and accuracy of the vehicle-end signals uploaded to the server.

[0100] Figure 2 A vehicle function update method provided in an embodiment of the present application can be applied to a situation where a vehicle remotely upgrades its software through a cloud server. The vehicle function update method provided in an embodiment of the present application can be executed by a vehicle function update device. The vehicle function update device can be integrated in an electronic device by means of hardware and / or software. The electronic device can be set in a vehicle. Figure 2 , the method provided in the embodiment of the present application comprises the following steps:

[0101] S210: Receive and install the software update package sent by the server.

[0102] Among them, the software update package can be a data installation package for updating the software in the vehicle (such as the vehicle system), and the software update package can include an installation program, an executable file, registration information, and resource files. It is understandable that when the software on the vehicle side needs to be updated, such as upgrading a new version of the software or installing an old version of the software, the software update package is developed and debugged in advance by relevant technical personnel and pre-configured in the cloud server. When an update is required, the software update package is sent to the vehicle side. The vehicle side receives and installs the software update package sent by the server.

[0103] S220: Feedback the update result of the successful update of the software update package and the current version number information of the vehicle-side software to the server.

[0104] Among them, the current version number information can be the version information of all files of the current vehicle-side software, for example, it can include the software version number, the matrix version number of the vehicle CAN communication, etc. It can be understood that different configuration files or resource files have different version numbers, and their file contents generally differ.

[0105] Specifically, when the vehicle receives the software update package sent by the server, it installs the software update package. The result of the installation success or failure can be the update result, including update success and update failure. The update result of the software update package is fed back to the server, and the server can directly receive the update result. At the same time, the current version number information of the vehicle software after the update is synchronized to the server.

[0106] In the technical solution of the embodiment of the present application, as a party on the vehicle side, the software update package sent by the server is received and installed, and the update result of the successful update of the software update package and the current version number information of the vehicle-side software are fed back to the server, so that the server can subsequently synchronize the configuration of functional items of the user's client according to the successful update result and the current version number information, helping the server to promptly determine whether the user's client needs to be configured, helping to improve the synchronization between the vehicle side and the client when the vehicle software is updated, improve the efficiency of the vehicle software update, and enhance the user experience of the vehicle side and the client after the software update.

[0107] In an optional implementation, the current version number information includes the current communication matrix version number; in S220, the update result of the successful update of the software update package and the current version number information of the vehicle-side software are fed back to the server, which may include:

[0108] S221. Feedback the update result of the successful software update package and the current communication matrix version number of the vehicle-side software to the server, so that the server can determine the target acquisition plan according to the vehicle model information and the current communication matrix version number of the vehicle-side; the target acquisition plan includes the target sending position and target signal length of the vehicle-side signal.

[0109] On the server side, the target acquisition scheme is determined according to the vehicle model information and the current communication matrix version number, and the target sending position and target signal length when collecting the vehicle-side signal are determined. The contents have been explained in detail in the previous embodiments and will not be repeated here.

[0110] S222. Receive the target acquisition plan sent by the server, and collect and upload the vehicle-side signal based on the target sending position and target signal length.

[0111] After determining the target acquisition plan, the server sends it to the vehicle side. The vehicle side receives the target acquisition plan, collects the vehicle side signals of each electronic control unit inside the vehicle according to the target sending position and target signal length in the target acquisition plan, and then uploads it to the server to complete the signal acquisition process.

[0112] In the above implementation, the vehicle side receives the target acquisition plan sent by the server, and collects and uploads the vehicle side signal according to the signal acquisition method in the target acquisition plan. It can update the vehicle side's acquisition plan and adapt to new functions after installation in a timely manner, thereby ensuring the normal operation of the functions and the correct communication between the vehicle side and the cloud server.

[0113] In another optional implementation, the method may further include:

[0114] B1. Receive the software backtracking instruction sent by the server.

[0115] Among them, the software rollback instruction can be an instruction sent by the cloud server to the vehicle side to roll back the vehicle software to an old version.

[0116] B2. According to the software backtracking instruction, call and download the installation version backtracking package from the server.

[0117] The version backtracking package may be an installation package of an old version of the vehicle software. When the vehicle side receives the software backtracking instruction sent by the server, it calls the version backtracking package from the server, downloads the version backtracking package and installs it on the vehicle side.

[0118] B3. Collect and upload vehicle-side signals according to the signal collection plan of the historical version corresponding to the version backtracking package.

[0119] It is understandable that in actual situations, there are situations where the new version of the vehicle software has many problems that are difficult to fix. The vehicle can reinstall the previous stable version through version backtracking, so the corresponding signal collection plan must also be backtracked. Different old versions of vehicle software also correspond to different vehicle-side signal collection plans. According to the software version number in the version backtracking package, query the server for the signal collection plan of the historical version corresponding to the software version number. According to the collection method specified in the signal collection plan of the historical version, the vehicle-side signal is collected and uploaded to the cloud server.

[0120] In the above implementation, by downloading and installing the version backtracking package and adjusting the signal acquisition scheme to return to the historical version, problems with the new version of the vehicle software can be avoided in a timely manner, and the vehicle-side software can be temporarily run with a stable version, ensuring the normal use of the vehicle and normal communication between the vehicle-side and the cloud server.

[0121] On the basis of the above two embodiments, the embodiment of the present application further provides a specific preferred embodiment, which illustrates an example of the present application scheme from the interaction between the cloud server end and the vehicle end, such as Figure 3 As shown, the details are as follows:

[0122] Process ①: The OTA (Over The Air, air upgrade / remote upgrade) integrated management platform pre-records the communication matrix of the CAN bus communication of each vehicle model in the cloud server, and each communication matrix corresponds to a matrix version number; the signal acquisition plan of each vehicle model and vehicle is pre-recorded. The signal acquisition plan of each vehicle model can be changed according to the actual situation, including increasing the acquisition signal, reducing the acquisition signal, changing the acquisition frequency, changing the upload frequency, etc. It should be noted that the signal acquisition plan is a subset of the communication matrix. Different signal combinations uploaded in the same communication matrix correspond to different signal acquisition plans. Therefore, one communication matrix can correspond to multiple signal acquisition plans. In addition, the vehicle data acquisition configuration system can synchronize the correspondence between the vehicle model and the matrix version number to the OTA integrated management platform.

[0123] Process ②: The APP (application) permission configuration system manages the total set of permission nodes corresponding to all exposed items on the client, as well as the customized permission configuration for each vehicle. The OTA integrated management platform uses the feature value marking function. For example, the feature value of the smart parking function is SAP. The APP permission configuration system is responsible for matching the feature values ​​of new functions synchronized from the OTA integrated management platform with permission nodes. The permission nodes correspond to configuration files and programs for subsequent configuration on the user's client. For example, if the smart parking function is exposed on the client as a remote control button and a parking status display, two new permission nodes are created and attributed to the feature value SAP.

[0124] Process ③: For each software update package stored in the OTA server, it is necessary to ensure that the software version number, the matrix version number corresponding to the software implementation, and the characteristic value of the new function corresponding to the software version number are correct.

[0125] Process ④: The server in the cloud sends the software update package to the vehicle side (sent to the OTA master ECU on the vehicle side through the OTA server in the cloud), the vehicle side downloads the software update package and installs it. As for how the OTA master ECU installs the update program to each ECU (Electronic Control Unit) under the vehicle side, this embodiment of the application does not elaborate.

[0126] Process ⑤: The vehicle side feeds back the installation result of the software update package to the cloud.

[0127] Process ⑥: If the installation is successful, the OTA integrated management platform will determine that if the upgraded version number has a matching target feature value of the new function, the result of the successful installation will be notified to the APP permission configuration center (i.e. process ⑦), and the target feature value of the new function of this upgrade will be synchronized. The APP permission configuration center enables the permission node corresponding to the target feature value according to the VIN (i.e. vehicle identification number), updates the vehicle's permission configuration on the client, and installs the configuration file and level corresponding to the new function into the user's client, so that the interactive button of the new function is exposed on the client's interactive interface to support user use. If this upgrade does not involve the feature value of the new function, it is considered that no new vehicle function has been installed, and no processing is required.

[0128] Process ⑧: The OTA integrated management platform determines that if the matrix version number changes after the upgrade, the vehicle data acquisition configuration system will be informed of the successful installation result, and the current communication matrix version number of this upgrade will be synchronized. The vehicle data acquisition configuration system generates a new acquisition plan according to the current communication matrix and sends it to the vehicle (i.e. process ⑨). The vehicle collects vehicle signals according to the new acquisition plan and uploads the collected vehicle signals to the cloud.

[0129] In the above specific examples, the matrix version number, function characteristic value, and software version number are used to achieve multi-terminal information synchronization, which improves the efficiency and accuracy of OTA operations. Originally, it was necessary to manually confirm offline whether the OTA upgrade would change the communication matrix, and then analyze whether the vehicle's data collection plan needed to be updated. This solution can realize automatic monitoring of OTA upgrade results and automatically update the signal collection plan. Originally, it was necessary to regularly count the users who successfully upgraded OTA every night, update the functional permission configuration of the client for them, and support users to use new functions. This solution can enable users to use new functions after the OTA upgrade is completed, saving labor costs and improving the user experience.

[0130] It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0131] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a vehicle function updating device that can be applied to a server. Figure 4 A schematic diagram of a vehicle function updating device provided in an embodiment of the present application, referring to Figure 4 The vehicle function updating device includes an update package sending module 410, an update result receiving module 420, a current version obtaining module 430, a function item determining module 440 and a function item sending module 450, wherein:

[0132] An update package sending module 410 is used to send a software update package to a target vehicle end;

[0133] An update result receiving module 420 is used to receive the update result of the software update package fed back by the target vehicle end;

[0134] The current version acquisition module 430 is used to acquire the current version number information of the vehicle-side software of the target vehicle-side in response to the update result being that the update is successful;

[0135] The function item determination module 440 is used to determine the target function item to be updated on the target vehicle side according to the current version number information and the vehicle information of the target vehicle side;

[0136] The function item sending module 450 is used to send the target function item to the target client paired with the target vehicle end, so that the target client sets the corresponding configuration information according to the target function item.

[0137] In the technical solution of the embodiment of the present application, the server sends a software update package to the target vehicle end and receives the update result of the software update package fed back by the target vehicle end. Based on the update result, it is determined whether it is necessary to configure the function items of the user's client, which enables the server to accurately identify which vehicles' corresponding clients need to perform function configuration, thereby improving the accuracy of the server's synchronization between the vehicle software and the client. In response to the update result being a successful update, the current version number information of the vehicle-side software of the target vehicle end is obtained, and the target function items to be updated by the target vehicle end are determined based on the current version number information and the vehicle information of the target vehicle end. When the vehicle end is successfully updated, the updated version information of the vehicle end is obtained. These version information helps the server determine the function items that need to be configured on the client side for the new function, so as to improve the accuracy of the client synchronizing these function items. The target function items are sent to the target client paired with the target vehicle, so that the target client sets the corresponding configuration information according to the target function items, and the accurate target function items corresponding to the new functions of the target vehicle are synchronized to the accurate target client paired with the target vehicle, so that users who have successfully upgraded the vehicle can use the corresponding function options of the client in time, thereby improving the accuracy, timeliness and function update efficiency of vehicle function configuration on the client, and also improving the user experience after updating the new vehicle functions.

[0138] In an optional implementation, the current version number information includes a software version number; the vehicle information includes a vehicle identification code;

[0139] The function item determination module 440 may include:

[0140] A target client determination unit, used to determine the target client corresponding to each vehicle identification code;

[0141] A target characteristic value acquisition unit is used to acquire a target characteristic value carried by the software version number; the target characteristic value is at least one of the characteristic values;

[0142] A target function node screening unit, configured to screen at least one target function node corresponding to a target feature value in the association relationship between the pre-configured feature value and the function node of the target client;

[0143] The target function item determination unit is used to take each target function node as a target function item.

[0144] In another optional implementation, the version number information includes a communication matrix version number; the vehicle information includes vehicle model information; and the device may further include:

[0145] A historical communication matrix determination unit, used to determine the historical communication matrix and the historical communication matrix version number of the target vehicle according to the vehicle model information;

[0146] A target acquisition scheme determining unit, configured to determine a target acquisition scheme in response to a current communication matrix version number being different from a historical communication matrix version number, according to a correspondence between a historical communication matrix and a historical signal acquisition scheme;

[0147] The target acquisition plan sending unit is used to send the target acquisition plan to the target vehicle end, so that the target vehicle end sets the target sending position and target signal length when uploading the vehicle end signal according to the target acquisition plan.

[0148] In a further optional implementation, the target acquisition scheme determination unit may include:

[0149] A signal transmission rule determination unit, used to determine the historical sending position and historical signal length of the vehicle-side signal upload, and the signal transmission rule between the historical communication matrix and the historical signal collection scheme according to the corresponding relationship between the historical communication matrix and the historical signal collection scheme;

[0150] A signal position and length determination unit, used to determine a target sending position and a target signal length corresponding to the current communication matrix according to a signal transmission rule;

[0151] The acquisition scheme determining unit is used to use the target sending position and the target signal length as the target acquisition scheme.

[0152] In a further optional implementation, the signal transmission rule determination unit may include:

[0153] The flag bit determination subunit is used to determine different signal flag bits when uploading different vehicle-side signals according to the corresponding relationship between the historical communication matrix and the historical signal acquisition scheme; each signal flag bit is associated with a signal sending position and a signal length of at least one bit;

[0154] The transmission rule determination subunit is used to associate the relationship between each signal flag bit and the signal transmission position and the signal length as a signal transmission rule;

[0155] Accordingly, the signal position and length determination unit may include:

[0156] The target sending position determination subunit is used to use the signal sending position corresponding to the signal flag bit in the current communication matrix as the target sending position;

[0157] The target signal length determination subunit is used to take the signal length corresponding to the signal flag bit in the current communication matrix as the target signal length.

[0158] For the convenience of description, the above device is described in terms of functions divided into various modules. Of course, when implementing the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0159] The device of the above-mentioned embodiment is used to implement the corresponding vehicle function updating method in the above-mentioned vehicle-side corresponding embodiment, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0160] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a vehicle function updating device that can be applied to the vehicle side. Figure 5 A schematic diagram of a vehicle function updating device provided in an embodiment of the present application, referring to Figure 5 The vehicle function updating device includes an update package receiving module 510 and an update result feedback module 520, wherein:

[0161] The update package receiving module 510 is used to receive and install the software update package sent by the server;

[0162] The update result feedback module 520 is used to feed back the update result of the successful update of the software update package and the current version number information of the vehicle-side software to the server.

[0163] In the technical solution of the embodiment of the present application, as a party on the vehicle side, the software update package sent by the server is received and installed, and the update result of the successful update of the software update package and the current version number information of the vehicle side software are fed back to the server, so that the server can subsequently synchronize the function items of the user's client according to the successful update result and the current version number information, helping the server to promptly determine whether the user's client needs to be configured, which helps to improve the synchronization between the vehicle side and the client when the vehicle software is updated, improve the efficiency of the vehicle software update, and enhance the user's experience when using the vehicle side and the client after the software update. In an optional implementation, the current version number information includes the current communication matrix version number; the update result feedback module 520 may include:

[0164] An update result feedback unit is used to feed back the update result of the successful update of the software update package and the current communication matrix version number of the vehicle-side software to the server, so that the server can determine the target acquisition plan according to the vehicle model information and the current communication matrix version number of the vehicle-side; the target acquisition plan includes the target sending position and target signal length of the vehicle-side signal;

[0165] The acquisition scheme application unit is used to receive the target acquisition scheme sent by the server, and to collect and upload the vehicle-side signal based on the target sending position and target signal length.

[0166] In another optional embodiment, the device may further include:

[0167] A backtracking instruction receiving unit, used for receiving a software backtracking instruction sent by a server;

[0168] The backtracking package installation unit is used to call and download the installation version backtracking package from the server according to the software backtracking instruction;

[0169] The historical collection scheme application unit is used to collect and upload vehicle-side signals according to the signal collection scheme of the historical version corresponding to the version backtracking package.

[0170] The device of the above-mentioned embodiment is used to implement the corresponding vehicle function updating method in the above-mentioned embodiment applied to the vehicle side, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0171] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the vehicle function updating method described in any of the above embodiments is implemented.

[0172] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, Figure 6 A specific electronic device hardware structure is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0173] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0174] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0175] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0176] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0177] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0178] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0179] The electronic device of the above embodiment is used to implement the updating method of the corresponding vehicle function in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0180] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application further provides a server, the server comprising:

[0181] A memory for storing executable program codes;

[0182] A processor is used to call and run the executable program code from the memory, so that the vehicle executes the vehicle function updating method provided by the embodiment corresponding to the server of this application.

[0183] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application further provides a vehicle, the vehicle comprising:

[0184] A memory for storing executable program codes;

[0185] The processor is used to call and run the executable program code from the memory so that the vehicle executes the vehicle function updating method provided by the embodiment corresponding to the vehicle side of the present application.

[0186] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the vehicle function update method described in any of the above embodiments.

[0187] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0188] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the vehicle function updating method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0189] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0190] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0191] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0192] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A method for updating vehicle functions, characterized in that: Applied to a server, the method comprises: Send software update package to target vehicle; Receiving an update result of the software update package fed back by the target vehicle end; In response to the update result being a successful update, obtaining current version number information of the vehicle-side software of the target vehicle-side; Determining a target function item to be updated on the target vehicle side according to the current version number information and the vehicle information on the target vehicle side; The target function item is sent to a target client paired with the target vehicle end, so that the target client sets corresponding configuration information according to the target function item.

2. The method according to claim 1, characterized in that The current version number information includes the software version number; the vehicle information includes the vehicle identification code; The step of determining the target function item to be updated for each target vehicle terminal according to the current version number information and the vehicle information of the target vehicle terminal includes: Determining a target client corresponding to each of the vehicle identification codes; Obtain a target feature value carried by the software version number; the target feature value is at least one of the feature values; In the association relationship between the pre-configured feature value and the function node of the target client, screening at least one target function node corresponding to the target feature value; Each of the target function nodes is used as the target function item.

3. The method according to claim 1, characterized in that The version number information includes a communication matrix version number; the vehicle information includes vehicle model information; and the method further includes: Determine the historical communication matrix and the historical communication matrix version number of the target vehicle according to the vehicle model information; In response to the current communication matrix version number being different from the historical communication matrix version number, determining a target acquisition scheme according to a correspondence between the historical communication matrix and the historical signal acquisition scheme; The target acquisition scheme is sent to the target vehicle end, so that the target vehicle end sets the target sending position and target signal length when uploading the vehicle end signal according to the target acquisition scheme.

4. The method according to claim 3, characterized in that Determining the target acquisition scheme according to the correspondence between the historical communication matrix and the historical signal acquisition scheme includes: According to the correspondence between the historical communication matrix and the historical signal acquisition scheme, determine the historical sending position and historical signal length of the vehicle-side signal upload, and the signal transmission rules between the historical communication matrix; Determining the target sending position and the target signal length corresponding to the current communication matrix according to the signal transmission rule; The target sending position and the target signal length are used as the target acquisition plan.

5. The method according to claim 4, characterized in that The method of determining the historical transmission position and historical signal length of the vehicle-side signal upload according to the correspondence between the historical communication matrix and the historical signal acquisition scheme, and the signal transmission rules between the historical communication matrix and the vehicle-side signal upload, includes: According to the correspondence between the historical communication matrix and the historical signal acquisition scheme, different signal flags when uploading different vehicle-side signals are determined respectively; each of the signal flags is associated with a signal sending position and a signal length of at least one bit; Using the association between each of the signal flags, the signal sending position and the signal length as the signal transmission rule; The step of determining the target sending position and the target signal length corresponding to the current communication matrix according to the signal transmission rule includes: Using the signal sending position corresponding to the signal flag bit in the current communication matrix as the target sending position; The signal length corresponding to the signal flag bit in the current communication matrix is ​​used as the target signal length.

6. A method for updating vehicle functions, characterized in that: Applied to the vehicle side, the method includes: Receive and install software update packages sent by the server; The update result of the successful update of the software update package and the current version number information of the vehicle-side software are fed back to the server.

7. The method according to claim 6, characterized in that The current version number information includes the current communication matrix version number; Feeding back the update result of the software update package being successfully updated and the current version number information of the vehicle-side software to the server includes: Feedback the update result of the software update package being successfully updated and the current communication matrix version number of the vehicle-side software to the server, so that the server determines the target acquisition plan according to the vehicle model information of the vehicle-side and the current communication matrix version number; the target acquisition plan includes the target sending position and target signal length of the vehicle-side signal; Receive the target acquisition plan sent by the server, and collect and upload the vehicle-side signal based on the target sending position and target signal length.

8. The method according to claim 6, characterized in that The method further comprises: Receiving a software backtracking instruction sent by the server; According to the software backtracking instruction, calling and downloading the installation version backtracking package from the server; The vehicle-side signal is collected and uploaded according to the signal collection scheme of the historical version corresponding to the version backtracking package.

9. A server comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 5 is implemented.

10. A vehicle comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 6 to 8 is implemented.

Images