Linkage updating method, device, vehicle networking platform and system

Abstract

The invention provides a linkage updating method and device, an Internet of Vehicles platform and a system, the method is applied to the Internet of Vehicles platform, and the method comprises the following steps: receiving a version upgrade package sent by a remote upgrade platform, analyzing the version upgrade package, and determining upgrade information corresponding to the version upgrade package; updating the version function identifier corresponding relation according to the upgrading information; for each vehicle, receiving a current version of each controller corresponding to the vehicle and a mobile application program version of the mobile terminal, and determining function updating information according to the current version of each controller, a version function identifier corresponding relation and a function identifier set currently displayed on a display interface of the mobile terminal; and according to the version of the mobile application program and the function updating information, determining an updating instruction of the mobile application program, and sending the updating instruction to the mobile application program so as to update the function identifier set in the display interface of the mobile terminal. Through the technical scheme of the invention, the consistency and availability of the functions of the vehicle end and the mobile application program are improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle remote function technology, and in particular to a linkage update method, device, vehicle networking platform and system. Background Art

[0002] At present, it is very common to control vehicles and perform remote functions through mobile applications. The update of each controller in the vehicle is mainly based on the remote upgrade platform for version update. The update of mobile applications is based on user selection needs.

[0003] The above situation may lead to the problem of mismatch between vehicle functions and the functions in mobile applications. For example, if a new function is added to the vehicle, the vehicle controller needs to be upgraded, and the corresponding related interface or content of the mobile application needs to be newly developed. However, if only the vehicle controller is upgraded or only the mobile application is upgraded, the complete new functions cannot be experienced, which will lead to poor user experience. Summary of the invention

[0004] In view of this, the purpose of this application is to propose a linkage update method, device, Internet of Vehicles platform and system to solve the problem of remote function mismatch and even user inability to fully use the remote function due to the upgrade of only one of the vehicle and mobile terminals.

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

[0006] Receive a version upgrade package sent by a remote upgrade platform, parse the version upgrade package, and determine upgrade information corresponding to the version upgrade package;

[0007] According to the upgrade information, the version function identifier correspondence is updated; wherein the version function identifier correspondence is the correspondence between the vehicle function identifier and the controller version;

[0008] For each vehicle, receiving the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determining the function update information according to the current version of each controller, the corresponding relationship between the version function identifiers, and the function identifier set currently displayed on the display interface of the mobile terminal;

[0009] An update instruction for the mobile application is determined according to the mobile application version and the function update information, and the update instruction is sent to the mobile application to update a function identifier set in the mobile terminal display interface.

[0010] Based on the above purpose, the present application also provides a linkage update device, which is configured on a vehicle networking platform, and the device includes:

[0011] An information determination module is used to receive a version upgrade package sent by a remote upgrade platform, parse the version upgrade package, and determine the upgrade information corresponding to the version upgrade package;

[0012] A correspondence determination module, used to update the version function identifier correspondence according to the upgrade information; wherein the version function identifier correspondence is the correspondence between the vehicle function identifier and the controller version;

[0013] A function change determination module is used to receive, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determine the function update information according to the current version of each controller, the corresponding relationship between the version function identifiers, and the function identifier set currently displayed on the display interface of the mobile terminal;

[0014] The mobile application update module is used to determine the update instruction of the mobile application according to the mobile application version and the function update information, and send the update instruction to the mobile application to update the function identifier set in the mobile terminal display interface.

[0015] Based on the above purpose, the present application also provides a vehicle networking platform, 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, a linkage update method as provided in any embodiment of the present application is implemented.

[0016] Based on the above purpose, the present application also provides a linkage update system, which includes: a remote upgrade platform, a vehicle networking platform as provided in any embodiment of the present application, at least one vehicle, and a mobile application corresponding to each vehicle; wherein,

[0017] The remote upgrade platform is used to send the version upgrade package to the vehicle networking platform; receive the controller upgrade results sent by each vehicle, and update the controller version corresponding to each vehicle according to the controller upgrade results;

[0018] The vehicle is configured to receive a version upgrade package sent by the vehicle networking platform, perform an upgrade based on the version upgrade package, determine an upgrade result, and send the upgrade result to the remote upgrade platform;

[0019] The mobile application corresponding to each vehicle is used to receive and respond to the update instruction.

[0020] From the above, it can be seen that the linkage update method provided in the present application receives the version upgrade package sent by the remote upgrade platform, parses the version upgrade package, determines the upgrade information corresponding to the version upgrade package, and updates the version function identifier correspondence according to the upgrade information, so as to record the correspondence between the vehicle function identifier and the controller version in the Internet of Vehicles platform, so as to ensure the correspondence between the vehicle-side controller and the mobile application function. Furthermore, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal are received, and the function update information is determined according to the current version of each controller, the version function identifier correspondence and the function identifier set currently displayed on the mobile terminal display interface. By comparing the current version of each controller and the version function identifier correspondence, the function identifier sets that can be satisfied by each controller on the vehicle side can be determined, and then compared with the currently displayed function identifier set to determine the function update information. Among the functions supported by the mobile application version, it is determined whether there is function update information. According to the judgment result, it can be determined whether there is a functional mismatch between the vehicle side and the mobile side. Furthermore, if there is a mismatch, an update instruction for the mobile application can be generated and sent to the mobile application to update the function identifier set in the mobile terminal display interface. This realizes that when the vehicle controller is updated, the mobile application corresponding to the vehicle is matched and linked through the updated version function identifier correspondence, ensuring the functional consistency and availability of the two, and further improving the user's remote control experience of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] 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.

[0022] Figure 1 A flowchart of a linkage update method provided in an embodiment of the present application;

[0023] Figure 2 A flowchart of another linkage update method provided in an embodiment of the present application;

