Data sharing method and electronic equipment

Abstract

The embodiment of the invention provides a data sharing method and electronic equipment, and the method comprises the steps: determining target objects, target positions and second user identifiers according to a sharing request of a first user in a cloud storage environment and a storage scene of binary object data, thereby obtaining first data bodies and first metadata corresponding to the target objects, a basis is provided for subsequently establishing metadata at the target position according to the identifier of the second user, and the first user can access the first data through the initial metadata. The target position of the first data needs to be used, new second metadata is established, and the second metadata comprises the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata, and multiplexing of the data ontology is achieved; according to the method, the situation that multiple first data bodies are repeatedly stored in the cluster is avoided, so that waste of storage resources is reduced, the storage efficiency is improved, and in conclusion, the storage resource occupation situation in the object data storage process is optimized.

Description

Technical Field

[0001] The present application relates to cloud storage technology, and more particularly to a data sharing method and electronic device. Background Art

[0002] In a cloud storage environment, users can complete data storage sharing through a storage service interface, so that first data can be migrated from a source storage bucket to a target storage bucket to achieve data storage. In a multi-cloud tenant environment, this data storage method will be frequently involved.

[0003] However, this type of data sharing method, which uses a preset object storage service interface to perform data sharing, may cause redundant storage, resulting in multiple copies of the same first data being stored repeatedly in the cluster, thereby resulting in a waste of storage resources. At the same time, as the amount of first data increases, the time used for data storage will also increase, thereby also resulting in the occupancy of storage resources and a decrease in storage efficiency. Therefore, a data sharing method can be provided to optimize the storage resource occupancy of the object data storage process. Summary of the invention

[0004] The embodiments of the present application provide a data sharing method and an electronic device to solve the problem of large storage resource occupation in the current data sharing method.

[0005] In a first aspect, an embodiment of the present application provides a data sharing method, the method comprising:

[0006] determining, according to a sharing request of a first user, a target object, a target location, and an identifier of a second user, wherein the target object includes first data and first metadata, and the first user can access the first data through the first metadata;

[0007] Second metadata is generated at the target location according to the first metadata, where the second metadata includes a storage address of the first data and an identifier of the second user, so that the second user can access the first data through the second metadata.

[0008] By determining the target object, target location, and second user identifier in a cloud storage environment according to the sharing request of the first user, the first data entity and the first metadata corresponding to each target object are obtained, providing a basis for subsequently establishing metadata at the target location according to the identifier of the second user, and the first user can access the first data through the initial metadata. At the target location where the first data is needed, new second metadata is established, and the second metadata includes the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata, realizing the reuse of the data entity, avoiding the situation where multiple copies of the same first data entity are repeatedly stored in the cluster, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0009] As an optional implementation manner, the first metadata further includes an index of a storage bucket where the first metadata is located, and generating the second metadata according to the first metadata at the target location includes:

[0010] The second metadata also includes an index of the storage bucket where the second metadata is located.

[0011] As an optional implementation manner, the first metadata further includes user authentication information of the first user, and generating second metadata according to the first metadata at the target location includes:

[0012] The second metadata generates user authentication information of the second user according to the identifier of the second user.

[0013] As an optional implementation manner, the first metadata further includes the size of the first data, and generating the second metadata according to the first metadata at the target location includes:

[0014] The first data size of the second metadata is the same as the first data size of the first metadata.

[0015] Therefore, by realizing the reuse of the data body in the process of generating the second metadata, the correspondence and validity between the metadata and the user are further ensured, the convenience of subsequent data operations through the metadata is improved, and the situation where multiple copies of the same first data body are stored repeatedly in the cluster is avoided, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0016] As an optional implementation, the method further includes:

[0017] The correspondence between the second metadata, the identifier of the first data and the identifier of the second user is stored in a metadata storage pool.

[0018] After completing the establishment of the second metadata, the correspondence between the second metadata, the identifier of the first data and the identifier of the second user can also be synchronized to the metadata storage pool. When the second user wants to access the first data, the management device can find the corresponding second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user, and then go to the first data address in the second metadata to access the first data, thereby facilitating subsequent calls by the corresponding user.

[0019] As an optional implementation, the method further includes:

[0020] Obtaining an access request of the second user, where the access request includes an identifier of the first data and an identifier of the second user;

[0021] determining the second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user;

[0022] The first data is accessed according to the storage address of the first data of the second metadata.

[0023] In a scenario where the second user needs to use the first data, an access request from the second user is obtained, and second metadata is determined in a metadata storage pool through an identifier of the first data and an identifier of the second user in the access request, so that the second user can access the first data through the second metadata, thereby realizing the storage and call of metadata and simplifying the operation and interaction of users when using data.

[0024] As an optional implementation, the method further includes:

[0025] Performing metadata consistency check and / or integrity check according to the first metadata and the second metadata;

[0026] storing the correspondence between the second metadata, the identifier of the second data, and the identifier of the second user in a metadata storage pool, including:

[0027] If it is determined that the second metadata meets the corresponding consistency condition and integrity condition, storing the correspondence between the second metadata, the identifier of the second data and the identifier of the second user in a metadata storage pool;

