CN105763601A - File sharing method and device - Google Patents

Abstract

The present disclosure provides a file sharing method and device. The method includes: after receiving a file sharing request carrying a download link, asking the user whether to agree to download the target file pointed to by the download link to the routing device; When agreeing to download the target file to the routing device, generate a file download request carrying the download link; send the file download request to the routing device, so that the routing device requests the target file from the server corresponding to the download link ; When the local and the routing device are in the same network, receiving the target file pushed by the routing device. It can be seen that the disclosure can choose to download the file to the routing device when the terminal device is inconvenient to receive the file, and when the terminal device and the routing device are in the same network, the terminal device can directly obtain the file from the routing device, thereby improving It improves the convenience and practicality of sharing files.

Description

File sharing method and device

technical field

The present disclosure relates to the field of communication technologies, and in particular to a file sharing method and device.

Background technique

With the rapid development of network technology, the functions of network applications are becoming more and more abundant. Taking social applications as an example, users can share pictures, text or audio and video files on the network with other users through social applications in terminal devices. In the related art, when the terminal device is inconvenient to receive the shared file, the file sharing fails, and the practicability is poor.

Contents of the invention

In order to solve the above problems, the present disclosure provides a file sharing method and device.

Specifically, the present disclosure is achieved through the following technical solutions:

According to a first aspect of an embodiment of the present disclosure, a file sharing method is provided, the method comprising:

After receiving the file sharing request carrying the download link, ask the user whether to agree to download the target file pointed to by the download link to the routing device;

When confirming that the user agrees to download the target file to the routing device, generate a file download request carrying the download link;

sending the file download request to a routing device, so that the routing device requests a target file from a server corresponding to the download link;

When the local area and the routing device are in the same network, the target file pushed by the routing device is received.

In one embodiment, before the user is asked whether to agree to download the target file pointed to by the download link to the routing device, it also includes:

judging whether the target file meets a preset inquiry condition;

When the target file meets the preset query condition, perform a step of asking the user whether to agree to download the target file pointed to by the download link to the routing device.

In one embodiment, the judging whether the target file meets a preset query condition includes:

Determine whether the local area is connected to the wireless network;

When the local area is not connected to the wireless network, it is judged whether the file size of the target file exceeds the preset file size, and if it exceeds, it meets the preset query condition.

In an embodiment, the sending the file download request to the routing device includes:

Detect whether there is a routing device bound;

When a routing device is bound, the file download request is sent to the bound routing device.

In one embodiment, the method also includes:

When the routing device is not bound, display the routing device login page, wherein the page is used to provide the user with an interface for inputting account associated information;

Receive account association information input by the user, so that the server authenticates the account corresponding to the account association information;

When the authentication is successful, display the associated routing device under the account;

receiving a routing device selection operation input by the user, and determining the routing device selected by the user according to the selection operation;

The sending the file download request to the routing device includes:

Send the file download request to the routing device selected by the user.

According to a second aspect of an embodiment of the present disclosure, a file sharing method is provided, the method comprising:

Receive a file download request with a download link sent by the terminal device;

requesting the target file pointed to by the download link from the server;

Receive the target file sent by the server;

When the local area and the terminal device are in the same network, push the target file to the terminal device.

In one embodiment, after receiving the target file sent by the server, it further includes:

Generates a download link to the target file within the routing device.

According to a third aspect of the embodiments of the present disclosure, there is provided a file sharing device, the device comprising:

The inquiry module is configured to, after receiving the file sharing request carrying the download link, ask the user whether to agree to download the target file pointed to by the download link to the routing device;

The request generation module is configured to generate a file download request carrying the download link when it is confirmed that the user agrees to download the target file to the routing device;

A sending module configured to send the file download request to a routing device, so that the routing device requests a target file from a server corresponding to the download link;

The file receiving module is configured to receive the target file pushed by the routing device when the local area and the routing device are in the same network.

In one embodiment, the device also includes:

The judging module is configured to judge whether the target file meets the preset inquiry condition, and when the judgment result is yes, trigger the inquiry module to execute asking whether the user agrees to download the target file pointed to by the download link to the router device action.

In one embodiment, the judgment module includes:

The first judging submodule is configured to judge whether the local area is connected to the wireless network;

