Resource data interaction method and device and computer equipment

Abstract

The invention relates to a resource data interaction method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: in response to an interaction request for resource data, determining a target interaction address corresponding to the interaction request; wherein the interaction address is used for storing metadata of resource data; the metadata comprises a resource data identifier; the resource data identifier is used for matching a target storage address of the resource data; the resource data corresponds to one or more resource data identifiers; different resource data identifiers are stored in metadata of different interaction addresses; and according to the interaction request, performing corresponding interaction operation on the metadata of the resource data of the target interaction address. By adopting the method, waste of storage space can be avoided.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a resource data interaction method, apparatus, computer equipment, storage medium and computer program product. Background Art

[0002] With the continuous development of scientific research computing, more and more algorithms, models and data have emerged. Before running these algorithms, models and data, it is usually necessary to prepare the corresponding hardware and algorithm resources. However, with the continuous increase of algorithms, models and data, the existing technology often copies the same resource data file to multiple storage addresses in order to facilitate the use of resource data. Although this approach is convenient for access, since the same resource data file is stored in different locations, it greatly increases the storage burden of the system and cannot meet actual needs. Summary of the invention

[0003] Based on this, it is necessary to provide a resource data interaction method, device, computer equipment, computer-readable storage medium and computer program product to address the above technical issues.

[0004] In a first aspect, the present application provides a resource data interaction method. The method comprises:

[0005] In response to an interactive request for resource data, a target interactive address corresponding to the interactive request is determined; wherein the interactive address is used to store metadata of the resource data; the metadata includes a resource data identifier; the resource data identifier is used to match the target storage address of the resource data; the resource data corresponds to one or more metadata; different metadata are stored in different interactive addresses;

[0006] According to the interaction request, a corresponding interaction operation is performed on the metadata of the resource data of the target interaction address.

[0007] In one embodiment, the interaction request includes a storage request, and performing a corresponding interaction operation on metadata of resource data of the target interaction address according to the interaction request includes:

[0008] Using a preset hash strategy, the resource data to be stored is identified to obtain a characteristic value of the resource data to be stored;

[0009] According to the feature value, matching target resource data corresponding to the feature value from a preset resource data set;

[0010] In the case where the target resource data corresponding to the characteristic value is matched, metadata matching the target resource data is established in the storage address.

[0011] In one embodiment, after matching the target resource data corresponding to the feature value from a preset resource data set according to the feature value, the method further includes:

[0012] In the case where the target resource data corresponding to the feature value is not matched, the resource data and the corresponding feature value are stored in the target storage address; wherein the target storage address adopts distributed storage;

[0013] In the target interaction address, metadata corresponding to the resource data is established.

[0014] In one embodiment, the interaction request includes a deletion request, and performing a corresponding interaction operation on metadata of resource data of the target interaction address according to the interaction request includes:

[0015] Deleting metadata of the resource data in the target interaction address, and obtaining the number of resource data identifiers matching the resource data;

[0016] In the case that there is no resource data identifier matching the resource data, the corresponding resource data in the target storage address is deleted.

[0017] In one embodiment, performing a corresponding interaction operation on metadata of resource data of the target interaction address according to the interaction request includes:

[0018] Get the interaction account corresponding to the interaction request;

[0019] According to the interactive account, determining the data interaction authority corresponding to the interactive account;

[0020] In the case where the data interaction permission matches the interaction request type, a corresponding interaction operation is performed on the metadata of the resource data of the target interaction address.

[0021] In one embodiment, the method further comprises:

[0022] Establishing a metadata directory according to the interaction address of the metadata;

[0023] When the interaction request is completed, a corresponding interaction operation is performed on the metadata directory according to the interaction request.

[0024] In a second aspect, the present application also provides a resource data interaction device. The device comprises:

[0025] An interactive response module, used to respond to an interactive request for resource data and determine a target interactive address corresponding to the interactive request; wherein the interactive address is used to store metadata of the resource data; the metadata includes a resource data identifier; the resource data identifier is used to match a target storage address of the resource data; the resource data corresponds to one or more metadata; different metadata are stored in different interactive addresses;

[0026] The data interaction module is used to perform corresponding interaction operations on the metadata of the resource data of the target interaction address according to the interaction request.

[0027] In one embodiment, the interaction request includes a storage request, and the data interaction module includes:

[0028] A feature value determination submodule, used to identify the resource data to be stored by using a preset hash strategy, and obtain the feature value of the resource data to be stored;

[0029] A data matching submodule, used to match target resource data corresponding to the feature value from a preset resource data set according to the feature value;

[0030] The metadata establishment submodule is used to establish metadata matching the target resource data in the storage address when the target resource data corresponding to the characteristic value is matched.

[0031] In one embodiment, the data interaction module further includes:

[0032] A data storage submodule, used for storing the resource data and the corresponding characteristic value in the target storage address when the target resource data corresponding to the characteristic value is not matched; wherein the target storage address adopts distributed storage;

[0033] The metadata establishment submodule is used to establish metadata corresponding to the resource data in the target interaction address.

[0034] In one embodiment, the interaction request includes a deletion request, and the data interaction module includes:

[0035] A metadata deletion submodule, used to delete the metadata of the resource data in the target interaction address and obtain the number of resource data identifiers matching the resource data;

[0036] The resource data deletion submodule is used to delete the corresponding resource data in the target storage address when there is no resource data identifier matching the resource data.

[0037] In one embodiment, the data interaction module includes:

[0038] The account acquisition submodule is used to obtain the interaction account corresponding to the interaction request;

[0039] The permission acquisition submodule is used to determine the data interaction permission corresponding to the interaction account according to the interaction account;

[0040] The data interaction submodule is used to perform corresponding interaction operations on the metadata of the resource data of the target interaction address when the data interaction authority matches the interaction request type.

[0041] In one embodiment, the device further comprises:

[0042] A directory establishment module, used to establish a metadata directory according to the interaction address of the metadata;

[0043] The directory interaction module is used to perform corresponding interaction operations on the metadata directory according to the interaction request when the interaction request is completed.

[0044] In a third aspect, the present application further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the resource data interaction method as described in any one of the embodiments of the present disclosure is implemented.

[0045] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the resource data interaction method as described in any one of the embodiments of the present disclosure is implemented.

[0046] In a fifth aspect, the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the resource data interaction method as described in any one of the embodiments of the present disclosure is implemented.

[0047] The resource data interaction method, device, computer equipment, storage medium and computer program product described above, in response to an interaction request for resource data, determine the target interaction address corresponding to the interaction request; and perform corresponding interaction operations on the metadata of the resource data corresponding to the target interaction address; wherein the resource data is stored at the target storage address, and the metadata includes a resource data identifier, and the resource data identifier can match the target storage address of the resource data; the resource data corresponds to one or more metadata, and different metadata are stored in different interaction addresses. By storing different metadata in different interaction addresses, and matching the target storage address of the resource data with the resource data identifier in the metadata, it is realized that only the resource data needs to be stored at the target storage address, and the metadata corresponding to the resource data is stored in other interaction addresses, so that the storage of resource data in multiple interaction addresses can be completed; without affecting actual use, the waste of storage space caused by the resource data being stored in multiple interaction addresses is avoided, the utilization rate of the memory is effectively improved, and the cost of resource data management is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] FIG1 is a schematic diagram of a flow chart of a resource data interaction method in one embodiment;

[0049] FIG2 is a schematic diagram of a first process of storing resource data in one embodiment;

[0050] FIG3 is a schematic diagram of a second process of storing resource data in one embodiment;

[0051] FIG4 is a schematic diagram of a process of deleting resource data in one embodiment;

[0052] FIG5 is a schematic diagram of a flow chart of resource data interaction in one embodiment;

[0053] FIG6 is a schematic diagram of a process for establishing and maintaining a metadata directory in one embodiment;

[0054] FIG7 is a schematic diagram of a flow chart of a resource data interaction method according to an embodiment;

[0055] FIG8 is a structural block diagram of a resource data interaction device in one embodiment;

[0056] FIG. 9 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0058] In one embodiment, as shown in FIG1 , a resource data interaction method is provided. This embodiment is illustrated by applying the method to a terminal. It is understandable that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0059] Step S100, in response to an interactive request for resource data, determining a target interactive address corresponding to the interactive request; wherein the interactive address is used to store metadata of the resource data; the metadata includes a resource data identifier; the resource data identifier is used to match a target storage address of the resource data; the resource data corresponds to one or more metadata; different metadata are stored in different interactive addresses;

