WO2009039705A1

WO2009039705A1 - A method and system for realizing file transfer through browser

Info

Publication number: WO2009039705A1
Application number: PCT/CN2007/070813
Authority: WO
Inventors: Jianxiang Mo
Original assignee: Alibaba Group Holding Limited
Priority date: 2007-09-28
Filing date: 2007-09-28
Publication date: 2009-04-02

Abstract

A method and system for realizing file transfer through browser is disclosed, used to resolve the problem in the current instant messaging technology that the file can be transferred only when particular instant messaging software is installed; in this method, a source user requests to transfer file to a target user, and at least one of the source user and the target user is a browser user; a file transfer link is established between the source user and the target user through the Web server with which the browser user associates; and, the source user transfers file to the target user through the file transfer link. Through the present invention, the file transfer between a browser user and an instant messaging user can be realized, and the file transfer between browser users can also be realized.

Description

Method and system for realizing file transfer through browser

The present invention relates to instant messaging technologies, and more particularly to a method and system for implementing file transfer through a browser. Background technique

Existing instant messaging is generally performed by installing specific desktop software, such as Tradelink, QQ, MSN, etc. These softwares need to be downloaded and installed and downloaded slowly. Generally, users need to upgrade or automatically upgrade the software version in the background. If the user does not upgrade, the old download and install instant messaging client software is still used. If you only want to send a small file to a friend and need to download a few megabytes, or even dozens of megabytes of client software, this operation is time consuming and cumbersome.

In the existing instant messaging, the method of transferring files is generally accomplished by point-to-point communication between the instant messaging client software. If the clients can communicate directly, the IP address and the opened port of the other party are obtained through the instant messaging server, and a TCP (UDP)/IP connection is directly established between the clients for file transfer; however, the instant messaging client software is used. File transfer is easy to cause file leaks, and because of the firewall and other reasons, the client can't communicate directly. It needs to transfer files through other server groups for transmission. Summary of the invention

The present invention provides a method and system for implementing file transfer through a browser, which solves the problem that only a specific instant messaging software can be installed before file transfer can be performed.

A method for implementing file transfer by a browser provided by the present invention includes:

The source user requests to transfer a file to the target user, at least one of the source user and the target user is a browser user;

Establishing a file transmission link between the source user and the target user by using a web server corresponding to the browser user. The file delivery system provided by the present invention includes: At least two user equipments for transmitting and receiving files, at least one of which is a user equipment provided with a browser;

Establishing, by the at least one web server, a network connection with the at least one browser-equipped user equipment, where the web server establishes a file transmission link between the at least two user equipments according to the request of the user equipment to transmit a file Transfer files.

More preferably, the system further comprises:

An instant messaging status server, configured to record status information of a user server and a user where the user equipment is located;

According to the state information of the server and the user of the user recorded by the instant messaging status server, if one of the user equipments is an instant communication user equipment, the system further includes: an instant communication server, connected to the instant communication user equipment, Interacting with the web server to forward an instant message between the user devices.

And a distribution server, configured to allocate a web server for a user device that sends a login request to the web server, and redirect the login request to the web server.

A file transfer server is respectively connected to the user equipment and the web server, and is configured to cooperate with the web server to transfer files.

The technical solution provided by the invention can realize the file transfer of the browser user who does not download and install the instant messaging software and the user who installs the instant communication software, and can also realize the file transfer between the browser users who have not downloaded and installed the instant communication software. There is no case where the file transfer cannot be performed due to the firewall blocking; and as long as the version is updated on the server side, the user opens the browser for file transfer, which is the latest version, so that the user does not need to upgrade the user, and the invention can be implemented simply and quickly. File transfer. DRAWINGS

1A is a schematic structural diagram of a file transfer system according to an embodiment of the present invention;

1B is a schematic structural diagram of a system for file transfer between a browser user and an instant communication user according to an embodiment of the present invention;

1C is a schematic structural diagram of a system for transferring a file between browser users according to an embodiment of the present invention; FIG. 2 is a flowchart of a browser user transmitting a file to an instant communication user according to an embodiment of the present invention; a flow chart of a communication user transmitting a file to a browser user; 4 is a flowchart of file transfer between browser users in the same network domain according to an embodiment of the present invention;

FIG. 5 is a flowchart of canceling file transfer by a user during file transfer in an embodiment of the present invention. detailed description

In order to enable a browser user who does not have a specific instant messaging software installed to perform file transfer with a user who installs the instant messaging software (hereinafter referred to as an instant messaging user) and a browser user who does not have the instant messaging software installed, the present invention passes the browser user. The web server is located to establish a file transfer link between users to implement file transfer between users.

