File reading and writing method and system based on object storage

Abstract

The embodiment of the invention provides a file reading and writing method and system based on object storage, and belongs to the technical field of object storage. The method comprises the following steps: collecting a file reading / writing request signal of a user, analyzing the reading / writing request, and judging a file reading / writing target storage library; calling a corresponding configuration item based on a file reading / writing target storage library; executing the configuration item, calling a corresponding service layer component, performing user identity verification based on the read / write request signal, and accessing a service access point of a file read / write target storage library based on the corresponding service layer component after the verification is passed; and downloading or uploading user request data in a file reading / writing target storage library based on the service access point. According to the scheme of the invention, through unified management configuration and service layer components, a user can perform switching operation among different read / write target storage libraries more conveniently, and the user experience is further improved.

Description

Technical Field

[0001] The present invention relates to the technical field of object storage, and in particular to a file reading and writing method based on object storage and a file reading and writing system based on object storage. Background Art

[0002] In today's cloud computing ecosystem, object storage, as one of the key technologies, is widely used due to its unique advantages. Object storage can provide high security, scalability, flexibility and cost-effectiveness, making it a popular choice for enterprise data storage solutions. Many cloud service providers such as Alibaba Cloud OSS, Tencent Cloud, Huawei Cloud and Amazon Cloud have launched their own object storage services, which has promoted the development of the market. However, the existing object storage solutions have also exposed some problems that need to be solved urgently.

[0003] First, the differences between existing cloud vendors are significant, which leads to major challenges for enterprises in choosing suitable object storage services. The storage principles and technical architectures of each cloud service provider are different. When choosing a storage service, enterprises need to spend a lot of time and energy to study and understand the characteristics and advantages of each vendor. This not only increases the complexity of decision-making, but also makes enterprises often feel overwhelmed after making a choice, making it difficult to make the best decision.

[0004] Secondly, since the security and privacy protection mechanisms of various object storage services are different, enterprises face difficulties in evaluating their security. Although most cloud service providers claim that their services are highly secure, the specific implementation details are often complex and opaque, making it difficult for enterprises to conduct effective evaluations. This situation makes it impossible for enterprises to fully guarantee the security of their data when choosing cloud services, and they may face the risk of data leakage and security vulnerabilities.

[0005] In addition, current object storage solutions lack flexibility. After using a cloud service, if an enterprise wants to migrate to another cloud service provider, it usually needs to go through a tedious data migration process. Issues such as incompatible data formats, differences in API calls, and data migration costs make flexible switching an ideal rather than a reality. Enterprises may be forced to lock in a specific cloud vendor due to technical barriers and lose the freedom of choice, which is particularly disadvantageous in a rapidly developing market environment.

[0006] In summary, although existing object storage solutions have advantages in security, scalability and cost, there are many problems in selection complexity, security assessment and flexible switching. These problems urgently need the support of technological innovation and solutions to help enterprises more effectively use cloud storage technology and improve overall operational efficiency and security. Summary of the invention

[0007] The purpose of the embodiments of the present invention is to provide a file reading and writing method based on object storage, so as to at least solve the problem of difficulty in switching target storage repositories when users face multi-object target storage repositories.

[0008] In order to achieve the above-mentioned purpose, the first aspect of the present invention provides a file reading and writing method based on object storage, the method comprising: collecting a user's file reading / writing request signal, parsing the reading / writing request, and determining a file reading / writing target storage repository; based on the file reading / writing target storage repository, calling a corresponding configuration item; executing the configuration item, calling a corresponding service layer component, performing user identity authentication based on the reading / writing request signal, and after the authentication is passed, accessing a service access point of the file reading / writing target storage repository based on the corresponding service layer component; based on the service access point, downloading or uploading user requested data in the file reading / writing target storage repository.

