Method and apparatus for controlling permissions, vehicle and electronic device

Abstract

The application provides a permission control method and device, a vehicle and electronic equipment. The method comprises the following steps: receiving a target request of a target terminal and corresponding identity authentication information; the target request is used for requesting a vehicle-mounted camera of a target vehicle to perform a target action, and the identity authentication information is obtained by performing identity authentication on a first account logged in the target terminal; and whether the target terminal is allowed to perform the target action is determined according to a target permission corresponding to the identity authentication information. Therefore, only the target terminal that is authorized can perform the target action that is adapted to the target request, the access and operation of the target terminal that is not authorized are effectively prevented, and the safety of the vehicle and the privacy protection of the user are improved.

Description

Technical Field

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

[0002] With the rapid development of vehicle-to-everything (V2X) technology and smart devices, modern vehicles not only possess traditional transportation functions but also integrate advanced intelligent features such as remote monitoring, real-time video streaming, and vehicle status management. These functions allow users to interact with their vehicles through terminal devices (such as mobile apps), enabling them to view and modify vehicle-related data. However, unauthorized access to or modification of vehicle data can lead to serious security and privacy risks, such as data leaks or tampering. Therefore, implementing strict access control mechanisms to ensure that only authorized users can perform these sensitive operations is crucial for protecting system security and user privacy. This mechanism not only prevents potential security threats but also enhances user trust and overall experience. Summary of the Invention

[0003] This application aims to address, to a certain extent, one of the technical problems in the related art.

[0004] To this end, this application proposes an access control method, device, vehicle, and electronic device to ensure that only authorized target terminals can execute target actions adapted to target requests, effectively preventing unauthorized access and operation, and improving vehicle security and user privacy protection.

[0005] One embodiment of this application proposes an access control method, including:

[0006] Receive a target request from the target terminal and corresponding authentication information; wherein, the target request is used to request the vehicle-mounted camera device of the target vehicle to perform a target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal;

[0007] Based on the target permissions corresponding to the authentication information, determine whether to allow the target terminal to execute the target action.

[0008] Another embodiment of this application proposes an alternative access control method, including:

[0009] Send the target request.

[0010] Another aspect of this application provides an access control device, comprising:

[0011] The receiving module is used to receive a target request from a target terminal and corresponding authentication information; wherein, the target request is used to request the vehicle-mounted camera device of the target vehicle to perform a target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal;

[0012] The determination module is used to determine whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information.

[0013] Another embodiment of this application provides an access control device, comprising:

[0014] The sending module is used to send target requests.

[0015] In another aspect, this application provides a vehicle including: a processor and a memory communicatively connected to the processor;

[0016] The memory stores computer-executed instructions;

[0017] The processor executes computer execution instructions stored in the memory to implement the method described in one aspect of this application.

[0018] In another aspect, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0019] The memory stores computer-executed instructions;

[0020] The processor executes computer execution instructions stored in the memory to implement the method described in another embodiment of this application.

[0021] The access control method, device, vehicle, and electronic device proposed in this application receive the target request from the target terminal and its corresponding authentication information, and determine whether to allow the target terminal to perform the target action based on the target permissions relative to the authentication information. This ensures that only authorized target terminals can perform the target action adapted to the target request, effectively preventing unauthorized access and operation by the target terminal, and improving vehicle security and user privacy protection.

[0022] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0023] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0024] Figure 1A flowchart illustrating an access control method provided in an embodiment of this application;

[0025] Figure 2 A flowchart illustrating another access control method provided in an embodiment of this application;

[0026] Figure 3 A flowchart illustrating another access control method provided in an embodiment of this application;

[0027] Figure 4 A flowchart illustrating another access control method provided in an embodiment of this application;

[0028] Figure 5 An interactive schematic diagram of an access control method provided in an embodiment of this application;

[0029] Figure 6 This is a schematic diagram of the structure of an access control device provided in an embodiment of this application;

[0030] Figure 7 This is a schematic diagram of another access control device provided in an embodiment of this application;

[0031] Figure 8 This is a block diagram illustrating a vehicle according to an exemplary embodiment;

[0032] Figure 9 A block diagram of an electronic device provided in an embodiment of this application;

[0033] Figure 10 This is a schematic diagram of the chip structure proposed in the embodiments of this application. Detailed Implementation

[0034] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0035] In related technologies, vehicle-mounted camera devices (also known as vehicle-mounted network camera devices (IP Cameras, or IPCs)) are mainly used in personal vehicles or single-user scenarios. Each user's configuration (e.g., viewing resolution, Artificial Intelligence (AI) functions) is managed using independent files. Both the main account and shared accounts have direct access to view real-time video and modify attributes. When multiple accounts modify attributes, the system determines the final attribute settings based on the order of modification time.

[0036] However, the in-vehicle IPC technology in related technologies has significant limitations in terms of storage architecture, access control, security, and real-time performance, as detailed below;

[0037] (1) Storage mechanism: Vehicle IPC is mainly designed for personal vehicles or single user scenarios. Its data storage and access permission mechanism fails to fully consider the sharing needs of multiple users, resulting in the repeated storage of the same attribute data among different users, which reduces storage efficiency.

