WO2020253401A1 - 文件管理方法、装置、系统、设备及计算机可读存储介质 - Google Patents

文件管理方法、装置、系统、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2020253401A1
WO2020253401A1 PCT/CN2020/088129 CN2020088129W WO2020253401A1 WO 2020253401 A1 WO2020253401 A1 WO 2020253401A1 CN 2020088129 W CN2020088129 W CN 2020088129W WO 2020253401 A1 WO2020253401 A1 WO 2020253401A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
client
object storage
file management
index
Prior art date
Application number
PCT/CN2020/088129
Other languages
English (en)
French (fr)
Inventor
胡思文
陈晓峰
李勇
黄善荣
陈景
朱嘉伟
陈文龙
罗锶
杨军
卢道和
Original Assignee
深圳前海微众银行股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳前海微众银行股份有限公司 filed Critical 深圳前海微众银行股份有限公司
Publication of WO2020253401A1 publication Critical patent/WO2020253401A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/122—File system administration, e.g. details of archiving or snapshots using management policies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This application relates to the field of financial technology (Fintech) technology, in particular to file management methods, devices, systems, equipment, and computer-readable storage media.
  • Financial technology Fetech
  • the main purpose of this application is to propose a file management method, device, system, equipment, and computer-readable storage medium, aiming to solve the current technical problems that enterprises use object storage services are troublesome and the object storage service file management is not uniform.
  • the present application provides a file management method, which includes the following steps:
  • the present application also provides a file management device, the file management device includes:
  • the request receiving module is configured to, when receiving the file upload request sent by the client, obtain the user ID corresponding to the file upload request, and perform user identity verification according to the user ID;
  • the path generation module is used to generate a signed object storage path and send it to the client when the user identity verification is passed, so that the client can press the target file corresponding to the file upload request according to the signed Object storage path for storage;
  • the directory maintenance module is configured to receive a file index fed back by the client based on the target file that has been uploaded, and input the file index into a preset file directory.
  • the present application also provides a file management system
  • the file management system includes a file management device, a client and a preset cloud object storage architecture that are connected in communication, and the file management system includes:
  • the file management device When the file management device receives the file upload request sent by the client, the file management device obtains the user ID corresponding to the file upload request, and performs user identity verification according to the user ID;
  • the file management device When the user identity verification is passed, the file management device generates a signed object storage path and sends it to the client;
  • the cloud object storage architecture receives the target file uploaded by the client, and sends the file index of the target file to the client;
  • the client receives the file index sent by the cloud object storage architecture, and sends the file index to the file management device;
  • the file management device receives the file index fed back by the client based on the uploaded target file, and inputs the file index into a preset file directory.
  • the present application also provides a file management device, the file management device includes: a memory, a processor, and a file management program stored in the memory and running on the processor, so When the file management program is executed by the processor, the steps of the file management method described above are implemented.
  • the present application also provides a computer-readable storage medium having a file management program stored on the computer-readable storage medium, and when the file management program is executed by a processor, the file management as described above is realized. Method steps.
  • This application proposes a file management method, device, system, equipment, and computer-readable storage medium; when the file management device in the embodiment of this application receives a file upload request sent by a client, it obtains the file upload request corresponding And perform user identity verification based on the user identity; when the user identity verification is passed, a signed object storage path is generated and sent to the client, so that the client can respond to the file upload request
  • the target file is stored according to the object storage path with the signature; receiving the file index fed back by the client based on the target file after the upload is completed, and inputting the file index into the preset file directory, an embodiment of the application
  • each enterprise does not need to develop the interface code separately, which reduces the waste of human and material resources in the process of enterprise code development.
  • the file management device stores files in the cloud object storage architecture by setting a unified format object storage path to obtain file storage. File index, the file management device saves the file index to the preset file directory, which can quickly find and manage the target files stored in the cloud object storage architecture.
  • FIG. 1 is a schematic diagram of a device structure of a hardware operating environment involved in a solution of an embodiment of the present application
  • FIG. 2 is a schematic flowchart of the first embodiment of the application file management method
  • FIG. 3 is a schematic diagram of a specific scenario of the first embodiment of the application file management method
  • FIG. 5 is a schematic flowchart of a second embodiment of the application file management method
  • FIG. 6 is a schematic flowchart of a third embodiment of the application file management method
  • FIG. 7 is a schematic diagram of interaction of the third embodiment of the application file management method.
  • FIG. 8 is a schematic diagram of interaction of the fifth embodiment of the application file management method.
  • FIG. 9 is a schematic diagram of functional modules of an embodiment of a file management apparatus of this application.
  • FIG. 1 is a schematic diagram of the device structure of the hardware operating environment involved in the solution of the embodiment of the present application.
  • the file management device (also called FPS server, File Processing System server, distributed file management system server) of the embodiment of the present application may be a PC or a server device, on which a Java virtual machine runs.
  • the file management device may include a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 1005 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as a magnetic disk memory.
  • the memory 1005 may also be a storage device independent of the foregoing processor 1001.
  • FIG. 1 does not constitute a limitation on the device, and may include more or fewer components than those shown in the figure, or a combination of certain components, or different component arrangements.
  • a memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a file management program.
  • the network interface 1004 is mainly used to connect to the back-end server and communicate with the back-end server;
  • the user interface 1003 is mainly used to connect to the user end (user end) and communicate with the user end; and the processor 1001 can be used to call a computer program corresponding to file management stored in the memory 1005, and perform operations in the following file management method.
  • the preset cloud object storage architecture refers to a durable and highly available system architecture that can store any object in advance.
  • the preset cloud object storage architecture is independent
  • applications and users can use simple API (Application Programming Interface) to access data in object storage.
  • the preset cloud object storage architecture can be COS (Cloud Object Storage).
  • COS is a distributed storage service that has no directory hierarchy, no data format restrictions, can accommodate massive amounts of data and supports HTTP/HTTPS protocol access; this
  • the preset cloud object storage architecture can also be BOS (Baidu Object Storage).
  • BOS is an Internet-oriented storage service. Users can quickly and easily complete basic functions such as object storage and retrieval through the console interface.
  • FIG. 2 is a schematic flowchart of a first embodiment of a file management method of this application, and the method includes:
  • Step S10 upon receiving the file upload request sent by the client, obtain the user ID corresponding to the file upload request, and perform user identity verification according to the user ID.
  • the file management method in this embodiment is applied to file management equipment.
  • the file management equipment can be installed in financial institutions (financial institutions include banking institutions, insurance institutions, or securities institutions, etc.). Take banking institutions as an example for explanation. Bank institutions’ corresponding file management
  • the device saves the business data in the preset cloud object storage architecture to realize the unified storage, fast query and periodic update of massive banking business data.
  • this application involves the interaction between the client, load balancer, file management device (FPS (File Processing System for Cloud Service, cloud unified file management system) server in the figure), database and COS;
  • the database can be MySQL Database, or HBase database, the database can save the data information in the file management device; it can be understood that the load balancer is used for scheduling of operation requests when the number of customers is large, specifically:
  • the file management device receives the file upload request.
  • the triggering method of the file upload request is not specifically limited. That is, the file upload request can be triggered by the user. For example, the user clicks the "File upload" button on the client to actively trigger the file upload request.
  • the client sends the file upload request to the file management device; or the file upload request can also be automatically triggered by the file management device.
  • the file management device automatically triggers the file upload request when it detects a file added by the client.
  • the file management device determines the user ID corresponding to the file upload request.
  • the user ID refers to the identification information that uniquely identifies the user.
  • the user ID can be user account information, user contact information, and/or User biometric information, the file management device performs user identity verification according to the user ID; specifically, it includes:
  • Step a1 The file management device compares the user ID corresponding to the upload request with the standard user information in the preset user information table; the preset user information table refers to the user information that the user actively enters during registration;
  • Step a2 if there is target standard user information matching the user ID in the preset user information table, the file management device determines that the user identity verification is passed;
  • Step a3 If there is no target standard user information matching the user ID in the preset user information table, the file management device determines that the user identity verification is not passed, and the file management device sends a prompt message to the client to make the client upload a new User ID.
  • the file management device performs user identity verification according to the user identification, avoids attacks from bad users, and ensures the security of cloud object storage.
  • Step S20 When the user identity verification is passed, a signed object storage path is generated and sent to the client, so that the client stores the target file corresponding to the file upload request according to the object storage path.
  • the file management device When the file management device passes the user authentication, the file management device sets the object storage path of the file, that is, the file management device obtains the file identification and processes the file identification to generate a unified format object storage path, specifically:
  • Implementation method 1 The file management device forms a uniform format string in the order of storage date-file identification-user identification, and the file management device uses a digital signature algorithm (such as symmetric encryption or asymmetric encryption) to sign the uniform format string Algorithm) process to generate a signed object storage path;
  • a digital signature algorithm such as symmetric encryption or asymmetric encryption
  • Implementation method 2 The file management device adds the verification code to the file identification to form a uniform format string, and the file management device processes the uniform format string according to the digital signature algorithm to generate a signed object storage path;
  • the file management device gets the signed object storage path
  • the file management device sends the signed object storage path to the client (FpsQClient in the figure) so that the client will
  • the target file corresponding to the file upload request is stored in the preset cloud object storage architecture (Cos) according to the object storage path.
  • the client After the preset cloud object storage architecture receives the target file sent by the client, the client verifies the integrity of the target file, that is, the cloud object storage architecture and the client agree on the hash algorithm, and the cloud object storage architecture is processed according to the hash algorithm
  • the received target file obtains the verification hash value, and the cloud object storage architecture sends the verification hash value to the client;
  • the client receives the verification hash value sent by the cloud object storage architecture.
  • the client processes the target file before uploading according to the agreed hash algorithm to obtain the basic hash value, and the client compares to verify whether the hash value is the same as the basic hash value ; If the verification hash value is different from the basic hash value, the client determines that the target file transmission is incomplete, and the client outputs a prompt message so that the client can re-upload the corresponding user; if the verification hash value is the same as the basic hash value, the client will If the target file is verified, the client sends a verification pass prompt to the cloud object storage architecture, so that the cloud object storage architecture returns a file index (the file index corresponds to the object storage path of the target file, and the specific format of the file index is not limited) To the client, the client receives the file index sent by the cloud object storage architecture and sends the file index to the file management device.
  • Step S30 Receive a file index fed back by the client based on the target file that has been uploaded, and input the file index into a preset file directory.
  • the file management device receives the file index fed back by the client based on the uploaded target file.
  • the file management device inputs the file index into a preset file directory.
  • the preset file directory refers to a preset file query directory.
  • the file management device can be based on the preset file index. Set each file index in the file directory to query and download files of different users.
  • each enterprise does not need to develop the interface code separately, which reduces the waste of human and material resources in the enterprise code development process.
  • the file management device sets the unified format of the object storage path to uniformly store the files in the cloud object storage architecture.
  • the file index of the file storage is obtained, and the file management device saves the file index to the preset file directory, which can quickly find and manage the target files stored in the cloud object storage architecture; in this embodiment, the file management device is set in the associated In different financial institutions, for example, file management equipment is set up in banking institutions and insurance institutions.
  • the business data of different financial institutions can be saved to the cloud object storage architecture in a unified format object storage path, realizing business data of different financial institutions Unified management.
  • step S20 is a refinement of step S20 in the first embodiment.
  • the difference between this embodiment and the first embodiment is that in this embodiment, step S20 may also include:
  • Step S21 When the user identity verification is passed, obtain the file identifier corresponding to the file upload request, and send a time limit setting window to the client.
  • the file management device When the file management device passes the user identity verification, the file management device obtains the file identification corresponding to the file upload request, where the file identification refers to the information that uniquely identifies the file, and the file identification can be the file number and file name. At the same time, the file management The device sends a period setting window to the client, so that the user corresponding to the client can set the storage period of the target file.
  • Step S22 Receive a storage period set by the client based on the period setting window within a preset time period, and convert the storage period and the file identifier into a signed object storage path.
  • the file management device receives the preset time period (the preset time period can be flexibly set according to specific scenarios, for example, the preset time period is set to 3s) within the storage period set by the client based on the period setting window, the file management device will store the storage period and the file The identification is transformed into a signed object storage path.
  • the preset time period can be flexibly set according to specific scenarios, for example, the preset time period is set to 3s
  • Step S23 If the storage period set by the client based on the period setting window is not received for the preset time period, obtain the file attribute of the target file, and set the storage period of the target file according to the file attribute , Transforming the storage period and the file identifier into a signed object storage path.
  • the file management device obtains the file attributes of the target file.
  • the file attributes include: file size (file size refers to the storage space occupied by the file), file type, File creation time, text editing information (text editing information includes but not limited to file editing times, file editing time, and file editing content) and file access information (file access information includes but not limited to file access times, file access time).
  • the file management device sets the storage period of the target file corresponding to the file identifier according to the file attribute, specifically including:
  • Step b1 the file management device queries the preset attribute and score mapping table, and obtains the score corresponding to the file size, file type, file creation time, text editing information, and file access information; among them, the preset attribute and score mapping table
  • the mapping relationship between file attributes and scores is preset. Take the file size in the file attributes as an example. A file size less than 200k corresponds to 8 points, a file size from 200k to 1M corresponds to 6 points, and a file size from 1M to 10M. The corresponding score is 4 points, and the file size greater than 10M corresponds to 2 points.
  • Step b2 The file management device obtains the preset weights corresponding to the file size, file type, file creation time, text editing information and file access information, and corresponds to the file size, file type, file creation time, text editing information and file access information The score is weighted with the corresponding weight to obtain the comprehensive score of the target file corresponding to the file identifier;
  • Step b3 query the preset score and deadline mapping table, obtain the target deadline corresponding to the comprehensive score, and use the target deadline as the storage deadline of the target file, where the preset score and deadline mapping table is preset with scores and deadlines
  • the mapping relationship of the mapping for example, a score greater than 8 points corresponds to a storage period of 5 years, a score value of 8 to 4 points has a storage period of 2 years, and a score value less than 4 points has a storage period of 6 months.
  • the file management device After the file management device determines the storage period of the target file, the file management device converts the storage period and the file identifier into a signed object storage path.
  • the storage period of the target file can be set by the user, or it can be the file management device Set according to the file attributes of the target file, and by setting the storage period of the target file, the long-term occupation of storage space is effectively avoided.
  • the file storage period is set, which can ensure the real-time validity of the data when it is specifically applied to a financial institution.
  • Step S40 When a file download request is received, a user ID and a file ID corresponding to the file download request are obtained, and user identity verification is performed according to the user ID;
  • the file management device is receiving the file download request.
  • the triggering method of the file download request is not specifically limited.
  • the file management device obtains the user ID and file ID corresponding to the file download request.
  • the file management device performs user identity verification based on the user identity. The method of user identity verification You can refer to the first embodiment, and this embodiment will not be repeated.
  • Step S50 When the user identity verification is passed, it is determined whether the target file corresponding to the file identifier has expired;
  • the file management device determines whether the target file corresponding to the file identifier has expired. As shown in Figure 7, the file management device obtains the storage period and current date corresponding to the file identifier. If the current date exceeds the storage period, The target file corresponding to the file identifier is expired, otherwise, it is not expired.
  • Step S60 if the target file corresponding to the file identifier expires, the file management device sends a prompt message to the client.
  • the file management device sends a prompt message to the client.
  • Step S70 If the target file corresponding to the file identifier has not expired, query the preset file directory to obtain the file index corresponding to the file identifier and the object storage path corresponding to the file index; instead of storing the object The path is sent to the client, so that the client downloads the target file according to the object storage path.
  • the file management device queries the preset file directory to obtain the file index corresponding to the file identifier and the object storage path corresponding to the file index.
  • the file management device sends the object storage path to the client, so that the client downloads the target file from the cloud object storage architecture according to the object storage path. That is, the file management device generates a URL (Uniform Resource Locator) according to the file index. Locator) and sent to the client, so that the client clicks on the URL to download the target file; in this embodiment, the file management device can perform file query and download based on the preset file directory, which realizes the file storage of different users in the cloud object storage architecture. Unified management.
  • URL Uniform Resource Locator
  • This embodiment is a step after step S40 in the third embodiment.
  • the difference between this embodiment and the third embodiment lies in:
  • the client enters the first hash value of the target file to be downloaded in the file download request and sends it to the file management device.
  • the file management device obtains the first hash value corresponding to the file download request, and performs hash correction during file download.
  • This embodiment is a refinement of step S60 in the third embodiment.
  • the difference between this embodiment and the third embodiment lies in:
  • the object storage path corresponding to the file index is obtained, and the object storage path is sent to the client, so that the client can Download the target file in the object storage path.
  • the file management device when the file management device determines that the target file corresponding to the file identifier has not expired, it queries the preset file directory to obtain the file index and the second hash value corresponding to the file identifier; where the second hash value is the client when the file is uploaded Sent to the file management device; the file management device determines that the first hash value is different from the second hash value, the file management device sends a prompt message to the client; the file management device determines that the first hash value is the same as the second hash value, the file management device The object storage path corresponding to the file index is obtained, and the object storage path is sent to the client, so that the client downloads the target file to the cloud object storage architecture according to the object storage path.
  • the file management device performs hash verification on the target file when the file is downloaded, to avoid the target file being tampered with in the cloud object storage architecture, and to realize the download management of the target file.
  • This embodiment can be combined with any one or more of the embodiments.
  • the difference between this embodiment and the above-mentioned embodiments is:
  • the file management device When the file management device receives the file deletion instruction, the file management device traverses the preset file directory to find the target file index in the preset file directory that has reached the storage period; the file management device queries the preset according to the file storage period in the file index Index of the target file in the file directory that has reached the storage period.
  • the file management device deletes the expired file corresponding to the target file index and the target file index in the preset file directory.
  • the file management device queries the preset file directory to perform life cycle management on the files uploaded by the user, which is effective Reduce the occupation of storage capacity.
  • the present application also provides a file management device, the file management device includes:
  • the request receiving module 10 is configured to, when receiving a file upload request sent by the client, obtain a user ID corresponding to the file upload request, and perform user identity verification according to the user ID;
  • the path generation module 20 is configured to generate a signed object storage path and send it to the client when the user identity verification is passed, so that the client can assign the target file corresponding to the file upload request according to the signed all The object storage path for storage;
  • the directory maintenance module 30 is configured to receive a file index fed back by the client based on the target file that has been uploaded, and input the file index into a preset file directory.
  • the path generation module 20 includes:
  • An obtaining and sending unit configured to obtain a file identifier corresponding to the file upload request when the user identity verification is passed, and send a time limit setting window to the client;
  • the first generating unit is configured to receive the storage period set by the client based on the period setting window within a preset time period, and convert the storage period and the file identifier into a signed object storage path.
  • the path generation module 20 includes:
  • the attribute obtaining unit is configured to obtain the file attributes of the target file if the storage period set by the client based on the period setting window is not received for a preset period of time, where the file attributes include: file size, File type, file creation time, text editing information and file access information;
  • the second generating unit is configured to set the storage period of the target file according to the file attribute, and convert the storage period and the file identifier into a signed object storage path.
  • the file management device includes:
  • the identity verification module is configured to, when a file download request is received, obtain a user ID and a file ID corresponding to the file download request, and perform user identity verification according to the user ID;
  • the deadline judging module is used to judge whether the target file corresponding to the file identifier has expired when the user identity verification is passed;
  • a path query module configured to query the preset file directory to obtain the file index corresponding to the file identifier and the object storage path corresponding to the file index if the target file corresponding to the file identifier has not expired;
  • the file download module is configured to send the object storage path to the client, so that the client downloads the target file according to the object storage path.
  • the file management device includes:
  • a hash value obtaining module configured to obtain the first hash value corresponding to the file download request
  • the path query module is also used for:
  • the object storage path corresponding to the file index is obtained.
  • the file management device further includes:
  • the directory traversal module is configured to traverse the preset file directory when receiving a file deletion instruction to find the target file index in the preset file directory that has reached the storage period;
  • the file deletion module is used for deleting the expired file corresponding to the target file index and the target file index in the preset file directory.
  • This application also provides a file management system; the file management system includes a file management device, a client and a cloud object storage architecture that are connected in communication, and the file management system includes:
  • the file management device When the file management device receives the file upload request sent by the client, the file management device obtains the user ID corresponding to the file upload request, and performs user identity verification according to the user ID;
  • the file management device When the user identity verification is passed, the file management device generates a signed object storage path and sends it to the client;
  • the cloud object storage architecture receives the target file uploaded by the client, and sends a file index of the target file to the client;
  • the client receives the file index sent by the cloud object storage architecture, and sends the file index to the file management device;
  • the file management device receives the file index fed back by the client based on the uploaded target file, and inputs the file index into a preset file directory.
  • the application also provides a computer-readable storage medium.
  • a file management program is stored on the computer-readable storage medium of the present application, and when the file management program is executed by a processor, the steps of the file management method described above are realized.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种文件管理方法，包括：在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证（S10）；在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储（S20）；接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录（S30）。还公开了一种文件管理装置、系统、设备和计算机可读存储介质。

