Method for controlling vehicle authority, electronic device, and vehicle

Abstract

The application provides a vehicle permission control method, an electronic device and a vehicle, applied to the intelligent network connection technical field, when a permission sharing instruction sent by a permission sharing user is received and it is determined that the permission sharing user is a valid user, a permission receiving user and permission information are determined based on the permission sharing instruction; receiving user image information of the permission receiving user is obtained, and identity authentication is performed on the permission receiving user to obtain an authentication result; when the authentication result is authentication passed, a permission receiving user is sent to the permission receiving user, and the whole process does not need the mobile devices of the permission sharing user and the permission receiving user to participate in interaction, and the sharing of the control vehicle permission can be realized only through the direct interaction of the permission sharing user and the permission receiving user with the vehicle machine, greatly simplifying the permission sharing process and improving the use experience of the user.

Description

Technical Field

[0001] This application relates to the field of intelligent connected vehicle technology, and in particular to a method for controlling vehicle access, an electronic device, and a vehicle. Background Technology

[0002] Currently, when using digital key permissions for quick sharing, it all relies on the application on the user's mobile device. Car owners must use their mobile devices to operate, and temporary users also need to complete a complex verification process through the application on their mobile devices, making the temporary permission sharing process very cumbersome and resulting in a poor user experience. Summary of the Invention

[0003] In view of this, the purpose of this application is to propose a vehicle access control method, electronic device and vehicle to solve or partially solve the problems mentioned in the background art and improve the user experience.

[0004] To achieve the above objectives, the first aspect of this application provides a method for controlling vehicle access, comprising:

[0005] In response to receiving a permission sharing instruction sent by a permission sharing user and determining that the permission sharing user is a valid user, the permission receiving user and permission information are determined based on the permission sharing instruction; Obtain the image information of the user receiving the permission, verify the identity of the user receiving the permission, and obtain the verification result; In response to the verification result being successful, the received user image information and the permission information are associated and stored, and a command to allow vehicle control is sent to the user with the permission.

[0006] In this way, by simply receiving the permission sharing command sent directly by the permission sharing user via voice and verifying both the permission sharing user and the permission receiving user, the permission to control the vehicle can be directly shared with the permission receiving user. The entire process does not require the mobile devices of the permission sharing user and the permission receiving user to participate in the interaction. The sharing of vehicle control permissions can be achieved solely through the interaction between the permission sharing user and the permission receiving user and the vehicle system, which greatly simplifies the permission sharing process and improves the user experience.

[0007] Based on the same inventive concept, a second aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the method as described in any of the first aspects above.

[0008] Based on the same inventive concept, a third aspect of this application provides a vehicle that includes the electronic equipment described in the second aspect above.

[0009] As can be seen from the above, the vehicle access control method, electronic device, and vehicle provided in this application, when receiving an access sharing instruction sent by an access sharing user and determining that the access sharing user is a valid user, determine the access receiving user and access information based on the access sharing instruction; obtain the receiving user's image information and verify the access receiving user to obtain a verification result; when the verification result is successful, send an access control instruction to the access receiving user. In this way, by simply receiving the access sharing instruction sent directly by the access sharing user via voice and verifying both the access sharing user and the access receiving user, the access to control the vehicle can be directly shared with the access receiving user. The entire process does not require interaction between the access sharing user and the access receiving user's mobile devices; the sharing of vehicle access can be achieved solely through the interaction between the access sharing user and the access receiving user and the vehicle's infotainment system, greatly simplifying the access sharing process and improving the user experience. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 A diagram illustrating a usage scenario where both the car owner and temporary users share a temporary digital key inside the vehicle. Figure 2 This is a flowchart illustrating the vehicle access control method according to an embodiment of this application; Figure 3 This is a schematic diagram of a vehicle access control device according to an embodiment of this application; Figure 4 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0012] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0013] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0014] With the increasing popularity of digital key technology, traditional physical car keys are being replaced by digital keys carried on mobile devices such as smartphones, smartwatches, or smart bracelets. A digital key is an electronic credential stored in a smart device that uses wireless technologies such as Bluetooth, Near Field Communication (NFC), or Ultra-Wideband (UWB) to allow users to unlock and start their vehicles without carrying a physical key.

[0015] Digital keys primarily communicate with vehicles using the following wireless technologies: Bluetooth is the most common solution. When a user approaches the vehicle with a paired mobile device carrying a digital key, Bluetooth will detect it and unlock the car. Once inside, the car can be started. Typically, the digital key-related application needs to be running in the background.

[0016] Near Field Communication (NFC): This requires placing a specific area of ​​the mobile device carrying the digital key (such as near the rear camera) close to the vehicle's door handle or the sensor area on the center console. One tap unlocks the car, and another tap locks it. Starting the car also requires placing the mobile device in a designated sensor area (such as the wireless charging pad). Its main advantage is extremely low power consumption; the phone can usually still be used for a period of time after it has been powered off.

[0017] Ultra-wideband (UWB) is the latest high-precision technology that enables a seamless user experience: users don't need to take out their mobile devices carrying digital keys, or even touch anything. As long as the mobile device is in the user's pocket or bag, and they approach the vehicle within a few meters, the headlights automatically turn on, and pulling the door handle unlocks the door. Because it can accurately locate the mobile device's position (e.g., whether it's outside or inside the vehicle), it has stronger protection against relay attacks.

[0018] In temporary vehicle use scenarios, car owners can also quickly share digital key permissions with others. Without having to hand over the physical key in person, car owners can directly and securely share partial, time-limited access to the vehicle's digital key (such as a Bluetooth or NFC key) with others through mobile applications, WeChat mini-programs, etc.

[0019] Typically, in temporary situations where someone needs to use the car briefly—such as a friend borrowing the car, a family member picking up items, valet parking, car washing / moving, or package delivery—the car owner can generate a "virtual key" via a link and send it to the designated person through a few steps on a mobile device, such as a smartphone. The recipient doesn't need to download a full car control application; they can often receive it directly through a WeChat / Alipay mini-program. The car owner can set the sharing validity period (e.g., 1 hour, 1 day) and specific permissions (e.g., only allowing door opening but not driving away, limiting maximum speed, restricting driving area, etc.). Permissions can be remotely revoked at any time after expiration or when the car is no longer in use.