[0038] (2) In terms of access control: the system adopts a broad management model of "all open or all closed" and lacks a fine-grained access control mechanism. However, this design cannot meet the personalized needs of different users, which reduces the flexibility of the system and increases the risk of data security.

[0039] (3) Security: Traditional vehicle IPC systems have serious security risks, such as the ability to access in-vehicle video data at will through simple account sharing, which cannot effectively protect the privacy and security of people in the vehicle;

[0040] (4) System real-time performance: When multiple users modify the vehicle IPC configuration at the same time, due to the lack of automated conflict detection and intelligent merging strategy, configuration overwriting or system errors are likely to occur, affecting the stability and reliability of the system.

[0041] To address the aforementioned issues, this application proposes an access control method, apparatus, vehicle, and electronic device.

[0042] The following description, with reference to the accompanying drawings, describes the access control method, apparatus, vehicle, and electronic device according to embodiments of this application.

[0043] Figure 1 This is a flowchart illustrating an access control method provided in an embodiment of this application.

[0044] It should be noted that the access control method of this application embodiment can be applied to an access control device. In some possible embodiments, the access control device can be configured in a vehicle (i.e., the target vehicle in this application) or a chip, so that the vehicle or chip can perform access control functions. Additionally, in some possible embodiments, the access control device can also be software within the vehicle.

[0045] In any embodiment of this application, the chip can be integrated into a vehicle. The chip includes a Central Processing Unit (CPU), Image Signal Processing (ISP), Application-Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), System on a Chip (SOC), Reduced Instruction Set Computer (RISC), etc., which will not be listed individually here. For ease of explanation, the vehicle will be used as the executor of this access control method in the following illustrative description.

[0046] The vehicles include, but are not limited to, hybrid vehicles, non-hybrid vehicles, electric vehicles, fuel cell vehicles, or other types of vehicles. The vehicles can be autonomous vehicles, semi-autonomous vehicles, or non-autonomous vehicles; this application does not impose any limitations on this.

[0047] like Figure 1 As shown, the access control method may include the following steps:

[0048] Step 101: Receive the target request from the target terminal and the corresponding authentication information.

[0049] The target request is used to request the vehicle-mounted camera device of the target vehicle to perform the target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal.

[0050] As one possible implementation, the target terminal sends a target request to the cloud. The cloud verifies the user identity based on the User ID (UID) in the target request, obtaining authentication information such as the user's identity category (primary driver, co-driver, or family member, etc.). Then, the cloud sends the target request and authentication information to the target vehicle. The target request is used to request the execution of a target action on the vehicle's in-vehicle camera device. The target request may include an audio / video access request or an attribute setting request. An audio / video access request is used to access the audio / video data of the target vehicle's in-vehicle camera device, while an attribute setting request is used to set attributes for the target vehicle's in-vehicle camera device.

[0051] Step 102: Determine whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information.

[0052] As one possible implementation, after the target vehicle receives the target request and authentication information sent from the cloud, it obtains the target permissions corresponding to the authentication information, and determines whether the target terminal has the ability to perform target actions that are compatible with the target request on the target vehicle based on the target permissions.

[0053] To enhance user experience, in this embodiment of the application, the target vehicle may send feedback information to the target terminal to indicate whether the target terminal is allowed to perform the target action, so that the user can know in a timely manner whether their operation is permitted.

[0054] In summary, by receiving the target terminal's target request and its corresponding authentication information, and determining whether to allow the target terminal to execute the target action based on the target permissions corresponding to the authentication information, this system ensures that only authorized target terminals can execute target actions adapted to the target request. This effectively prevents unauthorized access and operation by target terminals, thereby improving vehicle security and user privacy protection.

[0055] To clearly illustrate how the above embodiments determine whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information, this application proposes another permission control method.

[0056] Figure 2 This is a flowchart illustrating another access control method provided in an embodiment of this application.

[0057] like Figure 2 As shown, the access control method may include the following steps:

[0058] Step 201: Receive the target request from the target terminal and the corresponding authentication information.

[0059] The target request is used to request the vehicle-mounted camera device of the target vehicle to perform the target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal.

[0060] Step 202: If the target action includes accessing the audio and video data of the vehicle-mounted camera device, obtain the user operation based on the authentication information.

[0061] To prevent unauthorized access and data leakage, as one possible approach, after receiving a target request, the target vehicle determines the type of the target request. If the target action includes accessing audio and video data from the vehicle's camera device, the vehicle obtains the user's actions triggered based on authentication information.

[0062] As an example, authentication information is displayed on the authorization request page to obtain the user's (e.g., a person in the vehicle) actions on the first specified control on the authorization request page. For example, the first specified control is a confirmation control, which is clicked or touched.

[0063] As another example, obtain the user's action on a second specified control on the authorization request page; for example, if the second specified control is a cancel control, click or touch the second specified control.

