Method for synchronizing vehicle state data and related device

Abstract

The application discloses a kind of synchronization method of vehicle state data and related equipment, it is related to vehicle network connection technical field, mainly for solving the defect that vehicle state synchronization method exists data transmission redundancy causes when network exception, vehicle cloud state is extremely easy to be inconsistent.The method comprises: obtaining vehicle end verification code based on vehicle end controller, wherein the vehicle end verification code is the unique identifier generated based on the vehicle end state data of the reservation scene acquired in real time;Target verification code is obtained based on user end, wherein the target verification code is the unique identifier generated based on the target state data of the reservation scene input by user;In the case where the vehicle end verification code and the target verification code are inconsistent, synchronization operation is executed based on the feedback information of user.The application is used for the synchronization process of vehicle state data.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a method and related equipment for synchronizing vehicle status data. Background Technology

[0002] In current remote control systems for intelligent connected vehicles, the common practice for synchronizing vehicle status is as follows: when a user sets a reservation scenario via a mobile application, including approximately thirty parameters such as air conditioning, seat heating, and steering wheel heating, detailed data of all status parameters for that scenario must be uploaded to the cloud, and then forwarded by the cloud to the vehicle controller for execution. To enable the application interface to display the vehicle's real-time status, the vehicle controller also needs to report the same massive full status data packet to the cloud frequently (e.g., once per second). This mechanism of real-time synchronization based on complete status detail data packets has several drawbacks. Firstly, each synchronization interaction transmits data containing numerous fields over the network channel, resulting in significant data transmission redundancy, continuously consuming network bandwidth and depleting terminal and cloud resources. On the other hand, this mechanism is particularly vulnerable to common anomalies such as unstable or interrupted mobile network signals or failure to establish a connection during the initial vehicle startup. Any failure or delay in data packet transmission will directly cause a deviation between the preset state displayed on the mobile terminal and the actual operating state of the vehicle. Furthermore, the system lacks the ability to quickly and easily detect and repair these discrepancies, making it easy for the vehicle cloud state to fall into and remain inconsistent when the network is abnormal, which severely restricts the reliability of the remote control function and the user experience. Summary of the Invention

[0003] In view of the above problems, the present invention provides a method and related equipment for synchronizing vehicle status data. The main purpose is to solve the defect of the vehicle status synchronization method having data transmission redundancy, which makes the vehicle-cloud status very easy to be inconsistent when the network is abnormal.

[0004] To address at least one of the aforementioned technical problems, in a first aspect, the present invention provides a method for synchronizing vehicle status data, the method comprising: The vehicle terminal verification code is obtained based on the vehicle terminal controller, wherein the vehicle terminal verification code is a unique identifier generated based on the real-time acquired vehicle terminal status data of the reservation scenario; The target verification code is obtained based on the user terminal, wherein the target verification code is a unique identifier generated based on the target status data of the reservation scenario input by the user; If the vehicle-side verification code and the target verification code are inconsistent, a synchronization operation is performed based on the user's feedback information.

[0005] Optionally, the above methods also include: Initial state data is set for different reservation scenarios based on the user's client; Generate a verification code for each reservation scenario; Each reservation scenario and the corresponding verification code are sent to the vehicle controller to form the initial reservation scenario of the vehicle controller. If the reservation scenario changes, the vehicle verification code is updated based on the real-time acquired vehicle status data.

[0006] Optionally, the above methods also include: The status data of the reservation scenario are concatenated into a string based on a preset order; The string is used to generate a verification code using a preset algorithm.

[0007] Optionally, obtaining the vehicle verification code based on the vehicle controller includes: The on / off status of each reservation scenario and the vehicle-side verification code for each reservation scenario are obtained in real time based on the vehicle-side controller at a preset frequency.

[0008] Optionally, obtaining the target verification code based on the user terminal includes: When a user logs in on the client side, the target verification code is obtained based on the client side's login information.

[0009] Optionally, the step of performing a synchronization operation based on user feedback when the vehicle-side verification code and the target verification code are inconsistent includes: When the user is logged in, obtain the comparison result between the vehicle-side verification code and the target verification code; If the comparison results are inconsistent, a query message is sent to the user, wherein the query message is used to obtain the user's feedback on their willingness to resynchronize; The synchronization operation is performed based on the feedback information.

[0010] Optionally, performing the synchronization operation based on the feedback information includes: If the feedback information indicates resynchronization, the target status data of the reservation scenario and the target verification code will be sent to the vehicle controller.