[0024] Figure 3 A schematic diagram of the structure of a linkage update device provided in an embodiment of the present application;

[0025] Figure 4 A schematic diagram of the structure of a linkage update system provided in an embodiment of the present application;

[0026] Figure 5An interactive flow chart of a linkage update system provided in an embodiment of the present application;

[0027] Figure 6 A schematic diagram of the hardware structure of a vehicle networking platform provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] 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.

[0029] 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.

[0030] At present, the use of the remote function of the vehicle can only be used when the application on the mobile terminal and the controller program on the vehicle terminal are updated. The mobile application on the mobile terminal can be reminded to upgrade the versions of the controllers on the vehicle side in any of the following ways: 1. The remote upgrade platform receives the version upgrade package and the upgrade information corresponding to the version upgrade package uploaded by the operator, and the remote upgrade platform pushes the above content to the Internet of Vehicles platform and displays it through the mobile application on the mobile terminal. 2. The owner opens the mobile application to view the versions of the controllers on the vehicle side. Specifically, it can be clicked on the versions of the controllers on the vehicle side. The current versions of the controllers on the vehicle side can be uploaded to the Internet of Vehicles platform through T-BOX (Telematics Box, T box). Then, the Internet of Vehicles platform can obtain the latest versions of the controllers on the vehicle side from the remote upgrade platform and match them with the current versions on the vehicle side. Then, the mobile application can display whether the controllers on the vehicle side are the latest versions, and prompt the update of the controllers on the vehicle side through the mobile application. When upgrading the vehicle-side controllers, that is, upgrading the entire vehicle, the vehicle-side controllers can be determined to be upgraded through the mobile application, and then the entire vehicle can be remotely awakened through the mobile application. The vehicle computer accesses the remote upgrade platform through the public network provided by T-BOX to download the software, and after the download is completed, the vehicle-side controllers are upgraded. However, during the upgrade process, there are cases where the upgrade is abnormal and an error is reported, resulting in the failure of the vehicle upgrade.

[0031] Figure 1 A flowchart of a linkage update method provided in an embodiment of the present application is mainly applied to the Internet of Vehicles platform, and is suitable for recording the functions displayed by the mobile application on the corresponding mobile terminal for each vehicle in the Internet of Vehicles platform, and updating the functions displayed by the mobile application when the controller on the vehicle terminal is upgraded, so that the mobile terminal reference program can be adaptively updated. This method can be configured in the Internet of Vehicles platform. Figure 1 As shown, the method may specifically include the following steps:

[0032] S110: Receive a version upgrade package sent by a remote upgrade platform, parse the version upgrade package, and determine upgrade information corresponding to the version upgrade package.

[0033] Among them, the remote upgrade platform is a mobile terminal's firmware over-the-air (FOTA) software upgrade platform, which refers to a platform that provides upgrade services for controllers of vehicles with networking functions through cloud upgrade technology. The version upgrade package is a software package used to upgrade the version of the vehicle's controller. The upgrade information is information related to the specific upgrade content of the version upgrade package, such as: the controller upgraded this time, the version of the upgraded controller, and the new functions after the upgrade.

[0034] Specifically, when the vehicle controller needs to be upgraded, the version upgrade package can be sent to the Internet of Vehicles platform through the remote upgrade platform. After receiving the version upgrade package, the Internet of Vehicles platform can parse the information related to the upgrade content carried in the version upgrade package to obtain the upgrade information corresponding to the version upgrade package.

[0035] Based on the above example, if the upgrade information includes each target controller, target function, and target version corresponding to each target controller, the version upgrade package can be parsed in the following manner to determine the upgrade information corresponding to the version upgrade package:

[0036] Parse the version upgrade package and determine the function update field and controller upgrade field in the version upgrade package;

[0037] According to the controller upgrade field, determine each target controller and the target version corresponding to each target controller;

[0038] In response to the function update field being empty, determining that the target function is empty;

[0039] In response to the function update field being not empty, each target function is determined according to the function update field.

[0040] Among them, the target controller is the controller that can be upgraded after the vehicle executes the version upgrade package. The target version is the version of the target controller after the upgrade based on the version upgrade package. The target function is the function that is newly added or changed after the vehicle executes the version upgrade package. The target function includes the new function and the changed function of the function version update. It can be understood that the new function is a brand new function that did not exist in the past. The changed function is the function of the existing function after the version is upgraded. The function update field is a field related to the addition or change of the function carried in the version upgrade package. The controller upgrade field is a field related to the upgrade of the vehicle's controller carried in the version upgrade package.

[0041] Specifically, the version upgrade package is parsed, and the function update field and the controller upgrade field are determined from the version upgrade package. For example, the function update field and the controller upgrade field can be determined according to the predefined field position. After determining the controller upgrade field, the content of the controller field is analyzed to identify each target controller and the target version corresponding to each target controller. For example, each controller identifier included in the controller field is identified, and the controllers corresponding to these controller identifiers are used as target controllers. Then, for each controller identifier included in the controller field, the version identifier corresponding to it is identified, that is, the target version corresponding to the target controller. Further, the function update field is analyzed. In response to the function update field being empty, it means that the controller upgrade of this vehicle has not triggered any functional changes, so it can be determined that the target function is empty; in response to the function update field being not empty, it means that the controller upgrade of this vehicle will further cause functional changes, so each target function can be identified from the function update field. For example: the function identifier includes the function and the function version. If a new function identifier is identified, it is determined that the target function includes the new function, and the function version of the new function is used as the initial version of the new function. If an existing function identifier is identified, it is determined that the target function includes the changed function of the function version update, and the function version of the changed function is used as the new function version identifier of the existing function.

[0042] Based on the above example, the remote upgrade platform can send the version upgrade package to the vehicle, so that the vehicle can parse and execute the version upgrade package after receiving the version upgrade package, and upgrade each target controller to the target version.