[0064] In addition, it should be noted that if the user does not process the authorization request page for a long time (e.g., exceeding the set time threshold), a feedback message will be sent to the target terminal that the target terminal is not allowed to access audio and video.

[0065] Step 203: Based on the target permissions indicated by the user's operation, determine whether to allow the target terminal to access audio and video data.

[0066] To improve vehicle safety and protect user privacy, in this embodiment of the application, it is determined whether to allow the target terminal to access audio and video data based on the target permissions indicated by the user's operation.

[0067] As one possible implementation, if the user action is to click or touch the first specified control (e.g., a confirmation control) on the authorization request page, then the target permission indicated by the user action is authorized to access, thus allowing the target terminal to access the audio and video data. That is, if the user action indicates that the target terminal has authorized to access, then the target terminal is allowed to access the audio and video data.

[0068] As another possible implementation, if the user action is a click or touch of a second specified control (e.g., a cancel control) on the authorization request page, then the target permission indicated by the user action is no access, and the target terminal's access to audio and video data is denied; if the user action indicates no access, the target terminal's access to audio and video data is denied.

[0069] It should be noted that the execution process of step 201 can be implemented in any of the embodiments of this application. The embodiments of this application do not limit this, nor will they be described in detail.

[0070] In summary, by obtaining user actions based on authentication information and determining the target permissions indicated by the user actions, it is possible to determine whether to allow the target terminal to access audio and video data. This effectively prevents unauthorized access and data leakage, and enhances system security and user privacy protection.

[0071] To clearly illustrate how the above embodiments determine whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information, this application proposes a flowchart of another permission control method.

[0072] Figure 3 This is a flowchart illustrating another access control method provided in an embodiment of this application.

[0073] like Figure 3 As shown, the access control method may include the following steps:

[0074] Step 301: Receive the target request from the target terminal and the corresponding authentication information.

[0075] The target request is used to request the vehicle-mounted camera device of the target vehicle to perform the target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal.

[0076] Step 302: If the target action includes setting attributes for the vehicle-mounted camera device, and the attribute to be set is a public attribute, query the corresponding target permissions based on the authentication information, and determine whether the target terminal is allowed to set the public attribute based on whether the target permissions include the permission to set the public attribute.

[0077] As one possible implementation, after the target vehicle receives the target request, it determines the type of the target request. If the target request is for setting attributes of the vehicle-mounted camera device and the attribute to be set is a public attribute, that is, if the target action includes setting attributes of the vehicle-mounted camera device and the attribute to be set in the target request is a public attribute, it queries the target permissions corresponding to the authentication information based on the authentication information, and then determines whether to allow the target terminal to set the public attribute based on whether the target permissions have the permission to set public attributes.

[0078] As one possible implementation, if the target permissions include the permission to set public attributes, then the target terminal is allowed to set public attributes.

[0079] As an example, based on the authentication information, the local database of the vehicle-mounted camera device is queried to obtain a list of attributes that the first account logged into the target terminal is allowed to set. The permission level of each attribute in the attribute list is less than or equal to the permission level of the first account. Then, if the attribute to be set in the target request (such as resolution, encoding format, privacy area coordinates, or AI event notification, etc.) is in the attribute list, and the attribute to be set is a public attribute, it is determined that the first account has the permission to set the attribute to be set. That is, the target permissions include the permission to set public attributes, and the target terminal is allowed to set public attributes.

[0080] In order to enable users to understand the settings of public attributes in a timely manner, in this embodiment of the application, when the target terminal is allowed to set public attributes, the attributes are set according to the attribute information carried in the target request to obtain the setting result of the public attributes; and the setting result is sent to the target terminal.

[0081] As another possible implementation, if the target permissions do not include the permission to set public attributes, then the target terminal should be prohibited from setting public attributes.

[0082] In other words, if the attribute to be set is not in the attribute list, it is determined that the first account does not have permission to set the attribute to be set. That is, the target permissions do not include the permission to set public attributes, and the target terminal is prohibited from setting public attributes.

[0083] It should be noted that the attributes to be set include, for example, resolution, encoding format, privacy area coordinates, or AI event notifications; public attributes are those shared by the accounts bound to the target vehicle, such as resolution and encoding format.

[0084] To improve the management efficiency of public attributes, once public attributes are set, all accounts bound to the target vehicle will take effect simultaneously, eliminating the need to set public attributes for each account separately, thus saving time and effort.

[0085] Step 303: If the attribute to be set is a private attribute, allow the target terminal to set the private attribute.

[0086] Among them, the private attribute is the attribute that is private to the account bound to the target vehicle.

[0087] To meet the personalized settings needs of different users for in-vehicle camera devices, as another possible implementation, when the attribute to be set is a private attribute, the target terminal can be allowed to set private attributes. It should be noted that private attributes are attributes that are private to the account bound to the target vehicle; that is, private attributes are attributes that can only be set by an account bound to the target vehicle. For example, private attributes include: privacy zone coordinates, AI event notifications, etc. After a private attribute is set, it only takes effect for the corresponding account, and the difference attribute table includes private attributes matching a single account.

