Cyclic scheduled task synchronization method, apparatus and device for vehicle, and storage medium

Abstract

Disclosed in the present invention are a cyclic scheduled task synchronization method, apparatus and device for a vehicle, and a storage medium. The method is applied to a vehicle end, and the method comprises: receiving an unbinding and clearing request message issued by a cloud, wherein the unbinding and clearing request message is used for releasing bound first vehicle owner account information and clearing a cyclic scheduled task; and in response to the unbinding and clearing request message, determining a first cyclic scheduled task which is locally stored in a vehicle and is bound with the first vehicle owner account information, and clearing the first cyclic scheduled task.

Description

Synchronization method, device, equipment and storage medium for vehicle cycle reservation tasks CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The embodiments of this application are based on and claim the priority of Chinese patent application with application number 202410111952.4 and application date January 25, 2024. The entire contents of the Chinese patent application are hereby introduced into the embodiments of this application as a reference. Technical Field

[0002] The present invention relates to the field of intelligent vehicle technology, and in particular to a synchronization method, device, equipment and storage medium for vehicle cyclic reservation tasks. Background Art

[0003] With the increasing intelligence of smart cockpits and connected vehicles, demand for remote vehicle control is growing. This includes remotely scheduling air conditioning and charging, and manually setting the time and cycle for recurring scheduled tasks. However, if recurring tasks set via a mobile terminal or the vehicle's central control screen are not cleared promptly after a change of ownership, the recurring tasks set by the previous owner will be transferred to the next owner. Without the latter's knowledge, the vehicle will continue to execute the recurring tasks, seriously affecting the user experience and the lifespan of the vehicle battery. Summary of the Invention

[0004] In view of this, the present invention provides a method, device, equipment and storage medium for synchronizing vehicle cyclic reservation tasks.

[0005] The technical solution of the present invention is achieved as follows:

[0006] On the one hand, the present invention provides a method for synchronizing vehicle recurring reservation tasks, which is applied to the vehicle side, and the method includes: receiving an unbinding and clearing request message sent from the cloud; wherein the unbinding and clearing request message is used to unbind the first vehicle owner account information and clear the recurring reservation task; in response to the unbinding and clearing request message, determining the first recurring reservation task stored locally on the vehicle that is bound to the first vehicle owner account information, and clearing the first recurring reservation task.

[0007] On the other hand, the present invention provides a synchronization method for vehicle recurring reservation tasks, which is applied to the cloud, and the method includes: receiving an unbinding request sent by a user terminal; wherein the unbinding request is used to request the unbinding of the person-vehicle relationship; in response to the unbinding request, sending an unbinding and clearing message to the vehicle end; wherein the unbinding and clearing message is used to unbind the bound vehicle owner account information and clear the recurring reservation task; receiving an unbinding and clearing response message returned by the vehicle end; wherein the unbinding and clearing response message is used to indicate whether the unbinding and clearing are successful; based on the unbinding and clearing response message, sending a prompt information to the user terminal whether the unbinding and clearing are successful.

[0008] The present invention also provides a synchronization device for vehicle cyclic reservation tasks, which is applied to the vehicle side, and the synchronization device includes: a first receiving module, used to receive an unbinding and clearing request message sent from the cloud; wherein the unbinding and clearing request message is used to unbind the first vehicle owner account information and clear the cyclic reservation task; a first clearing module, used to respond to the unbinding and clearing request message, determine the first cyclic reservation task stored locally on the vehicle that is bound to the first vehicle owner account information, and clear the first cyclic reservation task.

[0009] The present invention also provides a synchronization device for vehicle cycle reservation tasks, including a processor and a memory, wherein the memory is used to store computer programs, and the processor is used to execute the computer programs stored in the memory to implement the synchronization method for vehicle cycle reservation tasks.

[0010] The present invention also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the synchronization method of the vehicle cycle reservation task is implemented.

[0011] In the present invention, after receiving the unbinding and clearing request message sent from the cloud, the vehicle responds to the unbinding and clearing request message, unbinding the first vehicle owner's account information, and simultaneously clearing the first recurring scheduled task locally stored in the vehicle that is bound to the first vehicle owner's account information. This ensures that when the vehicle owner changes, the recurring scheduled tasks stored locally in the vehicle are promptly cleared, preventing the vehicle from continuing to execute the recurring scheduled tasks set by the previous owner even if the vehicle owner changes.

[0012] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit the technical solutions of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and, together with the specification, are used to illustrate the technical solutions of the present application.

[0014] FIG1 is a schematic diagram of a first implementation flow of a method for synchronizing a vehicle cycle reservation task provided by an embodiment of the present application;

[0015] FIG2 is a second schematic diagram of a process for implementing a synchronization method for a vehicle cycle reservation task provided by an embodiment of the present application;

[0016] FIG3 is a schematic diagram of the structure of a synchronization system for vehicle cycle reservation tasks provided by an embodiment of the present application;

[0017] FIG4 is a third schematic diagram of an implementation flow of a method for synchronizing a vehicle cycle reservation task provided by an embodiment of the present application;

[0018] FIG5 is a schematic diagram of the first structure of a synchronization device for cyclically reserving vehicle tasks according to an embodiment of the present application;

[0019] FIG6 is a second schematic diagram of the structure of a synchronization device for cyclically reserving vehicle tasks according to an embodiment of the present application;

