WO2025112466A1 - File extended attribute management method, file storage client, and apparatus - Google Patents

Abstract

Disclosed are a file extended attribute management method, a file storage client and an apparatus, which relate to the technical field of storage. The method is used for a file storage client, and when the file storage client receives an instruction for instructing to manage a file extended attribute, for example: receiving an attribute setting instruction which instructs to set a target file extended attribute of a target file/target directory as a configured state or a configuring state; and on the basis of the attribute setting instruction and a target interface provided by an object storage service node of an object storage system, determining an attribute setting request, so as to achieve the purpose of converting the attribute setting instruction using file extended attribute semantics into the attribute setting request using object storage semantics. In this way, after the file storage client sends the attribute setting request to the object storage service node, the object storage service node can accurately identify content requested by the attribute setting request, so as to manage the file extended attribute on the basis of the content requested by the attribute setting request.

Description

File extension attribute management method, file storage client and device

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 27, 2023, with application number 202311607099.7 and application name “A method, device and other equipment for data processing”, and the Chinese patent application filed with the State Intellectual Property Office on March 12, 2024, with application number 202410284846.6 and application name “File extension attribute management method, file storage client and device”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of storage technology, and in particular to a file extension attribute management method, a file storage client, and a device.

Background Art

File storage is to store data in the form of files on file storage service nodes, and object storage is to store data in the form of objects on object storage service nodes. Since object storage has no directory and file hierarchy, object storage service nodes using object storage can store a large amount of data, which makes object storage more and more widely used.

Currently, in order to be compatible with some applications that can only access data through file interfaces (i.e., file ecosystem applications, also called file applications), such as desktop cloud applications, media video editing applications, etc., the object storage system (including object storage service nodes and file storage clients) provides object storage-based file services. That is to say, file applications can access data stored in the form of objects on object storage service nodes through the file storage client of the object storage system.

However, since the file semantics used by file extension attributes and the semantics of object storage are quite different, the file service provided by the object storage system cannot manage file extension attributes.

Summary of the invention

The present application provides a file extension attribute management method, a file storage client and a device, which can manage the file extension attributes of the file service provided by the object storage system, and help the object storage system provide more complete file services.

In order to achieve the above objectives, this application adopts the following technical solutions:

In a first aspect, a method for managing file extension attributes is provided, which is applied to a file storage client, wherein the file storage client runs on a Windows operating system, and the Windows operating system also provides a local file system, wherein a directory tree of the local file system includes a target node, wherein the target node is a file or a directory, and the file or the directory is stored in an object storage service node; the method includes: receiving an attribute setting instruction, wherein the attribute setting instruction indicates setting a target file extension attribute of the target node to a target state, wherein the target state includes a configured state or an unconfigured state; determining an attribute setting request based on the attribute setting instruction and a target interface provided by the object storage service node; wherein the interface provided by the object storage service node is used to indicate a format of the attribute setting request, and the attribute setting request is used to request setting a target file extension attribute of the target node to a target state; and sending an attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to a target state.

In this solution, the file storage client runs on the Windows operating system. The directory tree of the local file system provided by the Windows operating system includes a target node, which can be a file or a directory. The file or directory is stored on the object storage service node. On this basis, after receiving the attribute setting instruction, the file storage client can determine the attribute setting request based on the content indicated by the attribute setting instruction and the target interface provided by the object storage service node, so as to request to set the target file extension attribute of the target node to the target state. After that, the file storage client sends the attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to the target state.

When it is necessary to manage file extension attributes, the file storage client determines the attribute setting request through the attribute setting instruction and the format indicated by the target interface provided by the object storage service node, so as to convert the semantics of the file extension attributes (i.e., the attribute setting instruction) into the semantics of the object storage (i.e., the attribute setting request), so that the attribute setting request can use the semantics of the object storage to indicate the content indicated by the attribute setting instruction, so that the object storage service node can accurately identify the content requested by the attribute setting request, and thus manage the file extension attributes based on the content requested by the attribute setting request. Therefore, the object storage system can improve the semantics of object storage through the scheme of the present application, so that the semantics of object storage can be compatible with file extension attributes, thereby providing file extension attribute management services on the basis of providing file services, thereby realizing the provision of more complete file services, so that object storage can be better compatible with file applications.

In a possible implementation, the attribute setting request includes a message content and an operation command, wherein the message content is used to indicate the extended attribute of the target file, and the operation command is used to indicate the target state. This helps to comply with the request representation of the target interface.

In another possible implementation, the attribute setting request includes message content, and the message content is used to indicate the target file extended attribute and the target state. In this way, it is helpful to increase the diversity of the methods of indicating the target file extended attribute and the target state.

In another possible implementation, the message content includes the value of the target file's extended attribute, and the value of the target file's extended attribute is the same as the value of the target file's extended attribute in the Windows operating system. This helps improve the semantic conversion between object storage semantics and file extended attribute semantics. Accuracy of the process.

In another possible implementation, the method further includes: receiving a target instruction, the target instruction is used to instruct to perform a target operation on a target node; the target operation is related to a target file extension attribute; based on the state of the target file extension attribute, determining a permission check result of the target operation; the permission check result includes passing the check or failing the check; in the case where the permission check result is failing the check, returning response information based on the target instruction; the response information is used to indicate that the target operation is refused to be performed on the target node. The file storage client of the object storage system provides a function for implementing file extension attributes, such as implementing a read-only attribute, thereby helping the object storage system to provide a more complete file extension attribute management service.

In another possible implementation, the method further includes: when the permission check result is passed, returning first response information based on the target instruction; the first response information is used to indicate that the target operation is allowed to be performed on the target node.

In another possible implementation, when the target node is the first file, the method also includes: obtaining the first file based on the attribute setting instruction; performing the operation indicated by the attribute setting instruction on the first file to obtain the second file; sending a first storage request to the object storage service node, the first storage request being used to request storage of the second file; the first storage request includes the second file.

In this manner, the file storage client obtains the first file indicated by the attribute setting instruction and performs the operation indicated by the attribute setting instruction on the first file, thereby realizing the target file extension attribute for the first file, such as: realizing the encryption attribute, compression attribute, etc. for the first file. In addition, by sending the first storage request to the object storage service node, the object storage service node is provided with the data to be stored (i.e., the second file) that has no semantics related to the windows file extension attribute, thereby realizing that the object storage service node does not need to perform operations related to the semantics of the windows file extension attribute, such as: encryption operation, compression operation, etc.

In another possible implementation, when the target node is the third file, the method further includes: receiving a storage instruction, the storage instruction is used to instruct to store the third file; the target file extension attribute of the third file is in a configured state; performing the operation indicated by the target file extension attribute on the third file to obtain a fourth file; sending a second storage request to the object storage service node, the second storage request is used to request the object storage service node to store the fourth file; the storage request includes the fourth file. In this method, the file storage client provides a function for implementing file extension attributes, such as: implementing encryption attributes, compression attributes, etc., thereby helping the object storage system to provide a more complete file extension attribute management service.

In another possible implementation, the method further includes: receiving an attribute acquisition instruction, the attribute acquisition instruction being used to instruct to acquire the file extension attribute of the target node; and acquiring and returning the file extension attribute of the target node based on the attribute acquisition instruction. The file storage client of the object storage system provides a query function for the file extension attribute, thereby helping the object storage system to provide a more complete file extension attribute management service.

In another possible implementation, the file storage client runs on the electronic device; based on the attribute acquisition instruction, the file extended attribute of the target node is acquired, including: based on the attribute acquisition instruction, acquiring the file extended attribute of the target node from the storage medium of the electronic device. In this way, the efficiency of acquiring the file extended attribute is improved.

In another possible implementation, obtaining the file extension attribute of the target node based on the attribute obtaining instruction includes: obtaining the file extension attribute of the target node from the object storage service node based on the attribute obtaining instruction. This helps to improve the accuracy of the obtained file extension attribute.

In another possible implementation, the method further includes: writing the file extension attributes of the target node obtained from the object storage service node into the storage medium of the electronic device. In this way, when the file extension attributes need to be obtained later, they can be obtained from the local storage medium, which helps to improve the efficiency of obtaining the file extension attributes later.

In another possible implementation, the method further includes: receiving a metadata acquisition instruction, the metadata acquisition instruction is used to instruct to acquire metadata of the target node; based on the metadata acquisition instruction, acquiring and returning target metadata of the target node; the target metadata of the target node includes file extension attributes of the target node. When acquiring the metadata of the target node, the file extension attributes of the target node are provided at the same time, which helps to improve the integrity of the metadata of the target node.

In another possible implementation, the file storage client runs on the electronic device; based on the metadata acquisition instruction, the target metadata of the target node is acquired, including: based on the metadata acquisition instruction, the target metadata of the target node is acquired from the storage medium of the electronic device. This helps to improve the efficiency of acquiring the target metadata.

In another possible implementation, obtaining target metadata of the target node based on the metadata obtaining instruction includes: obtaining the target metadata of the target node from the object storage service node based on the metadata obtaining instruction. This helps to improve the accuracy of the target metadata.

In another possible implementation, when the target node is a target directory, the method further includes: receiving a directory listing instruction, the directory listing instruction is used to instruct to list the target directory; based on the directory listing instruction, obtaining and returning target metadata of the target directory; the target metadata of the target directory includes file extension attributes of at least one file/subdirectory under the target directory. In this method, when listing the directory, the file extension attributes of at least one file/subdirectory under the directory are also provided, which helps to improve the comprehensiveness of the listed directory.

In another possible implementation, the file storage client runs on the electronic device; based on the directory listing instruction, the target metadata of the target directory is obtained, including: based on the directory listing instruction, the target metadata of the target directory is obtained from the storage medium of the electronic device. This helps to improve the efficiency of obtaining the target metadata.

In another possible implementation, based on the directory listing instruction, obtaining the target metadata of the target directory includes: based on the directory listing instruction command to obtain the target metadata of the target directory from the object storage service node. This helps to improve the accuracy of the target metadata.

In a second aspect, a file extension attribute management method is provided, which is applied to an object storage service node, where a target object is stored on the object storage service node, and the object storage service node is used to map the target object to a target node on a directory tree, where the target node is a file or a directory; the method includes: receiving an attribute setting request sent by a file storage client, where the format of the attribute setting request is determined according to a target interface provided by the object storage service node, where the attribute setting request is used to request that a target file extension attribute of the target node be set to a target state, where the target state includes a configured state or an unconfigured state; parsing the attribute setting request through the target interface to obtain the content requested by the attribute setting request; and the object storage service node sets the target file extension attribute of the target node to the target state based on the content requested by the attribute setting request.

In this scheme, after the object storage service node receives the attribute setting request sent by the file storage client, it determines the content requested by the attribute setting request by parsing the attribute setting request, that is, sets the target file extension attribute of the target node to the target state, and thus sets the target file extension attribute of the target node to the target state based on the content requested by the attribute setting request, thereby completing the management of file extension attributes.

Since the property setting request is determined according to the interface provided by the object storage service node, the property setting request indicates the requested content through the semantics of the object storage, so that the object storage service node can accurately identify the requested content of the property setting request, thereby ensuring the management of file extension attributes. Therefore, the object storage system can improve the semantics of object storage through the solution of the present application, so that the semantics of object storage can be compatible with file extension attributes, thereby providing file extension attribute management services on the basis of providing file services, and further providing more complete file services, so that object storage can be better compatible with file applications.

In a possible implementation, when the target state is in the configured state, the target file extension attribute of the target node is set to the target state based on the content requested by the attribute setting request, including: generating a target field of the target node based on the content requested by the attribute setting request; the target field of the target node is used to indicate that the target file extension attribute has been configured; based on the identifier of the target node, storing the target field of the target node. In this implementation, the object storage service node indicates that the target file extension attribute has been configured on the target node by storing the target field, that is, the state of the target file extension attribute is in the configured state, which helps to improve the accuracy of the state indication of the target file extension attribute.

In another possible implementation, when the target state is an unconfigured state, the target file extended attributes of the target node are set to the target state based on the content requested by the attribute setting request, including: deleting the target field of the target node based on the content requested by the attribute setting request; the target field of the target node is used to indicate that the target file extended attributes have been configured.

In this implementation, the object storage service node indicates that the target node is not configured with the target file extension attribute by deleting the target field, that is, by not storing the target field. This helps to improve the accuracy of the status indication of the target file extension attribute.

In another possible implementation, the object storage service node stores a target string, and the target string is used to indicate the state of the file extension attribute of the target node; based on the content requested by the attribute setting request, the target file extension attribute of the target node is set to the target state, including: when the target state is the configured state, based on the content requested by the attribute setting request, the target bit of the target string is set to a first value; the target bit is used to indicate the target file extension attribute, and the first value is used to indicate the configured state; when the target state is the unconfigured state, based on the content requested by the attribute setting request, the target bit of the target string is set to a second value; the second value is used to indicate the unconfigured state. In this implementation, different file extension attributes are indicated by different bits of a string, and different states are indicated by values, which helps to reduce the storage space occupied by the file extension attributes for related fields.

In another possible implementation, the property setting request includes a message content and an operation command, the message content is used to indicate the target file extended attribute, and the operation command is used to indicate the target state. Alternatively, the property setting request includes a message content, and the message content is used to indicate the target file extended attribute and the target state.

In another possible implementation, the property setting request includes the value of the target file extension attribute; the object storage service node sets the target file extension attribute of the target node to the target state based on the content requested by the property setting request, including: determining the value of the target file extension attribute based on the property setting request; when the value of the target file extension attribute is the same as the target value, setting the target file extension attribute of the target node to the target state based on the content requested by the property setting request; the target value is the value of the target file extension attribute in the Windows operating system. In this implementation, by verifying the value of the target file extension attribute, it helps to improve the accuracy of subsequent file extension attribute management.

In another possible implementation, the method further includes: when the value of the target file extension attribute is different from the target value, returning a prompt message to the file storage client, the prompt message is used to indicate that the value of the target file extension attribute is wrong. In this way, it is helpful for the file storage client to adjust the generation logic of the attribute setting request in time to avoid subsequent wrong requests.

In another possible implementation, the method further includes: receiving an attribute acquisition request sent by a file storage client, the attribute acquisition request being used to request to acquire file extended attributes of a target node; and returning the file extended attributes of the target node to the file storage client based on the attribute acquisition request. In this method, the object storage service node provides a query service for file extended attributes.

In another possible implementation, the method further includes: receiving a metadata acquisition request sent by the file storage client, the metadata acquisition request being used to request the acquisition of metadata of the target node; and returning the target metadata of the target node to the file storage client based on the metadata acquisition request. The target metadata of the target node includes the file extension attributes of the target node. In this way, when requesting to obtain the metadata of the target node, the file extension attributes of the target node are provided at the same time, which helps to improve the integrity of the metadata of the target node.

In another possible implementation, when the target node is a target directory, the method further includes: receiving a directory listing request sent by a file storage client, the directory listing request being used to request metadata of the target directory; returning target metadata of the target directory to the file storage client based on the directory listing request; the target metadata of the target directory including file extension attributes of at least one file/subdirectory under the target directory. In this method, when requesting to list a directory, the file extension attributes of at least one file/subdirectory under the target directory are provided at the same time, which helps to improve the comprehensiveness of the listed directory.

In another possible implementation, the method further includes: receiving a deletion request sent by the file storage client, the deletion request being used to request deletion of metadata of the target node; and deleting the file extension attribute of the target node based on the deletion request. In this method, when requesting to delete the metadata of the target node, the file extension attribute of the target node is also deleted, which helps to completely clear the relevant data of the target node, thereby helping to avoid useless data occupying storage space.

In a third aspect, a file extension attribute management method is provided, which is used in an object storage system. The object storage system includes an object storage service node and a file storage client. The object storage service node stores a target object, and the object storage service node is used to map the target object to a target node on a directory tree. The file storage client runs on a Windows operating system, and the Windows operating system provides a local file system. The directory tree of the local file system includes a target node, and the target node is a file or a directory. The method comprises: a file storage client receives an attribute setting instruction, the attribute setting instruction indicates setting a target file extension attribute of a target node to a target state; the target state comprises a configured state or an unconfigured state; the file storage client determines an attribute setting request based on the attribute setting instruction and a target interface provided by an object storage service node; the target interface is used to indicate a format of the attribute setting request, and the attribute setting request is used to request setting a target file extension attribute of a target node to a target state; the file storage client sends an attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to a target state; the object storage service node receives the attribute setting request sent by the file storage client; the object storage service node parses the attribute setting request through the target interface to obtain the content requested by the attribute setting request; the object storage service node sets the target file extension attribute of the target node to a target state based on the content requested by the attribute setting request.

It should be noted that, in the third aspect, the file storage client can also be used to execute any possible implementation method provided in the first aspect above, and the object storage service node can also be used to execute any possible implementation method provided in the second aspect above.