The second judging submodule is configured to judge whether the file size of the target file exceeds the preset file size when the local area is not connected to the wireless network, and if so, it meets the preset query condition.

In one embodiment, the sending module includes:

The detection sub-module is configured to detect whether a routing device is bound;

The first sending submodule is configured to send the file download request to the bound routing device when the detection result of the detection submodule is yes.

In one embodiment, the device also includes:

The first display submodule is configured to display a routing device login page when the detection result of the detection submodule is negative, wherein the page is used to provide an interface for the user to input account association information;

The authentication submodule is configured to receive account association information input by the user, so that the server authenticates the account corresponding to the account association information;

The second display submodule is configured to display the associated routing device under the account when the authentication is successful;

The device determination submodule is configured to receive a routing device selection operation input by the user, and determine the routing device selected by the user according to the selection operation;

The second sending submodule is configured to send the file download request to the routing device selected by the user.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a file sharing device, the device comprising:

The request receiving module is configured to receive a file download request carrying a download link sent by the terminal device;

The file download module is configured to request the target file pointed to by the download link from the server, and receive the target file sent by the server;

The push module is configured to push the target file to the terminal device when the local terminal is in the same network as the terminal device.

In one embodiment, the device also includes:

The link generation module is configured to generate a download link pointing to the target file in the routing device.

According to a fifth aspect of the embodiments of the present disclosure, a file sharing device is provided, including:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured as:

After receiving the file sharing request carrying the download link, ask the user whether to agree to download the target file pointed to by the download link to the routing device;

When confirming that the user agrees to download the target file to the routing device, generate a file download request carrying the download link;

sending the file download request to a routing device, so that the routing device requests a target file from a server corresponding to the download link;

When the local area and the routing device are in the same network, the target file pushed by the routing device is received.

According to a sixth aspect of the embodiments of the present disclosure, a file sharing device is provided, including:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured as:

Receive a file download request with a download link sent by the terminal device;

requesting the target file pointed to by the download link from the server;

Receive the target file sent by the server;

When the local area and the terminal device are in the same network, push the target file to the terminal device.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

This embodiment can choose to download the file to the routing device when the terminal device is inconvenient to receive the file. When the terminal device and the routing device are in the same network, the terminal device can directly obtain the file from the routing device, thereby improving file sharing. convenience and practicality.

This embodiment can combine the network situation of the terminal device and the information of the target file to detect whether the terminal device is convenient to receive the above-mentioned target file. When the devices are in the same network, the terminal device can directly obtain the file from the routing device, thereby improving the convenience and practicality of file sharing.

Considering that using traffic to download files consumes more traffic, and the larger the downloaded file, the more traffic will be consumed. Therefore, when the smart device is connected to the wireless network and the file is large, this embodiment can suggest The user completes the download of the file through the routing device to avoid a large amount of traffic charges.

This embodiment can download the file to the routing device when the terminal device is inconvenient to receive the file, and when the terminal device and the routing device are in the same network, directly push the file to the terminal device, thereby improving the convenience and practicability of sharing files .

This embodiment can generate a download link pointing to a file in the routing device, so that the user can share the download link pointing to the file in the routing device to other users through a client bound to the routing device.

It is to be understood that both the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description serve to explain the principles of the invention.

Fig. 1 is a schematic diagram of an application scenario of a file sharing method according to an exemplary embodiment of the present disclosure;

Fig. 2 is a flow chart of a file sharing method according to an exemplary embodiment of the present disclosure;

Fig. 3 is a flowchart of another file sharing method according to an exemplary embodiment of the present disclosure;

Fig. 4(a) is an example diagram of a login page of a routing device according to an exemplary embodiment of the present disclosure;

Fig. 4(b) is an example diagram showing a routing device selection page according to an exemplary embodiment of the present disclosure;

Fig. 5 is a flowchart of another file sharing method according to an exemplary embodiment of the present disclosure;

Fig. 6 is a block diagram of a file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 7 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 8 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 9 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 10 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 11 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 12 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure;

Fig. 13 is a schematic structural diagram of a file sharing device according to an exemplary embodiment of the present disclosure.

detailed description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present disclosure as recited in the appended claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only, and is not intended to limit the present disclosure. As used in this disclosure and the appended claims, the singular forms "a", "the", and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in the present disclosure to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of the present disclosure, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination."