[0028] If it is determined that the second metadata does not meet the corresponding consistency condition or integrity condition, the second metadata is corrected.

[0029] This implementation manner performs metadata consistency check and / or integrity check based on the established second metadata and related information of the first metadata after establishing the second metadata. When the second metadata meets the corresponding consistency condition and / or integrity condition, the corresponding relationship between the second metadata, the identifier of the second data and the identifier of the second user is synchronized to the metadata storage pool to complete the entire metadata establishment cycle. When the corresponding conditions are not met, the second metadata is re-established or the related information of the second metadata is corrected, thereby ensuring data security and ensuring data validity when data is accessed or processed at the first data location.

[0030] As an optional implementation manner, determining the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes:

[0031] The sharing request includes the target object, the target location, and the identifier of the second user. The target object, the target location, and the identifier of the second user are obtained according to the sharing request.

[0032] As an optional implementation manner, determining the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes:

[0033] The sharing request includes the identifier of the first user, the identifier of the first data, the target location, and the identifier of the second user;

[0034] Obtaining the target location and an identifier of the second user according to the sharing request;

[0035] determining the first metadata in the metadata storage pool according to the identifier of the first user and the identifier of the first data;

[0036] An object corresponding to the first metadata is determined as the target object.

[0037] This implementation enables the corresponding user to directly obtain the corresponding target object, target location or identification of the second user and other information according to the sharing request through the management device, thereby improving the efficiency of data interaction during the data sharing process.

[0038] In a second aspect, an embodiment of the present application provides a data sharing device, the device comprising:

[0039] A determination module, configured to determine a target object, a target location, and an identifier of a second user according to a sharing request of a first user, wherein the target object includes first data and first metadata, and the first user can access the first data through the first metadata;

[0040] A processing module is used to generate second metadata at the target location according to the first metadata, wherein the second metadata includes a storage address of the first data and an identifier of the second user, so that the second user can access the first data through the second metadata.

[0041] In a cloud storage environment, in a storage scenario of binary object data, the target object, target location, and second user identifier are determined according to the sharing request of the first user, thereby obtaining the first data entity and the first metadata corresponding to each target object, providing a basis for subsequently establishing metadata at the target location according to the identifier of the second user, and the first user can access the first data through the initial metadata. At the target location where the first data is needed, new second metadata is established, and the second metadata includes the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata, realizing the reuse of the data entity, avoiding the situation where multiple copies of the same first data entity are repeatedly stored in the cluster, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0042] As an optional implementation manner, the first metadata further includes an index of a storage bucket where the first metadata is located, and the specific manner in which the processing module generates the second metadata at the target location according to the first metadata includes:

[0043] The second metadata also includes an index of the storage bucket where the second metadata is located.

[0044] As an optional implementation manner, the first metadata further includes user authentication information of the first user, and the specific manner in which the processing module generates the second metadata at the target location according to the first metadata includes:

[0045] The second metadata generates user authentication information of the second user according to the identifier of the second user.

[0046] As an optional implementation manner, the first metadata further includes the size of the first data, and the specific manner in which the processing module generates the second metadata at the target location according to the first metadata includes:

[0047] The first data size of the second metadata is the same as the first data size of the first metadata.

[0048] Therefore, by realizing the reuse of the data body in the process of generating the second metadata, the correspondence and validity between the metadata and the user are further ensured, the convenience of subsequent data operations through the metadata is improved, and the situation where multiple copies of the same first data body are stored repeatedly in the cluster is avoided, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0049] As an optional implementation manner, the processing module is further used for:

[0050] The correspondence between the second metadata, the identifier of the first data and the identifier of the second user is stored in a metadata storage pool.

[0051] After completing the establishment of the second metadata, the correspondence between the second metadata, the identifier of the first data and the identifier of the second user can also be synchronized to the metadata storage pool. When the second user wants to access the first data, the management device can find the corresponding second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user, and then go to the first data address in the second metadata to access the first data, thereby facilitating subsequent calls by the corresponding user.

[0052] As an optional implementation manner, the processing module is further used for:

[0053] Obtaining an access request of the second user, where the access request includes an identifier of the first data and an identifier of the second user;

[0054] determining the second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user;

[0055] The first data is accessed according to the storage address of the first data of the second metadata.

[0056] In a scenario where the second user needs to use the first data, an access request from the second user is obtained, and second metadata is determined in a metadata storage pool through an identifier of the first data and an identifier of the second user in the access request, so that the second user can access the first data through the second metadata, thereby realizing the storage and call of metadata and simplifying the operation and interaction of users when using data.

[0057] As an optional implementation manner, the processing module is further used for:

[0058] Performing metadata consistency check and / or integrity check according to the first metadata and the second metadata;

[0059] storing the correspondence between the second metadata, the identifier of the second data, and the identifier of the second user in a metadata storage pool, including:

[0060] If it is determined that the second metadata meets the corresponding consistency condition and integrity condition, storing the correspondence between the second metadata, the identifier of the second data and the identifier of the second user in a metadata storage pool;

[0061] If it is determined that the second metadata does not meet the corresponding consistency condition or integrity condition, the second metadata is corrected.