In a fourth aspect, a file storage client is provided, the file storage client comprising: a functional module for executing any one of the methods provided in the first aspect, the actions executed by each functional module are implemented by hardware execution or by hardware execution of corresponding software. For example, the file storage client may include a receiving module, an attribute management module and a sending module; the receiving module is used to receive an attribute setting instruction, the attribute setting instruction indicates that the target file extension attribute of the target node is set to a target state, the target state includes a configured state or an unconfigured state; the attribute management module is used to determine an attribute setting request based on the attribute setting instruction and a target interface provided by the object storage service node; the target interface provided by the object storage service node is used to indicate the format of the attribute setting request, the attribute setting request is used to request that the target file extension attribute of the target node be set to a target state; the sending module is used to send an attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to a target state.

In a fifth aspect, a file extension attribute management device is provided, the device comprising: a functional module for executing any one of the methods provided in the second aspect, the actions performed by each functional module are executed by hardware or by hardware executing corresponding software. For example, the file extension attribute management device may include a receiving module, a parsing module and a storage module; the receiving module is used to receive an attribute setting request sent by a file storage client, the format of the attribute setting request is determined according to a target interface provided by an object storage service node, the attribute setting request is used to request that the target file extension attribute of the target node be set to a target state, the target state including a configured state or an unconfigured state; the parsing module is used to parse the attribute setting request through the target interface to obtain the content requested by the attribute setting request; the management module is used to set the target file extension attribute of the target node to a target state based on the content requested by the attribute setting request.

In a sixth aspect, an object storage system is provided, which includes a file storage client and an object storage service node. A target object is stored on the object storage service node, and the object storage service node is used to map the target object to a target node on a directory tree; the file storage client runs on a Windows operating system, and the Windows operating system provides a local file system, and the directory tree of the local file system includes a target node, and the target node is a file or a directory. The file storage client is used to receive an attribute setting instruction, and the attribute setting instruction indicates that the target file extension attribute of the target node is set to a target state; the target state includes a configured state or an unconfigured state; the file storage client is also used to determine an attribute setting request based on the attribute setting instruction and a target interface provided by the object storage service node; the target interface of the object storage service node is used to indicate the format of the attribute setting request, and the attribute setting request is used to request that the target file extension attribute of the target node be set to a target state; the file storage client is also used to send an attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to a target state; the object storage service node is used to receive an attribute setting request sent by the file storage client of the object storage system; the object storage service node parses the attribute setting request through the target interface to obtain the content requested by the attribute setting request; The object storage service node is used to set the target file extended attribute of the target node to the target state based on the content requested by the attribute setting request.

It should be noted that in the sixth aspect, the file storage client can also be used to execute any possible implementation method provided in the first aspect above, and the object storage service node can also be used to execute any possible implementation method provided in the second aspect above.

In a seventh aspect, a processor is provided, which is used to execute the steps of any one of the methods provided in the first aspect.

In an eighth aspect, a processor is provided, which is used to execute the steps of any one of the methods provided in the second aspect.

In a ninth aspect, a chip is provided, comprising: a processor and a power supply circuit; the power supply circuit is used to supply power to the chip, and the processor is used to execute the steps of any one of the methods provided in the first aspect above.

In the tenth aspect, a chip is provided, comprising: a processor and a power supply circuit; the power supply circuit is used to supply power to the chip, and the processor is used to execute the steps of any one of the methods provided in the second aspect above.

In the eleventh aspect, an electronic device is provided, comprising: a processor, a memory, and a computer program/instructions stored in the memory; the processor executes the computer program/instructions to enable the electronic device to implement the steps of any one of the methods provided in the first aspect above.

In the twelfth aspect, a computing device is provided, comprising a processor, a memory, and a computer program/instructions stored in the memory; the processor executes the computer program/instructions so that the computing device implements the steps of any one of the methods provided in the second aspect above.

In the thirteenth aspect, a computing device cluster is provided, comprising: at least one computing device, each computing device in the at least one computing device comprises a processor and a memory; each computing device comprises a processor, a memory and a computer program/instructions stored on the memory; the processor executes the computer program/instructions so that the computing device cluster implements the steps of any one of the methods provided in the second aspect above.

In a fourteenth aspect, a computer program product is provided, comprising: a computer program/instructions; when the computer program/instructions are executed by a processor of an electronic device, the steps of any one of the methods provided in the first aspect are implemented.

In a fifteenth aspect, a computer program product is provided, comprising: a computer program/instructions; when the computer program/instructions are executed by a processor of a computing device, the steps of any one of the methods provided in the second aspect are implemented.

In the sixteenth aspect, a computer-readable storage medium is provided, on which a computer program/instruction is stored. When the computer program/instruction is executed by a processor of an electronic device, the steps of any one of the methods provided in the first aspect are implemented.

In the seventeenth aspect, a computer-readable storage medium is provided, on which a computer program/instruction is stored. When the computer program/instruction is executed by a processor of a computing device, the steps of any one of the methods provided in the second aspect are implemented.

Among them, the technical effects brought about by any design method in the second aspect to the seventeenth aspect can refer to the technical effects brought about by the different design methods in the above-mentioned first aspect, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a system architecture provided in an embodiment of the present application;

FIG2 is a schematic diagram of another system architecture provided in an embodiment of the present application;

FIG3 is a flow chart of a method for managing file extension attributes provided by an embodiment of the present application;

FIG4 is a schematic diagram of a property interface provided in an embodiment of the present application;

FIG5 is a framework diagram of setting file extension attributes provided by an embodiment of the present application;

FIG6 is a schematic diagram of setting file extension attributes provided by an embodiment of the present application;

FIG7 is a flowchart of another file extension attribute management method provided in an embodiment of the present application;

FIG8 is a flowchart of another file extension attribute management method provided in an embodiment of the present application;

FIG9 is a framework diagram of obtaining file extension attributes provided by an embodiment of the present application;

FIG10 is a schematic diagram of obtaining file extension attributes provided by an embodiment of the present application;

FIG11 is a schematic diagram of obtaining metadata of a file provided in an embodiment of the present application;

FIG12 is a schematic diagram of obtaining metadata of a directory provided in an embodiment of the present application;

FIG13 is a framework diagram of a directory listing provided in an embodiment of the present application;

FIG14 is a flowchart of another file extension attribute management method provided in an embodiment of the present application;

FIG15 is a schematic diagram of implementing file extension attributes provided by an embodiment of the present application;

FIG16 is a flowchart of another file extension attribute management method provided in an embodiment of the present application;

FIG17 is a flowchart of another file extension attribute management method provided in an embodiment of the present application;

FIG18 is a schematic diagram of another method for implementing file extension attributes provided in an embodiment of the present application;

FIG19 is a schematic diagram of a file storage client provided in an embodiment of the present application;

FIG20 is a schematic diagram of a file extension attribute management device provided in an embodiment of the present application;

FIG21 is a schematic diagram of a computing device provided in an embodiment of the present application;

FIG22 is a schematic diagram of a computing device cluster provided in an embodiment of the present application;

FIG23 is a schematic diagram of a connection of a computing device cluster provided in an embodiment of the present application;

FIG. 24 is a schematic diagram of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

Among them, in the description of the embodiments of the present application, unless otherwise specified, "/" indicates that the objects associated before and after are in an "or" relationship, for example, A/B can represent A or B; "and/or" in the present application is only a kind of association relationship describing the associated objects, indicating that there can be three relationships, for example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the embodiments of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or its similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple.

In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art can understand that the words "first", "second", etc. do not limit the quantity and execution order, and the words "first", "second", etc. do not necessarily limit the difference.

Meanwhile, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

The following is a brief introduction to the relevant terms involved in the embodiments of the present application.

File storage service (FSS): It stores data in the form of files on file storage service nodes. File storage service nodes provide a multi-level tree directory storage method based on the file system. File storage service nodes are used to provide operations that conform to file semantics (i.e., file services), such as: reading files, writing files, creating files, deleting files, opening files, closing files, renaming files, etc.

Object storage service (OBS): stores data in the form of objects in object storage nodes. Object storage nodes provide a flat storage method based on buckets and objects. All objects in a bucket are at the same logical level, removing the multi-level tree directory structure in the file storage service node. Object storage nodes are used to provide operations that conform to object semantics (i.e. object services), such as uploading objects, downloading objects, listing each object in a bucket, copying objects, moving objects, deleting objects, deleting each object in a bucket, etc.

Bucket: Also referred to as a bucket, it is a container for storing objects on an object storage node. Each bucket has its own storage category, access rights, region, and other attributes.

Object: It is the basic unit of data storage on an object storage node. An object is a collection of file data and its related attribute information (also called metadata). An object can include key value, metadata and data.

The key value is the name of the object, which can also be called the object name or object name. Each object in a bucket has a unique key value. Metadata is the description information of the object. Metadata includes user metadata and system metadata. User metadata is specified when the user uploads the object, and is the user-defined object description information. System metadata is automatically generated by the object storage service node. Data is the data content of the object, that is, the data of the file, which can also be called user data.

File system: It is the software in the operating system responsible for managing and storing file information. The file system includes the basic file system and several file subsystems. Users can remove and install file subsystems as needed. The target tree provided by the file system may include the root directory, subdirectories, and files under the subdirectories. The root directory or subdirectory may include files and the next-level subdirectories.

User space and kernel space: The virtual memory of electronic devices can be divided into user space and kernel space. User space is used to run user applications, and kernel space is used to run the kernel of the operating system. Among them, user space and kernel space are isolated from each other. Kernel space can execute any command and call all resources of the operating system. User space can only perform simple operations and cannot directly call the resources of the operating system. It needs to go through kernel space to call the resources of the operating system.

File system in user space (FUSE): is a component of the operating system and runs in the user space. It should be noted that in the embodiment of the present application, FUSE can be a component of the Windows operating system.

File extended attributes: are file constants provided by the file system and are used to indicate certain properties of files or directories in the file system.

It should be noted that in the embodiment of the present application, the file extension attribute may refer to the file constant provided by the local file system in the Windows operating system, which will not be described in detail later.

File storage client (Client): used to interact with the object storage service node, such as sending requests to the object storage service node and receiving response information returned by the object storage service node.

It should be noted that in the embodiment of the present application, the file storage client of the object storage system can provide an interface for the Windows operating system, and the Windows operating system can interact with the file storage client through the interface provided by the file storage client.

Transparent transmission: refers to the transmission of data packets from the source address to the destination address without any processing of the data content during the data transmission process. In other words, the business content in the data packet will not be changed, and its original format and instructions will be maintained, ensuring the integrity and accuracy of data transmission.

It should be noted that in the embodiment of the present application, transparent transmission may refer to the file storage client of the object storage system transmitting the file extension attributes to the operating system without performing related operations to implement the file extension attributes.

The following is an exemplary introduction to the application scenarios of the embodiments of the present application.

With the development of storage technology, object storage has been proposed in related technologies to facilitate the storage of unstructured data such as movies, office documents, and images. Object storage uses a flat address space to store data. This address space does not have a hierarchy of directories and files. Therefore, an object storage service node can store a large amount of data.

In order to be compatible with file applications, object storage systems (including object storage service nodes and file storage clients) provide file services based on object storage, that is, file services are built on the basis of object storage. However, due to the significant difference between the file semantics used by file extension attributes and the semantics of object storage, the file services provided by object storage systems cannot manage file extension attributes.

In view of this, an embodiment of the present application provides a file extension attribute management method, which is applied to a file storage client. After receiving a management instruction for a file extension attribute (such as an attribute setting instruction), the file storage client can determine an attribute setting request based on the content indicated by the attribute setting instruction and the target interface provided by the object storage service node, for requesting the management content indicated by the attribute setting instruction, such as requesting to set the target file extension attribute of the target node to a target state. Afterwards, the file storage client sends an attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to a target state.

Since the file storage client determines the attribute setting request through the attribute setting instruction and the format indicated by the target interface provided by the object storage service node, the semantics of the file extension attribute (i.e., the attribute setting instruction) is converted into the semantics of the object storage (i.e., the attribute setting request), and the attribute setting request can use the semantics of the object storage to indicate the content indicated by the attribute setting instruction, so that the object storage service node can accurately identify the content requested by the attribute setting request, and thus manage the file extension attribute based on the content requested by the attribute setting request. Therefore, the object storage system can improve the semantics of object storage through the scheme of the present application, so that the semantics of object storage can be compatible with the semantics of file extension attributes, thereby providing file extension attribute management services on the basis of providing file services, and then providing more complete file services, so that object storage can be better compatible with file applications.

The following is an exemplary introduction to the system architecture of the embodiments of the present application.

The file extension attribute management method provided in the embodiment of the present application is applicable to an object storage system. The object storage system includes an object storage service node (Server) and a file storage client (Client), and the file storage client and the object storage service node can communicate. Among them, the object storage system can provide file services and object services.

In an embodiment of the present application, the object storage service node may include at least one computing device.

It should be noted that in the embodiments of the present application, at least one may be one, or may be multiple, where multiple refers to two or more, which will not be repeated later.

Optionally, the computing device may be a network device or a terminal device. The network device may include a server, etc. Among them, the server may be a physical server, or two or more physical servers with different responsibilities, and the various functions of the server are realized by mutual cooperation. Exemplarily, the server may be a blade server, a high-density server, a rack server or a tower server, etc. The terminal device may include an ultra-mobile personal computer (UMPC), a laptop, a netbook, a desktop computer, an all-in-one computer, etc.

It should be noted that the above is only an exemplary description, and the embodiments of the present application do not limit the specific device form of the computing device.

In an embodiment of the present application, the object storage service node may also include a storage device, which may include one or more storage buckets, and the one or more storage buckets are used to store objects.

Exemplarily, the storage device may include a hard disk drive (HDD), a solid state disk/drive (SSD), etc. It should be noted that the form of the storage device in the embodiment of the present application is not limited, and the above is only an exemplary description. In addition, the number of storage devices in the embodiment of the present application is not limited.

In the embodiment of the present application, the storage device may be arranged on the computing device, or may be arranged independently of the computing device. When the storage device and the computing device are arranged independently of each other, the storage device and the computing device may communicate.

In the embodiment of the present application, the object storage service node stores data through storage buckets, that is, the object storage service node stores data in the form of objects in the storage bucket.

In order to make it easier for users to manage data in buckets, the object storage service node also provides a way to simulate folders. By adding "/" to the name of the object, the object is simulated as a folder on the OBS management console. The object name is abc.jpg. If you need to simulate object 0 as a file in a folder, you can modify the object identifier of object 0 to test/abc.jpg. At this time, "test" is the simulated folder. When the user lists the objects in the bucket through the object interface, the object identifiers obtained are separated by "/". If there is content after the last "/", it represents a file, that is, the object to which the object identifier belongs indicates a file. If there is no content after the last "/", it represents a folder path, that is, the object to which the object identifier belongs indicates a simulated folder. For example, the object identifier of object 1 is test/, so object 1 represents a folder path.

It should be noted that, when an object is simulated as a folder, the object identifier includes the folder path and the object name. In addition, when an object is not simulated as a folder, the object identifier can be the object name.

In the embodiment of the present application, the object storage service node can map objects in the storage bucket to nodes on the directory tree through a hierarchical namespace. Among them, a node can be a file or a directory, an object including user data can be mapped to a file, and a simulated folder (i.e., an object that does not include user data) can be mapped to a directory. On this basis, after the user sets the file service feature to be enabled for the object storage service node, the object storage service node can provide file services.

In the embodiment of the present application, the file storage client can be installed on the user's electronic device, and the electronic device can communicate with the object storage service node through the file storage client. The user can rent a cloud storage service from a cloud service provider through the file storage client, such as renting a storage bucket, and then the user can store data in the storage bucket through the file storage client.

On this basis, electronic devices can communicate with object storage service nodes through file storage clients, thereby using the object storage system to provide file services, such as accessing files, managing file extension attributes, etc.

It should be noted that, since the object storage system can provide file services through a file storage client, the file storage client can also be called a file system client (SFC).

Optionally, the electronic device may be a terminal device or a network device. The terminal device may include a mobile phone, a tablet computer, a handheld computer, a PC, a cellular phone, a personal digital assistant (PDA), a wearable device (such as a smart watch, a smart bracelet, etc.), a smart home device (such as a TV, etc.), a car machine (such as a car computer, etc.), a smart screen, a game console, a headset, an AI speaker, an augmented reality (AR)/virtual reality (VR) device, an ultra-mobile personal computer (UMPC), a laptop, a netbook, a desktop computer or an all-in-one computer, etc. The network device may include a server, etc. Among them, the server may be a physical server, or it may be two or more physical servers that share different responsibilities and cooperate with each other to realize the various functions of the server. Exemplarily, the server may be a blade server, a high-density server, a rack server or a tower server, etc.

It should be noted that the above is only an exemplary description, and the embodiments of the present application do not limit the specific device form of the electronic device.

As shown in FIG1 , it is a schematic diagram of a system architecture provided in an embodiment of the present application.

1 , the system architecture may include an object storage service node, a file storage client, and an electronic device, wherein the file storage client may be installed on the electronic device.

