Vehicle control method and device, electronic equipment and vehicle

Abstract

The application provides a vehicle control method and device, electronic equipment and vehicle, and applies to the technical field of vehicle intelligent control, wherein the method comprises the following steps: in response to receiving a remote control request of a user, determining the user-vehicle relationship information of the user and the request information of the user; based on the user-vehicle relationship information, determining the target control authority of the user to the vehicle; based on the matching relationship between the request information and the target control authority, calling the service interface corresponding to the request information to execute the remote control request. The application ensures that the user can only perform the allowed operation within the target control authority, accurately executes the remote control request, effectively prevents the execution of unauthorized remote control requests, improves the safety of the vehicle, and brings convenience to the user.

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 not only provide basic driving functions but also enable intelligent operations such as autonomous driving and remote control through advanced information technology and network communication technologies, greatly improving driving safety and convenience. However, the inability to accurately verify and manage the permissions between users and vehicles makes it difficult to accurately and successfully execute remote control requests. Summary of the Invention

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

[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 user-vehicle relationship information and the user's request information;

[0005] Determining the user's target control authority over the vehicle based on the person-vehicle relationship information;

[0006] 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.

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

[0008] a determination module configured to, in response to receiving a remote control request from a user, determine a 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, comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method 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 application provides a vehicle control method, device, electronic equipment and vehicle, wherein the method is applied to a telematics processor of the vehicle, and the method comprises: in response to receiving a remote control request of a user, determining the user-person-vehicle relationship information of the vehicle and the request information of the user; determining the target control authority of the user on the vehicle based on the person-vehicle relationship information, that is, determining whether there is a person-vehicle binding relationship according to the person-vehicle binding information, so as to ensure that only the user with the person-vehicle binding relationship can operate the vehicle; if it is determined that there is a person-vehicle binding relationship, obtaining an authority tree and determining the target control authority level of the user according to the authority tree; determining the target control authority corresponding to the target control authority level, that is, determining the remote control request allowed to be executed by 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, calling a service interface corresponding to the request information to execute the remote control request, so as to ensure that the user can only execute the operation allowed in the target control authority, each remote control request can be traced back to the user with the explicit target control authority, which effectively prevents the execution of unauthorized remote control requests, at the same time, the service interface corresponding to the request information is directly called by the telematics processor to execute the remote control request, which improves the execution efficiency and accuracy of the remote control request, improves the safety of the vehicle and brings convenience to the user. BRIEF DESCRIPTION OF DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in the present application or related art, the following will briefly introduce the drawings needed to be used in the embodiments or related art descriptions. Obviously, the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0014] Figure 1 Flowchart of the vehicle control method of the embodiment of the present application Figure 1 ;

[0015] Figure 2 Flowchart of the vehicle control method of the embodiment of the present application Figure 2 ;

[0016] Figure 3 Schematic diagram of the vehicle control device of the embodiment of the present application

[0017] Figure 4 The electronic equipment hardware structure schematic diagram provided by the embodiment of the present application. DETAILED DESCRIPTION

[0018] For purposes of the present application, technical solutions and advantages, further detailed explanations are made below in combination with specific embodiments and with reference to the drawings.

[0019] It should be noted that, unless otherwise defined, technical terms or scientific terms used in the embodiments of the present application should be understood as their common meanings to those skilled in the art to which the embodiments of the present application belong. The terms "first", "second" and similar terms used in the embodiments of the present application do not represent any order, number or importance, but are only used to distinguish different components. The terms "include" or "contain" and similar terms mean that the elements or objects before the terms encompass the elements or objects listed after the terms and their equivalents, and do not exclude other elements or objects. The terms "connect" or "connected" and similar terms are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. The terms "upper", "lower", "left", "right" and the like are only used to represent relative positional relationships, and when the absolute positions of the described objects change, the relative positional relationships may also change accordingly.