[0062] This implementation manner performs metadata consistency check and / or integrity check based on the established second metadata and related information of the first metadata after establishing the second metadata. When the second metadata meets the corresponding consistency condition and / or integrity condition, the corresponding relationship between the second metadata, the identifier of the second data and the identifier of the second user is synchronized to the metadata storage pool to complete the entire metadata establishment cycle. When the corresponding conditions are not met, the second metadata is re-established or the related information of the second metadata is corrected, thereby ensuring data security and ensuring data validity when data is accessed or processed at the first data location.

[0063] As an optional implementation manner, the specific manner in which the determination module determines the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes:

[0064] The sharing request includes the target object, the target location, and the identifier of the second user. The target object, the target location, and the identifier of the second user are obtained according to the sharing request.

[0065] As an optional implementation manner, the specific manner in which the determination module determines the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes:

[0066] The sharing request includes the identifier of the first user, the identifier of the first data, the target location, and the identifier of the second user;

[0067] Obtaining the target location and an identifier of the second user according to the sharing request;

[0068] determining the first metadata in the metadata storage pool according to the identifier of the first user and the identifier of the first data;

[0069] An object corresponding to the first metadata is determined as the target object.

[0070] This implementation enables the corresponding user to directly obtain the corresponding target object, target location or identification of the second user and other information according to the sharing request through the management device, thereby improving the efficiency of data interaction during the data sharing process.

[0071] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0072] The memory stores computer-executable instructions;

[0073] The processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect.

[0074] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect.

[0075] In a fifth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and at least one processor executes the computer program to implement the method described in the first aspect.

[0076] The data sharing method and electronic device provided by the present application, in a cloud storage environment, in a storage scenario of binary object data, determine the target object, target location, and second user identification according to the sharing request of the first user, thereby obtaining the first data body and first metadata corresponding to each target object, providing a basis for subsequently establishing metadata at the target location according to the identification of the second user, and the first user can access the first data through the initial metadata. At the target location where the first data is needed, new second metadata is established, the second metadata includes the storage address of the first data and the identification of the second user, so that the second user can access the first data through the second metadata, realizing the reuse of the data body, avoiding the situation where multiple copies of the same first data body are repeatedly stored in the cluster, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0078] Figure 1 It is a schematic diagram of an application scenario of a data sharing method disclosed in an embodiment of the present application;

[0079] Figure 2 It is a flowchart of a data sharing method disclosed in an embodiment of the present application;

[0080] Figure 3 It is a schematic diagram of an application scenario of a data sharing method disclosed in an embodiment of the present application;

[0081] Figure 4 It is a schematic diagram of an application scenario of a data sharing method disclosed in an embodiment of the present application;

[0082] Figure 5 It is a structural schematic diagram of a data sharing method and device disclosed in an embodiment of the present application;

[0083] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0084] The above-mentioned drawings have shown clear embodiments of the present application, which will be described in more detail hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0085] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0086] First, some terms that may be involved are explained:

[0087] Bucket: Each bucket has a unique name, which is used to identify and access the bucket in the cloud storage service. Each bucket can store at least one object, and different buckets can be located on the same storage device or on different storage devices.

[0088] Object Storage: A data storage model that uses objects as the basic storage unit and stores data in the form of objects. An object consists of a unique identifier (such as an object ID or key), metadata, and data. An object can be any type of data, such as text files, images, videos, etc.

[0089] In some feasible implementations, the metadata may include data size, data storage location, object storage location, user authentication information, and an index list of the bucket where the associated object is located. The data stored by the user may be divided into multiple segments of data, each object corresponds to a segment of data, and the different objects corresponding to these multiple data can be regarded as associated objects.

[0090] S3 (Simple Storage Service) is an object storage service.

[0091] In a cloud storage environment, when the first user shares data with the second user, the S3 (Simple Storage Service) method is usually used. It is necessary to copy a complete object corresponding to the first user in the second user's designated storage bucket. The object includes the aforementioned identifier, metadata, and data to achieve data sharing. Correspondingly, in this scenario, if data deletion is currently required at the second user, the complete object is directly deleted at the second user, resulting in a waste of storage resources and an increase in response time. In the scenario of multiple cloud tenants, if the transmission of such user data is implemented through the above-mentioned S3 solution, it may cause redundant storage, that is, multiple copies of the same file are stored repeatedly in the cluster, resulting in a waste of storage resources.

[0092] In summary, this type of data sharing method, which uses a preset object storage service interface to share data, may cause redundant storage, resulting in multiple copies of the same first data being stored repeatedly in the cluster, thereby wasting storage resources. At the same time, as the amount of data corresponding to the first data increases, the time used for data storage will also increase, which will also lead to the occupation of storage resources and a decrease in storage efficiency. Therefore, a data sharing method can be provided to optimize the storage resource occupation during the object data storage process.

[0093] See also Figure 1 , Figure 1 This is a schematic diagram of an application scenario of a data sharing method disclosed in an embodiment of the present application. A storage bucket may include multiple objects, and an object may include a data entity and metadata. To achieve data reuse, the embodiment of the present application provides a method that is different from the method of fully processing object data, but achieves data sharing and reuse through the establishment of metadata and the reuse of reference relationships.