Cloud service providers provide cloud services (such as object services, file services, file extension attribute management services, etc.) to users through object storage service nodes. Cloud service tenants (i.e. users) rent cloud services provided by cloud service providers through file storage clients on electronic devices.

Exemplarily, the storage device of the object storage service node may include storage bucket 1, ..., storage bucket N, where N is a positive integer greater than 1. After the user logs in to the file storage client through the electronic device, the user may rent a storage bucket (e.g., rent storage bucket 1) from the cloud service provider. After renting storage bucket 1, the data to be stored (e.g., data 0-data 4) may be sent to the object storage service node through the file storage client. After receiving data 0-data 4, the object storage service node stores data 0-data 4 in the form of an object (i.e., object 0-object 4) in storage bucket 1.

It should be noted that the embodiments of the present application do not limit the number of computing devices, the number of storage devices, and the number of storage buckets included in the object storage service node. Figure 1 is only for illustrative purposes.

As shown in FIG2 , it is a schematic diagram of another system architecture provided in an embodiment of the present application.

2 , the electronic device is installed with a Windows operating system and a file storage client, and the file storage client runs on the Windows operating system. The Windows operating system can call an interface provided by the file storage client to interact with the file storage client.

It should be noted that there is no limitation on the case of “window” in the embodiment of the present application. For example, “window” can also be represented by “Window”, which will not be repeated later.

Since the file storage client is installed on an electronic device running the Windows operating system, the file storage client may also be referred to as a Windows file storage client (client).

In the embodiment of the present application, the Windows operating system also provides a local file system. The local file system is used to provide a data storage mechanism based on files and directories. Among them, the target tree provided by the local file system may include a root directory, a subdirectory, and files under the subdirectory, and the root directory or subdirectory may include files and next-level subdirectories.

Exemplarily, the directory tree of the local file system may include multiple nodes, each of which may be a file or a directory. Files or directories are stored in buckets on Object Storage service nodes.

In the embodiment of the present application, the file storage client can interact with the object storage service node through the interface provided by the object storage service node. On this basis, the file storage client can transmit storage data unrelated to Windows semantics to the object storage service node.

It should be noted that in the embodiment of the present application, the file storage client performs a certain operation, which can be considered as the electronic device performing a certain operation during the process of running the file storage client, or the electronic device performing a certain operation through the file storage client, which will not be repeated later.

Exemplarily, the interface provided by the object storage service node can be a representational state transfer (REST) application programming interface (API).

In the embodiment of the present application, the Windows operating system includes a FUSE module, and the FUSE module can be used to interact with the file storage client. In other words, the Windows operating system can interact with the file storage client through the FUSE module. On this basis, the file storage client can provide the Windows operating system with data that conforms to Windows semantics.

It should be noted that in the embodiment of the present application, the FUSE module performs a certain operation, which can be considered as the electronic device performing a certain operation during the process of running the FUSE module, or the electronic device performing a certain operation through the FUSE module, which will not be repeated later.

Furthermore, since the file storage client can interact with Windows through the FUSE module, the file storage client can be considered to be a FUSE-based file storage client.

In the embodiment of the present application, the file storage client can also be used to manage file extension attributes, such as: configuring file extension attributes for nodes on the directory tree, canceling file extension attributes that have been configured for nodes on the directory, etc.

In the embodiment of the present application, the file storage client can also be used to implement file extension attributes, such as intercepting write operations performed on a node when a node is configured with a read-only attribute.

Exemplarily, when the encryption attribute and compression attribute of a file are configured, the file storage client can perform encryption operations, compression operations and other operations related to Windows semantics on the file, and obtain encrypted files and compressed files, thereby providing storage data unrelated to Windows semantics for the object storage service node. Afterwards, the file storage client transmits the encrypted files and compressed files to the object storage service node. After receiving the encrypted files and compressed files, the object storage service node can directly store the encrypted files and compressed files without having to care about the Windows semantics of the storage data.

For example, after the file storage client obtains the encrypted file or compressed file from the object storage service node, it can decrypt the encrypted file or decompress the compressed file to obtain the decrypted file or decompressed file. Afterwards, the file storage client can transfer the decrypted file or decompressed file to the operating system, which will display it to the user or transfer it to the application for use.

Based on the above, the file storage client can manage and logically implement the specific meanings represented by the file extension attributes.

In the embodiment of the present application, the file storage client may include an attribute management module, and the attribute management module may be used to manage file extension attributes.

Exemplarily, the file storage client may map the management instruction of the file extension attribute (eg, attribute setting instruction) into an attribute setting request through the attribute management module, and send the attribute setting request to the object storage service node to request to manage the file extension attribute.

In the embodiment of the present application, the file storage client may include an attribute implementation module, which may be used to implement file extension attributes. Exemplarily, the file storage client may implement the read-only attribute, encryption attribute, compression attribute, etc. of the file through the attribute implementation module.

It should be noted that the functions implemented by the attribute management module and the functions implemented by the attribute implementation module can also be implemented by one module, and this is not limited in the embodiments of the present application.

In an embodiment of the present application, the object storage service node is configured with a parsing module, which can be used to implement the parsing of attribute setting requests to determine the management method of file extension attributes based on the content requested by the attribute setting request, such as: setting the target file extension attribute of the target node to the target state, etc.

It should be noted that in the embodiments of the present application, an operation performed by the parsing module can be considered as an operation performed in the process of the object storage service node running the parsing module, or the object storage service node performs a certain operation through the parsing module, which will not be repeated later.

Exemplarily, the file extended attributes managed by the file storage client may include: read-only attribute, hidden attribute, system attribute, directory attribute, archive attribute, device driver installation attribute, normal attribute, temporary attribute, sparse file attribute, reanalysis point attribute, compression attribute, offline attribute, no content index attribute, encryption attribute, integrity stream attribute, virtual reality attribute, no erase data attribute, custom extended attribute, fixed attribute, unfixed attribute, recall open attribute, call data access attribute, etc.

As shown in Figure 2, the object storage service node provides a business interface and a management interface. The business interface is used to access objects stored on the object storage service node, and the management interface is used to manage file extension attributes of objects stored on the object storage service node.

Based on this, the file storage client can perform read and write operations on objects stored on the object storage service node through the business interface. In addition, the file extension attributes of objects stored on the object storage service node can also be managed through the management interface.

In the embodiment of the present application, the object storage service node also stores metadata of the object. The object storage service node can parse the attribute setting request through the parsing module to determine the management method of the file extension attribute, such as generating a target field, modifying the value of the target string, etc. Used to indicate the status of file extension attributes, etc., wherein the target field and target string can be stored in the metadata of the object to facilitate the permanent storage of file extension attributes.

It should be noted that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

For ease of understanding, the file extension attribute management method provided in the embodiment of the present application is exemplarily introduced below in combination with the above system architecture and accompanying drawings.

The embodiment of the present application will be divided into three parts to exemplarily introduce the scheme of the file extension attribute management method.

The first part, in conjunction with Figures 3 to 7, introduces a solution for setting file extension attributes of a file or directory, such as: configuring at least one file extension attribute for a target node, canceling at least one file extension attribute that has been configured for a target node, etc.

The second part, in conjunction with FIG. 8 to FIG. 13 , introduces a solution for querying file extension attributes of a file or directory, such as querying at least one file extension attribute of a target node.

The third part, in conjunction with FIG. 14 to FIG. 18 , introduces a solution for implementing file extension attributes of a file or directory, such as: implementing at least one file extension attribute of a target node.

The following introduces the first part of the embodiment of the present application in conjunction with Figures 3 to 7.

Fig. 3 is a flow chart of a method for managing file extension attributes according to an exemplary embodiment. Exemplarily, the method for managing file extension attributes may include the following steps 301-303.

It should be noted that the "step" in the embodiments of the present application can be abbreviated as "S" and will not be repeated later.

In an embodiment of the present application, an object storage service node stores multiple objects. Exemplarily, the multiple objects may include a target object, and the target object may be any one of the multiple objects. Among them, an object may be used to indicate a file or a folder. When an object is used to indicate a file, the object may include user data, metadata, and an object identifier (ID). When an object is used to indicate a folder, the object may include metadata and an object identifier.

The object storage service node maps multiple objects stored in the bucket to multiple nodes on the directory tree. Exemplarily, the multiple nodes include a target node, which is a node mapped based on the target object.

It should be noted that when a node is a file, the node may also be called a file node. When a node is a directory, the node may also be called a directory node.

It can be understood that an object used to indicate a file will be mapped to a file node on the directory tree, and an object used to indicate a folder will be mapped to a directory node on the directory tree.

In an embodiment of the present application, an object storage service node stores a mapping relationship between multiple objects and multiple nodes. There is a one-to-one correspondence between multiple objects and multiple nodes, that is, there is a mapping relationship between an object and the node to which the object is mapped. Exemplarily, there is a mapping relationship between a target node and a target object.

The following describes the relationship between nodes and objects by taking the target element stored on the object storage service node as an example.

Exemplarily, the object storage service node stores the target element in the form of an object in a storage bucket, and the target element can be user data or a simulated folder. When a user accesses the target element based on an object file storage client, the target data can be called a target object. When a user accesses the target element based on a file system file storage client, the target data is called a target node. Among them, the target node and the target object with a mapping relationship point to the same element (i.e., the target element).

The following uses a target object and a target node mapped to the target object as an example to exemplify the file extension attribute management method provided by the embodiment of the present application, wherein the identifier of the target object and the identifier of the target node are both target identifiers.

Exemplarily, the representation of the target identifier can be a Uniform Resource Identifier (URI), a string, etc., which is not limited in the embodiments of the present application.

In an embodiment of the present application, a Window operating system and a file storage client are installed on the electronic device. The Window operating system can interact with the file storage client through a FUSE module, and the file storage client can interact with the object storage service node through an interface provided by the object storage service node.

Step 301: The file storage client receives an attribute setting instruction, which indicates setting the target file extension attribute of the target node to a target state, wherein the target state includes a configured state or an unconfigured state.

It can be understood that setting the target file extended attribute to the configured state can be considered as configuring the target file extended attribute for the target node, and setting the target file extended attribute to the unconfigured state can be considered as canceling the target file extended attribute configured for the target node.

In the embodiment of the present application, the attribute setting instruction indicates the target node. Exemplarily, the attribute setting instruction may include the identifier of the target node, the path of the target node, etc., so as to indicate the target node. This helps to avoid the file storage client setting the file expansion of the non-target node. The extended attributes help ensure the accuracy of subsequent operations performed by the file storage client.

In the embodiment of the present application, the attribute setting instruction indicates the target file extended attribute. Exemplarily, the attribute setting instruction may include the identifier of the target file extended attribute, the name of the target file extended attribute, etc., so as to indicate the target file extended attribute. In this way, it is helpful to avoid the file storage client from managing non-target file extended attributes, thereby helping to ensure the accuracy of subsequent operations performed by the file storage client.

Optionally, the target file extended attributes may include: at least one of: read-only attribute, hidden attribute, system attribute, directory attribute, archive attribute, device driver installation attribute, normal attribute, temporary attribute, sparse file extension attribute, reanalysis point attribute, compression attribute, offline attribute, no content index attribute, encryption attribute, integrity stream attribute, virtual reality attribute, no erase data attribute, custom extended attribute, fixed attribute, unfixed attribute, recall open attribute, and call data access attribute.

It should be noted that the embodiment of the present application does not limit the type of extended attributes of the target file, and the above is only an exemplary description.

Optionally, the target file extended attribute refers to a type of attribute, i.e., each file extended attribute indicated by the attribute setting instruction. Since the attribute setting instruction can indicate setting one or more file extended attributes at the same time, the target file extended attribute can also refer to one or more file extended attributes, that is, one or more file extended attributes can be called the target file extended attribute.

Exemplarily, the attribute setting instruction may indicate setting file extended attributes such as read-only attribute, hidden attribute, encrypted attribute, compressed attribute, etc. Based on this, the target file extended attributes may include read-only attribute, hidden attribute, encrypted attribute, compressed attribute, etc. In other words, the read-only attribute, hidden attribute, encrypted attribute, compressed attribute, etc. may all be referred to as target file extended attributes.

In this embodiment, multiple file extension attributes can be indicated by setting the attribute setting instruction, that is, multiple file extension attributes are used as target file extension attributes. In this way, it is possible to set multiple file extension attributes at the same time, which helps to improve the setting efficiency of file extension attributes and further helps to improve the user experience.

In the embodiment of the present application, the attribute setting instruction indicates the target state, which helps to avoid the file storage client from setting a non-target state, thereby helping to ensure the accuracy of subsequent operations performed by the file storage client.

In the embodiment of the present application, when the target file extension attribute includes multiple file extension attributes, the target state of each file extension attribute in the multiple file extension attributes can be different, or can also be the same. In other words, the target states of different target file extension attributes can be the same, or can also be different. In this way, even file extension attributes with different target states can be set through the same instruction, thereby helping to improve the setting efficiency of file extension attributes.

Exemplarily, the attribute setting instruction indicates the target file extended attributes such as read-only attribute, hidden attribute, encryption attribute, and compression attribute. On this basis, the attribute setting instruction also indicates setting the read-only attribute to a configured state, the hidden attribute to an unconfigured state, the encryption attribute to a configured state, and the compression attribute to a configured state. Thus, the target state of the read-only attribute is a configured state, the target state of the hidden attribute is an unconfigured state, the target state of the encryption attribute is a configured state, and the target state of the compression attribute is a configured state.

In the embodiment of the present application, the attribute setting instruction includes multiple situations, and the following is an exemplary introduction through situation 1 to situation 2.

Case 1: The property setting instruction is a user-triggered instruction.

In one example, the user may directly instruct to set the target file extended attribute of the target node to the target state.

Exemplarily, as shown in (a) of FIG4 , the electronic device displays the property interface of the target node, and the property interface indicates a read-only property and a hidden property. The box on the left side of the read-only property is not selected, so the current state of the read-only property is an unconfigured state, and the box on the left side of the hidden property is selected, so the current state of the hidden property is a configured state.

Example 1, as shown in (b) in Figure 4, when the user selects the box on the left side of the read-only attribute through the electronic device, the electronic device responds to the user's trigger operation (i.e., selecting the box) and sends a property setting instruction to the file storage client, where the property setting instruction instructs the read-only attribute (i.e., the target file extended attribute) to be set to a configured state (i.e., the target state).

Example 2, as shown in (c) in Figure 4, when the user unchecks the box on the left side of the hidden attribute through the electronic device, the electronic device responds to the user's trigger operation (i.e., unchecking the box) and sends a property setting instruction to the file storage client, where the property setting instruction instructs to set the hidden attribute (i.e., the target file extended attribute) to an unconfigured state (i.e., the target state).

Exemplarily, as shown in (d) in FIG. 4 , when a user selects the solution on the left side of the read-only attribute and unselects the solution on the left side of the hidden attribute through an electronic device, the electronic device responds to the user's trigger operation and sends an attribute setting instruction to the file storage client, wherein the attribute setting instruction indicates that the read-only attribute is set to a configured state and the hidden attribute is set to an unconfigured state.

In another example, the user instructs to perform a first operation on the target node, thereby instructing to set the target file extension attribute of the target node to a target state, wherein the first operation is related to the target file extension attribute.

Example 3: The user instructs the encryption of the target node through the electronic device. The electronic device responds to the user's trigger operation and sends an encryption instruction (i.e., an attribute setting instruction) to the file storage client. After receiving the encryption instruction, the file storage client performs an encryption operation on the target node and sets the encryption attribute of the target node (i.e., the target file extended attribute) to the configured state (i.e., the target state). In other words, the encryption instruction not only instructs the encryption of the target node, but also instructs the encryption attribute of the target node to be set to the configured state.

Example 4: The user instructs the electronic device to compress the target node. The electronic device responds to the user's trigger operation and sends a compression instruction (i.e., an attribute setting instruction) to the file storage client. After receiving the compression instruction, the file storage client performs a compression operation on the target node and sets the compression attribute of the target node (i.e., the target file extension attribute) to the configured state (i.e., the target state). In other words, the compression instruction not only instructs the target node to be compressed, but also instructs the target node to be set to the configured state.

In an embodiment of the present application, after a user triggers an attribute setting instruction through an electronic device, the Windows operating system running on the electronic device sends an attribute setting instruction to a file storage client to instruct the file storage client to set the target file extended attribute of the target node to a target state.

It should be noted that in the embodiments of the present application, the operating system performs a certain operation, which can be considered as the electronic device performing a certain operation during the process of running the operating system, or the electronic device performing a certain operation through the operating system, which will not be further described later.

In this embodiment, the attribute setting instruction can be a user-triggered instruction, so that the user can set file extension attributes for different nodes, thereby helping to improve the user experience.

Case 2: The property setting instruction is a command triggered by the target application.

