Vehicle function control methods, devices, processors and electronic equipment

Abstract

This application discloses a method, apparatus, processor, and electronic device for controlling the function of a vehicle. The method includes: in response to detecting an operation request for a driver assistance function to be performed on the vehicle, obtaining the vehicle's login account and the corresponding permission information for the driver assistance function, wherein the permission information indicates whether the login account has permission to use the driver assistance function; verifying the login account and permission information to obtain a verification result; in response to the verification result indicating that the login account has successfully logged into the vehicle and the permission information indicates that the login account has permission to use the driver assistance function, triggering an operation command corresponding to the operation request on the vehicle; and in response to the operation command, controlling the vehicle to execute the driver assistance function. This application solves the technical problem of being unable to effectively control a vehicle to execute driver assistance functions.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and more specifically, to a method, apparatus, processor, and electronic device for controlling the function of a vehicle. Background Technology

[0002] Currently, before controlling a vehicle to execute driver assistance functions, it is necessary to verify whether the driver has completed the learning and examination process via terminal login. However, this method only verifies the login status of the account and cannot effectively prevent those who have not passed the assessment (such as users) from activating high-risk driver assistance functions. Therefore, there is still a technical problem in effectively controlling the vehicle's execution of driver assistance functions.

[0003] There is currently no effective solution to the aforementioned technical problems. Summary of the Invention

[0004] This application provides a vehicle function control method, device, processor, and electronic device to at least solve the technical problem of being unable to effectively control a vehicle to perform driving assistance functions.

[0005] According to one aspect of the embodiments of this application, a vehicle function control method is provided, comprising: in response to detecting an operation request for a driving assistance function to be performed on the vehicle, obtaining a login account of the vehicle and permission information of the driving assistance function corresponding to the login account, wherein the permission information is used to indicate whether the login account has permission to use the driving assistance function; verifying the login account and the permission information to obtain a verification result; in response to the verification result indicating that the login account has successfully logged into the vehicle and the permission information indicating that the login account has permission to use the driving assistance function, triggering an operation instruction corresponding to the operation request on the vehicle; and in response to the operation instruction, controlling the vehicle to perform the driving assistance function.

[0006] Further, the login account and permission information are verified to obtain verification results, including: verifying the login status and login type of the login account to obtain a first verification result, wherein the first verification result is used to indicate whether the login status is a valid login status and whether the login type is the type of the vehicle's local login account; verifying the permission information to obtain a second verification result, wherein the second verification result is used to indicate whether the permission information is valid permission information; and determining the verification result based on the first verification result and the second verification result.

[0007] Further, based on the first verification result and the second verification result, the verification result is determined, including: in response to the first verification result indicating that the login status is not logged in, determining the verification result as a failed login attempt to the vehicle; or, in response to the first verification result indicating a valid login status and the second verification result indicating invalid permission information, determining the verification result as a login account not having permission to use the driving assistance function; the method further includes: in response to the verification result indicating that the login account failed login to the vehicle, or the permission information indicating that the login account does not have permission to use the driving assistance function, prohibiting the vehicle from executing the driving assistance function, and outputting a prompt message using the vehicle's display module, wherein the prompt message is used to prompt the target object corresponding to the login account to learn the driving assistance function.

[0008] Furthermore, the method also includes: in response to the target object completing the learning of the driving assistance function and passing the test corresponding to the driving assistance function, determining the permission information that the logged-in account has the permission to use the driving assistance function.

[0009] Furthermore, based on the first verification result and the second verification result, the verification result is determined, including: in response to the first verification result indicating that the login status is a valid login status and the login type is a local login account, and the second verification result indicating that the permission information is valid permission information, the verification result is determined to be that the login account has successfully logged into the vehicle, and the permission information indicates that the login account has the permission to use the driving assistance function.

[0010] Furthermore, in response to detecting an operation request for a driving assistance function to be performed on the vehicle, the system obtains the vehicle's login account and the permission information of the driving assistance function corresponding to the login account, including: in response to the login account being the vehicle's local login account, obtaining the permission information of the driving assistance function corresponding to the login account; in response to the login account being a login account other than the local login account, sending a query request instruction to the cloud, wherein the query request instruction is used to indicate an instruction to query the identification information of the login account; and in response to the query request instruction, controlling the cloud to send the permission information of the driving assistance function corresponding to the login account to the vehicle.

[0011] Furthermore, the method also includes: locally storing the driving assistance functions controlled by the vehicle; and / or uploading the driving assistance functions to the cloud for backup.

[0012] According to another aspect of the embodiments of this application, a vehicle function control device is also provided. The device includes: an acquisition unit, configured to acquire, in response to detecting an operation request for a driving assistance function to be performed on the vehicle, a vehicle login account and permission information of the driving assistance function corresponding to the login account, wherein the permission information is used to indicate whether the login account has permission to use the driving assistance function; a verification unit, configured to verify the login account and the permission information to obtain a verification result; a triggering unit, configured to trigger an operation command corresponding to the operation request on the vehicle in response to the verification result indicating that the login account has successfully logged into the vehicle and the permission information indicating that the login account has permission to use the driving assistance function; and a control unit, configured to control the vehicle to perform the driving assistance function in response to the operation command.

[0013] According to another aspect of the embodiments of this application, a processor is also provided. The processor is used to run a program, wherein the program is executed by the processor to perform the methods described in the embodiments of this application.

[0014] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0015] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0016] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the methods in various embodiments of this application.

[0018] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0019] According to another aspect of the embodiments of this application, a vehicle is also provided that implements the methods of the various embodiments of this application when executed.

[0020] In this embodiment, if an operation request for a vehicle's driving assistance function is detected, the vehicle's login account and the corresponding driving assistance function's permission information can be obtained. Then, both the login account and permission information can be verified, overcoming the limitation of related technologies that rely solely on the validity of the login account as the sole prerequisite for enabling driving assistance functions. Thus, if the login account successfully logs into the vehicle and the permission information indicates that the login account has the authority to use driving assistance functions, the operation command corresponding to the operation request is triggered on the vehicle. Responding to the operation command, the vehicle is controlled to execute the driving assistance function, thereby solving the technical problem of ineffective control over the vehicle's execution of driving assistance functions and achieving the technical effect of effectively controlling the vehicle's execution of driving assistance functions. Attached Figure Description