[0088] As one possible implementation, it is determined whether a private attribute exists in the difference attribute table of the first account; if a private attribute exists in the difference attribute table, the private attribute is set according to the attribute information carried in the target request; if a private attribute does not exist in the difference attribute table, a private attribute is created in the difference attribute table, and the private attribute is set according to the attribute information carried in the target request.

[0089] As an example, if the attribute to be set is a private attribute, and the attribute to be set exists in the differential attribute table of the first account, then the attribute to be set is set in the differential attribute table of the first account according to the attribute information carried in the target request.

[0090] As another example, if the attribute to be set is a private attribute and the attribute to be set does not exist in the differential attribute table of the first account, the attribute to be set is created in the differential attribute table of the first account, and the created attribute to be set is set according to the attribute information carried in the target request.

[0091] It should be noted that after setting the private attributes in the difference attribute table, the setting results of the private attributes are sent to the target terminal.

[0092] In this embodiment, to reduce redundant storage, the public attributes of the accounts bound to the target vehicle are stored in a public attribute table, and the private attributes of each account bound to the target vehicle are stored in a corresponding differential attribute table. The public attributes in the public attribute table can only be set by accounts with setting permissions, not all accounts bound to the vehicle can set them. Furthermore, when multiple accounts set attributes, the attributes are overwritten according to the order of setting, avoiding confusion and conflict in attribute settings. The private attributes in the differential attribute table can only be set by the account corresponding to that private attribute, avoiding setting conflicts between different accounts. This ensures that each account can independently manage its own private attributes without being interfered with by other accounts, improving the stability and reliability of the system.

[0093] To push the captured images, in this embodiment of the application, a captured image of the environment where the target vehicle is located is obtained; based on the subject in the captured image, a second account is determined in the difference attribute table of each account bound to the target vehicle; wherein the target of interest indicated by the private attribute of the second account is consistent with the subject in the captured image; captured image information is sent to the second account; wherein the captured image information is used to instruct the second account to capture the captured image.

[0094] In other words, after capturing footage from the target vehicle, the system analyzes the subject in the footage, such as identifying a specific person or object. Next, it consults the differential attribute table of each account linked to the target vehicle. This table records the private attributes of each account. By comparing the subject with the target of interest indicated by the private attributes in the differential attribute table, the system can identify the account whose target of interest matches the current subject, such as a second account. Finally, the system sends the footage capture information to the second account to indicate that the vehicle has captured footage that they might be interested in, thus achieving the push notification of the captured footage.

[0095] It should be noted that the execution process of step 301 can be implemented in any of the embodiments of this application. The embodiments of this application do not limit this, nor will they be described in detail.

[0096] In summary, when the target action includes setting attributes for the vehicle-mounted camera device, and the attribute to be set is a public attribute, the system queries the corresponding target permissions based on the authentication information. It then determines whether the target terminal is allowed to set the public attribute based on whether it has the permission to do so. This ensures that only users with the appropriate permissions can set the public attributes of the vehicle-mounted camera device, effectively preventing unauthorized users from setting public attributes and enhancing system security. Furthermore, when the attribute to be set is a private attribute, the system allows the target terminal to set the private attribute. This allows the private attributes of the target vehicle's linked account to be freely set by the associated account, satisfying users' personalized setting needs.

[0097] The above are various method embodiments executed by the target vehicle. This application also proposes another permission control method executed by the target terminal.

[0098] Figure 4 This is a flowchart illustrating another access control method provided in an embodiment of this application.

[0099] The access control method of this application can be applied to an access control device. In some possible embodiments, the access control device can be configured in a terminal (the target terminal in this application) or a chip, so that the terminal or chip can perform access control functions. Additionally, in some possible embodiments, the access control device can also be software within the terminal.

[0100] In any embodiment of this application, the chip can be integrated into a terminal. The chip includes a Central Processing Unit (CPU), Image Signal Processing (ISP), Application-Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), System on a Chip (SOC), Reduced Instruction Set Computer (RISC), etc., which will not be listed here. The terminal is a user-side entity used to receive or transmit signals, such as a mobile phone. A terminal can also be called a terminal device, user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal can be a mobile phone with communication capabilities, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, and so on. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0101] For ease of explanation, the following description will use the terminal as the executing entity of this access control method as an example.

[0102] like Figure 4 As shown, the access control method may include the following steps:

[0103] Step 401: Send the target request.

[0104] The target request is used to authenticate the target terminal, obtain authentication information, and determine whether the target terminal is allowed to perform target actions adapted to the target request on the vehicle's onboard camera device based on the target permissions corresponding to the authentication information.

[0105] As one possible implementation, the target terminal sends a target request to the cloud. This target request may include an audio / video access request or an attribute setting request. For example, clicking an audio / video access control on the target terminal's display interface sends an audio / video access request associated with that control to the cloud; similarly, clicking an attribute setting control on the target terminal's display interface sends an attribute setting request associated with that control to the cloud. Upon receiving the target request from the target terminal, the cloud performs authentication based on the user identifier in the target request, obtaining authentication information such as the user's identity category (driver, co-driver, or family member, etc.). Then, the cloud sends the target request and authentication information to the target vehicle. The target vehicle, based on the target permissions corresponding to the authentication information, determines whether to allow the target terminal to perform the target action on the in-vehicle camera device.