Exemplarily, during the process of an electronic device running a target application (hereinafter referred to as the target application), if it is necessary to set the target file extension attribute of the target node to a target state, the target application can send a setting instruction to the operating system to instruct the target file extension attribute of the target node to be set to a target state. In response to the received setting instruction, the operating system sends an attribute setting instruction to the file storage client to instruct the file storage client to set the target file extension attribute of the target node to a target state.

It should be noted that in the embodiments of the present application, the target application performs a certain operation, which can be considered as the electronic device performing a certain operation during the process of running the target application, or the electronic device performing a certain operation through the target application, which will not be further described later.

For example, the target application may be a file application such as a desktop cloud application, a media asset video application, etc. It should be noted that the embodiment of the present application does not limit the type of the target application, and the above is only an exemplary description.

It should be noted that for other explanations of Case 2, please refer to the explanation of Case 1, which will not be repeated here.

In this embodiment, the attribute setting instruction can be set as an instruction triggered by the target application, thereby providing the target application with permission to set file extended attributes, thereby making the object storage more compatible with file applications and providing more comprehensive file services for file applications.

The following is an exemplary introduction to the manner in which the Windows operating system sends a property setting instruction to a file storage client.

In an embodiment of the present application, the Windows operating system can send attribute setting instructions to the file storage client through the FUSE module.

Exemplarily, after a user triggers a property setting instruction, or a target application sends a setting instruction to Windows, the Windows operating system sends the property setting instruction to the FUSE module, so that the FUSE module sends the property setting instruction to the file storage client.

In the embodiment of the present application, the file storage client is configured with a first interface, and the first interface is used to instruct to set the file extension attribute. On this basis, the Windows operating system can send the attribute setting instruction to the file storage client through the first interface.

Exemplarily, as shown in FIG5 , after receiving the attribute setting instruction sent by the operating system, the FUSE module sends the attribute setting instruction to the file storage client by calling the first interface.

Exemplarily, the first interface may be win_set_file_attr, where "win" is used to represent the Windows operating system, "set" is used to represent setting, and "file_attr" is used to represent file extended attributes.

It can be understood that the first interface can be considered as an interface provided by the file storage client to the operating system, so that the operating system can interact with the file storage client through the first interface. The FUSE module can be considered as an interface provided by the Windows operating system to the file storage client, so that the file storage client can interact with the Windows operating system through the FUSE module.

It should be noted that the embodiment of the present application does not limit the manner in which Windows sends attribute setting instructions to the file storage client, and the above is merely an exemplary description.

In this embodiment, by configuring the first interface for the file storage client as an interface for setting file extension attributes, this helps to improve the accuracy of setting file extension attributes, thereby helping to better provide file extension attribute management services.

Step 302: The file storage client determines a property setting request based on the property setting instruction and the target interface provided by the object storage service node. The target interface provided by the object storage service node is used to indicate the format of the property setting request, and the property setting request is used to request to set the target file extended attribute of the target node to the target state.

Exemplarily, the file storage client may receive the property setting instruction through the property management module, and determine the property setting request through the property management module.

In the embodiment of the present application, the target interface provided by the object storage service node may be a REST API interface. In other words, a property setting request indicating the semantics of file extension attributes (i.e., target node, target file extension attributes, target status, etc.) may be carried through the REST API interface.

In the embodiment of the present application, the property setting request may include message content, request address, operation command, etc. Among them, the format of the message content, request address and operation command adopts the format that can be defined by the REST API interface.

Exemplarily, the message content defined based on the REST API interface can be recorded in the XML Body. The message content can be recorded in the Xml Body. Based on this, the format of the message content of the property setting request adopts the format of Xml Body.

For example, the request address defined based on the REST API interface can be implemented through a uniform resource locator (URL). Based on this, the format of the request address adopts the format of the URL.

For example, the operation commands defined based on the REST API interface may include GET, PUT, HEAD, DELETE, POST, etc.

Among them, the format of Xml Body and the format of URL can be referred to the description in the relevant technology, which will not be repeated here.

In this embodiment, when the target interface provided by the object storage service node is a REST API interface, the message content of the property setting request adopts the format of Xml Body, the request address adopts the format of URL, and the operation command can be GET, PUT, HEAD, DELETE, POST, etc., so that the property setting request adopts the format of the REST API interface, which helps the object storage service node to accurately identify the content requested by the property setting request, thereby facilitating the accuracy of the file extension attribute management operations performed by the object storage service node.

It should be noted that the embodiment of the present application does not limit the type of target interface provided by the object storage service node, and the above is only an exemplary description.

In the embodiment of the present application, the attribute setting request may include a first field, wherein the first field is used to indicate a file extension attribute.

Exemplarily, the first field may be “winmode.” “win” in “winmode” is used to indicate a Windows operating system, and “mode” is used to indicate a file extension attribute.

Exemplarily, the request address may include a first field, and the format of the first field in the request address may be "?winmode". By adding the first field indicating the file extension attribute in the request address, it is possible to indicate that the attribute setting request is a request related to the file extension attribute, which helps to improve the accuracy of file extension attribute management.

Exemplarily, the message content may include a first field, and the format of the first field in the message content may be "<winmode></winmode>". By adding a field indicating the file extension attribute to the message content, it is helpful for the object storage node to accurately locate the content requested by the attribute setting request, thereby helping to improve the accuracy and efficiency of file extension attribute management.

In the embodiment of the present application, the attribute setting request realizes the request to set the target file extended attribute of the target node to the target state by indicating the target node, the target file extended attribute and the target state. Among them, the attribute setting request indicates the target node, the target file extended attribute and the target state, including multiple implementation methods, and the following is exemplified by method 1 and method 2.

Mode 1: The attribute setting request indicates the extended attributes of the target file through the message content and indicates the target status through the operation command.

Exemplarily, the message content of the attribute setting request may include a second field, and the second field is used to indicate an extended attribute of the target file.

Optionally, the second field may include a name of the target file extension attribute and a value of the target file extension attribute, wherein the value of the target file extension attribute is a value of the target file extension attribute in the Windows operating system.

In this embodiment, by setting the value of the target file extension attribute to the value of the target file extension attribute in the Windows operating system, the value of the target file extension attribute in the semantics of the object storage is the same as the value in the Windows operating system, thereby helping to improve the convenience and accuracy of the file storage client when performing semantic conversion, and further helping to improve the convenience and accuracy of file extension attribute management.

Exemplarily, when the target file extended attribute includes a read-only attribute, the second field may include “<FileAttributeReadonly>0x00000001</FileAttributeReadonly>”. The “FileAttribute” in “FileAttributeReadonly” is a prefix used to indicate the file extended attribute, and “Readonly” is used to indicate the name of the file extended attribute, that is, the “read-only attribute”. “0x00000001” is used to indicate the value of the file extended attribute, that is, the value of the target file extended attribute, and “0x” is used to indicate hexadecimal, that is, the hexadecimal value of the read-only attribute is “00000001”.

Exemplarily, when the attribute setting instruction indicates 22 file extension attributes, the attribute setting request also indicates 22 file extension attributes. Based on this, the message content of the attribute setting request may be as follows:

<winmode>

<FileAttributeReadonly>0x00000001</FileAttributeReadonly>

<FileAttributeHidden>0x00000002</FileAttributeHidden>

<FileAttributeSystem>0x00000004</FileAttributeSystem>

<FileAttributeDirectory>0x00000010</FileAttributeDirectory>

<FileAttributeArchive>0x00000020</FileAttributeArchive>

<FileAttributeDevice>0x00000040</FileAttributeDevice>

<FileAttributeNormal>0x00000080</FileAttributeNormal>

<FileAttributeTemporary>0x00000100</FileAttributeTemporary>

<FileAttributeSparseFile>0x00000200</FileAttributeSparseFile>

<FileAttributeReparsePoint>0x00000400</FileAttributeReparsePoint>

<FileAttributeCompressed>0x00000800</FileAttributeCompressed>

<FileAttributeOffline>0x00001000</FileAttributeOffline>

<FileAttributeNotContentIndexed>0x00002000</FileAttributeNotContentIndexed>

<FileAttributeEncrypted>0x00004000</FileAttributeEncrypted>

<FileAttributeIntegrityStream>0x00008000</FileAttributeIntegrityStream>

<FileAttributeVirtual>0x00010000</FileAttributeVirtual>

<FileAttributeNoScrubData>0x00020000</FileAttributeNoScrubData>

<FileAttributeEA>0x00040000</FileAttributeEA>

<FileAttributePinned>0x00080000</FileAttributePinned>

<FileAttributeUnpinned>0x00100000</FileAttributeUnpinned>

<FileAttributeRecallOnOpen>0x00200000</FileAttributeRecallOnOpen>

<FileAttributeRecallOnDataAccess>0x00400000</FileAttributeRecallOnDataAccess>

</winmode>

Since the binary value corresponding to "0x00000001" is 1, the binary value corresponding to "0x00000002" is 10, the binary value corresponding to "0x00000004" is 100, the binary value corresponding to "0x00000010" is 10000, ..., the binary value corresponding to "0x00400000" is 10 ²² . Based on this, the message content can also indicate the above 22 file extension attributes through a 23-bit binary string, wherein the first bit of the 23-bit string indicates the read-only attribute, the second bit indicates the attribute, the third bit indicates the system attribute, the fifth bit indicates the directory attribute, ..., and the 23rd bit indicates the call data access attribute.

It should be noted that the number of bits of the file extension attribute in the string is the same as the number of bits of the binary value of the file extension attribute. For example, the number of bits of the binary value of the read-only attribute is 1, so the first bit of the string indicates the read-only attribute.

In the embodiment of the present application, the property setting request can indicate different target states through different operation commands.

Exemplarily, the property setting request may indicate a configured state through PUT, and indicate an unconfigured state through DELETE. Based on this, when the target state is a configured state, the operation command included in the property setting request is PUT, and the property setting request may include "PUT/filesystem/dir/file?winmode". When the target state is an unconfigured state, the operation command included in the property setting request is DELETE, and the property setting request may include "DELETE/filesystem/dir/file?winmode".

It should be noted that the embodiment of the present application does not limit how the attribute setting request indicates the target state through the operation command, and the above is only an exemplary description.

In the embodiment of the present application, the property setting request may indicate the target node through the request address.

Exemplarily, the request address may be filesystem/dir/file?winmode, where "filesystem/dir/file" is used to indicate a target node.

In this implementation, the target file extended attributes are indicated by the message content, the target status is indicated by the operation command, and the target node is indicated by the request address. This helps to make full use of the functions of different parts supported by the target interface provided by the object storage service node, thereby simplifying the content of the attribute setting request, and further helping to improve the convenience and accuracy of file extended attribute management.

Mode 2: The attribute setting request indicates the target file extended attributes and the target status through the message content.

In the embodiment of the present application, the message content includes a second field and a third field. The second field is used to indicate the target file extension attribute, and the third field is used to indicate the target status.

It should be noted that for the relevant description of the second field, please refer to the description in method 1, which will not be repeated here.

Exemplarily, when the target state is the configured state, the third field can be "put", and the format of the third field in the message content can be <Type>put</Type>, where "Type" is used for the setting type of the file extension attribute, and "put" is used to indicate the configuration of the target file extension attribute, that is, setting the target file extension attribute to the configured state.

Exemplarily, when the target state is an unconfigured state, the second field may be "delete", and the format of the third field in the message content may be <Type>delete</Type>, where "delete" is used to indicate cancellation/deletion of the target file extended attributes, that is, setting the target file extended attributes to an unconfigured state.

Exemplarily, the third field can be stored between "<winmode>" and "</winmode>", so that the third field can be used to indicate the setting type of the file extension attribute, thereby helping to improve the accuracy of the object storage service node in identifying content.

It should be noted that the embodiment of the present application does not limit the specific content of the third field, and the above is only an exemplary description.

In an embodiment of the present application, when the target file extended attributes and the target status are indicated by different fields of the message content, the request address of the attribute setting request is used to indicate the target node. Exemplarily, the attribute setting request may include "PUT/filesystem/dir/file?winmode". Among them, "filesystem/dir/file" is used to indicate the target node.

In this implementation, different fields in the message content are used to indicate the target file extended attributes and the target status. On the one hand, the object storage service node can determine the content requested by the attribute setting request by reading the message content, thereby helping to improve the efficiency of processing the attribute setting request. On the other hand, the diversity of the ways in which the attribute setting request indicates the target file extended attributes and the target status is improved.

Based on the above, if the target states of the multiple file extension attributes indicated by the attribute setting instruction are the same, that is, the target states of the multiple file extension attributes are all configured or unconfigured, then the attribute setting request can indicate the target state in mode 1, that is, indicate the target states of the multiple file extension attributes through different operation commands. Alternatively, the attribute setting request can also indicate the target state in mode 2, that is, indicate the target states of the multiple file extension attributes through the third field in the message content.

If the attribute setting instruction indicates that the target states of multiple file extension attributes are different, that is, the target state of some file extension attributes among the multiple file extension attributes is a configured state, and the target state of another part of the file extension attributes is an unconfigured state, then the attribute setting request can indicate the target state through method 2, so that the attribute setting request can indicate two different types of target states at the same time.

Step 303: The file storage client sends an attribute setting request to the object storage service node to request that the target file extended attribute of the target node be set to a target state.

In an embodiment of the present application, after the file storage client determines the attribute setting request, it sends the attribute setting request to the object storage service node, such as: the attribute setting request can be sent to the object storage service node through the attribute management module.

Exemplarily, as shown in FIG5 , the file storage client may send a property setting request to the object storage service node through a target interface provided by the object storage service node.

In the above embodiment, after receiving the attribute setting instruction, the file storage client can determine the attribute setting request based on the content indicated by the attribute setting instruction and the target interface provided by the object storage service node, so as to request that the target file extension attribute of the target node be set to the target state. After that, the file storage client sends the attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to the target state.

When it is necessary to manage file extension attributes, the file storage client determines the attribute setting request through the attribute setting instruction and the format indicated by the target interface provided by the object storage service node, so as to convert the semantics of the file extension attributes (i.e., the attribute setting instruction) into the semantics of the object storage (i.e., the attribute setting request), so that the attribute setting request can use the semantics of the object storage to indicate the content indicated by the attribute setting instruction, so that the object storage service node can accurately identify the content requested by the attribute setting request, and thus manage the file extension attributes based on the content requested by the attribute setting request. Therefore, the object storage system can improve the semantics of object storage through the scheme of the present application, so that the semantics of object storage can be compatible with file extension attributes, thereby providing file extension attribute management services on the basis of providing file services, thereby realizing the provision of more complete file services, so that object storage can be better compatible with file applications.

Fig. 6 is a schematic diagram of setting file extension attributes provided by an embodiment of the present application. In the following, the process of setting file extension attributes is exemplarily introduced in conjunction with Fig. 6.

Exemplarily, after a user triggers an attribute setting instruction or a target application sends a setting instruction to the Windows operating system, the Windows operating system calls the first interface of the file storage client through the FUSE module and sends an attribute setting instruction to the file storage client to instruct the file storage client to manage the file extension attributes of the target node, such as setting the target file extension attributes of the target node to the target state. Exemplarily, the first interface may be "sfc_win_set_attributes" and the attribute setting instruction may be "fuse_operations::win_set_attributes".

After receiving the attribute setting instruction through the first interface, the file storage client can generate an attribute setting request based on the attribute setting instruction and the target interface provided by the object storage service node. After that, the file storage client sends the attribute setting request to the object storage file storage client (OSC) of the object storage service node to request to manage the file extension attributes of the target node, such as setting the target file extension attributes of the target node to the target state.

It should be noted that in the embodiment of the present application, OSC performs a certain operation, which can be considered as the object storage service node performing a certain operation in the process of running OCS, or the object storage service node performing a certain operation through OSC, which will not be repeated later.

Based on the above embodiment, the file storage client can map the semantics of file extension attributes to the semantics of object storage, thereby generating requests that can be recognized by the object storage service node (such as: attribute setting requests, etc.), and then isolating the semantics of file extension attributes on the file storage client side, so that the semantics of file extension attributes are independent of the object storage service node, that is, the object storage service node does not need to recognize the semantics of file extension attributes.

In addition, when the file storage client generates a request that can be recognized by the object storage service node, it makes full use of the scalability of the target interface provided by the object storage service node, such as: indicating the extended attributes of the target file to be managed through the message content, indicating the management method of the file extended attributes through the operation command, etc., thereby improving the accuracy and reliability of the requests that can be recognized by the object storage service node.

Fig. 7 is a flow chart of a method for managing file extension attributes according to an exemplary embodiment. Exemplarily, the method for managing file extension attributes may include the following steps 701-703.

Step 701: The object storage service node receives a property setting request sent by a file storage client.

It should be noted that for the description of the attribute setting request, please refer to the description of step 302, which will not be repeated here.

Step 702: The object storage service node parses the property setting request through the target interface to obtain the content requested by the property setting request.

In the embodiment of the present application, the object storage service node may determine the content requested by the attribute setting request by parsing the attribute setting request. Thus, file extended attributes are managed based on the content requested by the attribute setting request.

Exemplarily, the object storage service node may parse the property setting request through a parsing module.