[0020] In the related art, with the rapid development of science and technology and the acceleration of people's life pace, travel efficiency and comfortable experience have become an important demand in people's daily life. As one of the main means of transportation, the intelligent and networked development trend of the automobile has become the mainstream of the industry. The intelligent vehicle not only can provide basic driving functions, but also can realize intelligent operations such as automatic driving and remote control of the vehicle through advanced information technology and network communication technology, greatly improving the safety and convenience of driving. Although the vehicle can realize various intelligent functions through remote control, it needs to access user data in the cloud and execute corresponding operations according to the permission information provided by the cloud, which may cause delay of control commands, affecting the real-time performance 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 the user and the vehicle, the remote control request cannot be accurately and successfully executed, and the user's vehicle experience is still poor. Moreover, for the remote control request of reservation execution, the user's use of the vehicle is not completely determined, and when the user reserves the execution of the remote control request, it is easy to appear that the user needs to use the vehicle, but due to the time of the reserved execution of the remote control request has not arrived, the remote control request is not executed, affecting the user's vehicle experience.

[0021] Based on the above problems, the applicant finds that by the remote information processor (i.e. T-BOX) of the vehicle, the following scheme is executed: when receiving a remote control request of a user, the human-vehicle relationship information of the user and the request information of the user are determined; based on the human-vehicle relationship information, the target control authority of the user to the vehicle is determined, i.e. whether there is a human-vehicle binding relationship is determined according to the human-vehicle binding information; if it is determined that there is a human-vehicle binding relationship, the authority tree is obtained and the target control authority level of the user is determined according to the authority tree; the target control authority corresponding to the target control authority level is determined; 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, so as to ensure that the user can only execute the allowed operation in the target control authority, accurately execute the remote control request, effectively prevent the execution of unauthorized remote control request, improve the safety of the vehicle and bring convenience to the user. When it is determined that the remote control request is a pre-arranged execution remote control request, the pre-arranged execution time of executing the remote control request is obtained, and the predicted execution time of executing the remote control request is determined according to the historical remote control data of the user, and according to the difference between the pre-arranged execution time and the predicted execution time, the remote control request is executed at the predicted execution time or the remote control request is executed at the pre-arranged 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, complete the necessary vehicle control before the user arrives at the vehicle, and at the same time, since the operation is directly executed through the remote information processor, the execution efficiency of the remote control request is improved.

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

[0023] The present application provides a vehicle control method, as shown in Figure 1 In some embodiments, the method is executed by the remote information processor of the vehicle, and subsequent embodiments are all exemplarily illustrated by taking the remote information processor as an example; the method comprises:

[0024] S101, in response to receiving a remote control request of a user, determining the human-vehicle relationship information of the user and the request information of the user;

[0025] In specific implementation, when the user issues a remote control request, it is first confirmed whether the user has the right to control the vehicle, the identity of the user needs to be verified and the association relationship between the user and the vehicle is confirmed, the human-vehicle relationship information of the user and the vehicle is determined, and the request information of the user is also confirmed. The request information is the specific operation that the user hopes to execute.

[0026] S102, based on the human-vehicle relationship information, determining the target control authority of the user to the vehicle;

[0027] In specific implementation, the target control authority of the user on the vehicle is determined according to the human-vehicle relationship information, the target control authority determines the specific operation range that the user can perform, including which remote control request can be controlled by the user and under what conditions the remote control request can be executed. Specifically, it can be determined whether there is a human-vehicle binding relationship according to the human-vehicle binding information; if it is determined that there is a human-vehicle binding relationship, the authority tree is obtained, and the target control authority level of the user is determined according to the authority tree; and the target control authority corresponding to the target control authority level is determined. By determining the target control authority of the user on the vehicle, it can be ensured that each remote control operation is reasonable and safe, and the trust and satisfaction of the user on the intelligent vehicle remote control function is enhanced.