[0011] Secondly, embodiments of the present invention also provide a vehicle status data synchronization device, comprising: The first acquisition unit is used to acquire a vehicle terminal verification code based on the vehicle terminal controller, wherein the vehicle terminal verification code is a unique identifier generated based on the vehicle terminal status data of the reservation scenario acquired in real time; The second acquisition unit is used to acquire a target verification code based on the user terminal, wherein the target verification code is a unique identifier generated based on the target status data of the reservation scenario input by the user; An execution unit is used to perform a synchronization operation based on user feedback information when the vehicle-side verification code and the target verification code are inconsistent.

[0012] To achieve the above objectives, according to a third aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium comprising a stored program, wherein, when the program is executed by a processor, the steps of the above-described method for synchronizing vehicle state data are implemented.

[0013] To achieve the above objectives, according to a fourth aspect of the present invention, an electronic device is provided, comprising at least one processor and at least one memory connected to the processor; wherein the processor is configured to invoke program instructions in the memory to execute the steps of the vehicle state data synchronization method described above.

[0014] By employing the above technical solution, the vehicle status data synchronization method and related equipment provided by this invention address the drawback of traditional vehicle status synchronization methods where data transmission redundancy leads to inconsistencies in vehicle-cloud status during network anomalies. This invention addresses this by obtaining a vehicle-side verification code based on the vehicle controller, where the verification code is a unique identifier generated from real-time acquired vehicle-side status data for the reservation scenario; and obtaining a target verification code based on the user terminal, where the target verification code is a unique identifier generated from target status data for the reservation scenario input by the user. In cases where the vehicle-side verification code and the target verification code are inconsistent, a synchronization operation is performed based on user feedback. In this solution, firstly, the large amount of status data to be synchronized is converted into concise, unique verification codes for transmission and comparison, replacing the direct synchronization of all status details, thus reducing the amount of data generated by periodic status synchronization. Secondly, by comparing the two verification codes representing the actual vehicle status and the user-preset status, discrepancies between the two states are detected, providing a clear basis for detecting synchronization anomalies. Finally, upon detecting inconsistency, user feedback is introduced as a decision condition for performing synchronization operations. This makes subsequent synchronization actions more targeted and controllable, guiding the system from the detected inconsistency state to a consistent state. Ultimately, this significantly reduces the amount of data transmitted during periodic synchronization while ensuring vehicle-cloud state consistency, and improves the detectability and repairability of state asynchrony issues caused by network anomalies.

[0015] Correspondingly, the vehicle status data synchronization device, equipment, and computer-readable storage medium provided in the embodiments of the present invention also have the above-mentioned technical effects.

[0016] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart illustrating a method for synchronizing vehicle status data according to an embodiment of the present invention is shown; Figure 2 This diagram illustrates a schematic block diagram of a vehicle status data synchronization device provided in an embodiment of the present invention. Figure 3 A schematic block diagram of a vehicle status data synchronization electronic device provided in an embodiment of the present invention is shown. Detailed Implementation

[0018] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0019] To address the drawback of data transmission redundancy in vehicle status synchronization methods, which easily leads to inconsistencies between vehicle and cloud states during network anomalies, this invention provides a method for synchronizing vehicle status data, such as... Figure 1 As shown, the method includes: S101. Obtain the vehicle terminal verification code based on the vehicle terminal controller, wherein the vehicle terminal verification code is a unique identifier generated based on the real-time acquired vehicle terminal status data of the reservation scenario; For example, the aforementioned vehicle-side controller refers to the control unit in the vehicle used to control and manage functions related to reservation scenarios. The vehicle-side verification code is a fixed-length code generated by a specific algorithm, serving as a unique representative of a specific set of data. A reservation scenario refers to a complete set of function settings predefined and named by the user through the user terminal; each reservation scenario contains a complete set of status data for all its functional items. Vehicle-side status data refers to the real-time parameter values ​​of all functional items within that reservation scenario, obtained by the vehicle-side controller at a given moment.

[0020] In this embodiment, obtaining the vehicle-side verification code based on the vehicle-side controller refers to the vehicle-side controller actively collecting real-time status data of all currently active reservation scenarios within its internal system at preset time intervals. For each reservation scenario, the vehicle-side controller combines the real-time parameter values ​​of its various functional items into a complete data string according to a pre-defined, uniform order. Subsequently, the vehicle-side controller processes this data string using a preset irreversible algorithm to calculate a short, highly unique code, i.e., the vehicle-side verification code. Afterward, the vehicle-side controller acquires the current on / off status of each reservation scenario along with the calculated vehicle-side verification code and prepares it for reporting. For example, for a reservation scenario named "Work Mode," its vehicle-side status data may include dozens of real-time parameters such as the air conditioning temperature being 25 degrees Celsius and the driver's seat heating level being high. The vehicle-side controller concatenates and calculates these parameters in sequence to obtain a vehicle-side verification code such as "a1b2c3d4," and simultaneously records that the scenario is in the on state, thus completing the acquisition of the vehicle-side verification code for this scenario.