Exemplarily, after receiving the property setting request, the object storage service node can determine, through the first field (eg, winmode) in the request address, that the property setting request is a request related to file extension attributes.

Example 1, in combination with method 1 in step 302, an exemplary introduction to the implementation process of step 702 is given.

In the embodiment of the present application, the object storage service node can determine the extended attributes of the target file to be managed by parsing the message content of the attribute setting request.

Exemplarily, the object storage service node can determine the field indicating the extended attributes of the target file in the message content through the first field in the message content, such as “<FileAttributeReadonly>0x00000001</FileAttributeReadonly>” between “<winmode>” and “</winmode>”, thereby determining the extended attributes of the target file to be managed.

In the embodiment of the present application, the object storage service node can determine the management method of the file extension attribute by parsing the operation command of the attribute setting request, such as: setting to a configured state or setting to an unconfigured state.

Exemplarily, if the operation command in the property setting request is "PUT", the management mode is set to the configured state. If the operation command in the property setting request is "DELETE", the management mode is set to the unconfigured state.

Example 2, in combination with method 2 in step 302, an exemplary introduction to the implementation process of step 702 is given.

In an embodiment of the present application, the object storage service node can determine the management method of the file extension attributes by parsing the message content of the attribute setting request.

Exemplarily, the object storage service node can determine the management mode of the file extension attribute through the third field in the message content, such as the third field between "<winmode>" and "</winmode>", thereby determining the state to be set (i.e., the target state) of the target file extension attribute. If the message content includes "<Type>put</Type>", that is, the third field is "put", the management mode is set to the configured state, that is, the state to be set of the target file extension attribute is the configured state; if the message content includes "<Type>delete</Type>", that is, the third field is "delete", the management mode is set to the unconfigured state, that is, the state to be set of the target file extension attribute is the unconfigured state.

It should be noted that for other related instructions of Example 2, please refer to the instructions of Example 1, which will not be repeated here.

Optionally, the file extension attribute management method may further include the following S1-S4.

S1: The object storage service node determines the value of the target file's extended attribute by parsing the attribute setting request.

Exemplarily, “<FileAttributeReadonly>0x00000001</FileAttributeReadonly>” in the message content is used to indicate the value of the read-only attribute, “Readonly” is used to indicate the read-only attribute, and “0x00000001” is used to indicate the value.

S2: The object storage service node determines whether the value of the target file extension attribute is the same as the target value.

The target value is the value of the extended attribute of the target file in the Windows operating system.

In the embodiment of the present application, the object storage service node stores a target value of the target file extension attribute, and the target value is the value of the target file extension attribute in the Windows operating system. After the object storage service node parses the value of the target file extension attribute from the message content, it compares the value of the target file extension attribute with the target value. If they are the same, it is considered that the value of the target file extension attribute has passed the verification. Otherwise, if they are different, it is considered that the value of the target file extension attribute has not passed the verification.

For example, the value of the read-only attribute in the Windows operating system is 0x00000001, that is, the target value is 0x00000001. Therefore, if the value of the read-only attribute is <FileAttributeReadonly>0x00000001</FileAttributeReadonly>, it means that the value of the target file extended attribute is the same as the target value of the target file extended attribute. If the value of the read-only attribute is a non-target value, such as: "<FileAttributeReadonly>0x00000002</FileAttributeReadonly>", it means that the value of the target file extended attribute is different from the target value of the target file extended attribute.

S3: If the value of the target file extension attribute is the same as the target value, the object storage service node executes step 703.

In this embodiment, the target file extended attribute is set to the target state only when the value of the target file extended attribute is the same as the target value of the target file extended attribute, which helps to ensure the accuracy of the managed target file extended attribute.

S4: If the value of the target file's extended attribute is different from the target value, the object storage service node returns a prompt message to the file storage client, where the prompt message is used to indicate that there is an error in the value of the target file's extended attribute.

In this embodiment, when the value of the target file extension attribute is different from the target value of the target file extension attribute, a prompt message is returned to the file storage client to prompt that there is an error in the value of the target file extension attribute, which helps to correct the error of the file storage client in time.

Step 703: The object storage service node sets the target file extended attribute of the target node to the target state based on the content requested by the attribute setting request.

In the embodiment of the present application, after the object storage service node obtains the content requested by the attribute setting request, it executes the content requested by the attribute setting request, that is, sets the target file extended attribute of the target node to the target state.

There are multiple implementation methods for setting the target file extension attribute of the target node to the target state. The following is an exemplary description using Method A and Method B.

Method A: When the object storage service node indicates the state of each file extension attribute of the target node through a string (such as a target string), different bits of the target string are used to indicate different file extension attributes. Based on this, the object storage service node can set the target file extension attribute of the target node to the target state by modifying the value of the target bit of the target string.

It should be noted that based on the setting method of method A, when each file extension attribute of the target node is modified at the same time, it is equivalent to modifying the value of each bit of the target field. Based on this, it can be considered that the new state of the file extension attribute is used to overwrite the historical state of the file extension attribute.

In an embodiment of the present application, when the target state is a configured state, the object storage service node may set the target bit of the target string to a first value; the target bit is used to indicate an extended attribute of the target file, and the first value is used to indicate a configured state.

Exemplarily, the target string is a 23-bit binary string, wherein the first bit indicates the state of the read-only attribute. If the content of the attribute setting request is to set the read-only attribute to the configured state, the object storage service node may set the value of the first bit to 1 (i.e., the first value), thereby indicating that the read-only attribute is in the configured state.

In an embodiment of the present application, when the target state is an unconfigured state, the object storage service node may set the target bit of the target string to a second value; the second value is used to indicate an unconfigured state.

Exemplarily, the target string is a 23-bit binary string, wherein the second bit indicates the state of the hidden attribute. If the content of the attribute setting request is to set the hidden attribute to an unconfigured state, the object storage service node may set the value of the second bit to 0 (i.e., the second value), thereby indicating that the hidden attribute is in an unconfigured state.

In this embodiment, multiple file extension attributes of the target node are indicated by a character string, which not only helps improve the efficiency of subsequent updating, searching, and deleting file extension attributes, but also helps reduce the storage space occupied by the fields indicating file extension attributes.

In the embodiment of the present application, the target string can be stored in association with the identifier of the target node. For example, the target string can be stored in the metadata of the target object. In this way, when updating the file extension attribute of the target node, it helps to improve the convenience and accuracy of determining the target string.

Method B: The object storage service node indicates multiple file extension attributes of the target node through multiple fields, where one field is used to indicate one file extension attribute, such as the target field is used to indicate the target file extension attribute. Based on this, the object storage service node can set the target file extension attribute of the target node to the target state by generating a target field or deleting a target field.

In the embodiment of the present application, when the target state is in the configured state, the object storage service node can generate a target field and store the target field. The target field is used to indicate that the target file extension attribute has been configured. That is, when the object storage service node stores the target field, it indicates that the target node has configured the target file extension attribute, that is, the target file extension attribute of the target node is in the configured state.

Exemplarily, the target file extended attribute is a read-only attribute, that is, the message content of the attribute setting request includes <FileAttributeReadonly>0x00000001</FileAttributeReadonly>, based on which, the target field generated by the object storage service node may be x-obs-meta-winmode:0x0000001.

It should be noted that, based on the setting method of method B, when the state of the target file extended attribute is set to the configured state, if the target file extended attribute is set for the first time, it can be considered that the target file extended attribute is added to the target node. If it is not the first time to set the target file extended attribute, it can be considered that the state of the target file extended attribute of the target node is updated.

Exemplarily, after the object storage service node generates the target field, the target field may be stored in a non-volatile storage medium of the object storage service node, thereby achieving persistent storage of the target field.

Exemplarily, the object storage service node may store the target field based on the identifier of the target node, that is, store the identifier of the target node in association with the target field, so that when the file storage client subsequently queries the file extension attributes of the node, it can indicate the node to be queried through the node identifier.

Since the identifier of the target node is the same as the identifier of the target object, based on this, the object storage service node can store the target field in the metadata of the target object based on the identifier of the target node, thereby realizing the associated storage of the target field and the identifier of the target node.

In the embodiment of the present application, when the target state is in the unconfigured state, the object storage service node can delete the target field of the target node. That is, when the object storage service node does not store the target field, it means that the target node is not configured with the target file extension attribute, that is, the target file extension attribute of the target node is in the unconfigured state.

It should be noted that, based on the setting method of method B, when the state of the target file extended attribute is set to the unconfigured state, it can be considered that the target file extended attribute that has been configured on the target node is deleted.

Exemplarily, the target file extended attribute is a hidden attribute, and the target field may be x-obs-meta-winmode:0x00000002. The object storage service node may delete x-obs-meta-winmode:0x00000002 to set the target file extended attribute to an unconfigured state.

In this embodiment, multiple fields are used to indicate multiple file extension attributes of the target node, which helps to improve the independence, thereby helping to improve the accuracy of the indicated file extension attributes.

In the above embodiment, after the object storage service node receives the attribute setting request sent by the file storage client, it determines the content requested by the attribute setting request by parsing the attribute setting request, and then sets the target file extension attribute of the target node to the target state based on the content requested by the attribute setting request, thereby completing the management of the file extension attributes.

Since the property setting request is determined according to the interface provided by the object storage service node, the property setting request indicates the requested content through the semantics of the object storage, so that the object storage service node can accurately identify the requested content of the property setting request, thereby ensuring the management of file extension attributes. Therefore, the object storage system can improve the semantics of object storage through the solution of the present application, so that the semantics of object storage can be compatible with file extension attributes, thereby providing file extension attribute management services on the basis of providing file services, and further providing more complete file services, so that object storage can be better compatible with file applications.

Based on the above embodiments, the object storage service node of the object storage system can determine the management method of file extension attributes by parsing the attribute setting request using object storage semantics, and manage the file extension attributes based on the management method of file extension attributes indicated by the attribute setting request, thereby realizing the intercommunication between file extension attribute semantics and object storage semantics.

In addition, the object storage service node supports the parsing, management, storage, and query of file extension attribute related content, thereby realizing the functional implementation of the interface that supports the management of file extension attributes (i.e., the target interface), thereby enabling the object storage system to provide more complete file extension attribute management functions.

The above is the first part of the embodiment of the present application. The second part of the embodiment of the present application is introduced below in conjunction with Figures 8 to 13.

Fig. 8 is a flow chart of a method for managing file extension attributes according to an exemplary embodiment. Exemplarily, the method for managing file extension attributes may include the following steps 801-803.

Step 801: The file storage client receives an attribute acquisition instruction, where the attribute acquisition instruction is used to instruct to acquire file extended attributes of a target node.

In the embodiment of the present application, the attribute acquisition instruction indicates the target node, which helps to prevent the file storage client from acquiring file extension attributes of non-target nodes, thereby helping to ensure the accuracy of subsequent operations performed by the file storage client.

In an embodiment of the present application, the attribute acquisition instruction may be an instruction triggered by a user, such as when a user views the file extension attributes of a target node through an electronic device, the operating system responds to the user's triggering operation and sends an attribute acquisition instruction to the file storage client to instruct the file storage client to obtain the file extension attributes of the target node.

Alternatively, the attribute acquisition instruction can be an instruction triggered by the target application. For example, during the process of electronically setting up and running the target application, if it is necessary to query the file extension attributes of the target node, the target application can send a first query instruction to the operating system to instruct the query of the file extension attributes of the target node. After receiving the first query instruction, the operating system sends an attribute acquisition instruction to the file storage client to instruct the file storage client to obtain the file extension attributes of the target node.

The following is an exemplary introduction to the manner in which the operating system sends an attribute acquisition instruction to the file storage client.

In the embodiment of the present application, the Windows operating system can send a property acquisition instruction to the file storage client through the FUSE module.

Exemplarily, after a user triggers a property acquisition instruction, or a target application sends a first query instruction to Windows, the Windows operating system sends a property setting instruction to the FUSE module, so that the FUSE module sends the property setting instruction to the file storage client.

In the embodiment of the present application, the file storage client is configured with a second interface, and the second interface is used to instruct to obtain the file extension attribute. On this basis, the Windows operating system can send the attribute acquisition instruction to the file storage client by calling the second interface.

Exemplarily, as shown in FIG9 , after receiving the attribute acquisition instruction sent by the operating system, the FUSE module sends the attribute acquisition instruction to the file storage client by calling the second interface.

Exemplarily, the second interface may be win_get_file_attribute, wherein "set" is used to represent acquisition.

It can be understood that the second interface can be considered as an interface provided by the file storage client to the operating system, so that the operating system can interact with the file storage client through the second interface to query the file extension attributes of the node.

It should be noted that the embodiment of the present application does not limit the manner in which Windows sends attribute acquisition instructions to the file storage client, and the above is merely an exemplary description.

In this embodiment, by configuring the second interface for the file storage client as an interface for querying file extension attributes, this helps to improve the query accuracy of file extension attributes, thereby helping to better provide file extension attribute management services.

It should be noted that for other related instructions about step 801, please refer to the instructions of step 301, which will not be repeated here.

Step 802: The file storage client obtains the file extended attributes of the target node based on the attribute acquisition instruction.

In the embodiment of the present application, after receiving the attribute acquisition instruction, the file storage client obtains the file extended attribute of the target node according to the node identifier indicated by the attribute acquisition instruction, that is, the identifier of the target node.

Exemplarily, the file storage client may obtain the file extension attributes of the target node through the attribute management module.

There are multiple implementation methods for obtaining the file extension attribute of the target node. The following is an exemplary description using method a to method b.

Mode a: The file storage client may obtain the file extension attribute of the target node from the storage medium of the electronic device.

In the embodiment of the present application, the electronic device includes a first storage medium (i.e., a local storage medium of the electronic device), and the first storage medium can store file extension attributes of at least one node on the directory tree. On this basis, after receiving the attribute acquisition instruction, the file storage client can obtain the file extension attributes of the target node from the first storage medium, such as: obtaining the file extension attributes corresponding to the identifier of the target node.

Exemplarily, the first storage medium may be a cache, a memory, etc. It should be noted that the embodiment of the present application does not limit the type of storage medium, and the above is only an exemplary description.

In this manner, by acquiring the file extension attribute of the target node from the local storage medium of the electronic device, it is helpful to improve the efficiency of acquiring the file extension attribute.

Method b: The file storage client can obtain the file extended attributes of the target node from the object storage service node.

In this way, by obtaining the file extension attributes of the target node from the object storage service node, it helps to improve the accuracy of the obtained file extension attributes.

Example 1: After receiving the attribute acquisition instruction, the file storage client can first acquire the file extended attributes of the target node from the local storage medium of the electronic device. If the acquisition fails, the file extended attributes of the target node are acquired from the object storage service node. This helps to improve the efficiency of acquiring file extended attributes.

Example 2: After the file storage client receives the attribute acquisition instruction, if the file extension attribute of the target node is stored in the local storage medium of the electronic device, the file storage client determines whether the file extension attribute of the target node in the local storage medium meets the target condition. If so, the file extension attribute of the target node is acquired from the local storage medium; if not, the file extension attribute of the target node is acquired from the object storage service node. This helps to ensure the accuracy of the acquired file extension attribute.

Wherein, satisfying the target condition means that the value of the file extension attribute in the local storage medium is the same as the value of the file extension attribute in the Windows operating system. Not satisfying the target condition means that the value of the file extension attribute in the local storage medium is different from the value of the file extension attribute in the Windows operating system.

It should be noted that for other related instructions of Example 2, please refer to the instructions of S1-S4 above, which will not be repeated here.

Example 3: After receiving the attribute acquisition instruction, the file storage client can directly acquire the file extension attributes of the target node from the object storage service node, that is, regardless of whether the target condition is met, the file storage client acquires the file extension attributes of the target node from the object storage service node. This helps to ensure the accuracy of the acquired file extension attributes.

The following is an illustrative description of the implementation process of method b through S5-S7.

S5: The file storage client sends an attribute acquisition request to the object storage service node based on the attribute acquisition instruction.

The attribute acquisition request is used to request to acquire the file extended attributes of the target node.

In the embodiment of the present application, the attribute acquisition request indicates the target node. Exemplarily, the attribute acquisition request may include the identifier of the target node, which helps to ensure the accuracy of the acquired file extension attributes. In addition, the attribute acquisition request also indicates the file extension attributes. This helps to ensure the accuracy of the acquired information.

In an embodiment of the present application, the file storage client can determine the attribute acquisition request through the target interface provided by the object storage service node. The attribute acquisition request may include an operation command and a request address. The operation command can be used to obtain file extended attributes, and the request address can be used to indicate the target node.

Exemplarily, the attribute acquisition request may be “HEAD/filesystem/dir/file?winmode.” “?winmode” is used to indicate that the attribute acquisition request is a request related to file extended attributes, “HEAD” is an operation command for indicating acquisition of file extended attributes, and “filesystem/dir/file” is used to indicate a target node.

