Data synchronization method and device for vehicle-mounted account, equipment and medium
By temporarily displaying the personalized setting data of the slow startup controller during power-on startup time on the screen display unit and changing it according to the feedback status information, the problem of data synchronization failure is solved and the user experience is improved.
Patent Information
- Application Number
- CN202411950222.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-27
- Publication Date
- 2025-04-11
AI Technical Summary
When the car is powered on, the startup time of some controllers is longer than that of the large-screen display unit, resulting in the synchronization of personalized settings data of the on-board account failing, affecting the user experience.
The temporary display setting of the personalized setting data of the controller with slow startup time is performed in the screen display unit, and the temporary display setting is changed according to the feedback status information of the controller to ensure the accuracy of data synchronization.
It realizes the synchronization of personalized settings data of the on-board account accurately when the car is powered on and started, improving the user experience.
Smart Images

Figure CN119814804A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of intelligent Internet automobile technology, and in particular to a method, device, equipment and medium for synchronizing data of an in-vehicle account. Background Art
[0002] With the continuous improvement of the intelligence of automobiles, automobile manufacturers have developed their own in-vehicle account systems and installed them on their own models to facilitate the migration of user personalized settings data. The current accounts are all associated with the storage of personalized data used by users. Every time the account switches to log in, the cloud will send the personalized data of the account, and finally the large-screen display unit will synchronously send a setting request to other modules of the vehicle to ensure that the user's usage habits are recorded. However, when the account switches to log in when the vehicle is powered on, and some controllers have a longer startup time than the large-screen display unit, some data synchronization will fail. In the end, the user finds that the setting switch after power-on is different from the corresponding personalized data, which leads to a poor user experience. Therefore, how to accurately complete the synchronization of personalized settings data for in-vehicle accounts has become a technical issue that cannot be underestimated. Summary of the invention
[0003] In view of this, the purpose of the present application is to provide a method, device, equipment and medium for data synchronization of an in-vehicle account, by temporarily displaying the personalized setting data of a controller with a slow startup time on a screen display unit, and then changing the temporary display setting according to the feedback status information of the controller, so as to accurately complete data synchronization and enhance the user experience.
[0004] The present application provides a method for synchronizing data of an in-vehicle account, the method comprising:
[0005] Determine multiple personalized setting data of the target vehicle account after switching login of the current vehicle;
[0006] Performing temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit;
[0007] Based on the status information of the startup status signal of the first controller, it is determined whether to control the screen display unit to send a first setting request. If so, the temporary display setting is changed based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
[0008] In a possible implementation manner, after determining a plurality of personalized setting data of the target vehicle account after the switching login of the current vehicle, the data synchronization method further includes:
[0009] Controlling the screen display unit to send a second setting request corresponding to the personalized setting data to a second controller of the current vehicle, and receiving second feedback status information of the second controller in response to the second setting request; wherein the second controller is a controller whose startup time is faster than that of the screen display unit;
[0010] Based on the second feedback state information, corresponding data is synchronously displayed on the screen display unit.
[0011] In a possible implementation manner, determining whether to control the screen display unit to send a first setting request based on the status information of the startup status signal of the first controller includes:
[0012] Detecting whether the state of the start state signal is a ready state;
[0013] If yes, controlling the screen display unit to send a first setting request;
[0014] If not, the screen display unit is not controlled to send the first setting request.
[0015] In a possible implementation manner, the start status signal is determined in the following manner:
[0016] Determining the execution function corresponding to each execution module in the first controller;
[0017] A startup state signal of the first controller is constructed based on the execution state signals of each of the execution functions.
[0018] In a possible implementation manner, for any of the execution status signals, detecting whether the state of the start status signal is a ready state is performed in the following manner:
[0019] Detecting whether the execution status signal is in a startup completion state;
[0020] If yes, the start state signal of the execution module corresponding to the execution state signal is in the ready state, so that the screen display unit is subsequently controlled to send a first setting request to the execution module in the first controller;
[0021] If not, the start status signal of the execution module corresponding to the execution status signal is not in the ready state, so that the screen display unit is controlled not to send the first setting request to the execution module in the first controller.
[0022] In a possible implementation manner, the changing the temporary display setting based on the first feedback state information of the first controller in response to the first setting request includes:
[0023] If the first feedback state information is consistent with the state information of the temporary display setting, then the temporary display setting is not changed;
[0024] If the first feedback state information is inconsistent with the state information of the temporary display setting, the temporary display setting is modified based on the first feedback state information.
[0025] The embodiment of the present application also provides a data synchronization device for an in-vehicle account, the data synchronization device comprising:
[0026] A data acquisition module, used to determine a plurality of personalized setting data of a target vehicle account after switching login of the current vehicle;
[0027] A temporary display module, used for performing temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit;
[0028] A display modification module is used to determine whether to control the screen display unit to send a first setting request based on the status information of the startup status signal of the first controller. If so, a temporary display setting is changed based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
[0029] In a possible implementation manner, the data synchronization device further includes a data synchronization module, and the data synchronization module is used to:
[0030] Controlling the screen display unit to send a second setting request corresponding to the personalized setting data to a second controller of the current vehicle, and receiving second feedback status information of the second controller in response to the second setting request; wherein the second controller is a controller whose startup time is faster than that of the screen display unit;
[0031] Based on the second feedback state information, corresponding data is synchronously displayed on the screen display unit.
[0032] An embodiment of the present application also provides an electronic device, including: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the data synchronization method for an in-vehicle account as described above are performed.
[0033] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the data synchronization method for an in-vehicle account are executed.
[0034] The embodiment of the present application provides a method, device, equipment and medium for synchronizing data of an in-vehicle account, the data synchronization method comprising: determining multiple personalized setting data of the target in-vehicle account after the switching login of the current vehicle; performing temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit; based on the status information of the startup status signal of the first controller, determining whether to control the screen display unit to send a first setting request, and if so, changing the temporary display setting based on the first feedback status information of the first controller in response to the first setting request, so as to complete the personalized data synchronization of the first controller. By temporarily displaying the personalized setting data of the controller with a slow startup time on the screen display unit, and then changing the temporary display setting according to the feedback status information of the first controller, the data synchronization is completed accurately, and the user experience is improved.
[0035] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0037] Figure 1 A flow chart of a method for synchronizing data of an in-vehicle account provided in an embodiment of the present application;
[0038] Figure 2 A schematic diagram of a method for synchronizing data of an in-vehicle account provided in an embodiment of the present application;
[0039] Figure 3 One of the structural schematic diagrams of a data synchronization device for an in-vehicle account provided in an embodiment of the present application;
[0040] Figure 4 A second structural diagram of a data synchronization device for an in-vehicle account provided in an embodiment of the present application;
[0041] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0042] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.
[0043] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.
[0044] In order to enable those skilled in the art to use the contents of this application, the following implementation method is given in combination with the specific application scenario of "synchronizing personalized setting data of the vehicle account". For those skilled in the art, the general principles defined here can be applied to other embodiments and application scenarios without departing from the spirit and scope of this application.
[0045] The following methods, devices, electronic devices or computer-readable storage media of the embodiments of the present application can be applied to any scenario that requires synchronization of personalized setting data of an in-vehicle account. The embodiments of the present application are not limited to specific application scenarios. Any scheme using a data synchronization method, device, equipment and medium for an in-vehicle account provided by the embodiments of the present application is within the protection scope of the present application.
[0046] First, the application scenarios to which this application is applicable are introduced. This application can be applied in the field of intelligent Internet vehicle technology.
[0047] Research has found that with the continuous improvement of the intelligence of automobiles, automobile manufacturers have developed their own in-vehicle account systems and installed them on their own models to facilitate the migration of user personalized settings data. The current accounts all have associated storage of personalized data used by users. Every time the account switches login, the cloud will send the personalized data of the account, and finally the large-screen display unit will synchronously send a setting request to other modules of the vehicle to ensure that the user's usage habits are recorded. However, when the account switches login when the vehicle is powered on, and some controllers have a longer startup time than the large-screen display unit, some data synchronization will fail. In the end, the user finds that the setting switch after power-on is different from the corresponding personalized data, which leads to a poor user experience. Therefore, how to accurately complete the synchronization of personalized settings data for in-vehicle accounts has become a technical issue that cannot be underestimated.
[0048] Based on this, an embodiment of the present application provides a data synchronization method for a vehicle-mounted account, by temporarily displaying the personalized setting data of a controller with a slow startup time on a screen display unit, and then changing the temporary display setting according to the feedback status information of the controller, so as to accurately complete data synchronization and enhance the user experience.
[0049] See also Figure 1 , Figure 1 This is a flow chart of a method for synchronizing data of an in-vehicle account provided in an embodiment of the present application. Figure 1 As shown in , the data synchronization method provided by the embodiment of the present application includes:
[0050] S101: Determine a plurality of personalized setting data of a target vehicle account after switching login to the current vehicle.
[0051] In this step, multiple personalized setting data of the target vehicle account after the switching login of the current vehicle are obtained.
[0052] Among them, personalized setting data includes function setting switches, navigation preferences, driving assistance functions and other information.
[0053] Here, various apps and controllers on the vehicle side, as users of personalized setting data, can directly use the personalized setting data of the vehicle account to implement corresponding functions.
[0054] In a possible implementation manner, multiple personalized setting data of the target vehicle account after the switching login of the current vehicle are determined by the following steps:
[0055] Based on the user's request, the in-vehicle account of the current vehicle is switched to the target in-vehicle account; and based on the target in-vehicle account, a plurality of personalized setting data of the target in-vehicle account are acquired from the cloud.
[0056] Here, the current communication between the vehicle and the cloud is realized by setting up an account management center and an account synchronization center in the vehicle. The account management center is mainly used for vehicle account login, switching and exit, application account mapping, etc.; the account synchronization center is mainly used for personalized setting data management of vehicle accounts, including new creation, modification, storage, synchronization, etc., among which synchronization includes account data synchronization. The cloud has a cloud account management center, which is mainly used for vehicle data of multiple models and multiple accounts as well as storage and synchronization of vehicle accounts.
[0057] S102: Performing temporary display settings on a screen display unit based on personalized setting data corresponding to a first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than that of the screen display unit.
[0058] In this step, the personalized setting data corresponding to the first controller of the current vehicle is used to temporarily display the switch corresponding to the screen display unit. For example, after the screen display unit switches the login account, the personalized setting data corresponding to the first controller (Advanced Driver Assistance System Control Unit, ADCU) under the account is used to display the switch status, such as displaying that the door opening warning function is memorized as on.
[0059] The first controller is a controller whose startup time is slower than that of the screen display unit, such as an advanced driver assistance system control unit.
[0060] Here, the screen display unit displays the status of each switch.
[0061] Among them, taking ADCU as an example, because ADCU is equipped with MCU and SOC processors, the startup time of ADCU is usually relatively long (may exceed 30s), while if IDCU is hot-started (collectively referred to as quick startup), the startup is relatively fast (generally completed within 10s). During the 10s to 30s period, ADCU is still starting, and the user may have completed the account switch. At this time, if a request for setting personalized data memorized under the account is issued, ADCU will not respond. After ADCU startup is completed, the value returned by the setting status may still be the status before the last power-off, resulting in the setting switch status of the large screen and the ADCU function status not being maintained in the state last used by the user. Therefore, a temporary display is set in this application, and subsequent changes are made based on the actual feedback results of ADCU to enhance the user experience.
[0062] S103: Based on the status information of the startup status signal of the first controller, determine whether to control the screen display unit to send a first setting request. If so, change the temporary display setting based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
[0063] In this step, based on the status information of the startup status signal of the first controller, it is determined whether to control the screen display unit to send a first setting request. If so, the temporary display setting is changed based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
[0064] In a possible implementation manner, the start status signal is determined in the following manner:
[0065] Determine the execution function corresponding to each execution module in the first controller; and construct a startup state signal of the first controller based on the execution state signal of each execution function.
[0066] Here, the startup status signal of the first controller is constructed according to the execution status signals of the execution functions corresponding to the execution modules in the first controller. For example, the advanced driver assistance system control unit (ADCU) is responsible for managing and coordinating various advanced driver assistance functions, such as automatic parking assistance (APA), surround view system (AVM), high-precision automatic parking (HAVP) and pilot assisted driving (NOA). ADCU is usually integrated in the vehicle to ensure that the driver can safely operate these auxiliary functions. Therefore, the startup status signal of ADCU includes whether AVM is ready, whether APA is ready, whether HAVP is ready, whether NOA driving is ready, etc.
[0067] In a possible implementation manner, determining whether to control the screen display unit to send a first setting request based on the status information of the startup status signal of the first controller includes:
[0068] A: Detect whether the state of the startup state signal is a ready state.
[0069] Here, it is detected whether the state of the start state signal is the ready state.
[0070] In a possible implementation manner, for any of the execution status signals, detecting whether the state of the start status signal is a ready state is performed in the following manner:
[0071] (1) Detect whether the execution status signal is in a startup completion state.
[0072] Here, it is detected whether the execution status signal is in the startup completion state.
[0073] (2): If so, the startup status signal of the execution module corresponding to the execution status signal is in the ready state, so that the subsequent control of the screen display unit sends a first setting request to the execution module in the first controller; if not, the startup status signal of the execution module corresponding to the execution status signal is not in the ready state, so that the control of the screen display unit does not send the first setting request to the execution module in the first controller.
[0074] Here, if the first controller is ADCU, it detects whether the AVM, APA, HAVP, NOA driving, etc. contained in the startup status signal are ready. If the execution status signals of AVM and APA are ready, a first setting request is sent to the execution modules corresponding to AVM and APA. If the execution status signals of HAVP and NOA driving are not ready, the first setting request is not sent to the execution modules corresponding to HAVP and NOA driving.
[0075] B: If yes, control the screen display unit to send the first setting request; if no, do not control the screen display unit to send the first setting request.
[0076] Here, if yes, the screen display unit is controlled to send a first setting request to the execution module corresponding to the ready state of the startup state signal in the first controller; if no, the screen display unit is not controlled to send the first setting request to the execution module.
[0077] In a possible implementation manner, the changing the temporary display setting based on the first feedback state information of the first controller in response to the first setting request includes:
[0078] a: If the first feedback state information is consistent with the state information of the temporary display setting, the temporary display setting is not changed.
[0079] b: If the first feedback state information is inconsistent with the state information of the temporary display setting, modify the temporary display setting based on the first feedback state information.
[0080] Here, after the IDCU login is completed, when it is detected that the ADCU functional module is still in the startup state, since no signal can be sent during the ADCU startup process, the signal of the IDCU detecting ADCU is lost. Therefore, this solution designs a startup status signal of each execution module on the ADCU side, which includes whether the AVM is ready, whether the APA is ready, whether the HAVP is ready, whether the NOA driving is ready, etc. After the IDCU side switches the login account, the personalized data corresponding to the ADCU under the account is first used to display the switch status. After waiting for the execution module in the ADCU to feedback that the function is ready, the IDCU then sends the setting request signal corresponding to the personalized data to the execution module in the ADCU, and finally changes the temporarily set display switch status with the actual feedback status signal of the ADCU execution module.
[0081] In a possible implementation manner, after determining a plurality of personalized setting data of the target vehicle account after the switching login of the current vehicle, the data synchronization method further includes:
[0082] I: controlling the screen display unit to send a second setting request for corresponding personalized setting data to a second controller of the current vehicle, and receiving second feedback state information of the second controller in response to the second setting request.
[0083] Here, the control screen display unit sends a second setting request for corresponding personalized setting data to a second controller of the current vehicle, and receives second feedback state information of the second controller in response to the second setting request.
[0084] The second controller is a controller whose startup time is faster than that of the screen display unit.
[0085] Here, because the second controller that starts faster can receive the second setting request sent by the screen display unit after the screen display unit is started up, there is no need to set the startup state signal for the second controller.
[0086] II: synchronously displaying corresponding data on the screen display unit based on the second feedback state information.
[0087] Here, corresponding data is synchronously displayed on the screen display unit according to the second feedback state information.
[0088] For further information, see Figure 2 , Figure 2 A schematic diagram of a data synchronization method for an in-vehicle account provided in an embodiment of the present application. Figure 2As shown, when the user unlocks and powers on, the IDCU starts and the target vehicle account logs in, sends the target vehicle account to the cloud, sets the display switch state according to the personalized setting data obtained from the first controller, receives the ready state of the startup state signal fed back by the first controller, sends the first setting request corresponding to the personalized data to the first controller, receives the first feedback state information of the first controller in response to the first setting request, and changes the display switch state according to the first feedback state information.
[0089] The embodiment of the present application provides a data synchronization method for an in-vehicle account, the data synchronization method comprising: determining multiple personalized setting data of the target in-vehicle account after the switching login of the current vehicle; performing temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit; based on the status information of the startup status signal of the first controller, determining whether to control the screen display unit to send a first setting request, and if so, changing the temporary display settings based on the first feedback status information of the first controller in response to the first setting request, so as to complete the personalized data synchronization of the first controller. By temporarily displaying the personalized setting data of the controller with a slow startup time on the screen display unit, and then changing the temporary display settings according to the feedback status information of the first controller, the data synchronization is completed accurately, and the user experience is improved.
[0090] See also Figure 3 , Figure 4 , Figure 3 One of the structural schematic diagrams of a data synchronization device for an in-vehicle account provided in an embodiment of the present application; Figure 4 This is a second structural diagram of a data synchronization device for an in-vehicle account provided in an embodiment of the present application. Figure 3 As shown in , the data synchronization device 300 includes:
[0091] The data acquisition module 310 is used to determine a plurality of personalized setting data of the target vehicle account after the switching login of the current vehicle;
[0092] A temporary display module 320, configured to perform temporary display settings on a screen display unit based on personalized setting data corresponding to a first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than that of the screen display unit;
[0093] The display modification module 330 is used to determine whether to control the screen display unit to send a first setting request based on the status information of the startup status signal of the first controller, and if so, to change the temporary display setting based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
[0094] Further, such as Figure 4 As shown, the data synchronization device 300 further includes a data synchronization module 340, and the data synchronization module 340 is used to:
[0095] Controlling the screen display unit to send a second setting request corresponding to the personalized setting data to a second controller of the current vehicle, and receiving second feedback status information of the second controller in response to the second setting request; wherein the second controller is a controller whose startup time is faster than that of the screen display unit;
[0096] Based on the second feedback state information, corresponding data is synchronously displayed on the screen display unit.
[0097] Further, when the display modification module 3230 is used to determine whether to control the screen display unit to send the first setting request based on the state information of the startup state signal of the first controller, the display modification module 330 is specifically used to:
[0098] Detecting whether the state of the start state signal is a ready state;
[0099] If yes, controlling the screen display unit to send a first setting request;
[0100] If not, the screen display unit is not controlled to send the first setting request.
[0101] Further, the display modification module 330 determines the startup state signal in the following manner:
[0102] Determining the execution function corresponding to each execution module in the first controller;
[0103] A startup state signal of the first controller is constructed based on the execution state signals of each of the execution functions.
[0104] Further, the display modification module 330 is used to detect whether the state of the start state signal is the ready state in the following manner for any of the execution state signals:
[0105] Detecting whether the execution status signal is in a startup completion state;
[0106] If yes, the start state signal of the execution module corresponding to the execution state signal is in the ready state, so that the screen display unit is subsequently controlled to send a first setting request to the execution module in the first controller;
[0107] If not, the start status signal of the execution module corresponding to the execution status signal is not in the ready state, so that the screen display unit is controlled not to send the first setting request to the execution module in the first controller.
[0108] Further, when the display modification module 330 is used to modify the temporary display setting based on the first feedback state information of the first controller in response to the first setting request, the display modification module 330 is specifically used to:
[0109] If the first feedback state information is consistent with the state information of the temporary display setting, then the temporary display setting is not changed;
[0110] If the first feedback state information is inconsistent with the state information of the temporary display setting, the temporary display setting is modified based on the first feedback state information.
[0111] The embodiment of the present application provides a data synchronization device for an in-vehicle account, the data synchronization device comprising: a data acquisition module, used to determine multiple personalized setting data of the target in-vehicle account after the switching login of the current vehicle; a temporary display module, used to perform temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit; a display modification module, used to determine whether to control the screen display unit to send a first setting request based on the state information of the startup state signal of the first controller, and if so, to change the temporary display setting based on the first feedback state information of the first controller in response to the first setting request, so as to complete the personalized data synchronization of the first controller. By temporarily displaying the personalized setting data of the controller with a slow startup time on the screen display unit, and then changing the temporary display setting according to the feedback state information of the first controller, the data synchronization can be completed accurately, and the user experience can be improved.
[0112] See also Figure 5 , Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 5 As shown in , the electronic device 500 includes a processor 510 , a memory 520 and a bus 530 .
[0113] The memory 520 stores machine-readable instructions executable by the processor 510. When the electronic device 500 is running, the processor 510 communicates with the memory 520 via the bus 530. When the machine-readable instructions are executed by the processor 510, the above-mentioned Figure 1 as well as Figure 2 The steps of the data synchronization method for the vehicle account in the method embodiment shown, the specific implementation method can be found in the method embodiment, and will not be repeated here.
[0114] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 as well as Figure 2 The steps of the data synchronization method for the vehicle account in the method embodiment shown, the specific implementation method can be found in the method embodiment, and will not be repeated here.
[0115] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0116] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.
[0117] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0118] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0119] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0120] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.
Claims
1. A method for synchronizing vehicle account data, characterized in that: The data synchronization method comprises: Determine multiple personalized setting data of the target vehicle account after switching login of the current vehicle; Performing temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit; Based on the status information of the startup status signal of the first controller, it is determined whether to control the screen display unit to send a first setting request. If so, the temporary display setting is changed based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
2. The data synchronization method according to claim 1, characterized in that: After determining the multiple personalized setting data of the target vehicle account after the switching login of the current vehicle, the data synchronization method further includes: Controlling the screen display unit to send a second setting request corresponding to the personalized setting data to a second controller of the current vehicle, and receiving second feedback status information of the second controller in response to the second setting request; wherein the second controller is a controller whose startup time is faster than that of the screen display unit; Based on the second feedback state information, corresponding data is synchronously displayed on the screen display unit.
3. The data synchronization method according to claim 1, characterized in that: The determining whether to control the screen display unit to send a first setting request based on the state information of the startup state signal of the first controller includes: Detecting whether the state of the start state signal is a ready state; If yes, controlling the screen display unit to send a first setting request; If not, the screen display unit is not controlled to send the first setting request.
4. The data synchronization method according to claim 3, characterized in that: The start-up status signal is determined by: Determining the execution function corresponding to each execution module in the first controller; A startup state signal of the first controller is constructed based on the execution state signals of each of the execution functions.
5. The data synchronization method according to claim 4, characterized in that: For any of the execution status signals, whether the state of the start status signal is a ready state is detected in the following manner: Detecting whether the execution status signal is in a startup completion state; If yes, the start state signal of the execution module corresponding to the execution state signal is in the ready state, so that the screen display unit is subsequently controlled to send a first setting request to the execution module in the first controller; If not, the start status signal of the execution module corresponding to the execution status signal is not in the ready state, so that the screen display unit is controlled not to send the first setting request to the execution module in the first controller.
6. The data synchronization method according to claim 1, characterized in that: The changing the temporary display setting based on the first feedback state information of the first controller in response to the first setting request comprises: If the first feedback state information is consistent with the state information of the temporary display setting, then the temporary display setting is not changed; If the first feedback state information is inconsistent with the state information of the temporary display setting, the temporary display setting is modified based on the first feedback state information.
7. A data synchronization device for an in-vehicle account, characterized in that: The data synchronization device comprises: A data acquisition module, used to determine a plurality of personalized setting data of a target vehicle account after switching login of the current vehicle; A temporary display module, used for performing temporary display settings on the screen display unit based on the personalized setting data corresponding to the first controller of the current vehicle; wherein the first controller is a controller whose startup time is slower than the startup time of the screen display unit; A display modification module is used to determine whether to control the screen display unit to send a first setting request based on the status information of the startup status signal of the first controller. If so, a temporary display setting is changed based on the first feedback status information of the first controller in response to the first setting request to complete the personalized data synchronization of the first controller.
8. The data synchronization device according to claim 7, characterized in that: The data synchronization device also includes a data synchronization module, which is used to: Controlling the screen display unit to send a second setting request corresponding to the personalized setting data to a second controller of the current vehicle, and receiving second feedback status information of the second controller in response to the second setting request; wherein the second controller is a controller whose startup time is faster than that of the screen display unit; Based on the second feedback state information, corresponding data is synchronously displayed on the screen display unit.
9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate through the bus. When the machine-readable instructions are run by the processor, the steps of the method for synchronizing the data of an in-vehicle account as described in any one of claims 1 to 6 are executed.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for synchronizing the data of an in-vehicle account as described in any one of claims 1 to 6 are executed.