[0021] Using the above technical solution, when the vehicle periodically reports its status, it does not need to transmit a detailed list of parameters for all functional items; it only needs to report a brief vehicle verification code representing its complete status and the scene on / off status. This reduces the amount of data transmitted over the network channel during each status synchronization process, thus minimizing network bandwidth usage. Furthermore, since the vehicle verification code is a unique identifier generated based on real-time status data, it reliably represents the complex actual operating status of the vehicle, providing an accurate and efficient basis for subsequent status consistency comparisons at the user end, thereby laying the foundation for discovering status differences between the vehicle and the cloud.

[0022] S102. Obtain the target verification code based on the user terminal, wherein the target verification code is a unique identifier generated based on the target status data of the reservation scenario input by the user; For example, the "user terminal" mentioned above refers to the mobile terminal application used by the user. The target verification code is a fixed-length code generated by a specific algorithm, serving as a unique representative of a specific set of data. The target status data refers to the parameter values ​​of all functional items preset by the user for the reservation scenario through the user terminal.

[0023] In this embodiment, the acquisition of the target verification code based on the user terminal occurs after the user completes the functional settings for a reservation scenario through the user terminal. Specifically, when the user inputs and confirms the target parameters for various functions in a reservation scenario on the user terminal interface, such as setting the target temperature of the air conditioner and the target level of each seat heating element, the user terminal combines all these target status data into a complete data string according to a pre-defined order. Subsequently, the user terminal processes this data string using a preset irreversible algorithm to calculate a short, highly unique code, i.e., the target verification code. After generation, the target verification code, along with the complete target status data it represents, is sent and saved to the cloud server. When status verification is required, such as after the user terminal application is launched and logged in, the user terminal will send a request to the cloud server to retrieve the previously stored target verification code corresponding to the specific reservation scenario. For example, a user presets a reservation scenario called "Going Home Mode". The user's client calculates the target verification code "e5f6g7h8" from the dozens of target status data it contains and saves it in the cloud. When the user opens the application again, the target verification code "e5f6g7h8" can be successfully retrieved from the cloud.

[0024] Using the above technical solution, the user terminal pre-calculates and obtains a target verification code representing the user's complete preset state, providing a concise credential regarding the desired state in subsequent processes. When comparing vehicle-to-cloud states, the user terminal does not need to directly process or compare a complex list of original target state data; it only needs to use this target verification code. This reduces the computational and processing resource requirements on the user terminal and makes comparing the user's preset state with the actual vehicle state more direct and efficient, creating conditions for quickly and reliably detecting discrepancies between the two states.

[0025] S103. If the vehicle-side verification code and the target verification code are inconsistent, perform a synchronization operation based on the user's feedback information.

[0026] For example, the user feedback information mentioned above refers to the explicit choice made by the user when the vehicle-side verification code and the target verification code are inconsistent, as indicated by the query information sent by the user terminal to the user interface. Synchronization operation refers to specific instructions or data clearing actions performed based on the user feedback information to ensure that the vehicle-side state matches the user's preset state.

[0027] In this embodiment, when the vehicle-side verification code and the target verification code are inconsistent, the synchronization operation based on user feedback means that when the user terminal discovers a mismatch between the two verification codes, it does not automatically take action. Instead, it first provides an interface prompt to the user, informing them that the status of the set reservation scenario is abnormal, and asking if the user is willing to resend the data. The user makes a choice based on this prompt, and their feedback is obtained by the user terminal. If the user agrees to resynchronize, the user terminal will initiate a complete instruction delivery process, resending all the target status data and corresponding target verification codes initially preset by the user in the reservation scenario to the vehicle-side controller via the cloud. The vehicle-side controller then performs function settings and verification code updates based on the received complete data, thereby overwriting the current inconsistent state. If the user disagrees to resynchronize, the user terminal will trigger another clearing process, sending a cancellation command to the cloud. The cloud then deletes the target verification code and target status data stored for the reservation scenario and notifies the vehicle-side controller to delete the corresponding reservation settings. The user terminal's interface also reverts to the state before the scenario was set. The entire process, from detecting inconsistencies and prompting the user to finally executing the specific synchronization operation, is controlled and determined by the user's explicit feedback.