[0043] Optionally, the vehicle can upload the versions of each controller of the vehicle to the remote upgrade platform when ignition is started. The remote upgrade platform determines whether the versions of each controller of the vehicle are the latest versions. If not, the vehicle will be notified to update the controllers. After the vehicle confirms the update, the remote upgrade platform will send the version upgrade package to the vehicle so that the vehicle can complete the upgrade and report the upgrade results.

[0044] S120. Update the version function identifier correspondence according to the upgrade information.

[0045] Among them, the version function identification correspondence is a correspondence established in the Internet of Vehicles platform, and the version function identification correspondence is a correspondence between the vehicle's function identification and the controller version.

[0046] Specifically, the upgrade information is classified and organized into a pre-stored version function identifier correspondence relationship to update the version function identifier correspondence relationship so that the version function identifier correspondence relationship can adapt to each vehicle after the version upgrade package is upgraded.

[0047] Based on the above example, if the upgrade information includes each target controller, target function and target version corresponding to each target controller, the corresponding relationship of the version function identifier can be updated according to the upgrade information in the following manner:

[0048] In response to the target function being empty, adding each target version to the controller version of each target controller in the version function identifier correspondence relationship according to each target controller and the target version corresponding to each target controller;

[0049] In response to the number of the target functions being at least one, determining, based on each existing function and each target function, a function to be maintained, a function to be changed, and a function to be newly added;

[0050] For each retained function, in response to the controllers corresponding to the retained function in the version function identifier correspondence relationship including a target controller, each target version is added to the controller version of each target controller corresponding to the retained function in the version function identifier correspondence relationship according to each target controller and the target version corresponding to each target controller;

[0051] For each changed function, according to the target version of each target controller corresponding to the changed function, the function version corresponding to the changed function and the versions of each controller in the version function identifier correspondence are updated;

[0052] For each newly added function, according to each target controller corresponding to the newly added function and the target version of each target controller, the function version corresponding to the newly added function, each controller and each controller version are added to the version function identifier correspondence relationship.

[0053] Among them, the existing functions are the functions that have been available before this update according to the corresponding relationship between the version function identifier. The retained functions are the remaining functions except the target function in the existing functions, that is, the functions whose function versions have not changed. The function version can be understood as the version identifier of the vehicle function. The controller version can be understood as the version identifier of the vehicle controller.

[0054] Specifically, if the target function is empty, it means that the update using the version upgrade package only updates each target controller, but does not cause the function update of the vehicle. Therefore, for each target controller, the controller version corresponding to the target controller can be found in the version function identifier correspondence relationship, and the target version corresponding to the target controller can be added to the controller version of the target controller. If the number of target functions is at least one, it means that the target function is updated while updating the target controller, which can be a changed function and / or a new function. The existing functions can be determined from the version function identifier correspondence relationship, and the functions repeated with the existing functions in the target function are used as changed functions, and the functions repeated with the existing functions in the target function are used as new functions, that is, the other functions in the target function except the changed functions are used as new functions, and the remaining functions in the existing functions except the target functions can be used as retained functions. For each retained function, the corresponding controllers in the retained function are found in the version function identifier correspondence relationship. If the target controller is included, the target version of the target controller is added thereto, otherwise it remains unchanged. For each changed function, the changed function is found from the version function identifier correspondence, and the function version of the changed function is updated. Since the changed function is generated by the update of at least one controller corresponding to the changed function, a new correspondence is established for the updated function version. For example, the controller version of the controller that has not been upgraded is kept unchanged, and the controller version of the upgraded target controller is updated to the target version. For each new function, the new function is added to the version function identifier correspondence, and the controllers and controller versions required for the new function are identified. If these controllers include the target controller, the target version of the target controller is used to establish a correspondence. If these controllers include other controllers except the target controller, the current versions of the other controllers are used to establish a correspondence. Based on this, the function version, controllers and controller versions corresponding to the new function can be added to the version function identifier correspondence.

[0055] For example, if the target function is empty, the target controller is a, and the target version corresponding to the target controller a is v1.5, then in the corresponding relationship between the version and function identifiers, determine the controller flags corresponding to the target controller a, and add the target version v1.5. For example, if the target controller a and controller b corresponding to function A, at this time, the version corresponding to the target controller a is v1.4, and the version corresponding to the controller b is v2.0, then after adding the new target version, the versions of the target controller a corresponding to function A are v1.4 and v1.5, and the version corresponding to the controller b is still v2.0. If the number of target functions is at least one, the processing method for maintaining the function is similar to the processing method for the target function being empty, and will not be repeated here. If the target function includes the change function B, the target controller is a, and the target version corresponding to the target controller a is v1.5, then for the change function B, the change function B, the current version of the change function B, the corresponding target controller a and the controller c are determined in the version function identifier correspondence. At this time, the corresponding version of the target controller a is v1.4, and the corresponding version of the controller c is v2.2. Then, the current version of the change function B is changed and updated to the new function version. Then, for the new function version, the corresponding version of the target controller a is v1.5, and the corresponding version of the controller c is still v2.2. If the target function includes a new function C, and the target controller is a, and the target version corresponding to the target controller a is v1.5, it can be determined that the controllers corresponding to the new function C include the target controller a and controller d, wherein controller d is updated this time, and the current version is v1.1, then a correspondence corresponding to the new function C can be established in the version function identifier correspondence, and the function version of the new function C can be initialized, such as 1.0, etc. Further, a correspondence with the target controller a and controller d is established, wherein the version corresponding to the target controller a is v1.5, and the version corresponding to the controller d is v1.1.

[0056] S130. For each vehicle, receive the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determine the function update information according to the current version of each controller, the correspondence between the version function identifiers, and the function identifier set currently displayed on the mobile terminal display interface.