[0009] Optionally, the collecting of the user's file read / write request signal, parsing the read / write request, and determining the file read / write target repository include: parsing the read / write request to determine whether the user has a specified file read / write target repository, and if so, using the file read / write target repository specified by the user as the currently determined file read / write target repository; if the user has not specified a file read / write target repository, determining the file read / write target repository based on the current user retained information or identification information of the read / write request signal.

[0010] Optionally, the file read / write target repository judgment based on the current user retained information or the identification information of the read / write request signal includes: judging whether there is a historically accessed file read / write target repository for the user based on the current user retained information; if there is only a single historically accessed file read / write target repository and the current read / write request signal is a data read request signal, then the corresponding historically accessed file read / write target repository is used as the currently judged file read / write target repository; if there are multiple historically accessed file read / write target repositories or the current read / write request signal is a data write request signal, then the file read / write target repository is fed back to the user end for user confirmation; and the current file read / write target repository is judged based on the user confirmation information.

[0011] Optionally, calling the corresponding configuration item based on the file read / write target repository includes: identifying matching configuration items in a pre-built configuration item library based on the file read / write target repository; and determining the file read / write protocol based on the matching configuration items.

[0012] Optionally, the method also includes: constructing a configuration item library, including: traversing all file read / write target storage repositories, applying for an access account for each file read / write target storage repository respectively, and applying for corresponding object storage permissions and access keys; introducing an SDK for the corresponding file read / write target storage repository, and encapsulating configuration items based on the SDK for the file read / write target storage repository, the access account for the corresponding file read / write target storage repository, the object storage permissions for the corresponding file read / write target storage repository, and the access key for the corresponding file read / write target storage repository.

[0013] Optionally, executing the configuration item, calling the corresponding service layer component, and performing user identity authentication based on the read / write request signal, including: executing the configuration item, calling the corresponding service layer component, and verifying the access key of the current user; if the current user key verification fails, rejecting the current user's file read / write request; if the current user key verification passes, accessing the service access point of the file read / write target repository based on the corresponding service layer component.

[0014] Optionally, the service access point of the file read / write target repository based on the corresponding service layer component includes: obtaining the service access point of the current file read / write target repository based on the service layer component parsing; and establishing a communication connection with the current file read / write target repository based on the service access point to perform file reading or uploading based on the communication connection.

[0015] Optionally, based on the service access point, user-requested data download or upload is performed in the file read / write target storage repository, including: based on the read / write request signal, when the signal type is a data read request signal, corresponding data is downloaded based on the target data of the read / write request signal, and download log information is recorded; when the signal type is a data upload request signal, the uploaded data is written to the current file read / write target storage repository, and upload log information is recorded.

[0016] A second aspect of the present invention provides a file reading and writing method based on object storage, the method comprising: a collection unit, used to collect a user's file read / write request signal, and parse the read / write request to determine a file read / write target repository; a calling unit, used to call a corresponding configuration item based on the file read / write target repository; a connection unit, used to execute the configuration item, call a corresponding service layer component, perform user identity authentication based on the read / write request signal, and after the authentication is passed, access a service access point of the file read / write target repository based on the corresponding service layer component; an execution unit, used to download or upload user-requested data in the file read / write target repository based on the service access point.

[0017] On the other hand, the present invention provides a computer-readable storage medium, on which instructions are stored, which, when executed on a computer, enable the computer to execute the above-mentioned file reading and writing method based on object storage.

[0018] Through the above technical solution, the solution of the present invention can intelligently determine the target repository by collecting and parsing the user's file read / write request signal, thereby accurately calling the corresponding configuration items. By executing these configuration items, the system can effectively call the corresponding service layer components, verify the user's identity, and ensure the security of the operation. After the verification is passed, the system will achieve seamless access to the target repository based on the service access point and complete the user's file data download or upload request. This process not only improves the security and flexibility of file read / write operations, but also significantly reduces the complexity of enterprises switching between different cloud storage services, and optimizes the efficiency of data management. By uniformly managing configuration and service layer components, users can operate more conveniently, further improving the user experience.