Referring to FIG. 1A (other user equipments and servers are not shown in the figure), a file transfer system of this embodiment includes an instant messaging status server 13, a web server 12 and a user server B15 connected to the instant messaging status server 13, User equipment a10 (ie, browser user) connected to the web server 12, user equipment bl4 connected to the user server B15 (which may be a browser user or an instant communication user), and a connection with the web server 12 and the user equipment alo Distribution server 11; wherein

The instant messaging status server 13 is configured to record status information of the web server 12 and the user server B15 and the user where the user equipment alO and the user equipment bl4 are located;

The web server 12 establishes a file transfer link between the user devices and transmits the file through the web server 12 according to the state information of the server and the user of the user recorded by the instant messaging status server 13;

The user equipment alO and user equipment bl4, for transmitting and receiving files or instant messages; the distribution server 11 for allocating the web server 12 to the user equipment alO, and redirecting the login request to the web server 12.

The system also includes a file transfer server coupled to the instant messaging user device and the web server for forwarding files between browser users or between browser users and instant messaging users.

In the system of the present invention, the user server may also include an instant messaging server that is connected to the instant messaging user.

As shown in FIG. 1B (other user equipments and servers are not shown in the figure), a schematic diagram of a system structure for file transfer between a browser user and an instant communication user; in the system, file transmission The server 105 is connected to the web server 102 and the user device B 104 connected to the instant messaging server 103, respectively, and establishes a file transfer link and transfers files through the web server 102, the file transfer server 105, and the user device B 104 connected to the instant messaging server.

Correspondingly, the system structure for file transfer between browser users is as shown in FIG. 1C (other user equipments and servers are not shown in the figure); in the system, the file transfer server 115 is connected to the web server A 112 and the web server B 113 respectively. The file transfer link is established and the file is transmitted through the web server A 112, the file transfer server 115, and the web server B 113. When the two browser users are in the same network domain, the user may be directly connected to the web server A 112 and not through the file transfer server 115. The web server B113 performs file transfer.

The steps for the browser user to log in to the web server include:

The browser user sends a login request to the distribution server; the distribution server allocates a web server to the browser user according to the information carried in the login request, and redirects the login request to the web server; the web server verifies the browser user information, and Allow the user to log in after successful authentication.

After the browser user successfully logs in to the web server and performs instant communication with the instant messaging user or the browser user, the server of the source user queries the server information currently logged in by the target user, and forwards the instant message sent by the source user to the query result. The server where the target user is located; then the instant message provided by the target user's server to the target user, and the instant message replied by the target user is sent to the server where the source user is located, and the instant message is provided to the source user.

In the instant communication process, the instant messaging server can directly forward the instant message sent by the browser user to the instant communication user; but the web server cannot directly forward the instant message sent by the friend user to the browser user, but needs the browser user to go to the web. The instant message sent by the friend user is retrieved on the server.

The browser user sends a message or send a message command to the web server in the Ajax (asynchronous XMLHTTP) mode through the browser. The browser user sends a message retrieval command to the web server every predetermined time. After receiving the information such as the status change of the instant communication status server or receiving the instant message sent by the other party, the web server caches the message and waits for the browser. The user takes the instant message. If the browser user has not taken the information for more than the predetermined time, the browsing is considered The user has logged out, the web server clears the cache of the browser user, and notifies the other user that the browser user has logged out.

The present invention can realize file transfer between a browser user and an instant communication user. For example, FIG. 2 is a flowchart of a browser user transmitting a file to an instant communication user according to an embodiment of the present invention, and the implementation process thereof is as follows:

Step 200: The browser user selects an instant communication user, and clicks to send a file.

Step 201: The browser user sends a request to the web server to transfer the file to the instant communication user.

Step 202: The web server queries the instant communication status server for the server currently registered by the instant communication user, and queries whether it is online; if the result is yes, step 205 is performed; otherwise, steps 203 to 204 are performed.

Step 203: The web server caches the information that the instant communication user is not online, and waits for the browser user to retrieve the information.

Step 204: After the browser user obtains the information, cancel the sending of the file.

Step 205: The web server requests the file transfer server group to establish a file transfer dialog; the request includes the ID of the other party, and optional information such as the file name and the file size.

Step 206: The file transfer server group agrees to establish a dialog and returns information related to the dialog; the returned dialog information includes an IP address and port of the assigned file transfer server, and an acceptable protocol type (TCP or UDP or HTTP, etc.) And a string of unique Session ID and other information.

Step 207: The web server establishes a conversation connection with the allocated file transfer server according to the returned dialog information.

