CN103547339B - File uploading method, client side and server side - Google Patents

Abstract

Embodiments of the present invention provide a file upload method, a client and a server, which relate to the Internet field, can simplify file upload methods, and enhance processing capabilities before and after uploading, and the application server does not need to purchase and maintain storage devices. The method is as follows: the uploading server receives the request message sent by the client, the request message includes the request header field, judges whether the receiving condition of the file is satisfied according to the request header field in the request message, if the receiving condition of the file is satisfied, then receives the file, and Send a notification message to the application server according to the callback address, wherein the callback address is carried in the request header field of the request message sent by the client, or the callback address is obtained from the application server. The embodiment of the present invention is used for uploading files.

Description

A file upload method, client and server

technical field

The invention relates to the Internet field, in particular to a file uploading method, a client and a server.

Background technique

With the rapid development of the Internet, more and more websites provide upload tools to encourage users to upload files. However, due to the limitations of the performance, bandwidth, security, etc. of the website upload server, the efficiency of user upload files has been seriously affected. In the prior art, there are mainly two methods for improving the upload experience: one is CDN (Content Delivery Network, CDN) upload acceleration function, one is to use cloud storage.

Specifically, the CDN mainly provides upload acceleration and download acceleration functions. Among them, the upload acceleration method is: the user uploads the file to the CDN node, and the CDN node transmits the file to the website. In this way, the user needs to upload the file twice before uploading the file to the website. Cloud storage is a collection of a large number of different types of storage devices in the network to work together through application software to jointly provide data storage and business access services. When using the cloud storage method, users can upload files to the website, and the website uploads the files to the cloud storage.

Therefore, in the above two methods, the user's files need to be uploaded twice, and in the CDN upload acceleration method, it is also necessary to purchase and maintain storage facilities. In addition, in the cloud storage method, after the file is uploaded, the browser may need to interact with the web server again. If it is applied in the CDN system, the application logic needs to be greatly modified, and Amazon S3 ( Amazon Simple Storage Service, Amazon Simple Storage Service) is a centralized service, which brings inconvenience to users to upload files.

Contents of the invention

Embodiments of the present invention provide a file uploading method, a client and a server, which can simplify file upload methods and enhance processing capabilities before and after uploading, and the application server does not need to purchase and maintain storage devices.

In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:

In the first aspect, a file upload method is provided, including:

receiving a request message sent by the client, where the request message includes a request header field;

judging whether the receiving condition of the file is satisfied according to the request header field in the request message;

If the receiving condition of the file is satisfied, the file is received, and a notification message is sent to the application server according to the callback address.

With reference to the first aspect, in a first possible implementation manner, the callback address includes a pre-upload callback address and a post-upload callback address.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the request header field further includes an application identifier, and the application identifier is used to identify the application server.

With reference to the second possible implementation manner of the first aspect, in the third possible implementation manner, the callback address is carried in the request header field of the request message sent by the client, or the callback address obtained from the application server.

In combination with the third possible implementation manner of the first aspect, in the fourth possible implementation manner, when the callback address is obtained from the application server, it further includes:

receiving a registration message sent by the application server, where the registration message includes the callback address;

Save the callback address in a database.

With reference to the fourth possible implementation manner of the first aspect, in the fifth possible implementation manner, when the callback address is obtained from the application server, if the receiving condition of the file is met, Then receiving the file, and sending a notification message to the application server according to the callback address includes:

If the receiving condition of the file is satisfied, obtain the pre-upload callback address from the database according to the application identifier, and call the pre-upload callback address to send a first notification message to the application server, the first The notification message includes first file information of the file;

Send an upload response message to the client, where the upload response message includes the request header field, so that the client can continue to upload the file;

receiving and storing the file sent by the client according to the upload response message, then obtaining the post-upload callback address from the database according to the application identifier, and calling the post-upload callback address to the application The server sends a second notification message, where the second notification message includes second file information of the file.

With reference to the third possible implementation manner of the first aspect, in a sixth possible implementation manner, when the callback address is carried in the request header field of the request message sent by the client, the if If the receiving condition of the file is met, the file is received, and sending a notification message to the application server according to the callback address includes:

If the receiving condition of the file is satisfied, obtain the pre-upload callback address from the request header field, and call the pre-upload callback address to send a first notification message to the application server, the first notification the message includes first file information of the file;

Send an upload response message to the client, where the upload response message includes the request header field, so that the client can continue to upload the file;

receiving and storing the file sent by the client according to the upload response message, then obtaining the post-upload callback address from the request header field, and calling the post-upload callback address to send the file to the application server A second notification message, where the second notification message includes second file information of the file.

In combination with the first aspect or the first possible implementation manner to the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner, the method further includes:

After receiving the file, send a completion response message to the client.

In the second aspect, a file upload method is provided, including:

Send a registration message to the upload server, the registration message includes a callback address when the file is uploaded;

After the registration is completed, receive the file upload notification message sent by the upload server according to the callback address, so as to obtain the file information of the file.

With reference to the second aspect, in a first possible implementation manner, the callback address includes a pre-upload callback address and a post-upload callback address.

With reference to the first possible implementation manner of the second aspect, in the second possible implementation manner, the receiving the file upload notification message sent by the upload server according to the callback address to obtain the File information includes:

receiving a first notification message sent by the upload server according to the pre-upload callback address, the first notification message including first file information of the file;

When the upload server finishes receiving the file, receive a second notification message sent by the upload server according to the post-upload callback address, the second notification message includes second file information of the file.

In the third aspect, a file upload method is provided, including:

Send a request message to the upload server, where the request message includes a request header field;

receiving an upload response message sent by the upload server, where the upload response message includes the request header field;

Upload the file to the upload server according to the upload response message.

With reference to the third aspect, in a first possible implementation manner, the request header field includes an application identifier, or the request header field includes a callback address and the application identifier.

In combination with the first possible implementation manner of the third aspect, in the second possible implementation manner, the method further includes:

After the upload server successfully calls back to the application server through the callback address, it receives a completion response message sent by the upload server.

In the fourth aspect, an upload server is provided, including:

A receiving unit, configured to receive a request message sent by the client, where the request message includes a request header field;

A judging unit, configured to judge whether the receiving condition of the file is satisfied according to the request header field in the request message;

The processing unit is configured to receive the file if the receiving condition of the file is satisfied, and send a notification message to the application server according to the callback address.

With reference to the fourth aspect, in a first possible implementation manner, the callback address includes a pre-upload callback address and a post-upload callback address.

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the request header field further includes an application identifier, and the application identifier is used to identify the application server.

With reference to the second possible implementation manner of the fourth aspect, in the third possible implementation manner, the callback address is carried in the request header field of the request message sent by the client, or the callback address obtained from the application server.

With reference to the third possible implementation manner of the fourth aspect, in the fourth possible implementation manner, when the callback address is obtained from the application server, it further includes:

A first receiving unit, configured to receive a registration message sent by the application server, where the registration message includes the callback address;

A storage unit, configured to store the callback address in a database.

With reference to the fourth possible implementation manner of the fourth aspect, in a fifth possible implementation manner, when the callback address is obtained from the application server, the processing unit includes:

The first processing subunit is configured to obtain the pre-upload callback address from the database according to the application identifier if the file receiving condition is met, and call the pre-upload callback address to send the first file to the application server. a notification message, the first notification message includes first file information of the file;

A first sending subunit, configured to send an upload response message to the client, where the upload response message includes the request header field, so that the client can continue to upload the file;

The second processing subunit is configured to receive and store the file sent by the client according to the upload response message, and then obtain the post-upload callback address from the database according to the application identifier, and call the The post-upload callback address sends a second notification message to the application server, where the second notification message includes second file information of the file.