[0019] Other features and advantages of the embodiments of the present invention will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings are used to provide a further understanding of the embodiments of the present invention and constitute a part of the specification. Together with the following specific embodiments, they are used to explain the embodiments of the present invention, but do not constitute a limitation on the embodiments of the present invention. In the accompanying drawings:

[0021] Figure 1 It is a flowchart of the steps of a file reading and writing method based on object storage provided by an embodiment of the present invention;

[0022] Figure 2 It is a system structure diagram of a file reading and writing system based on object storage provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0023] The specific implementation of the present invention is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described here is only used to illustrate and explain the present invention, and is not used to limit the present invention.

[0024] Figure 1 1 is a method flow chart of a file reading and writing method based on object storage provided by an embodiment of the present invention. Figure 1 As shown, an embodiment of the present invention provides a file reading and writing method based on object storage, the method comprising:

[0025] Step S10: Collect the user's file read / write request signal, parse the read / write request, and determine the file read / write target storage library.

[0026] Specifically, the read / write request is parsed to determine whether there is a file read / write target repository specified by the user. If so, the file read / write target repository specified by the user is used as the file read / write target repository currently being determined; if the user does not specify a file read / write target repository, the file read / write target repository is determined based on the current user retained information or identification information of the read / write request signal.

[0027] Furthermore, the file read / write target repository judgment based on the current user retained information or the identification information of the read / write request signal includes: judging whether there is a historically accessed file read / write target repository of the user based on the current user retained information; if there is only a single historically accessed file read / write target repository and the current read / write request signal is a data read request signal, then the corresponding historically accessed file read / write target repository is used as the currently judged file read / write target repository; if there are multiple historically accessed file read / write target repositories or the current read / write request signal is a data write request signal, then the file read / write target repository is fed back to the user end for user confirmation; and the current file read / write target repository is judged based on the user confirmation information.

[0028] In an embodiment of the present invention, when a user initiates a read / write request, the request is first parsed to confirm whether the user has explicitly specified a target repository. If the user has specified a target repository, the repository is used as the target of the current operation. However, if the user has not explicitly indicated a repository, a judgment will be made based on the current user's retained information or the identification information of the request signal. This intelligent judgment can not only improve the user experience, but also reduce operation failures caused by incorrect user selections.

[0029] In further judgment, the target repository is determined based on the user's historical access records. For example, when it is detected that there is only a single target repository in the user's historical access records and the current request is a read signal, the historical repository will be automatically used as the target. This approach improves the efficiency of operations in data reading scenarios and avoids unnecessary user intervention. However, if multiple historical access repositories are identified, or the current request is a write signal, multiple possible repository options will be actively fed back to the user end to ensure that the user can confirm the target. This interactive process enhances flexibility, allowing users to better control and select appropriate storage locations when writing data, thereby reducing the risk of data loss or storage errors.

[0030] Based on the scheme of the present invention, the intelligence and security of file read / write operations are significantly improved. By comprehensively utilizing the user's historical information and real-time request signals, not only can the file read / write target storage library be determined quickly and accurately, but also erroneous operations caused by the user's unfamiliarity with the storage library can be effectively prevented. This intelligent judgment and feedback mechanism not only improves the convenience of user operation, but also enhances the security and reliability of data storage management, greatly optimizing the data management process of enterprises in cloud environments. At the same time, users do not need to master complex storage rules and parameter configurations, making the entire operation process more user-friendly, thereby improving the overall user experience.

[0031] Step S20: Based on the file read / write target repository, call the corresponding configuration item.

[0032] Specifically, based on the file read / write target repository, matching configuration items are identified in the pre-built configuration item library; based on the matching configuration items, the file read / write protocol is determined.