[0028] In specific implementation, the target control authority of the user on the vehicle is determined according to the human-vehicle relationship information, the target control authority determines the specific operation range that the user can perform, including which remote control request can be controlled by the user and under what conditions the remote control request can be executed. Specifically, it can be determined whether there is a human-vehicle binding relationship according to the human-vehicle binding information; if it is determined that there is a human-vehicle binding relationship, the authority tree is obtained, and the target control authority level of the user is determined according to the authority tree; and the target control authority corresponding to the target control authority level is determined. By determining the target control authority of the user on the vehicle, it can be ensured that each remote control operation is reasonable and safe, and the trust and satisfaction of the user on the intelligent vehicle remote control function is enhanced.

[0029] In specific implementation, the target control authority of the user on the vehicle is determined according to the human-vehicle relationship information, the target control authority determines the specific operation range that the user can perform, including which remote control request can be controlled by the user and under what conditions the remote control request can be executed. Specifically, it can be determined whether there is a human-vehicle binding relationship according to the human-vehicle binding information; if it is determined that there is a human-vehicle binding relationship, the authority tree is obtained, and the target control authority level of the user is determined according to the authority tree; and the target control authority corresponding to the target control authority level is determined. By determining the target control authority of the user on the vehicle, it can be ensured that each remote control operation is reasonable and safe, and the trust and satisfaction of the user on the intelligent vehicle remote control function is enhanced.

[0030] In specific implementation, the target control authority of the user on the vehicle is determined according to the human-vehicle relationship information, the target control authority determines the specific operation range that the user can perform, including which remote control request can be controlled by the user and under what conditions the remote control request can be executed. Specifically, it can be determined whether there is a human-vehicle binding relationship according to the human-vehicle binding information; if it is determined that there is a human-vehicle binding relationship, the authority tree is obtained, and the target control authority level of the user is determined according to the authority tree; and the target control authority corresponding to the target control authority level is determined. By determining the target control authority of the user on the vehicle, it can be ensured that each remote control operation is reasonable and safe, and the trust and satisfaction of the user on the intelligent vehicle remote control function is enhanced.

[0031] Based on the above embodiments, the matching relationship between the request information and the target control authority is described in detail, and the service interface corresponding to the request information is called to execute the remote control request, ensuring that the operation of the remote control request will not exceed the authorized range of the user. The service interface corresponding to the request information is called to execute the remote control request based on the matching relationship between the request information and the target control authority, including:

[0032] In response to determining 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;

[0033] In specific implementation, it is necessary to determine whether the operation requested by the user is within the authorized operation range, i.e., 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. To ensure communication security, encryption protocols and security authentication mechanisms may be used to protect data security and integrity during data transmission. Through this step, when the request information of the user's remote control request is within its target control authority, the remote control request can be safely and accurately executed, providing good user experience and high system security.

[0034] In response to determining that the request information is outside the target control authority, the target control authority of the user to the vehicle is adjusted based on the human-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, i.e., the user's remote control request exceeds its current control authority, the remote control request will not be immediately rejected, but the target control authority of the user will be adjusted based on the existing human-vehicle relationship information between the user and the vehicle, such as adjusting the target control authority of the user to the vehicle based on the number of times the user logs 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 review 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 to prevent unauthorized operations and potential security risks, while also flexibly handling remote control requests that exceed the current target control authority, ensuring the security of executing remote control requests and improving 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 target control authority of the user to the vehicle, it can be ensured that each remote control operation is reasonable and safe, so as to ensure that the operation of the remote control request does not exceed the authorized range of the user, and strict control of safety is maintained. Based on the human-vehicle relationship information, the target control authority of the user to the vehicle is adjusted, which can reduce the request rejection caused by the authority problem, thereby improving the overall efficiency and response speed of the system. The user does not have to try or contact customer service multiple times due to the authority problem, thereby improving the convenience and efficiency of the operation.