[0021] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0022] Figure 1 This is a flowchart of a vehicle function control method according to an embodiment of this application;

[0023] Figure 2 This is a flowchart of a learning and testing control method for intelligent driving assistance functions according to an embodiment of this application;

[0024] Figure 3 This is a flowchart illustrating a method for execution between a mobile app and the cloud, according to an embodiment of this application.

[0025] Figure 4 This is a flowchart illustrating a method for communication between an in-vehicle infotainment system and the cloud, according to an embodiment of this application.

[0026] Figure 5 This is a flowchart of a method for execution between an in-vehicle infotainment system and an advanced driver assistance system according to an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of a vehicle function control device according to an embodiment of this application;

[0028] Figure 7 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] According to an embodiment of this application, an embodiment of a vehicle function control method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0032] Figure 1 This is a flowchart of a vehicle function control method according to an embodiment of this application, such as... Figure 1 As shown, the method includes the following steps.

[0033] Step S102: In response to detecting an operation request for a driving assistance function to be performed on the vehicle, obtain the vehicle's login account and the permission information of the driving assistance function corresponding to the login account.

[0034] In the technical solution provided by step S102 in the embodiments of this application, the permission information can be used to indicate whether the login account has the permission to use driving assistance functions.

[0035] In this embodiment, the aforementioned driving assistance function can be an intelligent driving assistance function, which is an advanced driving assistance system function with a certain degree of autonomous decision-making ability, realized based on artificial intelligence technologies such as sensor fusion, environmental perception, decision planning and vehicle control. It is different from passive driving functions that only provide a single closed assistance (such as reversing radar, cruise control, etc.).

[0036] Optionally, the driving assistance functions may include, but are not limited to, functions corresponding to systems with multi-scenario perception, path planning and active intervention capabilities, such as highway navigation assistance, automatic parking assistance, memory parking, city navigation assistance, automatic lane change assistance, and traffic jam assistance. These are just examples and no specific limitations are made here.

[0037] Optionally, the login account mentioned above can be a user account currently detected in the vehicle's on-board system. The login account can be part of the same identity system as the cloud login account registered by the user on the mobile application (APP), achieving vehicle-cloud identity connectivity through a unified login account key or biometric binding. The login account can also be referred to as an account.

[0038] Optionally, the aforementioned login account can actively read the session information of the currently logged-in account through the vehicle's in-vehicle infotainment (IVI) system. The authentication process can be completed by the user through facial recognition, fingerprint, account password, or automatic association via Bluetooth device after the vehicle system is started or woken up.

[0039] Optionally, the aforementioned permission information can be a dynamic authorization status generated based on whether the user has completed the mandatory learning and examination for the corresponding driver assistance function. This dynamic authorization status can be generated and synchronously uploaded to the cloud after the user completes watching the instructional video for the specified driver assistance function, answering each question correctly, and completing all questions on the mobile app. The cloud can then send this dynamic authorization status to the local storage space of the user's current vehicle, or transmit it to the vehicle in real time when connected to the network, depending on network conditions, through differential synchronization or timed push mechanisms, for immediate verification.

[0040] Optionally, the aforementioned permission information can be stored as structured data, including fields such as account identity (ID), functional module identifier, exam pass mark, pass timestamp, and data source (local / cloud), to ensure that the dynamic authorization status is traceable, auditable, and tamper-proof.

[0041] In this embodiment of the application, in response to detecting an operation request for a driving assistance function to be performed on the vehicle, the vehicle's login account and the permission information of the driving assistance function corresponding to the login account are obtained, so as to provide true, valid and verifiable data basis for subsequent verification of login account and permission information.

[0042] Step S104: Verify the login account and permission information to obtain the verification result.

[0043] In the technical solution provided by step S104 in this application embodiment, after obtaining the vehicle's login account and the permission information of the driving assistance function corresponding to the login account, the login account and permission information can be verified to determine whether the login account has successfully logged into the vehicle and whether the permission information indicates that the login account has the permission to use the driving assistance function.

[0044] In this embodiment, by verifying the login account, it is possible to check whether the session token of the login account is valid, whether it has been forcibly logged out by other devices, and whether it is in a frozen or abnormal state. Verifying the permission information can determine the validity of the permission information, such as whether the login account has completed and successfully passed the mandatory learning exam for the currently requested driver assistance function.

[0045] Optionally, the verification process can be synchronously completed within milliseconds by the permission management module within the vehicle's vehicle-side domain controller. The verification result can be either successful login to the vehicle with the logged-in account having permission to use driver assistance functions, or a failed login attempt with permission information indicating that the logged-in account does not have permission to use driver assistance functions.

[0046] In this embodiment of the application, by performing a dual-condition joint verification of the login account and permission information, it can be determined whether the current user is legally qualified and competent to operate the driving assistance function.

[0047] In step S106, in response to the verification result that the login account has successfully logged into the vehicle and the permission information that the login account has the permission to use the driving assistance function, the operation command corresponding to the operation request is triggered on the vehicle.

[0048] In the technical solution provided by step S106 in this application embodiment, if the login account successfully logs into the vehicle and the permission information indicates that the login account has the permission to use driving assistance functions, then the operation command corresponding to the operation request can be triggered on the vehicle.

[0049] In this embodiment, the operation command corresponding to the above-mentioned trigger operation request can be directly called by the intelligent driving function management module of the vehicle domain controller to the underlying function control interface, and the user's operation command is converted into control signals in the Controller Area Network (CAN) bus or Ethernet communication protocol, so as to drive the perception system, decision planning module and actuator in the vehicle to work together to complete the start and operation of the driving assistance function.

[0050] Optionally, if the user suddenly switches login accounts or disconnects from the network during the triggering process, the activated driving assistance function can still continue to run until the end of the current operation cycle, but subsequent new operation commands will trigger verification again.

[0051] Optionally, if the user successfully logs into the vehicle and the permissions information indicates that the account has the authority to use driver assistance functions, it means that the user has completed the learning and passed the test for driver assistance functions before using them. At this point, the user has a clear understanding of the applicable scenarios, abnormal response mechanisms, and liability attribution for driver assistance functions, and can then trigger the corresponding operation command on the vehicle.

[0052] In this embodiment of the application, triggering the operation command corresponding to the operation request through the above steps can provide a safe premise for subsequently controlling the vehicle to perform driving assistance functions.