[0020] FIG7 is a schematic structural diagram of a synchronization device for a vehicle cycle reservation task provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solutions and advantages of this application clearer, the following figure will further describe this application in detail in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0022] The exemplary embodiments disclosed herein will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the specific embodiments described herein. Rather, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0023] In the following description, numerous specific details are provided to provide a more thorough understanding of the present application. However, it will be apparent to those skilled in the art that the present application can be practiced without one or more of these details. In other instances, certain technical features known in the art are not described to avoid confusion with the present application; that is, all features of actual embodiments are not described herein, nor are well-known functions and structures described in detail.

[0024] In the drawings, the sizes of layers, regions, elements and their relative sizes may be exaggerated for clarity. Like reference numerals denote like elements throughout.

[0025] The purpose of the terms used herein is only to describe specific embodiments and is not intended to limit the present application. When used herein, the singular forms "a", "an", and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the terms "comprising" and / or "including", when used in this specification, determine the presence of the features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or groups. When used herein, the term "and / or" includes any and all combinations of the relevant listed items.

[0026] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs. The technical and scientific terms used herein are only for the purpose of describing the embodiments of this application and do not limit this application.

[0027] With the gradual development of the smart car market, the intelligence of in-vehicle central control systems is becoming increasingly mature, in-vehicle applications are becoming more and more complex, and customer experience is becoming more and more important. Therefore, there are more and more application demands for cyclic appointment tasks, such as scheduling charging at night when electricity prices are at their lowest to save electricity bills, scheduling vehicle OTA upgrades at night so as not to affect daytime use, and scheduling to turn on the air conditioner before getting off work so that users can have a good cabin space as soon as they get in the car.

[0028] However, currently available solutions often involve setting up recurring scheduled tasks through a mobile app or the vehicle's central control screen, and then storing these tasks locally on the vehicle to ensure they can be executed even when there's no network connection. However, if these locally stored recurring tasks aren't cleared promptly when the vehicle's owner changes, the recurring tasks set by the previous owner will be transferred to the next owner. Without the latter's knowledge, the vehicle will continue to recur, severely impacting the user experience and the vehicle's battery life.

[0029] To address the issue of timely clearing recurring scheduled tasks locally in a vehicle when the vehicle owner changes, an embodiment of the present application provides a method for synchronizing recurring scheduled tasks for a vehicle. This method, applied to the vehicle, removes the binding relationship with the first vehicle owner's account information in response to the unbinding and clearing request message sent from the cloud, and simultaneously clears the first recurring scheduled task locally stored in the vehicle that is bound to the first vehicle owner's account information. This method enables timely clearing of recurring scheduled tasks locally stored in the vehicle when the vehicle owner changes, preventing the vehicle from continuing to execute recurring scheduled tasks set by the previous owner even after the vehicle owner changes.

[0030] FIG1 is a schematic diagram of a first implementation flow of a method for synchronizing a vehicle cyclic reservation task provided by an embodiment of the present application. As shown in FIG1 , the method is applied to a vehicle side, and the method includes the following steps S101 and S102:

[0031] Step S101: receiving an unbinding and clearing request message sent from the cloud; wherein, the unbinding and clearing request message is used to unbind the first vehicle owner account information and clear the recurring reservation task.

[0032] Here, the mobile terminal, vehicle, and cloud communicate over the network. When a user performs an unbinding operation on the mobile terminal, an unbinding operation request is sent to the cloud. Upon receiving the unbinding operation request, the cloud sends an unbinding and clearing request message to the vehicle. The unbinding and clearing request message is used to unbind the first owner's account information bound to the vehicle and clear the recurring scheduled tasks stored locally in the vehicle. Recurring scheduled tasks stored locally in the vehicle include, but are not limited to, recurring charging, recurring air conditioning, and recurring seat heating.

[0033] Step S102: In response to the unbinding and clearing request message, determine the first recurring scheduled task stored locally in the vehicle that is bound to the first vehicle owner account information, and clear the first recurring scheduled task.

[0034] Here, after receiving the unbinding and clearing request message sent from the cloud, the vehicle side responds to the unbinding and clearing request message, and cancels the binding relationship between the vehicle and the first vehicle owner account information. At the same time, the vehicle side clears the first cycle reservation task bound to the first vehicle owner account information stored locally in the vehicle.

[0035] In this embodiment of the present application, upon receiving an unbinding and clearing request message from the cloud, the vehicle responds to the unbinding and clearing request message, unbinding the first vehicle owner's account information, and simultaneously clearing the first recurring scheduled task stored locally on the vehicle that was bound to the first vehicle owner's account information. This ensures that when the vehicle owner changes, the recurring scheduled tasks stored locally on the vehicle are promptly cleared, preventing the vehicle from continuing to execute the recurring scheduled tasks set by the previous owner even after the vehicle owner changes.

[0036] In some embodiments, the method further includes steps S201 and S202, wherein:

[0037] Step S201: After the vehicle is powered on, the first owner account information is obtained from the cloud, and the second owner account information stored locally in the vehicle is obtained.

[0038] Here, after the vehicle is powered on, the first owner's account information is obtained from the cloud, and the second owner's account information stored locally in the vehicle is obtained, so as to facilitate subsequent comparison of the first owner's account information and the second owner's account information to determine whether the owner's account information has changed.

[0039] Step S202: When the first vehicle owner account information is inconsistent with the second vehicle owner account information, determine the second cyclic appointment task bound to the second vehicle owner account information, and clear the second cyclic appointment task.

