Vehicle cloud service synchronization method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a vehicle cloud service synchronization method and device, electronic equipment and a storage medium, the method is applied to a vehicle end, and the method comprises the steps that a baseline configuration table of the vehicle end is acquired from a cloud end through a first communication protocol, and the baseline configuration table comprises a plurality of first service applications suitable for being installed on the vehicle end; determining a plurality of second service applications installed in the vehicle end, and determining at least one differential service application of the vehicle end based on the plurality of first service applications and the plurality of second service applications; obtaining each file data packet corresponding to each differential service application from the cloud through a second communication protocol of which the transmission bandwidth is greater than that of the first communication protocol; and performing verification processing on each file data packet of each differential service application, and installing the successfully verified differential service application to a vehicle end. Through the vehicle cloud service synchronization scheme, the accuracy and reliability of vehicle cloud service synchronization processing can be improved, and the data synchronization efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a vehicle-to-cloud service synchronization method, apparatus, electronic device, and storage medium. Background Technology

[0002] In current technology, both the vehicle and cloud terminals use the lightweight MQTT protocol to exchange commands and synchronize configuration table data. However, the MQTT protocol, as a lightweight protocol, suffers from several drawbacks when transmitting files. Large messages can easily lead to transmission interruptions, and in low-bandwidth network environments, it can cause network congestion, latency, and significant bandwidth consumption.

[0003] As SOA development capabilities continue to expand, the number of service applications and library files that SOA application development relies on gradually increases, leading to a greater demand for interaction between vehicle-cloud service applications. In such scenarios, excessively long message transmissions via the MQTT protocol can exceed the protocol's traffic limit. At the same time, the retry mechanism can cause the traffic to remain under high load for a period of time, resulting in significant traffic consumption. Furthermore, MQTT transmission interruptions can cause vehicle-cloud synchronization failures, affecting the normal invocation of service-related functions. Summary of the Invention

[0004] In view of this, embodiments of this application provide a vehicle-to-cloud service synchronization solution to at least partially solve the above-mentioned problems.

[0005] According to a first aspect of the embodiments of this application, a vehicle-to-cloud service synchronization method is provided, applied to a vehicle, comprising: obtaining a baseline configuration table of the vehicle from the cloud via a first communication protocol, wherein the baseline configuration table includes a plurality of first service applications suitable for installation on the vehicle; determining a plurality of second service applications installed on the vehicle, and determining at least one differential service application on the vehicle based on the plurality of first service applications and the plurality of second service applications; obtaining file data packets corresponding to each differential service application from the cloud via a second communication protocol, wherein the transmission bandwidth of the second communication protocol is greater than the transmission bandwidth of the first communication protocol; performing verification processing on each file data packet of each differential service application, and installing the successfully verified differential service application to the vehicle.

[0006] According to a second aspect of the embodiments of this application, a vehicle-to-cloud service synchronization device is provided, applied to a vehicle, comprising: a first acquisition module, configured to acquire a baseline configuration table of the vehicle from the cloud via a first communication protocol, wherein the baseline configuration table includes a plurality of first service applications suitable for installation on the vehicle; an analysis module, configured to determine a plurality of second service applications installed on the vehicle, and based on the plurality of first service applications and the plurality of second service applications, determine at least one differential service application on the vehicle; a second acquisition module, configured to acquire file data packets corresponding to each differential service application from the cloud via a second communication protocol, wherein the transmission bandwidth of the second communication protocol is greater than the transmission bandwidth of the first communication protocol; and an installation module, configured to perform verification processing on each file data packet of each differential service application, and install the successfully verified differential service application to the vehicle.

[0007] According to a third aspect of the embodiments of this application, an electronic device is provided, including: a processor and a memory storing a program, wherein the program includes instructions that, when executed by the processor, cause the processor to perform the vehicle-to-cloud service synchronization method as described in the first aspect.

[0008] According to a fourth aspect of the embodiments of this application, a computer storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the vehicle-cloud service synchronization method as described in the first aspect.

[0009] In summary, the embodiments of this application, by combining a first communication protocol and a second communication protocol with different transmission bandwidths, and through vehicle-cloud collaboration, ensure the consistency of vehicle-cloud services without increasing channel costs, even when vehicle services are frequently updated or the mounted services change significantly. This solves the problems of network congestion, latency, and high traffic consumption caused by vehicle-cloud service synchronization in the prior art, and reduces resource consumption during vehicle-cloud service synchronization to a certain extent. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0011] Figure 1 The diagram shown is a flowchart of the method for synchronizing cloud services for a single vehicle according to this application;