[0053] Step S108: In response to the operation command, control the vehicle to perform driving assistance functions.

[0054] In the technical solution provided by step S108 in this application embodiment, after responding to the verification result that the login account has successfully logged into the vehicle and the permission information that the login account has the permission to use the driving assistance function, the operation command corresponding to the operation request is triggered on the vehicle, and the vehicle can be controlled to execute the driving assistance function in response to the operation command.

[0055] In this embodiment, after completing a series of pre-security controls such as account login, exam authorization, and permission verification, the system can initiate and take over some of the vehicle's dynamic control tasks to realize the physical operation of the driving assistance function.

[0056] Optionally, the intelligent driving function execution module in the vehicle's on-board domain controller can receive operation commands and then activate the corresponding subsystem. First, it can wake up the environmental perception unit (e.g., camera, millimeter-wave radar, ultrasonic sensors) to perform real-time environmental modeling, simultaneously calling the high-precision map and positioning module to determine the vehicle's current position and driving target. Then, the decision-making and planning module generates a control strategy based on user-defined parameters (e.g., following distance, lane change sensitivity, parking path preference) and real-time environmental data. Finally, the chassis control unit precisely outputs execution signals for acceleration, deceleration, steering, and gear shifting, achieving continuous and smooth intervention in the vehicle's motion state.

[0057] In the embodiments of this application, through the above steps, the system can no longer passively respond to user operations, but actively require users to master and use the technology first, thus transforming the driving assistance function from technically feasible to a responsibility-bearing one, thereby serving the ultimate goal of safe driving.

[0058] In steps S102 to S108 of this embodiment, if an operation request for a driving assistance function to be performed on the vehicle is detected, the vehicle's login account and the permission information for the driving assistance function corresponding to the login account can be obtained. Then, both the login account and the permission information can be verified, overcoming the limitation in related technologies that rely solely on the validity of the login account as the only prerequisite for enabling the driving assistance function. Thus, if the login account successfully logs into the vehicle and the permission information indicates that the login account has the permission to use the driving assistance function, the operation command corresponding to the operation request is triggered on the vehicle. In response to the operation command, the vehicle is controlled to execute the driving assistance function, thereby solving the technical problem of not being able to effectively control the vehicle to execute the driving assistance function and achieving the technical effect of effectively controlling the vehicle to execute the driving assistance function.

[0059] The method described in this embodiment will be further described below.

[0060] As an optional embodiment, step S104 verifies the login account and permission information to obtain a verification result, including: verifying the login status and login type of the login account to obtain a first verification result, wherein the first verification result is used to indicate whether the login status is a valid login status and whether the login type is the type of the vehicle's local login account; verifying the permission information to obtain a second verification result, wherein the second verification result is used to indicate whether the permission information is valid permission information; and determining the verification result based on the first verification result and the second verification result.

[0061] In this embodiment, the login account and permission information can be dually verified. The first verification result can be used to determine whether the login status is valid and whether the login type is the vehicle's local login account type. The second verification result can be used to determine whether the permission information is valid.

[0062] Optionally, by reading the authentication token, heartbeat signal, and account identifier of the currently logged-in account's session from the vehicle's operating system, it can be determined whether the logged-in account is in a valid login state that is continuously online, has not been forcibly logged out, and has not been locked by the system. Simultaneously, it can be compared to whether the logged-in account exists in a whitelist stored locally on the vehicle. This whitelist can consist of frequently used accounts pre-installed at the vehicle's factory or manually added by the user, and may include a small number of frequently used users (such as the vehicle owner, family members, etc.) to ensure rapid response capabilities in environments without network or with weak network conditions.

[0063] Optionally, if the login status is invalid (e.g., session expired, account abnormal), or the login type is a non-local account (e.g., temporary login via cloud only), the first verification result can indicate failure, without needing to proceed to the subsequent permission information judgment. In this case, a prompt can be made to "Please log in again or switch to the saved login account", thereby avoiding invalid network requests and resource waste.

[0064] Optionally, verifying the permission information can determine whether the logged-in account has successfully completed the mandatory learning and examination for driver assistance functions and obtained a valid permission mark synchronized in the cloud or locally. The permission information can be queried for examination pass flags, function ID matching, data signature integrity, and time validity to ensure that the permission information is not a tampered, expired, or forged temporary state. For example, if a user passes the exam on the mobile app but it hasn't been synchronized to the vehicle due to network latency, an automatic retransmission mechanism can be activated, temporarily retaining the "pending synchronization" status in the local cache and continuing to wait. If synchronization still fails after a timeout, it is still considered a failure, preventing incorrect authorization due to network fluctuations. When the permission information is complete, valid, verifiable, and precisely matches the currently requested function, the second verification result can be determined as passed.

[0065] In this embodiment of the application, the above steps solve the problem of slow response and unavailability of single cloud verification in weak network scenarios, which not only meets the stringent real-time requirements of driving scenarios, but also ensures the comprehensiveness of safety control.

[0066] As an optional embodiment, determining the verification result based on the first verification result and the second verification result includes: in response to the first verification result indicating that the login status is not logged in, determining the verification result as a failed login attempt to the vehicle; or, in response to the first verification result indicating a valid login status and the second verification result indicating invalid permission information, determining the verification result as a login account not having permission to use the driving assistance function; the method further includes: in response to the verification result indicating that the login account failed login to the vehicle, or the permission information indicating that the login account does not have permission to use the driving assistance function, prohibiting the vehicle from executing the driving assistance function, and outputting a prompt message using the vehicle's display module, wherein the prompt message is used to prompt the target object corresponding to the login account to learn the driving assistance function.

[0067] In this embodiment, the process of determining the verification result based on the first verification result and the second verification result includes the following steps: If the first verification result indicates that the login status is not logged in, the verification result can be directly determined as a failed login attempt to the vehicle. If the first verification result indicates that the login status is valid, and the second verification result indicates that the permission information is invalid, the verification result can be determined as a login account lacking the necessary permissions to use the driving assistance functions.

[0068] Optionally, if the first verification result indicates that the login account is not logged in, it means that the vehicle has not identified a valid identity. In this case, no permission information is checked, and the login is directly deemed unsuccessful. At this point, the activation request for the driver assistance function can be immediately blocked to prevent unauthorized operation or accidental activation by others, ensuring clear ownership of vehicle control.