[0033] In an embodiment of the present invention, the target repository is first identified according to the user's request, and then a detailed match is performed in the pre-built configuration item library to find the configuration items corresponding to the repository. The automation and intelligence of this process not only improves the efficiency of the operation, but also reduces the occurrence of human errors. During the matching process, each configuration in the configuration item library is compared, considering multiple factors such as storage protocol, access rights, and data security. Once the match is successful, the read / write protocol of this file will be automatically determined, and subsequent operations will be performed based on this protocol. This mechanism ensures the compatibility of data between different repositories and can be properly processed according to different protocol requirements.

[0034] Based on the scheme of the present invention, the flexibility and adaptability of file read / write operations are greatly improved. By automatically calling matching configuration items, it can not only adapt to various types of repositories, but also maintain efficient data management in a changing cloud environment. In addition, this dynamic matching of configuration items also provides users with a better experience, because they can perform data operations safely and quickly without having to deeply understand the technical details of different repositories. This intelligent processing lowers the technical threshold for enterprises, improves overall data management efficiency, and promotes the rational use of resources.

[0035] Preferably, the method also includes: constructing a configuration item library, including: traversing all file read / write target storage repositories, applying for an access account for each file read / write target storage repository respectively, and applying for corresponding object storage permissions and access keys; introducing an SDK corresponding to the file read / write target storage repository, and encapsulating configuration items based on the SDK of the file read / write target storage repository, the access account of the corresponding file read / write target storage repository, the object storage permissions of the corresponding file read / write target storage repository, and the access key of the corresponding file read / write target storage repository.

[0036] In an embodiment of the present invention, by traversing all file read / write target repositories, apply for access accounts of each repository respectively. This process not only includes applying for basic access rights to the repository, but also involves obtaining corresponding object storage permissions and access keys. The integration of this information is the basis for achieving flexibility and security. Next, the SDK of each file read / write target repository will be introduced. These SDKs provide the necessary tools and interfaces for interacting with the repository, allowing developers to manage different storage services through a unified programming interface. After obtaining the access account, object storage permissions and access keys, the configuration items will be encapsulated based on this information. This encapsulation process ensures that the configuration items of each repository can be called in a standardized form, thereby simplifying subsequent file read / write operations.

[0037] Based on the solution of the present invention, through the construction of a comprehensive configuration item library, it is possible to support multiple different types of object storage services, allowing enterprises to have greater flexibility in choosing storage solutions. In addition, the SDK-based encapsulation method reduces the learning cost of developers, allowing them to focus more on the implementation of business logic without having to delve into the implementation details of each repository. This standardized and modular design enables higher maintainability and scalability, laying a solid foundation for future access to other storage services. At the same time, by ensuring the secure management of access rights and keys, potential security threats can be more effectively prevented when processing sensitive data.

[0038] In a possible implementation, for the read / write target repository A, the corresponding configuration item construction rule is:

[0039] 1) Apply for an Alibaba Cloud account, purchase and activate the read / write target repository A object storage service, apply for access keys [AccessKey ID (AK) and Secret Access Key (SK)], apply for bucket storage space, and obtain the endpoint (service access point);

[0040] 2) Introduce the SDK (Java version) aliyun-sdk-oss that encapsulates the read / write target repository A;

[0041] 3) Create a configuration class to read the OSS parameters in the configuration file (the access key, storage space name, and service access point for the preparation operation application);

[0042] 4) Encapsulate OSSClient object operations as Service or Component classes;

[0043] 5) Provide upload and download methods to external parties based on business needs.

[0044] For the read / write target repository B, the corresponding configuration item construction rules are:

[0045] 1) Apply for a read / write target repository B account, purchase and activate the read / write target repository B object storage service, apply for access key [SecretId / SecretKey], apply for bucket storage space, and obtain Region (service access point);

[0046] 2) Introduce the SDK (Java version) cos_api that reads / writes the target repository B package;

[0047] 3) Create a configuration class to read the COS parameters in the configuration file (the access key, storage space name, and service access point requested in the preparation operation);

[0048] 4) Encapsulate COSClient object operations as Service or Component classes;

[0049] 5) Provide upload and download methods to external parties based on business needs.

