An information system and method for file management

Abstract

The application provides an information system and method for file management, the system comprising: an application end, a service end and a client end; the application end receives a file management request, sends application end information to the service end, receives feedback information fed back by the service end, and if the feedback information comprises a client end address list, sends the file management request and the application end information to any client end address in the client end address list; the service end carries out legality verification on the application end information, and after passing, sends feedback information to the application end, and if passing and no client end address list, carries out file management work on the service end; receives a legality verification request sent by the client end, and after passing, sends a storage information list to the client end; the client end receives a file management request, sends a legality verification request to the service end, if passing, carries out file management work in a storage resource represented by a storage information in the storage information list. The application separates the conventional function from the file storage function.

Description

Technical Field

[0001] This application relates to the field of document management technology, and in particular to an information system and method for document management. Background Technology

[0002] With the rapid development of information technology and the popularization of information technology construction in enterprises and institutions, many enterprises and institutions have built their own information systems. These information systems generally involve file management tasks such as storage, downloading, and querying of documents and materials. Ultimately, file management must be implemented on the corresponding storage resources.

[0003] Currently, there are many types of storage resources on the market, including conventional storage hardware and distributed storage services provided by major IT vendors. However, each type of storage resource has its own characteristics, so the technical solutions for using these storage resources in information systems are also quite different. This has led to limitations in file management in information systems. For example, existing file storage functions are generally built into information systems. When the concurrency of file storage functions in an information system is high, it will exhaust the server resources of the information system, thereby affecting the use of other functions that do not involve file storage. In other words, the conventional functions of the information system have not been effectively separated from the file storage functions. Summary of the Invention

[0004] In order to effectively separate the conventional functions of an information system from its file storage functions, this application provides an information system and method for file management.

[0005] In a first aspect, this embodiment provides an information system for file management, the system comprising: an application terminal, a server terminal, and a client terminal; wherein,

[0006] The application is used to receive file management requests, send application information corresponding to the file management requests to the server according to the file management requests, receive feedback information from the server according to the application information, and if the feedback information includes a list of client addresses, send the file management requests and the corresponding application information to any client address represented by any client address in the list of client addresses.

[0007] The server is configured to perform a first validity check upon receiving the application information, and send feedback information to the application corresponding to the application information after the check passes. If the check passes and the feedback information does not include a list of client addresses, the server performs file management work based on the application information. The server also receives a second validity check request sent by the client based on the file request information, and sends a list of storage information to the client after the check passes.

[0008] Upon receiving the file management request, the client sends a second validity verification request to the server. If the verification passes, the client selects a storage information from the storage information list to perform the file management work represented by the file management request in the storage resource represented by the storage information.

[0009] In some embodiments, the client further includes an interface module that allows the client to perform file management tasks in storage resources.

[0010] The server also includes a storage management module, which is used to configure the storage information required for file management and store the storage information in a database. The number of storage information is at least one, and each storage information corresponds to a unique storage resource. All storage information configured in the server allows the client to perform file management in the corresponding storage resource through the interface module.

[0011] In some embodiments, the server further includes a registration module, which comprises an application authorization registration unit and a client deployment registration unit; wherein,

[0012] The application authorization registration unit is used to register the authorized application authorization information and store the application authorization information in the database so that the server can compare the received application information with the application authorization information in the database to perform the first legality verification. The application authorization information includes application identity information that represents the application identity and corresponding key information.

[0013] The client deployment registration unit is used to register the client information corresponding to the clients already deployed in the information system and store the client information in the database. The client information includes client identity information that represents the client's identity and the corresponding client address.

[0014] In some embodiments, the server further includes a storage allocation module; wherein,

[0015] The storage allocation module is used to allocate storage resources to each authorized application terminal to determine the storage information list corresponding to each application terminal, so that the server can send the storage information list to the corresponding client after the second valid verification is passed.

[0016] And it performs client allocation for each authorized application to determine the list of client addresses that each application can access, so that the server sends the client address list to the corresponding client after the first validity check is passed.