[0069] Optionally, if the first verification passes (i.e., the login status is valid), but the second verification displays invalid permission information. For example, the account may be logged in, but the user has not yet participated in the corresponding driving assistance function learning and examination, or the driving assistance function examination has failed, data has not been synchronized, or the status has expired. In this case, it can be determined that the login account does not have the permission to use the driving assistance function; that is, it has the identity but not the ability, and the driving assistance function is also prohibited from being enabled. Afterwards, the vehicle's display module can be used to output prompt information. For example, the display module (e.g., instrument panel, central control screen, etc.) can proactively output highly structured prompt information, including not only "Current function unavailable," but also clearly stating "Please use the mobile APP to complete the [Navigate on Autopilot (NOA) highway navigation] learning and examination" or "Please log in with the account that has passed the examination first," and simultaneously dynamically generate a scannable QR code on the display module. This QR code is bound to the user's current login account; scanning the code automatically redirects to the corresponding function's dedicated learning and examination module in the mobile APP, achieving one-click redirection and seamless connection.

[0070] As an optional embodiment, the method further includes: in response to the target object completing the learning of the driving assistance function and passing the test corresponding to the driving assistance function, determining the permission information that the login account has the permission to use the driving assistance function.

[0071] In this embodiment, in order to determine whether the permission information indicates that the logged-in account has the permission to use the driving assistance function, it can be detected whether the target object has completed the learning of the driving assistance function and passed the test corresponding to the driving assistance function.

[0072] Optionally, when a user accesses the learning module for driver assistance functions (such as NOA and memory parking) via a mobile app, the user is required to watch a complete instructional video covering the principles, usage boundaries, exception handling, and human-machine responsibility division of the driver assistance function. The learning process cannot be paused, skipped, or fast-forwarded, ensuring the user has a complete understanding of each key aspect of the driver assistance function. After completing the learning, a closed-book quiz can be immediately launched. The quiz questions are closely designed based on the learning materials, employing a question-by-question verification and instant feedback mechanism. If a user answers a question incorrectly, a prompt will immediately appear indicating the key points, requiring the user to answer again until all questions are answered correctly to pass. Upon passing the quiz, the mobile app's permission management module encrypts and packages the user's account ID, function ID, exam time, pass status, device fingerprint, and other key information, generating a digitally signed permission credential. This credential is then synchronously uploaded to the cloud via a backend service, permanently recording and binding the permissions.

[0073] Optionally, after the permission information is successfully written to the cloud, the operation permission status of the login account and the driving assistance function can be automatically set to "approved". This operation permission status can be used as the basis for subsequent vehicle-side verification. Regardless of when, where, or what vehicle the user logs in to the login account, the vehicle-side system can obtain the permission information through real-time cloud caching or offline caching and determine whether to allow the driving assistance function to be enabled.

[0074] As an optional embodiment, the verification result is determined based on the first verification result and the second verification result, including: in response to the first verification result being that the login status is a valid login status and the login type is a local login account, and the second verification result being that the permission information is valid permission information, the verification result is determined to be that the login account has successfully logged into the vehicle, and the permission information is that the login account has the permission to use the driving assistance function.

[0075] In this embodiment, in order to identify and prioritize the activation of driving assistance functions instantly, seamlessly, and with zero latency for users who use the technology frequently, store it locally, and have passed the exam, it is necessary to first determine the verification results.

[0076] Optionally, if the first verification result indicates a valid login status and a local login account type, this means the current user is a trusted user pre-saved by the vehicle (e.g., the vehicle owner, family member, or designated driver). Identity authentication has been completed by the vehicle's local security module within milliseconds, without relying on cloud-based identity services. Simultaneously, if the second verification result indicates valid permission information, this means the current user has passed the mandatory learning exam for the driver assistance function. The exam results have been synchronized and persistently stored in the vehicle's local permission database, and the data has not been tampered with, expired, or matches the current function. At this point, it can be confirmed that the login account has successfully logged into the vehicle, and the permission information indicates the login account has the authority to use the driver assistance function. Without any network communication or waiting for a cloud response, the driver assistance function activation process can begin immediately.

[0077] In this embodiment, in intelligent driving scenarios, especially in high-speed driving environments such as highways and urban expressways, users have extremely low tolerance for delays in the response of driving assistance functions. Any system delays or function lags caused by network jitter or signal interruptions may result in operational gaps, delayed takeover, or even safety hazards. By caching the complete permission information (identity + examination status) of highly trusted users locally on the vehicle, the strong binding relationship between the activation of driving assistance functions and network availability is decoupled. This ensures the immediate availability of driving assistance functions even in extreme conditions such as no network, weak network, and signal blind spots, maximizing the continuity and reliability of the user experience.

[0078] As an optional embodiment, step S102, in response to detecting an operation request for a driving assistance function to be performed on the vehicle, obtains the vehicle's login account and the permission information of the driving assistance function corresponding to the login account, including: in response to the login account being the vehicle's local login account, obtaining the permission information of the driving assistance function corresponding to the login account; in response to the login account being a login account other than the local login account, sending a query request instruction to the cloud, wherein the query request instruction is used to indicate an instruction to query the identification information of the login account; in response to the query request instruction, controlling the cloud to send the permission information of the driving assistance function corresponding to the login account to the vehicle.

[0079] In this embodiment, based on the type of login account, an efficient and reliable path for obtaining permission information can be dynamically selected, realizing an intelligent data retrieval strategy that prioritizes local access and provides backup in the cloud.

[0080] Optionally, when a user initiates an operation request for a certain driving assistance function (such as NOA, memory parking, automatic lane change, etc.) on the vehicle, the identity attributes of the currently logged-in account can be identified. That is, whether the login account is a local login account that has been pre-stored in the vehicle's local storage, or a non-local account that is logging in for the first time or has never been used in the vehicle before, i.e., a login account other than the local login account.

[0081] Optionally, if the login account is a local login account, the permission information corresponding to that login account can be directly read from the vehicle's secure storage area. This includes key fields such as whether the user has passed the learning and testing for the specified driver assistance function, the test passing time, the function version number, and the signature verification code. This process is completed locally without relying on any external communication, resulting in extremely fast response times, completing within hundreds of milliseconds. This ensures that users can still obtain function authorization immediately even when driving at high speeds or in environments with low network quality.