[0012] Figure 2 The diagram shown is a partial flowchart of the one-vehicle-to-cloud synchronization method according to this application;

[0013] Figure 3 The diagram shown is a partial data processing flowchart according to an embodiment of this application;

[0014] Figure 4 The diagram shown is a partial data processing flowchart according to an embodiment of this application;

[0015] Figure 5 The diagram shown is a structural block diagram of a vehicle-to-cloud service synchronization device according to an embodiment of this application.

[0016] Figure 6 The diagram shown is a structural schematic of an electronic device according to an embodiment of this application;

[0017] Figure 7 The diagram shown is a flowchart illustrating the synchronization process of the vehicle cloud service according to this application. Detailed Implementation

[0018] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of this application.

[0019] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0020] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc., used in this disclosure are only used to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0021] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative and not restrictive. Those skilled in the art should understand that, unless explicitly stated in the context, they should be understood as "one or more". The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0022] Existing vehicle-to-cloud (V2X) service synchronization methods struggle to provide stable and convenient data transmission services when faced with increasing file transfer demands. Therefore, this application provides a V2X service synchronization method, the specific implementation of which will be described in detail below with reference to the accompanying drawings.

[0023] For example, Figure 1 The diagram shown is a flowchart of the method for synchronizing cloud services for a vehicle according to this application, which mainly includes the following steps:

[0024] The S100 obtains the vehicle's baseline configuration table from the cloud via the first communication protocol.

[0025] In some embodiments, the first communication protocol is the MQTT protocol.

[0026] In one implementation of S100, the vehicle can send a baseline synchronization request containing vehicle identification information to the cloud via a first communication protocol. The cloud can determine the current baseline to which the vehicle belongs based on the vehicle identification information and return the URL address of the latest baseline configuration table to the vehicle via the first communication protocol. The baseline configuration table contains multiple first service applications adapted to the vehicle, including but not limited to: vehicle air conditioning service application, vehicle intelligent driving service application, vehicle seat service application, vehicle multimedia service application, etc.

[0027] In some embodiments, the baseline configuration table includes, but is not limited to, any combination of one or more of the following parameters: each first service application contained in the baseline configuration table, version information corresponding to each first service application, unified resource locator, and data checksum of file data packets corresponding to each vehicle-side service application.

[0028] Specifically, in some practical applications, available resources on the Internet can be represented by simple strings, which are called "Uniform Resource Locators" (URLs). The purpose of a URL is to identify information resources on the Internet and uniformly address the services provided by the Internet. Through URLs, one can directly search for corresponding files, databases, and images on the network.

[0029] In some embodiments, the data checksum includes an MD5 checksum to ensure the integrity and consistency of information transmission.

[0030] For example, in order to prevent data packet loss during the vehicle-to-cloud service synchronization process and improve data transmission security, the consistency between the transmitted and received files can be ensured by verifying whether the MD5 codes of the transmitted and received files are consistent.

[0031] Specifically, during the vehicle-cloud service synchronization process, if the MD5 code of any local vehicle service file pointed to by any vehicle service is different from the MD5 code of the corresponding service file in the baseline configuration table, a verification result indicating that the transmitted file and the received file are inconsistent can be obtained.

[0032] In some embodiments, vehicle identification information includes, but is not limited to, the Vehicle Identification Number (VIN). Typically, the VIN consists of 17 characters and is determined according to national vehicle management standards, containing information such as the vehicle's manufacturer, year, model, body style and code, engine code, and assembly location.

[0033] Figure 2 The diagram shown is a partial flowchart of a vehicle-to-cloud synchronization method according to this application. It can be implemented by executing... Figure 2 The processing flow shown is used to retrieve the latest baseline configuration table of the vehicle from the cloud based on vehicle information:

[0034] S200: The vehicle sends vehicle identification information (VIN code) to the cloud.

[0035] S210, the vehicle obtains the storage URL of the baseline configuration table corresponding to the vehicle identification information. Specifically, the vehicle obtains the URL of the latest baseline configuration table of the vehicle through the first communication protocol.

[0036] In some embodiments, the first communication protocol is the MQTT protocol.

[0037] S220, the vehicle accesses the storage URL to obtain the latest baseline configuration table.

