Vehicle data authority autonomous management and control method, device and equipment, and storage medium

Abstract

This application relates to the field of vehicle data security technology, and in particular to a method, apparatus, device, and storage medium for autonomous management of vehicle data permissions. The method includes: setting data tags for each vehicle data; determining the data usage permissions corresponding to each vehicle data based on the data tags and usage permission configuration instructions to obtain usage permission information; determining the data scene permissions corresponding to each vehicle data from a data scene permission library based on the scene permission configuration instructions corresponding to each vehicle data to obtain scene permission information; responding to a data upload instruction, determining the target vehicle data corresponding to the data upload instruction, and determining the target data usage permissions and target data scene permissions corresponding to the target vehicle data from the usage permission information and scene permission information; and uploading the target vehicle data, target data usage permissions, and target data scene permissions to the cloud. This application facilitates reducing the risk of leakage of private vehicle data and improves the flexibility of autonomous management of vehicle data permissions.

Description

Technical Field

[0001] This application relates to the field of vehicle data security technology, and in particular to a method, device, equipment and storage medium for autonomous control of vehicle data permissions. Background Technology

[0002] During operation, the vehicle's infotainment system needs to collect vehicle data and send it to the cloud for processing in order to provide users with corresponding services, such as traffic congestion analysis results. However, to prevent the misuse or leakage of vehicle data, users need to use the infotainment system or (or a smart device that communicates with the infotainment system) to complete the self-configuration (self-management) of vehicle data permissions before the infotainment system has the corresponding permissions to upload the corresponding vehicle data to the cloud for processing.

[0003] Currently, the common way for users to autonomously manage vehicle data permissions through the vehicle's infotainment system is as follows: when logging into the vehicle's infotainment system, users agree to the relevant privacy agreement on vehicle data collection and use by checking the boxes on the login interface, thereby achieving autonomous management of vehicle data permissions.

[0004] However, firstly, in order to collect as much vehicle data as possible, cloud providers often reduce the control over vehicle data that can be uploaded to the cloud to the lowest level in the agreement, resulting in a large amount of highly private vehicle data being uploaded to the cloud, leading to a high risk of leakage of private vehicle data; secondly, since users can only control the permissions of all vehicle data by checking boxes in the agreement, it is difficult for users to flexibly adjust the usage permissions of different types of vehicle data according to their own wishes, resulting in poor flexibility in self-management of vehicle data permissions. Summary of the Invention

[0005] To reduce the risk of leakage of private vehicle data and improve the flexibility of autonomous control of vehicle data permissions, this application provides a method, apparatus, device and storage medium for autonomous control of vehicle data permissions.

[0006] Firstly, this application provides a method for autonomous management of vehicle data permissions, including: Data tags are set for each vehicle data in the vehicle dataset. Based on the data tags and the obtained usage permission configuration instructions, the data usage permissions corresponding to each vehicle data are determined to obtain usage permission information. Based on the scene permission configuration instructions corresponding to each of the vehicle data, the data scene permissions corresponding to each of the vehicle data are determined from the preset data scene permission library to obtain scene permission information; In response to a data upload instruction, the target vehicle data corresponding to the data upload instruction is determined, and the target data usage permission and target data scene permission corresponding to the target vehicle data are determined from the usage permission information and the scene permission information, respectively. The target vehicle data, along with the corresponding target data usage permissions and target data scenario permissions, are simultaneously uploaded to the cloud.

[0007] Secondly, this application provides a vehicle data access control autonomous management device, comprising: The purpose permission configuration module is used to set data tags for each vehicle data in the vehicle dataset, and determine the data purpose permission corresponding to each vehicle data based on the data tags and the obtained purpose permission configuration instructions, so as to obtain the purpose permission information. The scene permission configuration module is used to determine the data scene permissions corresponding to each of the vehicle data from a preset data scene permission library based on the scene permission configuration instructions corresponding to each of the vehicle data, and obtain scene permission information; The permission determination module is used to respond to a data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively. The data upload module is used to synchronously upload the target vehicle data and the corresponding target data usage permissions and target data scene permissions to the cloud.

[0008] Thirdly, this application provides a computer device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the method described above.

[0009] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described method.