With the rapid development of network technology, the functions of network applications are becoming more and more abundant. Taking social applications as an example, users can share pictures, text or audio and video files on the network with other users through social applications in terminal devices. In the related art, when the terminal device is inconvenient to receive the shared file, the file sharing fails, and the practicability is poor. In order to solve the above problems, the present disclosure provides a file sharing method and device.

For ease of understanding, the technical solution provided by the present disclosure will be introduced below firstly in combination with the exemplary application scenario diagram provided by the embodiments of the present disclosure.

As shown in FIG. 1, FIG. 1 is a schematic diagram of an application scenario of a file sharing method according to an exemplary embodiment of the present disclosure. The application scenario includes: a terminal device and a routing device, wherein the terminal device may include : a smart phone, a tablet computer, a personal digital assistant, etc., the routing device may include: a router, which is not limited in the present disclosure.

Next, the file sharing method applied to the terminal device side provided by the present disclosure will be introduced.

As shown in FIG. 2, FIG. 2 is a flow chart of a file sharing method according to an exemplary embodiment of the present disclosure. The method can be executed by a client, which is an application software installed on a terminal device. The method may include the steps of:

In step 201, after receiving a file sharing request carrying a download link, the user is asked whether to agree to download the target file pointed to by the download link to the routing device.

In this embodiment, after receiving the file sharing request carrying the download link, the user may be directly asked whether to agree to download the target file pointed to by the download link to the routing device.

It should be noted that the sender and receiver of the file sharing request in this embodiment can be the same terminal device or different terminal devices. The file sharing request is sent to the client B installed in the smart phone, or two smart phones send the file sharing request carrying the download link through the same client.

In practical applications, you can ask the user whether to agree to download the target file pointed to by the download link to the routing device through a pop-up window, or ask the user whether to agree to download the target file pointed to by the download link to the routing device through a voice prompt , which is not limited in this embodiment.

In step 202, when it is confirmed that the user agrees to download the target file to the routing device, a file download request carrying a download link is generated.

For example, after smart phone A receives the video sharing link sent by smart phone B, smart phone A can ask the user whether to agree to download the video file corresponding to the link to the router, that is, the router will complete the download of the video file. When agreeing to download the above video file by the router, the smart phone A may generate a file download request carrying: a download link pointing to the above video file.

In step 203, the file download request is sent to the routing device, so that the routing device requests the target file from the server corresponding to the download link.

Continuing from the previous example, after generating the above-mentioned file download request, smart phone A sends the above-mentioned file download request to the above-mentioned router, so that after receiving the above-mentioned file download request, the router can go to the download link carried in the above-mentioned file download request to obtain the above video file.

In step 204, when the local area and the routing device are in the same network, the target file pushed by the routing device is received.

It can be understood that the data transmission speed between two electronic devices in the same local area network is usually very fast. Based on the above situation, when the terminal device and the routing device are in the same network, the terminal device in this embodiment can actively Request the routing device to obtain the downloaded file of the routing device. Alternatively, the routing device in this embodiment may directly push the locally downloaded file to the terminal device, which is not limited in this embodiment.

It can be seen from the above embodiment that in this embodiment, when the terminal device is inconvenient to receive the file, it can choose to download the file to the routing device, and when the terminal device and the routing device are in the same network, the terminal device can directly obtain the file from the routing device , thus improving the convenience and practicality of sharing files.

As shown in FIG. 3, FIG. 3 is a flowchart of another file sharing method according to an exemplary embodiment of the present disclosure. When the terminal device is inconvenient to receive files due to file size or traffic restrictions, the method may include The following steps:

In step 300, after receiving the file sharing request carrying the download link, it is judged whether the target file pointed to by the download link meets the preset inquiry condition, and if yes, step 301 is executed.

It can be understood that, when the file is large or the traffic of the terminal device is insufficient, it is usually inconvenient for the terminal device to receive the file. In view of the above situation, the terminal device in this embodiment can combine the local According to the network conditions and the information of the target file, it is decided whether to advise the user: the downloading of the target file is completed by the routing device.

Correspondingly, in a possible implementation manner, the above step 300 may include:

Determine whether the local area is connected to the wireless network;

When the local area is not connected to the wireless network, it is judged whether the file size of the target file exceeds the preset file size, and if it exceeds, the preset inquiry condition is met.