[0060] In an exemplary embodiment, the interactive request for resource data may include copying, moving, deleting, sharing, reading, writing, exporting, etc. of the resource data.

[0061] In an exemplary embodiment, the target storage address of the resource data may include only one address, that is, the resource data only needs to be stored once, thus avoiding the waste of memory due to multiple storages.

[0062] In an exemplary embodiment, a resource data may correspond to one or more resource data identifiers, each resource data identifier may correspond to one or more metadata, and different metadata are stored in different interaction addresses. It can be understood that when copying resource data, metadata can be established only at the target interaction address, wherein the metadata may include the resource data identifier, and the target storage address of the resource data can be matched through the resource data identifier. In another exemplary embodiment, data copying can be performed when the resource data address is unknown. For example, metadata containing the resource data identifier can be copied to achieve the copying of resource data, etc.

[0063] In an exemplary embodiment, the resource data may include block data, object data, mirror data, etc. By customizing data types, resources of various data types are managed.

[0064] In an exemplary embodiment, the metadata may include name, resource type, source, creator, owner, owner authority, resource data identifier, etc.

[0065] Step S200: performing corresponding interaction operations on metadata of resource data of the target interaction address according to the interaction request.

[0066] In an exemplary embodiment, if the interaction request is for storage, the target interaction address may not include metadata of the resource data, and performing corresponding interaction operations on the metadata of the resource data of the target interaction address may include establishing metadata of the resource data, etc.

[0067] In an exemplary embodiment, when the resource data is copied, stored, deleted, etc., the corresponding interactive operation can be performed on the metadata of the resource data at the target interactive address. In another exemplary embodiment, when the resource data at the target storage address is modified, the modification of the resource data can be divided into querying the resource data and modifying the resource data. It can be understood that the above method can complete the query of the resource data, and after the resource data is queried, the operation of modifying the resource data can be performed. In another exemplary embodiment, when the resource data is shared, only the metadata corresponding to the resource data can be shared, and the resource data can be queried and interacted with through the metadata.

[0068] In an exemplary embodiment, when the resource data stored in the interactive address is modified, the association with the old resource data may be deleted, and management with the new resource data may be established.

[0069] In an exemplary embodiment, the actual storage address of the resource data may include multiple addresses, one of which is set as the target storage address for resource data interaction, etc. In another exemplary embodiment, only one storage address, namely the target storage address, may be set for the resource data for resource data interaction, etc.

[0070] In an exemplary embodiment, data within the system may be exported or data outside the system may be imported, etc. The import and export between different areas and workspaces within the system may be processed by operations such as copying, moving, duplicating, and pasting.

[0071] In an exemplary embodiment, in addition to uploading and downloading (files / images) and building (images) to add / acquire resources, for file resources, the logical layer directory structure can be exported to the file system in real time, or file data and directory structure can be imported from the file system; integration with computing resources can be quickly implemented. For image resources, the image warehouse is automatically associated, and the addition, deletion, modification and query of images are completed, which can be flexibly used by computing resources.

[0072] In the above-mentioned resource data interaction method, in response to an interaction request for resource data, a target interaction address corresponding to the interaction request is determined; and a corresponding interaction operation is performed on the metadata of the resource data corresponding to the target interaction address; wherein the resource data is stored at the target storage address, and the metadata includes a resource data identifier, and the resource data identifier can match the target storage address of the resource data; the resource data corresponds to one or more metadata, and different metadata are stored in different interaction addresses. By storing different metadata in different interaction addresses, and matching the target storage address of the resource data with the resource data identifier in the metadata, it is realized that only the resource data needs to be stored at the target storage address, and the metadata corresponding to the resource data is stored in other interaction addresses, so that the storage of resource data in multiple interaction addresses can be completed; without affecting actual use, the waste of storage space caused by the resource data being stored in multiple interaction addresses is avoided, the utilization rate of the memory is effectively improved, and the cost of resource data management is reduced.

[0073] In one embodiment, as shown in FIG. 2 , the interaction request includes a storage request, and the performing of a corresponding interaction operation on the metadata of the resource data of the target interaction address according to the interaction request includes:

[0074] Step S201: using a preset hash strategy, identifying resource data to be stored, and obtaining a characteristic value of the resource data to be stored.