[0106] As one possible implementation, feedback information is received; wherein the feedback information is used to indicate whether the target terminal has the authority to perform the target action on the vehicle-mounted camera device; the feedback information is then visualized and / or broadcast via voice.

[0107] As one possible implementation, after the target vehicle receives the target request and authentication information sent from the cloud, it determines whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information. Then, it sends feedback information to the target terminal through the cloud, which is used to indicate whether the target terminal is allowed to perform the target action.

[0108] To enhance user experience, in this embodiment of the application, after receiving feedback information, the target terminal can select an appropriate method to present the feedback information to the user according to the needs of the scenario.

[0109] As one possible approach, when users are viewing the screen, feedback information can be presented to them intuitively through a graphical interface (such as pop-ups, icon changes, text prompts, etc. in mobile apps).

[0110] As another possible approach, in driving scenarios or scenarios where users cannot focus on the screen, feedback information can be conveyed to the user through voice prompts on the target terminal.

[0111] In addition, it should be noted that the two possible implementation methods mentioned above for presenting response information to users through the target terminal can also be used in combination to meet user needs in different scenarios and ensure the timeliness and convenience of information transmission.

[0112] In order to enable users to view the audio and video data of the vehicle-mounted camera device in real time, in this embodiment of the application, when the feedback information indicates that the target terminal has the authority to perform audio and video viewing actions on the target vehicle, a communication connection is established with the vehicle-mounted camera device; wherein, the communication connection is used to transmit the audio and video data of the vehicle-mounted camera device.

[0113] In other words, once the target terminal has been authenticated or authorized, it can access the audio and video data on the target vehicle. Then, the target terminal establishes a communication connection with the vehicle's onboard camera, which is used to transmit audio and video data between the target terminal and the target vehicle. Thus, the target terminal can receive and display real-time recorded audio and video data from the target vehicle.

[0114] In summary, by sending a target request, which is used to authenticate the target terminal, obtain authentication information, and determine whether the target terminal is allowed to perform target actions on the vehicle's in-vehicle camera device in accordance with the target request based on the target permissions corresponding to the authentication information, it is ensured that only authorized target terminals can perform target actions in accordance with the target request. This effectively prevents unauthorized access and operation, and improves vehicle security and user privacy protection.

[0115] In any embodiment of this application, such as Figure 5 As shown, the access control method of this application embodiment can also be implemented based on the following steps:

[0116] 1. User A opens the APP and clicks the button to view audio and video data. At this time, the APP sends an access request to view audio and video to the cloud.

[0117] 2. The cloud performs identity verification based on the UID, obtains identity verification information, and matches user permissions (driver, co-driver, family members, etc.). The request information and permission-related information (identity verification information) are then sent to the vehicle's infotainment system.

[0118] 3. The vehicle-mounted system receives the request forwarded from the cloud and determines the type of the current request.

[0119] 4. If it is an audio or video access request, an audio or video authorization request page will pop up on the vehicle's infotainment system. The driver must click "Allow" to authorize before proceeding to the next step of audio or video communication. If the driver clicks "Disallow" or does not click within the time limit, an authorization failure message will be returned.

[0120] 5. If it is an attribute setting request, the vehicle-mounted system will directly forward it to the IPC.

[0121] 6. After receiving an attribute setting request, IPC looks up the corresponding setting in the database based on the UID. If the attribute to be modified is a public attribute (such as video flip, high dynamic range (HDR) on / off switch, etc.), it checks whether the permissions are sufficient. If the permissions are sufficient, the configuration attribute can be modified and the result of whether the modification was successful or not will be returned. If the permissions are insufficient, a permission deficiency message will be returned.

[0122] 7. If the attribute to be modified is a private attribute (such as privacy area coordinates, AI event notifications, etc.), then the differential attribute table (also known as the differential linked list) is searched. If the attribute node does not exist in the differential attribute table, a new node is created. If a node already exists, its attribute value is modified. In addition, it should be noted that modifications to public attributes take effect on all accounts simultaneously, while modifications to private attributes only take effect on a single account.

[0123] 8. When an event is triggered (privacy area / AI event, etc.), iterate through the difference attribute table and judge / push relevant events according to different user configurations. That is, based on the subject being filmed in the video captured by the vehicle camera, determine the second account in the difference attribute table of each account bound to the target vehicle, and send the video capture information to the second account; the video capture information is used to instruct the second account to capture the video.

[0124] With the above Figures 1 to 3 Corresponding to the access control method provided in the embodiments, this disclosure also provides an access control device. Because the access control device provided in the embodiments of this application is similar to the one described above... Figures 1 to 3 The permission control method provided in the embodiments corresponds to the permission control device provided in the embodiments of this disclosure, and will not be described in detail in the embodiments of this disclosure.

[0125] Figure 6 This is a schematic diagram of the structure of an access control device provided in an embodiment of this application.