[0017] In some embodiments, if file management is used for file storage, the file management request includes key information and the file body. The client is also used to obtain the storage address where the file body is stored in the storage resource and the descriptive information characterizing the features of the file body, and send the storage address and the descriptive information to the server so that the server associates the storage address and the descriptive information in the database, and sends it to the client after successfully storing it in the database.

[0018] In some of these embodiments, the types of storage resources are diverse.

[0019] In some embodiments, the client is also used to send a completion instruction indicating the completion of the file management task to the corresponding application after completing the file management task.

[0020] In some of these embodiments, if the server fails the first or second validity check, it sends feedback information indicating the failure to the application corresponding to the application information.

[0021] The application is used to receive feedback information from the server indicating that the representation has failed, and then stop responding to the current file management request to end the work management work represented by the file management request.

[0022] Secondly, this embodiment provides a method for file management, the method comprising: receiving a file management request on the application terminal, and sending application terminal information corresponding to the file management request to the server according to the file management request;

[0023] After receiving the application information, the server performs a first legality check. If the check passes, the server sends feedback information to the application corresponding to the application information. If the check passes and the feedback information does not include the client address list, the server performs the file management work represented by the file management request according to the application information.

[0024] The application receives feedback information from the server based on the application information, and if the feedback information includes a list of client addresses, sends the file management request and the corresponding application information to any client represented by any client address in the list of client addresses;

[0025] Upon receiving the file management request, the client sends a second validity verification request to the server.

[0026] The server receives a second validity verification request sent by the client based on the file request information, and sends a list of stored information to the client after the verification is successful;

[0027] If the second validity check passes, the client can select any storage information from the storage information list to perform the file management work represented by the file management request in the storage resource represented by the storage information.

[0028] In some embodiments, the method further includes:

[0029] The interface module in the client allows the client to perform file management tasks in storage resources through the interface module;

[0030] The storage management module in the server is configured with the storage information needed for file management and stores the storage information in the database. There is at least one type of storage information, and each type of storage information corresponds to a unique storage resource. All the storage information configured in the server allows the client to perform file management in the corresponding storage resource through the interface module.

[0031] By employing the aforementioned system, this application includes an application, a server, and a client. By deploying the server and client on the server, where the server's database stores the necessary file management relationships and the storage addresses of already stored files, after the server and client are deployed and configured, the application receives a file management request and executes the request on either the server or the client. The actual storage or downloading of files is handled by storage resources connected to the client. This separation of the information system's conventional functions from its file storage functions allows the system to focus solely on the upper-level file management application without needing to concern itself with the underlying technical details of file storage, thus indirectly ensuring the system's application stability.

[0032] In addition, the information system of this application can access a variety of storage resources, and when it is necessary to expand the information system, only one storage resource needs to be connected, and the storage management module of the server is used to configure the storage resource information corresponding to the newly connected storage resource, so that the information system can be expanded on a larger scale simply. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the structure of an information system for file management provided in an embodiment of this application.

[0034] Figure 2 This is a schematic diagram of the file storage process provided in an embodiment of this application.

[0035] Figure 3 This is a schematic diagram of the file download process provided in an embodiment of this application.

[0036] Figure 4This is a schematic diagram of the document query process provided in the embodiments of this application.

[0037] Figure 5 This is a block diagram of a method for file management provided in an embodiment of this application. Detailed Implementation

[0038] To better understand the purpose, technical solutions, and advantages of this application, it has been described and illustrated below with reference to the accompanying drawings and embodiments. However, those skilled in the art should understand that this application can be implemented without these details. It will be apparent to those skilled in the art that various modifications can be made to the embodiments disclosed in this application, and the general principles defined in this application can be applied to other embodiments and application scenarios without departing from the principles and scope of this application. Therefore, this application is not limited to the illustrated embodiments, but is consistent with the broadest scope claimed in this application.

[0039] The embodiments of this application will now be described in further detail with reference to the accompanying drawings.