[0057] Among them, the current version is the software version currently being used by each controller in the vehicle. The mobile terminal is a mobile terminal used to control the vehicle, such as a mobile phone. The mobile application version is the version information of the application installed in the mobile terminal for controlling the vehicle. The set of function identifiers currently displayed on the mobile terminal display interface is a set of identifiers of various functions that can be displayed and used by users in the display interface of the application installed in the mobile terminal for controlling the vehicle. It can be recorded in advance in the Internet of Vehicles platform corresponding to the vehicle, or it can be matched and determined based on the correspondence between the versions of the controllers before the update and the version function identifiers before the update. The function update information is the function identifiers that are different between the function identifier set currently displayed on the mobile terminal display interface and the function identifiers that can be used by the upgraded and updated vehicle, that is, it includes various functions and corresponding function versions.

[0058] Specifically, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal can be received. Further, the current version of each controller is matched in the version function identifier correspondence to determine the function identifier of each function currently available for the vehicle. These function identifiers are matched with the function identifier set currently displayed on the mobile terminal display interface to determine the function update information that is different.

[0059] Based on the above example, the current version of each controller corresponding to the vehicle can be received in the following way:

[0060] Based on the public network, the current versions of the controllers corresponding to the vehicle are received from the remote upgrade platform; or, based on the private network, the current versions of the controllers corresponding to the vehicle are received from the vehicle.

[0061] In this example, the public network refers to the communication network between the remote upgrade platform and the Internet of Vehicles platform. In this example, the private network refers to the communication network between the vehicle's onboard communication module and the Internet of Vehicles platform.

[0062] Specifically, after executing the version upgrade package, the vehicle can feed back the upgrade results to the remote upgrade platform to record the current versions of each controller of the vehicle through the remote upgrade platform. Therefore, the Internet of Vehicles platform can receive the current versions of each controller corresponding to the vehicle sent by the remote upgrade platform based on the public network between the remote upgrade platform and the Internet of Vehicles platform. After the vehicle executes the version upgrade package, the vehicle's on-board host can send the current versions of each controller corresponding to the vehicle to the on-board communication module. Therefore, the Internet of Vehicles platform can receive the current versions of each controller corresponding to the vehicle sent by the on-board communication module based on the private network between the on-board communication module and the Internet of Vehicles platform.

[0063] Optionally, the first version of each controller corresponding to the vehicle sent by the remote upgrade platform can be received based on the public network, and the second version of each controller corresponding to the vehicle sent by the vehicle can be received based on the private network; in response to the first version of each controller received being the same as the second version of each controller, the first version of each controller is used as the current version of each controller corresponding to the vehicle; in response to the first version of each controller received being different from at least one of the second versions of each controller, the communication links between the public network and the private network are checked, and after the check is passed, the steps of receiving the first version of each controller corresponding to the vehicle sent by the remote upgrade platform based on the public network, and receiving the second version of each controller corresponding to the vehicle sent by the vehicle based on the private network are returned to be executed.

[0064] If the public network is attacked by information, the current versions of the controllers corresponding to the vehicle sent by the remote upgrade platform will be unavailable. If the private network is attacked by information, the current versions of the controllers corresponding to the vehicle sent by the vehicle will be unavailable. The above two situations will affect the subsequent function comparison and make it impossible to accurately obtain function update information. The method of combining the public network and the private network to obtain the current version of each controller corresponding to the vehicle can avoid the situation where the public network or the private network is attacked by information alone, resulting in the loss or tampering of the current version, thereby ensuring the security and availability of information, and then ensuring the accuracy of the subsequent function update information.

[0065] S140: Determine an update instruction for the mobile application according to the mobile application version and the function update information, and send the update instruction to the mobile application to update the function identifier set in the mobile terminal display interface.

[0066] The update instruction may be an instruction for instructing the mobile application to update, or may be an instruction for instructing the mobile application to display some hidden existing functions.

[0067] Specifically, after obtaining the mobile application version, the functions supported by the mobile application version can be determined. Some of these functions may be used by the vehicle, and some of them cannot be used by the vehicle because the vehicle is not equipped with certain controllers. Therefore, some of the functions that can be used by the vehicle can be displayed in the mobile application display interface corresponding to the vehicle, and the remaining functions are hidden to avoid the situation where the user can see them in the mobile application display interface but cannot use them. Therefore, the functions supported by the mobile application version can be compared with the function update information. If the functions supported by the mobile application version include all the functions in the function update information, and the function versions are the same, if so, it means that the functions that could not be executed by the vehicle before can be executed through the controller update, but these functions are already configured in the mobile application. Therefore, an update instruction for changing the function from a hidden state to a displayed state is generated. If the functions supported by the mobile application version do not include all the functions in the function update information, or there are differences in the function versions of the included functions, it means that the mobile application version can no longer meet the requirements of the vehicle controller after the upgrade and update. Therefore, it is necessary to upgrade the mobile application version, that is, to generate an update instruction for upgrading the mobile application version. Send an update instruction to the mobile application to update the function identifier set in the mobile display interface to adapt it to the current versions of the vehicle's controllers.

[0068] The linkage update method provided in this embodiment receives the version upgrade package sent by the remote upgrade platform, parses the version upgrade package, determines the upgrade information corresponding to the version upgrade package, and updates the version function identifier correspondence based on the upgrade information, so as to record the correspondence between the vehicle function identifier and the controller version in the Internet of Vehicles platform, so as to facilitate the subsequent determination of the corresponding displayable and usable function identifier for each vehicle's different controller versions. Furthermore, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal are received, and the function update information is determined according to the current version of each controller, the correspondence between the version function identifiers and the function identifier set currently displayed on the mobile terminal display interface. By comparing the current version of each controller and the correspondence between the version function identifiers, the target function identifier set displayed on the mobile terminal display interface can be determined, and then compared with the currently displayed function identifier set to determine the function update information. Among the functions supported by the mobile application version, it is determined whether there is function update information. According to the judgment result, an update instruction for the mobile application is generated, and the update instruction is sent to the mobile application to update the function identifier set in the mobile terminal display interface. This realizes a matching linkage update of the mobile application corresponding to the vehicle while the vehicle controller is updated, thereby ensuring the functional consistency and availability of the two, and further improving the user's remote control experience of the vehicle.