[0126] like Figure 6 As shown, the access control device 600 includes a receiving module 610 and a determining module 620.

[0127] The receiving module 610 is used to receive the target request from the target terminal and the corresponding authentication information; wherein the target request is used to request the vehicle-mounted camera device of the target vehicle to perform the target action, and the authentication information is obtained by authenticating the first account logged into the target terminal; the determining module 620 is used to determine whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information.

[0128] As one possible implementation, the target action includes accessing audio and video data from the vehicle-mounted camera device. The determination module 620 is used to obtain user operations based on authentication information and determine whether to allow the target terminal to access the audio and video data based on the target permissions indicated by the user operations.

[0129] As one possible implementation, the target permissions include having access or not having access. The determination module 620 is used to deny the target terminal access to audio and video data when the user operation indicates that access is not permitted; and to allow the target terminal to access audio and video data when the user operation indicates that access is permitted.

[0130] As one possible implementation, the target action includes setting attributes for the vehicle-mounted camera device. The determining module 620 is used to query the corresponding target permissions based on the authentication information when the attribute to be set is a public attribute, and determine whether to allow the target terminal to set the public attribute based on whether the target permissions have the permission to set the public attribute; when the attribute to be set is a private attribute, the target terminal is allowed to set the private attribute; wherein, the private attribute is the attribute private to the target vehicle's bound account.

[0131] As one possible implementation, the determining module 620 is used to allow the target terminal to set public attributes if the target permissions include the permission to set public attributes; and to prohibit the target terminal from setting public attributes if the target permissions do not include the permission to set public attributes.

[0132] As one possible implementation, the access control device 600 also includes a first sending module.

[0133] The first sending module is used to set attributes based on the attribute information carried in the target request, when the target terminal is allowed to set public attributes, to obtain the setting result of the public attributes; and to send the setting result to the target terminal.

[0134] As one possible implementation, the determining module 620 is used to determine whether a private attribute exists in the difference attribute table of the first account; if a private attribute exists in the difference attribute table, the private attribute is set according to the attribute information carried in the target request; if a private attribute does not exist in the difference attribute table, the private attribute is created in the difference attribute table, and the private attribute is set according to the attribute information carried in the target request.

[0135] As one possible implementation, the access control device 600 also includes a second sending module.

[0136] The second sending module is used to send feedback information to the target terminal; the feedback information is used to indicate whether the target terminal is allowed to perform the target action.

[0137] As one possible implementation, the access control device 600 also includes a third sending module.

[0138] The third sending module is used to acquire the captured image of the environment where the target vehicle is located; determine the second account based on the subject in the captured image from the difference attribute table of each account bound to the target vehicle; wherein the target of interest indicated by the private attribute of the second account is consistent with the subject in the captured image; and send the captured image information to the second account; wherein the captured image information is used to instruct the second account to capture the captured image.

[0139] The access control device in this application receives the target request from the target terminal and its corresponding authentication information, and determines whether to allow the target terminal to perform the target action based on the target permission corresponding to the authentication information. This ensures that only authorized target terminals can perform the target action adapted to the target request, effectively preventing unauthorized access and operation by the target terminal, and improving vehicle safety and user privacy protection.

[0140] With the above Figure 4 Corresponding to the access control method provided in the embodiments, this disclosure also provides an access control device. Because the access control device provided in the embodiments of this application is similar to the one described above... Figure 4 The permission control method provided in the embodiments corresponds to the permission control device provided in the embodiments of this disclosure, and will not be described in detail in the embodiments of this disclosure.

[0141] Figure 7 This is a schematic diagram of another access control device provided in an embodiment of this application.

[0142] like Figure 7 As shown, the access control device 700 includes a sending module 710.

[0143] The sending module 710 is used to send the target request.

[0144] As one possible implementation, the access control device 700 also includes a receiving module.

[0145] The receiving module is used to receive feedback information; the feedback information is used to indicate whether the target terminal has the authority to perform the target action on the vehicle-mounted camera device; and to visualize and / or broadcast the feedback information via voice.

[0146] As one possible implementation, the target request is used to view the audio and video of the vehicle's onboard camera. The access control device 700 also includes a communication module.

[0147] The communication module is used to establish a communication connection with the vehicle-mounted camera when the feedback information indicates that the target terminal has the authority to view the audio and video of the vehicle-mounted camera. The communication connection is used to transmit the audio and video data of the vehicle-mounted camera.

[0148] The access control device in this application embodiment sends a target request; wherein the target request is used to authenticate the target terminal, obtain authentication information, and determine whether the target terminal is allowed to perform a target action adapted to the target request on the vehicle's in-vehicle camera device based on the target permission corresponding to the authentication information. Thus, only authorized target terminals can perform target actions adapted to the target request, effectively preventing unauthorized access and operation, and improving vehicle security and user privacy protection.

[0149] To implement the above embodiments, this disclosure also proposes a vehicle, including a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to achieve, as follows: Figures 1 to 3 The access control method described in the embodiments.

