CN110703980B - File transmission method and device - Google Patents

File transmission method and device Download PDF

Info

Publication number
CN110703980B
CN110703980B CN201810745872.9A CN201810745872A CN110703980B CN 110703980 B CN110703980 B CN 110703980B CN 201810745872 A CN201810745872 A CN 201810745872A CN 110703980 B CN110703980 B CN 110703980B
Authority
CN
China
Prior art keywords
file
target
node server
uploading
cloud storage
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.)
Active
Application number
CN201810745872.9A
Other languages
Chinese (zh)
Other versions
CN110703980A (en
Inventor
陈青龙
陈影旺
吴小云
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wangsu Science and Technology Co Ltd
Original Assignee
Wangsu Science and Technology Co Ltd
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 Wangsu Science and Technology Co Ltd filed Critical Wangsu Science and Technology Co Ltd
Priority to CN201810745872.9A priority Critical patent/CN110703980B/en
Publication of CN110703980A publication Critical patent/CN110703980A/en
Application granted granted Critical
Publication of CN110703980B publication Critical patent/CN110703980B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604Improving or facilitating administration, e.g. storage management
    • G06F3/0607Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638Organizing or formatting or addressing of data
    • G06F3/0643Management of files
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0668Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

The invention discloses a file transmission method and device. The method comprises the following steps: for any node server in the node server cluster, the node server can firstly generate corresponding meta information according to the received uploading file, and then send the uploading file and the meta information to the cloud storage device so as to enable the cloud storage device to store the meta information. On the one hand, a plurality of client devices in the client cluster can simultaneously send the uploading files to the node server cluster, so that the purpose of quick file transmission can be realized, and the file transmission rate is improved; on the other hand, after each node server receives the files sent by the client device, the files can be synchronously stored in the same storage position in the cloud storage device, so that a user can directly manage the files through the cloud storage device, and the user can conveniently and intensively manage the files.

Description

File transmission method and device
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for file transmission.
Background
With the rapid development of internet technology, the data volume of network information is also becoming larger, and the requirement of enterprises for storing mass data is becoming more important. The conventional file storage system has the problems of limited disk space, insufficient processing capacity and the like, and cannot meet the high-capacity storage requirement of users.
One existing solution is to upload files to be stored by a user to a plurality of node servers in a distributed storage manner, so as to meet the high-capacity storage requirement of the user. For example, if a distributed method is adopted, 500GB of files can be stored in the node server a, and another 500GB of files can be stored in the node server B. However, since the files are distributed in different node servers, when the user manages the files, it is necessary to manage part of the files stored in the node server a and the files stored in the node server B at the same time, so that the requirement of centralized management of the user cannot be satisfied.
Another solution is to use a centralized cloud storage service to centrally upload the files to be stored by the user into the cloud storage device. However, although this method can meet the requirement of the user for centralized management of the files, because the uploading rate that can be provided by the cloud storage device is limited, the method cannot meet the requirement of the user for uploading the files rapidly and concurrently when the data volume of the files is excessive.
Based on this, a file transmission method is needed at present, which is used for solving the problem that in the prior art, quick uploading and centralized management cannot be considered in the file transmission process.
Disclosure of Invention
The embodiment of the invention provides a file transmission method and device, which are used for solving the technical problem that the requirement of centralized management of users cannot be met when data are stored in a distributed manner in the prior art.
The embodiment of the invention provides a file uploading method, which is applied to a distributed storage system, wherein the distributed storage system comprises cloud storage equipment, a node server cluster and a client cluster; the node server cluster comprises a plurality of node servers, and the client cluster comprises a plurality of client devices; the method comprises the following steps:
for any node server in the node server cluster, the node server receives an uploading file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body;
the node server generates meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs;
the node server sends the uploading file and the meta information to the cloud storage device, so that the cloud storage device determines a target storage area according to the meta information, and stores the meta information and the uploading file in the target storage area; and each uploading file in the uploading file set is stored in the target storage area.
Therefore, aiming at the service with large data volume and transmission delay requirement, on one hand, a plurality of client devices in the client cluster can simultaneously send the uploading file set of the same data body to the node server cluster, and a plurality of node servers in the node server cluster provide available bandwidths to receive the uploading file set sent by the client cluster, so that the purpose of rapid file transmission can be realized, and the file transmission rate is improved; on the other hand, in order to ensure convenience in post management of the data of the service, after each node server receives the uploading file sent by the client device, the uploading file of the same data main body can be synchronously stored in the cloud storage device. According to the analysis, the data uploading service meeting the transmission delay requirement can be provided for the same data body, and the requirement of centralized storage can be met.
In one possible implementation manner, the node server sends the upload file and the meta information to the cloud storage device, including:
the node server sends a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information;
after receiving a response message of the synchronization request returned by the cloud storage device, the node server sends the uploading file to the cloud storage device; and the response information is sent after the cloud storage equipment receives the meta information after the meta information is stored and sent.
Therefore, the node server can send the meta-information to the cloud storage device, and the meta-information is smaller than the uploaded file, so that the meta-information can be quickly transmitted to the cloud storage device, and the uploaded file is retransmitted under the condition that the bandwidth is enough, so that the file transmission efficiency is improved.
In one possible implementation manner, after the node server sends the upload file and the meta information to the cloud storage device, the method further includes:
and deleting the uploading file and the meta information by the node server. Therefore, the storage burden of the node server can be reduced, and the problem that the content of the files stored in the cloud storage equipment and the node server is repeated is avoided.
The embodiment of the invention provides a file downloading method, which is applied to a distributed storage system, wherein the distributed storage system comprises cloud storage equipment, a node server cluster and a client cluster; the node server cluster comprises a plurality of node servers, and the client cluster comprises a plurality of client devices; the method comprises the following steps:
for any one of the client devices in the client cluster, the client device sends a downloading request to the cloud storage device, wherein the downloading request comprises a target file identifier;
the client device receives a response message of the downloading request sent by the cloud storage device, and obtains the target file from a target node server according to the position information of the target node server included in the response message;
the location information of the target node server is determined according to the corresponding relation between the file identifier and the location information of the node server after the cloud storage device determines that the target file corresponding to the target file identifier is not stored.
Therefore, when the client device downloads the target file, if the file is not synchronously stored in the cloud storage device, the client device can still download the target file from the corresponding node server, so that the situation that the file is not synchronous or the client device cannot download the target file in the file synchronization process is avoided.
In one possible implementation, the method further includes:
and the client device receives a target file sent by the cloud storage device, wherein the target file is a file stored in the cloud storage device and corresponding to the target file identifier.
Thus, when the client device downloads the target file, if the file is synchronously stored in the cloud storage device, the client device can directly acquire the target file.
The embodiment of the invention provides a file uploading method, which is applied to a distributed storage system, wherein the distributed storage system comprises cloud storage equipment, a node server cluster and a client cluster; the node server cluster comprises a plurality of node servers, and the client cluster comprises a plurality of client devices; the method comprises the following steps:
the cloud storage equipment receives an uploading file sent by any node server in the node server cluster and meta-information of the uploading file; the meta information comprises a data main body to which the uploading file belongs; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body;
The cloud storage equipment determines a target storage area of the uploading file according to the meta information and the corresponding relation between a preset data entity and the storage area; the target storage area is used for storing all uploading files in the uploading file set;
and the cloud storage device stores the uploading file and the meta information to the target storage area.
On the one hand, a plurality of client devices in the client cluster can simultaneously send the uploading files to the node server cluster, so that the purpose of quick file transmission can be realized, and the file transmission rate is improved; on the other hand, after each node server receives the files sent by the client device, the files can be synchronously stored in the cloud storage device.
In one possible implementation manner, the cloud storage device receives an upload file sent by any node server in the node server cluster, and meta information of the upload file, including:
The cloud storage equipment receives a synchronization request sent by the node server, wherein the synchronization request comprises the meta information;
after the cloud storage device determines that available transmission bandwidth exists, returning a response message of the synchronization request to the node server, wherein the response message is used for indicating the node server to send the uploading file to the cloud storage device;
and the cloud storage equipment receives the uploading file sent by the node server.
Therefore, the node server can send the meta-information to the cloud storage device, and the meta-information is smaller than the uploaded file, so that the meta-information can be quickly transmitted to the cloud storage device, and the uploaded file is retransmitted under the condition that the bandwidth is enough, so that the file transmission efficiency is improved.
In one possible implementation, the method further includes:
the cloud storage equipment receives a downloading request sent by any client equipment in the client cluster, wherein the downloading request comprises a target file identifier;
if the cloud storage equipment determines that the target file corresponding to the target file identifier is not stored, determining the position information of the target node server according to the corresponding relation between the file identifier and the position information of the node server; the corresponding relation is determined according to meta information;
The cloud storage device sends a response message of the downloading request to the client, wherein the response message comprises the position information of the target node server, and the response message is used for indicating the client device to acquire the target file from the target node server according to the position information of the target node server.
Therefore, when the client device downloads the target file, if the file is not synchronously stored in the cloud storage device, the client device can still download the target file from the corresponding node server, so that the situation that the file is not synchronous or the client device cannot download the target file in the file synchronization process is avoided.
In one possible implementation, the method further includes:
and if the cloud storage equipment determines that the target file corresponding to the target file identifier is stored, the target file is sent to the client.
Thus, when the client device downloads the target file, if the file is synchronously stored in the cloud storage device, the client device can directly acquire the target file.
The embodiment of the invention provides a server, which comprises:
the receiving and transmitting unit is used for receiving an uploading file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body;
The processing unit is used for generating meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs;
the receiving and transmitting unit is used for transmitting the uploading file and the meta information to the cloud storage device so that the cloud storage device can determine a target storage area according to the meta information and store the meta information and the uploading file into the target storage area; and each uploading file in the uploading file set is stored in the target storage area.
In one possible implementation manner, the transceiver unit is specifically configured to:
sending a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information; after receiving a response message of the synchronization request returned by the cloud storage device, sending the uploading file to the cloud storage device; the response information is sent when the cloud storage device determines that there is available transmission bandwidth.
In a possible implementation, the processing unit is further configured to:
and deleting the uploading file and the meta information.
An embodiment of the present invention provides a client device, including:
The sending unit is used for sending a downloading request to the cloud storage equipment, wherein the downloading request comprises a target file identifier;
the receiving unit is used for receiving a response message of the downloading request sent by the cloud storage equipment and acquiring the target file from the target node server according to the position information of the target node server included in the response message;
the position information of the target node server is determined according to the corresponding relation between the file identification and the position information of the node server after the cloud storage equipment determines that the target file corresponding to the target file identification is not stored; the correspondence is determined from meta information.
In a possible implementation, the receiving unit is further configured to:
and receiving a target file sent by the cloud storage device, wherein the target file is a file stored in the cloud storage device and corresponding to the target file identifier.
An embodiment of the present invention provides a cloud storage device, including:
the receiving and transmitting unit is used for receiving the uploading file sent by any node server in the node server cluster and meta-information of the uploading file; the meta information comprises a data main body to which the uploading file belongs; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body;
The processing unit is used for determining a target storage area of the uploading file according to the meta information and the corresponding relation between the preset data entity and the storage area; the target storage area is used for storing all uploading files in the uploading file set; and storing the upload file and the meta information to the target storage area.
In one possible implementation manner, the transceiver unit is specifically configured to:
receiving a synchronization request sent by the node server, wherein the synchronization request comprises the meta information; after determining that available transmission bandwidth exists, returning a response message of the synchronization request to the node server, wherein the response message is used for indicating the node server to send the uploading file to the cloud storage device; and receiving the uploading file sent by the node server.
In a possible implementation manner, the transceiver unit is further configured to:
receiving a downloading request sent by any client device in the client cluster, wherein the downloading request comprises a target file identifier;
the processing unit is further configured to:
if the target file corresponding to the target file identifier is not stored, determining the position information of the target node server according to the corresponding relation between the file identifier and the position information of the node server; the corresponding relation is determined according to meta information;
The receiving and sending unit is further configured to send a response message of the download request to the client, where the response message includes location information of the target node server, and the response message is used to instruct the client device to obtain the target file from the target node server according to the location information of the target node server.
In a possible implementation manner, the transceiver unit is further configured to:
and if the target file corresponding to the target file identification is determined to be stored, sending the target file to the client.
The embodiment of the application also provides a device which has the function of realizing the file transmission method. The functions may be implemented by hardware executing corresponding software, and in one possible design, the apparatus comprises: a processor, transceiver, memory; the memory is used for storing computer-executable instructions, the transceiver is used for realizing the communication between the device and other communication entities, the processor is connected with the memory through the bus, and when the device runs, the processor executes the computer-executable instructions stored in the memory so as to enable the device to execute the file transmission method described above.
Embodiments of the present invention also provide a computer storage medium having stored therein a software program which, when read and executed by one or more processors, implements the file transfer method described in the various possible implementations described above.
Embodiments of the present invention also provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the file transfer method described in the various possible implementations described above.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that are required to be used in the description of the embodiments will be briefly described below.
FIG. 1 is a schematic diagram of a system architecture to which embodiments of the present invention are applicable;
fig. 2 is a schematic flow chart corresponding to a file transfer method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart corresponding to a method for uploading a file by a client device according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of another system architecture according to an embodiment of the present invention;
fig. 5 is a schematic flow diagram corresponding to a method for synchronizing files by a node server according to an embodiment of the present invention;
FIG. 6 is a flowchart corresponding to another method for file transfer according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of an overall process involved in a second embodiment of the present invention;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a client device according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a cloud storage device according to an embodiment of the present invention.
Detailed Description
The following description of the present application is provided with reference to the accompanying drawings, and the specific operation method in the method embodiment may also be applied to the device embodiment.
Fig. 1 schematically illustrates a system architecture to which an embodiment of the present invention is applied, and as shown in fig. 1, a system architecture 100 to which an embodiment of the present invention is applied includes a cloud storage device 101, a node server cluster 102, and a client cluster 103. Wherein the system 100 may be a distributed storage system; node server cluster 102 may include a plurality of node servers, such as node server 1021, node server 1022, and node server 1023 shown in fig. 1; client cluster 103 may also include a plurality of client devices, such as client device 1031, client device 1032, and client device 1033 shown in fig. 1.
It should be noted that the client device in the present application may be various types of devices, for example, a notebook computer, a smart phone, a tablet computer, a smart television, and the like, which is not limited in particular.
Embodiment one:
based on the system architecture shown in fig. 1, fig. 2 schematically shows a flow diagram corresponding to a file transmission method according to an embodiment of the present invention, which specifically includes the following steps:
step 201, a node server receives an uploading file sent by any client device in a client cluster; the uploading files are files in an uploading file set sent by the client cluster, and all the files in the uploading file set correspond to the same data body.
Step 202, the node server generates meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs.
And 203, the node server sends the uploaded file and the meta information to the cloud storage device.
In step 204, the cloud storage device receives the upload file sent by the node server and meta information of the upload file.
In step 205, the cloud storage device determines a target storage area of the uploaded file according to the meta information and a preset correspondence between the data entity and the storage area.
In step 206, the cloud storage device stores the uploaded file and the meta information in the target storage area.
It should be noted that, the steps 201 to 203 may be performed by any node server in the node server cluster 102 shown in fig. 1, for example, may be performed by the node server 1021 shown in fig. 1; the above steps 204 to 206 may be performed by the cloud storage apparatus 101 shown in fig. 1.
Therefore, aiming at the service with large data volume and transmission delay requirement, on one hand, a plurality of client devices in the client cluster can simultaneously send the uploading file set of the same data body to the node server cluster, and a plurality of node servers in the node server cluster provide available bandwidths to receive the uploading file set sent by the client cluster, so that the purpose of rapid file transmission can be realized, and the file transmission rate is improved; on the other hand, in order to ensure convenience in post management of the data of the service, after each node server receives the uploading file sent by the client device, the uploading file of the same data main body can be synchronously stored in the cloud storage device. According to the analysis, the data uploading service meeting the transmission delay requirement can be provided for the same data body, and the requirement of centralized storage can be met.
Specifically, before step 201 is performed, the communication relationship between the client and the node server includes various types, for example, the node server may receive an upload file sent by any client device in the client cluster, and in one example, the node server may receive an upload file sent by the client device 1031 shown in fig. 1, may receive an upload file sent by the client device 1032, and may also receive an upload file sent by the client device 1033.
In another example, the node server may also receive the upload files transmitted by the client devices designated in the client device 1031, the client device 1032, and the client device 1033 shown in fig. 1. For example, the client device may send the upload file to the designated node server according to its own location information. For example, as shown in fig. 3, a flowchart of a method for determining, by a client device, a node server corresponding to an upload file according to an embodiment of the present invention is provided, where the method may be performed by the client device 1031 shown in fig. 1, and includes the following steps:
in step 301, a client device sends an upload request to a DNS server, the upload request including location information of the client device.
The location information of the client device may refer to an IP address of the client device, or may refer to a geographic location of the client device. As shown in table 1, is one example of location information of a client device. As can be seen from the contents shown in table 1, each client device has a corresponding geographical location, and taking the client device 1 shown in table 1 as an example, the IP address corresponding to the client device 1 is: 222.64.232.189, the corresponding geographic locations are: the location information of other client devices in the Shanghai Mincing area may be referred to in particular by means of a table, which will not be described in detail here.
Table 1: one example of location information for a client device
Changes in client devices IP address Geographic location
Client device 1 222.64.232.189 Shanghai Min Shengzhan
Client device 2 220.155.1.196 Haidian District, Beijing
Client device 3 112.10.39.255 Shou mountain region of Hangzhou city
Client device 4 221.226.140.255 Nanjing's Xuan Wu Ou
Client device 5 218.82.20.255 Shanghai city still district
In step 302, the dns server determines, from the node server cluster, the target node server according to the location information of the client device.
In the embodiment of the invention, the DNS server can be used for providing a corresponding node server for any client device in the client cluster. As shown in fig. 4, another system architecture schematic diagram provided in an embodiment of the present invention, where the system architecture 100 includes a cloud storage device 101, a node server cluster 102, a client cluster 103, and a DNS server 104. The DNS server 104 is connected to the client cluster 103 and the node server cluster 102, so that the DNS server 104 can determine a corresponding node server (such as the node server 1021) from the node server cluster 102 according to the location information of any client device (such as the client device 1031) in the client cluster 103, and further, the client device 1031 can communicate with the node server 1021.
For example, taking the client device 1 shown in table 1 as an example, the location information corresponding to the client device is a Shanghai city Min line area, the DNS server may screen out the node server cluster that both the location information is a Shanghai city Min line area, and use this node server as the node server corresponding to the client device 1.
In step 303, the dns server sends a response message for the upload request to the client device, where the response message includes location information of the target node server.
In step 304, the client device receives a response message of the upload request sent by the DNS server.
In step 305, the client device sends the upload file to the target node server according to the location information of the target node server.
It should be noted that the methods described in steps 301 to 305 are only examples, and in other possible examples, those skilled in the art may determine the target node server according to experience and actual situations, for example, may determine the target node server according to load information of the node servers in the node server cluster, which is not limited in particular.
In step 201, for a client cluster, all files uploaded by the client cluster may be regarded as an uploaded file set, and the files uploaded by each client in the client cluster are files in the uploaded file set, and each file in the uploaded file set corresponds to the same data body.
The data body may refer to a type corresponding to each file, such as a company type, an industry type, etc., and may be determined by a person skilled in the art according to actual situations. For example, if the uploading file 1 is a file of company a, the data entity corresponding to the uploading file 1 may be company a; the uploading file 2 is a file in the B domain, and the data entity corresponding to the uploading file 2 may be the B domain.
In step 202, the meta information is generated according to the upload file, and the meta information may include a data body to which the upload file belongs, or may include an upload file identifier, or may include location information of the node server, which is not specifically limited.
In the implementation process, the node server can directly take the data main body to which the uploading file belongs, the uploading file identifier and the position information of the node server as meta information; alternatively, the node server may encrypt the data body to which the uploaded file belongs, the uploaded file identifier, and the location information of the node server, and use the encrypted information as meta information, which is not specifically limited.
In step 203, the node server may directly send the uploaded file and the meta information to the cloud storage device together; or the node server can send the meta information to the cloud storage device first and then send the uploading file to the cloud storage device; the node server may also send the uploaded file to the cloud storage device within a set time after receiving the uploaded file. Specifically, as shown in fig. 5, a flow chart corresponding to a method for synchronizing files by a node server according to an embodiment of the present invention includes the following steps:
In step 501, a node server sends a synchronization request to a cloud storage device, the synchronization request including meta-information.
In step 502, the cloud storage device receives a synchronization request sent by a node server.
In step 503, after determining that there is available transmission bandwidth, the cloud storage device returns a response message of the synchronization request to the node server.
Before the cloud storage device returns the response message of the synchronization request to the node server, the cloud storage device can also judge whether available transmission bandwidth exists, and return the response message to the node server under the condition that the available transmission bandwidth exists, so that the rate of the node server sending the uploaded file to the cloud storage device can be improved.
And step 504, after receiving the response message of the synchronization request, the node server sends an uploading file to the cloud storage device.
Therefore, the node server can send the meta-information to the cloud storage device, and the meta-information is smaller than the uploaded file, so that the meta-information can be quickly transmitted to the cloud storage device, and the uploaded file is retransmitted under the condition that the bandwidth is enough, so that the file transmission efficiency is improved.
After executing step 204, the node server may also delete the uploaded file and meta information, so that the storage burden of the node server can be reduced, and the problem of duplication of file contents stored in the cloud storage device and the node server is avoided.
Embodiment two:
based on the system architecture shown in fig. 1, fig. 6 illustrates a flow diagram corresponding to another file transmission method according to an embodiment of the present invention, which specifically includes the following steps:
in step 601, the client device sends a download request to the cloud storage device, where the download request includes a target file identifier.
In step 602, the cloud storage device receives a download request sent by the client device.
In step 603, if the cloud storage device determines that the target file corresponding to the target file identifier is not stored, determining the location information of the target node server according to the correspondence between the file identifier and the location information of the node server.
In step 604, the cloud storage device sends a response message of the download request to the client, where the response message includes location information of the target node server.
Step 605, the client device receives a response message of the download request sent by the cloud storage device, and obtains the target file from the target node server according to the location information of the target node server included in the response message.
It should be noted that, the above-mentioned step 601 and step 605 may be performed by any client device in the client cluster 103 shown in fig. 1, for example, may be performed by the client device 1031 shown in fig. 1; the above steps 602 to 604 may be performed by the cloud storage apparatus 101 shown in fig. 1.
Therefore, when the client device downloads the target file, if the file is not synchronously stored in the cloud storage device, the client device can still download the target file from the corresponding node server, so that the situation that the file is not synchronous or the client device cannot download the target file in the file synchronization process is avoided.
Specifically, in step 603 and step 604, if the cloud storage device determines that the target file corresponding to the target file identifier is stored, the target file may be directly sent to the client, so that when the client device downloads the target file, if the file is already stored in the cloud storage device synchronously, the client device may directly obtain the target file.
In other possible embodiments, any information related to the target file identifier may not be stored in the cloud storage device, in other words, there is no target file corresponding to the target file identifier in the cloud storage device, and no node server corresponding to the target file identifier, so that information that the file does not exist may be returned to the client device.
In the specific implementation process, the client can be set to be directly connected with the cloud storage device when the downloading function is started; when the cloud storage device determines that the target file is not stored, the management server can also determine the position information of the target node server corresponding to the target file.
In order to more clearly describe the file transfer method, the flow involved in the second embodiment of the present invention will be described in detail with reference to fig. 7. As shown in fig. 7, the following steps may be included:
in step 701, a client device sends a download request to a cloud storage device, where the download request includes a target file identifier.
In step 702, the cloud storage device receives a download request sent by the client device.
Step 703, the cloud storage device determines whether a target file corresponding to the target file identifier is stored according to the target file identifier, and if so, executes step 704; if not, step 706 is performed.
In step 704, the cloud storage device sends the target file to the client.
In step 705, the client device receives the target file sent by the cloud storage device.
Step 706, the cloud storage device determines whether there is a target node server corresponding to the target file identifier according to the correspondence between the file identifier and the location information of the node server, and if so, executes step 707; if not, step 710 is performed.
In step 707, the cloud storage determines location information of the target node server.
In step 708, the cloud storage device sends a response message of the download request to the client, where the response message includes location information of the target node server.
In step 709, the client device receives a response message of the download request sent by the cloud storage device, and obtains the target file from the target node server according to the location information of the target node server included in the response message.
In step 710, the cloud storage device returns information that the file does not exist to the client device.
It should be noted that the above step numbers are only exemplary representations of one execution flow, and the sequence of each step is not specifically limited in this application. For example, in the above steps 703 and 706, the cloud storage device may determine whether there is a target node server corresponding to the target file identifier according to the correspondence between the file identifier and the location information of the node server, and then determine whether there is a target file corresponding to the target file identifier according to the target file identifier, which is not particularly limited.
Embodiment III:
based on the same inventive concept, fig. 8 schematically illustrates a structure of a server according to an embodiment of the present invention, and as shown in fig. 8, the server 800 includes a transceiver unit 801 and a processing unit 802.
A transceiver unit 801, configured to receive an upload file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body;
A processing unit 802, configured to generate meta information of the upload file, where the meta information includes a data body to which the upload file belongs;
the transceiver 801 is configured to send the upload file and the meta information to the cloud storage device, so that the cloud storage device determines a target storage area according to the meta information, and stores the meta information and the upload file in the target storage area; and each uploading file in the uploading file set is stored in the target storage area.
In one possible implementation manner, the transceiver unit 801 is specifically configured to:
sending a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information; after receiving a response message of the synchronization request returned by the cloud storage device, sending the uploading file to the cloud storage device; the response information is sent when the cloud storage device determines that there is available transmission bandwidth.
In one possible implementation, the processing unit 802 is further configured to:
and deleting the uploading file and the meta information.
Embodiment four:
based on the same inventive concept, fig. 9 schematically illustrates a structure of a client device according to an embodiment of the present invention, and as shown in fig. 9, the client device 900 includes a transmitting unit 901 and a receiving unit 902.
A sending unit 901, configured to send a download request to the cloud storage device, where the download request includes a target file identifier;
a receiving unit 902, configured to receive a response message of the download request sent by the cloud storage device, and obtain, according to location information of a target node server included in the response message, the target file from the target node server;
the position information of the target node server is determined according to the corresponding relation between the file identification and the position information of the node server after the cloud storage equipment determines that the target file corresponding to the target file identification is not stored; the correspondence is determined from meta information.
In a possible implementation manner, the receiving unit 902 is further configured to:
and receiving a target file sent by the cloud storage device, wherein the target file is a file stored in the cloud storage device and corresponding to the target file identifier.
Fifth embodiment:
based on the same inventive concept, fig. 10 schematically illustrates a schematic structural diagram of a cloud storage device according to an embodiment of the present invention, and as shown in fig. 10, the cloud storage device 1000 includes a transceiver unit 1001 and a processing unit 1002.
A transceiver unit 1001, configured to receive an upload file sent by any node server in the node server cluster and meta information of the upload file; the meta information comprises a data main body to which the uploading file belongs; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body;
a processing unit 1002, configured to determine a target storage area of the uploaded file according to the meta information and a preset correspondence between a data entity and the storage area; the target storage area is used for storing all uploading files in the uploading file set; and storing the upload file and the meta information to the target storage area.
In one possible implementation manner, the transceiver unit 1001 is specifically configured to:
receiving a synchronization request sent by the node server, wherein the synchronization request comprises the meta information; after determining that available transmission bandwidth exists, returning a response message of the synchronization request to the node server, wherein the response message is used for indicating the node server to send the uploading file to the cloud storage device; and receiving the uploading file sent by the node server.
In one possible implementation, the transceiver unit 1001 is further configured to:
receiving a downloading request sent by any client device in the client cluster, wherein the downloading request comprises a target file identifier;
the processing unit 1002 is further configured to:
if the target file corresponding to the target file identifier is not stored, determining the position information of the target node server according to the corresponding relation between the file identifier and the position information of the node server; the corresponding relation is determined according to meta information;
the transceiver 1001 is further configured to send a response message of the download request to the client, where the response message includes location information of the target node server, and the response message is used to instruct the client device to obtain the target file from the target node server according to the location information of the target node server.
In one possible implementation, the transceiver unit 1001 is further configured to:
and if the target file corresponding to the target file identification is determined to be stored, sending the target file to the client.
The embodiment of the application also provides a device which has the function of realizing the file transmission method. The functions may be implemented by hardware executing corresponding software, and in one possible design, the apparatus comprises: a processor, transceiver, memory; the memory is used for storing computer-executable instructions, the transceiver is used for realizing the communication between the device and other communication entities, the processor is connected with the memory through the bus, and when the device runs, the processor executes the computer-executable instructions stored in the memory so as to enable the device to execute the file transmission method described above.
Embodiments of the present invention also provide a computer storage medium having stored therein a software program which, when read and executed by one or more processors, implements the file transfer method described in the various possible implementations described above.
Embodiments of the present invention also provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the file transfer method described in the various possible implementations described above.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Based on the above description, the node server cluster included in the system applicable to the embodiment of the present invention has a plurality of node servers, so that a plurality of client devices in the client cluster can simultaneously send the uploading file set of the same data body to the node server cluster, and a plurality of node servers in the node server cluster can provide available bandwidth to receive the uploading file set sent by the client cluster, thereby achieving the purpose of rapid file transmission and improving the file transmission rate; further, after receiving the file sent by the client device, any node server can synchronously store the file to the same storage position in the cloud storage device, so that a user can directly manage the file through the cloud storage device, and the user can conveniently and intensively manage the file. Therefore, by adopting the method for providing the data, the uploading service which can meet the transmission delay requirement can be provided for the large-capacity data, and the large-capacity data can be stored in a centralized way, so that the requirement of centralized management on the large-capacity data is met. The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (16)

1. A method for file transfer, wherein the method is applied to a distributed storage system, and the distributed storage system comprises cloud storage equipment, a node server cluster and a client cluster; the node server cluster comprises a plurality of node servers, and the client cluster comprises a plurality of client devices; the method comprises the following steps:
for any node server in the node server cluster, the node server receives an uploading file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body; the data body is of a type corresponding to a file;
the node server generates meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs;
The node server sends a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information; after receiving a response message of the synchronization request returned by the cloud storage device, the node server sends the uploading file to the cloud storage device; the response message is sent when the cloud storage device determines that available transmission bandwidth exists, so that the cloud storage device determines a target storage area according to the meta-information and the corresponding relation between a preset data main body and the storage area, and stores the meta-information and the uploading file into the target storage area; and each uploading file in the uploading file set is stored in the target storage area.
2. The method of claim 1, wherein after the node server sends the upload file and the meta information to the cloud storage device, the method further comprises:
and deleting the uploading file and the meta information by the node server.
3. A method for file transfer, wherein the method is applied to a distributed storage system, and the distributed storage system comprises cloud storage equipment, a node server cluster and a client cluster; the node server cluster comprises a plurality of node servers, and the client cluster comprises a plurality of client devices; the method comprises the following steps:
For any node server in the node server cluster, the node server receives an uploading file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body; the data body is of a type corresponding to a file;
the node server generates meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs;
the node server sends a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information; after receiving a response message of the synchronization request returned by the cloud storage device, the node server sends the uploading file to the cloud storage device; the response message is sent when the cloud storage device determines that available transmission bandwidth exists, so that the cloud storage device determines a target storage area according to the meta-information and the corresponding relation between a preset data main body and the storage area, and stores the meta-information and the uploading file into the target storage area; each uploading file in the uploading file set is stored in the target storage area;
For any one of the client devices in the client cluster, the client device sends a downloading request to the cloud storage device, wherein the downloading request comprises a target file identifier;
the client device receives a response message of the downloading request sent by the cloud storage device, and obtains the target file from a target node server according to the position information of the target node server included in the response message;
the position information of the target node server is determined according to the corresponding relation between the file identification and the position information of the node server after the cloud storage equipment determines that the target file corresponding to the target file identification is not stored; the correspondence is determined from the meta information.
4. A method according to claim 3, characterized in that the method further comprises:
and the client device receives a target file sent by the cloud storage device, wherein the target file is a file stored in the cloud storage device and corresponding to the target file identifier.
5. A method for file transfer, wherein the method is applied to a distributed storage system, and the distributed storage system comprises cloud storage equipment, a node server cluster and a client cluster; the node server cluster comprises a plurality of node servers, and the client cluster comprises a plurality of client devices; the method comprises the following steps:
The cloud storage equipment receives a synchronization request sent by the node server, wherein the synchronization request comprises meta information; after the cloud storage equipment determines that available transmission bandwidth exists, a response message of the synchronization request is returned to the node server, wherein the response message is used for indicating the node server to send an uploading file to the cloud storage equipment; the cloud storage equipment receives the uploading file sent by the node server; the meta information comprises a data main body to which the uploading file belongs; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body; the data body is of a type corresponding to a file;
the cloud storage equipment determines a target storage area of the uploading file according to the meta information and the corresponding relation between a preset data entity and the storage area; the target storage area is used for storing all uploading files in the uploading file set;
and the cloud storage device stores the uploading file and the meta information to the target storage area.
6. The method of claim 5, wherein the method further comprises:
The cloud storage equipment receives a downloading request sent by any client equipment in the client cluster, wherein the downloading request comprises a target file identifier;
if the cloud storage equipment determines that the target file corresponding to the target file identifier is not stored, determining the position information of the target node server according to the corresponding relation between the file identifier and the position information of the node server; the corresponding relation is determined according to the meta information;
the cloud storage device sends a response message of the downloading request to the client, wherein the response message comprises the position information of the target node server, and the response message is used for indicating the client device to acquire the target file from the target node server according to the position information of the target node server.
7. The method of claim 6, wherein the method further comprises:
and if the cloud storage equipment determines that the target file corresponding to the target file identifier is stored, the target file is sent to the client.
8. A server, the server comprising:
the receiving and transmitting unit is used for receiving an uploading file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body; the data body is of a type corresponding to a file;
The processing unit is used for generating meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs;
the receiving and transmitting unit is used for sending a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information; after receiving a response message of the synchronization request returned by the cloud storage device, sending the uploading file to the cloud storage device; the response message is sent when the cloud storage device determines that available transmission bandwidth exists, so that the cloud storage device determines a target storage area according to the meta-information and the corresponding relation between a preset data entity and the storage area, and stores the meta-information and the uploading file into the target storage area; and each uploading file in the uploading file set is stored in the target storage area.
9. The server of claim 8, wherein the processing unit is further configured to:
and deleting the uploading file and the meta information.
10. A client device, the client device comprising:
the receiving and transmitting unit is used for receiving an uploading file sent by any client device in the client cluster; the uploading files are files in an uploading file set sent by the client cluster, and each file in the uploading file set corresponds to the same data body; the data body is of a type corresponding to a file;
The processing unit is used for generating meta information of the uploading file, wherein the meta information comprises a data main body to which the uploading file belongs;
the receiving and transmitting unit is used for sending a synchronization request to the cloud storage device, wherein the synchronization request comprises the meta information; after receiving a response message of the synchronization request returned by the cloud storage device, sending the uploading file to the cloud storage device; the response message is sent when the cloud storage device determines that available transmission bandwidth exists, so that the cloud storage device determines a target storage area according to the meta-information and the corresponding relation between a preset data main body and the storage area, and stores the meta-information and the uploading file into the target storage area; each uploading file in the uploading file set is stored in the target storage area;
the sending unit is used for sending a downloading request to the cloud storage equipment, wherein the downloading request comprises a target file identifier;
the receiving unit is used for receiving a response message of the downloading request sent by the cloud storage equipment and acquiring the target file from the target node server according to the position information of the target node server included in the response message;
The position information of the target node server is determined according to the corresponding relation between the file identification and the position information of the node server after the cloud storage equipment determines that the target file corresponding to the target file identification is not stored; the correspondence is determined from the meta information.
11. The client device of claim 10, wherein the receiving unit is further configured to:
and receiving a target file sent by the cloud storage device, wherein the target file is a file stored in the cloud storage device and corresponding to the target file identifier.
12. A cloud storage device, the cloud storage device comprising:
the receiving and transmitting unit is used for receiving a synchronization request sent by the node server, wherein the synchronization request comprises meta information; after determining that available transmission bandwidth exists, returning a response message of the synchronization request to the node server, wherein the response message is used for indicating the node server to send an uploading file to the cloud storage device; receiving the uploading file sent by the node server; the meta information comprises a data main body to which the uploading file belongs; the uploading files are files in an uploading file set sent by a client cluster, and each file in the uploading file set corresponds to the same data body; the data body is of a type corresponding to a file;
The processing unit is used for determining a target storage area of the uploading file according to the meta information and the corresponding relation between the preset data entity and the storage area; the target storage area is used for storing all uploading files in the uploading file set; and storing the upload file and the meta information to the target storage area.
13. The cloud storage device of claim 12, wherein the transceiver unit is further configured to:
receiving a downloading request sent by any client device in the client cluster, wherein the downloading request comprises a target file identifier;
the processing unit is further configured to:
if the target file corresponding to the target file identifier is not stored, determining the position information of the target node server according to the corresponding relation between the file identifier and the position information of the node server; the corresponding relation is determined according to the meta information;
the receiving and sending unit is further configured to send a response message of the download request to the client, where the response message includes location information of the target node server, and the response message is used to instruct the client device to obtain the target file from the target node server according to the location information of the target node server.
14. The cloud storage device of claim 13, wherein the transceiver unit is further configured to:
and if the target file corresponding to the target file identification is determined to be stored, sending the target file to the client.
15. A computer readable storage medium storing instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 2, or the method of claim 3 or 4, or the method of any one of claims 5 to 7.
16. A computer device, comprising:
a memory for storing program instructions;
a processor for invoking program instructions stored in the memory to perform the method according to any of claims 1-2, or the method according to claim 3 or 4, or the method according to any of claims 5-7, in accordance with the obtained program.
CN201810745872.9A 2018-07-09 2018-07-09 File transmission method and device Active CN110703980B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810745872.9A CN110703980B (en) 2018-07-09 2018-07-09 File transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810745872.9A CN110703980B (en) 2018-07-09 2018-07-09 File transmission method and device

Publications (2)

Publication Number Publication Date
CN110703980A CN110703980A (en) 2020-01-17
CN110703980B true CN110703980B (en) 2024-03-22

Family

ID=69192909

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810745872.9A Active CN110703980B (en) 2018-07-09 2018-07-09 File transmission method and device

Country Status (1)

Country Link
CN (1) CN110703980B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111291009B (en) * 2020-03-25 2023-05-09 上海飞旗网络技术股份有限公司 File block storage method and device
CN111478951B (en) * 2020-03-26 2023-08-08 深圳市鸿合创新信息技术有限责任公司 File issuing method and device
CN111723062A (en) * 2020-06-28 2020-09-29 天津联想协同科技有限公司 File synchronization method, device and storage medium
CN112328174A (en) * 2020-10-29 2021-02-05 北京京东尚科信息技术有限公司 Data pushing method, device, system and medium for cloud computing platform
CN112328560A (en) * 2020-11-25 2021-02-05 北京无线电测量研究所 File scheduling method and system
CN112671918B (en) * 2020-12-29 2024-03-05 平安普惠企业管理有限公司 Binary system-based distributed data downloading method, device, equipment and medium
CN114124981B (en) * 2021-11-19 2024-04-12 天翼视联科技有限公司 Cloud storage data direct transmission management method, cloud transmission management platform and system
CN114374683A (en) * 2021-12-20 2022-04-19 上海金仕达软件科技有限公司 Archive file management method and system and computer readable storage medium
CN114338694B (en) * 2022-03-04 2022-05-31 广州鹏捷科技股份有限公司 One-stop cloud data center server scheduling method and system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102420854A (en) * 2011-11-14 2012-04-18 西安电子科技大学 Distributed file system facing to cloud storage
CN105025106A (en) * 2015-07-28 2015-11-04 焦点科技股份有限公司 Breakpoint resuming method based on segmentation and meta-information
CN105812391A (en) * 2016-05-16 2016-07-27 广州鼎鼎信息科技有限公司 Safe cloud storage system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102420854A (en) * 2011-11-14 2012-04-18 西安电子科技大学 Distributed file system facing to cloud storage
CN105025106A (en) * 2015-07-28 2015-11-04 焦点科技股份有限公司 Breakpoint resuming method based on segmentation and meta-information
CN105812391A (en) * 2016-05-16 2016-07-27 广州鼎鼎信息科技有限公司 Safe cloud storage system

Also Published As

Publication number Publication date
CN110703980A (en) 2020-01-17

Similar Documents

Publication Publication Date Title
CN110703980B (en) File transmission method and device
CN109522330B (en) Cloud platform data processing method, device, equipment and medium based on block chain
EP2721504B1 (en) File processing method, system and server-clustered system for cloud storage
TWI431978B (en) Methods, devices and systems for obtaining resources
CN108023953B (en) High-availability implementation method and device for FTP service
KR20130088774A (en) System and method for delivering segmented content
US9900167B2 (en) Document sharing method, system, and device
CN111447248A (en) File transmission method and device
CN109376172B (en) Data acquisition method and system based on block chain
CN111124589B (en) Service discovery system, method, device and equipment
CN110430274A (en) A kind of document down loading method and system based on cloud storage
CN110324406B (en) Method for acquiring business data and cloud service system
CN109150936A (en) The sharing method and device of session object Session in a kind of distributed type assemblies
CN109325056A (en) A kind of big data processing method and processing device, communication equipment
CN107580021A (en) A kind of method and apparatus of file transmission
CN109873855A (en) A kind of resource acquiring method and system based on block chain network
CN114390044A (en) File uploading method, system, device and storage medium
CN110798495A (en) Method and server for end-to-end message push in cluster architecture mode
CN109618187B (en) Video data acquisition method and device
CN115277816B (en) Service adaptation method, device, system and computer readable medium
CN110798358B (en) Distributed service identification method and device, computer readable medium and electronic equipment
WO2017096886A1 (en) Content pushing method, apparatus and system
CN108023920B (en) Data packet transmission method, equipment and application interface
CN109347766A (en) A kind of method and device of scheduling of resource
US10798147B2 (en) Constraint based controlled seeding

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
GR01 Patent grant
GR01 Patent grant