[0040] Figure 1 This is a schematic diagram of the structure of an information system for file management provided in an embodiment of this application. For example... Figure 1 As shown, the information system for file management includes an application, a server, and a client. The application receives file management requests, sends corresponding application information to the server based on the file management request, receives feedback from the server based on the application information, and, if the feedback includes a list of client addresses, sends the file management request and the corresponding application information to any client address represented by any address in the client address list.

[0041] The server is used to perform a first validity check after receiving information from the application, and send feedback information to the application corresponding to the application information after the first validity check passes. If the first validity check passes and the feedback information does not include the client address list, the server performs file management work based on the application information. The server also receives a second validity check request sent by the client based on the file request information, and sends a storage information list to the client after the second validity check passes.

[0042] Upon receiving a file management request, the client sends a second validity verification request to the server. If the second validity verification request is successful, the client selects a storage information from the storage information list to perform the file management work represented by the file management request in the storage resource represented by that storage information.

[0043] In this application's embodiment, the application terminal in the information system uses the file management service within the information system. The server terminal provides the configuration information required for the file management service. The client terminal provides the file storage and download interfaces in the file management service. The storage resource is the storage resource used by the client to store files. The information system of this application has at least one application terminal, and each application terminal is uniquely determined. Each application terminal corresponds to a uniquely determined access key for accessing files, and each application terminal can receive file management requests. These file management requests can be user-initiated requests or requests initiated by the application terminal itself to meet business needs. This application allows for at least one server to be configured based on actual concurrency requirements. If one server can meet the concurrency needs, only one server is configured. If one server cannot meet the concurrency needs, the number of servers is increased as needed. All servers correspond to a unified access interface for interaction with the application and client. This access interface has an access address. When an application or client sends information to this access interface based on the access address, multiple servers automatically select one to connect to the application based on their workload to receive the information. This application also allows for at least one client to be configured based on actual needs. Each application is associated with at least one client, and each client includes an interface module to establish connections with all accessed storage resources. This allows the client to perform file management within the storage resources through the interface module.

[0044] The server and client are deployed on a server before the information system of this application is actually used. A database is also set up on this server, and all server configuration information in the information system of this application is stored in this database. Each server includes a storage management module, a registration module, and a storage allocation module. The registration module includes an application authorization registration unit and a client deployment registration unit. The application authorization registration unit is used to register the authorization information of authorized application terminals and store the application terminal authorization information in the database, so that the server can compare the received application terminal information with the application terminal authorization information in the database for the first legality verification. The application terminal authorization information includes application terminal identity information representing the application terminal's identity and corresponding key information. The client deployment registration unit is used to register the client information corresponding to the clients already deployed in the information system and store the client information in the database. The client information includes client identity information representing the client's identity and corresponding client address.

[0045] The server-side storage management module is used to configure the storage information needed for file management and store the storage information in the database. There is at least one storage information, and each storage information corresponds to a unique storage resource. All the storage information configured in the server allows the client to perform file management work in the corresponding storage resource through the interface module.

[0046] The server-side storage allocation module is used to allocate storage resources to each authorized application client to determine the storage information list corresponding to each application client, so that the server can send the storage information list to the corresponding application client after the second validity check passes; and to allocate clients to each authorized application client to determine the client address list corresponding to the client that each application client can access, so that the server can send the client address list to the corresponding client after the first validity check passes.

[0047] In the process of deploying the application and client on the server, the access address of the server needs to be configured when deploying the client so that the client can obtain the necessary information from the server. For example, the client can obtain storage information, application authorization information and storage information list through the storage management module, registration module and storage allocation module in the server. At the same time, the client can also actively send information about itself to the server and store it in the database, such as client information and description information of files obtained by the client from storage resources.

[0048] Only authorized applications can use the file management service in the information system. The server-side application authorization registration unit registers the authorization information of the authorized applications and stores the registered authorization information in the database. Only deployed clients can provide file storage and download interfaces in the file management service. The server-side client deployment registration unit registers the client information of the deployed clients and stores the registered client information in the database. In this way, the database stores all client and application information related to the information system of this application.