[0038] Specifically, in S220, the vehicle downloads the latest baseline configuration table of the vehicle from the cloud via the second communication protocol by accessing the URL of the latest baseline configuration table of the vehicle obtained from S210.

[0039] In some embodiments, the second communication protocol is the HTTP protocol. In some embodiments, the HTTP protocol is the HTTPS protocol.

[0040] In one embodiment, the baseline configuration table corresponding to the vehicle identification information is obtained by accessing the storage URL in S210, and is downloaded in S220. The downloaded baseline configuration table is saved to the first folder and named "local temporary folder".

[0041] Furthermore, in some embodiments, in S220, the latest baseline configuration table obtained by the vehicle is stored in a local temporary folder on the vehicle for easy retrieval in subsequent processes.

[0042] S110 identifies multiple secondary service applications installed in the vehicle.

[0043] In some embodiments, the second service application is a service application that is currently installed in the vehicle system and is running in the vehicle.

[0044] In some embodiments, the second service applications installed in the vehicle may include, but are not limited to: vehicle air conditioning service application, vehicle intelligent driving service application, vehicle seat service application, vehicle multimedia service application, etc.

[0045] S120, based on multiple first service applications and multiple second service applications, determines at least one differentiated service application on the vehicle side.

[0046] For example, Figure 3 The diagram shown is a partial data processing flowchart according to an embodiment of this application, which involves executing the following steps: Figure 3 The processing flow shown is used to determine at least one different service application on the vehicle based on the version information of the service application.

[0047] In one implementation of S120, the electronic device executes... Figure 3 The steps shown below determine at least one differential service application on the vehicle side.

[0048] S300: Extract the first file version information of each first service application from the baseline configuration table, and extract the second file version information of each second service application on the vehicle side.

[0049] Specifically, the second file version information includes, but is not limited to, the version number of any local vehicle service file pointed to by any vehicle service application, for example, seat adjustment 1.0 / or A1 version, seat adjustment 2.0 / or A2 version, etc.

[0050] S310: Compare the first file version information of each first service application in the baseline configuration table with the second file version information of each second service application in the vehicle. If they are consistent, proceed to step S320 to end vehicle-cloud synchronization. If they are inconsistent, proceed to step S330 to determine at least one different service application in the vehicle.

[0051] For example, when both the first and second service applications point to the "Vehicle Seat Adjustment Service Application," if the first file version information is "1.0 / or A1 version" and the second file version information is "2.0 / or A2 version," it indicates that the first file version information and the second file version information are inconsistent. In this case, the "Vehicle Seat Adjustment Service Application" is identified as a differing service application, and an updatable version of the "Vehicle Seat Adjustment Service Application" exists. If the first file version information is "1.0 / or A1 version" and the second file version information is also "1.0 / or A1 version," it indicates that the first file version information and the second file version information are consistent, and an updatable version of the "Vehicle Seat Adjustment Service Application" does not exist.

[0052] S130 obtains file data packets corresponding to various service applications from the cloud via the second communication protocol.

[0053] Figure 4 The diagram shown is a partial data processing flowchart according to an embodiment of this application, which can be executed... Figure 4 The processing steps shown enable vehicle-to-cloud service updates for at least one differentiated service application:

[0054] S400 identifies any differential service application as the current service application.

[0055] Specifically, in S400, any one of the differential service applications determined in S310 is taken as the current service application.

[0056] The S410 obtains the file data packets corresponding to the current service application from the cloud through the second communication protocol.

[0057] Specifically, in some embodiments, in S410, the data packet corresponding to the current service application determined in S400 is obtained from the cloud via a second communication protocol.

[0058] Furthermore, in some embodiments, the second communication protocol is the HTTP protocol; more specifically, in some embodiments, the HTTP protocol is the HTTPS protocol.

[0059] Furthermore, in some embodiments, in S410, the acquired file data packets corresponding to the current service application are stored in a local temporary folder for easy retrieval in subsequent processes.

[0060] Specifically, the data packet corresponding to the current service application identified in S400 is obtained from the cloud via the HTTPS protocol. After the data packet corresponding to the current service application is downloaded, a download completion feedback message is sent to the cloud via the first communication protocol. Understandably, if the download fails, a download failure feedback message is sent to the cloud via the first communication protocol.

[0061] Furthermore, in some embodiments, the first communication protocol is the MQTT protocol.