Step 208: The web server forwards the request information of the transfer file to the instant communication user through the instant messaging server; the request information includes the browser user and the web server information, the file name and size, the address and port of the file transfer server, and the file transfer server. Information such as acceptable protocols.

Step 209: After receiving the request of the browser user to transmit the file, the instant communication user determines to allow or refuse to receive the file; if yes, step 211 is performed; otherwise, step 210 is performed.

Step 210: The instant messaging user sends the information of the rejected file to the instant messaging server, and the instant messaging server forwards the information to the web server, where the information is cached. Waiting for the browser user to retrieve; jump to step 204.

Step 211: The instant messaging user sends a setup session connection request to the file transfer server according to the request information of the transfer file sent by the web server. The file transfer server verifies the instant communication according to the session ID and the instant communication user identifier and the IP address, as described in step 206. Whether the user information is legal, if the verification is passed, establish a conversation connection with the instant communication user.

Step 212: The instant messaging user sends the information of the received file to the instant messaging server, and the instant messaging server forwards the information to the web server, which caches the received information and waits for the browser user to retrieve it.

Step 213: After the browser user retrieves the information that the instant communication user is allowed to receive the file, the file is transmitted to the web server; the browser user sends the Http command to the web server, and the web server forwards the received part of the data to the file through step 214. The transport server; the web server begins to receive data from the body portion of the http protocol, and uses the method of receiving partial data for processing (eg, in units of 64 Kbytes) instead of receiving all data before processing.

Step 215: The file transfer server forwards the received file data to the instant messaging user until the file transfer is completed.

Please refer to FIG. 3, which is a flowchart of an instant messaging user transmitting a file to a browser user according to an embodiment of the present invention. The implementation process is as follows:

Step 300: The instant messaging user selects the browser user and clicks to send the file.

Step 301: The instant communication user sends a request to the instant messaging server to transmit the file to the browser user.

Step 302: The instant messaging server queries the server that the browser user is currently logged in through the instant messaging status server, and queries whether it is online. If the result is yes, step 305 is performed; otherwise, steps 303 to 304 are performed.

Step 303: The instant messaging server forwards the information that the browser user is not online to the instant communication corpse

Step 304: The instant messaging user cancels sending the file.

Step 305: The instant messaging user requests to establish a file transfer dialog to the file transfer server group. Step 306: The file transfer server group agrees to establish a dialogue and returns information related to the dialog; The returned dialog information includes the IP address and port of the assigned file transfer server, an acceptable protocol type (TCP or UDP or HTTP, etc.), and a string of unique session IDs.

Step 307: The instant messaging user establishes a conversation connection with the allocated file transmission server according to the returned conversation information.

Step 308: The instant messaging server forwards the request information for transmitting the file to the web server.

The web server caches the dialog information, and provides information of the file to be transmitted to the browser user. The information of the file to be transmitted includes information such as the user ID, the file name and size, and the URL of the file to be received by the browser user.

Step 309: After receiving the request of the instant communication user to transmit the file, the browser user determines to allow or refuse to receive the file; if yes, step 311 is performed; otherwise, step 310 is performed.

Step 310: The browser user sends the information of the rejected file to the web server, and the web server forwards the information to the instant messaging server, and forwards the information of the rejected file to the instant communication user; and the process proceeds to step 304.

Step 311: The web server sends a setup session connection request to the file transfer server according to the request information of the transfer file sent by the instant messaging server, and the file transfer server verifies the web server related information according to the session ID and the browser user identifier and the information described in step 306. If the verification is passed, a dialog connection is established with the web server.

Step 312: The browser user sends an Http get command to the web server, and forwards the information of the allowed file to the instant messaging server, and the instant messaging server forwards the received information to the instant communication user; the browser user and the web server remain persistent. connection.

Step 313: The instant messaging user transmits the file to the file transfer server.

Step 314: The file transfer server forwards the received file data to the web server. Step 315: The web server directly forwards the received file data to the browser user.

The invention can also implement file transfer between the browser user and the browser user. The process of file transfer is the same as the above, and the web server and the file transfer server where the user is located need to establish a file transfer link to implement file transfer. If the two browser users are in the same network domain, the file transfer between users can also be directly performed through the web server where the user is located. As shown in FIG. 4, the process of transferring files between two browser users in the same network domain is as follows:

Step 400: The browser user Ua selects the browser user Ub and clicks to send the file. Step 401: The browser user Ua sends a request to the web server A to transfer the file to the browser user Ub.

Step 402: The web server A queries the instant messaging status server for the server that the browser user Ub is currently logged in, and queries whether it is online. If the result is yes, step 405 is performed; otherwise, step 403 to step 404 are performed.

Step 403: The web server A caches the information that the browser user Ub is not online, and waits for the browser user Ua to retrieve it.

