Vehicle control method and device, electronic equipment and vehicle

Abstract

The invention provides a vehicle control method and device, electronic equipment and a vehicle, and is applied to the technical field of vehicle intelligent control, and the method comprises the steps: responding to a received remote control request of a user, and determining the human-vehicle relation information of the user and the vehicle, and the request information of the user; determining a target control authority of the user to the vehicle based on the human-vehicle relationship information; and calling a service interface corresponding to the request information to execute the remote control request based on the matching relationship between the request information and the target control permission. The application ensures that the user can only execute the operation allowed in the target control authority, accurately executes the remote control request, effectively prevents the execution of the unauthorized remote control request, and brings convenience to the user while improving the safety of the vehicle.

Description

Technical Field

[0001] The present application relates to the field of vehicle intelligent control technology, and in particular to a vehicle control method, device, electronic equipment and vehicle. Background Art

[0002] Smart vehicles can not only provide basic driving functions, but also realize intelligent operations such as automatic driving and remote control through advanced information technology and network communication technology, which greatly improves the safety and convenience of driving. However, due to the inability to accurately verify and manage the authority relationship between users and vehicles, remote control requests cannot be accurately and successfully executed. Summary of the invention

[0003] In view of this, the purpose of the present application is to propose a vehicle control method, device, electronic device and vehicle to accurately execute the user's remote control request while ensuring the safety of the vehicle.

[0004] Based on the above purpose, the present application provides a vehicle control method, which is applied to a telematics processor of the vehicle; the method comprises: in response to receiving a remote control request from a user, determining the person-vehicle relationship information between the user and the vehicle, and the user's request information;

[0005] Based on the person-vehicle relationship information, determining the user's target control authority over the vehicle;

[0006] Based on the matching relationship between the request information and the target control authority, a service interface corresponding to the request information is called to execute the remote control request.

[0007] Based on the same inventive concept, the present application also provides a vehicle control device, including:

[0008] A judgment module is configured to determine, in response to receiving a remote control request from a user, the person-vehicle relationship information between the user and the vehicle, and the user's request information; and determine the user's target control authority over the vehicle based on the person-vehicle relationship information;

[0009] An execution module is configured to call a service interface corresponding to the request information to execute the remote control request based on a matching relationship between the request information and the target control authority.

[0010] Based on the same inventive concept, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method as described above when executing the computer program.

[0011] Based on the same inventive concept, the present application also provides a vehicle, which includes the above-mentioned electronic device.

[0012] From the above, it can be seen that the present application provides a vehicle control method, device, electronic device and vehicle, wherein the method is applied to the remote information processor of the vehicle, and the method includes: in response to receiving a user's remote control request, determining the person-vehicle relationship information between the user and the vehicle, and the user's request information; based on the person-vehicle relationship information, determining the user's target control authority over the vehicle, that is, determining whether there is a person-vehicle binding relationship based on the person-vehicle binding information, ensuring that only users with a person-vehicle binding relationship can operate the vehicle; if it is determined that there is a person-vehicle binding relationship, obtaining a permission tree and determining the user's target control authority level based on the permission tree; and determining the target control authority level corresponding to the target control authority level. Permission, that is, determining the remote control requests that are allowed to be executed by the target control permission corresponding to the target control permission level; based on the matching relationship between the request information and the target control permission, calling the service interface corresponding to the request information to execute the remote control request, ensuring that the user can only execute the operations allowed within his target control permission. Each remote control request can be traced back to the user with clear target control permission, effectively preventing the execution of unauthorized remote control requests. At the same time, directly calling the service interface corresponding to the request information to execute the remote control request through the remote information processor improves the execution efficiency and accuracy of the remote control request, improves vehicle safety and brings convenience to users. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0014] Figure 1 The process diagram of the vehicle control method of the present application embodiment is as follows: Figure 1 ;

[0015] Figure 2 The process diagram of the vehicle control method of the present application embodiment is as follows: Figure 2 ;

[0016] Figure 3 A schematic diagram of a vehicle control device according to an embodiment of the present application;