[0010] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0011] The aforementioned autonomous vehicle data access control method, device, equipment, and storage medium, by setting data tags for each vehicle data in a vehicle dataset, determining the data usage permissions corresponding to each vehicle data based on the data tags and the acquired usage permission configuration instructions, and obtaining usage permission information; based on the scene permission configuration instructions corresponding to each vehicle data, determining the data scene permissions corresponding to each vehicle data from a preset data scene permission library, and obtaining scene permission information; responding to the acquisition of a data upload instruction, determining the target vehicle data corresponding to the data upload instruction, and determining the target data usage permissions and target data scene permissions corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively; and synchronously uploading the target vehicle data and the corresponding target data usage permissions and target data scene permissions to the cloud. Through the above implementation, users can flexibly issue usage permission configuration commands and scenario permission configuration commands in the vehicle data permission setting scenarios according to their own wishes. This makes it easier to configure higher usage permissions for private vehicle data, thereby reducing the risk of leakage of private vehicle data. In addition, since users can flexibly set different usage permissions for different types of vehicle data according to usage permission configuration commands and scenario permission configuration commands, the flexibility of autonomous control of vehicle data permissions can be effectively improved.

[0012] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a flowchart of a method for autonomous management of vehicle data permissions provided in the embodiments of this application; Figure 2 This is a schematic diagram of the structure of a vehicle data access autonomous control device provided in the embodiments of this application; Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application; Figure 4 This is an internal structural diagram of a computer-readable storage medium provided in an embodiment of this application. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this disclosure.

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

[0017] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0018] Example 1 Figure 1 This is a flowchart of a vehicle data access control method provided in Embodiment 1 of this application, for reference. Figure 1 The method can be executed by a device that performs the method, which can be implemented in software and / or hardware, and the method includes: S110. Set data tags for each vehicle data in the vehicle dataset. Based on the data tags and the obtained usage permission configuration instructions, determine the data usage permissions corresponding to each vehicle data to obtain usage permission information.

[0019] It should be noted that vehicles can collect a variety of vehicle data. For example, vehicle data includes: vehicle status data (vehicle speed, engine / motor speed, wheel speed, etc.), environmental perception data (in-vehicle camera data, radar point cloud, environmental images, temperature, air pressure, etc.), location and network data (vehicle location, network speed, etc.), human-machine interaction data (voice commands, touch operation, etc.), etc., without any specific limitations.

[0020] The vehicle's infotainment system can display various vehicle data to the user in a list format. All the vehicle data listed in the list are collectively referred to as the vehicle dataset, which includes the various vehicle data types mentioned above. Taking one vehicle data point in the dataset as an example, after the user selects that data, a list of data tags pops up. This list includes various data tags, such as vehicle status, environmental perception, location and network, human-machine interaction, etc., without specific limitations. The user can set corresponding data tags for the corresponding vehicle data by selecting tags. The infotainment system receives the tag selection command from the user and sets the data tag corresponding to that command as the data tag for the corresponding vehicle data. In this way, corresponding data tags can be set for each vehicle data point in the vehicle dataset (such as vehicle speed, in-vehicle camera data, vehicle location, voice commands, etc.).

[0021] The vehicle infotainment system includes a permission configuration model. This model is used to configure corresponding data usage permissions for each vehicle data corresponding to one or more data tags selected by the user, based on the user's usage permission configuration command. The permission configuration model is a pre-trained model set in the vehicle infotainment system. The usage permission configuration command is a command issued by the user to the vehicle infotainment system to set corresponding data usage permissions for vehicle data. The command form of the usage permission configuration command includes, but is not limited to, voice commands and text commands. The data usage permissions are used to limit the scope of use of the vehicle data corresponding to the vehicle data.

[0022] For example, a user issues a usage permission configuration instruction stating, "Limit the data usage permission for vehicle data tagged with 'Vehicle Status' and 'Environmental Awareness' to traffic congestion analysis." The permission configuration model processes this usage permission configuration instruction and generates data usage permissions, which are: the data usage permission for vehicle data tagged with "Vehicle Status" and "Environmental Awareness" is "for traffic congestion analysis." Using the method shown in this example, corresponding data usage permissions can be determined for each vehicle data point in the vehicle dataset, and the data usage permissions corresponding to each vehicle data point are collectively referred to as usage permission information.

[0023] S120. Based on the scene permission configuration instructions corresponding to each of the vehicle data, determine the data scene permissions corresponding to each of the vehicle data from the preset data scene permission library, and obtain scene permission information.

[0024] It should be noted that users may want to restrict the corresponding permissions for certain vehicle data for a certain vehicle usage scenario. To facilitate users in setting such permissions, this embodiment has a pre-set data scenario permission library based on pre-collected user suggestions. This data scenario permission library includes a variety of data scenario permissions. For example, one data scenario permission is "automatically prohibit sharing of in-vehicle camera data in 'valet parking' mode".

[0025] The aforementioned permission configuration model can also match the corresponding data scenario permissions from the data scenario permission library for the vehicle data corresponding to the scenario permission configuration command issued by the user.