[0150] To implement the above embodiments, this disclosure also proposes an electronic device, including a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to achieve the following: Figure 4 The access control method described in the embodiments.

[0151] To implement the above embodiments, this disclosure also proposes a chip including a processing circuit configured to execute the access control method as described in the foregoing method embodiments.

[0152] To implement the above embodiments, this disclosure also proposes a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the access control method as described in the foregoing method embodiments.

[0153] To implement the above embodiments, this disclosure also proposes a computer program product on which a computer program is stored, wherein the computer program, when executed by a processor, implements the access control method as described in the foregoing method embodiments.

[0154] Figure 8This is a block diagram illustrating a vehicle 800 according to an exemplary embodiment. For example, vehicle 800 may be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicle. Vehicle 800 may be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.

[0155] Reference Figure 8 The vehicle 800 may include various subsystems, such as an infotainment system 810, a perception system 820, a decision control system 830, a drive system 840, and a computing platform 850. The vehicle 800 may also include more or fewer subsystems, and each subsystem may include multiple components. Furthermore, each subsystem and each component of the vehicle 800 can be interconnected via wired or wireless means.

[0156] In some embodiments, the infotainment system 810 may include a communication system, an entertainment system, and a navigation system, etc.

[0157] The perception system 820 may include several sensors for sensing information about the environment surrounding the vehicle 800. For example, the perception system 820 may include a global positioning system (which may be GPS, BeiDou, or other positioning systems), an inertial measurement unit (IMU), lidar, millimeter-wave radar, ultrasonic radar, and a camera device.

[0158] The decision control system 830 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.

[0159] The drive system 840 may include components that provide powered motion to the vehicle 800. In one embodiment, the drive system 840 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of internal combustion engines, electric motors, and compressed air engines. The engine is capable of converting energy provided by the energy source into mechanical energy.

[0160] Some or all of the functions of the vehicle 800 are controlled by a computing platform 850. The computing platform 850 may include at least one processor 851 and a memory 852, the processor 851 being able to execute instructions 853 stored in the memory 852.

[0161] The processor 851 can be any conventional processor, such as a commercially available CPU. The processor may also include, for example, a Graphics Processing Unit (GPU), a Field Programmable Gate Array (FPGA), a System on Chip (SOC), an Application Specific Integrated Circuit (ASIC), or a combination thereof.

[0162] The memory 852 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0163] In addition to instruction set 853, memory 852 can also store data, such as road maps, route information, vehicle position, direction, speed, and other data. The data stored in memory 852 can be used by computing platform 850.

[0164] In this embodiment of the disclosure, processor 851 may execute instructions 853 to complete all or part of the steps of the above-described method embodiments.

[0165] Figure 9 This is a block diagram of an electronic device provided in an embodiment of this application. For example, the electronic device 900 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0166] Reference Figure 9 The electronic device 900 may include one or more of the following components: processing component 902, memory 904, power component 906, multimedia component 908, audio component 910, input / output (I / O) interface 912, sensor component 914, and communication component 916.

[0167] Processing component 902 typically controls the overall operation of electronic device 900, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 902 may include one or more processors 920 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 902 may include one or more modules to facilitate interaction between processing component 902 and other components. For example, processing component 902 may include a multimedia module to facilitate interaction between multimedia component 908 and processing component 902.

[0168] Memory 904 is configured to store various types of data to support the operation of electronic device 900. Examples of this data include instructions for any application or method operating on electronic device 900, contact data, phonebook data, messages, pictures, videos, etc. Memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0169] Power component 906 provides power to various components of electronic device 900. Power component 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 900.

[0170] Multimedia component 908 includes a screen that provides an output interface between the electronic device 900 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 908 includes a front-facing camera and / or a rear-facing camera. When the electronic device 900 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0171] Audio component 910 is configured to output and / or input audio signals. For example, audio component 910 includes a microphone (MIC) configured to receive external audio signals when electronic device 900 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 904 or transmitted via communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.

[0172] I / O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0173] Sensor assembly 914 includes one or more sensors for providing state assessments of various aspects of electronic device 900. For example, sensor assembly 914 can detect the on / off state of electronic device 900, the relative positioning of components such as the display and keypad of electronic device 900, changes in position of electronic device 900 or a component of electronic device 900, the presence or absence of user contact with electronic device 900, orientation or acceleration / deceleration of electronic device 900, and temperature changes of electronic device 900. Sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 914 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 914 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0174] Communication component 916 is configured to facilitate wired or wireless communication between electronic device 900 and other devices. Electronic device 900 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 916 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 916 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0175] In an exemplary embodiment, the electronic device 900 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0176] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including instructions, which can be executed by a processor 920 of an electronic device 900 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0177] Figure 10 This is a schematic diagram of the chip structure proposed in an embodiment of this application. See also... Figure 10 The diagram shown is a schematic representation of the structure of chip 1000, but it is not limited to this.

[0178] Chip 1000 includes processing circuit 1001, which is configured to perform any of the above methods.