[0094] The objects involved in the embodiments of the present application can realize the corresponding data sharing method through the management device, the management device is connected to the storage device, and there are multiple storage buckets in the storage device, each storage bucket is set corresponding to each user, and the migration of the reference relationship is realized through the reconstruction of metadata, thereby realizing the reuse of the original data Data in the data sharing process. It is understandable that the management device can also be connected to multiple storage devices, and the storage bucket A and the storage bucket B are respectively located in two different storage devices.

[0095] The management device and the storage device may be separate devices. In addition, the management device may also be located in the storage device. As an integrated device, when the management device is located in the storage device, the metadata storage pool in the management device is also stored in the storage device.

[0096] For example, consider A in the figure as the first user and B as the second user. When the second user needs to use the corresponding data, they can share the same copy of the data Data during the data storage process. At the storage bucket corresponding to the second user, a copy of the metadata can be rebuilt based on the metadata of the target object in the storage bucket corresponding to the first user and the reference relationship corresponding to the metadata. The first user and the second user are respectively connected to the storage device through the management device to process the object data in the corresponding storage bucket and maintain the corresponding metadata to access the same data Data through their respective metadata. Therefore, data storage and reuse are achieved by reconstructing the metadata. At the same time, when the data needs to be added, deleted, modified, or checked at the corresponding user location, the corresponding operations can also be achieved by processing the corresponding metadata. Maintenance and authentication are performed at each user's location to achieve distributed data processing, which reduces the waste of storage resources while improving the efficiency of data storage and processing.

[0097] Therefore, the technical concept of the present application is to determine the target object, target location, and second user identifier according to the sharing request of the first user in the storage scenario of binary object data in a cloud storage environment, thereby obtaining the first data entity and the first metadata corresponding to each target object, and providing a basis for subsequently establishing metadata at the target location according to the identifier of the second user, so that the first user can access the first data through the initial metadata. At the target location where the first data is needed, new second metadata is established, and the second metadata includes the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata, realizing the reuse of the data entity, avoiding the situation where multiple copies of the same first data entity are stored repeatedly in the cluster, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0098] See also Figure 2 , Figure 2Schematic diagram of a data sharing method disclosed in the embodiment of the present application. Figure 2 As shown, the method includes:

[0099] S101, determining a target object, a target location, and an identifier of a second user according to a sharing request of a first user, wherein the target object includes first data and first metadata;

[0100] The first user can send a sharing request to the management device to share the first data with the second user, and the management device can receive the sharing request of the first user. The target object includes the first data and the first metadata, and the target object can be one object or multiple objects. When there are multiple target objects, each object includes one first data and one first metadata; the target location is a location that the second user can access, and the storage bucket where the target location is located and the storage bucket where the target object is located can be the same or different.

[0101] The first metadata may include the storage address of the first data and the identifier of the first user. The first user can access the first data through the first data storage address in the first metadata. In a possible implementation, the first user needs to access the first data, and the first data may be located in multiple objects. A metadata storage pool is stored in the management device, and the metadata storage pool includes the first metadata, the first data identifier, and the correspondence between the first user. When the first user wants to access the first data, the management device can receive the data identifier sent by the first user, find all the metadata information in the metadata storage pool according to the file identifier and user information, and then access the first data at the first data address in the corresponding metadata. Exemplarily, the identifier of the first data can be the file name of the first data.

[0102] The sharing request includes the identifier of the second user, and the management device may directly obtain the identifier of the second user according to the sharing request.

[0103] The sharing request may also include an identifier of the target object, and the management device may directly obtain the target object based on the sharing request. Alternatively, the sharing request may include an identifier of the first user, a target location, and an identifier of the second user, and the management device may determine that the target object is all objects owned by the first user based on the identifier of the first user. Alternatively, the sharing request may include an identifier of a storage bucket, and the management device may determine that the target object is all objects stored in the storage bucket based on the identifier of the storage bucket. Alternatively, the sharing request may include an identifier of the first data and an identifier of the first user, and the management device may search the metadata storage pool for the first metadata based on the identifier of the first data, thereby determining the object corresponding to the first metadata as the target object.

[0104] The sharing request may also include a target location, and the management device may directly obtain the target location according to the sharing request. Alternatively, the sharing request may not include the target location, and the management device may determine a free storage space in a storage bucket accessible to the second user according to the identifier of the second user.

[0105] Optionally, the first metadata also includes one or more of a bucket index, user authentication information (such as an access key (AccessKey ID, AK) and a secret access key (Secret Access Key, SK)), the size of the first data, and the storage location of the target object. The bucket index indicates the correspondence between the metadata and the storage bucket, and illustratively, it can be the identifier of the storage bucket where the first metadata is located. When the first metadata includes user authentication information, when the first user accesses the first metadata, it is necessary to first pass the AK / SK inspection, and only after the verification is passed can the first user access the first metadata. And, when the first user shares data, it is also necessary to first pass the AK / SK inspection, and only after the verification is passed can the first user send a sharing request to the management device. Optionally, based on the user authentication information, the management device can determine the data operation permission of the first user on the first data, and open the corresponding data operation permission to the first user; wherein, the data operation permission is used to indicate the data operation that the current access user can perform, including data access, data upload, data retrieval, data deletion or data modification.