Exemplarily, as shown in FIG. 9 , the file storage client may send a property acquisition request to the object storage service node through a target interface provided by the object storage service node.

It should be noted that for the description of the attribute acquisition request, please refer to the description of the attribute setting request, which will not be repeated here.

S6: The object storage service node returns the file extended attributes of the target node to the file storage client based on the received attribute acquisition request.

In an embodiment of the present application, after receiving the attribute acquisition request, the object storage service node obtains the file extension attributes of the target node based on the content requested by the attribute acquisition request, and returns the file extension attributes of the target node to the file storage client.

Example 1: In combination with the method A in step 703 above, the object storage service node can return the target string of the target node to the file storage client, which helps to improve the data transmission efficiency.

Example 2: In combination with the method B in step 703, the object storage service node can return multiple fields of the target node to the file storage client, which helps improve the processing efficiency of the file storage client after receiving the file extension attributes of the target node.

Example 3: In combination with method B in step 703 above, the object storage service node may merge multiple fields into one field and return the merged field to the file storage client.

Exemplarily, the target node is configured with only a read-only attribute and a hidden attribute, wherein the field corresponding to the read-only attribute is x-obs-meta-winmode:0x00000001, and the field corresponding to the hidden attribute is x-obs-meta-winmode:0x00000002. Based on this, the object storage service node can merge the field corresponding to the read-only attribute and the field corresponding to the hidden attribute into winmode: 0x00000003, and return winmode: 0x00000003 to the file storage client.

It should be noted that for other related instructions of S6, reference can be made to the instructions of step 702, which will not be repeated here.

S7: The file storage client receives the file extension attributes of the target node sent by the object storage service node.

In one example, in combination with Example 1 and Example 3 in S6 above, after the file storage client receives the content returned by the object storage service node, it can parse the content returned by the object storage service node, such as: by parsing winmode: 0x00000003, winmode: 0x00000001, winmode: 0x00000002, etc. are obtained, and the parsed fields are returned to the operating system, that is, winmode: 0x00000001 and winmode: 0x00000002 are returned to the operating system.

In another example, combined with Example 2 in S2 above, after the file storage client receives the fields returned by the object storage service node, it can transmit the fields returned by the object storage service node to the operating system.

In the above embodiment, the file storage client determines the attribute acquisition request by extending the target interface provided by the object storage service node, thereby realizing the acquisition of the file extension attributes of the target node separately through the attribute acquisition request, so that the object storage system can provide more complete file extension attribute management services.

Optionally, the file extension attribute management method may further include: the file storage client writes the file extension attribute of the target node obtained from the object storage service node into the storage medium of the electronic device.

In this embodiment, the file extension attributes of the target node obtained from the object storage service node are stored in the local storage medium of the electronic device. In this way, when the file extension attributes of the target node need to be obtained later, they can be directly obtained from this storage medium, which helps to improve the efficiency of data acquisition.

Step 803: The file storage client returns the file extended attributes of the target node based on the attribute acquisition instruction.

In the embodiment of the present application, after the file storage client obtains the file extension attributes of the target node, it returns the file extension attributes of the target node to the sender of the attribute acquisition instruction, such as returning it to the operating system.

In the above embodiment, after receiving the attribute acquisition instruction, the file storage client can obtain the file extension attributes of the target node based on the attribute acquisition instruction, and return the file extension attributes of the target node, thereby providing a query service for the file extension attributes, which in turn helps the object storage system provide a more complete file extension attribute management service.

Fig. 10 is a schematic diagram of obtaining file extension attributes provided by an embodiment of the present application. In the following, the process of obtaining file extension attributes is exemplarily introduced in conjunction with Fig. 10 .

Exemplarily, after the user triggers the attribute acquisition instruction or the target application sends the first query instruction to the Windows operating system, the Windows operating system calls the second interface of the file storage client through the FUSE module and sends the attribute acquisition instruction to the file storage client to instruct the file storage client to query the file extended attributes of the target node. Exemplarily, the second interface may be "sfc_win_get_attributes" and the attribute acquisition instruction may be "fuse_operations::win_get_attributes".

After receiving the attribute acquisition instruction, the file storage client can obtain the file extension attributes of the target node from the local storage medium of the electronic device. If the acquisition is successful, the file extension attributes of the target node are returned to the Windows operating system. If the acquisition fails, an attribute acquisition request is generated and sent to the object storage service node to obtain the file extension attributes of the target node from the object storage service node. On this basis, the file storage client can write the file extension attributes of the target node obtained from the object storage node into the local storage medium of the electronic device, and return the file extension attributes of the target node obtained from the object storage node to the Windows operating system.

It should be noted that for other descriptions of FIG. 10 , reference can be made to the description of FIG. 6 , which will not be repeated here.

In the embodiment of the present application, the file extension attribute management method may also include the following S8-S10.

S8: The file storage client receives a metadata acquisition instruction, where the metadata acquisition instruction is used to instruct the acquisition of metadata of a target node.

S9: The file storage client obtains target metadata of the target node based on the metadata acquisition instruction, wherein the target metadata of the target node includes file extension attributes of the target node.

The following is an exemplary introduction to obtaining target metadata of a target node through two implementation methods.

In one implementation, the file storage client may obtain the target metadata of the target node from the storage medium of the electronic device, which helps to improve the efficiency of obtaining the target metadata.

Exemplarily, the electronic device includes a second storage medium (i.e., a local storage medium of the electronic device), and the second storage medium stores target metadata of at least one node on the directory tree. On this basis, after receiving the metadata acquisition instruction, the file storage client can acquire the target metadata of the target node from the second storage medium.

It should be noted that for the relevant description of the second storage medium, reference may be made to the description of the first storage medium, which will not be repeated here.

Exemplarily, the second storage medium and the first storage medium may be different storage media on the electronic device, so that the file extension attributes or target metadata of the node can be stored separately through different storage media, thereby facilitating the convenience of data search. Alternatively, the second storage medium and the first storage medium may be the same storage medium on the electronic device, thus helping to avoid occupying too much storage medium.

In another implementation, the file storage client may obtain the target metadata of the target node from the object storage service node, which helps to improve the accuracy of the obtained target metadata.

In an embodiment of the present application, after receiving the metadata acquisition instruction, the file storage client may send a metadata acquisition request to the object storage service node, and the metadata acquisition request is used to request the metadata of the target node. Exemplarily, the metadata acquisition request may be "HEAD/filesystem/dir/file". After receiving the metadata acquisition request, the object storage service node acquires the target metadata of the target node based on the content requested by the metadata acquisition request, and returns the target metadata of the target node to the file storage client.

Exemplarily, the target metadata of the target node may also include inode data and Dtree data, etc.

S10: The file storage client returns target metadata of the target node based on the metadata acquisition instruction.

It should be noted that for other related instructions of S8-S10, reference can be made to the instructions of step 802 above, which will not be repeated here.

In the above embodiment, after receiving the metadata acquisition instruction, the file storage client obtains and returns the target metadata of the target node, which includes the file extension attributes of the target node, thereby providing more comprehensive metadata, which in turn helps the object storage system to provide more complete file extension attribute management services.

Fig. 11 is a schematic diagram of a method for obtaining metadata provided by an embodiment of the present application. The following is an exemplary introduction to the process of obtaining metadata in conjunction with Fig. 11.

Exemplarily, after the user triggers the metadata acquisition instruction or the target application sends the second query instruction to the Windows operating system, the Windows operating system calls the third interface of the file storage client through the FUSE module and sends the metadata acquisition instruction to the file storage client to instruct the file storage client to query the metadata of the target node. Exemplarily, the third interface may be "sfc_get_attributes"/"sfc_getattr_obs", and the metadata acquisition instruction may be "fuse_operations::getattributes".

After receiving the metadata acquisition instruction, the file storage client can obtain the target metadata of the target node from the local storage medium of the electronic device. If the acquisition is successful, the target metadata of the target node is returned to the Windows operating system. If the acquisition fails, a metadata acquisition request is generated and sent to the object storage service node to obtain the target metadata of the target node from the object storage service node. After receiving the metadata acquisition request, the object storage service node returns the target metadata of the target node to the file storage client based on the metadata acquisition request.

On this basis, the file storage client can write the target metadata of the target node obtained from the object storage node into the storage medium of the electronic device, and return the target metadata of the target node obtained from the object storage node to the Windows operating system.

It should be noted that for other descriptions of FIG. 11 , reference can be made to the description of FIG. 6 , which will not be repeated here.

In the embodiment of the present application, the file extension attribute management method may also include the following S11-S13.

S11: The file storage client receives a directory listing instruction, where the directory listing instruction is used to indicate the listing of a target directory.

Here, listing a directory (ie, readdir directory) is to list at least one file/subdirectory under the directory when opening the directory, that is, for example, to display at least one file/subdirectory under the directory to the user.

Exemplarily, after the user opens the target directory, the operating system triggers a readdir operation and sends a directory listing instruction to the file storage client to instruct the file storage client to list the target directory.

S12: The file storage client obtains target metadata of the target directory based on the directory listing instruction; the target metadata of the target directory includes file extension attributes of at least one file/subdirectory under the target directory.

The at least one file under the target directory includes a file under a first-level directory of the target directory.

The following is an exemplary introduction to obtaining target metadata of a target directory through two implementation methods.

In one implementation, the file storage client may obtain the target metadata of the target directory from the storage medium of the electronic device, which helps to improve the efficiency of obtaining the target metadata.

Exemplarily, the electronic device includes a third storage medium (i.e., a local storage medium of the electronic device), and the third storage medium stores target metadata of at least one directory on the directory tree, such as file extension attributes of files/subdirectories under at least one directory. Based on this, after receiving the directory listing instruction, the file storage client can obtain the target metadata of the target directory from the third storage medium.

It should be noted that for the relevant description of the third storage medium, reference may be made to the description of the first storage medium, which will not be repeated here.

Exemplarily, the third storage medium and the first storage medium/second storage medium may be different storage media on the electronic device. In this way, the file extension attributes/target metadata of the node and the target metadata of the enumerated directory may be stored separately through different storage media, thereby facilitating data search.

In another implementation, the file storage client can obtain the target metadata of the target directory from the object storage service node. Helps improve the accuracy of the acquired target metadata.

In an embodiment of the present application, after receiving a directory listing instruction, the file storage client may send a directory listing request to the object storage service node, where the directory listing request is used to request metadata of the listed target directory. Exemplarily, the directory listing request may be "GET/filesystem/dir/file". After receiving the directory listing request, the object storage service node obtains the target metadata of the target directory based on the content requested by the directory listing request, thereby obtaining target metadata of at least one file/subdirectory under the target directory, wherein the target metadata of at least one file/subdirectory under the target directory includes file extension attributes of at least one file/subdirectory under the target directory. Afterwards, the object storage service node may return the target metadata of at least one file/subdirectory under the target directory to the file storage client.

S13: The file storage client returns target metadata of the target directory based on the directory listing instruction.

It should be noted that for other related instructions of S11-S13, reference can be made to the instructions of step 802 above, which will not be repeated here.

In the above embodiment, after receiving the directory listing instruction, the file storage client obtains and returns the target metadata of the target directory, and the target metadata includes the file extension attributes of at least one file/subdirectory under the target directory, thereby providing more comprehensive metadata when listing directories, which in turn helps the object storage system provide more complete file extension attribute management services.

Fig. 12 is a schematic diagram of a directory listing provided in an embodiment of the present application. In the following, in conjunction with Fig. 12, the process of listing targets is exemplarily introduced.

Exemplarily, after the user triggers the directory listing instruction or the target application sends the third query instruction to the Windows operating system, as shown in Figure 13, the Windows operating system calls the fourth interface of the file storage client through the FUSE module and sends the directory listing instruction to the file storage client to instruct the file storage client to list the target directory. Exemplarily, the fourth interface can be "sfc_readdir_attributes"/"sfc_readdir_obs", and the directory listing instruction can be "fuse_operations::readdir".

After receiving the directory enumeration instruction, the file storage client can obtain the target metadata of the target directory from the local storage medium of the electronic device. If the acquisition is successful, the target metadata of the target directory is returned to the Windows operating system. If the acquisition fails, a directory enumeration request is generated and sent to the object storage service node to obtain the target metadata of the target directory from the object storage service node. After receiving the directory enumeration request, the object storage service node returns the target metadata of the target directory to the file storage client.

On this basis, the file storage client can write the target metadata of the target directory obtained from the object storage node into the storage medium of the electronic device, and return the target metadata of the target directory obtained from the object storage node to the Windows operating system.

It should be noted that for other descriptions of FIG. 12 , reference can be made to the description of FIG. 6 , which will not be repeated here.

In the embodiment of the present application, the file extension attribute management method may further include the following S14-S16.

S14: The file storage client receives a deletion instruction, where the deletion instruction is used to instruct to delete a target node.

S15: The file storage client sends a deletion request to the object storage service node based on the deletion instruction, wherein the deletion request is used to request deletion of target metadata of the target node.

In an embodiment of the present application, after receiving the deletion instruction, the file storage client will send a deletion request to the object storage service node on the basis of sending a request to delete the target node, so as to request to delete the target metadata of the target node, thereby deleting the information related to the target node on the object storage service node and avoiding useless data occupying the storage space of the object storage service node.

S16: The object storage service node deletes the file extension attribute of the target node based on the received deletion request.

In an embodiment of the present application, after receiving a deletion request, the object storage service node will delete the file extension attributes of the target node on the basis of deleting the metadata such as the inode data and Dtree data of the target node, thereby completely clearing the information related to the target node.

For the related description of S14-S16, please refer to the description of the above step 802, which will not be repeated here.

In the above embodiment, after the file storage client receives the deletion instruction requesting to delete the target node, it sends a deletion request to the object storage service node to request to delete the metadata of the target node. After receiving the deletion request, the object storage service deletes the target node file extension attributes. In this way, after deleting the target node, it helps to completely clear the data related to the target node, thereby helping to avoid useless data occupying the storage space of the object storage service node.

The above is the second part of the embodiment of the present application. The following is an introduction to the third part of the embodiment of the present application in conjunction with Figures 14 to 16.

In the embodiment of the present application, based on the implementation mode of file extension attributes, file extension attributes can be divided into first type file extension attributes and second type file extension attributes. The first type file extension attributes can be implemented by the file storage client, and the second type file extension attributes can be implemented by the operating system.

Exemplarily, the first type of file extension attributes may include read-only attributes, encryption attributes, compression attributes, etc. The second type of file extension attributes may include hidden attributes, system attributes, etc.

Since the operations performed by the file storage client in the process of implementing the first type of file extension attributes are obtaining the file extension attributes and implementing the file extension attributes, for the file storage client, the first type of attributes can also be called function implementation type attributes.

In the process of implementing the second type of file extension attributes, the file storage client performs the operation of obtaining the file extension attributes and The extended attributes are transmitted to the operating system so that the operating system can implement the file extended attributes. Therefore, for the file storage client, the second type of attributes can also be called transparent attributes.

In the following, in conjunction with FIG. 14 to FIG. 17 , the implementation process of the first type of file extension attributes is exemplarily introduced.

In the following, in combination with FIG. 14 and FIG. 15 , the first implementation scheme is exemplarily introduced by taking the target file extension attribute of the target node as an example.

Fig. 14 is a flow chart of a method for managing file extension attributes according to an exemplary embodiment. Exemplarily, the method for managing file extension attributes may include the following steps 1401-1403.

Step 1401: The file storage client receives a target instruction, where the target instruction is used to instruct to perform a target operation on a target node.

The target operation is related to the extended attributes of the target file.

In an embodiment of the present application, when a user or a target application requests to perform a target operation on a target node, the operating system may send a target instruction to the file storage client to indicate the operation requested by the user or the target application, namely, to perform the target operation on the target node.

Exemplarily, the target operation may be a write operation, based on which the target file extended attribute is a read-only attribute, that is, the write operation is related to the read-only attribute.

Step 1402: The file storage client determines a permission verification result of a target operation based on the state of the target file extended attribute.

The permission verification result includes passed verification or failed verification.

In an embodiment of the present application, after receiving the target instruction, the file storage client can obtain the file extension attributes of the target node based on the target instruction to determine the status of the target file extension attributes, and thus determine the permission verification result based on the status of the target file extension attributes.

For example, the target operation is a write operation, and the target file extended attribute is a read-only attribute. If the read-only attribute is in a configured state, that is, the target node has been configured with the read-only attribute, the permission check result is a failed check, that is, the user or the target application does not have the permission to perform a write operation on the target node. If the read-only attribute is in an unconfigured state, that is, the target node is not configured with the read-only attribute, the permission check result is a passed check, that is, the user or the file application has the permission to perform a write operation on the target node.

Exemplarily, as shown in FIG15 , after receiving the target instruction, the attribute management module can obtain the file extension attribute of the target node. Afterwards, the attribute management module can send the file extension attribute of the target node and the type of the target operation to the attribute implementation module, and the attribute implementation module determines the permission verification result of the target operation. After the attribute implementation module determines the permission verification result, it transmits the permission verification result to the attribute management module.