[0082] Optionally, if the login account is a different account than the local login account (e.g., a family member temporarily borrowing the account, a rental vehicle user, a member of a company fleet, etc.), it can automatically switch to cloud collaboration mode and immediately send a query request instruction containing the unique identifier of the login account (e.g., mobile phone number, account ID, device fingerprint, etc.) to the cloud. This query request instruction only carries the minimum dataset required for identity authentication and does not involve privacy-sensitive information, complying with the principle of data minimization. After receiving the query request instruction, the cloud retrieves all learning and examination records completed by the login account on any device and at any time in the global user database based on the login account ID, confirming whether the examination for the currently requested function has been passed and whether the permission information has expired. After confirmation, the cloud encrypts and packages the latest permission status data (including digital signature) of the login account and sends it to the vehicle in real time. After receiving the permission status data, the vehicle immediately performs integrity verification and signature verification to ensure that the permission status data has not been tampered with. After successful verification, the permission information is cached in the local temporary storage area for quick subsequent access, and the local registration of the login account is completed, laying the foundation for local response for future use.

[0083] In this embodiment, the above steps do not simply involve uniformly hosting all user permissions in the cloud, which would lead to excessive network dependence and slow response; nor do they involve permanently storing all login account information on the vehicle, resulting in high storage pressure and poor scalability. Instead, the system intelligently identifies the account type of the login account and automatically selects the optimal path. That is, local storage is used for high-frequency and stable users to ensure response speed, while cloud query is used for temporary and variable users to ensure the authority of permissions and consistency across platforms.

[0084] As an optional embodiment, the method further includes: locally storing the driving assistance functions controlled by the vehicle; and / or uploading the driving assistance functions to the cloud for backup.

[0085] In this embodiment, after a user successfully logs in and passes the exam, they can activate driver assistance functions (such as NOA highway navigation, memory parking, and automatic lane changing). During the operation of these functions, not only can vehicle control commands be executed, but personalized operating parameters and usage preferences can also be collected and recorded simultaneously. These personalized operating parameters and preferences may include, but are not limited to: following distance settings, cruise speed range, lane change trigger sensitivity, parking path deviation, automatic start-stop threshold, radar detection priority, and preferred takeover response time. These operating parameters are not fixed factory values ​​but rather represent the unique driving style that users gradually develop through actual use, forming the core data assets for achieving "human-vehicle adaptation."

[0086] Optionally, after the driving assistance function finishes execution, these personalized operation parameters and usage preferences, along with contextual information such as driving assistance function usage duration, environmental conditions, and triggering scenarios, can be automatically archived in the form of encrypted structured data packets. First, they are persistently saved in the vehicle's local storage space (e.g., the secure user configuration area of ​​the vehicle's infotainment system). Second, they are remotely backed up by uploading them to the configuration database of the user's exclusive login account in the cloud via an encrypted communication channel.

[0087] Optionally, through the above steps, users do not need to adjust function parameters from scratch each time they change vehicles or log in to their accounts again. This mechanism ensures that users can instantly restore their preferred settings without an internet connection when logging in to the same vehicle again, achieving a seamless experience of "use it as soon as you get in the car, no adjustment required." Furthermore, cloud backup allows the system to automatically retrieve cloud configurations when the user logs in to the same account on other vehicles or devices that support this system, achieving cross-platform continuity of "account follows the user, preferences synchronized."

[0088] In the embodiments of this application, if an operation request for a vehicle to perform a driving assistance function is detected, the vehicle's login account and the corresponding driving assistance function permission information can be obtained. Then, both the login account and permission information can be verified, overcoming the limitation of related technologies that rely solely on the validity of the login account as the only prerequisite for enabling the driving assistance function. Thus, if the login account successfully logs into the vehicle and the permission information indicates that the login account has the permission to use the driving assistance function, the operation command corresponding to the operation request is triggered on the vehicle. In response to the operation command, the vehicle is controlled to execute the driving assistance function, thereby solving the technical problem of ineffective control over the vehicle's execution of driving assistance functions and achieving the technical effect of effectively controlling the vehicle to execute driving assistance functions.

[0089] The technical solutions of the embodiments of this application will be illustrated below with reference to preferred embodiments.

[0090] Currently, related technologies often detect whether a driver has passed the learning exam by logging in through an in-vehicle terminal, but the processing and information collaboration among different personnel are problematic.

[0091] Among related technologies, one proposed method for guiding intelligent driving instruction involves adjusting learning content through user information collection, but lacks verification of learning outcomes. Another proposed method is a vehicle driving instruction assistance practice method that compares vehicle targets with driver operations to guide and prompt driving actions, improving driving instruction efficiency, but it does not constrain the use of driving assistance functions.

[0092] Due to the rapid development of the vehicle industry (such as new energy vehicles) and the deep penetration of artificial intelligence technology, the technical level of automotive intelligent driving assistance systems has achieved a leapfrog improvement. Various derivative functions have been continuously enriched and improved, gradually extending from basic adaptive cruise control (ACC) to more complex scenario functions such as NOA highway navigation and memory parking. The operational logic of intelligent driving assistance functions has become increasingly complex, raising the barrier to entry and leading to cognitive biases among many users, blurring the boundaries of responsibility in human-machine co-driving. Furthermore, insufficient understanding of these functions results in inappropriate responses to emergencies such as takeover attempts, malfunctions, and unexpected road conditions, leading to frequent safety accidents.

[0093] To address the aforementioned issues, this application provides a method for controlling the learning and testing of intelligent driving assistance functions. This method employs a collaborative approach between local and cloud-based systems to specifically resolve problems such as inconvenient switching between different users, confusing permissions, inability to maintain personal preferences, and high deployment costs. Specifically, by pre-setting basic users locally, network dependency issues are effectively avoided, ensuring rapid response of the intelligent driving assistance function when switching users and guaranteeing smooth operation. Cloud-based collaborative management enables centralized management of user information, supporting unlimited expansion of the number of users and allowing users to freely switch between different vehicle models on the same platform, achieving seamless import of personalized preferences and significantly improving the user experience and operational efficiency. Furthermore, the learning and testing process is deployed on both the mobile application and the cloud, optimizing local deployment costs and further enhancing the product's market competitiveness.