Description

文件管理方法、装置、系统、设备及计算机可读存储介质
本申请要求于2019年6月18日申请的、申请号为201910535513.5、名称为“文件管理方法、装置、系统、设备及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及金融科技(Fintech)技术领域，尤其涉及文件管理方法、装置、系统、设备及计算机可读存储介质。
背景技术
随着互联网技术，尤其是互联网金融科技(Fintech)的飞速发展，越来越多的技术(大数据、分布式、区块链Blockchain、人工智能等)应用在金融领域。
以大型商业银行为例，通常它们拥有成百上千个业务系统、上亿用户以及海量的业务数据，目前海量的业务数据采用COS(Cloud Object Storage，对象存储)方式进行存储，具体地，企业开发人员根据对象存储服务提供数据接口，编写接口代码，通过接口代码实现业务数据的存储；这样的方式开发周期长效率低下，且每次新的企业接入就需要重复创建存储桶，分配相关访问账户，导致对象存储服务只能对每个企业进行单独管理，并不可以实现真正意义上的文件统一管理。
发明概述
技术问题
问题的解决方案
技术解决方案
本申请的主要目的在于提出一种文件管理方法、装置、系统、设备及计算机可读存储介质，旨在解决当前企业使用对象存储服务较为麻烦，且对象存储服务文件管理不统一的技术问题。
为实现上述目的，本申请提供一种文件管理方法，所述文件管理方法包括如下步骤：
在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；
接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
此外，为实现上述目的，本申请还提供一种文件管理装置，所述文件管理装置包括：
请求接收模块，用于在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
路径生成模块，用于在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；
目录维护模块，用于接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
此外，为实现上述目的，本申请还提供一种文件管理系统，所述文件管理系统包括通信连接的文件管理设备、客户端和预设的云对象存储架构，所述文件管理系统，包括：
文件管理设备在接收到客户端发送的文件上传请求时，文件管理设备获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
文件管理设备在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端；
所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径存储至所述云对象存储架构；
所述云对象存储架构接收所述客户端上传的所述目标文件，并发送所述目标文 件的文件索引至所述客户端；
所述客户端接收所述云对象存储架构发送的所述文件索引，并将所述文件索引发送至所述文件管理设备；
文件管理设备接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
此外，为实现上述目的，本申请还提供一种文件管理设备，所述文件管理设备包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的文件管理程序，所述文件管理程序被所述处理器执行时实现如上所述的文件管理方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有文件管理程序，所述文件管理程序被处理器执行时实现如上所述的文件管理方法的步骤。
本申请提出了一种文件管理方法、装置、系统、设备及计算机可读存储介质；本申请中实施例中文件管理设备在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录，本申请实施例中，不需要每个企业单独开发接口代码，减少了企业代码开发过程中人力物力资源的浪费，文件管理设备通过设置统一格式的对象存储路径，将文件统一存储到云对象存储架构，得到文件存储的文件索引，文件管理设备将文件索引保存至预设文件目录，可以对云对象存储架构中存储的目标文件进行快速查找统一管理。
发明的有益效果
对附图的简要说明
附图说明
图1是本申请实施例方案涉及的硬件运行环境的设备结构示意图；
图2为本申请文件管理方法第一实施例的流程示意图；
图3为本申请文件管理方法第一实施例的具体场景示意图；
图4为本申请文件管理方法第一实施例的交互示意图；
图5为本申请文件管理方法第二实施例的流程示意图；
图6为本申请文件管理方法第三实施例的流程示意图；
图7为本申请文件管理方法第三实施例的交互示意图；
图8为本申请文件管理方法第五实施例的交互示意图；
图9为本申请文件管理装置一实施例的功能模块示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
发明实施例
本发明的实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
如图1所示，图1是本申请实施例方案涉及的硬件运行环境的设备结构示意图。
本申请实施例文件管理设备(又叫FPS服务器，File Processing System serve，分布式文件管理系统服务器)可以是PC机或服务器设备，其上运行有Java虚拟机。如图1所示，该文件管理设备可以包括：处理器1001，例如CPU，网络接口1004，用户接口1003，存储器1005，通信总线1002。其中，通信总线1002用于实现这些组件之间的连接通信。用户接口1003可以包括显示屏(Display)、输入单元比如键盘(Keyboard)，可选用户接口1003还可以包括标准的有线接口、无线接口。网络接口1004可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。存储器1005可以是高速RAM存储器，也可以是稳定的存储器(non-volatile memory)，例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
本领域技术人员可以理解，图1中示出的设备结构并不构成对设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图1所示，作为一种计算机存储介质的存储器1005中可以包括操作系统、网络通信模块、用户接口模块以及文件管理程序。
在图1所示的设备中，网络接口1004主要用于连接后台服务器，与后台服务器进行数据通信；用户接口1003主要用于连接用户端(用户端)，与用户端进行数据通信；而处理器1001可以用于调用存储器1005中存储的文件管理对应的计算机程序，并执行下述文件管理方法中的操作。
基于上述硬件结构，提出本申请文件管理方法实施例。
本申请文件管理方法第一实施例包括：
在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；
接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
本实施例中是基于预设的云对象存储架构提出的，预设的云对象存储架构是指预先设置的可以存储任意对象的一个持久稳固且高度可用系统架构，预设的云对象存储架构独立于虚拟机实例之外，应用和用户可以在对象存储中使用简单的API(Application Programming Interface，应用程序编程接口)访问数据。
预设的云对象存储架构可以是COS(Cloud Object Storage，云对象存储)，COS是无目录层次结构、无数据格式限制，可容纳海量数据且支持HTTP/HTTPS协议访问的分布式存储服务；该预设的云对象存储架构还可以是BOS(Baidu Object Storage百度对象存储)，BOS是一种面向Internet的存储服务，用户可以通过控制台界面，简单快捷的完成对象的存储和检索等基本功能。
参照图2，图2为本申请文件管理方法第一实施例的流程示意图，所述方法包括：
步骤S10，在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证。
本实施例中文件管理方法应用于文件管理设备，文件管理设备可以设置于金融 机构(金融机构包括银行机构、保险机构或证券机构等)，以银行机构为例进行说明，银行机构对应的文件管理设备将业务数据保存至预设的云对象存储架构中，实现海量银行业务数据的统一存储、快速查询和周期性更新，参照图3，图3为本申请文件管理方法第一实施例的具体场景示意图，本申请涉及到客户端、负载均衡器、文件管理设备(如图中的FPS(File Processing System for Cloud Service，云统一的文件管理系统)服务器)、数据库和COS的交互；数据库可以是MySQL数据库，或者HBase数据库，数据库可以保存文件管理设备中的数据信息；可以理解的是负载均衡器用于客户量较多时，操作请求的调度，具体地：
文件管理设备接收文件上传请求，文件上传请求的触发方式不作具体限定，即，文件上传请求可以是用户主动触发的，例如，用户在客户端点击“文件上传”按键，主动触发文件上传请求，客户端将文件上传请求发送至文件管理设备；或者文件上传请求还可以是文件管理设备自动触发的，例如，文件管理设备在检测到客户端新增文件时，自动触发文件上传请求。
文件管理设备在接收到文件上传请求时，文件管理设备确定文件上传请求对应的用户标识，用户标识是指唯一识别用户身份的标识信息，用户标识可以是用户账本信息、用户联系方式信息和/或用户生物特征信息，文件管理设备根据用户标识进行用户身份验证；具体地，包括：
步骤a1，文件管理设备将上传请求对应的用户标识与预设用户信息表中的各标准用户信息比对；其中，预设用户信息表是指用户在注册时主动输入的用户信息；
步骤a2，若预设用户信息表中存在与该用户标识匹配的目标标准用户信息，文件管理设备判定用户身份验证通过；
步骤a3，若预设用户信息表中不存在与该用户标识匹配的目标标准用户信息，文件管理设备判定用户身份验证不通过，文件管理设备发送提示信息至客户端，以使客户端上传新的用户标识。
本实施例中，文件管理设备根据用户标识进行用户身份验证，避免不良用户的攻击，保证了云对象存储的安全性。
步骤S20，在所述用户身份验证通过时，生成带签名的对象存储路径并发送至 所述客户端，以使所述客户端将文件上传请求对应的目标文件按所述对象存储路径进行存储。
文件管理设备在用户身份验证通过时，文件管理设备设置文件的对象存储路径，即，文件管理设备获取文件标识，并将文件标识进行处理生成统一格式的对象存储路径，具体地：
实现方式一：文件管理设备按照存储日期-文件标识-用户标识的顺序形成统一格式的字符串，文件管理设备将统一格式的字符串按照数字签名算法(如，对称加密或者非对称加密等数字签名算法)处理生成带签名的对象存储路径；
实现方式二：文件管理设备将文件标识添加验证码形成统一格式的字符串，文件管理设备将统一格式的字符串按照对数字签名算法处理生成带签名的对象存储路径；
参照图4，文件管理设备(如图中FpsQServer)在得到带签名的对象存储路径之后，文件管理设备将带签名的对象存储路径并发送至客户端(如图中FpsQClient)，以使客户端将文件上传请求对应的目标文件按对象存储路径存储至预设的云对象存储架构(Cos)。
预设的云对象存储架构接收到客户端发送的目标文件之后，客户端对目标文件进行完整性校验，即，云对象存储架构和客户端约定hash算法，云对象存储架构按照该hash算法处理接收到的目标文件，得到校验hash值，云对象存储架构将校验hash值发送至客户端；
客户端接收云对象存储架构发送的校验hash值，以此同时，客户端按照约定的hash算法处理上传之前的目标文件，得到基础hash值，客户比对校验hash值与基础hash值是否相同；若校验hash值与基础hash值不同，客户端确定目标文件传输不完整，客户端输出提示信息，以使客户端对应用户重新上传；若校验hash值与基础hash值相同，客户端对目标文件校验通过，客户端发送校验通过提示至云对象存储架构，以使云对象存储架构返回一个文件索引(文件索引与目标文件的对象存储路径一一对应，文件索引具体格式不作限定)至客户端，客户端接收云对象存储架构发送的文件索引，并将文件索引发送至文件管理设备。
步骤S30，接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并 将所述文件索引输入至预设文件目录。
文件管理设备接收客户端基于上传完成的目标文件反馈的文件索引，文件管理设备将文件索引输入至预设文件目录，预设文件目录是指预先设置的文件查询目录，文件管理设备可以基于该预设文件目录中的各个文件索引，查询下载不同用户的文件。
本申请实施例中，不需要每个企业单独开发接口代码，减少了企业代码开发过程中人力物力资源的浪费，文件管理设备通过设置统一格式的对象存储路径，将文件统一存储到云对象存储架构，得到文件存储的文件索引，文件管理设备将文件索引保存至预设文件目录，可以对云对象存储架构中存储的目标文件进行快速查找统一管理；本实施例中文件管理设备设置在有关联的不同金融机构中，例如，在银行机构和保险机构中设置文件管理设备，不同金融机构的业务数据，都可以按照统一格式的对象存储路径保存至云对象存储架构中，实现了不同金融机构业务数据统一管理。
进一步地，参照图5，在本申请文件管理方法第一实施例的基础上，提出本申请文件管理方法的第二实施例。
本实施例是第一实施例步骤S20的细化，本实施例与第一实施例的区别在于，在本实施例中步骤S20，还可以包括：
步骤S21，在所述用户身份验证通过时，获取所述文件上传请求对应的文件标识，并向所述客户端发送期限设置窗口。
文件管理设备在用户身份验证通过时，文件管理设备获取文件上传请求对应的文件标识，其中，文件标识是指唯一标识文件的信息，文件标识可以是文件编号和文件名称，与此同时，文件管理设备向客户端发送期限设置窗口，以使客户端对应的用户设置该目标文件的存储期限。
步骤S22，接收预设时间段内所述客户端基于所述期限设置窗口设置的存储期限，将所述存储期限和所述文件标识转化为带签名的对象存储路径。
文件管理设备接收预设时间段(预设时间段可以根据具体场景灵活设置，例如，预设时间段设置为3s)内客户端基于期限设置窗口设置的存储期限，文件管理设备将存储期限和文件标识转化为带签名的对象存储路径。
步骤S23，若预设时间段没有接收到所述客户端基于所述期限设置窗口设置的存储期限，则获取所述目标文件的文件属性，并根据所述文件属性设置所述目标文件的存储期限，将所述存储期限和所述文件标识转化为带签名的对象存储路径。
若预设时间段没有接收到客户端基于期限设置窗口设置的存储期限，文件管理设备获取目标文件的文件属性，文件属性包括：文件大小(文件大小是指文件占用的存储空间)、文件类型、文件创建时间、文本编辑信息(文本编辑信息包括但不仅限于文件编辑次数、文件编辑时间和文件编辑内容)和文件访问信息(文件访问信息包括但不仅限于文件访问次数、文件访问时间)。
文件管理设备根据文件属性设置文件标识对应目标文件的存储期限，具体地，包括：
步骤b1，文件管理设备查询预设属性与分值映射表，获取文件大小、文件类型、文件创建时间、文本编辑信息和文件访问信息对应的分值；其中，预设属性与分值映射表中预先设置了文件属性与分值的映射关系，以文件属性中的文件大小为例，文件大小小于200k对应分值8分，文件大小在200k到1M对应分值6分，文件大小在1M到10M对应分值4分，文件大小大于10M对应分值2分。
步骤b2，文件管理设备获取文件大小、文件类型、文件创建时间、文本编辑信息和文件访问信息对应的预设权重，将文件大小、文件类型、文件创建时间、文本编辑信息和文件访问信息对应的分值与各自对应的权重进行加权运算，得到文件标识对应目标文件的综合分值；
步骤b3，查询预设分值与期限映射表，获取综合分值对应的目标期限，并将目标期限作为目标文件的存储期限，其中，预设分值与期限映射表预先设置了分值与期限映射的映射关系，例如，分值大于8分对应存储期限5年，分值8到4分存储期限2年，分值小于4分存储期限6个月。
文件管理设备确定目标文件的存储期限之后，文件管理设备将存储期限和文件标识转化为带签名的对象存储路径，本实施例中目标文件的存储期限可以由用户自行设置，还可以是文件管理设备按照目标文件的文件属性进行设置，通过设置目标文件存储期限，有效地避免了存储空间的长期占用，本实施例中设置 文件存储期限，具体应用在金融机构时，可以保证数据的实时有效性。
进一步地，参照图6，在本申请文件管理方法第二实施例的基础上，提出本申请文件管理方法第三实施例。
本实施例与上述实施例的区别在于：
步骤S40，在接收到文件下载请求时，获取所述文件下载请求对应的用户标识和文件标识，根据所述用户标识进行用户身份验证；
文件管理设备在接收文件下载请求，文件下载请求的触发方式不作具体限定，文件管理设备获取文件下载请求对应的用户标识和文件标识，文件管理设备根据用户标识进行用户身份验证，用户身份验证的方式可以参照第一实施例，本实施例不作赘述。
步骤S50，在所述用户身份验证通过时，判断所述文件标识对应的目标文件是否过期；
文件管理设备在用户身份验证通过时，文件管理设备判断文件标识对应的目标文件是否过期，如图7所示，文件管理设备获取文件标识对应的存储期限和当前日期，若当前日期超过存储期限，则文件标识对应的目标文件过期，反之则没有过期。
步骤S60，若文件标识对应的目标文件过期，文件管理设备发送提示信息至客户端。
若文件标识对应的目标文件过期，文件管理设备发送提示信息至客户端。
步骤S70，若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引，及所述文件索引对应的对象存储路径；并非将所述对象存储路径发送至所述客户端，以使所述客户端根据所述对象存储路径下载所述目标文件。
若文件标识对应的目标文件没有过期，文件管理设备则查询预设文件目录获取文件标识对应的文件索引，及文件索引对应的对象存储路径。文件管理设备将对象存储路径发送至客户端，以使客户端根据对象存储路径从云对象存储架构中下载所述目标文件，即，文件管理设备根据文件索引生成一个URL(Uniform Resource Locator，统一资源定位符)并发送至客户端，以使客户端点击该URL下 载目标文件；本实施例中，文件管理设备可以基于预设文件目录进行文件查询下载，实现了云对象存储架构中不同用户文件的统一管理。
进一步地，在本申请文件管理方法上述实施例的基础上，提出本申请文件管理方法第四实施例。
本实施例是第三实施例中步骤S40之后的步骤，本实施例与第三实施例的区别在于：
获取所述文件下载请求对应的第一hash值。
本实施例中，客户端在文件下载请求中输入待下载目标文件的第一hash值并发送至文件管理设备，文件管理设备获取文件下载请求对应的第一hash值，在文件下载时进行hash校验，具体地：
本实施例是第三实施例中步骤S60的细化，本实施例与第三实施例的区别在于：
若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引和第二hash值；
若所述第一hash值与所述第二hash值相同，则获取所述文件索引对应的对象存储路径，并将所述对象存储路径发送至所述客户端，以使所述客户端根据所述对象存储路径下载所述目标文件。
本实施例中，文件管理设备在确定文件标识对应的目标文件没有过期，则查询预设文件目录获取文件标识对应的文件索引和第二hash值；其中，第二hash值为文件上传时客户端发送至文件管理设备的；文件管理设备确定第一hash值与第二hash值不同，文件管理设备发送提示信息至客户端；文件管理设备确定第一hash值与第二hash值相同，文件管理设备则获取文件索引对应的对象存储路径，并将对象存储路径发送至客户端，以使客户端根据对象存储路径到云对象存储架构下载目标文件。本实施例中文件管理设备在文件下载的时候对目标文件进行hash校验，避免目标文件在云对象存储架构被篡改的情况，实现了目标文件的下载管理。
进一步地，参照图8，在本申请文件管理方法上述实施例的基础上，提出本申请文件管理方法第五实施例。
本实施例可以与任意一个或多个实施例进行结合，本实施例与上述实施例的区别在于：
在接收到文件删除指令时，遍历所述预设文件目录，以查找所述预设文件目录中到达存储期限的目标文件索引；
删除所述目标文件索引对应的过期文件，和所述预设文件目录中的所述目标文件索引。
文件管理设备在接收到文件删除指令时，文件管理设备遍历预设文件目录，以查找预设文件目录中到达存储期限的目标文件索引；文件管理设备根据文件索引中的文件存储期限，查询预设文件目录中到达存储期限的目标文件索引。
文件管理设备删除目标文件索引对应的过期文件，和预设文件目录中的目标文件索引，本实施例中文件管理设通过查询预设文件目录，从而对用户上传的文件执行生命周期管理，有效的降低存储容量的占用。
参照图9，本申请还提供一种文件管理装置，所述文件管理装置包括：
请求接收模块10，用于在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
路径生成模块20，用于在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；
目录维护模块30，用于接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
在一实施例中，所述路径生成模块20，包括：
获取发送单元，用于在所述用户身份验证通过时，获取所述文件上传请求对应的文件标识，并向所述客户端发送期限设置窗口；
第一生成单元，用于接收预设时间段内所述客户端基于所述期限设置窗口设置的存储期限，将所述存储期限和所述文件标识转化为带签名的对象存储路径。
在一实施例中，所述路径生成模块20，包括：
属性获取单元，用于若预设时间段没有接收到所述客户端基于所述期限设置窗口设置的存储期限，则获取所述目标文件的文件属性，其中，所述文件属性包 括：文件大小、文件类型、文件创建时间、文本编辑信息和文件访问信息；
第二生成单元，用于根据所述文件属性设置所述目标文件的存储期限，将所述存储期限和所述文件标识转化为带签名的对象存储路径。
在一实施例中，所述的文件管理装置，包括：
身份验证模块，用于在接收到文件下载请求时，获取所述文件下载请求对应的用户标识和文件标识，根据所述用户标识进行用户身份验证；
期限判断模块，用于在所述用户身份验证通过时，判断所述文件标识对应的目标文件是否过期；
路径查询模块，用于若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引，及所述文件索引对应的对象存储路径；
文件下载模块，用于将所述对象存储路径发送至所述客户端，以使所述客户端根据所述对象存储路径下载所述目标文件。
在一实施例中，所述文件管理装置，包括：
hash值获取模块，用于获取所述文件下载请求对应的第一hash值；
所述路径查询模块，还用于：
若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引和第二hash值；
若所述第一hash值与所述第二hash值相同，则获取所述文件索引对应的对象存储路径。
在一实施例中，所述文件管理装置，还包括：
目录遍历模块，用于在接收到文件删除指令时，遍历所述预设文件目录，以查找所述预设文件目录中到达存储期限的目标文件索引；
文件删除模块，用于删除所述目标文件索引对应的过期文件，和所述预设文件目录中的所述目标文件索引。
上述各程序模块所执行的方法可参照本申请文件管理方法各个实施例，此处不再赘述。
本申请还提供一种文件管理系统；所述文件管理系统包括通信连接的文件管理 设备、客户端和云对象存储架构，所述文件管理系统，包括：
文件管理设备在接收到客户端发送的文件上传请求时，文件管理设备获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
文件管理设备在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端；
所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径存储至所述云对象存储架构；
所述云对象存储架构接收所述客户端上传的所述目标文件，并发送所述目标文件的文件索引至所述客户端；
所述客户端接收所述云对象存储架构发送的所述文件索引，并将所述文件索引发送至所述文件管理设备；
文件管理设备接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
其中，上述文件管理系统所执行的方法可参照本申请文件管理方法各个实施例，此处不再赘述。
本申请还提供一种计算机可读存储介质。
本申请计算机可读存储介质上存储有文件管理程序，所述文件管理程序被处理器执行时实现如上所述的文件管理方法的步骤。
其中，在所述处理器上运行的文件管理程序被执行时所实现的方法可参照本申请文件管理方法各个实施例，此处不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者系统不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者系统所固有的要素。在没有更多限制的情况下，由语句“包括一个......”限定的要素，并不排除在包括该要素的过程、方法、物品或者系统中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例 方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (10)

  1. 一种文件管理方法，其中，所述文件管理方法包括如下步骤：
    在接收到客户端发送的文件上传请求时，获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
    在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；
    接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
  2. 如权利要求1所述的文件管理方法，其中，所述在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端的步骤，包括：
    在所述用户身份验证通过时，获取所述文件上传请求对应的文件标识，并向所述客户端发送期限设置窗口；
    接收预设时间段内所述客户端基于所述期限设置窗口设置的存储期限，将所述存储期限和所述文件标识转化为带签名的对象存储路径。
  3. 如权利要求2所述的文件管理方法，其中，所述在所述用户身份验证通过时，获取所述文件上传请求对应的文件标识，并向所述客户端发送期限设置窗口的步骤之后，包括：
    若预设时间段没有接收到所述客户端基于所述期限设置窗口设置的存储期限，则获取所述目标文件的文件属性，其中，所述文件属性包括：文件大小、文件类型、文件创建时间、文本编辑信息和文件访问信息；
    根据所述文件属性设置所述目标文件的存储期限，将所述存储期限和所述文件标识转化为带签名的对象存储路径。
  4. 如权利要求1所述的文件管理方法，其中，所述文件管理方法，还包括：
    在接收到文件下载请求时，获取所述文件下载请求对应的用户标识和文件标识，根据所述用户标识进行用户身份验证；
    在所述用户身份验证通过时，判断所述文件标识对应的目标文件是否过期；
    若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引，及所述文件索引对应的对象存储路径；
    将所述对象存储路径发送至所述客户端，以使所述客户端根据所述对象存储路径下载所述目标文件。
  5. 如权利要求4所述的文件管理方法，其中，所述在接收到文件下载请求时，获取所述文件下载请求对应的用户标识和文件标识，根据所述用户标识进行用户身份验证的步骤之后，包括：
    获取所述文件下载请求对应的第一hash值；
    所述若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引，及所述文件索引对应的对象存储路径的步骤，包括：
    若所述文件标识对应的目标文件没有过期，则查询所述预设文件目录获取所述文件标识对应的文件索引和第二hash值；
    若所述第一hash值与所述第二hash值相同，则获取所述文件索引对应的对象存储路径。
  6. 如权利要求1至5任意一项所述的文件管理方法，其中，所述文件管理方法，还包括：
    在接收到文件删除指令时，遍历所述预设文件目录，以查找所述预设文件目录中到达存储期限的目标文件索引；
    删除所述目标文件索引对应的过期文件，和所述预设文件目录中的所述目标文件索引。
  7. 一种文件管理装置，其中，所述文件管理装置包括：
    请求接收模块，用于在接收到客户端发送的文件上传请求时，获 取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
    路径生成模块，用于在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端，以使所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径进行存储；
    目录维护模块，用于接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
  8. 一种文件管理系统，其中，所述文件管理系统包括通信连接的文件管理设备、客户端和云对象存储架构，所述文件管理系统，包括：
    文件管理设备在接收到客户端发送的文件上传请求时，文件管理设备获取所述文件上传请求对应的用户标识，并根据所述用户标识进行用户身份验证；
    文件管理设备在所述用户身份验证通过时，生成带签名的对象存储路径并发送至所述客户端；
    所述客户端将文件上传请求对应的目标文件按带签名的所述对象存储路径存储至所述云对象存储架构；
    所述云对象存储架构接收所述客户端上传的所述目标文件，并发送所述目标文件的文件索引至所述客户端；
    所述客户端接收所述云对象存储架构发送的所述文件索引，并将所述文件索引发送至所述文件管理设备；
    文件管理设备接收所述客户端基于上传完成的所述目标文件反馈的文件索引，并将所述文件索引输入至预设文件目录。
  9. 一种文件管理设备，其中，所述文件管理设备包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的文件管理程序，所述文件管理程序被所述处理器执行时实现如权利要求1至6中任一项所述的文件管理方法的步骤。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存 储有文件管理程序，所述文件管理程序被处理器执行时实现如权利要求1至6中任一项所述的文件管理方法的步骤。