With reference to the fourth aspect or the third possible implementation manner of the fourth aspect, in the sixth possible implementation manner, when the callback address is carried in the request header field of the request message sent by the client , the processing unit includes:

The third processing subunit is configured to obtain the pre-upload callback address from the request header field if the receiving condition of the file is met, and call the pre-upload callback address to send the first a notification message, the first notification message includes first file information of the file;

a second sending subunit, configured to send an upload response message to the client, where the upload response message includes the request header field, so that the client can continue to upload the file;

The fourth processing subunit is configured to receive and store the file sent by the client according to the upload response message, then obtain the post-upload callback address from the request header field, and call the post-upload callback The address sends a second notification message to the application server, where the second notification message includes second file information of the file.

In combination with the fourth aspect or the first possible implementation manner of the fourth aspect to the sixth possible implementation manner, the seventh possible implementation manner further includes:

A response unit, configured to send a completion response message to the client after receiving the file.

In the fifth aspect, an application server is provided, including:

The second sending unit is configured to send a registration message to the upload server, where the registration message includes a callback address when the file is uploaded;

The second receiving unit is configured to receive the file upload notification message sent by the upload server according to the callback address after the registration is completed, so as to obtain the file information of the file.

With reference to the fifth aspect, in a first possible implementation manner, the callback address includes a pre-upload callback address and a post-upload callback address.

With reference to the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the second receiving unit is configured to:

receiving a first notification message sent by the upload server according to the pre-upload callback address, the first notification message including first file information of the file;

When the upload server finishes receiving the file, receive a second notification message sent by the upload server according to the post-upload callback address, the second notification message includes second file information of the file.

In the sixth aspect, a client is provided, including:

A third sending unit, configured to send a request message to the upload server, where the request message includes a request header field;

A third receiving unit, configured to receive an upload response message sent by the upload server, where the upload response message includes the request header field;

A file uploading unit, configured to upload a file to the upload server according to the upload response message.

With reference to the sixth aspect, in a first possible implementation manner, the request header field includes an application identifier, or the request header field includes a callback address and the application identifier.

In combination with the first possible implementation manner of the sixth aspect, the second possible implementation manner further includes:

After the upload server successfully calls back to the application server through the callback address, it receives a completion response message sent by the upload server.

In the seventh aspect, an upload server is provided, including:

The first receiver is configured to receive a request message sent by the client, where the request message includes a request header field;

The first processor is configured to judge whether the receiving condition of the file is satisfied according to the request header field in the request message;

The first receiver is further configured to receive the file if the receiving condition of the file is met, and the first transmitter sends a notification message to the application server according to the callback address.

With reference to the seventh aspect, in a first possible implementation manner, the callback address includes a pre-upload callback address and a post-upload callback address.

With reference to the first possible implementation manner of the seventh aspect, in a second possible implementation manner, the request header field further includes an application identifier, and the application identifier is used to identify the application server.

With reference to the second possible implementation manner of the seventh aspect, in the third possible implementation manner, the callback address is carried in the request header field of the request message sent by the client, or the callback address obtained from the application server.

With reference to the third possible implementation manner of the seventh aspect, in the fourth possible implementation manner, when the callback address is obtained from the application server, it further includes:

The first receiver is further configured to receive a registration message sent by the application server, where the registration message includes the callback address;

The first memory is used to store the callback address in a database.

With reference to the fourth possible implementation manner of the seventh aspect, in the fifth possible implementation manner, when the callback address is obtained from the application server, the first receiver, the first The processor, the first memory, and the first transmitter are further configured to:

If the receiving condition of the file is satisfied, the first processor obtains the pre-upload callback address from the database according to the application identifier, and the first transmitter invokes the pre-upload callback address to provide the application service The terminal sends a first notification message, where the first notification message includes first file information of the file;

The first transmitter is further configured to send an upload response message to the client, where the upload response message includes the request header field, so that the client can continue to upload the file;

The first receiver is further configured to receive the file sent by the client according to the upload response message, the first memory is further configured to store the file, and the first processor transmits the file according to the application Obtaining the post-upload callback address from the database, the first transmitter invokes the post-upload callback address to send a second notification message to the application server, the second notification message includes the Second file information.

With reference to the third possible implementation manner of the seventh aspect, in the sixth possible implementation manner, when the callback address is carried in the request header field of the request message sent by the client, the sixth a receiver, said first processor, said first memory, and first transmitter for:

If the file receiving condition is met, the first processor obtains the pre-upload callback address from the request header field, and the first transmitter invokes the pre-upload callback address to send to the application server a first notification message, where the first notification message includes first file information of the file;

The first transmitter sends an upload response message to the client, where the upload response message includes the request header field, so that the client can continue to upload the file;

The first receiver is further configured to receive the file sent by the client according to the upload response message, the first memory is further configured to store the file, and the first processor receives the file from the request Obtain the post-upload callback address in the header field, and the first transmitter invokes the post-upload callback address to send a second notification message to the application server, the second notification message includes the second file of the file information.

Combining the seventh aspect or the first possible implementation manner to the sixth possible implementation manner of the seventh aspect, the seventh possible implementation manner further includes:

After receiving the file, the first transmitter is further configured to send a completion response message to the client.

In the eighth aspect, an application server is provided, including:

The second transmitter is used to send a registration message to the upload server, and the registration message includes a callback address when the file is uploaded;

The second receiver is configured to receive the file upload notification message sent by the upload server according to the callback address after the registration is completed, so as to obtain the file information of the file.

With reference to the eighth aspect, in a first possible implementation manner, the callback address includes a pre-upload callback address and a post-upload callback address.

With reference to the first possible implementation manner of the eighth aspect, in a second possible implementation manner, the second receiver is configured to:

receiving a first notification message sent by the upload server according to the pre-upload callback address, the first notification message including first file information of the file;

When the upload server finishes receiving the file, receive a second notification message sent by the upload server according to the post-upload callback address, the second notification message includes second file information of the file.

In the ninth aspect, a client is provided, including:

A third transmitter, configured to send a request message to the upload server, where the request message includes a request header field;

A third receiver, configured to receive an upload response message sent by the upload server, where the upload response message includes the request header field;

The third processor is configured to upload the file to the upload server according to the upload response message.

With reference to the ninth aspect, in a first possible implementation manner, the request header field includes an application identifier, or the request header field includes a callback address and the application identifier.

With reference to the first possible implementation manner of the ninth aspect, in the second possible implementation manner, after the upload server successfully calls back to the application server through the callback address, the third receiver also uses and receiving the completion response message sent by the upload server.

In a tenth aspect, a communication system is provided, including:

The upload server provided in the seventh aspect, the application server provided in the eighth aspect, and the client provided in the ninth aspect.

The embodiment of the present invention provides a file upload method, a client and a server. The upload server receives the request message sent by the client. The request message includes a request header field, and judges whether the receiving condition of the file is met according to the request header field in the request message. , if the receiving condition of the file is met, the file is received, and a notification message is sent to the application server according to the callback address, where the callback address is carried in the request header field of the request message sent by the client, or the callback address is from the application It can simplify the file upload method and enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic flow chart of a file upload method provided by an embodiment of the present invention;

Fig. 2 is a schematic flow chart of a file uploading method provided by another embodiment of the present invention;

Fig. 3 is a schematic flow chart of a file uploading method provided by another embodiment of the present invention;

Fig. 4 is a schematic flow chart of a file uploading method provided by another embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method for uploading a file provided by another embodiment of the present invention;

Fig. 6 is a schematic structural diagram of an upload server provided by another embodiment of the present invention;

FIG. 7 is a schematic structural diagram of another upload server provided by another embodiment of the present invention;

FIG. 8 is a schematic structural diagram of yet another upload server provided by another embodiment of the present invention;