[0040] Here, when the first owner account information is consistent with the second owner account information, it indicates that the owner account information has not changed, and there is no need to clear the cyclic reservation tasks stored locally in the vehicle; when the first owner account information is inconsistent with the second owner account information, it indicates that the owner account information has changed, and the second owner account information needs to be unbound, and the second cyclic reservation tasks bound to the second owner account need to be cleared at the same time.

[0041] In this embodiment of the present application, after the vehicle is powered on, the first owner's account information obtained from the cloud is compared with the second owner's account information stored locally in the vehicle. If the first and second owner's account information are inconsistent, the second recurring scheduled task bound to the second owner's account information is cleared. This allows for the timely clearing of the vehicle's locally stored recurring scheduled tasks when the vehicle owner changes, preventing the vehicle from continuing to execute the recurring scheduled tasks set by the previous owner even after the owner changes.

[0042] In some embodiments, the method further includes steps S301 and S302, wherein:

[0043] Step S301: When the first vehicle owner account information is changed to the third vehicle owner account information, a change and clear request message is received from the cloud; wherein the change and clear request message is used to cancel the first vehicle owner account information and activate the third vehicle owner account information, and clear the recurring reservation task.

[0044] Here, when the vehicle side is powered on and the owner's account information changes, the vehicle side receives the change and clear request message sent from the cloud, wherein the change and clear request message is used to cancel the first owner's account information before the change, and activate the third owner's account information after the change, and at the same time clear the first cycle appointment task bound to the first owner's account information before the change.

[0045] Step S302: In response to the change and clear request message, clear the first recurring scheduled task.

[0046] Here, after receiving the change and clear request message sent by the cloud, the vehicle side responds to the change and clear request message and cancels the binding relationship between the vehicle and the first owner's account information. At the same time, the vehicle side clears the first cycle reservation task bound to the first owner's account information stored locally in the vehicle.

[0047] In this embodiment of the present application, when the first owner account information bound to the vehicle is changed to the third owner account information, the vehicle receives a change and clear request message from the cloud. The vehicle then deregisters the first owner account information and activates the third owner account information, while simultaneously clearing the first recurring scheduled task bound to the first owner account information. This allows for the timely clearing of locally stored recurring scheduled tasks when the vehicle owner changes, preventing the vehicle from continuing to execute the recurring scheduled tasks set by the previous owner even after the owner changes.

[0048] In some embodiments, the method further comprises step S401, wherein:

[0049] Step S401: When the software environment of the vehicle is switched from the first software environment to the second software environment, a third cyclic scheduled task stored locally in the vehicle that is bound to the first software environment is determined, and the third cyclic scheduled task is cleared.

[0050] In this embodiment of the present application, when the vehicle's software environment switches from a first software environment to a second software environment, a third recurring scheduled task stored locally in the vehicle and bound to the first software environment is determined and cleared. This allows for timely clearing of recurring scheduled tasks stored locally in the vehicle when the vehicle's software environment changes, preventing the vehicle from continuing to execute recurring scheduled tasks in the previous vehicle software environment after the vehicle software environment changes.

[0051] FIG2 is a second schematic diagram of a method for synchronizing a vehicle cycle reservation task according to an embodiment of the present application. As shown in FIG2 , the method is applied to the cloud, and the method includes steps S501 to S504:

[0052] Step S501: receiving an unbinding request sent by a user terminal; wherein the unbinding request is used to request unbinding of a person-vehicle relationship.

[0053] Here, the user terminal communicates with the cloud over the network. When the user performs an operation to unbind the person-vehicle relationship on the user terminal, the cloud receives the unbinding request sent by the user terminal.

[0054] Step S502: In response to the unbinding request, an unbinding and clearing message is sent to the vehicle end; wherein, the unbinding and clearing message is used to unbind the bound vehicle owner account information and clear the recurring reservation task.

[0055] Here, after the cloud receives the unbinding request sent by the user terminal, in response to the above unbinding request, the cloud sends an unbinding and clearing message to the vehicle side, wherein the unbinding and clearing message is used to unbind the bound vehicle owner account information and clear the recurring reservation task.

[0056] Step S503: receiving the unbinding and clearing response message returned by the vehicle end; wherein the unbinding and clearing response message is used to indicate whether the unbinding and clearing are successful.

[0057] Here, in response to the unbinding request, after the vehicle side unbinds the bound owner account information and clears the recurring reservation task, the vehicle side returns an unbinding and clearing response message to the cloud. The above unbinding and clearing response message is used to indicate whether the unbinding and clearing are successful.

[0058] Step S504: Based on the unbinding and clearing response message, a prompt message is sent to the user terminal indicating whether the unbinding and clearing are successful.

[0059] Here, after the cloud receives the unbinding and clearing response message returned by the vehicle side, based on the unbinding and clearing response message, the cloud sends a prompt message to the user terminal to indicate whether the unbinding and clearing are successful, so that the user can know whether the unbinding and clearing are successful in time.

[0060] In an embodiment of the present application, after receiving an unbinding request from a user terminal requesting the unbinding of the person-vehicle relationship, the cloud sends an unbinding and clearing message to the vehicle side. After the vehicle side unbinds the bound owner account information and clears the cyclic appointment task, it receives an unbinding and clearing response message returned by the vehicle side, and sends a prompt message to the user terminal indicating whether the unbinding and clearing are successful. On the one hand, when the vehicle owner unbinds the vehicle, the cyclic appointment tasks stored locally in the vehicle are cleared in a timely manner, so as to avoid the vehicle still executing the cyclic appointment tasks set by the owner when the owner's account has been unbound. On the other hand, after the cyclic appointment tasks stored locally in the vehicle are cleared in a timely manner, prompt information is provided to the user indicating whether the clearing of the cyclic appointment tasks is successful, so that the user can promptly know whether the cyclic appointment tasks have been cleared in a timely manner.