PCT/CN2020/088129 2019-06-18 2020-04-30 文件管理方法、装置、系统、设备及计算机可读存储介质 WO2020253401A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910535513.5 2019-06-18
CN201910535513.5A CN110263001B (zh) 2019-06-18 2019-06-18 文件管理方法、装置、系统、设备及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2020253401A1 true WO2020253401A1 (zh) 2020-12-24

Family

ID=67919718

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/088129 WO2020253401A1 (zh) 2019-06-18 2020-04-30 文件管理方法、装置、系统、设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN110263001B (zh)
WO (1) WO2020253401A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110263001B (zh) * 2019-06-18 2024-02-06 深圳前海微众银行股份有限公司 文件管理方法、装置、系统、设备及计算机可读存储介质
CN111125017B (zh) * 2019-12-26 2023-10-13 深圳前海环融联易信息科技服务有限公司 基于树形结构的数据存储方法、装置及计算机设备
CN111291002B (zh) * 2020-03-05 2023-07-18 深圳市网心科技有限公司 文件对账方法、装置、计算机设备及存储介质
CN111651408B (zh) * 2020-06-08 2024-05-03 Oppo广东移动通信有限公司 获取数据的方法、装置、终端及存储介质
CN113315801B (zh) * 2020-06-08 2024-06-04 阿里巴巴集团控股有限公司 存储区块链数据的方法和系统
CN112380167B (zh) * 2020-11-17 2024-06-25 深圳市和讯华谷信息技术有限公司 批量数据验证方法、装置、计算机设备及存储介质
CN113037770B (zh) * 2021-03-29 2022-09-06 武汉华工安鼎信息技术有限责任公司 一种基于存储虚拟化的工控数据安全系统及方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080040448A1 (en) * 2006-08-11 2008-02-14 International Business Machines Corporation Transferring web contents
CN103841170A (zh) * 2012-11-27 2014-06-04 联想(北京)有限公司 一种云存储方法和服务器
CN104636452A (zh) * 2015-01-28 2015-05-20 江苏大学 一种面向scm的统一文件系统管理方法
CN110263001A (zh) * 2019-06-18 2019-09-20 深圳前海微众银行股份有限公司 文件管理方法、装置、系统、设备及计算机可读存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103281325B (zh) * 2013-06-04 2018-03-02 北京奇虎科技有限公司 基于云安全的文件处理方法及装置
CN108268996A (zh) * 2017-11-06 2018-07-10 中国平安财产保险股份有限公司 任务跟踪处理方法、系统、计算机设备以及存储介质
CN109729386B (zh) * 2019-01-03 2021-06-15 深圳市网心科技有限公司 一种视频文件启播方法、系统及电子设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080040448A1 (en) * 2006-08-11 2008-02-14 International Business Machines Corporation Transferring web contents
CN103841170A (zh) * 2012-11-27 2014-06-04 联想(北京)有限公司 一种云存储方法和服务器
CN104636452A (zh) * 2015-01-28 2015-05-20 江苏大学 一种面向scm的统一文件系统管理方法
CN110263001A (zh) * 2019-06-18 2019-09-20 深圳前海微众银行股份有限公司 文件管理方法、装置、系统、设备及计算机可读存储介质