[0075] In an exemplary embodiment, the hash strategy may include a hash algorithm, etc., and the hash strategy may be used to identify the content of the resource data file to be stored, obtain a unique hash value of the resource data file, and determine whether the resource data file to be stored has been stored in the system, etc.

[0076] Step S202: According to the feature value, match the target resource data corresponding to the feature value from a preset resource data set.

[0077] In an exemplary embodiment, the resource data set may include a set of all resource data and corresponding feature values; matching is performed in the resource data set by utilizing the feature values, etc.

[0078] Step S203: when the target resource data corresponding to the characteristic value is matched, metadata matching the target resource data is established in the storage address.

[0079] In an exemplary embodiment, when the target resource data corresponding to the characteristic value is matched, it can include that the resource data has been stored in the system and is the target resource data, so metadata matching the target resource data can be established in the storage address, etc. It can be understood that the metadata matching the target resource data can include metadata containing the resource data identifier matching the target resource data, etc.

[0080] In an exemplary embodiment, the file resource calculates the hash value obtained by the data, performs hash storage, and ensures that a copy of the same data value is retained by comparing the hash values.

[0081] In this embodiment, the characteristic value of the resource data to be stored is determined through the hash strategy, and the characteristic value is used to determine whether the resource data has been stored. If the resource data has been stored, the corresponding metadata is established at the storage address. The resource data can be identified through the hash strategy and the characteristic value. At the same time, if the characteristic value matches, the metadata matching the resource data is established in the storage address, avoiding data redundancy caused by storing resource data in multiple addresses, improving the utilization rate of storage space, and further improving the efficiency of resource data processing.

[0082] In one embodiment, as shown in FIG3 , after matching the target resource data corresponding to the feature value from a preset resource data set according to the feature value, the method further includes:

[0083] Step S211, when the target resource data corresponding to the feature value is not matched, the resource data and the corresponding feature value are stored in the target storage address; wherein the target storage address adopts distributed storage.

[0084] In an exemplary embodiment, the target resource data not matching the characteristic value may include that the resource data has not been stored in the storage address, and thus the resource data may be stored in the target storage address.

[0085] In an exemplary embodiment, distributed storage can realize the interaction of multiple resource data at the same time to improve the high availability and fault tolerance of the resource data.

[0086] Step S212: creating metadata corresponding to the resource data in the target interaction address.

[0087] In an exemplary embodiment, the file resource is hashed and stored by calculating the hash value, that is, the stored metadata is randomly assigned to a storage address, so it is necessary to establish metadata corresponding to the resource data at the target interaction address.

[0088] In an exemplary embodiment, the resource data can be stored in a high-performance distributed storage system. It can be understood that the characteristic values ​​of the data can be used to store the resource data in the corresponding distributed storage system. Therefore, in the actual use process, the resource data has been stored in the distributed system, but it is still not stored in the target interaction address. Therefore, it is also necessary to store the resource data in the target interaction address.

[0089] In this embodiment, when the target resource data corresponding to the characteristic value is not matched, the resource data is stored in the target storage address, and metadata corresponding to the resource data is established in the target interaction address. When the target resource data corresponding to the characteristic value is not matched, the resource data and its characteristic value are stored in the target storage address using distributed storage, which can significantly improve the flexibility and reliability of data management. Distributed storage not only allows data to be stored redundantly on multiple nodes, thereby enhancing the availability and fault tolerance of data, but also can achieve higher performance and shorten access delays through load balancing. In addition, the distributed storage architecture supports horizontal expansion, can easily cope with the growing amount of data, and promote the scalability of the system. Metadata is established in the target interaction address, corresponding to the rapid access and efficient management of characteristic values ​​and resource data, further ensuring the optimal use of resources and the overall performance optimization of the system.

[0090] In one embodiment, as shown in FIG. 4 , the interaction request includes a deletion request, and the corresponding interaction operation is performed on the metadata of the resource data of the target interaction address according to the interaction request, including:

[0091] Step S221, deleting the metadata of the resource data in the target interaction address, and obtaining the number of resource data identifiers matching the resource data.

[0092] Step S222: if there is no resource data identifier matching the resource data, delete the corresponding resource data in the target storage address.