[0017] Figure 4 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0019] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0020] In the related technologies, with the rapid development of science and technology and the accelerated pace of people's lives, travel efficiency and comfortable experience have become important needs in people's daily lives. As one of the main means of transportation, the development trend of automobiles towards intelligence and networking has become the mainstream of the industry. Intelligent vehicles can not only provide basic driving functions, but also realize intelligent operations such as automatic driving and remote control of vehicles through advanced information technology, network communication technology, etc., which greatly improves the safety and convenience of driving. Although vehicles can realize a variety of intelligent functions through remote control, it is necessary to access user data in the cloud and perform corresponding operations according to the permission information provided by the cloud, which may cause delays in control commands and affect the real-time nature of remote control, especially in the case of unstable network. In addition, due to the inability to accurately verify and manage the permission relationship between users and vehicles, remote control requests cannot be accurately and successfully executed, and the user's car experience is still poor. Moreover, for remote control requests that are scheduled to be executed, the time when users use the vehicle is not completely certain. When users schedule to execute remote control requests, it is easy for users to need to use the car but the remote control request is not executed because the time for the scheduled execution of the remote control request has not arrived, which affects the user's car experience.

[0021] Based on the above problems, the applicant found that the following scheme is implemented through the vehicle's telematics processor (i.e., T-BOX): when a user's remote control request is received, the person-vehicle relationship information between the user and the vehicle, and the user's request information are determined; based on the person-vehicle relationship information, the user's target control authority over the vehicle is determined, that is, whether there is a person-vehicle binding relationship is determined according to the person-vehicle binding information; if it is determined that there is a person-vehicle binding relationship, the permission tree is obtained and the user's target control authority level is determined according to the permission tree; to determine the target control authority corresponding to the target control authority level; based on the matching relationship between the request information and the target control authority, the service interface corresponding to the request information is called to execute the remote control request, ensuring that the user can only perform operations allowed within his target control authority, accurately executing remote control requests, and effectively preventing the execution of unauthorized remote control requests, thereby improving vehicle safety and bringing convenience to users. When it is determined that the remote control request is a remote control request for scheduled execution, the scheduled execution time for executing the remote control request is obtained, and the predicted execution time for executing the remote control request is determined based on the user's historical remote control data. According to the difference between the scheduled execution time and the predicted execution time, it is determined whether to execute the remote control request at the predicted execution time or at the scheduled execution time. This can more effectively manage the execution of remote control requests, more accurately determine the execution time of remote control requests, and complete necessary vehicle control before the user arrives at the vehicle. At the same time, since the operation is performed directly through the telematics processor, the execution efficiency of the remote control request is improved.

[0022] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0023] The present application provides a vehicle control method, such as Figure 1 As shown, in some embodiments, the method is executed by a telematics processor of the vehicle, and the subsequent embodiments are all illustrated by taking the telematics processor as an example; the method includes:

[0024] S101, in response to receiving a remote control request from a user, determining the person-vehicle relationship information between the user and the vehicle, and the user's request information;

[0025] In specific implementation, when a user issues a remote control request, it is first necessary to confirm whether the user has the right to control the vehicle, verify the user's identity and confirm the relationship between the user and the vehicle, determine the person-vehicle relationship information of the user and the vehicle, and at the same time confirm the user's request information. The request information is the specific operation the user wishes to perform.

[0026] S102, determining the user's target control authority over the vehicle based on the person-vehicle relationship information;

[0027] In specific implementation, the user's target control authority over the vehicle is determined based on the person-vehicle relationship information. The target control authority determines the specific scope of operations that the user can perform, including which remote control requests the user can control and under what conditions the remote control requests can be executed. Specifically, it can be determined whether there is a person-vehicle binding relationship based on the person-vehicle binding information; if it is determined that there is a person-vehicle binding relationship, the authority tree is obtained, and the user's target control authority level is determined based on the authority tree; the target control authority corresponding to the target control authority level is determined. By determining the user's target control authority over the vehicle, it can ensure that each remote control operation is reasonable and safe, and enhance the user's trust and satisfaction with the remote control function of the smart vehicle.

[0028] S103: Based on the matching relationship between the request information and the target control authority, call a service interface corresponding to the request information to execute the remote control request.