[0049] The file management-based information system of this application also connects to at least one storage resource through a client, thereby enabling the system to perform file management. Each storage resource corresponds to unique storage information, including attribute information characterizing the storage resource's properties, address information characterizing the storage resource's location, and connection information required for establishing a connection between the storage resource and the client. The connection information includes the connection relationship and the connection parameters required for the connection. Whenever a storage resource needs to be connected, the corresponding storage information is configured in the server-side storage management module and stored in the database. Different types of storage resources can be connected, meaning the types of connected storage resources are diverse. Compared to existing systems where file storage operations are built into the information system, resulting in limitations such as a limited number of storage resources and a single type of storage resource, the information system of this application can connect to diverse types of storage resources. Furthermore, when the information system needs to be expanded, only one storage resource needs to be connected, and the server-side storage management module is used to configure the storage resource information corresponding to the newly added storage resource, allowing for simple and large-scale expansion of the information system. Storage resources can specifically include various types of storage resources such as disk directories, FTP shared directories, open-source file storage services FastDFS, Alibaba Cloud Object Storage Service OSS, and open-source object storage service minio.

[0050] This application describes an information system for file management that uses at least one type of application client. Each type of application client corresponds to several clients, enabling these clients to receive file management requests sent by that type of application client. Not every type of application client corresponds to the same clients; therefore, a server-side storage allocation module is needed to allocate several corresponding clients to each authorized application client. This results in a client address list for each application client, and all client address lists for all application clients are stored in a database. Each server can retrieve all information stored in the database. Furthermore, different types of clients may send or require different file types, requiring each client to have corresponding storage resources. The server-side storage allocation module allocates several corresponding storage resources to each stored storage resource, resulting in a storage resource list for each application client, and all storage resource lists for all application clients are stored in the database.

[0051] By deploying the server and client on the server and using the storage management module, registration module and storage allocation module in the server, the deployment of the information system for file management in this application can be completed, as well as the correspondence between the application and the client, and the correspondence between the application and storage resources.

[0052] File management requests specifically include file saving, file downloading, and file querying. The working principle of the file management information system in this application is that the client receives a file management request initiated by the user and sends application-side information corresponding to the file management request to the server. The sub-information included in the application-side information differs depending on the file management request. If the file management request is for file storage or downloading, the application-side information includes identity information representing the application's identity and corresponding key information. If the file management request is for file querying, the application-side information includes identity information representing the application's identity, corresponding key information, file type information representing the file to be queried, and file ID.

[0053] After receiving the application's information, the server compares it with the corresponding application authorization information in the database to perform a first legitimacy check. If both the identity information and the corresponding key information in the application authorization information match those in the application's information, the first legitimacy check passes. If at least one of the following is different: the identity information in the application authorization information differs from the identity information in the application's information, or the corresponding key information in the application authorization information differs from the corresponding key information in the application's information, the first legitimacy check fails. If the first legitimacy check fails, a feedback message indicating the failure is sent to the application. If the first legitimacy check passes, the server decides, based on the received client information, whether to send a feedback message indicating the success of the first legitimacy check to the application or to directly perform file management based on the application's information.

[0054] If the client information includes file type information and file ID in addition to identity and key information, it indicates that the current file management request is a file query. No client address list is needed, and no feedback information will be sent to the client corresponding to the client information. The server will directly perform file management based on the application's information. If the client information only contains identity and key information, it indicates that the current file management request is a file storage or file download. This file management request needs to be completed through the client. In this case, the server sends feedback information to the application indicating that the first legitimacy check has passed, and this feedback information includes the client address list.

[0055] Upon receiving feedback from the server containing a list of client addresses, the application sends the file management request and corresponding client information to any client represented by that client address in the list. This ensures that the client corresponding to that application can receive the file management request and client information. Because the server and client are independent, to ensure that the file management request received by the client is also sent by an authorized application, a second validity verification request is sent to the server based on the application information sent along with the file management request. The server then performs relevant verification based on this second validity verification request. If the second validity verification passes, the server sends a list of storage information associated with the file management request to the client that sent the second validity verification request. This allows the client to select any storage information from the list to perform the file management work represented by the file management request within the storage resource represented by that storage information.