[0106] S102, generating second metadata at a target location according to the first metadata, the second metadata including a storage address of the first data and an identifier of a second user, so that the second user can access the first data through the second metadata;

[0107] A target location can be associated with a user or user group, so in some implementations, the identity of the user currently accessing the target data location can also be authenticated and permission management can be performed, thereby improving the security of data storage and applications. The second metadata may include the storage address of the first data and the second user identifier, so that the second user can obtain the storage address of the first data through the second metadata to access the first data.

[0108] As in the aforementioned implementation, when the first metadata further includes an index of a storage bucket where the first metadata is located, generating the second metadata at the target location according to the first metadata includes:

[0109] The second metadata also includes an index of the storage bucket where the second metadata is located.

[0110] The second metadata may also include an index of the storage bucket where the second metadata is located. In addition, in some embodiments, as explained above, the second metadata may also include an index of the storage bucket where the second metadata is located, i.e., a bucket index, user authentication information, and at least one of the first data sizes. Accordingly, the first metadata may also include these corresponding information.

[0111] Among them, the bucket index of the second metadata is used to indicate the identifier of the storage bucket where the second metadata is located, the user authentication information of the second metadata can be regenerated according to the identifier of the second user, and the first data size of the second metadata can be the same as the first data size of the first metadata.

[0112] As in the aforementioned implementation mode, when the first metadata further includes the user authentication information of the first user, generating the second metadata at the target location according to the first metadata includes:

[0113] The second metadata generates user authentication information of the second user according to the identifier of the second user.

[0114] When the second metadata includes user authentication information, the second user needs to pass the AK / SK verification before accessing the second metadata. Only after the verification is passed can the first user access the second metadata, thereby accessing the first data. Optionally, based on the user authentication information, the management device can also determine the data operation authority of the second user on the first data, and open the corresponding data operation authority to the second user.

[0115] In addition, as in the aforementioned implementation manner, when the first metadata further includes the size of the first data, generating the second metadata at the target location according to the first metadata includes:

[0116] The first data size of the second metadata is the same as the first data size of the first metadata.

[0117] For the metadata information obtained by scanning, there is no need to perform an actual migration copy of the target object. Instead, only the corresponding metadata of the shared user can be newly created, new metadata can be generated for the target data location, and a new bucket index can be created to achieve reuse of the first data.

[0118] Therefore, by realizing the reuse of the data body in the process of generating the second metadata, the correspondence and validity between the metadata and the user are further ensured, the convenience of subsequent data operations through the metadata is improved, and the situation where multiple copies of the same first data body are stored repeatedly in the cluster is avoided, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0119] S103: Synchronize the second metadata to the metadata storage pool.

[0120] After the second metadata is established, the corresponding relationship between the second metadata, the identifier of the first data and the identifier of the second user may be synchronized to the metadata storage pool to facilitate the call of the corresponding user.

[0121] When the second user wants to access the first data, the management device can find the corresponding second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user, and then access the first data from the first data address in the second metadata.

[0122] Specifically, in this application scenario, the method may further include:

[0123] Obtaining an access request from a second user, where the access request includes an identifier of the first data and an identifier of the second user;

[0124] Determine second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user;

[0125] The first data is accessed according to the storage address of the first data of the second metadata.

[0126] Therefore, when the second user needs to use the first data, an access request from the second user is obtained, and the second metadata is determined in the metadata storage pool through the identifier of the first data and the identifier of the second user in the access request, so that the second user can access the first data through the second metadata, thereby realizing the storage and call of metadata and simplifying the operation and interaction of users when using data.

[0127] As an optional implementation, the method further includes:

[0128] Performing a metadata consistency check and / or an integrity check according to the first metadata and the second metadata to determine whether the second metadata meets corresponding consistency conditions and / or integrity conditions;

[0129] Synchronizing the second metadata to the metadata storage pool includes:

[0130] If it is determined that the second metadata meets the corresponding consistency condition and integrity condition, synchronizing the second metadata information to the metadata storage pool;

[0131] If it is determined that the second metadata does not meet the corresponding consistency condition or integrity condition, the second metadata is corrected according to the object information.

[0132] Among them, metadata consistency check and integrity check can be achieved by comparing whether the second metadata information used for data reuse is consistent with the metadata information of the first metadata. For example, consistency check can be achieved by checking whether the file size, timestamp, permissions, etc. of the second metadata are consistent. It can also verify the relationship of shared first data reference metadata, check whether the reference relationship is consistent, and check whether the correspondence relationship of the first data obtained through the reference relationship and the correspondence relationship of the user identity are consistent. The integrity check can verify whether the form of the second metadata itself and the data form of the first data obtained meet the standards through preset inspection conditions or generated verification values, and verify whether the data attributes and data content of the first data obtained through the second metadata are complete, or verify whether the relevant data meets the basic conditions for the normal operation of the storage environment. In order to improve efficiency, it can also be checked whether the key data points in the second metadata meet the corresponding conditions to complete the consistency check and integrity check.