[0050] For the read / write target repository C, the corresponding configuration item construction rules are:

[0051] 1) Download the read / write target repository C and build the object storage service, apply for the access key [accessKey / secretKey], allocate bucket storage space, and obtain the endpoint (service access point);

[0052] 2) Introduce the SDK (Java version) minio that reads / writes the target repository C package;

[0053] 3) Create a configuration class to read the minio parameters in the configuration file (access key, storage space name, and service access point requested in the preparation operation);

[0054] 4) Encapsulate the MinioClient object operation as a Service or Component class;

[0055] 5) Provide upload and download methods to external parties based on business needs.

[0056] Step S30: Execute the configuration item, call the corresponding service layer component, perform user identity authentication based on the read / write request signal, and after the authentication is passed, access the service access point of the file read / write target repository based on the corresponding service layer component.

[0057] Specifically, execute the configuration item, call the corresponding service layer component, and verify the access key of the current user; if the current user key verification fails, reject the current user's file read / write request; if the current user key verification passes, access the service access point of the file read / write target repository based on the corresponding service layer component.

[0058] Furthermore, the service access point of the file read / write target repository based on the corresponding service layer component includes: obtaining the service access point of the current file read / write target repository based on the service layer component analysis; based on the service access point, establishing a communication connection with the current file read / write target repository to perform file reading or uploading based on the communication connection.

[0059] In an embodiment of the present invention, the key to executing configuration items is to ensure that the user's file read / write request can be carried out safely and effectively. First, the corresponding service layer component will be called to verify the user's identity. The first task of this process is to check the access key of the current user to ensure that only authorized users can access and operate the target repository. Specifically, the user's access key is verified by the service layer component. If the verification fails, the user's file read / write request will be immediately rejected. This security measure can effectively prevent unauthorized users from accessing sensitive data, thereby ensuring the security of the data.

[0060] On the contrary, if the user's access key is verified, the service access point of the target repository for file reading / writing will be further accessed based on the corresponding service layer component. At this time, the service layer component will parse and obtain the specific service access point information of the target repository, laying the foundation for subsequent operations. Through this mechanism, it can dynamically adapt to the access needs of different repositories.

[0061] Furthermore, in the process of establishing a communication connection, a stable communication channel will be successfully established with the current file read / write target storage repository based on the obtained service access point information. This communication connection is a prerequisite for performing file read or upload operations, ensuring that data can flow safely between the user and the target storage repository. Whether uploading or downloading files, data interaction can be completed efficiently based on this communication connection.

[0062] Based on the solution of the present invention, through a strict user identity authentication mechanism, enterprises can effectively manage user permissions and prevent data leakage or malicious attacks. At the same time, the dynamic access of service layer components makes it easy to adapt to a variety of different repositories, improving the efficiency of data management. In addition, the establishment of communication connections based on service access points ensures the stability and reliability of data transmission when performing file read / write operations. This standardized design not only simplifies the development process, but also provides a good foundation for future functional expansion and access to new storage services, allowing enterprises to flexibly respond to various challenges in a rapidly changing cloud environment.

[0063] Step S40: Based on the service access point, download or upload the user-requested data in the file read / write target storage repository.

[0064] Specifically, based on the read / write request signal, when the signal type is a data read request signal, the corresponding data is downloaded based on the target data of the read / write request signal, and the download log information is recorded; when the signal type is a data upload request signal, the uploaded data is written to the current file read / write target storage repository, and the upload log information is recorded.

[0065] In the embodiment of the present invention, when a data read request signal is received, a download operation is performed for the specified target data. In this process, not only the actual data transmission is performed, but also a detailed log record is made for each download operation. These log information includes the download time, user identity, detailed information of the target data, etc., which is helpful for subsequent data auditing and tracking, thereby improving transparency and security.

[0066] On the contrary, when a data upload request signal is received, the uploaded data will be processed and written to the current file read / write target repository. At this time, the upload log information will also be recorded, including the upload time, user identity, uploaded data type, etc. This two-way logging mechanism provides users and administrators with a clear operation track, making it easy to trace back and verify the legitimacy of the operation when necessary.