[0056] After deploying and configuring the server and client, the system executes file management requests received from the application on either the server or client side. The actual storage or downloading of files is handled by the storage resources connected to the client. This separation of the information system's routine functions from file storage allows the system to focus solely on the upper-level file management application without needing to concern itself with the underlying technical details of file storage, thus indirectly ensuring system stability. Specifically, when the storage space of a particular storage resource is insufficient for the next file storage, the resource is set to read-only mode. Subsequent files will not be written to this resource, but files already written to it can still be read normally.

[0057] If either the first or second validity check fails, the server sends a feedback message indicating failure to the application corresponding to the application information. The application receives this feedback and stops responding to the current file management request, thus ending the file management task. This ensures that the file management system in this application only executes file management requests received by authorized and registered application clients, and does not execute file management requests received by unauthorized and registered application clients, thereby preventing potential dangers caused by unauthorized access from other application clients.

[0058] The client is also used to send a completion instruction to the corresponding application after completing the file management task. When the file management request represents file storage, the client completes the file management task through storage resources, and then sends a completion instruction to the application that sent the file management request so that the application knows that the file management request has been completed.

[0059] In addition, if file management is used for file storage, the file management request includes key information and the file body. The client is also used to obtain the storage address where the file body is stored in the storage resource and the descriptive information that characterizes the file body. The client then sends the storage address and descriptive information to the server so that the server associates the storage address and descriptive information in the database and sends it to the client after successfully storing it in the database.

[0060] After the client stores the corresponding file in the storage resource according to the file management request, the client also obtains the storage address and description information of the file text stored in the storage resource. Since the client can proactively send its own information to the server and store it in the database, the database contains the storage address and description file obtained by the client. This allows the server to obtain the corresponding description information only on the server side after receiving a file management request representing a file query, thus completing the file management work represented by the file management request, reducing operational steps and simplifying the process.

[0061] Figure 2 This is a schematic diagram of the file storage process provided in an embodiment of this application. For example... Figure 2 As shown, the file storage process includes the following steps:

[0062] L101: Upon receiving a file management request, the application sends corresponding application information to the server for initial legitimacy verification. This information includes key and identity information. The client accesses the server-provided legitimacy verification interface and inputs the key information. The server performs the initial legitimacy verification. If the verification passes, the server sends feedback to the application containing a list of client addresses accessible to the application. If the verification fails, the server directly sends a termination message to the application, ending the current operation.

[0063] L102: After receiving the list of client addresses, the application can randomly select an address as the address to be uploaded to, and then send the application information and the file text to the previously selected client address.

[0064] L103: After receiving the information from the application, the first step for the client is to access the server for a second validity check to prevent unauthorized applications from initiating file management requests that represent file storage. Once the second validity check is passed, the client will return a list of storage options available to the current application.

[0065] L104: After receiving the list of available storage, the client can randomly select a storage location and then write the received file text into the selected storage resource. Once the file text is successfully written into the corresponding storage resource, the client will send the description information of the current file text and the storage address to the server.

[0066] L105: After receiving the file description information, the server stores the description information and storage address in the database and sends the result back to the client.

[0067] L106: After receiving the result from the server, the client sends a completion instruction to the application indicating whether the file has been successfully stored.

[0068] L107, after receiving the completion instruction, the application completes the process represented by this file management request.

[0069] Figure 3 This is a schematic diagram of the file download process provided in an embodiment of this application. For example... Figure 3 As shown, the file download process includes the following steps:

[0070] L201: Upon receiving a file management request, the application sends corresponding application information to the server for initial legitimacy verification. This information includes key and identity information. The client accesses the server-provided legitimacy verification interface and inputs the key information. The server performs the initial legitimacy verification. If successful, the server sends feedback to the application containing a list of client addresses accessible to the application. If the initial legitimacy verification fails, the server directly sends a termination message to the application, ending the current operation.