[0133] This implementation manner performs metadata consistency check and / or integrity check based on the established second metadata and related information of the first metadata after establishing the second metadata. When the second metadata meets the corresponding consistency condition and / or integrity condition, the corresponding relationship between the second metadata, the identifier of the second data and the identifier of the second user is synchronized to the metadata storage pool to complete the entire metadata establishment cycle. When the corresponding conditions are not met, the second metadata is re-established or the related information of the second metadata is corrected, thereby ensuring data security and ensuring data validity when data is accessed or processed at the first data location.

[0134] As an optional implementation, performing metadata consistency check according to the first metadata and the second metadata includes:

[0135] Comparing metadata information of the first metadata and the second metadata to determine whether the metadata information of the first metadata and the second metadata are consistent;

[0136] Among them, metadata information includes file size, timestamp and access permission information;

[0137] Verifying whether the reference relationship between the second metadata and the data ontology corresponds to the reference relationship between the first metadata and the data ontology;

[0138] If it is determined that the second metadata meets the corresponding consistency condition, synchronizing the second metadata information to the metadata storage pool includes:

[0139] If the metadata information of the first metadata and the second metadata are consistent, and the reference relationship between the second metadata and the data body corresponds to the reference relationship between the first metadata and the data body, it is determined that the second metadata meets the corresponding consistency condition, and the second metadata information is synchronized to the metadata storage pool.

[0140] This implementation determines whether metadata information such as file size, timestamp, and access permission information of the established second metadata is consistent with the first metadata by comparing the first metadata and the second metadata, as well as the metadata information of the first metadata and the second metadata. At the same time, it verifies whether the reference relationship between the second metadata and the data body meets the conditions corresponding to the initial metadata, thereby ensuring the effectiveness and security of the second metadata establishment process and ensuring the effectiveness of the data when accessing or processing the data at the first data location.

[0141] As an optional implementation, performing metadata integrity verification according to the first metadata and the second metadata includes:

[0142] Determine a first verification point position of the initial metadata and a second verification point position of the second metadata;

[0143] Generate a first verification code according to the information of the first verification point;

[0144] Generate a second verification code according to the information of the second verification point;

[0145] Verify whether the second verification code is consistent with the first verification code.

[0146] The check code can be implemented through calculation methods such as hash value. The metadata integrity check can be performed by performing an integrity check on key data at corresponding data points or by performing an integrity check on all data.

[0147] Therefore, it is possible to determine whether the data point where the second metadata needs to be verified for integrity meets the integrity conditions in the form of a check code, thereby achieving data integrity verification, thereby ensuring the effectiveness and security of the second metadata establishment process, and ensuring the effectiveness of the data when accessing or processing data at the first data location.

[0148] See also Figure 3 , Figure 3 Schematic diagram of an application scenario of an object data sharing method in a cloud storage environment disclosed in an embodiment of the present application. Figure 3 As shown, Figure 3 A scenario of data sharing and data retrieval is shown.

[0149] For users A and B who share the same file, in the case of object data sharing, they do not need to upload data through the s3 protocol to avoid redundant storage. They only need to complete the metadata reconstruction operation to achieve the reuse of the same file data and maintain the metadata information for each. When sharing files, the same name is overwritten, and the correspondence between the file's metadata and the data body is restored. In the file retrieval scenario, the first data information of the same file is reused, and the metadata information is maintained for each, and can be viewed by users with access rights to the file.

[0150] See also Figure 4 , Figure 4 Schematic diagram of an application scenario of an object data sharing method in a cloud storage environment disclosed in an embodiment of the present application. Figure 4 As shown, Figure 4 An application scenario of data deletion is shown. The metadata of the files stored and shared using S3 corresponds to the data body of the first data one by one, and the data is stored in multiple copies. In this application, if a file is deleted for a certain user, only the metadata information and index link of the user's belonging file will be deleted, and the underlying actual first data will not be deleted.

[0151] In summary, this solution does not rely on the S3 protocol for data copying and sharing. It only needs to reuse the original storage data by creating metadata information of the object to be migrated to avoid redundant storage. It can achieve data sharing from user A to user B, avoiding the extremely long data sharing copy time. At the first data level, the storage sharing operation only performs the metadata update operation, which is a very fast operation compared to data copying and does not affect the modification of the shared data to be copied.

[0152] In addition, the various implementations provided in this application can be implemented in combination. Specifically, based on any implementation, a practical implementation of this application can be:

[0153] In the scenario of object data storage sharing, scan all objects to be copied and shared, obtain the size and corresponding metadata of each object, access rights and other information for subsequent sharing and verification. For the metadata information obtained by the scan, there is no need to actually migrate and copy the object at this time. By creating the corresponding metadata of the sharing user, new metadata is generated for the first data location. In terms of how the shared user accesses the first data, the AK / SK information can also be matched to improve the authentication method of multi-tenant sharing and ensure data security and isolation between tenants.

[0154] For example, after the metadata is newly generated, the shared object is verified and repaired, including the object link relationship and the consistency and integrity check with the original metadata; if there is an error in the metadata information, the metadata is repaired for the erroneous object. The consistency and integrity verification of metadata can be achieved by comparing the metadata information of the source data and the target data, and checking whether the file size, timestamp, permissions, etc. are consistent. In addition, the verification of the metadata relationship of the shared first data reference can also be performed to check whether it is consistent with the information of the person who has the access right to the data.