[0026] For example, if a user issues a scenario permission configuration command of "Disable in-vehicle camera data in valet parking mode," the permission configuration model retrieves the data scenario permission in the data scenario permission library that has the highest semantic similarity to this command, namely, "Automatically prohibit sharing in-vehicle camera data in 'valet parking' mode." This data scenario permission is then matched to the vehicle data (in-vehicle camera data) corresponding to this command. Using the method shown in this example, corresponding data scenario permissions can be generated for each vehicle data in the vehicle dataset, and the data scenario permissions corresponding to each vehicle data in the vehicle dataset are collectively referred to as scenario permission information.

[0027] S130. In response to the data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively.

[0028] It should be noted that during the interaction between the vehicle and the cloud, in order to perform a certain goal, such as providing traffic congestion analysis services for the vehicle, the cloud will issue corresponding data upload instructions to the vehicle to request the corresponding vehicle data.

[0029] Among them, the data upload instruction corresponds to one or more types of vehicle data, and the vehicle data corresponding to the data upload instruction is recorded as the target vehicle data; taking one type of target vehicle data as an example, the data usage permission corresponding to this type of target vehicle data in the usage permission information is recorded as the target data usage permission, and the data scene permission corresponding to this type of target vehicle data in the scene permission information is also recorded as the target data scene permission.

[0030] In this embodiment, the target vehicle data is associated with the corresponding target data usage permissions and target data scenario permissions in the form of key-value pairs ([key, first value, second value]), where the key is the target vehicle data, the first value is the target data usage permissions, and the second value is the target data scenario permissions.

[0031] S140. The target vehicle data and the corresponding target data usage permissions and target data scene permissions are simultaneously uploaded to the cloud.

[0032] To prevent the cloud from arbitrarily using the vehicle data corresponding to the target vehicle data, the target vehicle data, along with the corresponding target data usage permissions and target data scenario permissions, are also uploaded to the cloud simultaneously when the target vehicle data is uploaded to the cloud.

[0033] In an optional embodiment, if the target vehicle data is private data, the target vehicle data is de-identified to obtain de-identified data, and the de-identified data is stored locally (in the vehicle system); if the target vehicle data is non-private data, the target vehicle data and the corresponding target data usage permissions and target data scenario permissions are synchronously uploaded to the cloud.

[0034] It should be noted that this embodiment sets data tags for each vehicle data in the vehicle dataset, and determines the data usage permissions corresponding to each vehicle data based on the data tags and the obtained usage permission configuration instructions, thus obtaining usage permission information; based on the scene permission configuration instructions corresponding to each vehicle data, it determines the data scene permissions corresponding to each vehicle data from a preset data scene permission library, thus obtaining scene permission information; in response to obtaining a data upload instruction, it determines the target vehicle data corresponding to the data upload instruction, and determines the target data usage permissions and target data scene permissions corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively; and it synchronously uploads the target vehicle data and the corresponding target data usage permissions and target data scene permissions to the cloud. Through the above implementation, users can flexibly issue usage permission configuration instructions and scene permission configuration instructions in the vehicle data permission setting scenarios according to their own wishes, which makes it easy to configure higher usage permissions for private vehicle data, thereby reducing the risk of leakage of private vehicle data; in addition, since users can flexibly set different usage permissions for different types of vehicle data according to usage permission configuration instructions and scene permission configuration instructions, the flexibility of autonomous management of vehicle data permissions can be effectively improved.

[0035] Example 2 This application provides a method for autonomous management of vehicle data permissions in Embodiment 2. This method optimizes the "setting data labels for each vehicle data in the vehicle dataset" in Embodiment 1. It should be noted that for parts not described in detail in this embodiment, please refer to the descriptions in other embodiments. The method includes: S211. Determine the metadata of each vehicle data in the vehicle dataset.

[0036] It should be noted that, taking one type of vehicle data as an example, this vehicle data has corresponding metadata set according to a predetermined data format, and the vehicle system can collect the metadata corresponding to each vehicle data.

[0037] The predetermined data format consists of multiple fields, including: data name (data_name) + data domain (data_domain) + data format type (data_type) + data collection location (collect_position) + data sensitivity level (sensitive_level). In other embodiments, the specific fields are not limited.

[0038] For example, the metadata corresponding to a vehicle data is: rear seat camera data + cabin domain + image type + rear seat + high privacy.

[0039] S212. Based on the metadata of the vehicle data and a preset rule base, determine the data tag of the vehicle data.

[0040] It should be noted that this embodiment has a pre-set rule base, which is used to match the metadata of vehicle data to determine the data tag corresponding to the metadata.

[0041] The rule base contains multiple conditional expressions, which are used to make logical judgments on one or more fields in the metadata. If the logical judgment passes, the corresponding data tag is set for the vehicle data corresponding to that metadata.