[0071] L202: After receiving the list of client addresses, the application can randomly select an address as the address to be uploaded to, and then send the application information and file ID to the previously selected client address.

[0072] L203: After receiving the information from the application, the first step for the client is to access the server for a second validity check to prevent unauthorized applications from initiating file management requests that represent file storage. Once the second validity check is passed, the client will return the description information and storage address of the file to be downloaded.

[0073] L204: After obtaining the storage address of the file, the client directly downloads the corresponding file text from the corresponding storage resource. After successfully obtaining the file text, it sends the relevant data about the file text to the application.

[0074] L205: After receiving the relevant data about the file text, the application completes the process of representing this file management request.

[0075] Figure 4 This is a schematic diagram of the document retrieval process provided in an embodiment of this application. For example... Figure 4 As shown, the process of performing a file search includes the following steps:

[0076] L301: Upon receiving a file management request, the application sends corresponding application information to the server for initial legitimacy verification. This information includes key information, identity information, file type information, and file ID. The client accesses the server-provided legitimacy verification interface and passes in the key information. The server performs the initial legitimacy verification. If the verification passes, the server queries the database for a description matching the file type and file ID and sends the result back to the application. If the verification fails, the server directly sends a termination message to the application, ending the current operation.

[0077] L302: After receiving the query results for the relevant file text, the application completes the process of representing this file management request.

[0078] Figure 5 This is a block diagram of a method for file management provided in an embodiment of this application. For example... Figure 5 As shown, a method for file management includes the following steps:

[0079] In step S100, the application receives a file management request and sends application information corresponding to the file management request to the server.

[0080] In step S200, after receiving the application information, the server performs the first validity check and sends feedback information to the application corresponding to the application information after the check passes. If the check passes and the feedback information does not include the client address list, the server performs file management work represented by the file management request based on the application information.

[0081] In step S300, the application receives feedback information from the server based on the application information, and if the feedback information includes a list of client addresses, sends the file management request and the corresponding application information to any client represented by any client address in the list of client addresses.

[0082] In step S400, upon receiving the file management request, the client sends a second validity verification request to the server.

[0083] In step S500, the server receives the second validity verification request sent by the client based on the file request information, and sends the storage information list to the client after the verification is successful.

[0084] In step S600, if the second validity check passes, the client selects any storage information from the storage information list to perform file management work represented by the file management request in the storage resource represented by the storage information.

[0085] In addition, a file management method also includes an interface module in the client side that allows the client to perform file management tasks in storage resources through the interface module; a storage management module in the server side configures the storage information needed for file management and stores the storage information in a database. The number of storage information entries is at least one, and each storage information entry corresponds to a uniquely identified storage resource. All storage information configured in the server allows the client to perform file management tasks in the corresponding storage resources through the interface module. The other functions performed by the above-described file management method and the technical details of each function are the same as or similar to the corresponding features in the file management system described above, and therefore will not be repeated here.

[0086] It should be understood that although the steps in the flowcharts in the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order requirement for the execution of these steps, and they may be performed in other orders.

