CN110708355A - File uploading method, system, device and readable storage medium - Google Patents
File uploading method, system, device and readable storage medium Download PDFInfo
- Publication number
- CN110708355A CN110708355A CN201910839156.1A CN201910839156A CN110708355A CN 110708355 A CN110708355 A CN 110708355A CN 201910839156 A CN201910839156 A CN 201910839156A CN 110708355 A CN110708355 A CN 110708355A
- Authority
- CN
- China
- Prior art keywords
- file
- uploading
- uploaded
- target file
- tail
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a file uploading method, which comprises the following steps: acquiring a file uploading request, and determining a file to be uploaded and a target file according to the file uploading request; judging whether the target file exists in a storage system or not; wherein, the target file consists of a head object and at least one tail object; and if so, uploading the file to be uploaded to the tail object of the target file. When a scene needing to be uploaded is generated in real time by facing data, the method and the device can directly upload the subsequently generated files additionally and store the files in the same file, so that the trouble that new objects need to be uploaded continuously is avoided, and the uploading process of the objects in the distributed object storage system is simplified. The application also provides a system, equipment and a readable storage medium for uploading the file, and the system, the equipment and the readable storage medium have the beneficial effects.
Description
Technical Field
The present application relates to the field of file uploading, and in particular, to a method, a system, a device, and a readable storage medium for file uploading.
Background
In the distributed object storage system, after the uploading of the object is finished, the content of the object is fixed and can only be read but cannot be modified. If the object content has changed, only the object with the same name can be re-uploaded to overwrite the previously uploaded content. This feature is inconvenient in many application scenarios, such as video surveillance, video live broadcast, etc., where video data is continuously generated in real time. If a common uploading mode is used, the video stream can only be cut into small blocks according to a certain rule and then new objects are continuously uploaded. The method has obvious defects in practical use, and if the object segmentation is small, a plurality of objects are caused, and the management is complex; if the object slicing is large, the data delay is high.
Therefore, how to simplify the uploading process of objects in the distributed object storage system is a technical problem that needs to be solved by those skilled in the art at present.
Disclosure of Invention
The application aims to provide a file uploading method, a file uploading system, a file uploading device and a readable storage medium, which are used for simplifying the uploading process of objects in a distributed object storage system.
In order to solve the above technical problem, the present application provides a method for uploading a file, including:
acquiring a file uploading request, and determining a file to be uploaded and a target file according to the file uploading request;
judging whether the target file exists in a storage system or not; wherein, the target file consists of a head object and at least one tail object;
and if so, uploading the file to be uploaded to the tail object of the target file.
Optionally, before uploading the file to be uploaded to the tail object of the target file, the method further includes:
acquiring state information stored in the head object;
judging whether the target file is of an additionally-uploaded type or not according to the state information;
if not, canceling the uploading, and returning prompt information of uploading failure.
Optionally, after the file to be uploaded is uploaded to the tail object of the target file, the method further includes:
when the last tail object is full, creating an adjacent object according to the state information; wherein the neighboring object is adjacent to the tail object;
and uploading the rest files to be uploaded to the adjacent objects.
Optionally, after the file to be uploaded is uploaded to the tail object of the target file, the method further includes:
and determining metadata information of the target file, and updating the metadata information into identification information of a head object of the target file.
The present application further provides a system for uploading a file, the system comprising:
the first acquisition module is used for acquiring a file uploading request and determining a file to be uploaded and a target file according to the file uploading request;
the first judgment module is used for judging whether the target file exists in a storage system or not; wherein, the target file consists of a head object and at least one tail object;
and the first uploading module is used for uploading the file to be uploaded to a tail object of the target file when the target file exists in the storage system.
Optionally, the method further includes:
a second obtaining module, configured to obtain state information stored in the head object before the file to be uploaded is uploaded to the tail object of the target file;
the second judging module is used for judging whether the target file is of an additionally-uploaded type or not according to the state information;
and the return module is used for canceling the uploading and returning prompt information of uploading failure when the target file is not in the additionally-uploaded type.
Optionally, the method further includes:
the creating module is used for creating an adjacent object according to the state information when the tail object is full; wherein the neighboring object is adjacent to the tail object;
and the second uploading module is used for uploading the remaining files to be uploaded to the adjacent objects.
Optionally, the method further includes:
and the determining module is used for determining the metadata information of the target file and updating the metadata information into the identification information of the head object of the target file.
The present application further provides a file uploading apparatus, which includes:
a memory for storing a computer program;
a processor for implementing the steps of the file uploading method according to any one of the above when the computer program is executed.
The present application also provides a readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method for uploading a file according to any one of the above.
The file uploading method provided by the application comprises the following steps: acquiring a file uploading request, and determining a file to be uploaded and a target file according to the file uploading request; judging whether the target file exists in a storage system or not; wherein, the target file consists of a head object and at least one tail object; and if so, uploading the file to be uploaded to the tail object of the target file.
According to the technical scheme, the target file is determined according to the file uploading request, whether the target file with the same name as the file to be uploaded exists in the storage system or not is judged, if yes, the file to be uploaded is uploaded to the tail object of the target file, when a scene needing to be uploaded is generated in real time in the face of data, the file can be uploaded additionally and stored in the same file, the trouble that a new object needs to be uploaded continuously is avoided, and the uploading process of the object in the distributed object storage system is simplified. The application also provides a system, a device and a readable storage medium for uploading files, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for uploading a file according to an embodiment of the present application;
FIG. 2 is a flowchart of an actual representation of S103 in the method for uploading files provided in FIG. 1;
fig. 3 is a block diagram of a system for uploading a file according to an embodiment of the present application;
fig. 4 is a block diagram of another file uploading system provided in an embodiment of the present application;
fig. 5 is a structural diagram of a file uploading device according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a method, a system, a device and a readable storage medium for uploading files, which are used for simplifying the uploading process of objects in a distributed object storage system.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a file uploading method according to an embodiment of the present application.
The method specifically comprises the following steps:
s101: acquiring a file uploading request, and determining a file to be uploaded and a target file according to the file uploading request;
the file to be uploaded is a file to be uploaded into the system, and the content of the file to be uploaded is fixed and can only be read and cannot be modified after the object is uploaded in the distributed object storage system. If the object content is changed, only the object with the same name can be uploaded again to cover the previously uploaded content, and aiming at the fields of video monitoring, video live broadcast and the like, because video data is continuously generated, if a common uploading mode is used, only a video stream can be divided into small blocks according to a certain rule and then a new object is continuously uploaded, so that the management is complicated; therefore, the present application provides a method for uploading a file, which is used to solve the above problems.
S102: judging whether a target file exists in a storage system or not;
if yes, go to step S103;
in the storage system, the target file consists of a head object and at least one tail object, and the judgment mentioned here judges whether the target file exists in the storage system or not, and aims to detect whether the target file which is to be uploaded and can be uploaded additionally exists in the storage system or not;
optionally, when the target file does not exist in the storage system, a storage object may also be established, and the file to be uploaded is uploaded to the storage object, so as to complete the uploading operation.
S103: and uploading the file to be uploaded to a tail object at the tail of the target file.
Optionally, after the file to be uploaded is uploaded to the tail object of the target file, metadata information of the target file may be determined, and the metadata information is updated to the identification information of the head object of the target file, so that the program can directly obtain data corresponding to the file to be uploaded when calling the target file;
optionally, the identification information mentioned herein may specifically include, but is not limited to, an entity value of the requested variable, an object type identifier, and other information.
Based on the technical scheme, the file uploading method determines the target file according to the file uploading request, judges whether the target file with the same name as the file to be uploaded exists in the storage system, and uploads the file to be uploaded to the tail object of the target file if the target file exists, so that when a scene needing to be uploaded is generated in real time in the face of data, the subsequently generated file can be directly uploaded additionally and stored in the same file, the trouble of continuously uploading a new object is avoided, and the uploading process of the object in the distributed object storage system is simplified.
With respect to step S103 of the previous embodiment, before uploading the file to be uploaded to the tail object of the target file, the steps shown in fig. 2 may also be performed, which is described below with reference to fig. 2.
Referring to fig. 2, fig. 2 is a flowchart of another file uploading method according to an embodiment of the present application.
The method specifically comprises the following steps:
s201: acquiring state information stored in the head object;
s202: judging whether the target file is of an additionally-uploaded type or not according to the state information;
if yes, go to step S103; if not, go to step S203;
the status information mentioned here may include, but is not limited to, the size, the type, the size of the last stripe object, and the like of the target file, after the status information of the target file is obtained, it is determined whether the target file is an additionally uploadable type according to the status information, so as to determine whether to upload the file to be uploaded to the target file, and if the target file is not an additionally uploadable type, step S203 is performed to cancel the uploading, and a prompt message indicating that the uploading fails is returned.
S203: and canceling the uploading, and returning prompt information of uploading failure.
On this basis, after uploading the file to be uploaded to the tail object of the target file, the method further comprises the following steps:
when the tail object is full, creating an adjacent object according to the state information; wherein the adjacent object is adjacent to the tail object;
and uploading the rest files to be uploaded to the adjacent objects.
The method comprises the steps that a file is stored in a storage system in a mode of adding one or more tail objects to one head object, the head object stores state information of the file, the tail object stores data, and the size of the storage object is limited, so that when the tail object of a target file is full, an adjacent object adjacent to the tail object is created according to the state information, and then the remaining file to be uploaded is uploaded to the adjacent object, so that the adjacent object becomes a new tail object of the target file;
further, when the adjacent object is full, a new adjacent object adjacent to the adjacent object can be created according to the state information, then the remaining files to be uploaded are uploaded to the new adjacent object, and the process is repeatedly executed until all the files to be uploaded are uploaded.
Referring to fig. 3, fig. 3 is a structural diagram of a file uploading system according to an embodiment of the present application.
The system may include:
the first obtaining module 100 is configured to obtain a file uploading request, and determine a file to be uploaded and a target file according to the file uploading request;
a first judging module 200, configured to judge whether a target file exists in a storage system; wherein, the target file consists of a head object and at least one tail object;
the first uploading module 300 is configured to, when a target file exists in the storage system, upload a file to be uploaded to a tail object of the target file.
Referring to fig. 4, fig. 4 is a structural diagram of another file uploading system according to an embodiment of the present application.
The system may further comprise:
the second acquisition module is used for acquiring the state information stored in the head object before uploading the file to be uploaded to the tail object of the target file;
the second judging module is used for judging whether the target file is of an additionally-uploaded type or not according to the state information;
and the return module is used for canceling the uploading and returning prompt information of uploading failure when the target file is not in the type of being additionally uploaded.
The system may further comprise:
the creating module is used for creating an adjacent object according to the state information when the tail object is full; wherein the adjacent object is adjacent to the tail object;
and the second uploading module is used for uploading the remaining files to be uploaded to the adjacent objects.
The system may further comprise:
and the determining module is used for determining the metadata information of the target file and updating the metadata information into the identification information of the head object of the target file.
The various components of the above system may be practically applied in the following embodiments:
the first acquisition module acquires a file uploading request and determines a file to be uploaded and a target file according to the file uploading request; the first judgment module judges whether a target file exists in the storage system or not; when the target file exists in the storage system, the second acquisition module acquires the state information stored in the head object; the second judging module judges whether the target file is of an additionally-uploaded type or not according to the state information; and when the target file is of an additionally uploaded type, the first uploading module uploads the file to be uploaded to the tail object of the target file. The determining module determines metadata information of the target file and updates the metadata information into identification information of a head object of the target file; when the tail object is full, the creating module creates an adjacent object according to the state information; and the second uploading module uploads the rest files to be uploaded to the adjacent objects.
And when the target file is not of the type capable of being uploaded additionally, the return module cancels the uploading and returns prompt information of uploading failure.
Referring to fig. 5, fig. 5 is a structural diagram of a file uploading device according to an embodiment of the present application.
The file uploading device 500 may vary greatly in configuration or performance, and may include one or more processors (CPUs) 522 (e.g., one or more processors) and memory 532, one or more storage media 530 (e.g., one or more mass storage devices) storing applications 542 or data 544. Memory 532 and storage media 530 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 530 may include one or more modules (not shown), each of which may include a sequence of instruction operations for the device. Still further, the central processor 522 may be configured to communicate with the storage medium 530, and execute a series of instruction operations in the storage medium 530 on the file upload apparatus 500.
The file upload apparatus 500 may also include one or more power supplies 525, one or more wired or wireless network interfaces 550, one or more input-output interfaces 558, and/or one or more operating systems 541, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps in the file uploading method described in fig. 1 to 2 above are implemented by the file uploading device based on the structure shown in fig. 5.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the module described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a function calling device, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
A method, a system, a device and a readable storage medium for uploading a file provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A method for uploading a file, comprising:
acquiring a file uploading request, and determining a file to be uploaded and a target file according to the file uploading request;
judging whether the target file exists in a storage system or not; wherein, the target file consists of a head object and at least one tail object;
and if so, uploading the file to be uploaded to the tail object of the target file.
2. The method according to claim 1, before uploading the file to be uploaded into the tail object of the target file, further comprising:
acquiring state information stored in the head object;
judging whether the target file is of an additionally-uploaded type or not according to the state information;
if not, canceling the uploading, and returning prompt information of uploading failure.
3. The method according to claim 2, further comprising, after uploading the file to be uploaded into the tail object of the target file:
when the last tail object is full, creating an adjacent object according to the state information; wherein the neighboring object is adjacent to the tail object;
and uploading the rest files to be uploaded to the adjacent objects.
4. The method according to claim 1, further comprising, after uploading the file to be uploaded into the tail object of the target file:
and determining metadata information of the target file, and updating the metadata information into identification information of a head object of the target file.
5. A system for uploading a file, comprising:
the first acquisition module is used for acquiring a file uploading request and determining a file to be uploaded and a target file according to the file uploading request;
the first judgment module is used for judging whether the target file exists in a storage system or not; wherein, the target file consists of a head object and at least one tail object;
and the first uploading module is used for uploading the file to be uploaded to a tail object of the target file when the target file exists in the storage system.
6. The system of claim 5, further comprising:
a second obtaining module, configured to obtain state information stored in the head object before the file to be uploaded is uploaded to the tail object of the target file;
the second judging module is used for judging whether the target file is of an additionally-uploaded type or not according to the state information;
and the return module is used for canceling the uploading and returning prompt information of uploading failure when the target file is not in the additionally-uploaded type.
7. The system of claim 5, further comprising:
the creating module is used for creating an adjacent object according to the state information when the tail object is full; wherein the neighboring object is adjacent to the tail object;
and the second uploading module is used for uploading the remaining files to be uploaded to the adjacent objects.
8. The system of claim 5, further comprising:
and the determining module is used for determining the metadata information of the target file and updating the metadata information into the identification information of the head object of the target file.
9. A file uploading device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the method for uploading a document according to any of claims 1 to 4 when executing the computer program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when being executed by a processor, realizes the steps of the method for uploading a file according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910839156.1A CN110708355A (en) | 2019-09-05 | 2019-09-05 | File uploading method, system, device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910839156.1A CN110708355A (en) | 2019-09-05 | 2019-09-05 | File uploading method, system, device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110708355A true CN110708355A (en) | 2020-01-17 |
Family
ID=69194390
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910839156.1A Pending CN110708355A (en) | 2019-09-05 | 2019-09-05 | File uploading method, system, device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110708355A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113126923A (en) * | 2021-04-21 | 2021-07-16 | 山东英信计算机技术有限公司 | Additional uploading method, system, equipment and storage medium for distributed object storage |
| CN115858473A (en) * | 2023-01-29 | 2023-03-28 | 北京阿丘科技有限公司 | Data interaction method and device based on training system and object storage system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1522927A2 (en) * | 2003-10-10 | 2005-04-13 | Sony Corporation | File storage apparatus capable of restoring file management information |
| CN102117623A (en) * | 2009-12-30 | 2011-07-06 | 北大方正集团有限公司 | Method and device for recovering magnetic tape metadata |
| CN102622350A (en) * | 2011-01-26 | 2012-08-01 | 腾讯科技（深圳）有限公司 | Method, device and system for writing data |
| CN105306860A (en) * | 2015-10-12 | 2016-02-03 | 东方网力科技股份有限公司 | Video recording data storage method and device |
| CN109669632A (en) * | 2018-12-10 | 2019-04-23 | 浪潮电子信息产业股份有限公司 | Metadata wiring method, device and medium based on distributed objects storage system |
| CN109933570A (en) * | 2019-03-15 | 2019-06-25 | 中山大学 | A kind of metadata management method, system and medium |
-
2019
- 2019-09-05 CN CN201910839156.1A patent/CN110708355A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1522927A2 (en) * | 2003-10-10 | 2005-04-13 | Sony Corporation | File storage apparatus capable of restoring file management information |
| CN102117623A (en) * | 2009-12-30 | 2011-07-06 | 北大方正集团有限公司 | Method and device for recovering magnetic tape metadata |
| CN102622350A (en) * | 2011-01-26 | 2012-08-01 | 腾讯科技（深圳）有限公司 | Method, device and system for writing data |
| CN105306860A (en) * | 2015-10-12 | 2016-02-03 | 东方网力科技股份有限公司 | Video recording data storage method and device |
| CN109669632A (en) * | 2018-12-10 | 2019-04-23 | 浪潮电子信息产业股份有限公司 | Metadata wiring method, device and medium based on distributed objects storage system |
| CN109933570A (en) * | 2019-03-15 | 2019-06-25 | 中山大学 | A kind of metadata management method, system and medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113126923A (en) * | 2021-04-21 | 2021-07-16 | 山东英信计算机技术有限公司 | Additional uploading method, system, equipment and storage medium for distributed object storage |
| CN115858473A (en) * | 2023-01-29 | 2023-03-28 | 北京阿丘科技有限公司 | Data interaction method and device based on training system and object storage system |
| CN115858473B (en) * | 2023-01-29 | 2023-10-10 | 北京阿丘科技有限公司 | Data interaction method and device based on training system and object storage system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11080143B2 (en) | Systems and processes for data backup and recovery | |
| EP3084613A1 (en) | Management of storage in a storage network | |
| CN110753112A (en) | Elastic expansion method and device of cloud service | |
| CN112395157B (en) | Audit log acquisition method and device, computer equipment and storage medium | |
| CN112925759B (en) | Data file processing method and device, storage medium and electronic device | |
| CN106648445B (en) | Data storage method and device for web crawler | |
| US10990483B2 (en) | Minimizing a footprint of incremental backups | |
| CN110708355A (en) | File uploading method, system, device and readable storage medium | |
| CN108875035B (en) | Data storage method of distributed file system and related equipment | |
| CN108363727B (en) | Data storage method and device based on ZFS file system | |
| CN112860412B (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN109710454A (en) | A kind of cloud host snapshot method and device | |
| CN107357864B (en) | File processing method and terminal | |
| CN107633080B (en) | User task processing method and device | |
| CN110442439B (en) | Task process processing method and device and computer equipment | |
| CN110532457B (en) | Method and system for acquiring network segment ID | |
| CN107422991B (en) | Storage strategy management system | |
| CN112506429B (en) | Method, device, equipment and storage medium for deleting | |
| CN112445952B (en) | Data management method, device, equipment and storage medium | |
| CN110704382B (en) | File deployment method, device, server and storage medium | |
| CN114048171A (en) | Image data storage method, device, medium and equipment | |
| CN112684985B (en) | Data writing method and device | |
| CN111782588A (en) | File reading method, device, equipment and medium | |
| CN110990665A (en) | Data processing method, device, system, electronic equipment and storage medium | |
| CN116909816B (en) | Database recovery method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200117 |
|
| RJ01 | Rejection of invention patent application after publication |