[0020] However, currently, when using digital key permissions for quick sharing, it all relies on the application on the user's mobile device (such as a mobile phone). The car owner must use the mobile device to operate, and temporary users also need to complete a complex verification process through the application on their mobile device, making the temporary permission sharing process very cumbersome and inconvenient.

[0021] In particular, such as Figure 1 As shown, when both the car owner and the temporary user are in the car and the car owner wants to share digital key permissions with the temporary user, the car owner needs to open the application on their mobile device to operate, and the temporary user also needs to complete a complicated verification process through the application on their mobile device before the digital key permissions can be successfully shared with the temporary user. The whole process is very cumbersome and greatly reduces the user experience.

[0022] Therefore, simplifying the digital key permission sharing process and improving the user experience are urgent issues that need to be addressed.

[0023] Based on this, see Figure 2 This application provides a method for controlling vehicle permissions, executed by the vehicle's infotainment system, the method specifically including the following steps: Step S100: In response to receiving a permission sharing instruction sent by a permission sharing user and determining that the permission sharing user is a valid user, determine the permission receiving user and permission information based on the permission sharing instruction; Step S200: Obtain the receiving user image information of the authorized receiving user, and verify the identity of the authorized receiving user to obtain the verification result; Step S300: In response to the verification result being successful, the received user image information and the permission information are associated and stored, and a command to allow vehicle control is sent to the permission-receiving user.

[0024] Specifically, when the vehicle system receives a permission sharing instruction sent directly by the permission sharing user via voice, it determines whether the permission sharing user is a valid user. A valid user refers to a legitimate user who has been associated with or registered with the vehicle system in advance, such as the vehicle owner or the vehicle owner's family members.

[0025] The permission sharing command is a voice command, which means that the user sends the command directly by voice. The user does not need to interact with the vehicle system based on the user's mobile device, but interacts with the vehicle system by voice.

[0026] When it is determined that the permission sharing user is a valid user, it means that the permission sharing user who sends the permission sharing instruction is a legitimate user who has been associated with or registered with the vehicle system in advance. Therefore, the permission sharing instruction is a legitimate instruction. Thus, the permission receiving user and permission information are determined based on the permission sharing instruction.

[0027] The user receiving the permission is the recipient of the temporary permission sharing, meaning that this person currently does not have a valid digital key and cannot control the vehicle, while the permission sharing user wants to share temporary digital key permissions that can control the vehicle with this person.