[0037] Based on the above embodiment, the target control authority of the user to the vehicle is determined based on the human-vehicle relationship information, which ensures that each remote control request can be traced back to a user with clear authority, and the safety of the operation is guaranteed. As shown in Figure 2 The human-vehicle relationship information includes human-vehicle binding information and an authority tree. The target control authority of the user to the vehicle is determined based on the human-vehicle relationship information, including:

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

[0039] In specific implementation, the human-vehicle binding information needs to be stored through a database or a data management system, which includes but is not limited to the identity details of the user, the unique identifier of the vehicle, the human-vehicle binding relationship, the binding validity period, etc. When the user initiates a remote control request, the human-vehicle binding information is queried to confirm whether there is a human-vehicle binding relationship, so as to effectively manage and verify the human-vehicle binding information, and ensure that only the user with a human-vehicle binding relationship can operate the vehicle, thereby not only enhancing the safety of the system, but also improving the trust and satisfaction of the user.

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

[0041] In specific implementation, after confirming that there is a human-vehicle binding relationship between the user and the vehicle, the authority tree is obtained, and the target control authority level of the user is determined according to the authority tree. The authority tree is a structured data model used to define the target control authority level of different users or user groups to the vehicle. The target control authority level at the root node of the authority tree has the highest level, and the corresponding target control authority is allowed to execute all remote control requests. For the target control authority level at the branch node of the authority tree, the corresponding target control authority is allowed to execute part of the remote control request, for example, only access the lock and unlock function of the vehicle door.

[0042] S203, determine a target control authority corresponding to the target control authority level.

[0043] In the implementation, after confirming the target control authority level of the user, the corresponding target control authority is searched according to the target control authority level, and the target control authority defines specific vehicle remote control operations that can be performed by the user. It is ensured that the user can only perform the operations allowed in the target control authority, thereby maintaining the security and integrity of the system and effectively preventing unauthorized operations.

[0044] In the embodiment, the user can clearly understand which operations can be performed according to the target control authority level. The structured management of the person-vehicle binding information and the authority tree makes it easy for the vehicle owner or manager to add, modify or delete user permissions, facilitating the maintenance and updating of the system. Each remote control request can be traced back to a user with clear permissions, which not only guarantees the security of the operation, but also optimizes the user experience and system management.

[0045] Based on the above embodiment, the target control authority of the user to the vehicle is adjusted based on the person-vehicle relationship information, and it is ensured that only users who frequently and legally use the vehicle can obtain higher permissions. The person-vehicle relationship information includes the number of times the user logs into the vehicle within a first preset historical time period. The target control authority of the user to the vehicle is adjusted based on the person-vehicle relationship information, including:

[0046] In response to determining that the number of times the user logs into the vehicle within the 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, the target control authority level of the user is adjusted to a root node;

[0047] In implementation, the time when the user logs in the vehicle is usually queried, and the number of times when the user logs in the vehicle within a first preset historical time period (for example, the first preset historical time period can be set as 24 hours) is determined. When it is determined that the number of times when the user logs in the vehicle within the first preset historical time period is greater than or equal to a preset number of times (for example, the preset number of times can be set as 1), it indicates that the user uses the vehicle frequently within the first preset historical time period, and the trustworthiness of the user is high. At this time, if the target control authority level of the user is at the branch node, the target control authority level of the user can be adjusted to the root node, so that the remote control request of the user can be successfully executed. Not only can the target control authority level be flexibly adjusted according to the actual use of the user, but also the safety and transparency of the whole process can be ensured, which helps to improve the satisfaction of the user and ensures the stability and safety of the system. When the authority level of the user is adjusted, the user can be notified of the details and reasons of the change of the target control authority level. It can be understood that, in response to the determination that the number of times when the user logs in the vehicle within the first preset historical time period is greater than or equal to the preset number of times, and the target control authority level of the user is at the leaf node, it indicates that the target control authority level of the user is the lowest. At this time, in order to ensure the safety of the vehicle, the target control authority level of the user will not be adjusted.

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