FIG. 9 is a schematic structural diagram of yet another upload server provided by another embodiment of the present invention;

FIG. 10 is a schematic structural diagram of yet another upload server provided by another embodiment of the present invention;

Fig. 11 is a schematic structural diagram of an application server provided by another embodiment of the present invention;

Fig. 12 is a schematic structural diagram of a client provided by another embodiment of the present invention;

Fig. 13 is a schematic structural diagram of an upload server provided by another embodiment of the present invention;

Fig. 14 is a schematic structural diagram of an application server provided by another embodiment of the present invention;

Fig. 15 is a schematic structural diagram of a client provided by another embodiment of the present invention;

Fig. 16 is a schematic structural diagram of a communication system provided by another embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The system architecture in the embodiment of the present invention may include a client, a CDN (Content Delivery Network, content distribution network) node, and an App site (Application, application server), and the client, the CDN node, and the App site all use HTTP (Hyper Text Transport Protocol, hypertext transfer protocol) communication protocol for communication. Clients and CDN nodes need to support 100-continue processing.

An embodiment of the present invention provides a file upload method, as shown in Figure 1, including:

101. The upload server receives a request message sent by the client, where the request message includes a request header field.

Among them, the upload server can be a CDN (Content Delivery Network) node based on cloud storage. This CDN node has the advantages of cloud storage and traditional CDN, and provides massive storage capacity. Users can upload and upload from the nearest CDN node. download file.

102. The upload server judges whether the receiving condition of the file is satisfied according to the request header field in the request message.

Wherein, the request header field in the request message sent by the client may include Expect: 100-continue, which is used to inquire whether the CDN is willing to receive the file.

103. If the receiving condition of the file is satisfied, the upload server receives the file, and sends a notification message to the application server according to the callback address.

Wherein, the App (Application, application server) site may be a website using CDN node upload and download services. The callback address may include a pre-upload callback address and a post-upload callback address.

Exemplarily, the callback address is carried in the request header field of the request message sent by the client, or the callback address is obtained from the application server.

Specifically, when the callback address is acquired from the application server, the registration message sent by the application server is received, the registration message includes the callback address, and the callback address is stored in the database. If the receiving condition of the file is met, the CDN node obtains the pre-upload callback address from the database according to the application identifier, and calls the pre-upload callback address to send a first notification message to the application server, the first notification message includes the first file information of the file, Then send an upload response message to the client, the upload response message includes the request header field, so that the client can continue to upload files, and then receive and store the file sent by the client according to the upload response message, and then get the callback after uploading from the database according to the application identifier address, and call the post-upload callback address to send a second notification message to the application server, where the second notification message includes the second file information of the file.

When the callback address is carried in the request header field of the request message sent by the client, if the receiving condition of the file is met, the CDN node obtains the pre-upload callback address from the request header field, and calls the pre-upload callback address to the application service The end sends a first notification message, the first notification message includes the first file information of the file, and then sends an upload response message to the client, the upload response message includes a request header field, so that the client can continue to upload the file, and then receive and store the client According to the file sent by the upload response message, the post-upload callback address is obtained from the request header field, and the post-upload callback address is called to send a second notification message to the application server. The second notification message includes the second file information of the file.

The embodiment of the present invention provides a method for uploading a file. The uploading server receives a request message sent by the client. The request message includes a request header field. According to the request header field in the request message, it is judged whether the receiving condition of the file is satisfied. conditions, the file is received and a notification message is sent to the application server according to the callback address, which can simplify the file upload method and enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Another embodiment of the present invention provides a file upload method, as shown in Figure 2, including:

201. The upload server receives a request message sent by the client, where the request message includes a request header field.

Wherein, the client may be a device such as a mobile phone or a computer used by the user, and the upload server may be a CDN node providing upload and download services. Clients, App sites, and CDN nodes all communicate using the HTTP (Hyper Text Transport Protocol, Hypertext Transfer Protocol) protocol.

Specifically, before uploading a file to the CDN node, the client sends an HTTP message to the CDN node, and the request message includes a request header field, which is used to inquire whether the CDN node is willing to accept the file uploaded by the client. The request header field may contain the first status code Expect: 100-continue, that is, the client and the CDN node need to support the processing of the 100-continue status code in the HTTP1.1 protocol. The request header field may also include an Appid (Application IDentity, application identifier) and a callback address. The callback address may include a pre-upload callback address (callback_url_pre) and a post-upload callback address (callback_url_post), so that the CDN node notifies the App site of the uploaded file information according to the callback address after receiving the request message sent by the client. The Appid application identifier is used to mark the App application server, and the CDN can distinguish the App site according to the Appid. Therefore, the requestor code can be as follows:

POST /app1/path/filename.ext HTTP/1.1

Host:upload.cdn.com

Expect: 100-continue

appid:app1

callback_url_pre: http://app1_domain_name/callback_url_pre

callback_url_post: http://app1_domain_name/callback_url_post

202. The upload server judges whether the receiving condition of the file is satisfied according to the request header field in the request message.

Specifically, when the CDN node blocks after receiving the request message from the client, it can judge whether the HTTP request header field contains the first status code Expect: 100-continue header according to the request header field in the request message. If it contains the Expect: 100- continue header, the communication with the client will continue, and the CDN node is willing to accept the file upload from the client; if the Expect:100-continue header is not included, the CDN node will disconnect from the client.

203. If the conditions for receiving the file are met, the upload server obtains the pre-upload callback address from the request header field, and calls the pre-upload callback address to send a first notification message to the application server. The first notification message includes the first file of the file information.

Specifically, if the request message sent by the client includes the Expect: 100-continue header, the condition for receiving the file is met. The CDN obtains the pre-upload callback address callback_url_pre from the request header field of the request message sent by the client, and invokes the pre-upload callback address to send the first notification message to the App site application server to notify the App site of the first notification message of the uploaded file. A file information. The first file information may include information such as file size and file name.

The program code of the callback request of this step process can be:

POST /callback_url_pre HTTP/1.1

Host: app1_domain_name

File_upload_info

HTTP/1.1200 OK

Connection: close

{"filename":"filename.ext","success":"true"}

204. The upload server sends an upload response message to the client, where the upload response message includes a request header field, so that the client can continue to upload the file.

Specifically, when the CDN node invokes the pre-upload callback address to call back to the App site successfully, it can return a response message to the client, agreeing to receive the file content sent by the client. Wherein, the response message may include a 100-continue header, so that the client continues to upload files to the CDN node. After the client receives the response header carrying 100-continue from the CDN node, it continues to upload the file content to the CDN node. When the client does not receive the response header returned by the CDN node, the client fails to upload the file.

The program code of the response process in this step can be as follows:

HTTP/1.1100 Continue

205. The upload server receives and stores the file sent by the client according to the upload response message, then obtains the post-upload callback address from the request header field, and calls the post-upload callback address to send a second notification message to the application server. The second notification message Include second file information for the file.

Specifically, after the CDN node sends an upload response message to the client, it continues to receive the file uploaded by the client. When the client continues to upload the file content to the CDN node until the file is uploaded, the CDN node receives the file content from the client The post-upload callback address callback_url_post is obtained in the sent request header field, and the post-upload callback address is called to send a second notification message to the App site, and the second notification message includes the second file information of the file uploaded by the client. The second file information may include file content of the file uploaded by the client. Wherein, the second notification message may further include a download URL (Universal Resource Locator, Uniform Resource Locator) field, so that the user can use the URL address to download the file from the CDN node.

The program code in this step can be:

POST/callback_url_post HTTP/1.1

Host: app1_domain_name

file_upload_info

HTTP/1.1200 OK

Connection: close

{"filename":"filename.ext","success":"true","url":"http://download.cdn.com/path/to/filename.ext"}