[0069] The above embodiment describes the method of linkage update. In addition to the method of determining the upgrade information corresponding to the version upgrade package and the method of updating the corresponding relationship between the version function identifiers in the above example, in this embodiment, a method of determining the function update information and a method of determining the update instruction of the mobile application are further described, such as Figure 2 shown. Figure 2 This is a flowchart of another linkage update method provided by an embodiment of the present application, wherein the explanations of terms that are the same or corresponding to the above-mentioned embodiments are not repeated here. Figure 2 As shown, the method may specifically include the following steps:

[0070] S201: Receive a version upgrade package sent by a remote upgrade platform, parse the version upgrade package, and determine upgrade information corresponding to the version upgrade package.

[0071] Based on the above example, when the vehicle leaves the factory, the display interface of the mobile terminal can be adaptively configured according to the vehicle configuration information, that is, before receiving the version upgrade package sent by the remote upgrade platform, perform the following operations:

[0072] For each vehicle, determine the controllers corresponding to the vehicle and the installation versions of the controllers according to the configuration information corresponding to the vehicle;

[0073] Determine the single vehicle function corresponding to the vehicle from the function permission library according to the pre-stored version function identification correspondence, each controller and the installation version of each controller;

[0074] According to the bicycle functions, determine the initial function identifier set displayed on the mobile terminal display interface.

[0075] Among them, the configuration information refers to the configuration of the vehicle when it leaves the factory, which may include standard information and optional information. The installed version is the version information of each controller configured when the vehicle leaves the factory. Single vehicle functions are functions configured for each vehicle when it leaves the factory. The function permission library refers to each function in the corresponding relationship between version function identifiers, which may be all functions that can be supported by the current version of the mobile terminal. The initial function identifier set is a set of function identifiers of each single vehicle function, that is, a set of function identifiers of the functions that can be displayed on the mobile application of the mobile terminal when the vehicle leaves the factory.

[0076] Specifically, for each vehicle, the configuration information of the vehicle is obtained, and the controllers corresponding to the vehicle and the installed versions of the controllers are determined from the configuration information. Furthermore, in the pre-stored version function identifier correspondence, the correspondence is retrieved according to the controllers and the installed versions of the controllers, and the functions that can be supported by these controllers and the corresponding installed versions, that is, the single vehicle functions corresponding to the vehicle, can be determined from the function permission library. The function identifiers of these single vehicle functions are used as the initial function identifier set displayed on the mobile terminal display interface, so that only the single vehicle functions corresponding to the initial function identifier set are displayed in the mobile application of the mobile terminal corresponding to the vehicle, so as to avoid other functions except single vehicle functions being exposed in the mobile application and affecting the user's use.

[0077] S202: Update the version function identifier correspondence according to the upgrade information.

[0078] S203. For each vehicle, receive the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determine the target function identifier set displayed on the mobile terminal display interface according to the current version of each controller and the corresponding relationship between the version function identifiers.

[0079] The target function identifier set is a set of function identifiers determined by matching the current version of each controller in the version function identifier correspondence, that is, the function identifiers of each function that the vehicle can currently use.

[0080] Specifically, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal can be received. Further, the current version of each controller is matched in the version function identifier correspondence relationship to determine the function identifier of each function currently available for the vehicle as the target function identifier set displayed on the mobile terminal display interface.

[0081] S204: Determine function update information according to the function identifier set currently displayed on the mobile terminal display interface and the target function identifier set.

[0082] Specifically, the target function identification set is compared with the function identification set currently displayed on the mobile terminal display interface to determine each function identification that exists in the target function identification set but does not exist in the function identification set currently displayed on the mobile terminal display interface, including each function and its functional version, and these function identifications are used as function update information.

[0083] S205. According to the mobile application version, determine the supporting functions corresponding to the mobile application version and the function versions corresponding to each supporting function, and judge whether each supporting function includes each function in the function update information. If so, execute S207; if not, execute S206.

[0084] Among them, the supported functions are the functions that can be used after the mobile application version is developed, and are irrelevant to whether the vehicle itself is installed with the corresponding controller and whether the controller version is compliant.

[0085] Specifically, according to the mobile application version, the supporting functions corresponding to the mobile application version and the functional versions corresponding to these supporting functions can be determined according to the functional information when the mobile application version is developed. Furthermore, it can be determined whether each supporting function includes each function in the functional update information, so as to determine whether the mobile application version needs to be updated or the existing supporting functions need to be displayed on the display interface of the mobile application.

[0086] S206: Determine that the update instruction of the mobile application is an upgrade reminder instruction, and execute S210.

[0087] Among them, the upgrade reminder instruction is an instruction used to remind and trigger the mobile application installed on the mobile terminal corresponding to the vehicle to update its version.

[0088] Specifically, if no, it means that the supported functions do not include at least one function in the function update information, that is, the supported functions of the current mobile application version cannot cover all the functions that can be realized after the controller is updated. It can be understood that there are also new functions on the mobile application, which the current mobile application cannot support. Therefore, the update instruction of the mobile application is determined to be a reminder upgrade instruction to control the mobile terminal to update the version of the mobile application.