[0028] By employing the aforementioned technical solution, upon detecting state inconsistencies, the decision-making power regarding the specific corrective action is delegated to the user. This ensures that subsequent synchronization operations are no longer blind or pre-defined, but rather aligned with the user's current intentions. This feedback-based mechanism makes synchronization operations more targeted and controllable, adapting to the user's actual needs in different scenarios and avoiding unnecessary network signaling and data transmission. Simultaneously, this solution provides a clear and controlled path for the system to recover from detected inconsistencies. Whether through forced state alignment via retransmission or state reset by clearing settings, the system can systematically handle state discrepancies caused by network anomalies and other reasons based on user intent, thereby improving the reliability of state synchronization management and user experience.

[0029] In one embodiment, the above method further includes: Initial state data is set for different reservation scenarios based on the user's client; Generate a verification code for each reservation scenario; Each reservation scenario and the corresponding verification code are sent to the vehicle controller to form the initial reservation scenario of the vehicle controller. If the reservation scenario changes, the vehicle verification code is updated based on the real-time acquired vehicle status data.

[0030] For example, the aforementioned initial state data refers to a set of specific parameter values ​​that the user presets for different reservation scenarios through the user terminal, which constitute the complete functional settings of the scenario.

[0031] First, users create and name multiple booking scenarios for different travel needs through the user client, and set specific parameter values ​​for all functional items under each scenario, i.e., initial state data. Next, for each booking scenario with pre-set initial state data, the user client combines all the initial state data of the scenario into a string according to a preset fixed order, and calculates a unique verification code for each booking scenario using a preset irreversible algorithm. Then, the user client packages each booking scenario, along with its corresponding complete initial state data and the generated verification code, into an instruction and sends it to the vehicle controller via the cloud server. The vehicle controller receives and stores this information, performs the corresponding functional settings preparation based on the initial state data, and associates the stored verification code, thus forming the initial version of the booking scenario within the vehicle controller. Subsequently, during actual vehicle use, once the booking scenario is triggered or the user manually adjusts the relevant functions, causing a change in the actual state of the booking scenario, the vehicle controller will recalculate and update the vehicle verification code corresponding to the booking scenario based on its latest real-time vehicle state data, according to the same algorithm and order rules as when it was generated. For example, a user sets the initial status data for "Work Mode" and generates a verification code "A1B2". This data and verification code are sent and stored in the vehicle controller. When the vehicle executes this mode, the actual air conditioning temperature may fluctuate slightly from the preset value. At this time, the vehicle controller calculates a new vehicle verification code "C3D4" based on the real-time vehicle status data containing this actual temperature, thus completing the update of the original verification code.

[0032] For example, SHA256 is a specific and widely used cryptographic hash algorithm. It transforms (or "compresses") an input of arbitrary length (i.e., a string composed of all state data of a reservation scenario concatenated in a fixed order) into a fixed-length (256-bit, usually represented as 64 hexadecimal characters) unique output code through its defined calculation process. This output code is the checksum. First, it has extremely strong collision resistance, meaning that two different sets of state data are almost impossible to produce the same SHA256 checksum, thus ensuring the reliability of the checksum as a "unique identifier." Second, it is a one-way function; it is almost impossible to deduce the original state data from the checksum result, balancing the simplicity of data representation with a certain degree of information concealment. Finally, as long as the input state data strings are exactly the same, the result of SHA256 calculation will be consistent regardless of the device (user terminal or vehicle controller). This provides a solid mathematical foundation for the consistency comparison between the vehicle checksum and the target checksum, ensuring that the comparison result truly reflects whether the underlying state data at both ends are completely consistent.

[0033] The above technical solution establishes a reliable vehicle-side data foundation and management capabilities for the entire synchronization method. By forming an initial reservation scenario on the vehicle-side controller using the user-preset complete state and its verification code, it ensures that the vehicle-side has all the basis for executing user instructions and the credentials for comparison. When the scenario changes, the vehicle-side verification code is proactively updated, enabling the vehicle-side controller to continuously and accurately reflect its latest real-time state through this verification code. This ensures the real-time and authenticity of the status identifiers subsequently reported by the vehicle-side, providing a source guarantee for effective status comparison. Furthermore, the proper storage of the initial state data sent to the vehicle-side allows it to clearly understand the specific target state to be restored when synchronization operations such as re-sending are required, improving the accuracy and efficiency of synchronization operations. The entire process enables the vehicle-side controller to autonomously maintain the states and identifiers related to the reservation scenario, laying the foundation for its participation in efficient and accurate vehicle-cloud status synchronization and collaboration.