[0029] During specific implementation, it is necessary to determine the matching relationship between the request information and the target control authority, that is, to verify whether the remote control request complies with the user's target control authority, and to ensure that the operation of the remote control request does not exceed the user's authorization scope. When it is determined that the request information is within the target control authority, the service interface corresponding to the request information can be called to execute the remote control request; the service interface includes but is not limited to interfaces corresponding to services such as starting the engine, adjusting the air conditioner, and operating the windows. Interface calls require a high degree of security protection, such as using secure communication protocols and data encryption to prevent data leakage or tampering. By calling the service interface corresponding to the request information to execute the remote control request based on the matching relationship between the request information and the target control authority, it can be ensured that the operation of the vehicle remote control system is both safe and efficient, while providing a good user experience.

[0030] In this embodiment, based on the person-vehicle relationship information, the user's target control authority over the vehicle is determined. By strictly verifying the user's identity and the relationship with the vehicle, it is ensured that only users whose request information matches the target control authority can perform remote control operations, reducing the risk of illegal access and manipulation. For example, it is determined whether there is a person-vehicle binding relationship based on the person-vehicle binding information. If it is determined that there is a person-vehicle binding relationship, the permission tree is obtained, and the user's target control authority level is determined based on the permission tree; the target control authority corresponding to the target control authority level is determined; the user can remotely control the vehicle based on his or her target control authority, such as starting the engine, adjusting the air conditioner, etc., which provides great convenience and comfort. In general, through precise permission control and request processing, not only the safety and efficiency of vehicle use are improved, but also the user's overall vehicle experience is greatly improved.

[0031] Based on the above embodiment, the calling of the service interface corresponding to the request information to execute the remote control request based on the matching relationship between the request information and the target control authority is described in detail to ensure that the operation of the remote control request does not exceed the authorization scope of the user. The calling of the service interface corresponding to the request information to execute the remote control request based on the matching relationship between the request information and the target control authority includes:

[0032] In response to determining that the request information is within the target control authority, calling a service interface corresponding to the request information to execute the remote control request;

[0033] In the specific implementation, it is necessary to determine whether the operation requested by the user is within the authorized operation scope, that is, to determine whether the request information is within the target control authority. If it is determined that the request information is within the target control authority, the service interface corresponding to the request information is called to execute the remote control request; wherein, the remote control request can be executed by calling the service interface corresponding to the request information through the vehicle network. To ensure communication security, encryption protocols and security authentication mechanisms may be required to protect data security and integrity during data transmission. This step can ensure that when the request information of the user's remote control request is within its target control authority, the remote control request can be executed safely and accurately, providing a good user experience and a high degree of system security.

[0034] In response to determining that the request information is outside the target control authority, the user's target control authority for the vehicle is adjusted based on the person-vehicle relationship information so that the request information matches the adjusted target control authority, and the service interface corresponding to the request information is called to execute the remote control request.

[0035] In specific implementation, when it is determined that the request information is outside the target control authority, that is, the user's remote control request exceeds its current control authority, the remote control request will not be rejected immediately, but an attempt will be made to adjust the user's target control authority based on the existing person-vehicle relationship information between the user and the vehicle, such as adjusting the user's target control authority for the vehicle based on the number of times the user has logged into the vehicle within a first preset historical time period. If the adjusted request information is within the target control authority, the service interface corresponding to the request information is called to execute the remote control request. Before adjusting the target control authority, additional security reviews can be performed, such as confirming the user's identity through multi-factor authentication, or reviewing the user's historical operation records to assess their trustworthiness, which helps prevent unauthorized operations and potential security risks. At the same time, remote control requests that exceed the current target control authority can also be flexibly handled, which not only ensures the security of executing remote control requests, but also improves user experience.

[0036] In this embodiment, the operation is performed only when the user's request information matches the target control authority, and the service interface corresponding to the request information is called to execute the remote control request. By determining the user's target control authority for the vehicle, it can be ensured that each remote control operation is reasonable and safe, thereby ensuring that the operation of the remote control request does not exceed the user's authorization scope, maintaining strict control of safety, and adjusting the user's target control authority for the vehicle based on the person-vehicle relationship information can reduce request rejections caused by authority issues, thereby improving the overall efficiency and response speed of the system. Users do not have to try or contact customer service multiple times due to authority issues, thereby improving the convenience and efficiency of operations.

[0037] Based on the above embodiment, the determination of the user's target control authority over the vehicle based on the person-vehicle relationship information is described in detail to ensure that each remote control request can be traced back to a user with clear authority, thereby ensuring the safety of the operation. Figure 2 As shown, the person-vehicle relationship information includes person-vehicle binding information and a permission tree; and determining the user's target control authority over the vehicle based on the person-vehicle relationship information includes:

[0038] S201, determining whether there is a person-vehicle binding relationship according to the person-vehicle binding information;

[0039] In specific implementation, it is necessary to store the person-vehicle binding information through a database or data management system. The person-vehicle binding information includes but is not limited to the user's identity details, the vehicle's unique identifier, the person-vehicle binding relationship, the binding validity period, etc. When a user initiates a remote control request, the person-vehicle binding information is queried to confirm whether there is a person-vehicle binding relationship, so as to effectively manage and verify the person-vehicle binding information and ensure that only users with a person-vehicle binding relationship can operate the vehicle, which not only enhances the security of the system, but also improves user trust and satisfaction.

[0040] S202, in response to determining that there is a person-vehicle binding relationship, obtaining a permission tree, and determining a target control permission level of the user according to the permission tree;

[0041] In specific implementation, after confirming that there is a binding relationship between the user and the vehicle, the permission tree is obtained, and the user's target control permission level is determined according to the permission tree. The permission tree is a structured data model used to define the target control permission level of different users or user groups for the vehicle. Usually, the target control permission level at the root node of the permission tree is the highest, and its corresponding target control permission is allowed to execute all remote control requests. For the target control permission level at the branch node of the permission tree, its corresponding target control permission is allowed to execute some remote control requests, such as only accessing the door locking and unlocking functions.

[0042] S203: Determine the target control authority corresponding to the target control authority level.

[0043] In specific implementation, after confirming the user's target control authority level, it is necessary to find the corresponding target control authority according to the target control authority level. The target control authority defines the specific vehicle remote control operations that the user can perform. Ensure that the user can only perform operations allowed within his target control authority, thereby maintaining the security and integrity of the system and effectively preventing unauthorized operations.

[0044] In this embodiment, users can clearly understand which operations can be performed according to their target control permission level. The structured management of the person-vehicle binding information and permission tree allows vehicle owners or managers to easily add, modify or delete user permissions, which facilitates system maintenance and updates. Each remote control request can be traced back to a user with clear permissions, which not only ensures the safety of the operation, but also optimizes the user experience and system management.

[0045] Based on the above embodiment, the method of adjusting the user's target control authority over the vehicle based on the person-vehicle relationship information is described in detail to ensure that only users who frequently and legally use the vehicle can obtain higher authority. The person-vehicle relationship information includes the number of times the user has logged into the vehicle within a first preset historical time period; the method of adjusting the user's target control authority over the vehicle based on the person-vehicle relationship information includes:

[0046] In response to determining that the number of times the user has logged into the vehicle within a first preset historical time period is greater than or equal to a preset number of times, and the target control authority level of the user is at a branch node, adjusting the target control authority level of the user to a root node;

[0047] In specific implementation, it is usually necessary to query the time when the user logs in to the vehicle and determine the number of times the user logs in to the vehicle within the first preset historical duration (exemplarily, the first preset historical duration can be set to 24 hours). When it is determined that the number of times the user logs in to the vehicle within the first preset historical duration is greater than or equal to the preset number of times (exemplarily, the preset number of times can be set to 1 time), it indicates that the user frequently uses the vehicle within the first preset historical duration, and the user's trustworthiness is high. At this time, if the user's target control authority level is at a branch node, the user's target control authority level can be adjusted to the root node so that the user's remote control request can be executed smoothly, which can not only flexibly adjust the target control authority level according to the user's actual use, but also ensure the security and transparency of the entire process, help improve user satisfaction, and ensure the stability and security of the system. When the user's authority level is adjusted, the user can be notified to inform the details and reasons of the change in the target control authority level. It can be understood that in response to determining that the number of times the user logs in to the vehicle within the first preset historical duration is greater than or equal to the preset number of times, and the user's target control authority level is at a leaf node, it indicates that the user's target control authority level is the lowest. At this time, in order to ensure the safety of the vehicle, the user's target control authority level will not be adjusted.

[0048] A target control authority corresponding to the target control authority level adjusted to the root node is determined.

[0049] In specific implementation, after confirming the user's target control authority level, it is necessary to find the corresponding target control authority according to the target control authority level. The target control authority defines the specific vehicle remote control operations that the user can perform. Ensure that the user can only perform operations allowed within his target control authority, thereby maintaining the security and integrity of the system and effectively preventing unauthorized operations.