[0042] For example, a conditional expression in the rule base is: data_domain == "cockpit domain" AND collect_position == "inside the vehicle". The data label corresponding to this conditional expression is "cockpit privacy data". If the functional domain (data_domain) of a certain vehicle data's metadata is "cockpit domain" and the data collection location (collect_position) is "inside the vehicle", then the logic judgment passes, and the data label "cockpit privacy data" is set for the vehicle data corresponding to the metadata.

[0043] Through the above implementation, corresponding data tags can be automatically matched for each vehicle data, eliminating the need for users to manually set corresponding data tags for each type of vehicle data, thus effectively improving the efficiency of setting vehicle data tags. Each data tag may correspond to multiple types of vehicle data. When a user wants to set corresponding usage permissions for each type of vehicle data corresponding to a certain data tag (such as "cabin privacy data"), it is not necessary to set corresponding usage permissions for each vehicle corresponding to that data tag individually. Instead, the user can directly determine the corresponding types of vehicle data through that data tag, so that the corresponding usage permissions can be set synchronously for all types of vehicle data corresponding to that data tag in a unified manner, thus effectively improving the efficiency of setting vehicle data usage permissions.

[0044] S213. Based on the data tags and the obtained usage permission configuration instructions, determine the data usage permissions corresponding to each of the vehicle data, and obtain usage permission information.

[0045] S220. Based on the scene permission configuration instructions corresponding to each of the vehicle data, determine the data scene permissions corresponding to each of the vehicle data from the preset data scene permission library, and obtain scene permission information.

[0046] S230. In response to the data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively.

[0047] S240. The target vehicle data and the corresponding target data usage permissions and target data scene permissions are simultaneously uploaded to the cloud.

[0048] Example 3 This application provides a method for autonomous management of vehicle data permissions in Embodiment 3. This method optimizes the step of "determining the data tag of the vehicle data based on the metadata of the vehicle data and a preset rule base" in Embodiment 2. It should be noted that for parts not described in detail in this embodiment, please refer to the descriptions in other embodiments. The method includes: S311. Determine the metadata of each vehicle data in the vehicle dataset.

[0049] S312A. In response to the fact that the metadata of the vehicle data does not successfully match the corresponding data tag in the preset rule base, the vehicle data is determined to be data to be matched.

[0050] It should be noted that the types of conditional expressions in the preset rule base are limited, and there may be cases where the metadata of a certain type of vehicle data does not match the corresponding data tag in the rule base. In order to determine the data tag corresponding to the vehicle data, this embodiment intends to use the data tags of other types of vehicle data that have a high degree of similarity to the vehicle data as the data tag of the vehicle data.

[0051] If it is determined that the metadata of the vehicle data does not successfully match the corresponding data tag in the preset rule base, then the vehicle data is recorded as data to be matched.

[0052] S312B. Calculate the data similarity between the data to be matched and the data of each other vehicle in the vehicle dataset to obtain a similarity set.

[0053] The vehicle dataset includes various types of vehicle data. The similarity between the data to be matched and any non-matching vehicle data in the dataset can be calculated and denoted as data similarity. In this embodiment, data similarity specifically refers to semantic relevance or semantic similarity; in other embodiments, the specific meaning is not limited.

[0054] For example, taking the calculation of the semantic relevance between the data to be matched and any non-matching vehicle data in the vehicle dataset as an example, firstly, the word vectors of the data to be matched and the vehicle data are calculated separately, denoted as the first word vector A and the second word vector B, respectively; then, the Euclidean distance d1 between the first word vector A and the second word vector B is calculated, and then the Euclidean distance d1 is normalized to obtain the semantic relevance d2, which is used as the data similarity. In other embodiments, the cosine similarity between the first word vector A and the second word vector B can also be used as the data similarity, and there is no specific limitation.

[0055] In this way, the data similarity between the data to be matched and any non-data in the vehicle dataset can be calculated, and the set of calculated data similarities is denoted as the similarity set.

[0056] S312C. In response to the vehicle data corresponding to the largest data similarity in the similarity set, if there is a corresponding data tag, the data tag is shared as the data tag of the data to be matched.

[0057] The greater the data similarity, the higher the semantic relevance between the corresponding data to be matched and the vehicle data. This also indicates that the two belong to the same type of data and are more likely to have the same data label. For example, vehicle speed data (one type of vehicle data) and vehicle acceleration data (another type of vehicle data) have a high semantic relevance. Both belong to the vehicle state data type, and both should have the same data label "vehicle speed state".

[0058] Among them, the vehicle data with the highest data similarity in the similarity set has the highest semantic relevance to the data to be matched. If the vehicle data already has a corresponding data tag, the data tag can be shared with the data to be matched.

[0059] In other embodiments, if the vehicle data corresponding to the largest data similarity in the similarity set does not have a corresponding data label, then the data label can be shared with the data to be matched if the vehicle data corresponding to the second largest data similarity in the similarity set has a data label; and so on, until the vehicle data corresponding to the third largest data similarity in the similarity set is determined.