[0061] In some embodiments, the method further includes steps S601 to S603, wherein:

[0062] Step S601: In response to the owner account sending request sent by the vehicle end, the first owner account information stored in the cloud is sent to the vehicle end; wherein, the first owner account information is used to compare with the second owner account information stored locally in the vehicle. When the first owner account information and the second owner account information are inconsistent, the recurring reservation tasks stored locally in the vehicle are cleared.

[0063] Here, after the vehicle is powered on, the vehicle sends a request for the owner account to the cloud. In response to the request, the cloud sends the stored first owner account information to the vehicle. The vehicle compares the first owner account information sent by the cloud with the second owner account information stored in the vehicle. If the first owner account information and the second owner account information are consistent, it indicates that the owner account information has not changed, and there is no need to clear the cyclic reservation tasks stored locally in the vehicle. If the first owner account information and the second owner account information are inconsistent, it indicates that the owner account information has changed, and the cyclic reservation tasks stored locally in the vehicle are cleared.

[0064] Step S602: receiving a clear response message returned by the vehicle end; wherein the clear response message is used to indicate whether the clearing of the cyclic reservation task is successful.

[0065] Here, after clearing the recurring scheduled tasks stored locally on the vehicle, the cloud receives a clear response message returned by the vehicle, wherein the clear response message is used to indicate whether the clearing of the recurring scheduled tasks is successful.

[0066] Step S603: Based on the clear response message, a prompt message is sent to the user terminal indicating whether the clearing of the recurring scheduled task is successful.

[0067] Here, after the cloud receives the clear response message returned by the vehicle side, based on the clear response message, the cloud sends a prompt message to the user terminal indicating whether the clearing of the cyclic appointment task is successful, so that the user can know in time whether the cyclic appointment task is successfully cleared.

[0068] In one embodiment of the present application, the vehicle sends a request to the cloud to assign a vehicle owner account. In response to the request, the cloud sends the first vehicle owner account information stored in the cloud to the vehicle. After obtaining the first vehicle owner account information, the vehicle compares the first vehicle owner account information with the second vehicle owner account information stored on the vehicle to determine whether the vehicle owner account information has changed. If the first vehicle owner account information and the second vehicle owner account information are inconsistent, indicating that the vehicle owner account information has changed, the recurring scheduled tasks bound to the second vehicle owner account information stored locally on the vehicle must be cleared. After the clearing, the cloud receives a clear response message from the vehicle and sends a prompt to the user terminal indicating whether the clearing of the recurring scheduled tasks was successful. This ensures that when the vehicle owner information changes, the recurring scheduled tasks stored locally on the vehicle are promptly cleared, preventing the vehicle from continuing to execute the recurring scheduled tasks set by the previous owner even if the owner changes. Furthermore, after the recurring scheduled tasks stored locally on the vehicle are promptly cleared, prompt information is provided to the user indicating whether the clearing of the recurring scheduled tasks was successful, allowing the user to promptly inform the user whether the recurring scheduled tasks have been cleared.

[0069] In some embodiments, the method further includes steps S701 to S704, wherein:

[0070] Step S701: In response to the new owner account information sent by the user terminal, the original owner account information is cancelled and the new owner account information is activated.

[0071] Here, when a new user binds the new owner account information on the user terminal, the user terminal communicates with the cloud, and the user terminal sends the new owner account information to the cloud. After receiving the new owner account information sent by the user terminal, the cloud cancels the original owner account and activates the new owner account.

[0072] Step S702: Send a cancellation request to the vehicle end; wherein, the cancellation request is used to cancel the original owner's account information and activate the new owner's account information. After receiving the cancellation request, the vehicle end clears the recurring reservation tasks stored locally on the vehicle.

[0073] Here, after the cloud cancels the original owner's account information and activates the new owner's account information, it sends a cancellation request to the vehicle side. After receiving the cancellation request, the vehicle side clears the recurring reservation tasks stored locally in the vehicle.

[0074] Step S703: receiving a clear response message returned by the vehicle end; wherein the clear response message is used to indicate whether the clearing of the cyclic reservation task is successful.

[0075] Here, after clearing the recurring appointment tasks stored locally in the vehicle, the cloud receives a clear response message sent by the vehicle. The clear response message is used to indicate whether the clearing of the recurring appointment tasks is successful, so that the cloud can promptly prompt the user after receiving the clear response message.

[0076] Step S704: Based on the clear response message, a prompt message is sent to the user terminal indicating whether the clearing of the recurring scheduled task is successful.

[0077] Here, after receiving the clear response message, the cloud sends a prompt message to the user terminal indicating whether the clearing of the cyclic reservation task is successful, so that the user can know whether the cyclic reservation task is successfully cleared in time.