[0034] In one embodiment, the above method further includes: The status data of the reservation scenario are concatenated into a string based on a preset order; The string is used to generate a verification code using a preset algorithm.

[0035] For example, the aforementioned preset order refers to a pre-defined and uniformly followed rule for arranging and combining the state data of the reservation scenario. The preset algorithm refers to a pre-selected deterministic computation function used to convert input data into fixed-length output code.

[0036] This application embodiment also includes the following steps. When it is necessary to generate a corresponding verification code for a reservation scenario, whether it is generating a target verification code based on the target status data input by the user or generating a vehicle-side verification code based on the vehicle-side status data obtained in real time, this unified method must be followed. First, all the status data that needs to be synchronized in the reservation scenario is obtained. This data may contain dozens of specific functional parameters. Then, strictly following the aforementioned preset order, all the status data are concatenated sequentially to form a long, continuous data string. This preset order ensures that no matter when, where, or what kind of status data is used to generate the verification code, as long as the status data is the same, the concatenated string will be completely consistent. Next, the concatenated string is input into a preset algorithm for calculation. This preset algorithm is a digest calculation function with irreversible characteristics, which can process input strings of arbitrary length and generate a code of fixed length that has a highly unique correspondence with the input data. This code is the required verification code. For example, in a reservation scenario, the status data includes parameters such as the air conditioning set temperature and the driver's seat heating level. These parameters are concatenated in a preset order to form the string "Air conditioning temperature 25 degrees Celsius, driver's seat heating high". This string is then input into a preset algorithm, and after calculation, it may output a checksum such as "x9y8z7".

[0037] By employing the aforementioned technical solution, a unified, standardized, and reliable set of calculation rules for generating checksums in the entire synchronization method is established. By forcibly specifying the concatenation order of state data, it ensures that the same set of state information will inevitably produce the same input string, eliminating the possibility of accidental identical checksums due to different data arrangements. Using a highly reliable preset algorithm, a short and highly unique identifier can be stably generated from the input string. This allows the final checksum to serve as an authoritative and reliable representative of the complex state data behind it. This method is applicable not only to generating target checksums at the user end but also to generating vehicle-side checksums at the vehicle controller, ensuring that the checksums used by both ends for comparison are generated based on identical data organization rules and calculation logic. This ensures that the consistency comparison results of the checksums can truly and accurately reflect whether the underlying state data at both ends are completely consistent, laying a solid foundation for the reliability of the entire synchronization method.

[0038] In one embodiment, obtaining the vehicle-side verification code based on the vehicle-side controller includes: The on / off status of each reservation scenario and the vehicle-side verification code for each reservation scenario are obtained in real time based on the vehicle-side controller at a preset frequency.

[0039] For example, the aforementioned preset frequency refers to a fixed time interval for the vehicle-side controller to report its execution status.

[0040] In this embodiment, obtaining the vehicle-side verification code based on the vehicle-side controller specifically includes acquiring the on / off status of each reservation scenario and the vehicle-side verification code for each reservation scenario in real time at a preset frequency. This refers to the vehicle-side controller operating at a fixed, periodic rhythm. At the end of each cycle, the vehicle-side controller will traverse and check all existing reservation scenarios within it. For each reservation scenario, the vehicle-side controller performs two operations: first, it determines and records the current overall activation status of the reservation scenario, i.e., whether it is in an on or off state; second, based on the real-time parameters of all functional items of the reservation scenario at this moment, i.e., the vehicle-side status data, it calculates and generates a vehicle-side verification code representing this latest status in real time according to a predetermined order and algorithm. Subsequently, the vehicle-side controller acquires these two pieces of information for each reservation scenario—the on / off status and the vehicle-side verification code—and prepares to send them through the vehicle network. For example, the vehicle controller performs this operation once per second. When it detects that a reservation scenario called "Home Mode" is currently running and its switch status is "On", and calculates the vehicle verification code "M8N9O0" based on real-time data such as the actual temperature of the air conditioner and the actual heating level of the seats, then the result obtained this time will include "Home Mode: On, Vehicle Verification Code M8N9O0".