[0060] Through the above implementation, in the case of vehicle data (data to be matched) that has not been matched with a data tag, the data tags of other vehicle data that have a high degree of similarity to the data to be matched can be shared with the data to be matched, thereby ensuring that the data to be matched also has a corresponding data tag as much as possible. Since data tags can improve the efficiency of setting usage permissions for vehicle data, determining the corresponding data tag for the data to be matched facilitates improving the efficiency of setting usage permissions for the data to be matched in the future.

[0061] S313. Based on the data tags and the obtained usage permission configuration instructions, determine the data usage permissions corresponding to each of the vehicle data, and obtain usage permission information.

[0062] S320. Based on the scene permission configuration instructions corresponding to each of the vehicle data, determine the data scene permissions corresponding to each of the vehicle data from the preset data scene permission library, and obtain scene permission information.

[0063] S330. In response to the data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively.

[0064] S340. The target vehicle data and the corresponding target data usage permissions and target data scene permissions are simultaneously uploaded to the cloud.

[0065] Example 4 This application provides a method for autonomous management of vehicle data permissions in Embodiment 4. This method optimizes the step in Embodiment 1, which involves "determining the data scene permissions corresponding to each vehicle data from a preset data scene permission library based on the scene permission configuration instructions corresponding to each vehicle data, and obtaining scene permission information." It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S410. Set data tags for each vehicle data in the vehicle dataset. Based on the data tags and the obtained usage permission configuration instructions, determine the data usage permissions corresponding to each vehicle data and obtain usage permission information.

[0066] S421. Construct a data tree based on the vehicle data, and determine the target data node from the data tree.

[0067] The vehicle dataset contains various types of vehicle data, which may have corresponding hierarchical relationships. For example, the vehicle dataset includes vehicle status data, vehicle speed data, motor data, vehicle acceleration data, wheel speed data, motor temperature data, and motor speed data. Vehicle speed data and motor data belong to vehicle status data; vehicle acceleration data and wheel speed data belong to vehicle speed data; and motor temperature data and motor speed data belong to motor data. Based on these hierarchical relationships, a corresponding data tree can be constructed. The vehicle status data is the root node, with two child nodes: vehicle speed data and motor data. Vehicle speed data has two child nodes: vehicle acceleration data and wheel speed data. Motor data has two child nodes: motor temperature data and motor speed data.

[0068] Among them, it is used to select any node from the data tree as the target data node according to one's own wishes.

[0069] S422. Based on the scene permission configuration instruction corresponding to the target data node, determine the data scene permission corresponding to the target data node from the preset data scene permission library to obtain the target data scene permission.

[0070] Users can input corresponding scene permission configuration instructions into the permission configuration model built into the vehicle system according to the selected target data node (a type of vehicle data). This allows the permission configuration model to select the data scene permission with the highest semantic similarity to the scene permission configuration instruction from the preset data scene permission library, and use it as the target data scene permission for the target data node.

[0071] For example, if the target data node selected by the user is "vehicle status data", the scenario permission configuration instruction input to the permission configuration model based on the target data node is: do not share "vehicle status data" in "valet parking" mode. The target data scenario permission output by the permission configuration model is: prohibit sharing "vehicle status data" in "valet parking" mode.

[0072] S423. In response to the target data node being the parent node in the data tree, the target data scene permissions are shared to child nodes at different levels under the parent node.

[0073] It should be noted that if a data node in the data tree is a parent node, that is, if the data node has at least one child node, then the target data scenario permissions set for the parent node are generally also applicable to the child nodes under the parent node.

[0074] Specifically, if the target data node is determined to be the parent node in the data tree, the target data scene permissions set for the target data node will also be shared with the child nodes at different levels under the parent node. That is, the same target data scene permissions will be set for the parent node and all its child nodes.

[0075] By implementing the above methods, the efficiency of setting scene permissions for vehicle data can be effectively improved by sharing the target data scene permissions of the parent node to all child nodes under the parent node.

[0076] S430. In response to the data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively.

[0077] S440. The target vehicle data and the corresponding target data usage permissions and target data scene permissions are simultaneously uploaded to the cloud.

[0078] Example 5 This application provides a method for autonomous management of vehicle data permissions in Embodiment 5. This method optimizes the step in Embodiment 4, which involves "determining the data scene permissions corresponding to the target data node from a preset data scene permission library based on the scene permission configuration instruction corresponding to the target data node, and obtaining the target data scene permissions". It should be noted that for parts not described in detail in this embodiment, please refer to the descriptions in other embodiments. The method includes: S510. Set data tags for each vehicle data in the vehicle dataset, and determine the data usage permissions corresponding to each vehicle data based on the data tags and the obtained usage permission configuration instructions, thereby obtaining usage permission information.