[0089] Optionally, in response to the mobile application performing a version update based on the reminder upgrade instruction, according to the correspondence between the current version function identifiers in the Internet of Vehicles platform, for each controller corresponding to the received vehicle and the corresponding current version, the current function corresponding to the vehicle is determined from the function permission library corresponding to the updated mobile application version, and based on the current function, the function identifier set displayed on the mobile display interface of the updated mobile application version is determined.

[0090] S207 , determining whether the function version of each function in the function update information is the same as the function version of each supporting function, if they are the same, executing S208 ; if they are not the same, executing S209 .

[0091] Specifically, if yes, it means that the supported functions include the functions in the function update information, but it is necessary to further determine whether the function version has changed. For example, the current mobile application version can support the old version of a function, but does not support the new version of the function, and the controller version of the updated vehicle matches the new version of the function. In this case, the mobile application version needs to be updated.

[0092] S208 , determining that the update instruction of the mobile application is a function display update instruction, and executing S210 .

[0093] Among them, the function display update instruction is an instruction for triggering the mobile application to update and display various function identifiers that can be displayed on the mobile terminal display interface based on the current mobile application version.

[0094] Specifically, if the function version of each function in the function update information is the same as the function version of each supporting function, it means that only these functions in the function update information need to be displayed, and there is no need to update the version of the mobile application. Therefore, the update instruction of the mobile application is determined to be a function display update instruction.

[0095] S209: Determine that the update instruction of the mobile application is an upgrade reminder instruction, and execute S210.

[0096] Specifically, if the function version of each function in the function update information is different from the function version of each supported function, it means that although the current mobile application version can support each function in the function update information, the function version cannot match the controller versions of the vehicle after the update based on the version upgrade package. Therefore, the update instruction of the mobile application is determined to be a reminder upgrade instruction to control the mobile terminal to update the version of the mobile application.

[0097] S210: Send an update instruction to the mobile application to update the function identifier set in the mobile terminal display interface.

[0098] The linkage update method provided in this embodiment receives, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determines the target function identification set displayed on the mobile terminal display interface based on the current version of each controller and the correspondence between the version function identifications. By comparing the current version of each controller and the correspondence between the version function identifications, the target function identification set can be determined. Furthermore, based on the function identification set currently displayed on the mobile terminal display interface and the target function identification set, function update information is determined, so that the target function identification set is compared with the currently displayed function identification set to determine the difference in the displayed function identification. According to the mobile application version, the supported functions corresponding to the mobile application version and the functional versions corresponding to each supported function are determined, and it is determined whether each supported function includes each function in the functional update information. If so, it is further determined whether the functional version of each function in the functional update information is the same as the functional version of each supported function. If they are the same, it is determined that the update instruction of the mobile application is a function display update instruction. If they are not the same, it is determined that the update instruction of the mobile application is a reminder upgrade instruction; if not, it is determined that the update instruction of the mobile application is a reminder upgrade instruction. By comparing whether the supported functions include each function in the functional update information, and comparing the functional version of each function in the functional update information with the functional version of each supported function, it is achieved to further distinguish whether to display previously hidden functions based on the mobile application version or to update the mobile application version. It is added that only function display updates are performed without updating the mobile application version. The mobile application can be updated according to different situations to ensure functional consistency and availability with the vehicle end, improve update efficiency, and avoid the problem of displaying functions that cannot be used on the vehicle end on the mobile application, causing interference to users.

[0099] It should be noted that the method of the embodiment of the present application can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present application, and the multiple devices will interact with each other to complete the described method.

[0100] 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.

[0101] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a linkage update device. Figure 3 A schematic diagram of a linkage update device provided in an embodiment of the present application, referring to Figure 3 The linkage update device is configured on the Internet of Vehicles platform, and includes: an information determination module 310, a corresponding relationship determination module 320, a function change determination module 330 and a mobile application update module 340.

[0102] Among them, the information determination module 310 is used to receive the version upgrade package sent by the remote upgrade platform, parse the version upgrade package, and determine the upgrade information corresponding to the version upgrade package; the correspondence determination module 320 is used to update the version function identifier correspondence according to the upgrade information; wherein the version function identifier correspondence is the correspondence between the vehicle function identifier and the controller version; the function change determination module 330 is used to receive the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal for each vehicle, and determine the function update information according to the current version of each controller, the version function identifier correspondence and the function identifier set currently displayed on the mobile terminal display interface; the mobile application update module 340 is used to determine the update instruction of the mobile application according to the mobile application version and the function update information, and send the update instruction to the mobile application to update the function identifier set in the mobile terminal display interface.

[0103] Based on the above example, optionally, the upgrade information includes each target controller, target function and the target version corresponding to each target controller; the information determination module 310 is also used to parse the version upgrade package to determine the function update field and the controller upgrade field in the version upgrade package; according to the controller upgrade field, each target controller and the target version corresponding to each target controller are determined; in response to the function update field being empty, the target function is determined to be empty; in response to the function update field being not empty, each target function is determined according to the function update field; wherein the target function includes a new function and a changed function of the function version update.

[0104] Based on the above example, optionally, the upgrade information includes each target controller, target function and the target version corresponding to each target controller; the correspondence determination module 320 is also used to respond to the target function being empty, then, according to each target controller and the target version corresponding to each target controller, add each target version to the controller version of each target controller in the version function identifier correspondence; in response to the number of the target functions being at least one, determine the maintained function, changed function and new function according to each existing function and each target function; for each maintained function, in response to the corresponding relationship between the version function identifier and each controller corresponding to the maintained function, Including target controllers, then according to each target controller and the target version corresponding to each target controller, each target version is added to the controller version of each target controller corresponding to the maintained function in the version function identification correspondence relationship; for each changed function, according to the target version of each target controller corresponding to the changed function, the function version and each controller version corresponding to the changed function in the version function identification correspondence relationship are updated; for each newly added function, according to each target controller corresponding to the newly added function and the target version of each target controller, the function version, each controller and each controller version corresponding to the newly added function are added in the version function identification correspondence relationship.