[0041] Using the aforementioned technical solution, the vehicle-side controller can prepare core operational summary information for each scheduled scenario in a regular and continuous manner. Regular sampling and updating of status information are achieved through fixed-frequency triggering, ensuring the timeliness of data required for subsequent synchronization. The acquired content only includes the on / off status of the scenario and a concise checksum, without involving a complex list of original status parameters. This fundamentally creates an efficient data organization and preparation model. This model ensures that the status synchronization information sent from the vehicle remains structurally consistent and concise, providing a prerequisite for significantly reducing the amount of network data transmission during subsequent reporting. It also ensures that the provided information is sufficient to unambiguously represent the complex real-time status of the vehicle, laying a reliable data foundation for accurate status comparison at the upper layer.

[0042] In one embodiment, obtaining the target verification code based on the user terminal includes: When a user logs in on the client side, the target verification code is obtained based on the client side's login information.

[0043] For example, the above-mentioned user login refers to the process by which a user launches a mobile terminal application and successfully passes authentication to enter the application's main interface.

[0044] In this embodiment, the acquisition of the target verification code is not performed arbitrarily, but is associated with a specific and defined system event: the startup and login of the user application. When a user opens the application and completes the login process, the application enters a ready state. At this time, as part of its initialization or status check process, the user client actively sends a request to the cloud server to obtain the target verification codes corresponding to all preset reservation scenarios under the current user account. This target verification code is generated by the user client and stored in the cloud when the user successfully sets up a reservation scenario. For example, if the user previously presets a "work mode" and generated a target verification code, this code is stored in the cloud; when the user opens and logs in to the application again the next day, the application will automatically query and retrieve the target verification code for this "work mode" from the cloud, thus completing the acquisition based on the user client.

[0045] By anchoring the acquisition of the target verification code to the critical event of user login, the acquisition behavior gains clear timeliness and purpose. This ensures that every time a user starts using the application, the user's terminal can promptly and uniformly retrieve the latest authoritative credentials representing all of the user's preset states, preparing data for any subsequent vehicle-to-cloud state comparison. This approach avoids unnecessary, repetitive, or inappropriately timed remote data acquisition requests during application runtime, reducing meaningless network interactions and cloud query load. Furthermore, since the login behavior itself signifies the user's intention to use remote vehicle control functions, acquiring the target verification code at this moment best aligns with the user's actual operational context, ensuring that subsequent comparison and prompting logic are triggered and executed at the most relevant time, thereby improving the overall coherence of the state synchronization management process and the smoothness of the user experience.

[0046] In one embodiment, the step of performing a synchronization operation based on user feedback information when the vehicle-side verification code and the target verification code are inconsistent includes: When the user is logged in, obtain the comparison result between the vehicle-side verification code and the target verification code; If the comparison results are inconsistent, a query message is sent to the user, wherein the query message is used to obtain the user's feedback on their willingness to resynchronize; The synchronization operation is performed based on the feedback information.

[0047] For example, the comparison result mentioned above refers to the conclusion obtained by comparing the vehicle-side verification code with the target verification code to see if they are consistent. The solicitation information refers to the prompt content generated by the user terminal and displayed to the user when the comparison results are inconsistent, used to inquire about their willingness to perform subsequent operations. The willingness to resynchronize refers to the user's choice of whether or not to agree to perform the re-distribution operation in response to this solicitation information.

[0048] In this embodiment, when the vehicle-side verification code and the target verification code are inconsistent, a synchronization operation is performed based on user feedback. Specifically, the process includes the following: First, when the user is logged in, the user client retrieves the latest stored vehicle-side verification code and target verification code from the cloud server and directly compares these two codes to obtain a comparison result. When the comparison result clearly shows an inconsistency, the user client does not automatically perform any operation but immediately sends a specific query message to the current user interface. This query message clearly informs the user that there is an anomaly in the settings of a specific reservation scenario they are concerned about, and directly asks the user whether they are willing to re-issue the code to fix this anomaly, thereby obtaining clear feedback from the user regarding their willingness to resynchronize. The user's feedback, i.e., their choice of "agree" or "disagree" to resynchronize, is recorded by the user client. Finally, the user client will strictly trigger and execute the corresponding synchronization operation based on the obtained feedback information. For example, after the user logs into the APP, the system compares and finds that the vehicle-side verification code for "Work Mode" is different from the target verification code, and then a pop-up window appears on the APP interface prompting, "An anomaly has been found in the settings of Work Mode. Do you want to re-issue it?". If the user clicks "Yes", the feedback message will indicate that they agree to resynchronize, and the user's client will execute a synchronization operation to reissue the complete settings command; if the user clicks "No", the feedback message will indicate that they disagree, and the user's client will execute a synchronization operation to cancel the scheduled settings.