[0079] S521. Construct a data tree based on the vehicle data, and determine the target data node from the data tree.

[0080] S522A. Calculate the semantic relevance between the target data node and the permissions of each data scenario in the preset data scenario permission library to obtain an initial relevance set.

[0081] Among them, the number of data scenario permissions in the preset data scenario permission library is large. The data scenario permissions corresponding to the target data nodes that are subsequently determined have a relatively high semantic relevance to the target data nodes. Therefore, the semantic relevance between each data scenario permission in the data scenario permission library and the target data nodes can be calculated first, and the calculated semantic relevance is collectively referred to as the initial relevance set.

[0082] S522B. Sort the initial relevance set in descending order to obtain the target relevance set.

[0083] The target relevance set is the new set of semantic relevance obtained by reordering the semantic relevance in the initial relevance set in descending order.

[0084] S522C. Determine a preset number of initial relevances from the target relevance set to obtain a target relevance group.

[0085] In this embodiment, the preset quantity is 5, but in other embodiments, the specific quantity is not limited.

[0086] S522D. Determine the data scene permissions corresponding to each initial relevance in the target relevance group in the preset data scene permission library to obtain the data scene permission group.

[0087] The target relevance group contains multiple semantic relevances, each of which has a corresponding data scenario permission. The set of data scenario permissions corresponding to each semantic relevance in the target relevance group is denoted as the data scenario permission group.

[0088] S522E: Based on the acquired scene permission configuration instructions, determine the target data scene permission from the data scene permission group.

[0089] Once the scenario permission configuration command is input into the permission configuration model in the vehicle system, the permission configuration model can calculate the semantic relevance between each data scenario permission in the data scenario permission group and the scenario permission configuration command. Then, the data scenario permission corresponding to the highest semantic relevance is taken as the data scenario permission of the target data node and recorded as the target data scenario permission.

[0090] Through the above implementation, a small number of data scenario permissions with high semantic relevance to the target data node are first identified from the data scenario permission library. These are then used as data scenario permission groups, which form the selection range for determining the target data scenario permissions corresponding to the target data node. This reduces the amount of calculation required to determine the semantic relevance between the scenario permission configuration instructions and the data scenario permissions in the data scenario permission library, thereby effectively improving the efficiency of determining the data scenario permissions for vehicle data.

[0091] S523. In response to the target data node being the parent node in the data tree, the target data scene permissions are shared to child nodes at different levels under the parent node.

[0092] S530. In response to the data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively.

[0093] S540. The target vehicle data and the corresponding target data usage permissions and target data scene permissions are simultaneously uploaded to the cloud.

[0094] Example 6 This application provides a method for autonomous management of vehicle data permissions in Embodiment Six, which supplements the method described in Embodiment One. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S610. Set data tags for each vehicle data in the vehicle dataset, and determine the data usage permissions corresponding to each vehicle data based on the data tags and the obtained usage permission configuration instructions, thereby obtaining usage permission information.

[0095] S620. Based on the scene permission configuration instructions corresponding to each of the vehicle data, determine the data scene permissions corresponding to each of the vehicle data from the preset data scene permission library, and obtain scene permission information.

[0096] S630. In response to the data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively.

[0097] S640. The target vehicle data and the corresponding target data usage permissions and target data scene permissions are simultaneously uploaded to the cloud.

[0098] S650. In response to obtaining the target vehicle data usage log sent from the cloud, the target vehicle data usage log is structured to obtain a structured log.

[0099] When the cloud uses the target vehicle data uploaded by the vehicle, it will retain the corresponding usage log, which is called the target vehicle data usage log. In order to facilitate the statistics of the target vehicle data usage logs of the same type of target vehicle data, the target vehicle data usage logs need to be structured according to a predetermined format to obtain structured logs. In this embodiment, the structured log consists of multiple fields, namely: log unique identifier (UUID), data usage request initiation time, data usage completion time, initiating entity (system / personnel / third-party application), time range of vehicle data used, data usage scenario, etc., which are not specifically limited.

[0100] S660. Perform statistics on the structured logs to obtain statistical results.

[0101] The statistical results may include the number of times the initiating entity initiates data usage requests between the time the data usage request is initiated and the time the data usage is completed, the number of different data usage scenarios, etc., without any specific limitations.

[0102] S670. Visualize the statistical results to obtain the visualization results.

[0103] The visualization results are presented in the form of charts or graphs.

[0104] Through the above implementation, the use of logs for target vehicle data can effectively improve the convenience and efficiency of log statistics, and the visualization of statistical results can enhance the readability and intuitiveness of the statistical results.