[0050] In this embodiment, by dynamically adjusting permissions by considering the number of times the user logs into the vehicle within the first preset historical time period, such as adjusting the user's target control permission level to the root node, it can more flexibly adapt to user needs and ensure that only users who truly use the vehicle frequently and legally can obtain higher permissions so that the user's remote control request can be executed smoothly, which helps prevent unauthorized operations and potential security threats, while enabling the user's remote control request to be executed smoothly.

[0051] Based on the above embodiment, the calling of the service interface corresponding to the request information to execute the remote control request is described in detail to ensure that the vehicle is in the best state when the user arrives and improve the efficiency of executing the remote control request. The calling of the service interface corresponding to the request information to execute the remote control request includes:

[0052] In response to determining that the remote control request is a remote control request for scheduled execution, obtaining a scheduled execution time for executing the remote control request, and determining a predicted execution time for executing the remote control request based on historical remote control data of the user;

[0053] In specific implementation, when it is determined that the remote control request is a remote control request for scheduled execution, that is, when the user initiates the remote control request, he specifies a specific time when he hopes to execute the remote control request. At this time, the scheduled execution time for executing the remote control request is obtained, and the predicted execution time for executing the remote control request is determined based on the user's historical remote control data. The predicted execution time may be different from the scheduled execution time set by the user. The predicted execution time helps to optimize the execution of the remote control request, making it more in line with the actual needs of the user, and making the execution of the remote control request more in line with the actual behavior and expectations of the user, which helps to improve the overall efficiency of the remote control request execution and user satisfaction.

[0054] In response to determining that the difference between the scheduled execution time and the predicted execution time is less than or equal to a preset difference, executing the remote control request at the predicted execution time;

[0055] In specific implementation, the preset difference defines the maximum acceptable difference between the scheduled execution time and the predicted execution time. This value can be set based on historical data and user feedback to ensure that both user needs are met and the timeliness and relevance of the operation are maintained. Exemplarily, the preset difference can be set to 1 hour. When it is determined that the difference between the scheduled execution time and the predicted execution time is less than or equal to the preset difference, indicating that the difference between the scheduled execution time and the predicted execution time is small, the remote control request is executed at the predicted execution time, which can more effectively manage the execution of the remote control request, more accurately determine the execution time of the remote control request, and complete the necessary vehicle control before the user arrives at the vehicle, thereby improving the execution efficiency of the remote control request and user satisfaction.

[0056] In response to determining that the difference between the scheduled execution time and the predicted execution time is greater than a preset difference, executing the remote control request at the scheduled execution time.

[0057] During specific implementation, when it is determined that the difference between the scheduled execution time and the predicted execution time is greater than the preset difference, it indicates that there is a large deviation between the predicted execution time and the user's scheduled execution time. At this time, the user's scheduled execution time is given priority to ensure the intuitiveness and certainty of user control, so as to ensure the accuracy and safety of operations while ensuring user control and meeting user expectations.

[0058] In this embodiment, by considering the user's scheduled execution time and predicted execution time, if the difference between the scheduled execution time and the predicted execution time is less than or equal to the preset difference, the remote control request is executed at the predicted execution time, and if the difference between the scheduled execution time and the predicted execution time is greater than the preset difference, the remote control request is executed at the scheduled execution time, which can more accurately meet the needs of the user. Selecting the predicted execution time can optimize the use of the vehicle according to the user's actual behavior pattern, such as preheating or cooling the vehicle in advance, thereby improving energy efficiency and the immediate availability of the vehicle. Waiting and preparation time is reduced, ensuring that the vehicle is in the best condition when the user arrives, which not only improves the user experience, but also improves the efficiency of execution.

[0059] Based on the above embodiment, the method of determining the predicted execution time of executing the remote control request according to the user's historical remote control data is described in detail, so as to more accurately predict the future remote control request execution time, so that the remote control operation better meets the actual needs of the user. The historical remote control data includes multiple execution times of the remote control request within a second preset historical time length; the method of determining the predicted execution time of executing the remote control request according to the user's historical remote control data includes:

[0060] Sort multiple execution times in time to obtain a time series table;