[0094] In other words, this application embodiment restricts the use of intelligent driving assistance functions, conducts system function learning and testing to improve users' understanding of the functions and operational proficiency, and mitigates safety risks to a certain extent. Simultaneously, the collaborative binding of learning and testing with accounts enables constraint management for different users and also retains users' driving habits, achieving seamless integration of usage and preferences, further improving human-machine collaboration and driving safety.

[0095] Figure 2 This is a flowchart of a learning and testing control method for an intelligent driving assistance function according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps.

[0096] Step S201: Log in to the corresponding account on the mobile APP to access the intelligent driving assistance learning and examination module.

[0097] In this embodiment, the user first logs in to the account corresponding to the mobile APP, and then can access the intelligent driving assistance learning and examination module in two ways.

[0098] Optionally, in Method 1, while logged into the mobile app, users can manually locate the dedicated entry point for the intelligent driving assistance function, click to enter the learning and examination module, and view the functions categorized by type (highway navigation, memory parking, etc.). Users can select the corresponding function category based on the specific function they intend to use to begin the learning and examination process. Alternatively, when operating the intelligent driving assistance function on the vehicle's large screen, if the currently logged-in account has not passed the learning and examination for that function, the vehicle will automatically display a prompt for the corresponding function's learning and examination, along with a QR code for the dedicated entry point for the intelligent driving assistance learning and examination on the mobile app. Users can scan this QR code with their logged-in mobile app, and the app will automatically redirect to the intelligent driving assistance learning and examination module to begin the learning and examination process.

[0099] Step S202: Start the learning and examination process.

[0100] In this embodiment, after a user starts the learning and examination process, the process can be executed in the order of learning, examination, and result upload.

[0101] Optionally, the learning process requires users to first watch the instructional videos corresponding to the intelligent driving assistance functions. The instructional videos cover key points such as the operation methods, usage scenarios, abnormal handling, and the division of responsibilities between humans and machines, ensuring that users fully understand the functions. The learning process cannot be paused, and the test can only be started after the user has completed the learning process.

[0102] Optionally, the exam questions are designed around the learning content to test the user's understanding of how to use the functions, the steps to handle exceptions, and the definition of related responsibilities. The exam adopts a question-by-question, real-time verification mode. After the user completes the current question, the system immediately judges the answer. If the answer is wrong, the system will pop up the corresponding knowledge point prompts. The user needs to answer the question again according to the prompts until the answer is correct before moving on to the next question.

[0103] Optionally, once the user completes all questions and answers them all correctly, the exam ends, and the mobile app will pop up a message indicating that the exam is complete and close. At the same time, the system will synchronously upload the account information and the exam results for the corresponding functions to the cloud for permanent storage. At this point, the status of the corresponding function module that passed the exam will be automatically updated to the relearning status, making it convenient for the user to review the key points of the function as needed later.

[0104] Step S203: Make an operation request for intelligent driving assistance function.

[0105] In this embodiment, if the user has not logged into the vehicle's system account after starting the vehicle, when the user attempts to operate any intelligent driving assistance function, the vehicle system will display an account login prompt on the large screen and provide an account login entry. Only after the user completes the login can they make operation requests for intelligent driving assistance functions.

[0106] Step S204: Perform permission authentication using the exam results transmitted through the cloud, and execute the response operation based on the authentication result.

[0107] In this embodiment, after the user logs in to the vehicle's large screen account, when the user operates the intelligent driving assistance function switch, the intelligent driving assistance system will perform permission authentication through the test results transmitted from the cloud, and execute the response operation based on the authentication result.

[0108] Optionally, permission authentication: After obtaining the test results of the currently logged-in account corresponding to the function transmitted through the cloud, the intelligent driving assistance system determines whether the user has the permission to operate the function based on whether the test for the corresponding function has been passed.

[0109] Optionally, the result processing is as follows: If the permission authentication fails, the intelligent driving assistance function will not respond to the user's operation command. At the same time, a learning and examination prompt will pop up on the vehicle's large screen, and a QR code for the mobile APP learning and examination entry will be displayed simultaneously to guide the user to complete the prerequisite learning and examination conditions. If the permission authentication passes, the intelligent driving assistance system will respond normally to the user's operation command, complete the on / off switching of the corresponding function, and at the same time, the intelligent driving assistance system will store the intelligent driving assistance function preferences set by the user during this operation to the local dedicated storage space of the corresponding account, and simultaneously upload it to the cloud for backup, ensuring that the user can directly call it up in subsequent use to meet the user's personalized usage needs.

[0110] Step S205: Execute different personalized settings synchronization logic based on whether the newly logged-in account is an existing local account.

[0111] In this embodiment, when a user changes and switches login accounts on the vehicle's infotainment system, the system will execute different personalized settings synchronization logic based on whether the new login account is an existing local account, thereby enabling rapid account switching and cross-platform information continuity.

[0112] Optionally, account type: After the vehicle-mounted infotainment system detects that a user has switched login accounts, it immediately determines the characteristics of the newly logged-in account to see if the account has been stored in the vehicle's local storage space.

[0113] Optionally, synchronization is enabled. If the newly logged-in account is an existing local account, the vehicle's infotainment system will synchronize the corresponding locally stored information to the intelligent driving assistance system. The intelligent driving assistance system will then access the locally stored function settings and complete the settings switch synchronously with the account switching operation, achieving rapid response from the local account and eliminating network dependence. If the newly logged-in account is not an existing local account, the vehicle will send a data request to the cloud to retrieve the intelligent driving assistance function settings information saved in the cloud for the new account. The intelligent driving assistance system will then refresh the local storage space on the vehicle with the new account's settings, completing the import of personalized settings. This cloud-based approach allows for unlimited expansion of user accounts, ensuring seamless continuation of intelligent driving assistance function settings when users use the vehicle across platforms and devices, meeting the continuity needs of users switching between vehicles and improving the user experience.

[0114] Figure 3 This is a flowchart illustrating a method for execution between a mobile app and the cloud according to an embodiment of this application, such as... Figure 3 As shown, the method includes the following steps.

[0115] In step S301, the user directly opens the mobile app.

[0116] In this embodiment, the user can directly open the mobile app.

[0117] Step S302: Begin studying for the exam.

[0118] In this embodiment, after the user directly opens the mobile app, they can enter the learning and examination process through a pop-up window via a QR code.

[0119] Step S303: Determine if the account is logged in.