[0078] In an embodiment of the present application, after the cloud receives the new owner account information sent by the user terminal, it cancels the original owner account information and activates the new owner account information on the cloud. At the same time, it sends a cancellation request to the vehicle terminal to cancel the original owner account information and activate the new owner account information. After receiving the cancellation request, the vehicle terminal cancels the original owner account information and activates the new owner account information, and clears the recurring scheduled tasks stored locally on the vehicle. After clearing the recurring scheduled tasks stored locally on the vehicle, the cloud terminal receives a clear response message returned by the vehicle terminal to indicate whether the clearing of the recurring scheduled tasks was successful, and sends a prompt message to the user terminal indicating whether the clearing of the recurring scheduled tasks was successful. On the one hand, after the vehicle cancels the original owner account information and activates the new owner account information, the recurring scheduled tasks stored locally on the vehicle are cleared in a timely manner, avoiding the situation where the vehicle still executes the recurring scheduled tasks set by the previous owner even if the owner account information changes. On the other hand, after the recurring scheduled tasks stored locally on the vehicle are cleared in a timely manner, prompt information is provided to the user indicating whether the clearing of the recurring scheduled tasks was successful, so that the user can promptly know whether the recurring scheduled tasks have been cleared in a timely manner.

[0079] The present application provides a synchronization system for cyclically scheduling vehicle tasks, as shown in FIG3 . Before introducing the synchronization system, the following concepts are first introduced:

[0080] 1) In-Vehicle Infotainment (IVI), also known as the vehicle computer, utilizes a dedicated onboard central processing unit (CPU) and leverages the vehicle's bus system and internet services to form a comprehensive in-vehicle information processing system. IVI enables a range of applications, including 3D navigation, real-time traffic conditions, assisted driving, fault detection, vehicle information, body control, mobile office, wireless communications, and online entertainment, significantly enhancing the vehicle's electronic, networked, and intelligent capabilities.

[0081] 2) The in-vehicle communication device (Telematics Box, T-box) is primarily used for communication with the cloud system / mobile app, enabling the mobile app to display and control vehicle information. When a user sends a control command through the mobile app, the cloud sends a monitoring request to the in-vehicle T-box. After receiving the control command, the vehicle sends a control message via the CAN bus to control the vehicle. The operation results are then fed back to the user's mobile app, allowing users to remotely start the vehicle, turn on the air conditioning, adjust the seat to the desired position, and more.

[0082] 3) Telematics Service Provider (TSP), also known as TSP Cloud, includes a cloud-based data processing and analysis platform, as well as a cloud storage service platform. The cloud enables services such as vehicle data analysis, data mining, artificial intelligence algorithms, intelligent maintenance, and predictive maintenance.

[0083] As shown in Figure 3, an embodiment of the present application provides a synchronization system for vehicle cycle reservation tasks, including a mobile phone APP 301, a TSP cloud 302 (including an account management module 303 and a reservation task management module 304), an IVI car machine 305, a T-box 306, and a body domain controller 307 on the vehicle side responsible for executing the air-conditioning function and a power domain controller 308 responsible for executing the charging function.

[0084] When a user sets a recurring appointment task on the mobile phone APP 301, it is transmitted to the TSP cloud 302 via the network. The TSP cloud 302 sends the recurring appointment task to the IVI car machine 305 and the T-box 306 for storage. When the execution conditions of the recurring appointment task are met, such as when the execution time of the recurring appointment task is reached, the IVI car machine 305 or the T-box 306 actively wakes up the vehicle network and sends the corresponding CAN signal to the body domain controller 307 or the power domain controller 308 to execute the corresponding function. At the same time, the TSP cloud 302 feeds back the execution result of the recurring appointment task to the mobile phone APP 301 so that the user can know the execution result of the recurring appointment task in a timely manner. After the user sets a cyclic reservation task on the IVI car computer 305, the cyclic reservation task is saved in the IVI car computer. When the execution conditions of the cyclic reservation task are met, the IVI car computer sends the cyclic reservation task to the T-box 306. After receiving the instruction to execute the cyclic reservation task, the T-box 306 sends the corresponding CAN signal to the body domain controller 307 or the power domain controller 308 to execute the corresponding function.

[0085] FIG4 is a third schematic diagram of an implementation flow of a method for synchronizing a vehicle cyclic reservation task provided by an embodiment of the present application. As shown in FIG4 , the synchronization method includes synchronization methods executed separately by the TSP cloud, the IVI vehicle machine, and the T-box from the perspective of the execution entities (TSP cloud, IVI vehicle machine, and T-box), including the following three cases, among which:

[0086] Case 1: The IVI car machine is the execution entity. After the vehicle is powered on and the network is restored, the IVI car machine compares the locally stored owner account information with the owner account information obtained from the TSP cloud. If they are consistent, it means that the owner account has not changed and there is no need to clear the cyclic reservation task; if the owner account information obtained from the TSP cloud is inconsistent with the locally stored owner account information, it means that the owner account has changed, then the IVI car machine executes to clear the locally stored cyclic reservation task, and at the same time notifies the T-box to clear the local cyclic reservation task. Specifically, it includes the following steps:

[0087] Step S411: The vehicle is powered on and the vehicle network is restored;

[0088] Step S412: Compare local vehicle owner account information;

[0089] After the vehicle is powered on and the network is restored, the IVI car computer compares the locally stored owner account information with the owner account information obtained from the TSP cloud.

[0090] Step S413: whether the vehicle owner has changed;

[0091] The IVI car machine compares the locally stored owner account information with the owner account information obtained from the TSP cloud. If they are consistent, it indicates that the owner account has not changed, and step S414 is executed. If they are inconsistent, it indicates that the owner account has changed, and step S416 is executed.

[0092] Step S414: storing and managing the recurring appointment tasks;

[0093] When the owner's account has not changed, the IVI car computer does not need to clear the cyclic reservation task and still stores the cyclic reservation task.

[0094] Step S415: Detect whether the vehicle software environment is switched;