206. After receiving the file, the upload server sends a completion response message to the client.

Specifically, after successfully receiving the file content uploaded by the client, the CDN node stores the file content, and returns a response message to the client, and the client obtains the file upload success message. In this way, after the App site obtains the file information, assuming that the user downloads the file on the App application site, the App site can guide the user to download the file content in the CDN node through the URL corresponding to the file in the second notification message after uploading. As the upload server, the CDN node provides file upload and download services, and the App site, as the application server, uses the CDN node for upload and download services. In this way, when uploading a file, the file only needs to be uploaded to the CDN once through the callback address, which simplifies the upload method and enhances the processing ability before and after uploading. The application server does not need to purchase and maintain storage facilities.

An embodiment of the present invention provides a method for uploading a file. The request message sent by the client is received. The request message includes a request header field, and the request header field includes a callback address. According to the request header field in the request message, it is judged whether the receiving condition of the file is met. If If the receiving condition of the file is met, the upload server obtains the pre-upload callback address from the request header field, and calls the pre-upload callback address to send the first notification message to the application server. The first notification message includes the first file information of the file and sends The client sends an upload response message, which includes the request header field, so that the client can continue to upload files, receive and store the file sent by the client according to the upload response message, and then obtain the post-upload callback address from the request header field, and call After uploading, the callback address sends a second notification message to the application server. The second notification message includes the second file information of the file. After receiving the file, a completion response message is sent to the client, which can simplify the file upload method and enhance the processing before and after uploading capabilities, and the application server does not need to purchase and maintain storage devices.

Another embodiment of the present invention provides a file upload method, as shown in Figure 3, including:

301. The upload server receives a registration message sent by the application server, where the registration message includes a callback address.

Wherein, the uploading server may be a CDN node, providing uploading and downloading services. The App site may be a website using CDN node upload and download services.

Specifically, the CDN node may provide the App site with a callback registration interface, and the App site calls the callback registration interface to send a registration message to the CDN node. The registration message may include a callback address, including callback address callback_url_pre before upload and callback address callback_url_post after upload. The callback address can be registered with the CDN node through the App site to obtain file upload notifications. The program code of the App registration process can be:

POST/upload/regester HTTP/1.1

Host:upload.cdn.com

appid=app1﹠callback_url_pre=http℅3A℅2F℅2Fapp1_domain_nam e℅2Fcallback_url_pre﹠callback_url_post=http℅3A℅2F℅2Fapp1_domain_name℅2Fcallback_url_post

HTTP/1.1200 OK

Connection: close

{"appid":"app1","success":"true"}

302. The upload server saves the callback address in the database.

Specifically, after the App site successfully registers with the CDN node, the CDN node returns a registration response message to the App site, notifying the App site of successful registration. The CDN node saves the callback address registered by the App site in the database.

303. The upload server receives the request message sent by the client, where the request message includes a request header field.

Specifically, the client, the App site, and the CDN node all use the HTTP (Hyper Text Transport Protocol, hypertext transfer protocol) protocol for communication. When the client requests a CDN node to upload a file, it sends a request message to the CDN node, the request message includes a request header field, and the request header field includes the first status code Expect: 100-continue, that is, the client and the CDN node need to support the Handling of 100-continue status code in HTTP1.1 protocol. The request header field also includes Appid, and the Appid application identifier is used to identify the App application server, and the CDN node can distinguish the App site according to the Appid. The program code of the request message can be as follows:

POST /app1/path/filename.ext HTTP/1.1

Host:upload.cdn.com

Expect: 100-continue

appid:app1

304. The upload server judges whether the receiving condition of the file is satisfied according to the request header field in the request message.

Specifically, when the CDN node blocks after receiving the request message from the client, it can judge whether the HTTP request header field contains the first status code Expect: 100-continue header according to the request header field in the request message. If it contains the Expect: 100- continue header, the communication with the client will continue, and the CDN node is willing to accept the file upload from the client; if the Expect:100-continue header is not included, the CDN node will disconnect from the client.

305. If the receiving condition of the file is satisfied, the upload server obtains the pre-upload callback address from the database according to the application identifier, and calls the pre-upload callback address to send a first notification message to the application server. The first notification message includes the first notification message of the file. file information.

Specifically, when the request message from the client to upload a file satisfies the receiving condition of the file, the CDN node calls the pre-upload callback address callback_url_pre from the database according to the Appid application identifier, and calls the pre-upload callback address to send the first URL to the App site. The notification message is used to notify the first file information of the file uploaded by the App site client. The first file information may include information such as file size and file name.

The program code of the callback request of this step process can be:

POST /callback_url_pre HTTP/1.1

Host:app1_domain_name

File_upload_info

HTTP/1.1200 OK

Connection: close

{"filename":"filename.ext","success":"true"}

306. The upload server sends an upload response message to the client, where the upload response message includes a request header field, so that the client can continue to upload the file.

Specifically, when the CDN node invokes the pre-upload callback address to call back to the App site successfully, it can return a response message to the client, agreeing to receive the file content sent by the client. Wherein, the response message may include a 100-continue header, so that the client continues to upload files to the CDN node.

The program code of the response process in this step can be as follows:

HTTP/1.1100 Continue

After the client receives the response header carrying 100-continue from the CDN node, it continues to upload the file content to the CDN node. When the client does not receive the response header returned by the CDN node, the client fails to upload the file.

307. The upload server receives and stores the file sent by the client according to the upload response message, then obtains the post-upload callback address from the database according to the application identifier, and calls the post-upload callback address to send a second notification message to the application server, the second notification The message includes second file information of the file.

Specifically, when the client continues to upload the file content to the CDN node until the file is uploaded, after the CDN node receives the file content, the CDN node queries the database according to the Appid application identifier to obtain the post-upload callback address registered by the App site callback_url_post, The App site is notified of the uploaded second file information. The second file information may include file content of the file uploaded by the client. Wherein, the second notification message may also include a download URL field, so that the user can use the URL address to download the file from the CDN node.

The program code in this step can be:

POST/callback_url_post HTTP/1.1

Host:app1_domain_name

file_upload_info

HTTP/1.1200 OK

Connection: close

{"filename":"filename.ext","success":"true","url":"http://download.cdn.com/path/to/filename.ext"}

308. After receiving the file, the upload server sends a completion response message to the client.

Specifically, after successfully receiving the file content uploaded by the client, the CDN node stores the file content, and returns a response message to the client, and the client obtains the file upload success message. In this way, after the App site obtains the file information, assuming that the user downloads the file on the App application site, the App site can guide the user to download the file content in the CDN node through the URL corresponding to the file in the second notification message after uploading. As the upload server, the CDN node provides file upload and download services, and the App site, as the application server, uses the CDN node for upload and download services. In addition, the CDN node adopts the architecture combining CDN and cloud storage, so that when uploading files, the files uploaded by the client only need to be uploaded to the CDN once, which simplifies the uploading method and enhances the processing ability before and after uploading. There is no need to purchase and maintain storage facilities.

An embodiment of the present invention provides a method for uploading a file. It receives a registration message sent by an application server. The registration message includes a callback address, saves the callback address in a database, and receives a request message sent by a client. The request message includes a request header field. According to The request header field in the request message judges whether the receiving conditions of the file are met. If the receiving conditions of the file are met, the upload server obtains the pre-upload callback address from the database according to the application ID, and calls the pre-upload callback address to send the first A notification message, the first notification message includes the first file information of the file, and then sends an upload response message to the client, the upload response message includes a request header field, so that the client can continue to upload the file, and then receive and store the client according to the upload response The file sent by the message, and then obtain the post-upload callback address from the database according to the application identifier, and call the post-upload callback address to send the second notification message to the application server. The second notification message includes the second file information of the file. After receiving the file After that, sending a completion response message to the client can simplify the file upload method, enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Another embodiment of the present invention provides a file upload method, as shown in Figure 4, including:

401. The application server sends a registration message to the upload server, where the registration message includes a callback address when the file is uploaded.

Wherein, the application server is an App site, such as an Internet application site, a website, and the like. The CDN node provides a callback registration interface, and the App site can call the callback registration interface to send a registration message to the CDN node. The registration message includes a callback address, including a pre-upload callback address and a post-upload callback address. The callback address can be registered with the CDN node through the App site to obtain file upload notifications.

The program code of the app registration process can be:

POST/upload/regester HTTP/1.1

Host:upload.cdn.com

appid=app1﹠callback_url_pre=http℅3A℅2F℅2Fapp1_domain_nam e℅2Fc

callback_url_pre﹠callback_url_post=http℅3A℅2F℅2Fapp1_domain_name℅2Fcallback_url_post

HTTP/1.1200 OK

Connection: close

{"appid":"app1","success":"true"}

402. After the registration of the application server is completed, receive the file upload notification message sent by the upload server according to the callback address, so as to obtain the file information of the file.

Specifically, after the App site successfully registers with the CDN node, the CDN node returns a registration response message to the App site, notifying the App site of successful registration. The CDN node saves the callback address registered by the App site in the database.

The CDN node receives the request message sent by the client. The request message includes the request header field. The CDN node judges whether the receiving condition of the file is met according to the request header field in the request message. If the receiving condition of the file is met, the App site receives the CDN node according to Call back the first notification message sent by the address. The first notification message includes the first file information of the file. The first file information may include information such as the size of the file and the name of the file.

Wherein, the pre-upload callback address obtained by the CDN node can be obtained from the request header field sent by the client, that is, the callback address is carried in the request header field of the request message, or obtained from the database through the Appid.

Then, the CDN node sends an upload response message to the client, and the upload response message includes a request header field, so that the client can continue to upload the file.

When the CDN node finishes receiving the file, the CDN node obtains the post-upload callback address from the request header field sent by the client, or obtains the post-upload callback address from the database through the Appid, and sends the second post-upload callback address to the App site through the post-upload callback address. The notification message, that is, the App site receives the second notification message sent by the upload server according to the post-upload callback address. The second notification message includes the second file information of the file, and the second file information may include the file content of the file uploaded by the client. .

The embodiment of the present invention provides a file upload method. The application server sends a registration message to the upload server. The registration message includes the callback address when the file is uploaded. After the registration of the application server is completed, the upload server receives the file sent by the callback address. The upload notification message is used to obtain the file information of the file, which can simplify the file upload method and enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Another embodiment of the present invention provides a file upload method, as shown in Figure 5, including:

501. The client sends a request message to the upload server, where the request message includes a request header field.

Wherein, the client refers to a program that corresponds to the server and provides local services for the client, such as a browser and various mobile phone applications. Except for some applications that only run locally, they are generally installed on ordinary client computers and need to cooperate with the server to run. For example, it can run on the user's computer, mobile phone and other devices.

The request header field may include the first status code Expect: 100-continue, and the client and the CDN node need to support the processing of the 100-continue status code in the HTTP1.1 protocol. It also includes Appid, which is used to identify the App application server, and the CDN can distinguish App sites according to the Appid.

502. The client receives the upload response message sent by the upload server.

Specifically, when the client sends a request message to the CDN node, the CDN node judges whether the receiving condition of the file is satisfied according to whether the request header field of the request message contains the first status code Expect: 100-continue. If the receiving condition of the file is satisfied, the CDN The node sends a first notification message to the client through the pre-upload callback address, the first notification message includes the first file information of the file, and then sends an upload response message to the client.

Wherein, the upload response message includes the request header field in the request message sent by the client, so that the client can continue to upload the file. The callback address can be carried in the request header field of the request message sent by the client, or the callback address can be obtained from the application server, including the pre-upload callback address and post-upload callback address. When the callback address is obtained from the application server, by receiving the registration message sent by the application server, the registration message includes the callback address, and saves the callback address in the database.

503. The client uploads the file to the upload server according to the upload response message.

Specifically, after receiving the response header carrying 100-continue from the CDN node, the client continues to upload the file content to the CDN node. When the client does not receive the response header returned by the CDN node, the client fails to upload the file.

Then, the CDN node obtains the post-upload callback address from the request header field, or obtains the post-upload callback address from the database, and calls the post-upload callback address to send a second notification message to the application server. The second notification message includes the second file information.

The embodiment of the present invention provides a file upload method. The client sends a request message to the upload server, and after receiving the upload response message sent by the upload server, uploads the file to the upload server according to the upload response message, which can simplify the file upload method. .

Yet another embodiment of the present invention provides an upload server 01, as shown in FIG. 6, including:

The receiving unit 016 is configured to receive a request message sent by the client, where the request message includes a request header field.

The judging unit 011 is configured to judge whether the file receiving condition is satisfied according to the request header field in the request message.

The processing unit 012 is configured to receive the file if the file receiving condition is satisfied, and send a notification message to the application server according to the callback address.

Wherein, the callback address includes a pre-upload callback address and a post-upload callback address.

Optionally, the request header field also includes an application identifier, which is used to identify the application server.

Optionally, the callback address is carried in the request header field of the request message sent by the client, or the callback address is obtained from the application server.

Optionally, as shown in Figure 7, when the callback address is obtained from the application server, it also includes:

The first receiving unit 014 is configured to receive a registration message sent by the application server before receiving the request message sent by the client, and the registration message includes a callback address.

The storage unit 015 is configured to store the callback address in the database.

Optionally, as shown in FIG. 8, when the callback address is obtained from the application server, the processing unit 012 may include:

The first processing subunit 0121 is configured to obtain the pre-upload callback address from the database according to the application identifier if the file receiving condition is met, and call the pre-upload callback address to send a first notification message to the application server, the first notification message includes the file The first file information.

The first sending subunit 0122 is configured to send an upload response message to the client, where the upload response message includes a request header field, so that the client can continue to upload files.

The second processing subunit 0123 is used to receive and store the file sent by the client according to the upload response message, then obtain the post-upload callback address from the database according to the application identifier, and call the post-upload callback address to send the second notification message to the application server , the second notification message includes second file information of the file.

Optionally, as shown in FIG. 9, when the callback address is carried in the request header field of the request message sent by the client, the processing unit 012 may include:

The third processing subunit 0124 is configured to obtain the pre-upload callback address from the request header field if the receiving condition of the file is met, and call the pre-upload callback address to send a first notification message to the application server, the first notification message includes the file The first file information.

The second sending subunit 0125 is configured to send an upload response message to the client, where the upload response message includes a request header field, so that the client can continue to upload files.

The fourth processing subunit 0126 is configured to receive and store the file sent by the client according to the upload response message, then obtain the post-upload callback address from the request header field, and call the post-upload callback address to send the second notification message to the application server, The second notification message includes second file information of the file.

Optionally, as shown in Figure 10, may also include:

The response unit 013 is configured to send a completion response message to the client after receiving the file.