[0155] After metadata is created, verified or repaired, the generated metadata information is synchronized to the metadata storage pool, and storage migration is completed. Subsequent shared data files can be accessed by users with sharing permissions, and subsequent upload, retrieval, deletion, modification and other operations by the sharing users can be performed.

[0156] In summary, the embodiment of the present application determines the target object, target location, and second user identifier according to the sharing request of the first user in the storage scenario of binary object data in a cloud storage environment, thereby obtaining the first data entity and the first metadata corresponding to each target object, and providing a basis for subsequently establishing metadata at the target location according to the identifier of the second user, and the first user can access the first data through the initial metadata. At the target location where the first data is needed, new second metadata is established, and the second metadata includes the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata, realizing the reuse of the data entity, avoiding the situation where multiple copies of the same first data entity are stored repeatedly in the cluster, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0157] The present application also provides an object data sharing device to implement the above method, see Figure 5 , Figure 5 Schematic diagram of the structure of an object data storage device in a cloud storage environment disclosed in an embodiment of the present application. Figure 5 As shown, based on any other embodiment, the device includes:

[0158] A determination module 21, configured to determine a target object, a target location, and an identifier of a second user according to a sharing request of a first user, wherein the target object includes first data and first metadata, and the first user can access the first data through the first metadata;

[0159] The processing module 22 is used to generate second metadata at the target location according to the first metadata, where the second metadata includes the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata.

[0160] In a cloud storage environment, in a storage scenario of binary object data, the target object, target location, and second user identifier are determined according to the sharing request of the first user, thereby obtaining the first data entity and the first metadata corresponding to each target object, providing a basis for subsequently establishing metadata at the target location according to the identifier of the second user, and the first user can access the first data through the initial metadata. At the target location where the first data is needed, new second metadata is established, and the second metadata includes the storage address of the first data and the identifier of the second user, so that the second user can access the first data through the second metadata, realizing the reuse of the data entity, avoiding the situation where multiple copies of the same first data entity are repeatedly stored in the cluster, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0161] As an optional implementation, the first metadata also includes an index of a storage bucket where the first metadata is located. The specific manner in which the processing module 22 generates the second metadata at the target location according to the first metadata includes:

[0162] The second metadata also includes an index of the storage bucket where the second metadata is located.

[0163] As an optional implementation, the first metadata further includes user authentication information of the first user. The specific manner in which the processing module 22 generates the second metadata at the target location according to the first metadata includes:

[0164] The second metadata generates user authentication information of the second user according to the identifier of the second user.

[0165] As an optional implementation, the first metadata further includes the size of the first data. The specific manner in which the processing module 22 generates the second metadata at the target location according to the first metadata includes:

[0166] The first data size of the second metadata is the same as the first data size of the first metadata.

[0167] Therefore, by realizing the reuse of the data body in the process of generating the second metadata, the correspondence and validity between the metadata and the user are further ensured, the convenience of subsequent data operations through the metadata is improved, and the situation where multiple copies of the same first data body are stored repeatedly in the cluster is avoided, thereby reducing the waste of storage resources and improving storage efficiency. In summary, the storage resource occupancy of the object data storage process is optimized.

[0168] As an optional implementation, the processing module 22 is further configured to:

[0169] The correspondence between the second metadata, the identifier of the first data, and the identifier of the second user is stored in the metadata storage pool.

[0170] After completing the establishment of the second metadata, the correspondence between the second metadata, the identifier of the first data and the identifier of the second user can also be synchronized to the metadata storage pool. When the second user wants to access the first data, the management device can find the corresponding second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user, and then go to the first data address in the second metadata to access the first data, thereby facilitating subsequent calls by the corresponding user.

[0171] As an optional implementation, the processing module 22 is further configured to:

[0172] Obtaining an access request from a second user, where the access request includes an identifier of the first data and an identifier of the second user;

[0173] Determine second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user;

[0174] The first data is accessed according to the storage address of the first data of the second metadata.

[0175] In a scenario where the second user needs to use the first data, an access request from the second user is obtained, and second metadata is determined in a metadata storage pool through an identifier of the first data and an identifier of the second user in the access request, so that the second user can access the first data through the second metadata, thereby realizing the storage and call of metadata and simplifying the operation and interaction of users when using data.

[0176] As an optional implementation, the processing module 22 is further configured to:

[0177] Performing metadata consistency check and / or integrity check according to the first metadata and the second metadata;

[0178] The corresponding relationship between the second metadata, the identifier of the second data, and the identifier of the second user is stored in the metadata storage pool, including:

[0179] If it is determined that the second metadata meets the corresponding consistency condition and integrity condition, the corresponding relationship between the second metadata, the identifier of the second data, and the identifier of the second user is stored in the metadata storage pool;

[0180] If it is determined that the second metadata does not meet the corresponding consistency condition or integrity condition, the second metadata is corrected.