[0095] The IVI vehicle computer detects whether the vehicle software environment switches between the User Acceptance Testing Environment (UAT), the Performance Testing Environment (Perf), and the application's Production Environment (Pro). When the IVI vehicle computer detects that the vehicle software environment switches between the UAT, Perf, and Pro environments, step S416 is executed; otherwise, step S418 is executed.

[0096] Step S416: Clear the recurring appointment task;

[0097] When the IVI car computer detects a change in the vehicle software environment or a change in the owner's account, it clears the recurring reservation tasks stored locally in the vehicle.

[0098] Step S417: Notify the T-box to clear the cyclic reservation task;

[0099] When the IVI vehicle computer clears the cyclic reservation tasks stored locally in the vehicle, it sends an instruction to clear the cyclic reservation tasks to the T-box, and then executes step S431, and the T-box clears the cyclic reservation tasks stored locally in the vehicle.

[0100] Step S418: Check whether the appointment time has arrived;

[0101] When the IVI vehicle computer detects that the vehicle software environment has not changed, it checks whether the scheduled time of the cyclic scheduled task has arrived. If so, step S419 is executed.

[0102] Step S419: Wake up the network and send an execution signal to start charging;

[0103] After the IVI vehicle computer detects that the scheduled time of the cyclic scheduled task has arrived, it wakes up the vehicle CAN network, sends an execution signal to start charging, and executes step S441.

[0104] Step S441: Turn on the charging function.

[0105] Case 2: The TSP cloud is the execution entity. When the user sets a recurring appointment task on the mobile APP, it will be uploaded to the TSP cloud. The TSP cloud will store and manage the recurring appointment task. After the TSP cloud receives the recurring appointment task, it will immediately send it to the IVI car machine and T-box. After the IVI car machine and T-box receive the recurring appointment task, they must store it locally. When the user performs the owner unbinding operation or adds a new owner and cancels the original owner information on the mobile APP, the owner information change instruction will be sent to the TSP cloud. After receiving the owner information change instruction, the TSP cloud will send a message instruction to clear the recurring appointment task to the IVI car machine and T-box. If the vehicle is in the power-on running state at this time, the IVI car machine and T-box will immediately clear the local recurring appointment task after receiving the message instruction to clear the recurring appointment task. Specifically including the following steps:

[0106] Step S400: Setting a recurring appointment task on the mobile phone;

[0107] The user sets a recurring scheduled task on the mobile phone, including a recurring scheduled task such as recurring scheduled turning on the air conditioner or recurring scheduled charging, and uploads the recurring scheduled task to the TSP cloud, and executes step S421.

[0108] Step S421: Storing and managing recurring appointment tasks;

[0109] After receiving the recurring reservation task, the TSP cloud stores the recurring reservation task. After storing the recurring reservation task, the TSP cloud performs steps S414 and S431, and the IVI vehicle machine and the T-box respectively store the recurring reservation task.

[0110] Step S422: Detect whether the vehicle owner information has changed;

[0111] After storing the recurring reservation task in the TSP cloud, it is detected whether the owner information has changed. If so, step S423 is executed; if not, step S415 is executed.

[0112] Step S423: issuing an instruction to clear the recurring scheduled task;

[0113] When the owner information changes, the TSP cloud sends instructions to the IVI vehicle computer and T-box respectively to clear the cyclic reservation task, and then executes steps S414 and S431, and the IVI vehicle computer and T-box respectively clear the cyclic reservation task.

[0114] Case three: T-box is the execution entity. After the vehicle is powered on and the network is restored, the IVI car computer compares the locally stored owner account information with the owner account information obtained from the TSP cloud. If the owner account information has not changed, the T-box stores the cyclic appointment task. When the subsequent detection reaches the execution time of the cyclic appointment task, the T-box wakes up the vehicle network and sends the corresponding CAN signal to the execution controller to execute the corresponding function. In the case of a change in the owner account information, the IVI car computer executes the clearing of the locally stored cyclic appointment task and notifies the T-box to clear the local cyclic appointment task. Specifically including the following steps:

[0115] Step S411: The vehicle is powered on and the vehicle network is restored;

[0116] Step S412: Compare local vehicle owner account information;

[0117] After the vehicle is powered on and the network is restored, the IVI car computer compares the locally stored owner account information with the owner account information obtained from the TSP cloud.

[0118] Step S413: whether the vehicle owner has changed;

[0119] The IVI car machine compares the locally stored owner account information with the owner account information obtained from the TSP cloud. If they are consistent, it indicates that the owner account has not changed, and step S431 is executed. If they are inconsistent, it indicates that the owner account has changed, and step S416 is executed to clear the locally stored recurring reservation tasks.

[0120] Step S431: Storing and managing recurring appointment tasks;

[0121] If the owner's account information has not changed, the T-box does not need to clear the recurring reservation tasks stored locally in the vehicle and will continue to store the recurring reservation tasks.

[0122] Step S432: Check whether the appointment time has arrived;

[0123] When the owner's account information has not changed, the T-box detects whether the scheduled time of the recurring scheduled task has arrived. If so, step S433 is executed.

[0124] Step S433: Wake up the network and send an execution signal to turn on the air conditioner;

[0125] After detecting that the scheduled time of the cyclic scheduled task has arrived, the T-box wakes up the vehicle CAN network, sends an execution signal to turn on the air conditioner, and executes step S442.

[0126] Step S442: Turn on the air conditioner.

[0127] In the embodiment of the present application, when a change in the owner's account information or a change in the vehicle's software environment is detected, the vehicle's locally stored cyclic scheduled tasks are promptly cleared to avoid the vehicle still executing the locally stored cyclic scheduled tasks even when the owner or vehicle software environment changes.