[0061] In specific implementation, it is necessary to collect multiple execution times of the remote control request of the user within a second preset historical time period from a database or other data storage (for example, the second preset historical time period can be set to one month). The collected execution times are sorted in chronological order, usually by comparing timestamps and sorting algorithms of arrays or lists to obtain a time series table.

[0062] Determine the average time interval between two adjacent execution times in the time series table;

[0063] In specific implementation, after obtaining the time series table, the time interval between two adjacent execution times will be calculated to obtain multiple time intervals, and the average of multiple time intervals will be calculated to obtain the average time interval to analyze the frequency and regularity of user remote control requests, thereby helping to predict the user's future car usage habits.

[0064] In response to determining that the average time interval is less than or equal to the preset time interval, an execution time at a middle position in the time series table is determined as the predicted execution time.

[0065] In specific implementation, when it is determined that the average time interval is less than or equal to the preset time interval (for example, the preset time interval can be set to 10 minutes), it indicates that the user's remote control request has a certain regularity, and the execution time in the middle of the time series table is determined as the predicted execution time. If the length of the time series table is an odd number, the time point in the middle is directly selected as the predicted execution time; if it is an even number, it is necessary to take the average of the two middle time points or select one of them as the predicted execution time, so as to effectively predict the execution time of the user's remote control request, optimize the response time of the service and improve the overall user experience.

[0066] In this embodiment, by sorting multiple execution times in time to obtain a time series table, the average time interval between two adjacent execution times is determined, and the user's historical remote control data is used to identify the pattern of the user's remote control request execution. If the average time interval is less than or equal to the preset time interval, the execution time in the middle of the time series table is determined as the predicted execution time, thereby more accurately predicting the future remote control request execution time, improving the accuracy of the prediction, and making the remote control operation more in line with the user's actual needs. For example, the vehicle can automatically adjust to a suitable temperature before the user arrives, or start in advance, greatly enhancing the user's car experience.

[0067] Based on the above embodiment, the method of determining the predicted execution time of executing the remote control request according to the user's historical remote control data is described in detail, so as to more accurately predict the future remote control request execution time, so that the remote control operation is more in line with the actual needs of the user. The historical remote control data includes the number of executions of the remote control request at the scheduled execution time within the second preset historical time length; the method of determining the predicted execution time of executing the remote control request according to the user's historical remote control data includes:

[0068] In response to determining that the execution number is greater than or equal to the preset execution number, obtaining a plurality of scheduled execution times for executing the remote control request at the scheduled execution time within a second preset historical duration;

[0069] In specific implementation, when it is determined that the number of executions is greater than or equal to the preset number of executions (for example, the preset number of executions can be set to 60% of the total number of executions of the remote control request within the second preset historical time period, and the total number of executions of the remote control request within the second preset historical time period includes the number of executions of the remote control request at the scheduled execution time and the number of executions of the remote control request at the predicted execution time), it indicates that for the remote control request, the scheduled execution time has been used more frequently in history. Therefore, multiple scheduled execution times for executing the remote control request at the scheduled execution time within the second preset historical time period are obtained, providing reliable data support for the subsequent determination of the predicted execution time for executing the remote control request.

[0070] The plurality of scheduled execution times are time-sorted to obtain a time sequence table, and the scheduled execution time in the middle of the time sequence table is determined as the predicted execution time.

[0071] In specific implementation, after collecting multiple scheduled execution times of the user within the second preset historical duration, the scheduled execution times are sorted in chronological order to form a time series table. Selecting the time point in the middle of the time series table as the predicted execution time can more accurately predict the execution time of the user's remote control request, thereby optimizing the service response time and improving the overall user experience.

[0072] In this embodiment, the predicted execution time of the remote control request is determined by analyzing the number of executions of the remote control request at the scheduled execution time within the second preset historical time period, and the prediction is made based on the actual user behavior, thereby improving the accuracy of the prediction. Selecting the middle value can effectively represent the most common behavior mode of the user and reduce the impact of extreme values. It can not only improve efficiency and user satisfaction, but also enhance the reliability and security of executing remote control requests through accurate time management.

[0073] In some embodiments, the historical remote control data also includes the number of times the user canceled the scheduled execution of the remote control request within a second preset historical time period; and determining the predicted execution time of executing the remote control request according to the historical remote control data of the user includes:

[0074] In response to determining that the number of times the remote control request is canceled is greater than or equal to a preset number of cancellations, obtaining a plurality of cancellation times for canceling the remote control request within a second preset historical time period;

[0075] Sort the cancellation time in time to obtain a time series table;

[0076] The cancellation time at the middle position of the time series table is determined as the predicted cancellation time, so as to cancel the remote control request for execution reservation at the predicted cancellation time.

[0077] By analyzing the number of times the remote control request is canceled within the second preset historical time period (i.e., the number of times the remote control request is canceled is greater than or equal to the preset cancellation number, and the preset cancellation number can be set to 10 times), the predicted cancellation time is determined to cancel the remote control request for execution at the predicted cancellation time, thereby providing users with a better remote control experience and avoiding the inconvenience caused to the user by the normal execution of the remote control request due to the user forgetting to cancel the remote control request for execution. Predictions based on actual user behavior can improve the accuracy of predictions, and selecting intermediate values ​​can effectively represent the most common behavior patterns of users and reduce the impact of extreme values.

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

[0079] It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0080] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a vehicle control device.

[0081] refer to Figure 3 , the vehicle control device comprises:

[0082] The judgment module 701 is configured to determine the person-vehicle relationship information between the user and the vehicle and the user's request information in response to receiving the user's remote control request; and determine the user's target control authority over the vehicle based on the person-vehicle relationship information;

[0083] The execution module 701 is configured to call the service interface corresponding to the request information to execute the remote control request based on the matching relationship between the request information and the target control authority.

[0084] Further, the execution module 701 is specifically used for:

[0085] In response to determining that the request information is within the target control authority, calling a service interface corresponding to the request information to execute the remote control request;

[0086] In response to determining that the request information is outside the target control authority, the user's target control authority for the vehicle is adjusted based on the person-vehicle relationship information so that the request information matches the adjusted target control authority, and the service interface corresponding to the request information is called to execute the remote control request.

[0087] Further, the determination module 701 is specifically used for:

[0088] Determining whether there is a person-vehicle binding relationship according to the person-vehicle binding information;

[0089] In response to determining that there is a person-vehicle binding relationship, obtaining a permission tree, and determining a target control permission level of the user according to the permission tree;

[0090] Determine the target control authority corresponding to the target control authority level.

[0091] Further, the execution module 701 is further specifically used for:

[0092] In response to determining that the number of times the user has logged into the vehicle within a first preset historical time period is greater than or equal to a preset number of times, and the target control authority level of the user is at a branch node, adjusting the target control authority level of the user to a root node;

[0093] A target control authority corresponding to the target control authority level adjusted to the root node is determined.

[0094] Further, the execution module 701 is further specifically used for:

[0095] In response to determining that the remote control request is a remote control request for scheduled execution, obtaining a scheduled execution time for executing the remote control request, and determining a predicted execution time for executing the remote control request based on historical remote control data of the user;

[0096] In response to determining that the difference between the scheduled execution time and the predicted execution time is less than or equal to a preset difference, executing the remote control request at the predicted execution time;

[0097] In response to determining that the difference between the scheduled execution time and the predicted execution time is greater than a preset difference, executing the remote control request at the scheduled execution time.

[0098] Further, the execution module 701 is further specifically used for:

[0099] Sort multiple execution times in time to obtain a time series table;

[0100] Determine the average time interval between two adjacent execution times in the time series table;

[0101] In response to determining that the average time interval is less than or equal to the preset time interval, an execution time at a middle position in the time series table is determined as the predicted execution time.

[0102] Further, the execution module 701 is further specifically used for:

[0103] In response to determining that the execution number is greater than or equal to the preset execution number, obtaining a plurality of scheduled execution times for executing the remote control request at the scheduled execution time within a second preset historical duration;

[0104] The plurality of scheduled execution times are time-sorted to obtain a time sequence table, and the scheduled execution time in the middle of the time sequence table is determined as the predicted execution time.

[0105] For the convenience of description, the above device is described in terms of functions divided into various modules. Of course, when implementing the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0106] The device of the above embodiment is used to implement the corresponding vehicle control method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0107] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the vehicle control method described in any of the above embodiments is implemented.

[0108] Figure 4 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0109] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0110] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0111] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0112] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0113] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0114] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0115] The electronic device of the above embodiment is used to implement the corresponding vehicle control method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

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