[0049] In implementation, after confirming the target control authority level of the user, the corresponding target control authority needs to be found according to the target control authority level. The target control authority defines the specific vehicle remote control operation that can be performed by the user. It is ensured that the user can only perform the operation allowed in the target control authority, so as to maintain the safety and integrity of the system and effectively prevent unauthorized operation.

[0050] In the embodiment, the authority is dynamically adjusted by considering the number of times when the user logs in the vehicle within the first preset historical time period, such as adjusting the target control authority level of the user to the root node. The user's demand can be more flexibly adapted, and only the user who really frequently and legally uses the vehicle can obtain higher authority, so that the remote control request of the user can be successfully executed, which helps to prevent unauthorized operation and potential security threats, and at the same time, the remote control request of the user can be successfully executed.

[0051] Based on the above embodiment, the remote control request is executed by calling the service interface corresponding to the request information, which ensures that the vehicle is in the best state when the user arrives, and improves the efficiency of the execution of the remote control request. The remote control request is executed by calling the service interface corresponding to the request information, including:

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

[0053] In specific implementation, when it is determined that the remote control request is a pre-scheduled remote control request, that is, the user specifies a specific time when initiating the remote control request, the pre-scheduled execution time of executing the remote control request is obtained, and the predicted execution time of executing the remote control request is determined according to the historical remote control data of the user. The predicted execution time may be different from the pre-scheduled execution time set by the user. The predicted execution time helps to optimize the execution of the remote control request, so that it is more in line with the actual needs of the user, and the execution of the remote control request is more in line with the actual behavior and expectation of the user, which helps to improve the overall efficiency and user satisfaction of the execution of the remote control request.

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

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

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

[0057] In specific implementation, when it is determined that the difference between the pre-scheduled execution time and the predicted execution time is greater than the preset difference value, it indicates that there is a large deviation between the predicted execution time and the pre-scheduled execution time of the user. At this time, the pre-scheduled execution time of the user is given priority to ensure the intuitiveness and certainty of user control, and to ensure the accuracy and safety of the operation 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 a preset difference, the remote control request is executed at the predicted execution time; 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, thereby more accurately meeting the user's needs. Selecting a predicted execution time can optimize vehicle usage based on the user's actual behavior patterns, such as preheating or cooling the vehicle in advance, thereby improving energy efficiency and immediate vehicle availability. This reduces waiting and preparation time, ensuring that the vehicle is in optimal condition when the user arrives, which not only improves the user experience but also increases execution efficiency.

[0059] Based on the above embodiment, the method of determining the predicted execution time of executing the remote control request based on the user's historical remote control data is described in detail, thereby more accurately predicting the execution time of future remote control requests and making the remote control operation more in line with the user's actual needs. The historical remote control data includes multiple execution times of the remote control request within a second preset historical time period; the method of determining the predicted execution time of executing the remote control request based on the user's historical remote control data includes:

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

[0061] In a specific implementation, it is necessary to collect multiple execution times of the remote control request of the user within a second preset historical period (for example, the second preset historical period can be set to one month) from a database or other data storage. The collected execution times are sorted in chronological order, usually by comparing timestamps and using an array or list sorting algorithm 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. The average value of multiple time intervals is 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, the execution time at the middle position of the time series table is determined as the predicted execution time.

[0065] In a specific implementation, when it is determined that the average time interval is less than or equal to a 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 at the middle position of the time sequence list is determined as the predicted execution time. If the length of the time sequence list is odd, the time point at the middle position is directly selected as the predicted execution time; if the length is even, the average of the two middle time points or one of them is selected 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 time sorting a plurality of execution times to obtain a time sequence list, determining the average time interval of two adjacent execution times, using the user historical remote control data, the regularity of the user executing the remote control request can be recognized, and if the average time interval is less than or equal to a preset time interval, the execution time at the middle position of the time sequence list is determined as the predicted execution time, so as to more accurately predict the execution time of the future remote control request, improve the prediction accuracy, and make the remote control operation more in line with the actual needs of the user. For example, the vehicle can automatically adjust to a suitable temperature before the user arrives, or start in advance, greatly enhancing the user's vehicle experience.

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