For example, after a smart phone receives a file sharing request sent by other smart devices, it can first determine whether the local WiFi is connected. The value of the preset file size determines whether the file to be downloaded is very large), if it is larger, it is recommended that the user: complete the download of the target file by the routing device.

Considering that using traffic to download files consumes more traffic, and the larger the downloaded file, the more traffic will be consumed. Therefore, when the smart device is connected to the wireless network and the file is large, this embodiment can suggest The user completes the download of the file through the routing device to avoid a large amount of traffic charges.

In step 301, the user is asked whether to agree to download the target file to the routing device.

In step 302, when it is confirmed that the user agrees to download the target file to the routing device, a file download request carrying a download link is generated.

Step 301 and step 302 in this embodiment are similar to step 201 and step 202 in the embodiment shown in FIG. 2 , which will not be repeated in this embodiment.

In step 303, the file download request is sent to the routing device, so that the routing device requests the target file from the server corresponding to the download link.

In a possible implementation manner, the above step 303 may include:

Detect whether the client in the terminal device is bound with a routing device, that is, detect whether the above-mentioned client is bound with the routing device in advance, and if the routing device is pre-bound, send the file download request to the bound routing device .

Considering that some users do not want to bind the client in the terminal device with the routing device, in view of the above situation, this embodiment may also include the following steps:

S1. When not bound to the routing device, display the routing device login page, where the page is used to provide the user with an interface for inputting account association information.

In this embodiment, when the terminal device detects that the client is not bound to any router, it can generate a link pointing to the route login web page, and then jump to the route login web page corresponding to the link automatically or triggered by the user page, where the user can enter the account associated information for login.

S2. Receive account association information input by the user, so that the server authenticates the account corresponding to the account association information.

S3, when the authentication is successful, display the associated routing device under the account.

S4. Receive a routing device selection operation input by the user, determine the routing device selected by the user according to the selection operation, and send a file download request to the routing device selected by the user.

For ease of understanding, the above S1-S4 will be introduced below in conjunction with FIG. 4(a) and FIG. 4(b). Figure 4(a) is the login page of the routing device. After the user enters the account number and password on the page, the user can click the "Confirm" button for authentication. When the authentication is successful, the terminal device jumps to the routing device display page shown in Figure 4(b), and the user can select the routing device for downloading files by clicking on the routing device name.

In another possible implementation, the above step 303 may not perform any detection operation, directly display and display the login page of the routing device, receive the account association information input by the user, and when the server authenticates the account successfully, display the information under the account. The associated routing device receives the routing device selection operation input by the user, determines the routing device selected by the user according to the selection operation, and sends the file download request to the routing device selected by the user, so that the user can directly select the routing device independently. This embodiment does not limit the implementation manner of the foregoing step 303 .

In step 304, when the local area and the routing device are in the same network, the target file pushed by the routing device is received.

It can be seen from the above embodiment that this embodiment can combine the network conditions of the terminal device and the information of the target file to detect whether the terminal device is convenient to receive the above target file, and when the terminal device is inconvenient to receive the above file, choose to download the file to the routing device , when the terminal device and the routing device are in the same network, the terminal device can directly obtain the file from the routing device, thereby improving the convenience and practicability of file sharing.

Corresponding to the method applied to the terminal device side shown in FIG. 2 , the present disclosure also provides a file sharing method applied to the routing device side, which will be introduced below.

As shown in FIG. 5, FIG. 5 is a flowchart of another file sharing method according to an exemplary embodiment of the present disclosure, which is applied to a routing device. The method may include the following steps:

In step 501, a file download request carrying a download link sent by a terminal device is received.

In step 502, the server is requested to download the target file pointed to by the link.

In step 503, the target file sent by the server is received.

In step 504, when the local terminal and the terminal device are in the same network, push the target file to the terminal device.

It can be seen from the above-mentioned embodiment that this embodiment can download the file to the routing device when the terminal device is inconvenient to receive the file, and when the terminal device and the routing device are in the same network, directly push the file to the terminal device, thereby improving file sharing. convenience and practicality.

In another embodiment of the present disclosure, the file sharing method provided in this embodiment may further add the following steps on the basis of the embodiment shown in FIG. 5 :

Generates a download link to the target file within the routing device.