[0067] Based on the solution of the present invention, firstly, through accurate request identification and processing, it is ensured that users can quickly and securely complete data download and upload operations. Secondly, detailed log records provide a powerful tracking mechanism for data operations, and users and administrators can promptly discover potential problems or security risks by auditing these log information. In addition, the recording of log information also provides support for data compliance review, especially when facing strict data protection regulations, this mechanism can effectively reduce the compliance risk of enterprises. In summary, this technology not only optimizes the process of file operations, but also enhances the capabilities in data security and compliance management, so that it can better adapt to the needs of modern cloud environments.

[0068] In a possible implementation, the system defines access parameters of different object storage platforms through configuration files to achieve flexible data storage and management. The specific implementation steps are as follows:

[0069] 1) System environment preparation: First, install and configure the Spring Boot framework to ensure that the system can run normally. Then, introduce the required dependencies, which include SDKs of different object storage services, such as Minio, Alibaba Cloud OSS, and Tencent Cloud COS.

[0070] 2) Configuration file settings: Create a configuration file named application.yml, in which users enter the access information of various object storage platforms, including the default storage platform, access key, bucket name, etc. This information helps the system select the appropriate storage service for data operations at runtime.

[0071] 3) Service layer component implementation: Create a service class named FileStorageService to handle the interaction with object storage. In this service class, select the corresponding SDK for file upload and download operations based on the default storage platform set by the user. When the user calls the method to upload a file, the service class will check the currently configured default storage platform and call the corresponding SDK to upload the file. If the current platform is Minio, use Minio's SDK; if it is Alibaba Cloud OSS, use OSS's SDK, and so on.

[0072] 4) Logging and security: A logging function is added to the operations of uploading and downloading files. Whenever a user performs a file operation, the system will record relevant information, including user identity, operation time, and operation type. This facilitates subsequent auditing and tracking.

[0073] 5) Testing and Verification: Finally, unit testing and integration testing are performed to ensure that all functions are functioning properly. The system should be able to successfully complete file upload and download operations and switch seamlessly between different storage platforms.

[0074] Figure 2 1 is a system structure diagram of a file reading and writing system based on object storage provided by an embodiment of the present invention. Figure 2As shown, an embodiment of the present invention provides a file read / write system based on object storage, and the system includes: a collection unit, used to collect user file read / write request signals, and parse the read / write requests to determine the file read / write target storage repository; a calling unit, used to call corresponding configuration items based on the file read / write target storage repository; a connection unit, used to execute the configuration items, call corresponding service layer components, perform user identity authentication based on the read / write request signal, and after the authentication is passed, access the service access point of the file read / write target storage repository based on the corresponding service layer component; an execution unit, used to download or upload user requested data in the file read / write target storage repository based on the service access point.

[0075] The embodiment of the present invention further provides a computer-readable storage medium, on which instructions are stored, which, when executed on a computer, enable the computer to execute the above-mentioned file reading and writing method based on object storage.

[0076] Those skilled in the art will understand that all or part of the steps in the method for implementing the above-mentioned embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions for making a single-chip microcomputer, a chip or a processor (processor) perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0077] The optional embodiments of the present invention are described in detail above in conjunction with the accompanying drawings. However, the embodiments of the present invention are not limited to the specific details in the above embodiments. Within the technical concept of the embodiments of the present invention, the technical scheme of the embodiments of the present invention can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the embodiments of the present invention. It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the embodiments of the present invention will not further describe various possible combinations.

[0078] In addition, various embodiments of the present invention may be arbitrarily combined, and as long as they do not violate the concept of the embodiments of the present invention, they should also be regarded as the contents disclosed in the embodiments of the present invention.

Claims