Step 404: After the browser user Ua obtains the information, cancel the sending of the file.

Step 405: The web server A provides a request for the browser user Ua to transfer the file to the browser user Ub through the web server B.

Step 406: After receiving the request for file transfer, the browser user B determines to allow or refuse to receive the file; if yes, step 408 is performed; otherwise, step 407 is performed.

Step 407: The browser user Ub sends the information of the rejected file to the web server B, and the web server B forwards the information to the web server A, which caches the received information and waits for the browser user Ua to retrieve it. Go to step 404.

Step 408: The browser user B provides the information for allowing the received file to the browser user Ua through the web server B and the web server A.

Step 409: The browser user Ua transmits the file to the web server A.

Step 410: The web server A transmits the file data sent by the browser user Ua to the web server B.

Step 411: The web server B forwards the received file data directly to the browser user Ub. During the file transfer process, if the user cancels the file transfer, the user provides the information for canceling the file transfer to the other party, prompting the file transfer to be interrupted. At this time, the user connected to the file transfer server or the user server where the user is located disconnects the file transfer session. Connect, and clear the original file transfer dialog, the file transfer is terminated. The process of canceling the file transfer between the browser user and the instant messaging user is the same. The following describes the process of canceling the file transfer by the instant messaging user. As shown in Figure 5, the main implementation process is as follows:

500, instant messaging users cancel file transfer.

501. The instant messaging user disconnects the conversation with the file transfer server. 502. After receiving the information of disconnecting the conversation, the file transfer server disconnects the conversation with the web server.

503. The web server caches the received information of the disconnected conversation, and waits for the browser user to retrieve it.

504. After the browser user retrieves the information, cancel the file transfer, and the file transfer is terminated. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

Rights request

A method for implementing file transfer by a browser, comprising the steps of: a source user requesting to transmit a file to a target user, at least one of the source user and the target user being a browser user;

Establishing a file transmission link between the source user and the target user by using a web server corresponding to the browser user;

The method for implementing file transfer by a browser according to claim 1, wherein the source user and the target user are browser users, and a file transmission chain is established by the web server where the source user is located and the web server where the target user is located. Or; establish a file transfer link through the web server where the source user is located, the file transfer server, and the web server where the target user is located.

The method for implementing file transfer by a browser according to claim 1, wherein the source user or the target user is an instant communication user, and is established by an instant communication user, a file transfer server, and a web server where the browser user is located. File transfer link.

The method for implementing file transfer by a browser according to any one of claims 1 to 3, further comprising:

Before transmitting the file, the browser user sends a login request; assigns a web server according to the information carried by the login request, and redirects the login request to the web server.

Query whether the target user is online before establishing the file transmission link;

If online, the corresponding file transfer link is established.

After the file transmission link is established, when the target user receives the file transfer request of the source user, it determines whether the file is allowed to be received, and if so, establishes a dialog connection for file transmission; otherwise, the feedback is rejected. Receiving information of the file to the source user.

7. The method for implementing file transfer by a browser according to claim 2 or 3, wherein the step of establishing a file transfer link by the file transfer server comprises the steps of: The file transfer server receives a setup file transfer dialog request sent by the source user side; and establishes a file transfer dialog between the source user side and the allocated file transfer server according to the returned dialog information;

Sending a file transfer request carrying file transfer related information to the target user side; the file transfer server establishes a file transfer session with the target user side.

8. The method for implementing file transfer by a browser according to claim 7, wherein the file transfer dialog request carries a counterpart user identifier, a file name, and a size.

The method for implementing file transfer by a browser according to claim 7, wherein the dialog information includes an IP address and port of the file transfer server, an acceptable protocol type, and a dialog identifier.

The method for implementing file transfer by a browser according to claim 7, wherein in the file transfer process, when the source user or the target user cancels transferring the file, releasing the file transmission link and related resources .

11. A file transfer system, comprising:

At least two user equipments for transmitting and receiving files, at least one of which is a user equipment provided with a browser;

12. The file transfer system of claim 11, wherein one of the user devices is an instant messaging user device, the system further comprising:

Status information of the server and user of the user recorded according to the instant messaging status server.

The file transfer system according to claim 11, wherein one of the user devices is an instant messaging user device, and the system further includes:

An instant messaging server is coupled to the instant messaging user device for interacting with the web server to forward an instant message between the user devices.

14. The document delivery system of claim 11, 12 or 13 further characterized by Includes:

The file transfer system of claim 11, 12 or 13, further comprising:

The file transfer system according to claim 15, further comprising: a distribution server, configured to allocate a web server to a user device that sends a login request connected to the web server, and redirect the login request to The web server.