[0120] In this embodiment, it can be determined whether the account is logged in. If the account is logged in, step S305 is executed; otherwise, step S304 is executed.

[0121] Step S304 prompts you to log in to your account.

[0122] In this embodiment, if the account is not logged in, a login prompt will be displayed.

[0123] Step S305: Proceed to the video tutorial.

[0124] In this embodiment, if an account is logged in, video content is retrieved from the cloud and accessed via video learning tutorials.

[0125] Step S306: Determine whether the learning is complete.

[0126] In this embodiment, it can be determined whether the learning is complete. If the learning is complete, step S307 is executed; otherwise, step S305 is executed.

[0127] Step S307: Proceed to the exam.

[0128] In this embodiment, if the learning is completed, the exam begins.

[0129] Step S308: Begin answering the questions.

[0130] In this embodiment, upon entering the exam, the exam questions are retrieved from the cloud, and the user can begin answering the questions.

[0131] Step S309: Determine whether the exam has been passed.

[0132] In this embodiment, it can be determined whether the exam has been passed. If passed, step S310 is executed; otherwise, step S307 is executed.

[0133] Step S310: Store the account and exam results.

[0134] In this embodiment, if the exam is passed, the account and exam results are stored in the cloud.

[0135] Step S311: Update the status.

[0136] In this embodiment, after storing the account and exam results in the cloud, the status can be updated.

[0137] Figure 4 This is a flowchart illustrating a method for communication between an in-vehicle infotainment system and the cloud, according to an embodiment of this application. Figure 4 As shown, the method includes the following steps.

[0138] Step S401: Receive account information.

[0139] In this embodiment, the in-vehicle infotainment system can receive account information.

[0140] Step S402: Determine whether the account is a local account.

[0141] In this embodiment, it can be determined whether the account is a local account. If so, step S403 is executed; otherwise, step S404 is executed.

[0142] Step S403: Obtain setting information.

[0143] In this embodiment, if the account is a local account, the settings information is obtained through the cloud.

[0144] Step S404: Local account storage access.

[0145] In this embodiment, if the account is not a local account, the local account storage is accessed through the in-vehicle infotainment system.

[0146] Figure 5 This is a flowchart illustrating a method for execution between an in-vehicle infotainment system and an advanced driver assistance system according to an embodiment of this application, such as... Figure 5 As shown, the method includes the following steps.

[0147] Step S501: Perform function permission authentication.

[0148] In this embodiment, after the in-vehicle infotainment system receives account information and obtains the exam results via the cloud, it can authenticate function permissions through the advanced driver assistance system. The function settings are configured by the in-vehicle infotainment system.

[0149] Step S502: Determine if the account is logged in.

[0150] In this embodiment, it can be determined whether the account is logged in. If yes, then step S504 is executed; otherwise, step S503 is executed.

[0151] Step S503 prompts you to log in to your account.

[0152] In this embodiment, if the account is not logged in, the in-vehicle infotainment system will prompt the user to log in.

[0153] Step S504: Determine whether the exam has been passed.

[0154] In this embodiment, it can be determined whether the exam has been passed. If so, step S506 is executed; otherwise, step S505 is executed.

[0155] Step S505 prompts you to study and take the exam.

[0156] In this embodiment, if the test is failed, the in-vehicle infotainment system will prompt the user to study and take the test again.

[0157] Step S506: Switch the function state.

[0158] In this embodiment, if the test is passed, the function state is switched through the advanced driver assistance system.

[0159] Step S507: Perform local storage.

[0160] In this embodiment, after switching functional states, local storage can be performed via the advanced driver assistance system. The stored results can then be set in the cloud.

[0161] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0162] According to an embodiment of this application, a vehicle function control device is also provided. It should be noted that this vehicle function control device can be used to execute the vehicle function control method described in the embodiment.

[0163] Embodiments of this application also provide a vehicle function control device. Figure 6 This is a schematic diagram of a vehicle function control device according to an embodiment of this application, such as... Figure 6 As shown, the vehicle's function control device 600 includes: an acquisition unit 602, a verification unit 604, a triggering unit 606, and a control unit 608.

[0164] The acquisition unit 602 is used to acquire the vehicle's login account and the permission information of the driving assistance function corresponding to the login account in response to the detection of an operation request for the driving assistance function to be performed on the vehicle. The permission information is used to indicate whether the login account has the permission to use the driving assistance function.

[0165] Verification unit 604 is used to verify the login account and permission information and obtain the verification result.

[0166] Triggering unit 606 is used to trigger the operation command corresponding to the operation request on the vehicle in response to the verification result indicating that the login account has successfully logged into the vehicle and the permission information indicating that the login account has the permission to use driving assistance functions.

[0167] Control unit 608 is used to control the vehicle to perform driving assistance functions in response to operating commands.

[0168] Optionally, the verification unit 604 includes: a first verification subunit, used to verify the login status and login type of the login account to obtain a first verification result, wherein the first verification result is used to indicate whether the login status is a valid login status and whether the login type is the type of the vehicle's local login account; a second verification subunit, used to verify the permission information to obtain a second verification result, wherein the second verification result is used to indicate whether the permission information is valid permission information; and a first determination subunit, used to determine the verification result based on the first verification result and the second verification result.

[0169] Optionally, the first determining subunit includes: a second determining subunit, configured to determine that the verification result is a failed login attempt if the first verification result indicates that the login status is not logged in; or, if the first verification result indicates a valid login status and the second verification result indicates invalid permission information, the verification result is that the login account does not have permission to use the driving assistance function; the vehicle's function control device 600 further includes: a prohibition unit, configured to prohibit the vehicle from executing driving assistance functions if the verification result indicates a failed login attempt or if the permission information indicates that the login account does not have permission to use the driving assistance function, and to output prompt information using the vehicle's display module, wherein the prompt information is used to prompt the target object corresponding to the login account to learn the driving assistance function.

[0170] Optionally, the vehicle's function control device 600 further includes a determining unit, configured to determine, in response to the target object completing the learning of the driving assistance function and passing the test corresponding to the driving assistance function, that the login account has the permission to use the driving assistance function.

[0171] Optionally, the first determining subunit includes: a third determining subunit, configured to determine, in response to the first verification result being that the login status is a valid login status and the login type is a local login account, and the second verification result being that the permission information is valid permission information, that the verification result is that the login account has successfully logged into the vehicle, and the permission information is that the login account has the permission to use driving assistance functions.