[0093] In an exemplary embodiment, the number of resource data identifiers of resource data can be checked, and the number of resource data identifiers can be modified when deleting or adding resource data identifiers. For example, when copying resource data, a new resource data identifier can be created and the amount of resource data identifier data can be increased by one. When deleting the metadata of resource data in the target interaction address, the number of resource data identifiers can be reduced by one, etc. When the number of resource data identifiers is zero, it means that no metadata is associated with the resource data, that is, the resource data is invalid, so the resource data of the target storage address is deleted, etc. It can be understood that the number of resource data identifiers corresponding to the data object is the life cycle of the resource data. When the resource data identifier is zero, there is no reference, that is, the resource data is invalid, etc.

[0094] In an exemplary embodiment, the interaction request may include modifying the resource data identifier, may include deleting the old resource data identifier, generating a new resource data identifier, etc. It can be understood that modifying the resource data identifier includes deleting the resource data identifier, therefore, when modifying the resource data identifier, it may also include obtaining the number of resource data identifiers matching the resource data, etc.

[0095] In this embodiment, by deleting the resource data metadata in the target interaction address and obtaining the number of resource data identifiers that match it, useless information in the system can be effectively cleaned up and the data management process can be optimized. If it is found after deletion that there is no resource data identifier that matches the resource data, this means that the resource is no longer needed, and the corresponding resource data can be further completely deleted from the target storage address. This process not only reduces the waste of storage space, but also improves the performance and response speed of the system. At the same time, regular cleaning of invalid data helps maintain the neatness and consistency of the data, ensuring that the system always remains efficient and reliable during operation.

[0096] In one embodiment, as shown in FIG5 , performing corresponding interaction operations on metadata of resource data of the target interaction address according to the interaction request includes:

[0097] Step S101, obtaining an interaction account corresponding to an interaction request.

[0098] Step S102: determining the data interaction authority corresponding to the interaction account according to the interaction account.

[0099] Step S103, when the data interaction permission matches the interaction request type, a corresponding interaction operation is performed on the metadata of the resource data of the target interaction address.

[0100] In an exemplary embodiment, when interacting with resource data, you can first log in to a corresponding interaction account, and interact with the resource data through the interaction account.

[0101] In an exemplary embodiment, the data interaction permissions may include read, write, copy, move, delete, share, download, export, authorize, etc. In another exemplary embodiment, the data interaction permissions may also include that certain resource data has certain permissions, etc. For example, resource data may be divided into core resources and non-core resources, and core resources may be read but not written.

[0102] In an exemplary embodiment, the permissions may include authorization, etc., and specifically may include that an administrator can grant certain permissions to a user's account. For example, the administrator has all permissions, but the user does not have sharing permissions to resource data. The administrator can change the user's permissions, grant the user sharing permissions, etc.

[0103] In an exemplary embodiment, when the data interaction authority does not match the interaction request, a reminder may be given that the interaction account does not have the authority.

[0104] In an exemplary embodiment, the setting of permissions includes setting metadata when establishing metadata of resource data, setting certain resource data to be interacted with by certain accounts, and corresponding interactive operations, for example, setting a metadata to be interacted with only by administrators, or setting a metadata to be interacted with by administrators and users, but users only have read permissions. It can be understood that the user here can refer to a type of account, etc.

[0105] In this embodiment, by obtaining the interaction account corresponding to the interaction request, the permissions of the account can be clarified, thereby ensuring that only users with corresponding data interaction permissions can operate the resource data of the target interaction address. This permission verification mechanism effectively improves the security and standardization of data interaction, avoids the risks brought by unauthorized access, and ensures the security and integrity of data. At the same time, this process can improve the efficiency of interaction and ensure the stability and efficiency of information flow.

[0106] In one embodiment, as shown in FIG6 , the method further includes:

[0107] Step S301: Create a metadata directory according to the metadata interaction address.

[0108] In an exemplary embodiment, the data directory may include the parent object and the subordinate object of the metadata, etc. It is understandable that the metadata and the parent object may be one-to-one, the metadata and the subordinate object may be one-to-many, etc. Specifically, a piece of metadata may include sales, the parent object may include a specific product, and the subordinate object may include a corresponding year, wherein the year may be multiple, and the product corresponding to the sales is only one, etc. Specifically, the metadata forms a tree structure association by recording the parent object (1:1) and the subordinate object (1:m), thereby realizing a directory structure consistent with the file system, etc.