It should be noted that the method for obtaining the file extension attribute of the target node can refer to the description of the embodiment shown in FIG. 8 , which will not be described in detail here.

The above method for the file storage client to receive the target instruction is only an exemplary description, and the embodiments of the present application do not limit this. For example, the operating system may send the target instruction to the attribute implementation module, and the attribute implementation module instructs the attribute management to obtain the state of the target file extended attribute, and then the attribute implementation module determines the permission verification result of the target operation.

Step 1403: If the permission check result is failure to pass the check, the file storage client returns a response message based on the target instruction.

The response information is used to indicate a refusal to execute the target operation on the target node.

In an embodiment of the present application, when the file storage client determines that the permission check result of the target operation is that it fails the check, the file storage client returns a response message to the sender of the target instruction (such as: operating system) to indicate that the target operation is refused to be performed on the target node, thereby instructing the operating system to intercept the user or target application from performing the target operation on the target node.

In the above embodiment, after receiving the target instruction, the file storage client automatically obtains the file extension attribute of the target node according to the target instruction indicating the execution of the target operation on the target node, so as to determine the state of the target file extension attribute related to the target operation, thereby determining the permission verification result of the target operation. In the case where the permission verification result of the target operation fails to pass the verification, the file storage client returns a response message for indicating the refusal to execute the target operation on the target node, thereby realizing the instruction to intercept the execution of the target operation on the target node, and then realizing the target file extension attribute of the target node, such as: when the target node is configured with a read-only attribute, the user, target application, etc. are denied to execute a write operation on the target node, that is, only a read operation can be executed.

Optionally, the file extended attribute management method may further include: when the permission check result is passed, the file storage client returns first response information based on the target instruction; the first response information is used to indicate that the target operation is allowed to be performed on the target node.

In the embodiment of the present application, if the permission check result of the target operation is passed, the file storage client can return the first response information to the sender of the target instruction, such as returning the first response information to the operating system to indicate that the target operation is allowed to be performed on the target node. In this way, it helps the operating system to quickly respond to the operation request of the user or the target application.

In the following, in combination with FIG. 16 and FIG. 17 , the second implementation scheme is exemplarily introduced by taking the target file extension attribute of the target node as an example.

Fig. 16 is a flow chart of another method for managing file extension attributes according to an exemplary embodiment. Exemplarily, the method for managing file extension attributes may include the following steps 1601-1603.

When the target file extension attributes are some attributes of the first category of file extension attributes, such as encryption attributes, compression attributes, etc., after the file storage client receives the attribute setting instruction, it can implement the target file extension attributes of the target node through the following steps 1601-1603.

The following uses the example that the target node includes the first file to exemplarily illustrate steps 1601 to 1603.

Step 1601: The file storage client obtains the first file based on the attribute setting instruction.

In an embodiment of the present application, after the file storage client receives the attribute setting instruction, if the target file extension attribute indicated by the attribute setting instruction is a partial attribute of the first category of file extension attributes, such as encryption attribute, compression attribute, etc., the file storage client obtains the first file indicated by the attribute setting instruction.

In one example, the file storage client may obtain the first file from a local storage medium of the electronic device. In another example, the file storage client may send an acquisition request to the object storage service node to request to obtain the first file indicated by the attribute setting instruction.

Step 1602: The file storage client performs the operation indicated by the attribute setting instruction on the first file to obtain a second file.

In the embodiment of the present application, after the file storage client obtains the first file, it performs the operation indicated by the attribute setting instruction on the first file to obtain the second file.

Example 1, the attribute setting instruction indicates that the encryption attribute of the first file is set to a configured state, and the operation indicated by the attribute setting instruction is to perform an encryption operation. Based on this, the file storage client performs an encryption operation on the first file to obtain an encrypted file (ie, the second file).

Example 2, the attribute setting instruction indicates that the encryption attribute of the first file is set to an unconfigured state, and the operation indicated by the attribute setting instruction is to perform a decryption operation. Based on this, the file storage client performs a decryption operation on the first file to obtain a decrypted file (ie, the second file).

Example 3, the attribute setting instruction indicates that the compression attribute of the first file is set to a configured state, and the operation indicated by the attribute setting instruction is to perform a compression operation. Based on this, the file storage client performs a compression operation on the first file to obtain a compressed file (ie, the second file).

Example 4: The attribute setting instruction indicates that the compression attribute of the first file is set to an unconfigured state, and the operation indicated by the attribute setting instruction is to perform a decompression operation. Based on this, the file storage client performs a decompression operation on the first file to obtain a decompressed file (ie, the second file).

Step 1603: The file storage client sends a first storage request to the object storage service node, where the first storage request is used to request storage of the second file, wherein the first storage request includes the second file.

In an embodiment of the present application, after the file storage client obtains the second file, it can send a first storage request to the object storage service node to request the object storage service node to store the second file. After receiving the first storage request, the object storage service node stores the second file in response to the first storage request. For example, the second file can overwrite the first file.

It should be noted that steps 1601 to 1603 are illustrative examples of the first file included in the target node. When the target node includes the first directory/first subdirectory, the process of the file storage client implementing the target file extended attributes of the first directory/first subdirectory can refer to steps 1601 to 1603 and will not be repeated here.

In the above embodiment, after the file storage client receives the attribute setting instruction, if the target file extended attribute is part of the attributes of the first type of file extended attributes, such as encryption attribute, compression attribute, etc., the file storage client can obtain the first file indicated by the attribute setting instruction, and perform the operation indicated by the attribute setting instruction on the first file, such as encryption operation, decryption operation, compression operation, decompression operation, etc., so as to realize the target file extended attribute for the first file or cancel the target file extended attribute for the first file, that is, realize/cancel the attribute of the windows file extended attribute, such as: realize/cancel the encryption attribute, compression attribute, etc. Afterwards, the file storage client sends a first storage request to the object storage service node, and when requesting the object storage service node to store the first file, the file storage client can provide the object storage service node with data to be stored (i.e., the second file) that is not related to the semantics of the windows file extended attribute, so that the object storage service node does not need to care about the semantics of the windows file extended attribute of the data to be stored, that is, the object storage service node does not need to realize/cancel the file extended attribute of the data to be stored, which helps to simplify the software logic of the object storage service node on the basis of providing file extended attribute management services.

Fig. 17 is a flow chart of another method for managing file extension attributes according to an exemplary embodiment. Exemplarily, the method for managing file extension attributes may include the following steps 1701-1703.

Exemplarily, in combination with the embodiments shown in FIG. 3 and FIG. 16 , if the target state is a configured state, the file storage client may further implement the target file extended attributes of the target node through the following steps 1701 to 1703 .

The following uses the example that the target node includes the third file to exemplarily illustrate steps 1701 to 1703.

Step 1701: the file storage client receives a storage instruction, where the storage instruction is used to instruct to store a third file; the target file extension attribute of the third file is in a configured state.

In the embodiment of the present application, after the user updates the third file through the electronic device, or after the target application updates the third file, such as: adding new content to the third file, deleting part of the content in the third file, etc., the Windows operating system sends a storage instruction to the file storage client, and the storage instruction is used to instruct to store the third file. After receiving the storage instruction, the file storage client can obtain the file extension attribute of the third file to determine whether the target file extension attribute of the third file is in a configured state. If the target file extension attribute of the third file is in a configured state, step 1702 is executed. Otherwise, a storage request is directly sent to the object storage service node to request the object storage service node to store the third file.

Exemplarily, the target file extended attributes may include encryption attributes, compression attributes, etc., and the encryption attributes, compression attributes, etc. of the third file are Configured state.

It should be noted that the third file and the second file may be the same file, or may be different files, and this embodiment of the present application does not limit this.

Step 1702: The file storage client performs the operation indicated by the target file extension attribute on the third file to obtain a fourth file.

In the embodiment of the present application, when it is determined that the target file extension attribute of the third file is in a configured state, the file storage client performs the operation indicated by the target file extension attribute on the third file to obtain a fourth file.

In combination with Example 1 in step 1602, the target file extended attributes of the third file include encryption attributes, the encryption attributes of the third file are in a configured state, and the operation indicated by the encryption attributes in the configured state is an encryption operation. Based on this, the file storage client performs an encryption operation on the second file to obtain an encrypted file (i.e., the fourth file).

In combination with Example 3 in step 1602, the target file extension attribute of the third file includes a compression attribute, the compression attribute of the third file is in a configured state, and the operation indicated by the compression attribute in the configured state is a compression operation. Based on this, the file storage client performs a compression operation on the second file to obtain a compressed file (i.e., the fourth file).

Step 1703: The file storage client sends a second storage request to the object storage service node, where the second storage request is used to request the object storage service node to store a fourth file; the second storage request includes the fourth file.

In the embodiment of the present application, after obtaining the fourth file, the file storage client sends a second storage request to the object storage service node to request the object storage service node to store the fourth file. After receiving the second storage request, the object storage service node stores the fourth file in response to the second storage request, such as: the fourth file can overwrite the third file.

It should be noted that steps 1701 to 1703 are illustratively described using the first file included in the target node as an example. When the target node includes the first directory/first subdirectory, the process of the file storage client implementing the target file extended attributes of the first directory/first subdirectory can refer to steps 1701 to 1703 and will not be repeated here.

In the above embodiment, after the file storage client receives the storage instruction, if the target file extension attribute of the file indicated by the storage instruction is in a configured state, the file storage client first performs the operation indicated by the target file extension attribute on the third file indicated by the storage instruction to obtain the fourth file, thereby realizing the target file extension attribute for the updated third file, thereby helping to ensure the accuracy of the provided file extension attribute.

In the following, in conjunction with FIG. 18 , an exemplary introduction is given to the implementation of the second type of file extension attributes.

Exemplarily, taking the hidden attribute of the target node as an example, the implementation process of the second type of file extension attribute is introduced.

As shown in Figure 18, after the file storage client obtains the file extension attributes (including hidden attributes) of the target node, it can directly transmit the file extension attributes of the target node to the operating system, that is, transparently transmit to the operating system. After the operating system receives the file extension attributes of the target node, if the target node has been configured with hidden attributes, the operating system displays the target node according to the current display rule.

Exemplarily, if the current display rule is "show hidden items", the operating system displays the target node according to a preset rule, such as grayscale display of the target node. If the display rule is "do not show hidden items", the operating system does not display the target node.

In this embodiment, some file extension attributes are implemented by the operating system, which helps to fully utilize the functions of the operating system and simplify the complexity of the file storage client.

The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to achieve the above functions, the file storage client/file extension attribute management device includes a hardware structure and/or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application can divide the file storage client/file extension attribute management device into functional modules according to the above method. For example, the file storage client/file extension attribute management device can include various functional modules corresponding to the various functional divisions, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

Exemplarily, FIG19 shows a possible schematic diagram of the file storage client (referred to as file storage client 1900) involved in the above-mentioned embodiment. The actions performed by the file storage client 1900 are implemented by an electronic device or by executing corresponding software through an electronic device. File storage client 1900 includes: a receiving module 1901, an attribute management module 1902 and a sending module 1903. Receiving module 1901 is used to receive an attribute setting instruction, and the attribute setting instruction indicates that the target file extension attribute of the target node is set to a target state, and the target state includes a configured state or an unconfigured state. For example, step 301 shown in FIG3. Attribute management module 1902 is used to determine an attribute setting request based on the attribute setting instruction and the target interface provided by the object storage service node; the interface provided by the object storage service node is used to indicate the attribute setting request. The format of the attribute setting request is used to request to set the target file extension attribute of the target node to the target state. For example, step 302 shown in Figure 3. The sending module 1903 is used to send the attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to the target state. For example, step 303 shown in Figure 3.

Optionally, the attribute setting request includes message content and an operation command, the message content is used to indicate the extended attribute of the target file, and the operation command is used to indicate the target status.

Optionally, the attribute setting request includes message content, and the message content is used to indicate the target file extended attributes and the target status.

Optionally, the message content includes a value of an extended attribute of the target file, and the value of the extended attribute of the target file is the same as a value of the extended attribute of the target file in the Windows operating system.

Optionally, the file storage client further includes an attribute implementation module 1904. The attribute implementation module 1904 is used to: receive a target instruction, the target instruction is used to instruct to perform a target operation on a target node; the target operation is related to the target file extension attribute; based on the state of the target file extension attribute, determine the permission verification result of the target operation; the permission verification result includes passing the verification or failing the verification; if the permission verification result is failing the verification, return response information based on the target instruction; the response information is used to indicate that the target operation is refused to be performed on the target node.

Optionally, the attribute implementation module 1904 is further used to: when the permission check result is passed, based on the target instruction, return first response information; the first response information is used to indicate that the target operation is allowed to be performed on the target node.

Optionally, when the target node is the first file, the attribute implementation module 1904 is also used to: obtain the first file based on the attribute setting instruction; perform the operation indicated by the attribute setting instruction on the first file to obtain the second file; send a first storage request to the object storage service node, the first storage request is used to request storage of the second file; the first storage request includes the second file.

Optionally, when the target node is the third file, the attribute implementation module 1904 is also used to: receive a storage instruction, the storage instruction is used to indicate the storage of the third file; the target file extension attribute of the third file is in a configured state; perform the operation indicated by the target file extension attribute on the third file to obtain a fourth file; send a storage request to the object storage service node to request the object storage service node to store the fourth file; the storage request includes the fourth file.

Optionally, the attribute management module 1902 is further used to: receive an attribute acquisition instruction, the attribute acquisition instruction is used to instruct to acquire the file extension attribute of the target node; based on the attribute acquisition instruction, acquire and return the file extension attribute of the target node.

Optionally, the attribute management module 1902 is specifically configured to: obtain the file extension attribute of the target node from the storage medium of the electronic device based on the attribute acquisition instruction.

Optionally, the attribute management module 1902 is specifically used to: obtain the file extension attribute of the target node from the object storage service node based on the attribute acquisition instruction.

Optionally, the attribute management module 1902 is further used to write the file extension attributes of the target node obtained from the object storage service node into the storage medium of the electronic device.

Optionally, the attribute management module 1902 is further used to: receive a metadata acquisition instruction, the metadata acquisition instruction is used to instruct to obtain metadata of the target node; based on the metadata acquisition instruction, obtain and return target metadata of the target node; the target metadata of the target node includes file extension attributes of the target node.

Optionally, the attribute management module 1902 is specifically configured to: obtain target metadata of the target node from a storage medium of the electronic device based on a metadata acquisition instruction.

Optionally, the attribute management module 1902 is specifically used to: obtain target metadata of the target node from the object storage service node based on the metadata acquisition instruction.

Optionally, the attribute management module 1902 is also used to: receive a directory listing instruction, the directory listing instruction is used to instruct the listing of a target directory; based on the directory listing instruction, obtain and return target metadata of the target directory; the target metadata of the target directory includes file extension attributes of at least one file/subdirectory under the target directory.

Optionally, the attribute management module 1902 is specifically configured to: obtain target metadata of the target directory from a storage medium of the electronic device based on a metadata acquisition instruction.

Optionally, the attribute management module 1902 is specifically used to: obtain target metadata of the target directory from the object storage service node based on the metadata acquisition instruction.

For the specific description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. In addition, the explanation of any file storage client 1900 provided above and the description of the beneficial effects can refer to the above corresponding method embodiments, which will not be repeated here.

Exemplarily, FIG20 shows a possible structural diagram of the file extension attribute management device (referred to as file extension attribute management device 2000) involved in the above embodiment. The actions performed by the file extension attribute management device 2000 are implemented by an object storage service node (such as a computing device) or by executing corresponding software by a computing device. The file extension attribute management device 2000 includes a receiving module 2001, a parsing module 2002 and a management module 2003. The receiving module 2001 is used to receive the attribute setting information sent by the file storage client of the object storage system. A property setting request is configured to request that a target file extension attribute of a target node be set to a target state, wherein the target state includes a configured state or an unconfigured state. For example, step 701 shown in FIG. 7 . A parsing module 2002 is configured to parse the property setting request through the target interface to obtain the content requested by the property setting request. For example, step 702 shown in FIG. 7 . A management module 2003 is configured to set the target file extension attribute of the target node to the target state based on the content requested by the property setting request. For example, step 703 shown in FIG. 7 .

Optionally, when the target state is the configured state, the management module 2003 is specifically used to: generate a target field of the target node based on the content requested by the attribute setting request; the target field of the target node is used to indicate the configured target file extended attributes; based on the identifier of the target node, store the target field of the target node.

Optionally, when the target state is an unconfigured state, the management module 2003 is specifically used to: delete the target field of the target node based on the content requested by the attribute setting request; the target field of the target node is used to indicate that the target file extended attribute has been configured.

Optionally, the object storage service node stores a target string, which is used to indicate the state of the file extension attribute of the target node; the management module 2003 is specifically used to: when the target state is a configured state, based on the content requested by the attribute setting request, set the target bit of the target string to a first value; the target bit is used to indicate the target file extension attribute, and the first value is used to indicate the configured state; when the target state is an unconfigured state, based on the content requested by the attribute setting request, set the target bit of the target string to a second value; the second value is used to indicate the unconfigured state.