[0179] In some embodiments, the chip 1000 further includes one or more interface circuits 1002. Optionally, the interface circuit 1002 is connected to the memory 1003, and the interface circuit 1002 can be used to receive signals from the memory 1003 or other devices, and the interface circuit 1002 can be used to send signals to the memory 1003 or other devices. For example, the interface circuit 1002 can read instructions stored in the memory 1003 and send the instructions to the processing circuit 1001.

[0180] In some embodiments, the interface circuit 1002 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 1001 performs other steps.

[0181] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0182] In some embodiments, chip 1000 further includes one or more memories 1003 for storing instructions. Optionally, all or part of the memories 1003 may be located outside of chip 1000.

[0183] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0184] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0185] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0186] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0187] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0188] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0189] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0190] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A method for access control of a vehicle-mounted camera device, characterized in that, include: Receive a target request from the target terminal and corresponding authentication information; wherein, the target request is used to request the vehicle-mounted camera device of the target vehicle to perform a target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal; Based on the target permissions corresponding to the authentication information, determine whether the target terminal is allowed to perform the target action.

2. The method according to claim 1, characterized in that, The target action includes accessing the audio and video data of the vehicle-mounted camera device; determining whether to allow the target terminal to execute the target action based on the target permissions corresponding to the authentication information includes: Based on the authentication information, obtain the user's actions; Based on the target permissions indicated by the user operation, determine whether to allow the target terminal to access the audio and video data.

3. The method according to claim 2, characterized in that, The target permissions include having access rights or not having access rights; The step of determining whether to allow the target terminal to access the audio and video data based on the target permissions indicated by the user operation includes: If the user operation indicates that they do not have permission to access, the target terminal is denied access to the audio and video data; If the user operation indicates that they have permission to access, the target terminal is allowed to access the audio and video data.

4. The method according to claim 1, characterized in that, The target action includes setting attributes for the vehicle-mounted camera device. The step of determining whether to allow the target terminal to execute the target action based on the target permissions corresponding to the authentication information includes: If the attribute to be set is a public attribute, the corresponding target permissions are queried based on the authentication information, and it is determined whether the target terminal is allowed to set the public attribute based on whether the target permissions have the permission to set the public attribute. If the attribute to be set is a private attribute, the target terminal is allowed to set the private attribute; wherein, the private attribute is a private attribute of the target vehicle's bound account.

5. The method according to claim 4, characterized in that, The step of determining whether to allow the target terminal to set the public attribute based on whether the target permissions include permission to set the public attribute includes: If the target permissions include the permission to set the public attribute, then the target terminal is allowed to set the public attribute; If the target permissions do not include the permission to set the public attribute, the target terminal is prohibited from setting the public attribute.

6. The method according to claim 4, characterized in that, The method further includes: If the target terminal is allowed to set the public attribute, the attribute is set according to the attribute information carried in the target request to obtain the setting result of the public attribute; The setting result is sent to the target terminal.

7. The method according to claim 4, characterized in that, The step of allowing the target terminal to set the private attribute includes: Determine whether the private attribute exists in the differential attribute table of the first account; If the private attribute exists in the difference attribute table, then the private attribute is set according to the attribute information carried in the target request; If the private attribute does not exist in the difference attribute table, the private attribute is created in the difference attribute table, and the private attribute is set according to the attribute information carried in the target request.

8. The method according to claim 1, characterized in that, The method further includes: Send feedback information to the target terminal; wherein the feedback information is used to indicate whether the target terminal is allowed to perform the target action.

9. The method according to claim 1, characterized in that, The method further includes: Acquire images of the environment in which the target vehicle is located; Based on the subject being filmed in the captured image, a second account is determined from the difference attribute table of each account bound to the target vehicle; wherein the target of interest indicated by the private attribute of the second account is consistent with the subject being filmed. Sending image capture information to the second account; wherein, the image capture information is used to instruct the second account to capture the image.

10. A method for access control of a vehicle-mounted camera device, characterized in that, include: Send the target request.

11. The method according to claim 10, characterized in that, The method further includes: Receive feedback information; wherein the feedback information is used to indicate whether the target terminal has the authority to perform the target action on the vehicle-mounted camera device; The feedback information is displayed visually and / or broadcast aloud.

12. The method according to claim 11, characterized in that, The target request is used to view the audio and video of the vehicle's onboard camera device, and the method further includes: When the feedback information indicates that the target terminal has the authority to view the audio and video of the vehicle's in-vehicle camera, a communication connection is established with the in-vehicle camera; wherein, the communication connection is used to transmit the audio and video data of the in-vehicle camera.

13. An access control device for a vehicle-mounted camera, characterized in that, include: The receiving module is used to receive a target request from a target terminal and corresponding authentication information; wherein, the target request is used to request the vehicle-mounted camera device of the target vehicle to perform a target action, and the authentication information is obtained by authenticating the first account that logs into the target terminal; The determination module is used to determine whether to allow the target terminal to perform the target action based on the target permissions corresponding to the authentication information.

14. An access control device for a vehicle-mounted camera, characterized in that, include: The sending module is used to send target requests.

15. A vehicle, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-9.

16. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 10-12.

Images