[0062] S140 verifies the file data packets of each differential service application and installs the successfully verified differential service applications to the vehicle.

[0063] S420 performs verification processing on each file data packet of the current service application.

[0064] S430: Compare the reference data check code of the current service application with the actual data check code. If they match, proceed to step S460 to install the different service application on the vehicle. Otherwise, proceed to step S440 to determine whether the current download count exceeds the duplicate download threshold.

[0065] Specifically, based on the file data packets corresponding to the current service application obtained in S410, an actual data checksum for the current service application is generated. Based on the baseline configuration table stored in the local temporary folder in S220, a reference data checksum for the current service application is extracted. The actual data checksum and the reference data checksum are compared to see if they match, and the execution result is output based on the comparison result.

[0066] Optionally, in one embodiment, the data check code is determined to be an MD5 code.

[0067] Specifically, in S440, it is determined whether the current download count exceeds the repeated download threshold. If the determination result is yes, then S450 is executed to send the execution result of the current service application's file data packet download failure to the cloud. Otherwise, step S410 is executed. When the number of repeated loop executions in S410 to S440 exceeds the repeated download threshold in S450, it is determined that the loop execution process ends, and step S450 is executed to send the execution result of the current service application's file data packet download failure to the cloud.

[0068] Furthermore, in S430, if the reference data checksum of the current service application is inconsistent with the actual data checksum, the exception handling mechanism is activated to execute step S440, and S410 to S430 are executed repeatedly in a loop. If step S410 is not being executed for the first time, the actual data checksum of the current service application in the current temporary folder is traversed and compared with the reference data checksum. The comparison result is used as a heuristic condition for the non-first execution of S410. If a consistent comparison result exists, S410 is not executed in the current temporary folder; otherwise, S410 is executed.

[0069] Furthermore, in the S450, the vehicle sends the execution result of the failure to download the file data package of the current service application to the cloud through the first communication protocol. After receiving the execution result of the failure to download, the cloud replies to the vehicle through the first communication protocol to ensure that the information between the vehicle and the cloud is consistent.

[0070] Furthermore, in some embodiments, the first communication protocol is the MQTT protocol.

[0071] Understandably, in the S450, before installing the differentiated service application on the vehicle, the vehicle sends the result of the successful download of the file data package of the current service application to the cloud via the MQTT protocol. After receiving the successful download result, the cloud replies to the vehicle via MQTT to ensure that the information between the vehicle and the cloud is consistent.

[0072] After confirming that the information between the vehicle and the cloud is consistent, S460 is executed using the data file packages corresponding to each differentiated service application in the local temporary folder to install the differentiated service application.

[0073] Figure 5 The figure shown is a structural block diagram of a vehicle-to-cloud service synchronization device according to an embodiment of this application. As shown, the vehicle-to-cloud service synchronization device 500 of this embodiment includes:

[0074] The first acquisition module 502 is used to acquire the baseline configuration table of the vehicle from the cloud through a first communication protocol, wherein the baseline configuration table includes a plurality of first service applications suitable for installation on the vehicle.

[0075] Analysis module 504 is used to determine multiple second service applications installed in the vehicle terminal, and based on the multiple first service applications and the multiple second service applications, to determine at least one differential service application in the vehicle terminal;

[0076] The second acquisition module 506 is used to acquire file data packets corresponding to each different service application from the cloud through a second communication protocol, wherein the transmission bandwidth of the second communication protocol is greater than the transmission bandwidth of the first communication protocol.

[0077] The installation module 508 is used to verify the file data packets of each differential service application and install the successfully verified differential service applications to the vehicle terminal.

[0078] Figure 6 The diagram shown is a structural schematic of an electronic device according to an embodiment of this application. The specific embodiments of this application do not limit the specific implementation of the electronic device.

[0079] like Figure 6As shown, the electronic device may include: a processor 602, a communications interface 604, a memory 606, and a communications bus 608.

[0080] in:

[0081] The processor 602, communication interface 604, and memory 606 communicate with each other via communication bus 608.

[0082] Communication interface 604 is used for communication with other electronic devices or servers.

[0083] The processor 602 is used to execute program 610, specifically to execute the relevant steps in the above-described vehicle-cloud service synchronization method embodiment.

[0084] Specifically, program 610 may include program code that includes computer operation instructions.