[0068] In response to determining that the number of times is greater than or equal to a preset number of times, a plurality of reservation execution times of the remote control request at a reservation execution time within a second preset historical time length are obtained;

[0069] In a specific implementation, when it is determined that the number of execution times is greater than or equal to a preset number of execution times (for example, the preset number of execution times can be set to 60% of the total number of times of executing the remote control request in a second preset historical time period, and the total number of times of executing the remote control request in the second preset historical time period includes the number of times of executing the remote control request at the scheduled execution time and the number of times of executing the remote control request at the predicted execution time), it indicates that, historically, the scheduled execution time is more often used for the remote control request, and therefore, a plurality of scheduled execution times of executing the remote control request at the scheduled execution time in the second preset historical time period are obtained to provide reliable data support for subsequently determining the predicted execution time of executing the remote control request.

[0070] The plurality of scheduled execution times are time-sequenced to obtain a time sequence list, and a scheduled execution time at a middle position of the time sequence list is determined as the predicted execution time.

[0071] In a specific implementation, after the plurality of scheduled execution times of the user in the second preset historical time period are collected, the scheduled execution times are sorted in time sequence to form a time sequence list. The time point at the middle position of the time sequence list is selected as the predicted execution time, which can more accurately predict the execution time of the remote control request of the user, thereby optimizing the response time of the service and improving the overall user experience.

[0072] In this embodiment, the predicted execution time of executing the remote control request is determined by analyzing the number of times of executing the remote control request at the scheduled execution time in the second preset historical time period, which is based on actual user behavior to improve the accuracy of prediction, and the middle value can effectively represent the most common behavior pattern of the user to reduce the influence of extreme values. Not only can efficiency and user satisfaction be improved, but also the reliability and safety of executing the remote control request can be enhanced through accurate time management.

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

[0074] In response to determining that the number of times of canceling the scheduled execution of the remote control request is greater than or equal to a preset number of canceling times, a plurality of canceling times of canceling the scheduled execution of the remote control request in the second preset historical time period are obtained;

[0075] The canceling times are time-sequenced to obtain a time sequence list;

[0076] A canceling time at a middle position of the time sequence list is determined as a predicted canceling time, so as to cancel the execution of the scheduled remote control request at the predicted canceling time.

[0077] By analyzing the number of times of canceling the remote control request in the second preset historical time length (i.e., the number of times of canceling the remote control request is greater than or equal to a preset canceling number, for example, the preset canceling number can be set to 10 times), a prediction canceling time is determined to cancel the execution of the remote control request in the prediction canceling time, so as to provide a better remote control experience for the user and avoid the user forgetting to cancel the execution of the remote control request, resulting in the normal execution of the remote control request and bringing inconvenience to the user. Based on the actual user behavior, the prediction accuracy is improved, and the intermediate value can effectively represent the most common behavior mode of the user and reduce the influence of extreme values.

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

[0079] It should be noted that some embodiments of the present application have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than the order described above and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

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

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

[0082] The judgment module 701 is configured to determine the human-vehicle relationship information of the user and the request information of the user in response to receiving the remote control request of the user, and determine the target control authority of the user on the vehicle based on the human-vehicle relationship information.

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

[0084] Further, the execution module 701 is specifically configured to:

[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] Furthermore, the judgment module 701 is specifically configured to:

[0088] Determining whether a person-vehicle binding relationship exists based on the person-vehicle binding information;

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

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

[0091] Furthermore, the execution module 701 is further configured to:

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

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

[0094] Furthermore, the execution module 701 is further configured to:

[0095] In response to determining that the remote control request is a scheduled execution remote control request, 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 a 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 a 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] Furthermore, the execution module 701 is further configured to:

[0099] Sort multiple execution times by 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, the execution time at the middle position of the time series table is determined as the predicted execution time.

[0102] Furthermore, the execution module 701 is further configured to:

[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 times 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 devices are described as being divided into various modules according to their functions. Of course, when implementing this application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0106] The apparatus 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 embodiments, which will not be described in detail 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 runnable 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 10 is a schematic diagram showing a more specific hardware structure of an electronic device provided in this embodiment. 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 communicatively connected to each other within the device via the bus 1050.

[0109] The processor 1010 can be implemented using 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 can be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1020 can store an operating system and other application programs, and when the technical solutions provided by the embodiments of the present specification are implemented by software or firmware, the related program codes are stored in the memory 1020 and are called and executed by the processor 1010.

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

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

[0113] The bus 1050 includes a channel for transmitting information between various components (such as the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040) of the device.

[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 can also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device can also only contain the components necessary to implement the embodiments of the present specification, and does not have to contain all the components shown in the figure.

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

[0116] Based on the same inventive concept, the present application also provides a non-transitory computer readable storage medium, which stores computer instructions for causing the computer to execute the vehicle control method according to any of the above embodiments.

[0117] The computer readable medium of the embodiments includes permanent and non-permanent, removable and non-removable media, which can realize information storage by any method or technology. The information can be computer readable instructions, data structures, program modules 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0118] The storage medium of the above-mentioned embodiments stores computer instructions for causing the computer to execute the vehicle control method as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which are not repeated here.

[0119] Based on the same concept, the present application also provides a computer program product corresponding to the method of any of the above-mentioned embodiments, comprising computer program instructions, which, when executed on a computer, cause the computer to execute the method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which are not repeated here.

[0120] It can be understood that before using the technical solutions of various embodiments in the present disclosure, the type of personal information involved, the scope of use, the scene of use, etc. will be informed to the user in a proper way, and the authorization of the user will be obtained.

[0121] For example, in response to receiving the user's active request, prompt information is sent to the user to explicitly prompt the user that the operation requested to be performed will require the acquisition and use of the user's personal information. Thus, the user can voluntarily choose whether to provide personal information to the software or hardware such as electronic device, application program, server or storage medium that performs the technical solutions of the present disclosure according to the prompt information.

[0122] As an optional but not limited implementation manner, in response to accepting the user's active request, the way of sending prompt information to the user may, for example, be the way of pop-up window, and the prompt information can be presented in the form of text in the pop-up window. In addition, the pop-up window can also carry selection controls for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0123] It can be understood that the above notification and obtaining user authorization process is only illustrative, and does not limit the implementation of the present disclosure, and other ways meeting relevant laws and regulations can also be applied to the implementation of the present disclosure.

[0124] It should be understood by those of ordinary skill in the art that the above discussion of any embodiment is merely exemplary and is not intended to suggest that the scope of the present application is limited to these examples; the above embodiments or technical features among different embodiments can also be combined, steps can be implemented in any order, and there are many other changes of different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of brevity. It is intended that the scope of the present application encompass all such changes and modifications.

[0125] In addition, in order to simplify the description and discussion, and so as not to make the embodiments of the present application difficult to understand, the well-known power / ground connections of integrated circuit (IC) chips and other components can or can not be shown in the provided drawings. In addition, the apparatus can be shown in the form of a block diagram in order 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 apparatus are highly dependent on the platform to be implemented in the embodiments of the present application (i.e., these details should be fully within the understanding of those skilled in the art). Where specific details (e.g., circuitry) are set forth in order to describe an illustrative embodiment of the present application, it will be apparent to those skilled in the art that the embodiments of the present application can be practiced without these specific details or with variations on these specific details. Therefore, these descriptions should be considered as illustrative rather than limiting.