[0117] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

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

[0119] Based on the same concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a computer program product, including computer program instructions. When the computer program instructions are run on a computer, the computer executes the method described in any of the above embodiments, which has the beneficial effects of the corresponding method embodiments and will not be repeated here.

[0120] It is understandable that before using the technical solutions of each embodiment of the present disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.

[0121] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0122] As an optional but non-limiting implementation, in response to receiving the user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0123] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0124] A person skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0125] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0126] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0127] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the present application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the protection scope of the present application.

Claims

1. A vehicle control method, characterized in that: A telematics processor applied to the vehicle; the method comprising: In response to receiving a remote control request from a user, determining the person-vehicle relationship information between the user and the vehicle, and the user's request information; Based on the person-vehicle relationship information, determining the user's target control authority over the vehicle; Based on the matching relationship between the request information and the target control authority, a service interface corresponding to the request information is called to execute the remote control request.

2. The vehicle control method according to claim 1, characterized in that: The calling, based on the matching relationship between the request information and the target control authority, of a service interface corresponding to the request information to execute the remote control request includes: In response to determining that the request information is outside the target control authority, the user's target control authority for the vehicle is adjusted based on the person-vehicle relationship information so that the request information matches the adjusted target control authority, and the service interface corresponding to the request information is called to execute the remote control request.

3. The vehicle control method according to claim 2, characterized in that: The person-vehicle relationship information includes person-vehicle binding information and a permission tree; and determining the user's target control authority over the vehicle based on the person-vehicle relationship information includes: Determining whether there is a person-vehicle binding relationship according to the person-vehicle binding information; In response to determining that there is a person-vehicle binding relationship, obtaining a permission tree, and determining a target control permission level of the user according to the permission tree; Determine the target control authority corresponding to the target control authority level.

4. The vehicle control method according to claim 3, characterized in that: The person-vehicle relationship information includes the number of times the user has logged into the vehicle within a first preset historical period; and adjusting the user's target control authority over the vehicle based on the person-vehicle relationship information includes: In response to determining that the number of times the user has logged into the vehicle within a first preset historical time period is greater than or equal to a preset number of times, and the target control authority level of the user is at a branch node, adjusting the target control authority level of the user to a root node; A target control authority corresponding to the target control authority level adjusted to the root node is determined.

5. The vehicle control method according to claim 1, characterized in that: The calling of the service interface corresponding to the request information to execute the remote control request includes: In response to determining that the remote control request is a remote control request for scheduled execution, obtaining a scheduled execution time for executing the remote control request, and determining a predicted execution time for executing the remote control request based on historical remote control data of the user; In response to determining that the difference between the scheduled execution time and the predicted execution time is less than or equal to a preset difference, executing the remote control request at the predicted execution time.

6. The vehicle control method according to claim 5, characterized in that: The historical remote control data includes a plurality of execution times of the remote control request within a second preset historical time period; The step of determining the predicted execution time of executing the remote control request according to the historical remote control data of the user includes: Sort multiple execution times in time to obtain a time series table; Determine the average time interval between two adjacent execution times in the time series table; In response to determining that the average time interval is less than or equal to the preset time interval, an execution time at a middle position in the time series table is determined as the predicted execution time.

7. The vehicle control method according to claim 5, characterized in that: The historical remote control data includes the number of executions of the remote control request at the scheduled execution time within a second preset historical time period; The step of determining the predicted execution time of executing the remote control request according to the historical remote control data of the user includes: In response to determining that the execution number is greater than or equal to the preset execution number, obtaining a plurality of scheduled execution times for executing the remote control request at the scheduled execution time within a second preset historical duration; The plurality of scheduled execution times are time-sorted to obtain a time sequence table, and the scheduled execution time in the middle of the time sequence table is determined as the predicted execution time.

8. A vehicle control device, characterized in that: include: a determination module configured to determine, in response to receiving a remote control request from a user, the person-vehicle relationship information between the user and the vehicle, and the user's request information; Based on the person-vehicle relationship information, determining the user's target control authority over the vehicle; An execution module is configured to call a service interface corresponding to the request information to execute the remote control request based on a matching relationship between the request information and the target control authority.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A vehicle, characterized in that: The vehicle comprises the electronic device as claimed in claim 9.

Images