[0181] This implementation manner performs metadata consistency check and / or integrity check based on the established second metadata and related information of the first metadata after establishing the second metadata. When the second metadata meets the corresponding consistency condition and / or integrity condition, the corresponding relationship between the second metadata, the identifier of the second data and the identifier of the second user is synchronized to the metadata storage pool to complete the entire metadata establishment cycle. When the corresponding conditions are not met, the second metadata is re-established or the related information of the second metadata is corrected, thereby ensuring data security and ensuring data validity when data is accessed or processed at the first data location.

[0182] As an optional implementation manner, the specific manner in which the determination module 21 determines the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes:

[0183] The sharing request includes a target object, a target location, and an identifier of a second user. According to the sharing request, the target object, the target location, and the identifier of the second user are obtained.

[0184] As an optional implementation manner, the specific manner in which the determination module 21 determines the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes:

[0185] The sharing request includes an identifier of the first user, an identifier of the first data, a target location, and an identifier of the second user;

[0186] According to the sharing request, obtaining the target location and the identifier of the second user;

[0187] Determining first metadata in a metadata storage pool according to an identifier of the first user and an identifier of the first data;

[0188] An object corresponding to the first metadata is determined as a target object.

[0189] This implementation enables the corresponding user to directly obtain the corresponding target object, target location or identification of the second user and other information according to the sharing request through the management device, thereby improving the efficiency of data interaction during the data sharing process.

[0190] It can be explained that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the determination module 21 can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The function of the above determination module 21. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0191] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. In the embodiment of the present application, the user involved can implement the method provided in any implementation mode through a cloud management device, and the structure of the management device can be as follows: Figure 6 The electronic device shown may include: a transceiver 121 , a processor 122 , and a memory 123 .

[0192] The processor 122 executes the computer execution instructions stored in the memory, so that the processor 122 executes the scheme in the above embodiment. The processor 122 can be a general-purpose processor, including a central processing unit CPU, a network processor (network processor, NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0193] The memory 123 is connected to the processor 122 via a system bus and completes communication between them. The memory 123 is used to store computer program instructions.

[0194] The transceiver 121 may be used to obtain tasks to be executed and configuration information of the tasks to be executed.

[0195] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0196] The electronic device provided in the embodiment of the present application may be the terminal device of the above embodiment.

[0197] An embodiment of the present application also provides a chip for executing instructions, which is used to execute the technical solution of the data sharing method in the above embodiment.

[0198] An embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the data sharing method of the above embodiment.

[0199] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When at least one processor executes the computer program, it can implement the technical solution of the data sharing method in the above embodiment.

[0200] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0201] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0202] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0203] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0204] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0205] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0206] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0207] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0208] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0209] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0210] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data sharing method, characterized in that: The method comprises: determining, according to a sharing request of a first user, a target object, a target location, and an identifier of a second user, wherein the target object includes first data and first metadata, and the first user can access the first data through the first metadata; Second metadata is generated at the target location according to the first metadata, where the second metadata includes a storage address of the first data and an identifier of the second user, so that the second user can access the first data through the second metadata.

2. The method according to claim 1, characterized in that The first metadata also includes an index of a storage bucket where the first metadata is located, and generating second metadata according to the first metadata at the target location includes: The second metadata also includes an index of the storage bucket where the second metadata is located.

3. The method according to claim 1, characterized in that The first metadata also includes user authentication information of the first user, and generating second metadata according to the first metadata at the target location includes: The second metadata generates user authentication information of the second user according to the identifier of the second user.

4. The method according to any one of claims 1 to 3, characterized in that The first metadata also includes the size of the first data, and generating the second metadata at the target location according to the first metadata includes: The first data size of the second metadata is the same as the first data size of the first metadata.

5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The correspondence between the second metadata, the identifier of the first data and the identifier of the second user is stored in a metadata storage pool.

6. The method according to claim 5, characterized in that The method further comprises: Obtaining an access request of the second user, where the access request includes an identifier of the first data and an identifier of the second user; determining the second metadata in the metadata storage pool according to the identifier of the first data and the identifier of the second user; The first data is accessed according to the storage address of the first data of the second metadata.

7. The method according to claim 6, characterized in that The method further comprises: Performing metadata consistency check and / or integrity check according to the first metadata and the second metadata; The storing the correspondence between the second metadata, the identifier of the first data and the identifier of the second user in a metadata storage pool includes: If it is determined that the second metadata meets the corresponding consistency condition and integrity condition, storing the correspondence between the second metadata, the identifier of the first data and the identifier of the second user in a metadata storage pool; If it is determined that the second metadata does not meet the corresponding consistency condition or integrity condition, the second metadata is corrected.

8. The method according to claim 1, characterized in that The step of determining the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes: The sharing request includes the target object, the target location, and the identifier of the second user. The target object, the target location, and the identifier of the second user are obtained according to the sharing request.

9. The method according to claim 5, characterized in that The step of determining the target object, the target location, and the identifier of the second user according to the sharing request of the first user includes: The sharing request includes the identifier of the first user, the identifier of the first data, the target location, and the identifier of the second user; Obtaining the target location and an identifier of the second user according to the sharing request; determining the first metadata in the metadata storage pool according to the identifier of the first user and the identifier of the first data; An object corresponding to the first metadata is determined as the target object.

10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 9.

Images