1. A file reading and writing method based on object storage, characterized in that: The method comprises: Collecting the user's file read / write request signal, parsing the read / write request, and determining the file read / write target storage repository; Based on the file read / write target repository, call the corresponding configuration item; Execute the configuration item, call the corresponding service layer component, perform user identity authentication based on the read / write request signal, and after the authentication is passed, access the service access point of the file read / write target storage repository based on the corresponding service layer component; Based on the service access point, the user requested data is downloaded or uploaded in the file read / write target storage repository.

2. The method according to claim 1, characterized in that The collecting of the user's file read / write request signal, parsing the read / write request, and determining the file read / write target storage repository includes: Parsing the read / write request to determine whether there is a file read / write target storage repository specified by the user, and if so, using the file read / write target storage repository specified by the user as the currently determined file read / write target storage repository; If the user does not specify the file read / write target storage library, the file read / write target storage library is determined based on the current user retention information or the identification information of the read / write request signal.

3. The method according to claim 2, characterized in that The determination of the file read / write target storage repository based on the current user retention information or the identification information of the read / write request signal includes: Based on the current user retention information, determine whether there is a historical access file read / write target storage repository for the user at present; if there is only a single historical access file read / write target storage repository and the current read / write request signal is a data read request signal, then use the corresponding historical access file read / write target storage repository as the currently determined file read / write target storage repository; If there are multiple historically accessed file read / write target storage repositories or the current read / write request signal is a data write request signal, the file read / write target storage repositories are fed back to the user end for user confirmation; The current file read / write target storage repository is determined based on the user confirmation information.

4. The method according to claim 1, characterized in that: The file-based reading / writing target repository calls the corresponding configuration items, including: Based on the file read / write target repository, matching configuration items are identified in the pre-built configuration item library; Based on the matching configuration items, determine the file read / write protocol.

5. The method according to claim 4, characterized in that The method further comprises: Build the configuration item library, including: Traverse all file read / write target repositories, apply for access accounts for each file read / write target repository, and apply for corresponding object storage permissions and access keys; The SDK of the corresponding file read / write target repository is introduced, and the configuration items are encapsulated based on the SDK of the file read / write target repository, the access account of the corresponding file read / write target repository, the object storage permission of the corresponding file read / write target repository, and the access key of the corresponding file read / write target repository.

6. The method according to claim 1, characterized in that Executing the configuration item, calling the corresponding service layer component, and performing user identity authentication based on the read / write request signal, including: Execute the configuration item, call the corresponding service layer component, and verify the access key of the current user; If the current user key verification fails, the current user's file read / write request will be rejected; If the current user key verification is successful, the service access point of the file read / write target repository is accessed based on the corresponding service layer component.

7. The method according to claim 1, characterized in that The service access point for accessing the file read / write target storage repository based on the corresponding service layer component includes: Obtain the service access point of the current file read / write target repository based on the service layer component analysis; Based on the service access point, a communication connection is established with the current file read / write target storage repository to perform file reading or uploading based on the communication connection.

8. The method according to claim 1, characterized in that Based on the service access point, downloading or uploading the user-requested data in the file read / write target storage repository includes: Based on the read / write request signal, when the signal type is a data read request signal, downloading corresponding data based on the target data of the read / write request signal, and recording download log information; When the signal type is a data upload request signal, the uploaded data is written to the current file read / write target repository and the upload log information is recorded.

9. A file reading and writing system based on object storage, characterized in that: The system comprises: A collection unit, used to collect a user's file read / write request signal, parse the read / write request, and determine a file read / write target storage repository; A calling unit is used to read / write the target repository based on the file and call the corresponding configuration item; A connection unit, configured to execute the configuration item, call the corresponding service layer component, perform user identity authentication based on the read / write request signal, and after the authentication is passed, access the service access point of the file read / write target storage repository based on the corresponding service layer component; The execution unit is used to download or upload the user-requested data in the file read / write target storage repository based on the service access point.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the file reading and writing method based on object storage as described in any one of claims 1 to 8.

Images