[0109] In an exemplary embodiment, when a folder is imported from outside the system, the system will build a consistent metadata hierarchy structure based on the imported folder structure. In another exemplary embodiment, the metadata directory can be exported to more clearly observe the metadata or facilitate the search for corresponding metadata.

[0110] In an exemplary embodiment, resource data may be hashed and stored through a calculated hash value, so there is no logical structure between storage addresses of resource data, and therefore a logical structure between metadata needs to be established.

[0111] Step S302: When the interaction request is completed, a corresponding interaction operation is performed on the metadata directory according to the interaction request.

[0112] In an exemplary embodiment, after interacting with metadata, new metadata may be generated or some metadata may be deleted. Therefore, after completing the interaction request, it is necessary to perform corresponding interaction operations on the metadata directory to ensure the consistency of the metadata directory.

[0113] In this embodiment, a metadata directory is established, and when an interactive request is completed, a corresponding interactive operation is performed on the metadata directory. Establishing a metadata directory can effectively organize and manage metadata and provide a clear structure and retrieval method. After completing an interactive request, performing a corresponding interactive operation on the metadata directory according to the request can achieve efficient data access and processing and ensure the accuracy and consistency of information.

[0114] In an exemplary embodiment, the resource data interaction method may be implemented as shown in the flowchart of FIG. 7 , and specifically includes:

[0115] Step S901, uploading resources; specifically, the resources may include data to be stored and a storage address; wherein the resources may include different types of resources, such as block data, object data, mirror data, etc.;

[0116] Step S902, using hashing to obtain a characteristic value of the resource data; specifically, it may include using a hashing algorithm to identify the resource data to obtain a corresponding characteristic value;

[0117] Step S903, matching the feature value from the resource data set; if matched, proceed to step S904; if not matched, proceed to step S905;

[0118] Step S904, creating metadata in the storage address, the metadata including the identifier of the resource data matched from the resource data set;

[0119] Step S905: Add the resource data to the distributed storage system and create metadata in the storage address, where the metadata includes an identifier of the resource data.

[0120] In an exemplary embodiment, metadata may be stored in a distributed database for quick search, and it is understood that the distributed database supports multi-dimensional, range, fuzzy and other combination queries, etc. The query dimensions may include name, type, creator, owner, tag, time, etc.

[0121] In an exemplary embodiment, when sharing resource data, metadata corresponding to the resource data may be shared. It is understood that the metadata shared in this way is controlled by the sharer, and the sharing of the metadata may be withdrawn. In another exemplary embodiment, when sharing household resources, the resource data may be directly shared. It is understood that when sharing in this way, the sharer cannot control and cannot withdraw the metadata.

[0122] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0123] Based on the same inventive concept, the embodiment of the present application also provides a resource data interaction device for implementing the resource data interaction method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiment of one or more resource data interaction devices provided below can refer to the limitations of the resource data interaction method above, and will not be repeated here.

[0124] In one embodiment, as shown in FIG8 , a resource data interaction device 100 is provided, including: an interaction response module 101 and a data interaction module 102, wherein:

[0125] An interactive response module, used to respond to an interactive request for resource data and determine a target interactive address corresponding to the interactive request; wherein the interactive address is used to store metadata of the resource data; the metadata includes a resource data identifier; the resource data identifier is used to match a target storage address of the resource data; the resource data corresponds to one or more metadata; different metadata are stored in different interactive addresses;

[0126] The data interaction module is used to perform corresponding interaction operations on the metadata of the resource data of the target interaction address according to the interaction request.

[0127] In one embodiment, the interaction request includes a storage request, and the data interaction module includes:

[0128] A feature value determination submodule, used to identify the resource data to be stored by using a preset hash strategy, and obtain the feature value of the resource data to be stored;

[0129] A data matching submodule, used to match target resource data corresponding to the feature value from a preset resource data set according to the feature value;

[0130] The metadata establishment submodule is used to establish metadata matching the target resource data in the storage address when the target resource data corresponding to the characteristic value is matched.

[0131] In one embodiment, the data interaction module further includes:

[0132] A data storage submodule, used for storing the resource data and the corresponding characteristic value in the target storage address when the target resource data corresponding to the characteristic value is not matched; wherein the target storage address adopts distributed storage;