[0105] Based on the above example, optionally, before receiving the version upgrade package sent by the remote upgrade platform, it also includes: a mobile terminal initial display interface configuration module, which is used to determine, for each vehicle, the controllers corresponding to the vehicle and the installation version of each controller according to the configuration information corresponding to the vehicle; determine the single vehicle function corresponding to the vehicle from the function permission library according to the pre-stored version function identifier correspondence, each controller and the installation version of each controller; determine the initial function identifier set displayed on the mobile terminal display interface according to the single vehicle function.

[0106] Based on the above example, optionally, the function change determination module 330 is used to receive the current version of each controller corresponding to the vehicle sent by the remote upgrade platform based on a public network; or, based on a private network, receive the current version of each controller corresponding to the vehicle sent by the vehicle.

[0107] Based on the above example, optionally, the function change determination module 330 is also used to determine the target function identifier set displayed on the mobile terminal display interface according to the current version of each controller and the correspondence between the version function identifiers; and determine the function update information according to the function identifier set currently displayed on the mobile terminal display interface and the target function identifier set.

[0108] Based on the above example, optionally, the mobile application update module 340 is also used to determine the supporting functions corresponding to the mobile application version and the function versions corresponding to each supporting function according to the mobile application version; in response to each supporting function not including at least one function in the function update information, determining that the update instruction of the mobile application is a reminder upgrade instruction; in response to each supporting function including each function in the function update information, determining whether the function version of each function in the function update information is the same as the function version of each supporting function; if they are the same, determining that the update instruction of the mobile application is a function display update instruction; if they are not the same, determining that the update instruction of the mobile application is a reminder upgrade instruction.

[0109] 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.

[0110] The device of the above embodiment is used to implement the corresponding linkage update method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0111] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application also provides a vehicle networking platform, 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 linkage update method described in any of the above embodiments is implemented.

[0112] Figure 4 A schematic diagram of a linkage update system provided in an embodiment of the present application, referring to Figure 4 , a remote upgrade platform 410, a vehicle networking platform 420 as described in any embodiment, at least one vehicle 430, and a mobile application 440 corresponding to each vehicle 430; wherein,

[0113] The remote upgrade platform 410 is used to send the version upgrade package to the vehicle networking platform 420; receive the controller upgrade results sent by each vehicle 430, and update the controller version corresponding to each vehicle 430 according to the controller upgrade results;

[0114] The vehicle 430 is used to receive the version upgrade package sent by the remote upgrade platform 410, perform an upgrade based on the version upgrade package, determine an upgrade result, and send the upgrade result to the remote upgrade platform 420;

[0115] The mobile application 440 corresponding to each vehicle 430 is used to receive and respond to the update instruction.

[0116] It is understandable that the corresponding vehicle 430 can be remotely controlled via the mobile application 440 .

[0117] Figure 5 An interactive flow chart of a linkage update system provided in an embodiment of the present application, Figure 5 Specifically, it may include the following contents:

[0118] The remote upgrade platform is used to maintain the upgradeable versions of each controller and the corresponding version upgrade packages. Therefore, the version upgrade package can be sent to the Internet of Vehicles platform. After receiving the version upgrade package, the Internet of Vehicles platform can parse the version upgrade package, determine the upgrade information corresponding to the version upgrade package, and maintain and update the corresponding relationship between the version function identifiers stored on the Internet of Vehicles platform. When the vehicle is ignited, the current version of each controller can be uploaded to the remote upgrade platform. The remote upgrade platform stores the current version of each controller reported by the vehicle and determines whether there is a version upgrade package that can upgrade the vehicle. If not, the process ends. If so, a message is pushed to the vehicle to allow the user to confirm the upgrade. When the confirmation message is received, the upgrade version package is sent to the vehicle, so that the vehicle is upgraded based on the upgrade version package, and the upgrade result (updated current version) is reported to the remote upgrade platform. The remote upgrade platform can record the upgrade results of the vehicle and send the upgrade results of the vehicle to the Internet of Vehicles platform, notifying the Internet of Vehicles platform to optimize the display of the mobile application. The Internet of Vehicles platform receives the upgrade results of the vehicle, matches based on the pre-stored version function identifier correspondence, and determines whether there is function update information. If not, the process ends. If so, a message is pushed to the mobile terminal, and when the user confirms the update, the update instruction of the mobile application is determined and sent to the mobile terminal to update the display interface of the mobile application on the mobile terminal. The user can remotely control the vehicle through the updated mobile application on the mobile terminal, that is, send a remote control instruction to the corresponding vehicle, and the vehicle can respond to the remote control instruction issued by the mobile application to complete the remote control of the vehicle.

[0119] The linkage update system provided in this embodiment maintains the correspondence between version function identifiers in the Internet of Vehicles platform through the interaction between the remote upgrade platform, the Internet of Vehicles platform, at least one vehicle, and the mobile applications corresponding to each vehicle, and can issue update instructions to the mobile application after the various controllers of the vehicle are upgraded, thereby realizing linkage updates of the vehicle and the mobile application corresponding to the vehicle, ensuring the consistency and availability of the functions between the two, and improving the user experience.

[0120] Figure 6A more specific schematic diagram of the hardware structure of the Internet of Vehicles platform provided in this embodiment 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 in communication within the device through the bus 1050.

[0121] 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.

[0122] 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.

[0123] 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.

[0124] 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.).

[0125] 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).

[0126] 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.

[0127] The Internet of Vehicles platform of the above-mentioned embodiment is used to implement the corresponding linkage update method in any of the above-mentioned embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

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