[0049] Understandably, if the user disagrees with resynchronization, the user's device will trigger a cancellation process, sending a cancellation command to the cloud. Based on this cancellation command, the cloud server will delete the target verification code and target status data stored for that reservation scenario and notify the vehicle controller to delete the corresponding reservation settings. The user's interface will also revert to its state before the scenario was set.

[0050] By employing the aforementioned technical solution, a user-centric decision-making and execution chain with clearly defined responsibilities is constructed after the core comparison stage. By performing comparisons and obtaining results only upon login, the timing of status checks is made more reasonable, avoiding unnecessary frequent background comparisons. Upon detecting inconsistencies, feedback is forcibly obtained by sending a query message to the user, giving them the decision-making power to decide whether to perform synchronization and what type of synchronization to perform. This transforms the system's response to status anomalies from a preset or automatic process into a controllable process governed by the user's real-time intentions. This approach reduces the randomness and potential conflicts of issuing commands, ensuring that every network communication and vehicle-side control initiated to correct inconsistencies is explicitly authorized by the user and consistent with their current intentions, thereby improving the humanization of status synchronization management and the overall reliability of operation.

[0051] In one embodiment, performing the synchronization operation based on the feedback information includes: If the feedback information indicates resynchronization, the target status data of the reservation scenario and the target verification code will be sent to the vehicle controller.

[0052] In this embodiment, the synchronization operation based on the feedback information specifically includes, in the case of resynchronization, sending the target state data of the reservation scenario and the target verification code to the vehicle controller. This defines the specific synchronization action triggered when the user explicitly expresses their willingness to resynchronize through a request. This process is a complete instruction sending procedure initiated immediately after the user receives confirmation. The user client will repackage the complete target state data initially preset by the user for the reservation scenario with inconsistencies, along with its uniquely corresponding target verification code, into an instruction package identical to the initial setting. This instruction package is forwarded via the cloud server and finally arrives at the vehicle controller. Upon receiving this instruction, the vehicle controller will use the complete target state data contained therein to execute the specific settings of various functions, thereby overriding the current operating state of the vehicle, and simultaneously update its locally stored corresponding verification code with the sent target verification code. For example, when a user chooses to resend the abnormal "work mode", the user terminal will resend the previously stored target status data, including all parameters such as the target temperature of the air conditioner and the target heating level of the seat, as well as the target verification code, to the vehicle terminal. The vehicle terminal will then set the air conditioner and seats accordingly and update the verification code to the resent value, thereby forcing the vehicle terminal status to be consistent with the user's preset.

[0053] By employing the aforementioned technical solution, this specific synchronization operation, performed with user authorization, provides a direct and effective path to repair detected state inconsistencies. By retransmitting the complete original preset data and checksum, the offset state caused by various reasons on the vehicle side can be clearly and thoroughly covered, thereby forcibly pulling the vehicle side back to the user-expected setting state. This process not only synchronizes specific functional parameters but also synchronizes the authoritative identifier used for comparison, ensuring that the states and identifiers at both ends are immediately restored to uniformity after repair. This mechanism closely integrates the effectiveness of the repair action with user intent, ensuring that every data transmission and vehicle control initiated to correct inconsistencies has a clear purpose and user basis, avoiding potential misoperations or resource waste caused by automatic background synchronization, and enhancing the accuracy of state synchronization management and the controllability perceived by the user.

[0054] Furthermore, as a response to the above Figure 1 In addition to the implementation of the method shown, this embodiment of the invention also provides a vehicle status data synchronization device for the above-mentioned... Figure 1The method shown is implemented accordingly. This device embodiment corresponds to the foregoing method embodiment. For ease of reading, this device embodiment will not repeat the details of the foregoing method embodiment, but it should be clear that the device in this embodiment can implement all the contents of the foregoing method embodiment. Figure 2 As shown, the device includes: a first acquisition unit 21, a second acquisition unit 22, and an execution unit 23, wherein... The first acquisition unit 21 is used to acquire a vehicle terminal verification code based on the vehicle terminal controller, wherein the vehicle terminal verification code is a unique identifier generated based on the vehicle terminal status data of the reservation scenario acquired in real time; The second acquisition unit 22 is used to acquire a target verification code based on the user terminal, wherein the target verification code is a unique identifier generated based on the target status data of the reservation scenario input by the user; The execution unit 23 is used to perform a synchronization operation based on user feedback information when the vehicle-side verification code and the target verification code are inconsistent.