[0105] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0106] Example 7 Based on the same inventive concept, this embodiment also provides a vehicle data permission autonomous management device for implementing the above-mentioned vehicle data permission autonomous management method. The solution provided by this device is similar to the solution described in the above method. Therefore, the specific limitations of one or more vehicle data permission autonomous management device embodiments provided below can be found in the limitations of the vehicle data permission autonomous management method above, and will not be repeated here.

[0107] In this embodiment, as Figure 2 As shown, a vehicle data access autonomous control device is provided, comprising: The purpose permission configuration module is used to set data tags for each vehicle data in the vehicle dataset, and determine the data purpose permission corresponding to each vehicle data based on the data tags and the obtained purpose permission configuration instructions, so as to obtain the purpose permission information. The scene permission configuration module is used to determine the data scene permissions corresponding to each of the vehicle data from a preset data scene permission library based on the scene permission configuration instructions corresponding to each of the vehicle data, and obtain scene permission information; The permission determination module is used to respond to a data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively. The data upload module is used to synchronously upload the target vehicle data and the corresponding target data usage permissions and target data scene permissions to the cloud.

[0108] Each module in the aforementioned autonomous vehicle data access control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0109] It should be noted that this embodiment sets data tags for each vehicle data in the vehicle dataset, and determines the data usage permissions corresponding to each vehicle data based on the data tags and the obtained usage permission configuration instructions, thus obtaining usage permission information; based on the scene permission configuration instructions corresponding to each vehicle data, it determines the data scene permissions corresponding to each vehicle data from a preset data scene permission library, thus obtaining scene permission information; in response to obtaining a data upload instruction, it determines the target vehicle data corresponding to the data upload instruction, and determines the target data usage permissions and target data scene permissions corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively; and it synchronously uploads the target vehicle data and the corresponding target data usage permissions and target data scene permissions to the cloud. Through the above implementation, users can flexibly issue usage permission configuration instructions and scene permission configuration instructions in the vehicle data permission setting scenarios according to their own wishes, which makes it easy to configure higher usage permissions for private vehicle data, thereby reducing the risk of leakage of private vehicle data; in addition, since users can flexibly set different usage permissions for different types of vehicle data according to usage permission configuration instructions and scene permission configuration instructions, the flexibility of autonomous management of vehicle data permissions can be effectively improved.

[0110] In an optional embodiment, setting data labels for each vehicle data point in the vehicle dataset includes: Determine the metadata for each vehicle data in the vehicle dataset; Based on the metadata of the vehicle data and a preset rule base, the data tags of the vehicle data are determined.

[0111] In an optional embodiment, determining the data tag of the vehicle data based on the metadata of the vehicle data and a preset rule base includes: In response to the fact that the metadata of the vehicle data does not successfully match the corresponding data tag in the preset rule base, the vehicle data is determined to be data to be matched; Calculate the data similarity between the data to be matched and each of the other vehicle data in the vehicle dataset to obtain a similarity set; In response to the vehicle data corresponding to the largest data similarity in the similarity set, there exists a corresponding data tag, and the data tag is shared as the data tag of the data to be matched.

[0112] In an optional embodiment, the step of determining the data scene permissions corresponding to each of the vehicle data from a preset data scene permission library based on the scene permission configuration instructions corresponding to each of the vehicle data, and obtaining scene permission information, includes: A data tree is constructed based on the vehicle data, and the target data node is determined from the data tree; Based on the scene permission configuration instructions corresponding to the target data node, the data scene permissions corresponding to the target data node are determined from the preset data scene permission library to obtain the target data scene permissions; In response to the target data node being the parent node in the data tree, the permissions of the target data scene are shared to child nodes at different levels under the parent node.

[0113] In an optional embodiment, the step of determining the data scene permissions corresponding to the target data node from a preset data scene permission library based on the scene permission configuration instruction corresponding to the target data node, and obtaining the target data scene permissions, includes: Calculate the semantic relevance between the target data node and the permissions of each data scenario in the preset data scenario permission library to obtain an initial relevance set; The initial relevance set is sorted in descending order to obtain the target relevance set; A target relevance group is obtained by determining a preset number of initial relevances from the target relevance set; Determine the data scene permissions corresponding to each initial relevance in the target relevance group in the preset data scene permission library to obtain the data scene permission group; Based on the acquired scene permission configuration instructions, the target data scene permissions are determined from the data scene permission group.

[0114] In an optional embodiment, the vehicle data access control device further includes: The structuring module is used to structure the target vehicle data usage log in response to obtaining the target vehicle data usage log sent from the cloud, so as to obtain the structured log. The statistics module is used to perform statistics on the structured logs and obtain statistical results; The visualization module is used to visualize the statistical results and obtain visualization results.

[0115] Example 8 In this embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows. Figure 3As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a method for autonomous management of vehicle data permissions.