[0028] The permission information includes the basic information of the user receiving the permission (including the user's identity information, such as ID card number and / or mobile phone number) and the permitted content for the user (including the permission time range and permission location range). The permission time range is the time range during which the user is allowed to use the permission, such as 8:00~12:00, or 15:00~22:00, etc. The permission location range is the geographical area range during which the user is allowed to use the permission, such as limited to urban areas, or limited to a specific city, etc.

[0029] Then, the system obtains the received user image information of the authorized user, which is the image information of the person receiving the authorized user. The received user image information can be image information and / or video information.

[0030] Then, the user receiving the permission is authenticated to determine whether their identity matches the target person the user sharing the permission wants to share it with. The final verification result is then obtained. If the user receiving the permission is determined to be the same person as the target person, the verification result is "verification passed"; if they are not, the verification result is "verification failed".

[0031] When the verification result is successful, it indicates that the identity of the user receiving the permission is the same person as the target person to whom the user sharing the permission wants to share it. At this point, the image information of the receiving user and the permission information are associated and stored, that is, the image information of the person granted permission (i.e., the receiving user) and the permitted permission content (i.e., the permission information) are associated and stored together. A command to grant vehicle control is then sent to the user receiving the permission. For example, a command to grant vehicle control is sent to the user receiving the permission's mobile device, such as a mobile phone, smart bracelet, or smartwatch, to notify the user that they have obtained temporary permission to control the vehicle.

[0032] In this way, by simply receiving the permission sharing command sent directly by the permission sharing user via voice and verifying both the permission sharing user and the permission receiving user, the permission to control the vehicle can be directly shared with the permission receiving user. The entire process does not require the mobile devices of the permission sharing user and the permission receiving user to participate in the interaction. The sharing of vehicle control permissions can be achieved solely through the interaction between the permission sharing user and the permission receiving user and the vehicle system, which greatly simplifies the permission sharing process and improves the user experience.

[0033] Furthermore, by associating and storing the received user image information and the permission information, on the one hand, the user image information of the permission-receiving user is stored, making the permission-receiving user temporarily a registered or stored legitimate user; on the other hand, when the permission-receiving user controls the vehicle, their control over the vehicle can be directly restricted based on the corresponding permission information, ensuring the security of vehicle control.

[0034] In this application, upon receiving a permission sharing instruction from a permission sharing user and confirming that the permission sharing user is a valid user, the system determines the permission receiving user and permission information based on the permission sharing instruction; it obtains the receiving user's image information and verifies the permission receiving user's identity to obtain a verification result; if the verification result is successful, it sends a command to the permission receiving user to allow vehicle control. Thus, by simply receiving a permission sharing instruction directly sent by the permission sharing user via voice and verifying both the permission sharing user and the permission receiving user, the permission to control the vehicle can be directly shared with the permission receiving user. The entire process does not require interaction between the permission sharing user's and the permission receiving user's mobile devices; the sharing of vehicle control permission can be achieved solely through interaction between the permission sharing user and the permission receiving user and the vehicle's infotainment system, greatly simplifying the permission sharing process and improving the user experience.

[0035] In some embodiments, the method further includes: Obtain the shared user image of the user with the permission to share, and determine the matching degree between the shared user image and each pre-stored user image; In response to at least one of the matching degrees being greater than or equal to a preset matching degree, the voiceprint information of the sharing user is determined based on the permission sharing instruction; In response to the sharing user's voiceprint information matching at least one pre-stored voiceprint information, the user sharing the permission is determined to be a valid user.

[0036] Specifically, the first step is to obtain the sharing user image of the user who has the permission to share, which includes at least the facial image of the user who has the permission to share, so as to perform preliminary identity verification of the user who has the permission to share based on the user sharing image.

[0037] After determining the sharing user image, the matching degree between the sharing user image and each pre-stored user image is determined. The pre-stored user images are user images of registered or authenticated legitimate users that are pre-stored in the corresponding storage space of the vehicle system.

[0038] The matching degree between the shared user image and each pre-stored user image is the similarity between the two, which is used to characterize the similarity between the user sharing the permission and the user corresponding to the pre-stored user image. Therefore, it can be determined whether the user sharing the permission and the user corresponding to the pre-stored user image are the same user based on whether the matching degree is greater than or equal to the preset matching degree.

[0039] The preset matching degree is determined based on historical testing experience or is a preset minimum value where the user sharing the permissions and the user corresponding to the pre-stored user image are the same user. For example, the preset matching degree can be 90% or 95%, etc.

[0040] When at least one of the matching degrees is greater than or equal to the preset matching degree, it indicates that, based on image authentication, it is preliminarily determined that the user sharing the permission and the user corresponding to the pre-stored user image are the same user. In other words, it is preliminarily determined that the user sharing the permission is a legitimate user who has been registered or authenticated.

[0041] Then, in actual implementation, the accuracy of image-based authentication may not be strong enough due to factors such as light or environment. Therefore, the sharing user's voiceprint information is determined based on the permission sharing instruction. The sharing user's voiceprint information is used to characterize the voice features of the permission sharing user.

[0042] Then, the shared user's voiceprint information is compared with all pre-stored voiceprint information, which is the voiceprint information of registered or authenticated legitimate users that are pre-stored in the storage space corresponding to the vehicle system.

[0043] When it is determined that the voiceprint information of the sharing user is consistent with at least one pre-stored voiceprint information, it indicates that the voice characteristics of the user sharing the permission are the same as the voice characteristics of the user corresponding to the pre-stored voiceprint information. This further indicates that the voice characteristics of the user sharing the permission are the same as the voice characteristics of the user corresponding to the pre-stored voiceprint information, and they belong to the same user. Therefore, it is determined that the user sharing the permission is a legitimate user who has been registered or authenticated.

[0044] Thus, based on the preliminary determination that the user sharing the permissions is a registered or authenticated legitimate user based on the image information, the user sharing the permissions is further confirmed to be a registered or authenticated legitimate user through voiceprint information. Therefore, the user sharing the permissions is ultimately determined to be a valid user.

[0045] In this application, the dual verification of image information and voiceprint information is used to ultimately determine whether the user sharing the permission is a valid user, which improves the accuracy of determining the valid user. Subsequent operations are only carried out on the basis of accurately determining that the user sharing the permission is a valid user, thus ensuring the accuracy and security of the user's interaction with the vehicle system.

[0046] In some embodiments, determining the permission receiving user and permission information based on the permission sharing instruction includes: Based on the permission sharing instruction, instruction feature information is determined, and the instruction feature information includes multiple sub-information, each of which corresponds to an information category. In response to the information category including user category and permission category, the sub-information corresponding to the user category is determined as the permission receiving user, and the sub-information corresponding to the permission category is determined as permission information; Alternatively, in response to the information category not including user category and / or permission category, the permission receiving user and permission information are determined based on the instruction feature information.

[0047] Specifically, in the process of determining the user receiving the permission and permission information based on the permission sharing instruction, the instruction feature information is first determined based on the permission sharing instruction. The instruction feature information includes multiple sub-information, each of which corresponds to an information category. The information category is used to characterize the category corresponding to the sub-information. The information category may include user category and / or permission category. The permission category may include time category, function category and / or location category.

[0048] The user category refers to the user's name as the content corresponding to the sub-information. The time category refers to the time or time range as the content corresponding to the sub-information. The function category refers to the specific function content as the content corresponding to the sub-information. The location category refers to the specific location range or location area as the content corresponding to the sub-information.

[0049] For example, if the permission sharing instruction is "Share a temporary car key with Zhang, allowing Zhang to use the vehicle at the car wash from 10:00 AM to 12:00 PM", then the instruction feature information corresponding to the permission sharing instruction is "Zhang", "10:00 AM to 12:00 PM", and "car wash". The information category corresponding to the instruction feature information "Zhang" is "user category", the information category corresponding to the instruction feature information "10:00 AM to 12:00 PM" is "time category", and the information category corresponding to the instruction feature information "car wash" is "location category".

[0050] The information categories corresponding to the multiple sub-information components of the instruction feature information can characterize what content is included and what content is excluded from the instruction feature information. Therefore, based on different information categories, different methods are needed to determine the authorized users and permission information.

[0051] When the information category includes a user category and a permission category, it means that the information category includes both temporary user information (i.e., information of the temporary permission recipient) and the permission content corresponding to the temporary user. In this case, the information category is complete for sharing vehicle permissions, and the vehicle system can directly perform subsequent vehicle control based on the instruction feature information. Therefore, the sub-information corresponding to the user category is directly determined as the permission recipient user, and the sub-information corresponding to the permission category is determined as the permission information.

[0052] When the information category does not include user category and / or permission category, it means that the information category may not include temporary user information, or it may not include the permission content corresponding to the temporary user, or neither temporary user information nor the permission content corresponding to the temporary user is included. In this case, the information category is incomplete for sharing vehicle permissions, and the vehicle system cannot directly perform subsequent vehicle control based on the instruction feature information (for example, it does not know which temporary user should be allowed to control the vehicle, or it does not know where the temporary user's control permissions are). Therefore, it is necessary to continue to determine the permission receiving user and permission information based on the instruction feature information in order to finally determine the accurate permission receiving user and permission information, so as to ensure the accuracy and security of vehicle permission control.

[0053] In this application, different methods are used to determine the authorized users and their authorization information based on different information categories, ensuring the accuracy of the determined authorized users and their authorization information, thereby ensuring the accuracy and security of vehicle authorization control.

[0054] In some embodiments, determining the permission-receiving user and permission information based on the instruction feature information includes: In response to the fact that the information category does not include user category and permission category, a user permission request is sent to the permission sharing user; in response to receiving user permission feedback information, the user information in the user permission feedback information is identified as the permission receiving user, and the permission feedback information in the user permission feedback information is identified as permission information. Alternatively, in response to the information category not including a user category but including a permission category, a user information request is sent to the permission sharing user; in response to receiving user feedback information, the user feedback information is identified as the permission receiving user, and the sub-information corresponding to the permission category is identified as permission information; Alternatively, in response to the information category including a user category but not a permission category, a permission information request is sent to the permission sharing user; in response to receiving permission feedback information, the permission feedback information is determined as permission information, and the sub-information corresponding to the user category is determined as the permission receiving user.

[0055] Specifically, when the information category does not include user category and permission category, it means that the instruction feature information does not include temporary user information or the permission content corresponding to the temporary permission user. In this case, it is necessary to further confirm the temporary user information and its corresponding permission content with the permission sharing user.

[0056] Therefore, a user permission request is sent to the permission-sharing user. In response to receiving the user permission feedback information sent by the permission-sharing user, the user information in the user permission feedback information is identified as the permission receiving user, and the permission feedback information in the user permission feedback information is identified as the permission information.

[0057] The vehicle's infotainment system can directly send user permission requests to the permission-sharing user via voice. After receiving the user permission request, the permission-sharing user can directly send user permission feedback information to the vehicle's infotainment system via voice. In this way, user permission feedback information can be obtained through direct voice interaction between the vehicle's infotainment system and the user, without the need for the user to set up or operate step by step on a mobile device, thus improving the user's convenience.

[0058] In practice, the instruction feature information is "share temporary key permission". At this time, the information category of the sub-information corresponding to the instruction feature information does not include either the user category or the permission category. Therefore, the vehicle system cannot perform subsequent operations based on this instruction feature information. It is necessary to further confirm the temporary user information and its corresponding permission content with the permission sharing user.

[0059] Therefore, when sending a user permission request to the permission-sharing user, "Please confirm the temporary user information and temporary usage permission content," and receiving the user permission feedback information from the permission-sharing user, "Share temporary key permissions with Zhang, the permission content is to use at the car wash from 9:00 AM to 11:00 AM," then the user information "Zhang" in the user permission feedback information is identified as the permission receiving user, and the permission feedback information "9:00 AM to 11:00 AM, car wash" is identified as the permission information.

[0060] When the information category does not include the user category but includes the permission category, it means that the instruction feature information does not include temporary user information, but includes the permission content corresponding to the temporary permission user. In this case, it is necessary to further confirm the temporary user information with the permission sharing user.

[0061] Therefore, a user information request is sent to the user who shares the permission. In response to receiving user feedback information sent by the user who shares the permission, the user feedback information is identified as the user who receives the permission, and the sub-information corresponding to the permission category is identified as the permission information.

[0062] The in-vehicle infotainment system can directly send user information requests to users who share permissions via voice. After receiving the user information request, the user who shares permissions can directly send user feedback information to the in-vehicle infotainment system via voice. In this way, user feedback information can be obtained through direct voice interaction between the in-vehicle infotainment system and the user, without the need for users to set up or operate step by step on their mobile devices, thus improving the convenience of use.

[0063] In practice, the instruction feature information is "share temporary key access at a car wash from 9:00 AM to 10:00 AM". At this time, the information category of the sub-information corresponding to the instruction feature information does not include the user category, but it does not include the permission category, namely the time category (i.e., the information category corresponding to 9:00 AM to 10:00 AM) and the location category (i.e., the information category corresponding to the car wash). At this time, the vehicle system cannot perform subsequent operations based on this instruction feature information, and does not know which temporary user should be allowed to control the vehicle. Therefore, it is necessary to further confirm the temporary user information with the user who shares the permission.

[0064] Therefore, when sending a user information request "Please confirm temporary user information" to the permission-sharing user, and receiving the user feedback information "Share temporary key permissions with Zhang" from the permission-sharing user, then the user feedback information "Zhang" is identified as the permission receiving user, and the sub-information "Car wash shop from 9:00 AM to 10:00 AM" corresponding to the permission category is identified as the permission information.

[0065] When the response indicates that the information category includes a user category but not a permission category, it means that the instruction feature information includes temporary user information but does not include the permission content corresponding to the temporary permission user. In this case, it is necessary to further confirm the permission content corresponding to the temporary user with the permission sharing user.

[0066] Therefore, a permission information request is sent to the permission-sharing user; in response to receiving permission feedback information, the permission feedback information is identified as permission information, and the sub-information corresponding to the user category is identified as the permission-receiving user.

[0067] The vehicle's infotainment system can directly send permission requests to users who share permissions via voice. Once the user receives the permission request, they can send permission feedback information back to the infotainment system via voice. In this way, permission feedback information can be obtained through direct voice interaction between the infotainment system and the user, without requiring the user to set up or operate the system step by step on their mobile device, thus improving user convenience.

[0068] In practice, the instruction feature information is "share temporary key permissions with Zhang". At this time, the information category of the sub-information corresponding to the instruction feature information includes the user category (i.e., the information category corresponding to Zhang), but does not include the permission category. At this time, the vehicle system cannot perform subsequent operations based on the instruction feature information and does not know when and where the temporary user should be allowed to control the vehicle. Therefore, it is necessary to further confirm the permission content corresponding to the temporary user with the permission sharing user.

[0069] Therefore, a permission information request "Please confirm the temporary user's permission scope" is sent to the permission sharing user. When the permission feedback information "Allowed to use at the car wash from 9:00 to 10:00 AM" is received from the permission sharing user, then the permission feedback information "9:00 to 10:00 AM, car wash" is identified as permission information, and the sub-information corresponding to the user category is identified as the permission receiving user.

[0070] In this application, different requests are sent to users who share permissions based on different information categories. Based on the different feedback information received from the users who share permissions, the accuracy of different permission receiving users and permission information can be determined. This ensures that the determined permission receiving users and permission information are accurate and meet the actual needs of users, thereby ensuring the accuracy and security of vehicle permission control.

[0071] In some embodiments, authenticating the user receiving the permission and obtaining the authentication result includes: Send an authentication request to the user with the specified permissions; In response to receiving identity authentication feedback information, and the identity authentication feedback information is consistent with the identity information of the authorized user, a first liveness verification instruction is sent to the authorized receiving user; In response to receiving the first liveness verification information, and the first liveness verification information matching the first liveness verification instruction, the verification result is determined to be successful.

[0072] Specifically, in the process of verifying the identity of the user receiving the authorization and obtaining the verification result, an authentication request is first sent to the user receiving the authorization. In response to receiving authentication feedback information from the user receiving the authorization, it is determined whether the authentication feedback information matches the identity information of the authorized user.

[0073] When the identity authentication feedback information is consistent with the identity information of the authorized user, it indicates that the identity of the user receiving the authorization is consistent with the identity information of the temporary user to whom the user sharing the authorization wants to share the authorization. Therefore, it is preliminarily determined that the user receiving the authorization and the temporary user to whom the user sharing the authorization wants to share the authorization are the same person.

[0074] The authentication feedback information is of the same type as the authorized user's identity information. For example, when the authorized user's identity information is an ID card number, the authentication feedback information is also an ID card number; when the authorized user's identity information is a mobile phone number, the authentication feedback information is also a mobile phone number.

[0075] Then, in order to prevent others from stealing or impersonating the temporary user's identity information and trying to gain control of the vehicle, it is necessary to further verify whether the user receiving the authorization is the real person.

[0076] Therefore, a first liveness verification instruction is sent to the authorized user, which may include, but is not limited to, one or more combinations of commands such as shaking head, nodding head, opening mouth, and blinking.

[0077] When the first liveness verification information sent by the authorized user is received, and the first liveness verification information matches the first liveness verification instruction, the verification result is determined to be successful.

[0078] The matching of the first liveness verification information with the first liveness verification instruction means that the first liveness verification information is the current person information after the authorized user executes the first liveness verification instruction.

[0079] For example, if the first liveness verification instruction is a nod, and the first liveness verification information is the current person information after the authorized user performs the nod operation, then it is determined that the first liveness verification information matches the first liveness verification instruction, and the verification result is determined to be successful.

[0080] For example, if the first liveness verification instruction is a nod, and the first liveness verification information is the current person information after the authorized user performs a head shake or the current person information after not performing any operation, then it is determined that the first liveness verification information does not match the first liveness verification instruction, and the verification result is determined to be verification failure.

[0081] In this application, by performing dual verification of the identity information and liveness of the user receiving the permission, it can be ensured that the user receiving the permission and the temporary user to whom the permission sharing user wants to share the permission are the same person and that this person is a person who can move, thereby ensuring the accuracy and security of vehicle permission sharing.

[0082] In some embodiments, sending a command to the permission-receiving user to control the vehicle further includes: In response to receiving the key signal from the digital key and the distance between the digital key and the vehicle being less than or equal to a preset distance, user image information of the user carrying the digital key is collected. In response to the user image information and the received user image information conforming to a preset control command, the vehicle is controlled based on the digital key and the permission information.

[0083] Specifically, after sending a command to the permission-receiving user to allow control of the vehicle, the permission-receiving user now has the authority to control the vehicle within the scope of the permission information.

[0084] When the vehicle's infotainment system receives the key signal from the digital key and the distance between the digital key and the vehicle is less than or equal to a preset distance, it indicates that a user carrying the digital key is approaching the vehicle. At this point, the infotainment system needs to confirm whether the user carrying the digital key has the authority to control the vehicle.

[0085] The digital key described in this application is a digital key that has not been registered and connected to the vehicle's infotainment system in advance, that is, a digital key that does not have the authority to control the vehicle. The digital key in this application does not include digital keys of valid users who have registered in advance, such as vehicle owners.

[0086] The preset distance is the maximum distance at which the digital key can control the vehicle. When the distance between the digital key and the vehicle is less than or equal to the preset distance, it means that the digital key can control the vehicle from a distance perspective. For example, the preset distance can be 2m or 3m.

[0087] Therefore, user image information of users carrying digital keys is collected. The user image information can be user image information or user video information.

[0088] When the user image information and the received user image information match the preset control command, it is determined that the user carrying the digital key is the authorized receiving user. At this time, it is determined that the user carrying the digital key is a person with temporary control authority, and therefore the vehicle is controlled based on the digital key and the authorization information.

[0089] The preset control command is a preset condition that the user image information must meet when the user corresponding to the user image information controls the vehicle.

[0090] In this application, when the vehicle system receives the key signal from the digital key, it needs to determine whether the digital key is an authorized digital key that has the authority to control the vehicle. Only when the user image information of the user carrying the digital key matches the preset control command can the user carrying the digital key be determined to be a user with the right to use it. Only then can the vehicle be controlled based on the digital key and the permission information, ensuring that the vehicle can only be controlled by the user with the right to control it and the digital key they carry, thereby ensuring the accuracy and security of vehicle control.

[0091] In some embodiments, the method further includes: In response to the similarity between the user image information and the received user image information being greater than or equal to a preset similarity, a second liveness verification command is sent to the user carrying the digital key; In response to receiving second liveness verification information, and the second liveness verification information matching the second liveness verification instruction, it is determined that the user image information and the received user image information conform to a preset control instruction; Alternatively, in response to the absence of second liveness verification information or the mismatch between the second liveness verification information and the second liveness verification instruction, it is determined that the user image information and the received user image information do not conform to the preset control instruction.

[0092] Specifically, the similarity between the user image information and the received user image information is first determined.

[0093] When both the user image information and the received user image information are video information, each frame of image information in the user image information is extracted, and each frame of image information in the received user image information is also extracted. Then, the initial similarity between each frame of image information in the user image information and each frame of image information in the received user image information is compared sequentially, and the average value of the initial similarity is determined as the similarity between the user image information and the received user image information.

[0094] When both the user image information and the received user image information are image information, the similarity between these two image information is directly determined as the similarity between the user image information and the received user image information.

[0095] The similarity of image information can be determined using existing, publicly available, conventional methods, which will not be elaborated upon here.

[0096] After determining the similarity between the user image information and the received user image information, it is determined whether the similarity score is greater than or equal to a preset similarity score. The preset similarity score is a preset minimum similarity score for determining that the people in the two video information or image information are the same person. For example, the preset similarity score can be 90% or 95%.

[0097] When it is determined that the similarity between the user image information and the received user image information is greater than or equal to a preset similarity, it is determined that the user carrying the digital key corresponding to the user image information and the authorized receiving user corresponding to the received user image information are the same person.

[0098] Then, in order to prevent the theft or misuse of user image information in order to gain control of the vehicle, it is necessary to further confirm that the user carrying the digital key is the authorized user who can act.

[0099] Therefore, a second liveness verification command is sent to the user carrying the digital key. The second liveness verification command may include, but is not limited to, one or more combinations of commands such as shaking the head, nodding, opening the mouth, and blinking.

[0100] When the second liveness verification information is received and the second liveness verification information matches the second liveness verification instruction, it is determined that the user image information and the received user image information conform to the preset control instruction. At this time, it is determined that the user carrying the digital key corresponding to the user image information and the authorized receiving user corresponding to the received user image information are the same person and that this person is active. Therefore, it is finally determined that the user carrying the digital key is the authorized receiving user himself and has vehicle control authority.

[0101] If no second liveness verification information is received or the second liveness verification information does not match the second liveness verification command, it is determined that the user image information and the received user image information do not conform to the preset control command. At this time, it is determined that the user carrying the digital key is not the authorized user who can move around. Therefore, it is determined that the user image information and the received user image information do not conform to the preset control command, and the user carrying the digital key does not have vehicle control authority.

[0102] In this application, the similarity between the user's image information and the received user's image information, as well as the dual verification of the second liveness verification command, are used to determine whether the user carrying the digital key is the authorized user who can actually receive the information, thereby determining whether he or she has the authority to control the vehicle, thus improving the accuracy and security of vehicle access control.

[0103] In some embodiments, controlling the vehicle based on the digital key and the authorization information further includes: Obtain current time information and real-time vehicle location information; In response to the current time information not being within the authorized time range, and / or the real-time location information not being within the authorized location range, a permission verification request is sent to the permission-sharing user; In response to receiving an authorization command within a preset time period, the vehicle is controlled based on the digital key; Alternatively, in response to the absence of an authorization permission command or the receipt of a prohibition command within a preset time period, the control of the vehicle by the digital key may be prohibited.

[0104] Specifically, after controlling the vehicle based on the digital key and the permission information, it is also necessary to monitor the vehicle's usage permissions in real time. Therefore, by obtaining the current time information and the vehicle's real-time location information, if the current time information is not within the permitted time range, and / or the real-time location information is not within the permitted location range, it indicates that the time for controlling the vehicle has exceeded the range corresponding to the permission information determined by the permission-sharing user, and / or the vehicle's location has exceeded the range corresponding to the permission information determined by the permission-sharing user. In this case, it is necessary to send a permission verification request to the permission-sharing user to verify whether the permission-receiving user and their digital key are still allowed to control the vehicle.

[0105] When the vehicle system receives a permission permission instruction within a preset time period, it indicates that the permission sharing user has granted permission to the permission receiving user and their digital key to continue controlling the vehicle. At this time, the vehicle can continue to be controlled based on the digital key.

[0106] If no permission permission instruction is received or a permission denial instruction is received within a preset time period, it means that the permission sharing user does not allow the permission receiving user and its digital key to continue controlling the vehicle, and the digital key is prohibited from controlling the vehicle.

[0107] The preset time period is the maximum time for a user to send instructions while the vehicle-mounted system receives permissions. For example, the preset time period can be 1 minute or 30 seconds, etc.

[0108] See Figure 3 The vehicle access control method provided in this application may also include the following specific steps: (a) Initialization settings (1) Owner identity binding: When using it for the first time, the owner needs to complete account registration and real-name authentication through the mobile application. The owner's facial features and voiceprint samples are collected in the car to establish a biometric database and set the owner's permission level and the scope of sharing permissions.

[0109] (2) System calibration: Adjust the angle of the in-vehicle camera to ensure the best acquisition effect; calibrate the microphone array to adapt to the acoustic environment inside the vehicle; test the positioning accuracy of communication modules such as UWB / Star Flash.

[0110] (II) Temporary Permission Sharing Procedure: (1) Trigger the sharing function The car owner can trigger the sharing function through natural voice commands, such as "I want to share a temporary car key with Zhang San." The system automatically initiates dual verification: facial recognition + voiceprint recognition, to confirm that the person issuing the command is the car owner.

[0111] (2) Recipient information entry The voice prompts the car owner to provide the recipient's information: "Please state the recipient's name", "Please state the recipient's mobile phone number", "Please describe the recipient's physical characteristics (optional)".

[0112] The system provides real-time voice feedback to confirm the accuracy of the information.

[0113] (3) Permission parameter settings Voice permission settings: "Please set the validity period, such as 2 hours", "Please set the scope of operable functions, such as only unlocking and starting", "Whether to set a geofence, such as only for use within the city".

[0114] The system provides default suggestions, which car owners can confirm or modify via voice.

[0115] (4) Face capture and binding The system guides the receiver to face the camera: "Please have the receiver face the camera in front of the driver's seat," and "Please have the receiver complete liveness detection actions such as blinking and turning their head."

[0116] The system collects and receives facial features, associates them with mobile phone numbers, and provides real-time feedback on the collection results and quality assessment.

[0117] (5) Permission confirmation and activation Voice confirmation of all settings: "Confirm sharing the temporary car key with Zhang San (phone number 138)." (1234), valid for 2 hours, permissions include unlocking and starting, confirm?

[0118] After the vehicle owner confirms, the system generates a temporary digital key and it automatically takes effect. The recipient will be notified via SMS / APP that the permission has been activated.

[0119] (6) Recipient's usage process First-time use verification: When the recipient approaches the vehicle, the system detects the distance using UWB / Starflash technology. Once within 3 meters, the system initiates facial recognition verification, and the recipient must complete identity confirmation through liveness detection (blinking, head turning, etc.).

[0120] Permission usage: Upon successful identification, the system automatically unlocks the vehicle and enters "guest mode." The recipient can control the vehicle via voice commands, but this is limited to authorized areas. The system monitors usage in real time to ensure it does not exceed the authorized scope.

[0121] Session Management: During use, the system performs facial recognition verification periodically. If abnormal behavior is detected (such as a vehicle leaving the geofence), secondary verification is automatically triggered. When permissions are about to expire, the system will provide an advance voice reminder.

[0122] Typical application scenarios that can be applied include: Vehicle maintenance scenario: The car owner can share temporary access with the 4S store service personnel through voice commands from inside the car, and set a precise time window (such as "9 am to 11 am"). The access will automatically expire after the service is completed, and the car owner does not need to be present.

[0123] In the scenario of borrowing a car from relatives and friends: when the car owner introduces the car to relatives and friends, the permission can be shared directly inside the car, with reasonable validity period and function scope set, and the vehicle usage can be monitored throughout the process to ensure safety.

[0124] In the shared mobility scenario: strict time and function restrictions are set for valet parking attendants, temporary driving permissions are provided to car rental users, and cargo compartment access is provided to logistics and delivery personnel.

[0125] This application also includes security control logic, specifically including access control mechanisms, real-time monitoring mechanisms, and emergency response mechanisms.

[0126] Access control mechanisms include: Guest mode: Hides the car owner's personal data and settings; Functionality limitations: Only functions within the authorized scope are enabled; Data isolation: Temporary user operation data is stored separately from vehicle owner data.

[0127] Real-time monitoring mechanisms include: Behavioral analysis: Monitoring abnormal driving behavior; Geofencing: Monitors whether a vehicle's location exceeds the authorized area; Permission usage audit: Record all temporary permission operations.

[0128] Emergency response mechanism: Remote termination: Vehicle owners can terminate temporary permissions at any time via a mobile application.

[0129] Automatic termination: Automatically terminate permissions when abnormal behavior is detected.

[0130] Fault recovery: The system automatically recovers to a safe state when a fault occurs.

[0131] Authentication logic: Dual verification: simultaneously verifying both voice and facial features; Liveness detection: Combining physiological indicators such as micro-expressions and heart rate to determine whether it is a real living body; Consistency check: Compare the content of the voice command with the biometric recognition results.

[0132] In this application, the method for controlling vehicle permissions greatly improves the convenience of vehicle permission control. Permission sharing can be completed in real time without the vehicle owner leaving the vehicle. No mobile application needs to be operated. The entire process is controlled by voice and automatically establishes the association between face and account, simplifying subsequent use.

[0133] Security is greatly enhanced by employing dual biometric verification, which is more secure than single verification. Precise positioning technology prevents relay attacks, and fine-grained access control avoids over-authorization.

[0134] User experience optimization includes natural voice interaction to lower the barrier to entry; intelligent guidance processes to reduce operational errors; and a real-time feedback mechanism to increase operational confidence.

[0135] It should be noted that the method in this embodiment can be executed by a single device, such as a computer or server. The method can also be applied in a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method in this embodiment, and the multiple devices will interact with each other to complete the method described.

[0136] It should be noted that some embodiments of this application have been described above. In some cases, the actions or steps described in the above embodiments can be performed in a different order than that shown in the above embodiments and the desired result can still be achieved. In addition, the processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0137] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a vehicle access control device.

[0138] refer to Figure 3 The vehicle access control device includes: The determination module 100 is configured to, in response to receiving a permission sharing instruction sent by a permission sharing user and determining that the permission sharing user is a valid user, determine the permission receiving user and permission information based on the permission sharing instruction; The verification module 200 is configured to obtain the receiving user image information of the authorized receiving user, and to verify the identity of the authorized receiving user to obtain the verification result; The execution module 300 is configured to, in response to the verification result being verified as passed, associate and store the received user image information and the permission information, and send a command to the permission-receiving user to allow control of the vehicle.

[0139] In some embodiments, the determining module 100 is further configured to: Obtain the shared user image of the user with the permission to share, and determine the matching degree between the shared user image and each pre-stored user image; In response to at least one of the matching degrees being greater than or equal to a preset matching degree, the voiceprint information of the sharing user is determined based on the permission sharing instruction; In response to the sharing user's voiceprint information matching at least one pre-stored voiceprint information, the user sharing the permission is determined to be a valid user.

[0140] In some embodiments, the determining module 100 is further configured to: Based on the permission sharing instruction, instruction feature information is determined, and the instruction feature information includes multiple sub-information, each of which corresponds to an information category. In response to the information category including user category and permission category, the sub-information corresponding to the user category is determined as the permission receiving user, and the sub-information corresponding to the permission category is determined as permission information; Alternatively, in response to the information category not including user category and / or permission category, the permission receiving user and permission information are determined based on the instruction feature information.

[0141] In some embodiments, the determining module 100 is further configured to: In response to the fact that the information category does not include user category and permission category, a user permission request is sent to the permission sharing user; in response to receiving user permission feedback information, the user information in the user permission feedback information is identified as the permission receiving user, and the permission feedback information in the user permission feedback information is identified as permission information. Alternatively, in response to the information category not including a user category but including a permission category, a user information request is sent to the permission sharing user; in response to receiving user feedback information, the user feedback information is identified as the permission receiving user, and the sub-information corresponding to the permission category is identified as permission information; Alternatively, in response to the information category including a user category but not a permission category, a permission information request is sent to the permission sharing user; in response to receiving permission feedback information, the permission feedback information is determined as permission information, and the sub-information corresponding to the user category is determined as the permission receiving user.

[0142] In some embodiments, the permission information includes the identity information of the authorized user.

[0143] In some embodiments, the verification module 200 is further configured to: Send an authentication request to the user with the specified permissions; In response to receiving identity authentication feedback information, and the identity authentication feedback information is consistent with the identity information of the authorized user, a first liveness verification instruction is sent to the authorized receiving user; In response to receiving the first liveness verification information, and the first liveness verification information matching the first liveness verification instruction, the verification result is determined to be successful.

[0144] In some embodiments, the execution module 300 is further configured to: In response to receiving the key signal from the digital key and the distance between the digital key and the vehicle being less than or equal to a preset distance, user image information of the user carrying the digital key is collected. In response to the user image information and the received user image information conforming to a preset control command, the vehicle is controlled based on the digital key and the permission information.

[0145] In some embodiments, the execution module 300 is further configured to: In response to the similarity between the user image information and the received user image information being greater than or equal to a preset similarity, a second liveness verification command is sent to the user carrying the digital key; In response to receiving second liveness verification information, and the second liveness verification information matching the second liveness verification instruction, it is determined that the user image information and the received user image information conform to a preset control instruction; Alternatively, in response to the absence of second liveness verification information or the mismatch between the second liveness verification information and the second liveness verification instruction, it is determined that the user image information and the received user image information do not conform to the preset control instruction.

[0146] In some embodiments, the permission information includes a permission time range and a permission location range.

[0147] In some embodiments, the execution module 300 is further configured to: Obtain current time information and real-time vehicle location information; In response to the current time information not being within the authorized time range, and / or the real-time location information not being within the authorized location range, a permission verification request is sent to the permission-sharing user; In response to receiving an authorization command within a preset time period, the vehicle is controlled based on the digital key; Alternatively, in response to the absence of an authorization permission command or the receipt of a prohibition command within a preset time period, the control of the vehicle by the digital key may be prohibited.

[0148] The apparatus described above is used to implement the corresponding vehicle access control method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0149] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle access control method described in any of the above embodiments.