[0133] The metadata establishment submodule is used to establish metadata corresponding to the resource data in the target interaction address.

[0134] In one embodiment, the interaction request includes a deletion request, and the data interaction module includes:

[0135] A metadata deletion submodule, used to delete the metadata of the resource data in the target interaction address and obtain the number of resource data identifiers matching the resource data;

[0136] The resource data deletion submodule is used to delete the corresponding resource data in the target storage address when there is no resource data identifier matching the resource data.

[0137] In one embodiment, the data interaction module includes:

[0138] The account acquisition submodule is used to obtain the interaction account corresponding to the interaction request;

[0139] The permission acquisition submodule is used to determine the data interaction permission corresponding to the interaction account according to the interaction account;

[0140] The data interaction submodule is used to perform corresponding interaction operations on the metadata of the resource data of the target interaction address when the data interaction authority matches the interaction request type.

[0141] In one embodiment, the device further comprises:

[0142] A directory establishment module, used to establish a metadata directory according to the interaction address of the metadata;

[0143] The directory interaction module is used to perform corresponding interaction operations on the metadata directory according to the interaction request when the interaction request is completed.

[0144] Each module in the resource data interaction device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0145] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG9. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store metadata. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for interacting with resource data is implemented.

[0146] Those skilled in the art will understand that the structure shown in FIG. 9 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

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

[0148] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application 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), magnetoresistive 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. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0149] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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.

[0150] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A resource data interaction method, characterized in that: The method comprises: In response to an interactive request for resource data, a target interactive address corresponding to the interactive request is determined; wherein the interactive address is used to store metadata of the resource data; the metadata includes a resource data identifier; the resource data identifier is used to match the target storage address of the resource data; the resource data corresponds to one or more metadata; different metadata are stored in different interactive addresses; According to the interaction request, a corresponding interaction operation is performed on the metadata of the resource data of the target interaction address.

2. The method according to claim 1, characterized in that: The interaction request includes a storage request, and the performing corresponding interaction operations on metadata of resource data of the target interaction address according to the interaction request includes: Using a preset hash strategy, the resource data to be stored is identified to obtain a characteristic value of the resource data to be stored; According to the feature value, matching target resource data corresponding to the feature value from a preset resource data set; In the case where the target resource data corresponding to the characteristic value is matched, metadata matching the target resource data is established in the storage address.

3. The method according to claim 2, characterized in that After matching the target resource data corresponding to the feature value from a preset resource data set according to the feature value, the method further includes: In the case where the target resource data corresponding to the feature value is not matched, the resource data and the corresponding feature value are stored in the target storage address; wherein the target storage address adopts distributed storage; In the target interaction address, metadata corresponding to the resource data is established.

4. The method according to claim 1, characterized in that: The interaction request includes a deletion request, and the performing corresponding interaction operations on metadata of resource data of the target interaction address according to the interaction request includes: Deleting metadata of the resource data in the target interaction address, and obtaining the number of resource data identifiers matching the resource data; In the case that there is no resource data identifier matching the resource data, the corresponding resource data in the target storage address is deleted.

5. The method according to claim 1, characterized in that The performing corresponding interaction operations on metadata of resource data of the target interaction address according to the interaction request includes: Get the interaction account corresponding to the interaction request; According to the interactive account, determining the data interaction authority corresponding to the interactive account; In the case where the data interaction permission matches the interaction request type, a corresponding interaction operation is performed on the metadata of the resource data of the target interaction address.

6. The method according to claim 1, characterized in that The method further comprises: Establishing a metadata directory according to the interaction address of the metadata; When the interaction request is completed, a corresponding interaction operation is performed on the metadata directory according to the interaction request.

7. A resource data interaction device, characterized in that: The device comprises: An interactive response module, used to respond to an interactive request for resource data and determine a target interactive address corresponding to the interactive request; wherein the interactive address is used to store metadata of the resource data; the metadata includes a resource data identifier; the resource data identifier is used to match a target storage address of the resource data; the resource data corresponds to one or more metadata; different metadata are stored in different interactive addresses; The data interaction module is used to perform corresponding interaction operations on the metadata of the resource data of the target interaction address according to the interaction request.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

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

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

Images