[0085] The processor 602 may be a CPU, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The smart device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0086] Memory 606 is used to store program 610. Memory 606 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0087] Program 610 may include multiple computer instructions. Specifically, program 610 may use multiple computer instructions to cause processor 602 to perform the operations corresponding to the vehicle-cloud service synchronization method described in any of the foregoing multiple method embodiments.

[0088] The specific implementation of each step in program 610 can be found in the corresponding steps and units described in the above method embodiments, and has corresponding beneficial effects, which will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the foregoing method embodiments, and will not be repeated here.

[0089] Figure 7 The diagram shown is a flowchart illustrating the synchronization process of the vehicle cloud service according to this application.

[0090] In one embodiment, see Figure 7 The example illustrates part of the information interaction process between the vehicle and the cloud using the method described in this application. It includes a first communication protocol and a second communication protocol represented by a dashed line. It should be clearly stated that the transmission bandwidth of the second communication protocol is greater than that of the first communication protocol.

[0091] In some embodiments, the first communication protocol includes the MQTT communication protocol, and the second communication protocol includes the HTTP communication protocol.

[0092] More specifically, in some embodiments, the HTTP communication protocol is the HTTPS protocol.

[0093] For example, when the vehicle initiates vehicle-to-cloud service synchronization, thread S1 is started. The vehicle sends a baseline request message to the cloud via a first communication protocol. The cloud returns the address of the vehicle's latest baseline configuration table via the first communication protocol. The vehicle processes the information obtained by thread S1 and further starts thread S2. The vehicle accesses the address of the latest baseline configuration table obtained in S1 via a second communication protocol and downloads it to a local first folder, named "local temporary folder" (hereinafter referred to as the local temporary folder). The cloud returns the vehicle's latest baseline configuration table via the second communication protocol. The vehicle compares the installed baseline configuration table with the latest baseline configuration table in the local temporary folder. If the baselines match, no download is needed, and the vehicle-to-cloud synchronization service ends. Otherwise, at least one differential application service is obtained based on the comparison result, and thread S3 is started. The vehicle downloads the data file packages corresponding to each differential service application from the cloud via the second communication protocol and stores them in the local temporary folder. The download result is then fed back to the cloud via the first communication protocol. When the cloud receives confirmation that all data file packages corresponding to each differential service application have been successfully downloaded, the reference data checksum of the current service application is compared with... If the actual data verification codes match, the vehicle will install the differentiated service application and replace the local temporary folder with the local folder, overwriting the original local folder. If the reference data verification codes of each differentiated service application obtained by the cloud do not match the actual data verification codes, the vehicle will send a message to the cloud via the first communication protocol indicating that at least one data file package download failed. Further, thread S4 will be entered, activating the exception handling mechanism. The vehicle will repeatedly execute thread S3. If thread S3 is not executed for the first time, the actual data verification codes of the current service application in the current temporary folder will be traversed and compared with the reference data verification codes. The comparison result will be used as the heuristic condition for the non-first execution of thread S4. If there is a matching result, thread S4 will not be executed for the current temporary folder. If there is no matching result, thread S4 will be executed until the cloud receives download feedback that all data file packages corresponding to each differentiated service application have been successfully downloaded, and the reference data verification codes of the current service application match the actual data verification codes. Then, the vehicle will install the differentiated service application and replace the local temporary folder with the local folder, overwriting the original local folder, to ensure that the information between the vehicle and the cloud is consistent.

[0094] Furthermore, proceeding to thread S5, in one embodiment, the vehicle sends a "Update complete" message (or other message content, to inform the cloud that all data file packages of each different service application have been downloaded and installed on the vehicle) to the cloud via the first communication protocol, and the cloud responds to the vehicle via the first protocol.

[0095] This application also provides a computer program product, including computer instructions that instruct a computing device to perform an operation corresponding to any of the vehicle-cloud service synchronization methods in the above-described multiple method embodiments.

[0096] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this application can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this application.

[0097] The methods described in the embodiments of this application can be implemented in hardware, firmware, or as software or computer code that can be stored in a recording medium (such as a CD-ROM, RAM, floppy disk, hard disk, or magneto-optical disk), or as computer code downloaded over a network that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium. Thus, the methods described herein can be stored on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an ASIC or FPGA) for such software processing. It is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., RAM, ROM, flash memory, etc.) capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the checksum generation method described herein is implemented. Furthermore, when a general-purpose computer accesses code used to implement the checksum generation method shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for executing the checksum generation method shown herein.