[0150] Figure 4 This embodiment illustrates a more specific hardware structure of an electronic device. 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, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0151] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, 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.

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

[0153] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0154] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0155] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0156] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0157] The electronic devices described above are used to implement the corresponding vehicle access control methods in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0158] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a non-transitory computer-readable storage medium that stores computer instructions for causing the computer to execute the vehicle access control method as described in any of the above embodiments.

[0159] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, 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, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

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

[0161] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a computer program product, including computer program instructions. When the computer program instructions are run on a computer, the computer executes the vehicle access control method as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0162] Based on the same inventive concept, and corresponding to the methods of any of the above embodiments, this application also provides a vehicle, which includes the vehicle access control device, electronic device, computer-readable storage medium, or computer program product described in any of the above embodiments. The vehicle possesses the technical effects corresponding to any of the above embodiments, which will not be elaborated further here.

[0163] It is understood that before using the technical solutions of the various embodiments in this application, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.

[0164] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations described in this application.

[0165] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0166] It is understood that the above notification and user authorization process are merely illustrative and do not limit the implementation of this application. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this application.

[0167] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application is limited to these examples; under the concept of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in detail for the sake of brevity.

[0168] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of the implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

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

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

Claims

1. A method for controlling vehicle access, characterized in that, include: In response to receiving a permission sharing instruction sent by a permission sharing user and determining that the permission sharing user is a valid user, the permission receiving user and permission information are determined based on the permission sharing instruction; Obtain the image information of the user receiving the permission, verify the identity of the user receiving the permission, and obtain the verification result; In response to the verification result being successful, the received user image information and the permission information are associated and stored, and a command to allow vehicle control is sent to the user with the permission.