Wherein, the receiving unit 016 is configured to execute step 101 in the embodiment shown in FIG. 1, or step 201 in the embodiment shown in FIG. 2, or step 303 in the embodiment shown in FIG. 3; the judging unit 011 is used to Execute step 102 in the embodiment shown in Figure 1, or step 202 in the embodiment shown in Figure 2, or step 304 in the embodiment shown in Figure 3; processing unit 012 is used to execute in the embodiment shown in Figure 1 Step 103 in the embodiment shown in FIG. 2, or steps 203 to 205 in the embodiment shown in FIG. 2, or steps 305 to 307 in the embodiment shown in FIG. 3; the first receiving unit 014 is used to execute the Step 301; the storage unit 015 is used to execute step 302 in the embodiment shown in FIG. 3; the first processing subunit 0121 is used to execute step 305 in the embodiment shown in FIG. 3; the first sending subunit 0122 is used to execute the Step 306 in the embodiment shown in Figure 3; the second processing subunit 0123 is used to execute step 307 in the embodiment shown in Figure 3; the third processing subunit 0124 is used to execute step 203 in the embodiment shown in Figure 2; The second sending subunit 0125 is used to execute step 204 in the embodiment shown in FIG. 2; the fourth processing subunit 0126 is used to execute step 205 in the embodiment shown in FIG. Step 206 in the embodiment, or step 308 in the embodiment shown in FIG. 3 .

An embodiment of the present invention provides an upload server. The upload server receives a request message sent by a client. The request message includes a request header field. According to the request header field in the request message, it is judged whether the receiving condition of the file is satisfied. conditions, the file is received and a notification message is sent to the application server according to the callback address, which can simplify the file upload method and enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Yet another embodiment of the present invention provides an application server 02, as shown in FIG. 11 , including:

The second sending unit 021 is configured to send a registration message to the upload server, where the registration message includes a callback address when the file is uploaded.

The second receiving unit 022 is configured to receive a file upload notification message sent by the upload server according to the callback address after the registration is completed, so as to obtain file information of the file.

Wherein, the callback address includes a pre-upload callback address and a post-upload callback address.

Optionally, the second receiving unit 022 may be used for:

receiving the first notification message sent by the upload server according to the pre-upload callback address, the first notification message includes the first file information of the file;

When the uploading server finishes receiving the file, it receives the second notification message sent by the uploading server according to the post-upload callback address, and the second notification message includes the second file information of the file.

Wherein, the second sending unit 021 is configured to execute step 401 in the embodiment shown in FIG. 4 , and the second receiving unit 022 is configured to execute step 402 in the embodiment shown in FIG. 4 .

The embodiment of the present invention provides an application server. The application server sends a registration message to the upload server. The registration message includes the callback address when the file is uploaded. After the registration of the application server is completed, the upload server receives the file sent by the callback address. The upload notification message is used to obtain the file information of the file, which can simplify the file upload method and enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Another embodiment of the present invention provides a client 03, as shown in Figure 12, including:

The third sending unit 031 is configured to send a request message to the upload server, where the request message includes a request header field.

The third receiving unit 032 is configured to receive an upload response message sent by the upload server, where the upload response message includes a request header field.

The file uploading unit 033 is configured to upload the file to the upload server according to the upload response message.

Optionally, the request header field includes an application identifier, or the request header field includes a callback address and an application identifier.

Optionally, can also include:

After the upload server successfully calls back to the application server through the callback address, it receives the completion response message sent by the upload server.

Wherein, the third sending unit 031 is used to execute step 501 in the embodiment shown in FIG. 5; the third receiving unit 032 is used to execute step 502 in the embodiment shown in FIG. Step 503 in the illustrated embodiment.

An embodiment of the present invention provides a client. The client sends a request message to the upload server. The request message includes a request header field, and receives an upload response message sent by the upload server. The upload response message includes a request header field. According to the upload response message, Uploading files to the upload server can simplify the file upload method.

Another embodiment of the present invention provides an upload server 04, as shown in Figure 13, the upload server 04 includes: a first bus 041, a first processor 042 connected to the first bus 041, and a first memory 043 , a first receiver 044 and a first transmitter 045, wherein the first memory 043 is used to store instructions, and the first receiver 044 is used to execute the instructions to receive a request message sent by the client, the request message includes a request The header field is specifically used to execute step 101 in the embodiment shown in FIG. 1, or step 201 in the embodiment shown in FIG. 2, or step 303 in the embodiment shown in FIG. 3; the first processor 042 uses Executing this instruction is used to judge whether the receiving condition of the file is met according to the request header field in the request message, specifically to execute step 102 in the embodiment shown in Figure 1, or step 202 in the embodiment shown in Figure 2, Or step 304 in the embodiment shown in Figure 3; the first receiver 044 is also used to execute the instruction and is also used to receive the file if the file receiving condition is met, and the first transmitter 045 calls the callback address to send the file to the application server The notification message is specifically used to execute step 103 in the embodiment shown in Figure 1, or steps 203 to 205 in the embodiment shown in Figure 2, or steps 305 to 307 in the embodiment shown in Figure 3;

In this embodiment of the present invention, optionally, the callback address includes a pre-upload callback address and a post-upload callback address.

In this embodiment of the present invention, optionally, the request header field includes an application identifier, and the application identifier is used to identify the application server.

In this embodiment of the present invention, optionally, the callback address is carried in the request header field of the request message sent by the client, or the callback address is obtained from the application server.

In the embodiment of the present invention, optionally, when the callback address is obtained from the application server, the first receiver 044 is used to execute the instruction, including:

Before receiving the request message sent by the client, the first receiver is also used to receive a registration message sent by the application server, the registration message includes a callback address, and is specifically used to execute step 301 in the embodiment shown in FIG. 3 ;

The first memory 043 is used to save the callback address in the database, and is specifically used to execute step 302 in the embodiment shown in FIG. 3 .

In this embodiment of the present invention, optionally, when the callback address is obtained from the application server, the first receiver 044, the first processor 042 and the first transmitter 045 execute the instruction and are also used to:

If the file receiving condition is met, the first processor 042 obtains the pre-upload callback address from the database according to the application identifier, and the first transmitter 045 invokes the pre-upload callback address to send a first notification message to the application server. The first notification message includes The first file information of the file is specifically used to execute step 305 in the embodiment shown in FIG. 3;

The first transmitter 045 is also configured to send an upload response message to the client, where the upload response message includes a request header field, so that the client can continue to upload the file, and is specifically used to execute step 306 in the embodiment shown in FIG. 3 ;

If the first receiver 044 is also used to receive and store the file sent by the client according to the upload response message, and the first storage 043 is also used to store the file, the first processor 042 obtains the post-upload callback address from the database according to the application identifier, The first transmitter 045 invokes the post-upload callback address to send a second notification message to the application server. The second notification message includes the second file information of the file, and is specifically used to execute step 307 in the embodiment shown in FIG. 3 .

In this embodiment of the present invention, optionally, when the callback address is carried in the request header field of the request message sent by the client, the first receiver 044, the first processor 042, the first memory 043 and the first A transmitter 045 executes the command for:

If the file receiving condition is satisfied, the first processor 042 obtains the pre-upload callback address from the request header field, and the first transmitter 045 invokes the pre-upload callback address to send a first notification message to the application server, the first notification message includes the file The first file information is specifically used to execute step 203 in the embodiment shown in FIG. 2;

The first transmitter 045 sends an upload response message to the client, and the upload response message includes a request header field, so that the client can continue to upload the file, and is specifically used to execute step 204 in the embodiment shown in FIG. 2 ;

If the first receiver 044 is also used to receive and store the file sent by the client according to the upload response message, and the first storage 043 is also used to store the file, the first processor 042 obtains the post-upload callback address from the request header field, and the first A transmitter 045 invokes the post-upload callback address to send a second notification message to the application server. The second notification message includes the second file information of the file, and is specifically used to execute step 205 in the embodiment shown in FIG. 2 .

In this embodiment of the present invention, optionally, after receiving the file, the first transmitter 045 executes the instruction to send a completion response message to the client, specifically to execute step 206 in the embodiment shown in FIG. 2 , or step 308 in the embodiment shown in FIG. 3 .