[0087] The above description is only a partial embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. An information system for file management, characterized in that, The system comprises an application end, a service end and a client end; wherein The application end is configured to receive a file management request, send application end information corresponding to the file management request to the service end according to the file management request, receive feedback information fed back by the service end according to the application end information, and if the feedback information comprises a client address list, send the file management request and the corresponding application end information to a client represented by any one of the client address list; The service end is configured to perform a first legality check after receiving the application end information, send feedback information to the application end corresponding to the application end information after the check passes, perform file management work in the service end according to the application end information if the check passes and the feedback information does not comprise a client address list, receive a second legality check request sent by the client according to the file request information, and send a storage information list to the client after the check passes; The client is configured to receive the file management request, send a second legality check request to the service end, and if the check passes, select any one of the storage information list to perform file management work represented by the file management request in the storage resource represented by the storage information. The service end further comprises a storage allocation module; wherein The storage allocation module is configured to perform storage resource allocation work for each authorized application end to determine the storage information list corresponding to each application end, so that the service end sends the storage information list to the corresponding client after the second legality check passes, and perform client allocation work for each authorized application end to determine the client address list corresponding to the client accessible by each application end, so that the service end sends the client address list to the corresponding client after the first legality check passes; If the file management is used for file storage, the file management request comprises secret key information and a file body, and the client is further configured to obtain a storage address of the file body stored in the storage resource and description information representing the characteristics of the file body, and send the storage address and the description information to the service end, so that the service end stores the storage address and the description information in the database in association, and sends them to the client after successful storage in the database. The client further comprises an interface module, so that the client can perform file management work in the storage resource through the interface module; 2. The system of claim 1, wherein, The service end further comprises a storage management module, which is configured to configure storage information needed for file management work and store the storage information in the database, wherein the number of the storage information is at least one, and each storage information corresponds to a uniquely determined storage resource, and all the storage information configured in the server can enable the client to perform file management work in the corresponding storage resource through the interface module. The service end further comprises a registration module, which comprises an application authorization registration unit and a deployed client registration unit; wherein 3. The system of claim 1, wherein, ​ The application authorization registration unit is configured to register authorized application end authorization information and store the application end authorization information in a database, so that the service end compares the received application end information with the application end authorization information in the database to perform first legality verification, wherein the application end authorization information includes application end identity information representing the identity of the application end and corresponding secret key information; The deployed client registration unit is configured to register client information corresponding to the deployed clients in the information system and store the client information in a database, wherein the client information includes client identity information representing the identity of the client and corresponding client addresses.

4. The system of claim 1, wherein, The types of storage resources are diversified.

5. The system of claim 1, wherein, The client is further configured to send a completion instruction representing the completion of the file management work to the corresponding application end after completing the file management work.

6. The system of claim 1, wherein, The service end sends feedback information representing failure to the application end corresponding to the application end information if the first legality verification fails or the second legality verification fails; The application end receives the feedback information representing failure sent by the service end to stop responding to the current file management request, so as to end the work management represented by the file management request.

7. A method for file management, characterized by, The method comprises: The application end receives a file management request and sends application end information corresponding to the file management request to the service end according to the file management request; The service end performs first legality verification after receiving the application end information and sends feedback information to the application end corresponding to the application end information after the verification passes, and performs file management represented by the file management request in the service end according to the application end information if the verification passes and the feedback information does not include a client address list; The application end receives feedback information fed back by the service end according to the application end information, and sends the file management request and corresponding application end information to a client represented by any one of the client address list if the feedback information includes the client address list; The client receives the file management request and sends a second legality verification request to the service end; The service end receives the second legality verification request sent by the client according to the file request information and sends a storage information list to the client after the verification passes; If the second legality verification passes, the client selects one storage information from the storage information list to perform file management represented by the file management request in the storage resource represented by the storage information; The service end further comprises a storage allocation module; wherein The storage allocation module is configured to perform storage resource allocation for each authorized application end to determine a storage information list corresponding to each application end, so that the service end sends the storage information list to the corresponding client after the second legality verification passes; and perform client allocation for each authorized application end to determine a client address list corresponding to the accessible client of each application end, so that the service end sends the client address list to the corresponding client after the first legality verification passes. If the file management is used for file storage, the file management request includes key information and file body, the client is further used for obtaining a storage address of a storage resource where the file body is stored and description information representing characteristics of the file body, and sending the storage address and the description information to the server, so that the server stores the storage address and the description information in association in the database, and sends the storage address and the description information to the client after successful storage in the database.

8. The method of claim 7, wherein, The method further comprises: The interface module in the client enables the client to perform file management work in the storage resource through the interface module; The storage management module in the server configures storage information required for file management work, and stores the storage information in the database, wherein the number of the storage information is at least one, and each storage information corresponds to a uniquely determined storage resource, and all the storage information configured in the server enables the client to perform file management work in the corresponding storage resource through the interface module.

Images