2. The method according to claim 1, characterized in that, The method further includes: Obtain the shared user image of the user with the permission to share, and determine the matching degree between the shared user image and each pre-stored user image; In response to at least one of the matching degrees being greater than or equal to a preset matching degree, the voiceprint information of the sharing user is determined based on the permission sharing instruction; In response to the sharing user's voiceprint information matching at least one pre-stored voiceprint information, the user sharing the permission is determined to be a valid user.

3. The method according to claim 1, characterized in that, The step of determining the permission-receiving user and permission information based on the permission sharing instruction includes: Based on the permission sharing instruction, instruction feature information is determined, and the instruction feature information includes multiple sub-information, each of which corresponds to an information category. In response to the information category including user category and permission category, the sub-information corresponding to the user category is determined as the permission receiving user, and the sub-information corresponding to the permission category is determined as permission information; Alternatively, in response to the information category not including user category and / or permission category, the permission receiving user and permission information are determined based on the instruction feature information.

4. The method according to claim 3, characterized in that, The step of determining the authorized user and authorization information based on the instruction feature information includes: In response to the fact that the information category does not include user category and permission category, a user permission request is sent to the permission sharing user; in response to receiving user permission feedback information, the user information in the user permission feedback information is identified as the permission receiving user, and the permission feedback information in the user permission feedback information is identified as permission information. Alternatively, in response to the information category not including a user category but including a permission category, a user information request is sent to the permission sharing user; in response to receiving user feedback information, the user feedback information is identified as the permission receiving user, and the sub-information corresponding to the permission category is identified as permission information; Alternatively, in response to the information category including a user category but not a permission category, a permission information request is sent to the permission sharing user; in response to receiving permission feedback information, the permission feedback information is determined as permission information, and the sub-information corresponding to the user category is determined as the permission receiving user.