[0098] Those skilled in the art will recognize that the units and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0099] The above embodiments are only used to illustrate the embodiments of this application, and are not intended to limit the embodiments of this application. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of this application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of this application, and the patent protection scope of the embodiments of this application should be defined by the claims.

Claims

1. A method for synchronizing a vehicle cloud service, applied to a vehicle side, characterized in that, The method comprises: obtaining a baseline configuration table of the vehicle terminal from the cloud through a first communication protocol, wherein the baseline configuration table comprises a plurality of first service applications suitable for being installed in the vehicle terminal; determining a plurality of second service applications installed in the vehicle terminal, and determining at least one difference service application of the vehicle terminal based on the plurality of first service applications and the plurality of second service applications; obtaining a file data packet corresponding to each difference service application from the cloud through a second communication protocol, wherein the transmission bandwidth of the second communication protocol is greater than that of the first communication protocol; performing verification processing on the file data packet of each difference service application, and installing the difference service application with successful verification to the vehicle terminal.

2. The method of claim 1, wherein, The method further comprises: sending vehicle identification information of the vehicle terminal to the cloud; obtaining a storage address of the baseline configuration table corresponding to the vehicle identification information from the cloud; accessing the storage address to obtain the baseline configuration table of the vehicle terminal.

3. The method of claim 1, wherein, The baseline configuration table comprises first file version information of each first service application, and each second service application installed in the vehicle terminal has second file version information; The method further comprises: matching the first file version information of each first service application with the second file version information of each second service application, and determining each first service application corresponding to each first file version information that does not match the second file version information as a difference service application of the vehicle terminal.

4. The method of claim 3, wherein, The baseline configuration table comprises a download address and a reference data verification code of each first service application. The method further comprises: for any one current service application in each difference service application, downloading a file data packet of the current service application from the cloud based on the download address of the current service application in the baseline configuration table, and generating an actual data verification code of the current service application based on the data download result of the file data packet of the current service application; The method further comprises: performing consistency verification based on the reference data verification code and the actual data verification code of the current service application, obtaining a verification result that the current service application is successfully verified if the reference data verification code and the actual data verification code of the current service application are consistent, and obtaining a verification result that the current service application is not successfully verified if the reference data verification code and the actual data verification code of the current service application are inconsistent.

5. The method of claim 4, wherein, The method further comprises: in response to the verification result of the current service application being unsuccessful, repeatedly downloading the file data package of the current service application by repeatedly performing the step of downloading the file data package of the current service application from the cloud based on the data download address of the current service application in the baseline configuration table until the number of repeated downloads of the file data package of the current service application exceeds a repeated download threshold; in response to the detection result that the number of repeated downloads of the file data package of the current service application exceeds the repeated download threshold, sending, to the cloud, an execution result of the file data package of the current service application failing to be downloaded by the first communication protocol.

6. The method of claim 1, wherein, After the step of installing the difference service application whose verification is successful to the vehicle end, the method further comprises: sending, to the cloud, an execution result of the difference service application being successfully installed by the first communication protocol.

7. The method of claim 1, wherein the first communication protocol comprises an MQTT communication protocol; the second communication protocol comprises an HTTP communication protocol. 8.A vehicle cloud service synchronization apparatus, applied to a vehicle end, and having the characteristics that, The apparatus comprises: a first obtaining module configured to obtain, from the cloud, a baseline configuration table of the vehicle end by a first communication protocol, wherein the baseline configuration table comprises a plurality of first service applications suitable for being installed in the vehicle end; an analysis module configured to determine a plurality of second service applications installed in the vehicle end, and determine at least one difference service application of the vehicle end based on the plurality of first service applications and the plurality of second service applications; a second obtaining module configured to obtain, from the cloud, a plurality of file data packages corresponding to the difference service applications by a second communication protocol, wherein a transmission bandwidth of the second communication protocol is greater than a transmission bandwidth of the first communication protocol; an installation module configured to perform verification processing on the plurality of file data packages of the difference service applications, and install the difference service applications whose verification is successful to the vehicle end.

9. An electronic device comprising: a processor; and a memory storing programs, wherein the programs include instructions that, when executed by the processor, cause the processor to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer program is stored in the computer readable storage medium, and when the computer program runs on the computer, the computer executes the method of any one of claims 1-7.

Images