[0128] Figure 5 is a schematic diagram of the composition structure of a synchronization device for a vehicle cyclic reservation task provided in an embodiment of the present application. As shown in Figure 5, the synchronization device 500 includes: a first receiving module 501, used to receive an unbinding and clearing request message sent from the cloud; wherein, the unbinding and clearing request message is used to unbind the first vehicle owner account information and clear the cyclic reservation task; a first clearing module 502, used to determine the first cyclic reservation task stored locally on the vehicle that is bound to the first vehicle owner account information in response to the unbinding and clearing request message, and clear the first cyclic reservation task.

[0129] In some embodiments, the synchronization device 500 also includes: an acquisition module, which is used to obtain the first vehicle owner account information from the cloud after the vehicle side is powered on, and obtain the second vehicle owner account information stored locally in the vehicle; a second clearing module, which is used to determine the second cyclic reservation task bound to the second vehicle owner account information when the first vehicle owner account information is inconsistent with the second vehicle owner account information, and clear the second cyclic reservation task.

[0130] In some embodiments, the synchronization device 500 also includes: a second receiving module, used to receive a change and clear request message sent from the cloud when the first vehicle owner account information is changed to the third vehicle owner account information; wherein, the change and clear request message is used to cancel the first vehicle owner account information and activate the third vehicle owner account information, and clear the recurring reservation task; a third clearing module, used to clear the first recurring reservation task in response to the change and clear request message.

[0131] In some embodiments, the synchronization device 500 also includes: a fourth clearing module, which is used to determine the third cyclic scheduled task stored locally in the vehicle bound to the first software environment and clear the third cyclic scheduled task when the software environment of the vehicle is switched from the first software environment to the second software environment.

[0132] Figure 6 is a second schematic diagram of the composition structure of a synchronization device for a vehicle cyclic reservation task provided in an embodiment of the present application. As shown in Figure 6, the synchronization device 600 is applied to the cloud, including: a third receiving module 601, for receiving an unbinding request sent by a user terminal; wherein the unbinding request is used to request the unbinding of the person-vehicle relationship; a first sending module 602, for responding to the unbinding request, sending an unbinding and clearing message to the vehicle end; wherein the unbinding and clearing message is used to unbind the bound vehicle owner account information and clear the cyclic reservation task; a fourth receiving module 603, for receiving an unbinding and clearing response message returned by the vehicle end; wherein the unbinding and clearing response message is used to indicate whether the unbinding and clearing are successful; a second sending module 604, for sending a prompt message to the user terminal whether the unbinding and clearing are successful based on the unbinding and clearing response message.

[0133] In some embodiments, the synchronization device 600 also includes: a third sending module, used to respond to the owner account sending request sent by the vehicle end, and send the first owner account information stored in the cloud to the vehicle end; wherein, the first owner account information is used to compare with the second owner account information stored locally in the vehicle, and when the first owner account information and the second owner account information are inconsistent, the recurring reservation task stored locally in the vehicle is cleared; a fifth receiving module, used to receive a clear response message returned by the vehicle end; wherein, the clear response message is used to indicate whether the clearing of the recurring reservation task is successful; a fourth sending module, used to send a prompt message to the user terminal based on the clear response message, indicating whether the clearing of the recurring reservation task is successful.

[0134] In some embodiments, the synchronization device 600 also includes: a deregistration module, used to cancel the original owner account information and activate the new owner account information in response to the new owner account information sent by the user terminal; a fifth sending module, used to send a deregistration request to the vehicle end; wherein, the deregistration request is used to cancel the original owner account information and activate the new owner account information, and the vehicle end clears the recurring reservation tasks stored locally on the vehicle after receiving the deregistration request; a sixth receiving module, used to receive a clear response message returned by the vehicle end; wherein, the clear response message is used to indicate whether the clearing of the recurring reservation task is successful; the sixth sending module is used to send a prompt message to the user terminal based on the clear response message whether the clearing of the recurring reservation task is successful.

[0135] The description of the above device embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to perform the methods described in the above method embodiments. For technical details not disclosed in the device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

[0136] An embodiment of the present application provides a synchronization device for vehicle cycle reservation tasks. When implemented, the device can be a computer device (such as a laptop computer, a desktop computer, a server cluster, etc.), including a processor and a memory, the memory being used to store a computer program; the processor being used to execute the computer program stored in the memory to implement the above method.

[0137] An embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method is implemented. The computer-readable storage medium can be transient or non-transient.

[0138] It should be noted that in the embodiments of the present application, if the above-mentioned method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for executing all or part of the above-mentioned methods of 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 magnetic disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific hardware, software or firmware, or any combination of hardware, software and firmware.

[0139] An embodiment of the present application provides a computer program, including computer-readable code. When the computer program is running, the processor executes some or all of the steps for implementing the above method.

[0140] An embodiment of the present application provides a computer program product, comprising a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, the computer program implements some or all of the steps of the above-described method. The computer program product can be implemented in hardware, software, or a combination thereof. In some embodiments, the computer program product is embodied as a computer storage medium. In other embodiments, the computer program product is embodied as a software product, such as a software development kit (SDK).

[0141] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between the various embodiments, and their similarities or similarities can be referenced to each other. The descriptions of the above device, storage medium, computer program, and computer program product embodiments are similar to the descriptions of the above method embodiments and have similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the description of the method embodiments of this application for understanding.