It can be seen from the above embodiment that this embodiment can generate a download link pointing to the file in the routing device, so that the user can share the download link pointing to the file in the routing device with other users through the client bound to the routing device.

Corresponding to the foregoing embodiment of the method shown in FIG. 2 , the present disclosure also provides an embodiment of a file sharing apparatus applied to a terminal device side.

As shown in FIG. 6, FIG. 6 is a block diagram of a file sharing device according to an exemplary embodiment of the present disclosure, and the device may include:

The inquiry module 610 is configured to, after receiving the file sharing request carrying the download link, ask the user whether to agree to download the target file pointed to by the download link to the routing device;

The request generating module 620 is configured to generate a file download request carrying the download link when it is confirmed that the user agrees to download the target file to the routing device;

The sending module 630 is configured to send the file download request to the routing device, so that the routing device requests the target file from the server corresponding to the download link;

The file receiving module 640 is configured to receive the target file pushed by the routing device when the local area is in the same network as the routing device.

It can be seen from the above embodiment that in this embodiment, when the terminal device is inconvenient to receive the file, it can choose to download the file to the routing device, and when the terminal device and the routing device are in the same network, the terminal device can directly obtain the file from the routing device , thus improving the convenience and practicality of sharing files.

As shown in FIG. 7, FIG. 7 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure. This embodiment may be based on the embodiment shown in FIG. 6, and the device may further include:

The judging module 710 is configured to judge whether the target file meets the preset query condition, and when the judgment result is yes, trigger the query module to execute asking whether the user agrees to download the target file pointed to by the download link to The action of the routing device.

As shown in FIG. 8, FIG. 8 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure. This embodiment may be based on the embodiment shown in FIG. 7, and the judging module 710 may be include:

The first judging submodule 711 is configured to judge whether the local area is connected to the wireless network;

The second judging sub-module 712 is configured to judge whether the file size of the target file exceeds the preset file size when the local area is not connected to the wireless network, and if so, it meets the preset query condition.

As shown in FIG. 9 , FIG. 9 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure. This embodiment can be based on any of the embodiments shown in FIGS. 6 to 8 . The sending module 630 may include:

The detection submodule 631 is configured to detect whether a routing device is bound;

The first sending submodule 632 is configured to send the file download request to the bound routing device if the detection result of the detection submodule 631 is yes.

As shown in FIG. 10, FIG. 10 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure. This embodiment may be based on the embodiment shown in FIG. 9, and the device may further include:

The first display submodule 633 is configured to display a routing device login page when the detection result of the detection submodule 631 is negative, wherein the page is used to provide the user with an interface for inputting account association information;

The authentication module 634 is configured to receive the account associated information input by the user, so that the server authenticates the account corresponding to the account associated information;

The second display submodule 635 is configured to display the associated routing device under the account when the authentication is successful;

The device determination submodule 636 is configured to receive a routing device selection operation input by the user, and determine the routing device selected by the user according to the selection operation;

The second sending submodule 637 is configured to send the file download request to the routing device selected by the user.

Corresponding to the aforementioned embodiment of the method shown in FIG. 5 , the present disclosure also provides an embodiment of a file sharing apparatus applied to the routing device side.

As shown in FIG. 11, FIG. 11 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure, and the device may include:

The request receiving module 1010 is configured to receive a file download request carrying a download link sent by the terminal device;

The file download module 1020 is configured to request the target file pointed to by the download link from the server, and receive the target file sent by the server;

The push module 1030 is configured to push the target file to the terminal device when the local terminal is in the same network as the terminal device.

It can be seen from the above-mentioned embodiment that this embodiment can download the file to the routing device when the terminal device is inconvenient to receive the file, and when the terminal device and the routing device are in the same network, directly push the file to the terminal device, thereby improving file sharing. convenience and practicality.

As shown in FIG. 12, FIG. 12 is a block diagram of another file sharing device according to an exemplary embodiment of the present disclosure. This embodiment may be based on the embodiment shown in FIG. 11, and the device may further include:

The link generation module 1040 is configured to generate a download link pointing to the target file in the routing device.

For the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method for details, and will not be repeated here.

As for the device embodiment, since it basically corresponds to the method embodiment, for related parts, please refer to the part description of the method embodiment. The device embodiments described above are only illustrative, and the modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution. It can be understood and implemented by those skilled in the art without creative effort.