Also Published As

Publication number Publication date
CN110263001A (zh) 2019-09-20
CN110263001B (zh) 2024-02-06

Similar Documents

Publication Publication Date Title
WO2020253401A1 (zh) 文件管理方法、装置、系统、设备及计算机可读存储介质
US10687210B2 (en) Switching mobile service provider using blockchain
CN110494876B (zh) 用于在分布式网络节点内发布和追踪数字令牌的系统和方法
US20210243193A1 (en) Systems, methods, and apparatuses for implementing consensus on read via a consensus on write smart contract trigger for a distributed ledger technology (dlt) platform
CN111771194B (zh) 用于在分布式网络节点内生成和维护不可变的数字会议记录的系统和方法
US10623476B2 (en) Endpoint management system providing an application programming interface proxy service
US10579424B2 (en) Prioritization in a permissioned blockchain
US20220276910A1 (en) Dynamically integrating a client application with third-party services
JP7144117B2 (ja) モデルトレーニングシステムおよび方法および記憶媒体
CN110494877B (zh) 用于在分布式网络节点内发布和追踪数字令牌的系统和方法
US11050690B2 (en) Method for providing recording and verification service for data received and transmitted by messenger service, and server using method
JP5429912B2 (ja) 認証システム、認証サーバ、サービス提供サーバ、認証方法、及びプログラム
JP2019160312A (ja) ブロックチェーン・ノード、ブロックチェーン・ノードの方法、およびブロックチェーン・ノードのコンピュータ・プログラム
US11539711B1 (en) Content integrity processing on browser applications
EP3513316B1 (en) Personalized search environment
US11275867B1 (en) Content integrity processing
US20230421570A1 (en) Accessing data on a blockchain with proof of data verification
CN107343028B (zh) 一种基于http协议的通信方法及系统
CN105141586A (zh) 一种对用户进行验证的方法和系统
CN112685451B (zh) 数据查询处理方法、装置、计算机设备及存储介质
KR102690041B1 (ko) 블록체인 기반의 복지혜택 제공 시스템 및 방법과 이를 위한 컴퓨터 프로그램
US20200250138A1 (en) Information read/write method and apparatus based on blockchain
CN118690400A (zh) 数据处理方法、装置、计算机设备、存储介质及产品
CN115426142A (zh) 调用加密数据服务接口的方法、装置和计算机设备
JP2023546883A (ja) コネクテッドｔｖアプリケーション及びオーバ・ザ・トップ・アプリケーションのためのプライバシ・マネージャ

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20825971

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20825971

Country of ref document: EP

Kind code of ref document: A1