[0116] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present disclosure and does not constitute a limitation on the computer device to which the present disclosure is applied. A specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0117] Example 9 In this embodiment, a computer-readable storage medium is provided, such as... Figure 4 As shown, a computer program is stored thereon, and when the computer program is executed by the processor, it implements the steps in the above-described method embodiments.

[0118] Example 10 In this embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0119] It should be noted that the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and it does not violate public order and good morals. Corresponding operation portals are provided for users to choose to authorize or refuse.

[0120] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this disclosure may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this disclosure may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0121] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0122] The embodiments described above are merely illustrative of several implementations of this disclosure, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent disclosure. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this disclosure, and these all fall within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the appended claims.

Claims

1. A method for autonomous control of vehicle data permissions, characterized in that, include: Data tags are set for each vehicle data in the vehicle dataset. Based on the data tags and the obtained usage permission configuration instructions, the data usage permissions corresponding to each vehicle data are determined to obtain usage permission information. Based on the scene permission configuration instructions corresponding to each of the vehicle data, the data scene permissions corresponding to each of the vehicle data are determined from the preset data scene permission library to obtain scene permission information; In response to a data upload instruction, the target vehicle data corresponding to the data upload instruction is determined, and the target data usage permission and target data scene permission corresponding to the target vehicle data are determined from the usage permission information and the scene permission information, respectively. The target vehicle data, along with the corresponding target data usage permissions and target data scenario permissions, are simultaneously uploaded to the cloud.

2. The method according to claim 1, characterized in that, The step of setting data labels for each vehicle in the vehicle dataset includes: Determine the metadata for each vehicle data in the vehicle dataset; Based on the metadata of the vehicle data and a preset rule base, the data tags of the vehicle data are determined.

3. The method according to claim 2, characterized in that, The process of determining the data tags for the vehicle data based on the metadata of the vehicle data and a preset rule base includes: In response to the fact that the metadata of the vehicle data does not successfully match the corresponding data tag in the preset rule base, the vehicle data is determined to be data to be matched; Calculate the data similarity between the data to be matched and each of the other vehicle data in the vehicle dataset to obtain a similarity set; In response to the vehicle data corresponding to the largest data similarity in the similarity set, there exists a corresponding data tag, and the data tag is shared as the data tag of the data to be matched.

4. The method according to claim 1, characterized in that, The method, based on the scene permission configuration instructions corresponding to each of the vehicle data, determines the data scene permissions corresponding to each of the vehicle data from a preset data scene permission library to obtain scene permission information, including: A data tree is constructed based on the vehicle data, and the target data node is determined from the data tree; Based on the scene permission configuration instructions corresponding to the target data node, the data scene permissions corresponding to the target data node are determined from the preset data scene permission library to obtain the target data scene permissions; In response to the target data node being the parent node in the data tree, the permissions of the target data scene are shared to child nodes at different levels under the parent node.

5. The method according to claim 4, characterized in that, The step of determining the data scene permissions corresponding to the target data node from a preset data scene permission library based on the scene permission configuration instruction corresponding to the target data node, and obtaining the target data scene permissions, includes: Calculate the semantic relevance between the target data node and the permissions of each data scenario in the preset data scenario permission library to obtain an initial relevance set; The initial relevance set is sorted in descending order to obtain the target relevance set; A target relevance group is obtained by determining a preset number of initial relevances from the target relevance set; Determine the data scene permissions corresponding to each initial relevance in the target relevance group in the preset data scene permission library to obtain the data scene permission group; Based on the acquired scene permission configuration instructions, the target data scene permissions are determined from the data scene permission group.

6. The method according to claim 1, characterized in that, Also includes: In response to obtaining the target vehicle data usage logs sent from the cloud, the target vehicle data usage logs are structured to obtain structured logs; Statistical analysis was performed on the structured logs to obtain the statistical results; The statistical results are then visualized to obtain the visualization results.

7. A vehicle data access control autonomous management device, characterized in that, The device includes: The purpose permission configuration module is used to set data tags for each vehicle data in the vehicle dataset, and determine the data purpose permission corresponding to each vehicle data based on the data tags and the obtained purpose permission configuration instructions, so as to obtain the purpose permission information. The scene permission configuration module is used to determine the data scene permissions corresponding to each of the vehicle data from a preset data scene permission library based on the scene permission configuration instructions corresponding to each of the vehicle data, and obtain scene permission information; The permission determination module is used to respond to a data upload instruction, determine the target vehicle data corresponding to the data upload instruction, and determine the target data usage permission and target data scene permission corresponding to the target vehicle data from the usage permission information and the scene permission information, respectively. The data upload module is used to synchronously upload the target vehicle data and the corresponding target data usage permissions and target data scene permissions to the cloud.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images