Therefore, in the uploading server of the embodiment of the present invention, the uploading server receives the request message sent by the client, the request message includes the request header field, and judges whether the receiving condition of the file is satisfied according to the request header field in the request message. condition, the file is received and a notification message is sent to the application server according to the callback address, which can simplify the file upload method and enhance the processing ability before and after uploading.

Another embodiment of the present invention provides an application server 05. As shown in FIG. 14, the application server includes: a second bus 041, a second processor 042 connected to the second bus 041, a second memory 043, The second receiver 044 and the second transmitter 045, wherein the second memory 043 is used to store instructions, and the second transmitter 045 executes the instructions to send a registration message to the upload server, the registration message includes the file upload Callback address; the second receiver 044 executes the instruction to receive the file upload notification message sent by the upload server according to the callback address after the registration is completed, so as to obtain the file information of the file.

In this embodiment of the present invention, optionally, the callback address includes a pre-upload callback address and a post-upload callback address.

In this embodiment of the present invention, optionally, the second receiver 044 executes the instruction for:

receiving the first notification message sent by the upload server according to the pre-upload callback address, the first notification message includes the first file information of the file;

When the uploading server finishes receiving the file, it receives the second notification message sent by the uploading server according to the post-upload callback address, and the second notification message includes the second file information of the file.

Wherein, the second transmitter 045 is used to execute step 401 in the embodiment shown in FIG. 4 , and the second receiver 044 is used to execute step 402 in the embodiment shown in FIG. 4 .

Therefore, in the application server of the embodiment of the present invention, the application server sends a registration message to the upload server. The registration message includes the callback address when the file is uploaded. After the registration of the application server is completed, the upload server receives the file sent by the callback address. The upload notification message is used to obtain the file information of the file, which can simplify the file upload method and enhance the processing ability before and after uploading, and the application server does not need to purchase and maintain storage devices.

Yet another embodiment of the present invention provides a client 06. As shown in FIG. Three receivers 044 and a third transmitter 045, wherein the third memory 043 is used to store instructions; the third transmitter 045 executes the instructions to send a request message to the upload server, and the request message includes a request header field; The third receiver 044 executes the instruction to receive the upload response message sent by the upload server, the upload response message includes the request header field; the third processor 042 executes the instruction to upload the file to the upload server according to the upload response message .

In this embodiment of the present invention, optionally, the request header field includes an application identifier, or the request header field includes a callback address and an application identifier.

In the embodiment of the present invention, optionally, after the upload server successfully calls back to the application server through the callback address, the third receiver 044 is used to execute the instruction and to receive a completion response message sent by the upload server.

Wherein, the third transmitter 045 is used to execute step 501 in the embodiment shown in FIG. 5; the third receiver 044 is used to execute step 502 in the embodiment shown in FIG. 5; the third processor 042 uses Step 503 in the embodiment shown in FIG. 5 is executed.

Therefore, in the client of the embodiment of the present invention, the client sends a request message to the upload server, the request message includes a request header field, receives an upload response message sent by the upload server, the upload response message includes a request header field, and according to the upload response message, Uploading files to the upload server can simplify the file upload method.

Another embodiment of the present invention provides a communication system 1 , as shown in FIG. 16 , including: the upload server 04 , the application server 05 and the client 06 provided in the foregoing embodiments.

Wherein, the upload server 04 is used to execute steps 101 to 103 in the embodiment shown in FIG. 1, or steps 201 to 206 in the embodiment shown in FIG. 2, or steps 301 to 206 in the embodiment shown in FIG. 308 ; the application server 05 is used to execute steps 401 to 402 in the embodiment shown in FIG. 4 ; the client 06 is used to execute steps 501 to 503 in the embodiment shown in FIG. 5 .

The embodiment of the present invention provides a communication system. The uploading server receives the request message sent by the client. The request message includes a request header field, and judges whether the file receiving condition is satisfied according to the request header field in the request message. If the file receiving condition is satisfied, Then receive the file and send a notification message to the application server according to the callback address. The callback address includes the callback address before upload and the callback address after upload. If the file is received, the file will be stored in the upload server and sent to the client. Response message, in which the callback address is carried in the request header field of the request message sent by the client, or the callback address is obtained from the application server, which can simplify the file upload method, enhance the processing ability before and after uploading, and the application server There is no need to purchase and maintain storage devices.

In the several embodiments provided in this application, it should be understood that the disclosed system, client, server and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

In addition, in the devices and systems in various embodiments of the present invention, each functional unit may be integrated into one processing unit, each unit may be physically included separately, or two or more units may be integrated into one unit. Moreover, each of the above-mentioned units can be implemented in the form of hardware, or can be implemented in the form of hardware plus software functional units.

All or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium, and when the program is executed, the steps including the above-mentioned method embodiments are executed; The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc., which can store program codes. medium.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (22)

1. a kind of file uploading method is it is characterised in that include:

Receive the request message that client sends, described request message includes asking header field, described request header field includes readjustment ground Location, described loopback address includes uploading loopback address after front loopback address and upload；

Judge whether to meet the condition of acceptance of file according to the request header field in described request message；

If meeting the condition of acceptance of described file, obtaining loopback address before described upload from described request header field, and calling Before described upload, loopback address sends the first notification message to application service end, and described first notification message includes described file First fileinfo；

Send to described client and upload response message, described upload response message includes described request header field, in order to described Client continues to upload described file；

Receive and store described client and upload, according to described, the described file that response message sends, then from described request header field Middle obtain described upload after loopback address, and call described upload after loopback address to described application service end send second notice Message, described second notification message includes the second fileinfo of described file.

2. method according to claim 1 is it is characterised in that methods described also includes:

After having received described file, it is sent completely response message to described client.

3. a kind of file uploading method is it is characterised in that include:

Receive the request message that client sends, described request message includes asking header field, described request header field also includes applying Mark, described application identities are used to identify application service end, and receive the registration message that described application service end sends, institute State registration message and include loopback address, described loopback address includes uploading loopback address after front loopback address and upload, will be described Loopback address is saved in database；

Judge whether to meet the condition of acceptance of file according to the request header field in described request message；

If meeting the condition of acceptance of described file, obtain loopback address before upload from database according to described application identities, And loopback address sends the first notification message to described application service end before calling described upload, described first notification message includes First fileinfo of described file；

Send to described client and upload response message, described upload response message includes described request header field, in order to described Client continues to upload described file；

Receive and store described client and upload, according to described, the described file that response message sends, then according to described application mark Know from described database obtain upload after loopback address, and call described upload after loopback address send out to described application service end Send second notification message, described second notification message includes the second fileinfo of described file.

4. method according to claim 3 is it is characterised in that methods described also includes:

After having received described file, it is sent completely response message to described client.

5. a kind of file uploading method is it is characterised in that include:

Send registration message to uploading service end, described registration message includes loopback address during files passe, described readjustment ground Location includes uploading loopback address after front loopback address and upload；

After the completion of registration, receive the first notification message that described upload service end sends according to loopback address before described upload, Described first notification message includes the first fileinfo of described file；

When described upload service termination harvests described file, receive described upload service end according to loopback address after described upload The second notification message sending, described second notification message includes the second fileinfo of described file.

6. a kind of file uploading method is it is characterised in that include:

Send request message to uploading service end, described request message includes asking header field, described request header field includes application mark Know, or described request header field includes loopback address and described application identities, described loopback address includes uploading front loopback address With loopback address after upload, before described upload, loopback address is used for making described upload service end receive the file that client sends Forward direction application server end send the first notification message, described first notification message include described file first file letter Breath, after described upload, loopback address is used for making described upload service end send to described application service end after receiving described file Second notification message, described second notification message includes the second fileinfo of described file；

Receive the upload response message that described upload service end sends, described upload response message includes described request header field；

According to described upload response message, the transmitting file on described upload service end.

7. method according to claim 6 is it is characterised in that methods described also includes:

After described upload service end adjusts back success by described loopback address to application service end, receive described upload service What end sent completes response message.

8. a kind of upload service end is it is characterised in that combine cloud storage function, comprising:

Receiving unit, for receiving the request message of client transmission, described request message includes asking header field, described request header Domain includes loopback address, and described loopback address includes uploading loopback address after front loopback address and upload；

Judging unit, for judging whether to meet the condition of acceptance of file according to the request header field in described request message；

Processing unit, if for the condition of acceptance meeting described file, return before obtaining described upload from described request header field Adjust address, and call described upload before loopback address to application service end send the first notification message, described first notification message The first fileinfo including described file；

Send to described client and upload response message, described upload response message includes described request header field, in order to described Client continues to upload described file；

Receive and store described client and upload, according to described, the described file that response message sends, then from described request header field Middle obtain described upload after loopback address, and call described upload after loopback address to described application service end send second notice Message, described second notification message includes the second fileinfo of described file.

9. upload service end according to claim 8 is it is characterised in that also include:

Response unit, for, after having received described file, being sent completely response message to described client.

10. a kind of upload service end is it is characterised in that include:

Receiving unit, for receiving the request message of client transmission, described request message includes asking header field, described request header Domain also includes application identities, and described application identities are used to identify application service end；And first receiving unit, for receiving The registration message that described application service end sends, described registration message includes loopback address, before described loopback address includes uploading Loopback address after loopback address and upload；Memory cell, for being saved in described loopback address in database；

Judging unit, for judging whether to meet the condition of acceptance of file according to the request header field in described request message；

Processing unit, if for the condition of acceptance meeting described file, obtain from database according to described application identities Loopback address before biography, and loopback address sends the first notification message to described application service end before calling described upload, described the One notification message includes the first fileinfo of described file；

Send to described client and upload response message, described upload response message includes described request header field, in order to described Client continues to upload described file；

Receive and store described client and upload, according to described, the described file that response message sends, then according to described application mark Know from described database obtain upload after loopback address, and call described upload after loopback address send out to described application service end Send second notification message, described second notification message includes the second fileinfo of described file.

11. upload service ends according to claim 10 are it is characterised in that also include:

Response unit, for, after having received described file, being sent completely response message to described client.

A kind of 12. application service ends are it is characterised in that include:

Second transmitting element, for uploading service end transmission registration message, described registration message includes returning during files passe Adjust address, described loopback address includes uploading loopback address after front loopback address and upload；

Second receiving unit, sends out according to loopback address before described upload for after the completion of registration, receiving described upload service end The first notification message sending, described first notification message includes the first fileinfo of described file；

When described upload service termination harvests described file, receive described upload service end according to loopback address after described upload The second notification message sending, described second notification message includes the second fileinfo of described file.

A kind of 13. clients, are characterised by, comprising:

3rd transmitting element, for upload service end send request message, described request message include ask header field, described please Ask header field to include application identities, or described request header field includes loopback address and described application identities, described loopback address bag Loopback address after including before upload loopback address and uploading, before described upload, loopback address is used for making described upload service end receive The forward direction application server end of the file that client sends sends the first notification message, and described first notification message includes described literary composition First fileinfo of part, after described upload, loopback address is used for making described upload service end to described after receiving described file Application service end sends second notification message, and described second notification message includes the second fileinfo of described file；

3rd receiving unit, for receiving the upload response message that described upload service end sends, described upload response message bag Include described request header field；

Files passe unit, for according to described upload response message, the transmitting file on described upload service end.

14. clients according to claim 13 are it is characterised in that also include:

After described upload service end adjusts back success by described loopback address to application service end, receive described upload service What end sent completes response message.

A kind of 15. upload service ends are it is characterised in that include:

First receiver, for receiving the request message of client transmission, described request message includes asking header field, described request Header field includes loopback address, and described loopback address includes uploading loopback address after front loopback address and upload；

First processor, for judging whether to meet the condition of acceptance of file according to the request header field in described request message；

Described first processor, if being additionally operable to meet the condition of acceptance of described file, obtains described from described request header field Loopback address before upload, before first transmitter is used for calling described upload, loopback address notifies to disappear to application service end transmission first Breath, described first notification message includes the first fileinfo of described file；

Described first transmitter, is additionally operable to send upload response message to described client, described upload response message includes institute State request header field, continue to upload described file in order to described client；

Described first receiver, for receive described client according to described upload response message send described file, first Memory is additionally operable to store described file, and described first processor is adjusted back after being used for obtaining described upload from described request header field Address, after described first transmitter is used for calling described upload, loopback address notifies to disappear to described application service end transmission second Breath, described second notification message includes the second fileinfo of described file.

16. upload service ends according to claim 15, it is characterised in that described first transmitter, are additionally operable to receiving After complete described file, it is sent completely response message to described client.

A kind of 17. upload service ends are it is characterised in that include:

First receiver, for receiving the request message of client transmission, described request message includes asking header field, described request Header field also includes application identities, and described application identities are used to identify application service end；Described first receiver is additionally operable to connect Receive the registration message that described application service end sends, described registration message includes loopback address, described loopback address includes uploading Loopback address after front loopback address and upload；

First memory is used for described loopback address is saved in database；

First processor, for judging whether to meet the condition of acceptance of file according to the request header field in described request message；

Described first processor, if be additionally operable to meet the condition of acceptance of described file, according to described application identities from database Loopback address before middle acquisition upload, before first transmitter is used for calling described upload, loopback address sends to described application service end First notification message, described first notification message includes the first fileinfo of described file；

Described first transmitter, is additionally operable to send upload response message to described client, described upload response message includes institute State request header field, continue to upload described file in order to described client；

Described first receiver, is additionally operable to receive and store described client according to the described described literary composition uploading response message transmission Part, described first processor is additionally operable to obtain loopback address after upload from described database according to described application identities, described First transmitter be additionally operable to call described after uploading loopback address send second notification message to described application service end, described the Two notice message packages include the second fileinfo of described file.

18. upload service ends according to claim 17 are it is characterised in that also include:

After having received described file, described first transmitter is additionally operable to be sent completely response message to described client.

A kind of 19. application service ends are it is characterised in that include:

Second transmitter, for uploading service end transmission registration message, described registration message includes readjustment during files passe Address, described loopback address includes uploading loopback address after front loopback address and upload；

Second receiver, sends according to loopback address before described upload for after the completion of registration, receiving described upload service end The first notification message, described first notification message includes the first fileinfo of described file；

When described upload service termination harvests described file, receive described upload service end according to loopback address after described upload The second notification message sending, described second notification message includes the second fileinfo of described file.

A kind of 20. clients are it is characterised in that include:

3rd transmitter, for uploading service end transmission request message, described request message includes asking header field, described request Header field includes application identities, or described request header field includes loopback address and described application identities, and described loopback address includes Loopback address and loopback address after uploading before upload, before described upload, loopback address is used for making described upload service end receiving visitor The forward direction application server end of the file that family end sends sends the first notification message, and described first notification message includes described file The first fileinfo, after described upload loopback address be used for making described upload service end after receiving described file to described should Send second notification message with service end, described second notification message includes the second fileinfo of described file；

3rd receiver, for receiving the upload response message that described upload service end sends, described upload response message includes Described request header field；

3rd processor, for according to described upload response message, the transmitting file on described upload service end.

21. clients according to claim 20 are it is characterised in that also include:

After described upload service end adjusts back success by described loopback address to application service end, described 3rd receiver is also Complete response message for receive that described upload service end sends.

A kind of 22. communication systems are it is characterised in that include:

Upload service end as described in claim 15 or 16, or the upload service end as described in claim 17 or 18；Right Require the application service end described in 19；Client described in claim 20 or 21.