[0055] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and by adjusting kernel parameters, a method for synchronizing vehicle status data can be implemented. This addresses the drawback of traditional vehicle status synchronization methods where data transmission redundancy leads to significant inconsistencies between vehicle and cloud states during network anomalies.

[0056] This invention provides a computer-readable storage medium including a stored program that, when executed by a processor, implements a method for synchronizing vehicle status data.

[0057] This invention provides a processor for running a program, wherein the program executes a method for synchronizing vehicle status data during runtime.

[0058] This invention provides an electronic device, which includes at least one processor and at least one memory connected to the processor; wherein the processor is used to call program instructions in the memory to execute the vehicle status data synchronization method described above. This invention provides an electronic device 30, such as... Figure 3 As shown, the electronic device includes at least one processor 301, and at least one memory 302 and bus 303 connected to the processor; wherein, the processor 301 and the memory 302 communicate with each other through the bus 303; the processor 301 is used to call program instructions in the memory to execute the above-mentioned vehicle status data synchronization method.

[0059] The smart electronic devices mentioned in this article can be PCs, tablets, mobile phones, etc.

[0060] This application also provides a computer program product that, when executed on a process management electronic device, is suitable for executing a program that initializes the synchronization method steps for the aforementioned vehicle state data.

[0061] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0062] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0063] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0064] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0065] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0066] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to perform actions such as... Figure 1 The control flow of the memory in the corresponding embodiment.

[0067] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0068] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0069] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0070] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0071] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0072] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0073] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for synchronizing vehicle status data, characterized in that, include: The vehicle terminal verification code is obtained based on the vehicle terminal controller, wherein the vehicle terminal verification code is a unique identifier generated based on the real-time acquired vehicle terminal status data of the reservation scenario; The target verification code is obtained based on the user terminal, wherein the target verification code is a unique identifier generated based on the target status data of the reservation scenario input by the user; If the vehicle-side verification code and the target verification code are inconsistent, a synchronization operation is performed based on the user's feedback information.

2. The method according to claim 1, characterized in that, Also includes: Initial state data is set for different reservation scenarios based on the user's client; Generate a verification code for each reservation scenario; Each reservation scenario and the corresponding verification code are sent to the vehicle controller to form the initial reservation scenario of the vehicle controller. If the reservation scenario changes, the vehicle verification code is updated based on the real-time acquired vehicle status data.

3. The method according to claim 2, characterized in that, Also includes: The status data of the reservation scenario are concatenated into a string based on a preset order; The string is used to generate a verification code using a preset algorithm.

4. The method according to claim 1, characterized in that, The process of obtaining the vehicle-side verification code based on the vehicle-side controller includes: The on / off status of each reservation scenario and the vehicle-side verification code for each reservation scenario are obtained in real time based on the vehicle-side controller at a preset frequency.

5. The method according to claim 1, characterized in that, The step of obtaining the target verification code based on the user terminal includes: When a user logs in on the client side, the target verification code is obtained based on the client side's login information.

6. The method according to claim 5, characterized in that, When the vehicle-side verification code and the target verification code are inconsistent, the synchronization operation is performed based on user feedback information, including: When the user is logged in, obtain the comparison result between the vehicle-side verification code and the target verification code; If the comparison results are inconsistent, a query message is sent to the user, wherein the query message is used to obtain the user's feedback on their willingness to resynchronize; The synchronization operation is performed based on the feedback information.

7. The method according to claim 6, characterized in that, The step of performing the synchronization operation based on the feedback information includes: If the feedback information indicates resynchronization, the target status data of the reservation scenario and the target verification code will be sent to the vehicle controller.

8. A vehicle status data synchronization device, characterized in that, Also includes: The first acquisition unit is used to acquire a vehicle terminal verification code based on the vehicle terminal controller, wherein the vehicle terminal verification code is a unique identifier generated based on the vehicle terminal status data of the reservation scenario acquired in real time; The second acquisition unit is used to acquire a target verification code based on the user terminal, wherein the target verification code is a unique identifier generated based on the target status data of the reservation scenario input by the user; An execution unit is used to perform a synchronization operation based on user feedback information when the vehicle-side verification code and the target verification code are inconsistent.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed by a processor, it implements the steps of the method for synchronizing vehicle state data as claimed in any one of claims 1 to 7.

10. An electronic device, characterized in that, The electronic device includes at least one processor and at least one memory connected to the processor; wherein the processor is configured to invoke program instructions in the memory to execute the steps of the vehicle status data synchronization method as described in any one of claims 1 to 7.

Images