[0172] Optionally, the acquisition unit 602 includes: an acquisition subunit, used to acquire the permission information of the driving assistance function corresponding to the login account in response to the login account being the vehicle's local login account; a sending subunit, used to send a query request instruction to the cloud in response to the login account being a login account other than the local login account, wherein the query request instruction is used to indicate an instruction to query the identification information of the login account; and a distribution subunit, used to control the cloud to distribute the permission information of the driving assistance function corresponding to the login account to the vehicle in response to the query request instruction.

[0173] Optionally, the vehicle's function control device 600 further includes: a storage unit for locally storing the driving assistance functions controlled by the vehicle; and / or an upload unit for uploading the driving assistance functions to the cloud for backup.

[0174] In this embodiment, in response to detecting an operation request for a driving assistance function to be performed on the vehicle, the acquisition unit 602 acquires the vehicle's login account and the permission information of the driving assistance function corresponding to the login account. The permission information indicates whether the login account has the permission to use the driving assistance function. The verification unit 604 verifies the login account and the permission information to obtain a verification result. In response to the verification result that the login account has successfully logged into the vehicle and the permission information indicates that the login account has the permission to use the driving assistance function, the triggering unit 606 triggers the operation command corresponding to the operation request on the vehicle. The control unit 608 responds to the operation command and controls the vehicle to execute the driving assistance function, thereby solving the technical problem of not being able to effectively control the vehicle to execute the driving assistance function and achieving the technical effect of effectively controlling the vehicle to execute the driving assistance function.

[0175] This application also provides an electronic device 70, please refer to... Figure 7 , Figure 7 This is a structural diagram of an electronic device provided in one embodiment of the present application, including a processor 710 and a memory 720, wherein the memory 720 is used to store computer programs; the processor 710 is used to execute the programs stored in the memory 720 to implement the methods described in any embodiment of the present application.

[0176] According to another aspect of the embodiments of this application, a processor is also provided. The processor is used to run a program, wherein the program is executed by the processor to perform the methods described in the embodiments of this application.

[0177] According to an embodiment of this application, a computer-readable storage medium is also provided, which includes a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to execute the methods of various embodiments of this application.

[0178] According to an embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0179] According to an embodiment of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the methods in various embodiments of this application.

[0180] According to embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods in various embodiments of this application.

[0181] According to an embodiment of this application, a vehicle is also provided that implements the methods in the various embodiments of this application when executed.

[0182] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

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

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

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

[0187] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for controlling the function of a vehicle, characterized in that, include: In response to detecting an operation request for a driving assistance function to be performed on the vehicle, the login account of the vehicle and the permission information of the driving assistance function corresponding to the login account are obtained, wherein the permission information is used to indicate whether the login account has the permission to use the driving assistance function; The login account and the permission information are verified to obtain the verification result. In response to the verification result indicating that the login account has successfully logged into the vehicle, and the permission information indicating that the login account has the permission to use the driving assistance function, the operation command corresponding to the operation request is triggered on the vehicle. In response to the operation command, the vehicle is controlled to perform the driving assistance function.

2. The method according to claim 1, characterized in that, The login account and permission information are verified to obtain the verification result, including: The login status and login type of the login account are verified to obtain a first verification result, wherein the first verification result is used to indicate whether the login status is a valid login status and whether the login type is the type of the vehicle's local login account; The permission information is verified to obtain a second verification result, wherein the second verification result is used to indicate whether the permission information is valid permission information; The verification result is determined based on the first verification result and the second verification result.

3. The method according to claim 2, characterized in that, Determining the verification result based on the first verification result and the second verification result includes: In response to the first verification result indicating that the login status is not logged in, the verification result is determined to be that the login account failed to log in to the vehicle; or, in response to the first verification result indicating that the login status is a valid login status and the second verification result indicating that the permission information is invalid permission information, the verification result is determined to be that the login account does not have the permission to use the driving assistance function. The method further includes: In response to the verification result indicating that the login account failed to log in to the vehicle, or the permission information indicating that the login account does not have permission to use the driving assistance function, the vehicle is prohibited from executing the driving assistance function, and a prompt message is output using the vehicle's display module, wherein the prompt message is used to prompt the target object corresponding to the login account to learn the driving assistance function.

4. The method according to claim 3, characterized in that, The method further includes: In response to the target object completing the learning of the driving assistance function and passing the test corresponding to the driving assistance function, the permission information is determined to indicate that the login account has the permission to use the driving assistance function.

5. The method according to claim 2, characterized in that, Determining the verification result based on the first verification result and the second verification result includes: In response to the first verification result indicating that the login status is the valid login status and the login type is the local login account, and the second verification result indicating that the permission information is the valid permission information, it is determined that the verification result indicates that the login account has successfully logged into the vehicle, and the permission information indicates that the login account has the permission to use the driving assistance function.

6. The method according to claim 1, characterized in that, In response to detecting an operation request for a driving assistance function to be performed on the vehicle, the system obtains the vehicle's login account and the permission information for the driving assistance function corresponding to the login account, including: In response to the login account being the local login account of the vehicle, the permission information of the driving assistance function corresponding to the login account is obtained; In response to the login account being a login account other than the local login account, a query request instruction is sent to the cloud, wherein the query request instruction is used to indicate an instruction to query the identification information of the login account; In response to the query request command, the cloud is controlled to send the permission information of the driving assistance function corresponding to the login account to the vehicle.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The driving assistance functions controlled by the vehicle are stored locally; and / or, The aforementioned driving assistance functions are uploaded to the cloud for backup.

8. A vehicle function control device, characterized in that, include: The acquisition unit is configured to, in response to detecting an operation request for a driving assistance function to be performed on the vehicle, acquire the vehicle's login account and the permission information of the driving assistance function corresponding to the login account, wherein the permission information is used to indicate whether the login account has the permission to use the driving assistance function; The verification unit is used to verify the login account and the permission information to obtain the verification result; A triggering unit is configured to, in response to the verification result indicating that the login account has successfully logged into the vehicle and the permission information indicating that the login account has permission to use the driving assistance function, trigger the operation instruction corresponding to the operation request on the vehicle. A control unit is configured to control the vehicle to perform the driving assistance function in response to the operation command.

9. A processor, characterized in that, The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 7 when it runs.

10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 7.

Images