[0129] 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.

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

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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 linkage update method, characterized in that: Applied to the Internet of Vehicles platform, including: Receive a version upgrade package sent by a remote upgrade platform, parse the version upgrade package, and determine upgrade information corresponding to the version upgrade package; According to the upgrade information, the version function identifier correspondence is updated; wherein the version function identifier correspondence is the correspondence between the vehicle function identifier and the controller version; For each vehicle, receiving the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determining the function update information according to the current version of each controller, the corresponding relationship between the version function identifiers, and the function identifier set currently displayed on the display interface of the mobile terminal; An update instruction for the mobile application is determined according to the mobile application version and the function update information, and the update instruction is sent to the mobile application to update a function identifier set in the mobile terminal display interface.

2. The method according to claim 1, characterized in that The upgrade information includes each target controller, target function and target version corresponding to each target controller; the parsing of the version upgrade package to determine the upgrade information corresponding to the version upgrade package includes: Parsing the version upgrade package to determine a function update field and a controller upgrade field in the version upgrade package; Determine each target controller and the target version corresponding to each target controller according to the controller upgrade field; In response to the function update field being empty, determining that the target function is empty; In response to the function update field being not empty, each target function is determined according to the function update field; wherein the target function includes a newly added function and a changed function of a function version update.

3. The method according to claim 1, characterized in that The upgrade information includes each target controller, target function and target version corresponding to each target controller; the corresponding relationship of the updated version function identifier according to the upgrade information includes: In response to the target function being empty, adding each target version to the controller version of each target controller in the version function identifier correspondence relationship according to each target controller and the target version corresponding to each target controller; In response to the number of the target functions being at least one, determining, according to each existing function and each target function, a function to be maintained, a function to be changed, and a function to be newly added; For each retained function, in response to the controllers corresponding to the retained function in the version function identifier correspondence relationship including a target controller, each target version is added to the controller version of each target controller corresponding to the retained function in the version function identifier correspondence relationship according to each target controller and the target version corresponding to each target controller; For each changed function, according to the target version of each target controller corresponding to the changed function, the function version corresponding to the changed function and the versions of each controller in the version function identifier correspondence are updated; For each newly added function, according to each target controller corresponding to the newly added function and the target version of each target controller, the function version corresponding to the newly added function, each controller and each controller version are added to the version function identifier correspondence relationship.

4. The method according to claim 1, characterized in that Before receiving the version upgrade package sent by the remote upgrade platform, the method further includes: For each vehicle, determining each controller corresponding to the vehicle and an installation version of each controller according to configuration information corresponding to the vehicle; Determine a single vehicle function corresponding to the vehicle from a function permission library according to a pre-stored version function identification correspondence, each controller and an installation version of each controller; According to the bicycle function, an initial function identifier set displayed on the mobile terminal display interface is determined.

5. The method according to claim 1, characterized in that The receiving the current version of each controller corresponding to the vehicle includes: Based on the public network, receiving the current version of each controller corresponding to the vehicle sent by the remote upgrade platform; or, Based on a private network, current versions of each controller corresponding to the vehicle sent by the vehicle are received.

6. The method according to claim 1, characterized in that The determining of function update information according to the current version of each controller, the corresponding relationship between the version function identifiers, and the function identifier set currently displayed on the mobile terminal display interface includes: Determine a target function identifier set displayed on the mobile terminal display interface according to the current version of each controller and the corresponding relationship between the version function identifiers; Function update information is determined according to the function identifier set currently displayed on the mobile terminal display interface and the target function identifier set.

7. The method according to claim 1, characterized in that The step of determining an update instruction for the mobile application according to the mobile application version and the function update information includes: Determine, according to the mobile application version, supported functions corresponding to the mobile application version and function versions corresponding to each supported function; In response to the supported functions not including at least one function in the function update information, determining that the update instruction of the mobile application is a reminder upgrade instruction; In response to each supported function including each function in the function update information, determining whether a function version of each function in the function update information is the same as a function version of each supported function; If they are the same, determining that the update instruction of the mobile application is a function display update instruction; If they are not the same, it is determined that the update instruction of the mobile application is a reminder upgrade instruction.

8. A linkage update device, characterized in that: Configured on the Internet of Vehicles platform, including: An information determination module is used to receive a version upgrade package sent by a remote upgrade platform, parse the version upgrade package, and determine the upgrade information corresponding to the version upgrade package; A correspondence determination module, used to update the version function identifier correspondence according to the upgrade information; wherein the version function identifier correspondence is the correspondence between the vehicle function identifier and the controller version; A function change determination module is used to receive, for each vehicle, the current version of each controller corresponding to the vehicle and the mobile application version of the mobile terminal, and determine the function update information according to the current version of each controller, the corresponding relationship between the version function identifiers, and the function identifier set currently displayed on the display interface of the mobile terminal; The mobile application update module is used to determine the update instruction of the mobile application according to the mobile application version and the function update information, and send the update instruction to the mobile application to update the function identifier set in the mobile terminal display interface.

9. A vehicle networking platform, 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 linkage update method according to any one of claims 1 to 7 is implemented.

10. A linkage update system, characterized in that: include: A remote upgrade platform, a vehicle networking platform as claimed in claim 9, at least one vehicle and a mobile application corresponding to each vehicle; wherein, The remote upgrade platform is used to send the version upgrade package to the vehicle networking platform; receive the controller upgrade results sent by each vehicle, and update the controller version corresponding to each vehicle according to the controller upgrade results; The vehicle is configured to receive a version upgrade package sent by the remote upgrade platform, perform an upgrade based on the version upgrade package, determine an upgrade result, and send the upgrade result to the remote upgrade platform; The mobile application corresponding to each vehicle is used to receive and respond to the update instruction.

Images