Optionally, the attribute setting request includes message content and an operation command, the message content is used to indicate the extended attribute of the target file, and the operation command is used to indicate the target status.

Optionally, the attribute setting request includes message content, and the message content is used to indicate the target file extended attributes and the target status.

Optionally, the attribute setting request includes the value of the target file extended attribute; the management module 2003 is also used to: determine the value of the target file extended attribute based on the attribute setting request; when the value of the target file extended attribute is the same as the target value, set the target file extended attribute of the target node to the target state based on the content requested by the attribute setting request; the target value is the value of the target file extended attribute in the Windows operating system.

Optionally, the management module 2003 is further used to: when the value of the target file extended attribute is different from the target value, return a prompt message to the file storage client, where the prompt message is used to indicate that there is an error in the value of the target file extended attribute.

Optionally, the receiving module 2001 is further used to: receive an attribute acquisition request sent by the file storage client, the attribute acquisition request is used to request to obtain the file extension attributes of the target node; the management module 2003 is used to: return the file extension attributes of the target node to the file storage client based on the attribute acquisition request.

Optionally, the receiving module 2001 is also used for: the object storage service node receives a metadata acquisition request sent by the file storage client, and the metadata acquisition request is used to request to obtain the metadata of the target node; the management module 200 is also used for: based on the metadata acquisition request, returning the target metadata of the target node to the file storage client; the target metadata of the target node includes the file extension attributes of the target node.

Optionally, when the target node is a target directory, the receiving module 2001 is also used to: receive a directory listing request sent by the file storage client, the directory listing request is used to request to obtain the metadata of the target directory; the management module 200 is also used to: return the target metadata of the target directory to the file storage client based on the directory listing request; the target metadata of the target directory includes the file extension attributes of at least one file/subdirectory under the target directory.

Optionally, the receiving module 2001 is further used to: receive a deletion request sent by the file storage client, the deletion request is used to request deletion of metadata of the target node; the management module 2003 is further used to: delete the file extension attribute of the target node based on the deletion request.

For the detailed description of the above optional methods, please refer to the above method embodiments, which will not be repeated here. In addition, the explanation and description of the beneficial effects of any of the above file extension attribute management devices 2000 can refer to the above corresponding method embodiments, which will not be repeated here.

In the embodiment of the present application, the receiving module 2001, the parsing module 2002 and the management module 2003 can be implemented by software or by hardware. Exemplarily, the implementation of the parsing module 2002 is described below by taking the parsing module 2002 as an example. Similarly, the implementation of the receiving module 2001 and the management module 2003 can refer to the implementation of the attribute parsing module 2002.

As an example of a software functional unit, the parsing module 2002 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the parsing module 2002 may include code running on multiple hosts/virtual machines/containers. It should be noted that the multiple hosts/virtual machines/containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts/virtual machines/containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple data centers with close geographical locations. Among them, usually a region may include multiple AZs.

Similarly, multiple hosts/virtual machines/containers running the code can be distributed in the same virtual private cloud (VPC). VPC) or multiple VPCs. Usually, a VPC is set in one region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set in each VPC to realize the interconnection between VPCs through the communication gateway.

As an example of a hardware functional unit, the parsing module 2002 may include at least one computing device, such as a server, etc. Alternatively, the parsing module 2002 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

The multiple computing devices included in the analysis module 2002 can be distributed in the same region or in different regions. The multiple computing devices included in the analysis module 2002 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the analysis module 2002 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

It should be noted that, in other embodiments, the parsing module 2002 can be used to execute any step in the file extension attribute management method, the receiving module 2001 can be used to execute any step in the file extension attribute management method, and the management module 2003 can be used to execute any step in the file extension attribute management method, or the steps that the receiving module 2001, the parsing module 2002 and the management module 2003 are responsible for implementing can be specified as needed, and the receiving module 2001, the parsing module 2002 and the management module 2003 respectively implement different steps in the file extension attribute management method to realize all the functions of the file extension attribute management device.

The embodiment of the present application also provides a computing device. As shown in FIG. 21 , the computing device 210 includes: a bus 212, a processor 214, a memory 216, and a communication interface 218. The processor 214, the memory 216, and the communication interface 218 communicate with each other via the bus 212. The computing device 210 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 210.

The bus 212 may be 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, only one line is used in FIG. 21, but it does not mean that there is only one bus or one type of bus. The bus 212 may include a path for transmitting information between various components of the computing device 210 (e.g., the memory 216, the processor 214, and the communication interface 218).

The processor 214 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

The memory 216 may include a volatile memory (volatile memory), such as a random access memory (RAM). The memory 216 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

The memory 216 stores executable program codes, and the processor 214 executes the executable program codes to respectively implement the functions of the aforementioned receiving module 2001, parsing module 2002, and management module 2003, thereby implementing the file extension attribute management method. That is, the memory 216 stores instructions for executing the file extension attribute management method.

Alternatively, the memory 216 stores executable program codes, and the processor 214 executes the executable program codes to respectively implement the functions of the aforementioned receiving module 2001, parsing module 2002, and management module 2003, thereby implementing a file extension attribute management method. That is, the memory 216 stores instructions for executing a file extension attribute management method.

The communication interface 218 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 210 and other devices or communication networks.

It should be noted that the computing device 210 may be a computing device in an object storage service node (as shown in FIG. 1 and FIG. 2 ).

The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, for example, a cloud server, a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

As shown in Fig. 22, the computing device cluster 220 includes at least one computing device 210. The memory 216 in one or more computing devices 210 in the computing device cluster 220 may store the same instructions for executing the file extension attribute management method.

In some possible implementations, the memory 216 of one or more computing devices 210 in the computing device cluster 220 may also respectively store some instructions for executing the file extension attribute management method. In other words, the combination of one or more computing devices 210 may jointly execute the instructions for executing the file extension attribute management method.

It should be noted that the memory 216 in different computing devices 210 in the computing device cluster 220 may store different instructions, which are respectively used to execute part of the functions of the file extension attribute management apparatus 2000. That is, the memory 216 in different computing devices 210 may store different instructions. The instruction may implement the functions of one or more modules among the receiving module 2001 , the parsing module 2002 and the management module 2003 .

It should be noted that the computing device cluster 220 can be used as an object storage service node (as shown in Figures 1 and 2) to provide cloud services for cloud service tenants. The relevant description of at least one computing device 210 in the computing device cluster shown in Figure 22 can refer to the relevant description of the computing device shown in Figure 21, which will not be repeated here.

The following is an exemplary introduction to the connection method of the computing device cluster.

In a possible implementation, one or more computing devices in a computing device cluster (such as the computing device cluster shown in FIG. 22 ) may be connected via a network. The network may be a wide area network or a local area network, etc. FIG. 23 shows a possible implementation. As shown in FIG. 23 , two computing devices (such as computing device 210A and computing device 210B) are connected via a network. Specifically, the network is connected via the communication interface of each computing device. In this type of possible implementation, the memory 216 in the computing device 210A stores instructions for executing the functions of the receiving module 2001 and the management module 2003. At the same time, the memory 216 in the computing device 210B stores instructions for executing the functions of the parsing module 2002.

The connection method between the computing device clusters shown in Figure 23 can be considered to be that the file extension attribute management method provided in this application requires higher computing resources, so it is considered to hand over the functions implemented by the receiving module 2001 and the management module 2003 to the computing device 210A for execution, and the functions implemented by the parsing module 2002 to the computing device 210B for execution.

It should be understood that the functionality of the computing device 210A shown in FIG23 may also be accomplished by multiple computing devices 210. Similarly, the functionality of the computing device 210B may also be accomplished by multiple computing devices 210.

The embodiment of the present application also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to the connection mode of the computing device cluster shown in Figure 21. The difference is that the memory 216 in one or more computing devices 210 in the computing device cluster can store the same instructions for executing the file extension attribute management method.

In some possible implementations, the memory 216 of one or more computing devices 210 in the computing device cluster may also store partial instructions for executing the file extension attribute management method. In other words, the combination of one or more computing devices 210 may jointly execute the instructions for executing the file extension attribute management method.

The embodiment of the present application also provides an electronic device. As shown in FIG. 24 , the electronic device 240 includes: a bus 242, a processor 244, a memory 246, and a communication interface 248. The processor 244, the memory 246, and the communication interface 248 communicate with each other via the bus 242. The electronic device 240 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the electronic device 240.

The memory 246 stores executable program codes, and the processor 244 executes the executable program codes to respectively implement the functions of the aforementioned receiving module 1901, the attribute management module 1902, the sending module 1903, and the attribute implementation module 1904, thereby implementing the file extended attribute management method. That is, the memory 246 stores instructions for executing the file extended attribute management method.

It should be noted that the electronic device 240 may be an electronic device used by the cloud service tenant shown in Figures 1 and 2. For other related descriptions of the bus 242, processor 244, memory 246, and communication interface 248 of the electronic device 240, reference may be made to the related descriptions of the computing device shown in Figure 21 above, which will not be repeated here.

The embodiment of the present application also provides a computer program product. The computer program product may be a software or program product that includes a computer program/instruction and can be run on an electronic device or stored in any available medium. When the computer program product is run on at least one electronic device, the at least one electronic device executes the file extension attribute management method.

The embodiment of the present application also provides a computer program product. The computer program product may be a software or program product that includes a computer program/instruction and can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the file extension attribute management method.

The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by the electronic device or a data storage device such as a data center containing one or more available media. The computer-readable storage medium includes a computer program/instruction that instructs the electronic device to execute the file extension attribute management method.

The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that includes one or more available media. The computer-readable storage medium includes a computer program/instruction that instructs the computing device to execute the file extension attribute management method.

The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive), etc.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention 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 make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims (20)

A method for managing file extension attributes, characterized in that the method is applied to a file storage client, the file storage client runs on a Windows operating system, the Windows operating system also provides a local file system, the directory tree of the local file system includes a target node, the target node is a file or a directory, and the file or directory is stored in an object storage service node; the method comprises: receiving an attribute setting instruction, wherein the attribute setting instruction indicates setting a target file extension attribute of the target node to a target state; the target state includes a configured state or an unconfigured state; Determine a property setting request based on the property setting instruction and a target interface provided by the object storage service node; the target interface of the object storage service node is used to indicate a format of the property setting request, and the property setting request is used to request to set the target file extended attribute of the target node to the target state; The attribute setting request is sent to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to the target state. The method according to claim 1, characterized in that The attribute setting request includes a message content and an operation command, wherein the message content is used to indicate the extended attribute of the target file, and the operation command is used to indicate the target state; Alternatively, the attribute setting request includes message content, and the message content is used to indicate the target file extended attribute and the target status. The method according to claim 1 or 2, characterized in that the method further comprises: receiving a target instruction, wherein the target instruction is used to instruct to perform a target operation on a target node; the target operation is related to an extended attribute of the target file; Determining a permission check result of the target operation based on the state of the target file extension attribute; the permission check result includes passing the check or failing the check; In the case where the permission check result is failure to pass the check, response information is returned based on the target instruction; the response information is used to indicate a refusal to execute the target operation on the target node. The method according to any one of claims 1 to 3, characterized in that, when the target node is the first file, the method further comprises: Based on the attribute setting instruction, obtaining the first file; Performing the operation indicated by the attribute setting instruction on the first file to obtain a second file; A first storage request is sent to the object storage service node, where the first storage request is used to request storage of the second file; and the first storage request includes the second file. The method according to any one of claims 1 to 4, characterized in that, when the target node is a third file, the method further comprises: receiving a storage instruction, wherein the storage instruction is used to instruct to store a third file; the target file extension attribute of the third file is in a configured state; Performing the operation indicated by the target file extension attribute on the third file to obtain a fourth file; A second storage request is sent to the object storage service node, where the second storage request is used to request the object storage service node to store the fourth file; and the storage request includes the fourth file. The method according to any one of claims 1 to 5, characterized in that the method further comprises: Receive an attribute acquisition instruction, where the attribute acquisition instruction is used to instruct to acquire a file extended attribute of the target node; Based on the attribute acquisition instruction, the file extended attribute of the target node is acquired and returned. The method according to any one of claims 1 to 6, characterized in that the method further comprises: Receive a metadata acquisition instruction, where the metadata acquisition instruction is used to instruct to acquire metadata of the target node; Based on the metadata acquisition instruction, the target metadata of the target node is acquired and returned; the target metadata of the target node includes the file extension attribute of the target node. A file extension attribute management method, characterized in that the method is applied to an object storage service node, the object storage service node stores a target object, and the object storage service node is used to map the target object to a target node on a directory tree, and the target node is a file or a directory; the method comprises: Receive a property setting request sent by a file storage client, wherein the format of the property setting request is determined according to a target interface provided by the object storage service node, and the property setting request is used to request setting a target file extended attribute of the target node to a target state, wherein the target state includes a configured state or an unconfigured state; Parsing the property setting request through the target interface to obtain the content requested by the property setting request; The target file extended attribute of the target node is set to the target state based on the content requested by the attribute setting request. The method according to claim 8, characterized in that, when the target state is a configured state, setting the target file extended attribute of the target node to the target state based on the content requested by the attribute setting request comprises: Generate a target field of the target node based on the content requested by the attribute setting request; the target field of the target node is used to indicate that the target file extended attribute has been configured; Based on the identifier of the target node, a target field of the target node is stored. The method according to claim 8, characterized in that, when the target state is an unconfigured state, setting the target file extended attribute of the target node to the target state based on the content requested by the attribute setting request comprises: Based on the content requested by the attribute setting request, the target field of the target node is deleted; the target field of the target node is used to indicate that the target file extended attribute has been configured. The method according to claim 8, characterized in that the object storage service node stores a target string, the target string being used to indicate a state of a file extension attribute of the target node; and setting the target file extension attribute of the target node to the target state based on the content requested by the attribute setting request comprises: In the case where the target state is a configured state, based on the content requested by the attribute setting request, the target bit of the target character string is set to a first value; the target bit is used to indicate the target file extended attribute, and the first value is used to indicate the configured state; In the case where the target state is an unconfigured state, the target bit of the target character string is set to a second value based on the content requested by the attribute setting request; the second value is used to indicate an unconfigured state. The method according to any one of claims 8 to 11, characterized in that the method further comprises: Receiving an attribute acquisition request sent by the file storage client, wherein the attribute acquisition request is used to request to acquire a file extended attribute of the target node; Based on the attribute acquisition request, the file extended attributes of the target node are returned to the file storage client. The method according to any one of claims 8 to 12, characterized in that the method further comprises: Receive a metadata acquisition request sent by the client, where the metadata acquisition request is used to request to acquire metadata of the target node; Based on the metadata acquisition request, target metadata of the target node is returned to the file storage client; the target metadata of the target node includes file extension attributes of the target node. A file storage client, characterized in that the file storage client comprises: A receiving module, configured to receive an attribute setting instruction, wherein the attribute setting instruction indicates setting a target file extension attribute of a target node to a target state, wherein the target state includes a configured state or an unconfigured state; the target node is a file or a directory, and the file or directory is stored in an object storage service node; an attribute management module, configured to determine an attribute setting request based on the attribute setting instruction and a target interface provided by the object storage service node; the interface provided by the object storage service node is used to indicate a format of the attribute setting request, and the attribute setting request is used to request setting an extended attribute of a target file of the target node to a target state; A sending module is used to send the attribute setting request to the object storage service node to request the object storage service node to set the target file extension attribute of the target node to the target state. A file extension attribute management device, characterized in that the file extension attribute management device is applied to an object storage service node, and the file extension attribute management device comprises: A receiving module, configured to receive a property setting request sent by a file storage client, wherein the format of the property setting request is determined according to a target interface provided by the object storage service node, and the property setting request is used to request setting a target file extension attribute of a target node to a target state, wherein the target state includes a configured state or an unconfigured state; A parsing module, used for parsing the property setting request through the target interface to obtain the content requested by the property setting request; A management module is used to set the target file extension attribute of the target node to the target state based on the content requested by the attribute setting request. A computer program product, characterized in that it comprises: a computer program/instruction, which, when executed by a processor of an electronic device, implements the steps of the method as described in any one of claims 1 to 7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program/instruction, and when the computer program/instruction is executed by a processor of an electronic device, the steps of the method according to any one of claims 1 to 7 are implemented. A computing device cluster, comprising: at least one computing device, each computing device of the at least one computing device comprising a processor and a memory; Each computing device includes a processor, a memory, and a computer program/instruction stored in the memory; the processor executes the computer program/instruction to enable the computing device cluster to implement the steps of the method as described in any one of claims 8-13. A computer program product, characterized in that it comprises: a computer program/instruction, which, when executed by a processor of a computing device, implements the steps of the method as described in any one of claims 8 to 13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program/instruction, which, when executed by a processor of a computing device, implements the steps of the method according to any one of claims 8 to 13.