[0126] Although the present application has been described in conjunction with the specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art in light of the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) can use the embodiments discussed.

[0127] The embodiments of the present application are intended to cover all such alternatives, modifications and variations as falling within the broad scope of the application claimed. Accordingly, any omission, modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A vehicle control method characterized by, A telematics processor applied to the vehicle; the method comprises: In response to receiving a remote control request of a user, determining the user and the vehicle relationship information of the vehicle, and the request information of the user; Based on the vehicle relationship information, determine the target control authority of the user to the vehicle; Based on the matching relationship between the request information and the target control authority, call the service interface corresponding to the request information to execute the remote control request; Wherein, the calling the service interface corresponding to the request information to execute the remote control request comprises: In response to determining that the remote control request is a pre-arranged execution remote control request, obtaining the pre-arranged execution time of the remote control request, and determining the predicted execution time of the remote control request according to the historical remote control data of the user; Wherein, the historical remote control data comprises a plurality of execution times of the remote control request within a second preset historical time length; the determination of the predicted execution time of the remote control request according to the historical remote control data of the user comprises: Time sorting of multiple execution times to obtain a time sequence table; Determine the average time interval of the adjacent two execution times in the time sequence table; In response to determining that the average time interval is less than or equal to the preset time interval, determine the execution time at the middle position of the time sequence table as the predicted execution time.

2. The vehicle control method according to claim 1, characterized by, The 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 comprises: In response to determining that the request information is located outside the target control authority, adjusting the target control authority of the user to the vehicle based on the vehicle relationship information, so that the request information matches the adjusted target control authority, and calling the service interface corresponding to the request information to execute the remote control request.

3. The vehicle control method according to claim 2, characterized by, The vehicle relationship information comprises vehicle binding information and authority tree; the determination of the target control authority of the user to the vehicle based on the vehicle relationship information comprises: Determine whether there is a vehicle binding relationship according to the vehicle binding information; In response to determining that there is a vehicle binding relationship, obtain the authority tree and determine the target control authority level of the user according to the authority tree; Determine the target control authority corresponding to the target control authority level.

4. The vehicle control method according to claim 3, characterized by, The vehicle relationship information comprises the number of times that the user logs in the vehicle within a first preset historical time length; the adjustment of the target control authority of the user to the vehicle based on the vehicle relationship information comprises: In response to determining that the number of times that the user logs in the vehicle within a first preset historical time length 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 the root node; Determine the target control authority corresponding to the target control authority level adjusted to the root node.

5. The vehicle control method according to claim 1, characterized by The calling the service interface corresponding to the request information to execute the remote control request comprises: In response to determining that the difference between the pre-arranged 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 1, characterized by The historical remote control data includes an execution number of the remote control request executed at a scheduled execution time within a second preset historical time length; The method further includes: In response to determining that the execution number is greater than or equal to a preset execution number, obtaining a plurality of scheduled execution times of the remote control request executed at a scheduled execution time within a second preset historical time length; Time sorting the plurality of scheduled execution times to obtain a time sequence list, and determining a scheduled execution time at a middle position of the time sequence list as the predicted execution time.

7. A vehicle control device characterized by comprising: An electronic device configured to perform the method of claim 1, comprising: a judging module configured to, in response to receiving a remote control request of a user, determine the user-person-vehicle relationship information of the user and the request information of the user; and determine a target control authority of the user over the vehicle based on the user-person-vehicle relationship information; an executing module configured to, based on a matching relationship between the request information and the target control authority, invoke a service interface corresponding to the request information to execute the remote control request.

8. An electronic device comprising a memory, a processor, and a computer program stored on the memory and running on the processor, characterized in that, The processor implements the method of any one of claims 1 to 6 when executing the program.

9. A vehicle characterized by comprising: The vehicle comprises the electronic device of claim 8. The processor implements the method of any one of claims 1 to 6 when executing the program. The vehicle comprises the electronic device of claim 8.

Images