[0142] FIG7 is a schematic diagram of the structure of a synchronization device for a vehicle cycle reservation task provided by an embodiment of the present application. As shown in FIG7 , the hardware entity of the device 700 includes: a processor 701, a communication interface 702, and a memory 703, wherein:

[0143] Processor 701 generally controls the overall operation of device 700 .

[0144] The communication interface 702 enables the device to communicate with other terminals or servers through a network.

[0145] Memory 703 is configured to store instructions and applications executable by processor 701. It can also cache data to be processed or processed by processor 701 and various modules in device 700 (e.g., image data, audio data, voice communication data, and video communication data). This can be implemented using flash memory (FLASH) or random access memory (RAM). Data can be transmitted between processor 701, communication interface 702, and memory 703 via bus 704.

[0146] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification characterizes that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned steps / processes does not represent the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not characterize the advantages and disadvantages of the embodiments.

[0147] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0148] In the several embodiments provided in this application, it should be understood that the disclosed devices, equipment and methods can be implemented in other ways. The device and equipment embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0149] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed across multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0150] In addition, all functional units in the embodiments of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the above-mentioned integrated units can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0151] Those skilled in the art will understand that all or part of the steps of the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, and other media that can store program codes.

[0152] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a device to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks or optical disks.

[0153] The above is only an implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. A method for synchronizing vehicle cyclic reservation tasks, applied to a vehicle side, the method comprising: Receive an unbinding and clearing request message sent by the cloud; wherein the unbinding and clearing request message is used to unbind the first vehicle owner account information and clear the recurring reservation task; In response to the unbinding and clearing request message, a first recurring scheduled task stored locally in the vehicle that is bound to the first vehicle owner account information is determined, and the first recurring scheduled task is cleared.

2. The method according to claim 1, wherein The method further comprises: After the vehicle is powered on, obtaining the first vehicle owner account information from the cloud, and obtaining the second vehicle owner account information stored locally in the vehicle; When the first vehicle owner account information is inconsistent with the second vehicle owner account information, a second cyclic scheduled task bound to the second vehicle owner account information is determined, and the second cyclic scheduled task is cleared.

3. The method according to claim 1, wherein The method further comprises: When the first vehicle owner account information is changed to a third vehicle owner account information, receiving a change and clear request message sent from the cloud; wherein the change and clear request message is used to cancel the first vehicle owner account information and activate the third vehicle owner account information, and clear the recurring reservation task; In response to the change and clear request message, the first recurring scheduled task is cleared.

4. The method according to any one of claims 1 to 3, wherein: The method further comprises: When the software environment of the vehicle is switched from the first software environment to the second software environment, a third cyclic scheduled task locally stored in the vehicle bound to the first software environment is determined, and the third cyclic scheduled task is cleared.

5. A method for synchronizing vehicle cycle reservation tasks, applied to the cloud, comprising: Receiving an unbinding request sent by a user terminal; wherein the unbinding request is used to request unbinding of a person-vehicle relationship; In response to the unbinding request, an unbinding and clearing message is sent to the vehicle end; wherein the unbinding and clearing message is used to unbind the bound vehicle owner account information and clear the recurring reservation task; Receive the unbinding and clearing response message returned by the vehicle end; wherein the unbinding and clearing response message is used to indicate whether the unbinding and clearing are successful; Based on the unbinding and clearing response message, prompt information indicating whether the unbinding and clearing is successful is sent to the user terminal.

6. The method according to claim 5, wherein: The method further comprises: In response to the vehicle-side request for sending the vehicle owner account, sending the first vehicle owner account information stored in the cloud to the vehicle-side; wherein the first vehicle owner account information is used to compare with the second vehicle owner account information stored locally in the vehicle, and if the first vehicle owner account information and the second vehicle owner account information are inconsistent, clearing the recurring scheduled tasks stored locally in the vehicle; Receive a clear response message returned by the vehicle end; wherein the clear response message is used to indicate whether the clearing of the cyclic reservation task is successful; Based on the clear response message, prompt information indicating whether the clearing of the recurring scheduled task is successful is sent to the user terminal.

7. The method according to claim 5 or 6, wherein: The method further comprises: In response to the new owner account information sent by the user terminal, cancel the original owner account information and activate the new owner account information; Sending a cancellation request to the vehicle; wherein the cancellation request is used to cancel the original owner's account information and activate the new owner's account information, and the vehicle clears the recurring reservation tasks stored locally on the vehicle after receiving the cancellation request; Receive a clear response message returned by the vehicle end; wherein the clear response message is used to indicate whether the clearing of the cyclic reservation task is successful; Based on the clear response message, prompt information indicating whether the clearing of the recurring scheduled task is successful is sent to the user terminal.

8. A synchronization device for a vehicle's cyclic reservation task, applied to a vehicle, the synchronization device comprising: A first receiving module is configured to receive an unbinding and clearing request message sent from the cloud; wherein the unbinding and clearing request message is used to unbind the bound first vehicle owner account information and clear the recurring reservation task; The first clearing module is used to determine the first recurring scheduled task stored locally in the vehicle that is bound to the first vehicle owner account information in response to the unbinding and clearing request message, and clear the first recurring scheduled task.

9. A synchronization device for a vehicle cycle reservation task, the synchronization device comprising a processor and a memory: The memory is used to store computer programs; The processor is configured to execute the computer program stored in the memory to implement the steps of the method according to any one of claims 1 to 4, or to implement the steps of the method according to any one of claims 5 to 7.

10. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 or the steps of the method according to any one of claims 5 to 7 are implemented.

Images