Correspondingly, the present disclosure also provides a file sharing device, including: a processor; a memory for storing processor-executable instructions; wherein, the processor is configured to: After the request, ask whether the user agrees to download the target file pointed to by the download link to the routing device; when it is confirmed that the user agrees to download the target file to the routing device, generate a file download request that carries the download link; The file download request is sent to the routing device, so that the routing device requests the target file from the server corresponding to the download link; when the local area is in the same network as the routing device, the target file pushed by the routing device is received.

Correspondingly, the present disclosure also provides a file sharing device, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to: receive a download link sent by a terminal device A file download request; requesting the target file pointed to by the download link from the server; receiving the target file sent by the server; and pushing the target file to the terminal device when the local area is in the same network as the terminal device.

As shown in FIG. 13 , FIG. 13 is a schematic structural diagram of an apparatus 1300 for file sharing according to an exemplary embodiment of the present disclosure. For example, the apparatus 1300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, an aircraft, and the like.

13, device 1300 may include one or more of the following components: processing component 1302, memory 1304, power supply component 1306, multimedia component 1308, audio component 1310, input/output (I/O) interface 1312, sensor component 1314, and communication component 1316.

The processing component 1302 generally controls the overall operations of the device 1300, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 1302 may include one or more processors 1320 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 1302 may include one or more modules that facilitate interaction between processing component 1302 and other components. For example, processing component 1302 may include a multimedia module to facilitate interaction between multimedia component 1308 and processing component 1302 .

The memory 1304 is configured to store various types of data to support operations at the device 1300 . Examples of such data include instructions for any application or method operating on device 1300, contact data, phonebook data, messages, pictures, videos, and the like. The memory 1304 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

Power component 1306 provides power to various components of device 1300 . Power components 1306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 1300 .

The multimedia component 1308 includes a screen that provides an output interface between the device 1300 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or a swipe action, but also detect duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 1308 includes a front camera and/or a rear camera. When the device 1300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 1310 is configured to output and/or input audio signals. For example, the audio component 1310 includes a microphone (MIC), which is configured to receive external audio signals when the device 1300 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 1304 or sent via communication component 1316 . In some embodiments, the audio component 1310 also includes a speaker for outputting audio signals.

The I/O interface 1312 provides an interface between the processing component 1302 and a peripheral interface module. The peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 1314 includes one or more sensors for providing various aspects of status assessment for device 1300 . For example, the sensor component 1314 can detect the open/closed state of the device 1300, the relative positioning of components, such as the display and keypad of the device 1300, and the sensor component 1314 can also detect a change in the position of the device 1300 or a component of the device 1300 , the presence or absence of user contact with the device 600 , the device 1300 orientation or acceleration/deceleration and the temperature change of the device 1300 . Sensor assembly 1314 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 1314 may also include optical sensors, such as CMOS or CCD image sensors, for use in imaging applications. In some embodiments, the sensor component 1314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 1316 is configured to facilitate wired or wireless communication between the apparatus 1300 and other devices. The device 1300 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1316 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1316 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 1300 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 1304 including instructions, which can be executed by the processor 1320 of the device 1300 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (16)

1. a sharing files method, it is characterised in that described method includes:

After receiving the sharing files request carrying download link, ask the user whether to agree to the file destination pointed by described download link is downloaded to routing device；

When confirming that user agrees to that file destination is downloaded to routing device, generate the file download request carrying described download link；

The request of described file download is sent to routing device, so that described routing device is to server request file destination corresponding to described download link；

When local and described routing device is in consolidated network, receive the file destination that described routing device pushes.

2. method according to claim 1, it is characterised in that described ask the user whether to agree to the file destination pointed by described download link is downloaded to routing device before, also include:

Judge whether described file destination meets default query condition；

When described file destination meets default query condition, perform the step asking the user whether to agree to that the file destination pointed by described download link is downloaded to routing device.

3. method according to claim 2, it is characterised in that described judge whether described file destination meets default query condition, including:

Judge whether this locality accesses wireless network；

When wireless network is not accessed in this locality, it is judged that whether the file size of described file destination exceedes default file size, if it does, then meet default query condition.

4. method according to claim 1, it is characterised in that described by described file download request be sent to routing device, including:

Detect whether that binding has routing device；

When binding has routing device, the request of described file download is sent to the routing device bound.

5. method according to claim 4, it is characterised in that described method also includes:

When unbound routing device, showing routing device login page, wherein, the described page is for providing the user the interface of input account relating information；

Receive the account relating information of user's input, so that the account that described account relating information is corresponding is authenticated by server；

Upon successful authentication, the routing device associated under described account is shown；

The routing device receiving user's input selects operation, selects operation to determine the routing device that user selects according to described；

The request of described file download is sent to the routing device that user selects.

6. a sharing files method, it is characterised in that described method includes:

What receiving terminal apparatus sent carries the file download request of download link；

To the file destination pointed by download link described in server request；

Receive the file destination that server sends；

When local and described terminal unit is in consolidated network, push described file destination to described terminal unit.

7. method according to claim 1, it is characterised in that after the file destination that described reception server sends, also include:

Generate the download link pointing to routing device internal object file.

8. a sharing files device, it is characterised in that described device includes:

Inquiry module, is configured to, after receiving the sharing files request carrying download link, ask the user whether to agree to the file destination pointed by described download link is downloaded to routing device；

Request generation module, is configured as confirming when user agrees to that file destination is downloaded to routing device, generates the file download request carrying described download link；

Sending module, is configured to the request of described file download is sent to routing device, so that described routing device is to server request file destination corresponding to described download link；

File reception module, is configured as local and described routing device when being in consolidated network, receives the file destination that described routing device pushes.

9. device according to claim 8, it is characterised in that described device also includes:

Judge module, it is configured to judge whether described file destination meets default query condition, and when judged result is for being, trigger the action that described inquiry module performs to ask the user whether to agree to that the file destination pointed by described download link downloads to routing device.

10. device according to claim 9, it is characterised in that described judge module, including:

First judges submodule, is configured to judge whether this locality accesses wireless network；

Second judges submodule, is configured as this locality when not accessing wireless network, it is judged that whether the file size of described file destination exceedes default file size, if it does, then meet default query condition.

11. according to the device described in right 8, it is characterised in that described sending module, including:

Detection sub-module, is configured to detect whether that binding has routing device；

First sends submodule, is configured to when the testing result of described detection sub-module is for being, the request of described file download is sent to the routing device bound.

12. device according to claim 11, it is characterised in that described device also includes:

First shows submodule, is configured to when the testing result of described detection sub-module is no, shows routing device login page, and wherein, the described page is for providing the user the interface of input account relating information；

Authentication submodule, is configured to receive the account relating information of user's input, so that the account that described account relating information is corresponding is authenticated by server；

Second shows submodule, is configured to upon successful authentication, shows the routing device associated under described account；

Equipment determines submodule, and the routing device being configured to receive user's input selects operation, selects operation to determine the routing device that user selects according to described；

Second sends submodule, is configured to the request of described file download is sent to the routing device that user selects.

13. a sharing files device, it is characterised in that described device includes:

Request receiver module, is configured to the file download request carrying download link that receiving terminal apparatus sends；

File download module, is configured to, to the file destination pointed by download link described in server request, receive the file destination that server sends；

Pushing module, is configured as local and described terminal unit when being in consolidated network, pushes described file destination to described terminal unit.

14. device according to claim 13, it is characterised in that described device also includes:

Link generation module, is configurable to generate the download link pointing to routing device internal object file.

15. a sharing files device, it is characterised in that including:

Processor；

For storing the memorizer of processor executable；

Wherein, described processor is configured to:

After receiving the sharing files request carrying download link, ask the user whether to agree to the file destination pointed by described download link is downloaded to routing device；

When confirming that user agrees to that file destination is downloaded to routing device, generate the file download request carrying described download link；

The request of described file download is sent to routing device, so that described routing device is to server request file destination corresponding to described download link；

When local and described routing device is in consolidated network, receive the file destination that described routing device pushes.

16. a sharing files device, it is characterised in that including:

Processor；

For storing the memorizer of processor executable；

Wherein, described processor is configured to:

What receiving terminal apparatus sent carries the file download request of download link；

To the file destination pointed by download link described in server request；

Receive the file destination that server sends；

When local and described terminal unit is in consolidated network, push described file destination to described terminal unit.