5. The method according to claim 1, characterized in that, The permission information includes the identity information of the authorized user; The step of authenticating the user who receives the permission and obtaining the authentication result includes: Send an authentication request to the user with the specified permissions; In response to receiving identity authentication feedback information, and the identity authentication feedback information is consistent with the identity information of the authorized user, a first liveness verification instruction is sent to the authorized receiving user; In response to receiving the first liveness verification information, and the first liveness verification information matching the first liveness verification instruction, the verification result is determined to be successful.

6. The method according to claim 1, characterized in that, The step of sending a command to the user who has permission to control the vehicle further includes: In response to receiving the key signal from the digital key and the distance between the digital key and the vehicle being less than or equal to a preset distance, user image information of the user carrying the digital key is collected. In response to the user image information and the received user image information conforming to a preset control command, the vehicle is controlled based on the digital key and the permission information.

7. The method according to claim 6, characterized in that, The method further includes: In response to the similarity between the user image information and the received user image information being greater than or equal to a preset similarity, a second liveness verification command is sent to the user carrying the digital key; In response to receiving second liveness verification information, and the second liveness verification information matching the second liveness verification instruction, it is determined that the user image information and the received user image information conform to a preset control instruction; Alternatively, in response to the absence of second liveness verification information or the mismatch between the second liveness verification information and the second liveness verification instruction, it is determined that the user image information and the received user image information do not conform to the preset control instruction.

8. The method according to claim 6, characterized in that, The permission information includes the permission time range and the permission location range; The process of controlling the vehicle based on the digital key and the authorization information further includes: Obtain current time information and real-time vehicle location information; In response to the current time information not being within the authorized time range, and / or the real-time location information not being within the authorized location range, a permission verification request is sent to the permission-sharing user; In response to receiving an authorization command within a preset time period, the vehicle is controlled based on the digital key; Alternatively, in response to the absence of an authorization permission command or the receipt of a prohibition command within a preset time period, the control of the vehicle by the digital key may be prohibited.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 8.

10. A vehicle, characterized in that, Includes the electronic device as described in claim 9.

Images