WO2022214085A1 - 文件传输方法、云端服务器、客户端以及雾节点路由器 - Google Patents

文件传输方法、云端服务器、客户端以及雾节点路由器 Download PDF

Info

Publication number
WO2022214085A1
WO2022214085A1 PCT/CN2022/085914 CN2022085914W WO2022214085A1 WO 2022214085 A1 WO2022214085 A1 WO 2022214085A1 CN 2022085914 W CN2022085914 W CN 2022085914W WO 2022214085 A1 WO2022214085 A1 WO 2022214085A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
client
fog node
target
request
Prior art date
Application number
PCT/CN2022/085914
Other languages
English (en)
French (fr)
Inventor
刘禹瑄
Original Assignee
北京汇钧科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京汇钧科技有限公司 filed Critical 北京汇钧科技有限公司
Publication of WO2022214085A1 publication Critical patent/WO2022214085A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a file transmission method, a cloud server, a client, and a fog node router.
  • an electronic device such as a mobile phone is in an external network environment such as a 4G (The 4th Generation mobile communication technology, fourth generation mobile communication technology) network or a non-local network
  • the external network is usually provided for the electronic device through a transit service.
  • the electronic device obtains data from the source data server through the relay server.
  • the cost of data transfer is very high.
  • the rate, size or type of file transfer is usually artificially limited, which leads to electronic devices. Low file transfer rates, limited file size or type when downloading or storing are prone to issues.
  • the present application aims to solve one of the technical problems in the related art at least to a certain extent.
  • the present application proposes a file transmission method, cloud server, client, fog node router, file transmission system, electronic equipment and storage medium, so as to solve the problem of easy storage and download services on the external network provided by a relay server for electronic equipment in the related art.
  • An embodiment of the first aspect of the present application proposes a file transfer method, including: a cloud server receiving a file transfer request sent by a client, wherein the file transfer request carries an identifier of the client; the cloud server according to the file
  • the transmission request determines the target fog node router, and sends a connection request to the target fog node router, wherein the connection request carries the identifier of the client, so that the target fog node router can communicate with the target fog node router according to the identifier of the client.
  • the client establishes a file transfer connection, and performs file transfer through the file transfer connection.
  • An embodiment of the second aspect of the present application proposes another file transfer method, including: a client sends a file transfer request to a cloud server, so that the cloud server determines a target fog node router according to the file transfer request, and sends a request to the cloud server.
  • the target fog node router sends a connection request, wherein the file transfer request and the connection request carry the identifier of the client; after the client establishes a file transfer connection with the target fog node router according to the identifier of the client , and file transfer is performed through the file transfer connection.
  • the embodiment of the third aspect of the present application proposes another file transmission method, which includes: a fog node router receives a connection request sent by a cloud server, wherein the connection request is sent by the cloud server to the cloud server after receiving the client After the sent file transfer request is sent to the fog node router, the file transfer request and the connection request carry the identifier of the client; the fog node router establishes a relationship with the client according to the identifier of the client. A file transfer connection; the fog node router and the client perform file transfer through the file transfer connection.
  • An embodiment of the fourth aspect of the present application provides a cloud server, including: a receiving module configured to receive a file transfer request sent by a client, wherein the file transfer request carries an identifier of the client; a first determining module, configured with determining the target fog node router according to the file transfer request, and sending a connection request to the target fog node router, wherein the connection request carries the identifier of the client, so that the target fog node router according to the client
  • the identifier of the terminal establishes a file transfer connection with the client, and performs file transfer through the file transfer connection.
  • the embodiment of the fifth aspect of the present application proposes a client, including: a sending module, configured to send a file transfer request to a cloud server, so that the cloud server determines a target fog node router according to the file transfer request, and sends the request to the cloud server.
  • the target fog node router sends a connection request, wherein the file transfer request and the connection request carry the identifier of the client; the first transmission module is configured to communicate with the target at the client according to the identifier of the client After the fog node router establishes the file transfer connection, the file transfer is performed through the file transfer connection.
  • the embodiment of the sixth aspect of the present application proposes a fog node router, including: a receiving module, configured to receive a connection request sent by a cloud server, wherein the connection request is when the cloud server receives a request from a client to the cloud After the file transfer request sent by the server is sent to the fog node router, the file transfer request and the connection request carry the identifier of the client; the establishment module is configured to communicate with the client according to the identifier of the client A file transfer connection is established; a transfer module is configured to perform file transfer with the client through the file transfer connection.
  • An embodiment of the seventh aspect of the present application proposes a file transfer system, including a client, a cloud server, and a plurality of fog node routers; wherein the cloud server is configured to receive a file transfer request sent by the client, and according to the The file transfer request determines a target fog node router among the multiple fog node routers, and sends a connection request to the target fog node router, wherein the file transfer request and the connection request carry the identifier of the client
  • the target fog node router is used to establish a file transfer connection with the client according to the identifier of the client after receiving the connection request, and perform file transfer with the client through the file transfer connection.
  • transmission the client is configured to send the file transmission request to the cloud server, and perform file transmission with the target fog node router through the file transmission connection.
  • An embodiment of an eighth aspect of the present application provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores data that can be executed by the at least one processor The instruction is executed by the at least one processor, so that the at least one processor can execute the file transfer method proposed by the first aspect embodiment or the second aspect embodiment or the third aspect embodiment of the present application .
  • An embodiment of the ninth aspect of the present application provides a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to cause the computer to execute the embodiment of the first aspect or the second aspect of the present application or The file transmission method proposed by the embodiment of the third aspect.
  • An embodiment of the tenth aspect of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the first aspect of the present application, the second aspect, or the third aspect.
  • the proposed file transfer method is a computer program product, including a computer program, which, when executed by a processor, implements the first aspect of the present application, the second aspect, or the third aspect.
  • the present application realizes the file transfer between the client and the target fog node router through the file transfer connection between the two, so that the file transfer service of the external network can be provided for the client without data transfer, and when the file is transferred, It makes full use of the network bandwidth of the fog node router, improves the rate of file transfer, and does not limit the type and size of files to be transferred, which improves the user experience.
  • FIG. 1 is a schematic diagram of an application scenario of a file transmission method provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • FIG. 3 is another schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of determining a data type of a file in a file transmission method provided by an embodiment of the present application
  • FIG. 5 is an example diagram of determining the data type of a file in the file transmission method provided by the embodiment of the present application.
  • FIG. 6 is an example diagram of a communication mode between a cloud server and a fog node router, between a plurality of fog node routers, and between a fog node router and a local router according to an embodiment of the present application;
  • FIG. 7 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • FIG. 8 is another schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • FIG. 9 is another schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • FIG. 10 is another schematic flowchart of the file transmission method provided by the embodiment of the present application.
  • FIG. 11 is another schematic flowchart of the file transmission method provided by the embodiment of the application.
  • FIG. 12 is an exemplary diagram of a file transmission method provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a cloud server provided by an embodiment of the present application.
  • FIG. 14 is another schematic structural diagram of a cloud server provided by an embodiment of the present application.
  • 15 is a schematic structural diagram of a client provided by an embodiment of the present application.
  • 16 is a schematic structural diagram of a fog node router provided by an embodiment of the present application.
  • Figure 17 shows a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present application.
  • This application mainly aims at the technical problem of low file transfer rate and limited file size or type when providing storage and download services on the external network through a transfer service in the related art, and proposes a method that can improve the file transfer rate without File transfer methods, cloud servers, clients, fog node routers, file transfer systems, electronic devices, storage media, and computer program products that limit the type and size of transferred files.
  • FIG. 1 is a schematic diagram of an application scenario of a file transmission method provided by an embodiment of the present application.
  • the mobile phone, computer and other clients used by the user such as A1, A2 and A3 in Figure 1, all correspond to a local router connected to it, and the cloud server C can pre-store the intranet address of each router and Internet address.
  • the cloud server C can pre-store the intranet address of each router and Internet address.
  • other routers with external network addresses other than the local router corresponding to the client may be used as fog node routers.
  • client A1 For client A1, other routers with external network addresses except the local router B1 corresponding to client A1 can be used as fog node routers.
  • client A2 Except for the local router B2 corresponding to the client A2, other routers with external network addresses may be used as fog node routers.
  • client A1 needs to transfer files, it can search for its corresponding local router B1 and try to connect with the local router B1. If the connection is successful, that is, the environment where client A1 is located at this time is the intranet environment, then the local router is used.
  • B1 provides file transfer service for client A1.
  • client A1 can send a file transfer request to cloud server C, so that cloud server C can send a file transfer request according to the file transfer request.
  • cloud server C can send a file transfer request to the target fog node router, in which the file transfer request and the connection request carry the identity of the client A1.
  • the target fog node router can Establish a file transfer connection with the client A1 according to the identifier of the client A1, and perform file transfer with the client A1 through the file transfer connection.
  • the client and the target fog node router perform file transfer through the file transfer connection between the two, so that files from the external network can be provided to the client without data transfer.
  • Transmission service since the file transmission through the file transmission connection between the fog node router and the client fully utilizes the network bandwidth of the fog node router, thereby increasing the rate of file transmission, and does not limit the type and size of the transmitted file , which improves the user experience.
  • the file transmission method provided by the embodiment of the present application is described in detail below by taking the cloud server side, the client side, and the fog node router side as examples respectively.
  • the file transmission method provided by the embodiment of the present application is described by taking the cloud server side as an example.
  • the file transmission method provided by the embodiment of the present application is configured to be executed in a cloud server.
  • the cloud server may be a relay server or other types of servers.
  • FIG. 2 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • the file transmission method may include the following steps 201-202.
  • Step 201 The cloud server receives a file transfer request sent by the client, wherein the file transfer request carries the identifier of the client.
  • the client can be a personal computer (Personal Computer, PC for short), a mobile device, etc.
  • the mobile device can be, for example, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, a vehicle-mounted device, or any other device that needs to perform file transfer.
  • the identifier of the client is used to uniquely identify the client, which can be arbitrarily set as required.
  • a file transfer request may be sent to the cloud server, and the file transfer request carries the identifier of the client,
  • the cloud server can receive the file transfer request sent by the client.
  • Step 202 the cloud server determines the target fog node router according to the file transfer request, and sends a connection request to the target fog node router, wherein the connection request carries the client identifier, so that the target fog node router establishes file transfer with the client according to the client identifier connection, and file transfer over a file transfer connection.
  • the cloud server may select a target fog node router from a plurality of fog node routers according to the file transfer request, and send a connection request to the target fog node router, so that the target fog node router A file transfer connection is established with the client according to the client's identity, so that the client can transfer files with the target fog node router through the file transfer connection.
  • the client and the target fog node router can transfer files through the file transfer connection between the two, so that the file transfer service of the external network can be provided for the client without data transfer.
  • the file transfer connection between clients is used for file transfer, there is no need to artificially limit the rate, size or type of file transfer due to cost reasons, and the network bandwidth of the fog node router can be fully utilized, thereby increasing the rate of file transfer and avoiding the need for data transfer.
  • the file type and size limitations improve the user experience.
  • the cloud server can determine the target fog node router according to the file transfer request, and send a connection request to the target fog node router, wherein the connection request
  • the identifier of the client is carried, so that the target fog node router establishes a file transfer connection with the client according to the identifier of the client, and performs file transfer through the file transfer connection.
  • the client and the target fog node router are realized through the file transfer connection between the two to perform file transfer, so that the file transfer service of the external network can be provided for the client without data transfer. , which makes full use of the network bandwidth of the fog node router, improves the rate of file transfer, and does not limit the type and size of the transferred files, improving the user experience.
  • FIG. 3 is a schematic flowchart of a file transmission method provided by an embodiment of the present application. As shown in FIG. 3, the file transmission method includes the following steps 301-303.
  • Step 301 the cloud server receives a file transfer request sent by the client, wherein the file transfer request is a file access request, the file access request carries a target file identifier and an identifier of the client, and the cloud server stores multiple file identifiers and multiple fog nodes Router mapping table.
  • the file transfer request may be a file access request or a file upload request, and the embodiments of the present application are described by taking the file transfer request as a file access request as an example.
  • the target file identifier is used to uniquely identify the target file that the client requests to access.
  • a client when a client needs to access or download a file, it can send a file access request to the cloud server.
  • Step 302 the cloud server queries the mapping relation table according to the target text identifier, and determines the fog node router corresponding to the target file identifier in the mapping relation table as the target fog node router.
  • the cloud server may pre-store the intranet addresses and extranet addresses of multiple routers, and, for each client, other routers with extranets except the local router corresponding to the client may be The router of the address acts as the router of each fog node.
  • Each fog node router stores multiple files respectively, and the cloud server can store multiple file identifiers and the mapping relationship table of multiple fog node routers, so that when the cloud server receives a file access request sent by the client, it can The target text identifier carried in the request is used to query the mapping relationship table, so that the fog node router corresponding to the target file identifier in the mapping relationship table is determined as the target fog node router.
  • Step 303 the cloud server sends a connection request to the target fog node router, wherein the connection request carries the identifier of the client, so that the target fog node router establishes a file transfer connection with the client according to the identifier of the client, and transfers files through the file transfer connection.
  • the cloud server after the cloud server determines the target fog node router, it can send a connection request carrying the client's identifier to the target fog node router, so that after receiving the connection request, the target fog node router can send a connection request according to the connection request.
  • the ID of the client establishes a file transfer connection with the client, and then the target fog node router can perform file transfer with the client through the file transfer connection.
  • the connection request sent by the cloud server to the target fog node router can carry the target file identifier in addition to the client identifier, so that the target fog node can also carry the target file identifier.
  • the router After the router establishes a file transfer connection with the client according to the client's identification, it can directly determine the target file according to the target file identification, and send the target file to the client without the need for the client to identify the target file again after the file transfer connection is established. It is sent to the target fog node router, which can save the number of interactions between the client and the target fog node router and improve the file transfer efficiency.
  • the cloud server since the cloud server needs to determine the target fog node router according to the multiple file identifiers and the mapping relationship tables of the multiple fog node routers, the cloud server can predetermine and store the mapping relationship table accordingly. That is, before step 302, the following steps 304-306 may also be included.
  • Step 304 the cloud server determines the device levels corresponding to the multiple fog node routers respectively.
  • the cloud server may determine a device level corresponding to each fog node router in the plurality of fog node routers.
  • the method of determining the device levels corresponding to the multiple fog node routers may be: the cloud server determines the equipment quality of the multiple fog node routers according to the online status of the multiple fog node routers; according to the network bandwidth of the multiple fog node routers, Determine the network quality of multiple fog node routers; determine the device levels corresponding to the multiple fog node routers according to the device quality and network quality.
  • the cloud server may detect whether the fog node router is online at a first preset time interval, and determine whether the fog node router is online within the first preset time range, and determine whether the fog node router is online.
  • the equipment quality of the fog node router, and the cloud server may detect the network bandwidth of the fog node router at a second preset time interval, and determine the fog node according to the network bandwidth of the fog node router within the second preset time range.
  • the network quality of the router, and then the equipment level of the fog node router is determined according to the equipment quality and network quality of the fog node router.
  • the first preset time interval and the second preset time interval may be the same or different, and the specific value of the preset time interval may be set as required.
  • the first preset time range and the second preset time range may be the same or different, and the specific value of the preset time range may be set as required.
  • the cloud server can preset a device quality metric value a and a network quality metric value b for each fog node router. It is assumed that the initial value of a is 1000, and the initial value of b is 0.
  • the cloud server can detect whether the fog node router is online at a frequency of 3s. If the fog node router is online, the device quality metric value will be increased by 1. If the fog node router is not online, the device quality metric value will be added. Subtract 1000. In addition, for each fog node router, the cloud server can detect the network bandwidth of the fog node router at a frequency of 3 seconds. If the network bandwidth is less than 10Mbps (megabits per second), the network quality metric value b is reduced by 1. If the bandwidth is greater than 10Mbps and less than 100Mbps, add 1 to the network quality metric value. If the network bandwidth is greater than 100Mbps and less than 200Mbps, add 2 to the network quality metric value.
  • the device level of the fog node router can be determined according to the values of the device quality metric value a and the network quality metric value b after 24 hours. For example, when the value of the device quality metric value a is less than 0, or the network quality metric value is less than 0, the device level of the fog node router is determined to be "poor"; when the value of the device quality metric value a is greater than 0 and less than 10000, and the network When the quality metric value is greater than 0 and less than 10,000, the device level of the fog node router is determined to be "medium”; when the value of the device quality metric value a is greater than 10,000 and less than 20,000, and the network quality metric value is greater than 0 and less than 10,000, determine the fog node router.
  • the equipment level of the node router is "good”; when the value of the equipment quality metric value a is greater than 0 and less than 10000, and the network quality metric value is greater than 10000 and less than 20000, the equipment level of the fog node router is determined to be "good”; When the value of the quality metric value a is greater than 20000, and the network quality metric value is greater than 20000, it is determined that the equipment level of the fog node router is "excellent", and so on.
  • Step 305 the cloud server determines the data types of the files corresponding to the multiple file identifiers respectively.
  • each fog node router can transmit the identifier of each file stored in it, as well as the modification time, creation time, and the number of visits of each file to the cloud server, so that the cloud server can send data according to the data sent by each fog node router. data to determine the data type of each file.
  • the cloud server may identify the file corresponding to each file, and determine the data type of the file according to the current time, the creation time of the file, the modification time of the file, and the number of visits to the file on that day.
  • the data type may be, for example, a cold data type, a hot data type, a candidate cold data type, and the like.
  • the frequency at which the cloud server determines the data type of files stored in the routers of each fog node can be set as required, such as once a day or once every two days.
  • the embodiments of the present application are described by taking as an example that the data type of the file stored in each fog node router is determined once a day.
  • the process of determining the data type of the file by the cloud server according to the current time, the creation time of the file, the modification time of the file, and the access volume of the file on that day may include:
  • the cloud server determines whether the first difference between the current time and the creation time corresponding to the file, or the second difference between the current time and the modification time corresponding to the file, is greater than a preset time threshold;
  • the data type of the file is determined to be the cold data type
  • the cloud server determines whether the daily access volume of the file is greater than or equal to a second preset number threshold
  • the preset time threshold may be set as required.
  • the first preset number threshold and the second preset number threshold can be the same value or different values, and their specific values can be set as needed, for example, they can be based on the average value of the sum of the total number of visits of all files in one day and 80
  • the /20 rule is OK.
  • the embodiments of the present application are described by taking the first preset number threshold and the second preset number threshold as different values as an example.
  • the preset time period can be set as required, for example, it can be set to one month, two months, and so on.
  • FIG. 4 is a schematic flowchart of determining a data type of a file in a file transmission method provided by an embodiment of the present application.
  • FIG. 5 is an example diagram of determining a data type of a file in a file transmission method provided by an embodiment of the present application.
  • one candidate cold data queue and one cold data queue may be set, and each node in the candidate cold data queue and the cold data queue corresponds to a file respectively, and the files in the cold data queue
  • the data type is the cold data type
  • the data type of the files in the candidate cold data queue is the candidate cold data type.
  • flag bits flag1 and flag2 and time counts count1 and count2 are preset respectively.
  • the flag1 corresponding to the file identifier when the flag1 corresponding to the file identifier is true, it indicates that the file corresponding to the file identifier is in the candidate cold data queue, that is, the data type of the file is the candidate cold data type; when the flag1 corresponding to the file identifier is false, it indicates that the file identifier corresponds to The file is not in the candidate cold data queue, that is, the data type of the file is not the candidate cold data type.
  • the flag2 corresponding to the file ID when the flag2 corresponding to the file ID is true, it indicates that the file corresponding to the file ID is in the cold data queue, that is, the data type of the file is cold data type; when the flag2 corresponding to the file ID is false, it indicates that the file corresponding to the file ID is in the cold data queue.
  • count1 represents the time count of the file in the candidate cold data queue
  • count2 represents the time count of the file in the cold data queue. For example, when the count1 corresponding to a file identifier is 2, it means that the file corresponding to the file identifier has been in the candidate cold data queue for two consecutive days.
  • the preset time threshold is T0
  • the first preset number threshold P1, the second preset number threshold P2, the first preset number threshold H1 and the second preset number threshold H2, and the number of visits on the day is count
  • T1 represents the creation time of the file
  • T2 represents the modification time of the file.
  • the cloud server may first initialize parameters such as T0, P1, P2, H1, and H2 (step 401). After each fog node router transmits the identifier of each file stored in it, as well as the modification time, creation time, and the number of visits of each file to the cloud server, correspondingly, after the cloud server obtains the data sent by each fog node router (step 402 ) ), the cloud server can identify the corresponding file for each file, and determine the data type corresponding to the file.
  • parameters such as T0, P1, P2, H1, and H2
  • the cloud server may first determine whether the first difference T-T1 between the current time T and the creation time T1 corresponding to the file is greater than the preset time threshold T0, or whether the current time T is equal to Whether the second difference T-T2 between the modification times T2 corresponding to the files is greater than the preset time threshold T0 (step 403). If both the first difference and the second difference are not greater than the preset time threshold T0, it is determined that the data type of the file is the hot data type (step 404). If the first difference or the second difference is greater than the preset time threshold T0, it is further judged whether the daily access count of the file is greater than or equal to the first preset number threshold P1 (step 405).
  • step 406 If the daily access count of the file is less than the first preset number threshold P1, it is determined that the data type of the file is the candidate cold data type, and the file is inserted into the candidate cold data queue (step 406). Further, it is judged whether the file exists in the candidate cold data queue (step 407). When the file exists in the candidate cold data queue, count1 is incremented by 1, and flag1 is set to true (step 408). When there is no such file in the queue, set count1 to 1 and set flag1 to true (step 409). For the files in the candidate cold data queue, it can be determined whether the count1 corresponding to the file is greater than or equal to the first preset number of times threshold P1 (step 410 ).
  • the consecutive number of candidate cold data types exceeds the first preset number of times threshold P1
  • it can be determined that the data type of the file is a cold data type, and the file is added to the cold data queue.
  • set count1 to 0, flag1 to false, and flag2 to true step 411).
  • the daily access count1 of the file is greater than or equal to the first preset number threshold P1
  • it can be determined whether the file is in the cold data queue step 417), if not, that is, the data type of the file is not the cold data type, then determine the file The data type is a hot data type.
  • the cloud server may determine whether the daily access count of the files is greater than or equal to the second preset number threshold P2 (step 412). If the daily access count of the file is greater than or equal to the second preset number threshold P2, add 1 to count2 (step 414), and determine whether the count2 corresponding to the file is greater than or equal to the second preset number threshold H2 (step 415).
  • the corresponding count2 is greater than or equal to the second preset number of times threshold H2, that is, the number of consecutive times that the daily access volume of the file is greater than or equal to the second preset number of times threshold P2 exceeds the second preset number of times threshold H2, then it is determined that the data type of the file is a hot data type , remove the file from the cold data queue, count2 is 0, and flag2 is false.
  • step 417 when the daily access count of the file is greater than or equal to the second preset number threshold P2, it is also possible to first determine whether the count2 corresponding to the file is greater than or equal to The second preset number of times threshold H2 (step 417 ), and then add 1 to count2 (step 420 ).
  • the execution order of steps 417 and 420 can be set as required.
  • the first difference T-T1 between the current time T and the creation time T1 corresponding to the file, and the modification time T2 corresponding to the current time T and the file When the second difference between the two is not greater than the preset time threshold T0, it is determined whether to add the file to the candidate cold data queue or to the candidate cold data queue according to whether the daily access volume of the file is lower than the first preset number threshold P1. file removed. When the daily access volume of the file is lower than the first preset number threshold P1, the file is added to the candidate cold data queue.
  • the data type of the file is the candidate cold data type
  • the daily access volume of the file in the candidate cold data queue is higher than
  • the first preset number threshold is P1
  • the file is removed from the candidate cold data queue, and the data type of the file at this time is the hot data type.
  • whether to add the file to the cold data queue is determined according to whether the number of consecutive times the file's access volume is lower than the first preset number threshold P1 is greater than or equal to the first preset number threshold P1.
  • the number of consecutive times that the daily access volume of the file is lower than the first preset number threshold P1 is greater than or equal to the first preset number threshold value H1
  • the consecutive times of the threshold value P1 is less than the first preset times threshold value H1
  • whether to remove the file from the cold data queue is determined according to whether the number of consecutive times that the file's access volume is higher than the second preset number threshold P2 is greater than or equal to the second preset number threshold H2.
  • the number of consecutive times that the daily access volume of the file is higher than the second preset number threshold P2 is greater than or equal to the second preset number threshold H2
  • the consecutive number of times of the quantity threshold P2 is less than the second preset number of times threshold H2
  • the data type of each file stored in each fog node router can be determined.
  • Step 306 the cloud server determines a mapping relationship table between the multiple file identifiers and the multiple fog node routers according to the device levels corresponding to the multiple fog node routers and the data types of the files corresponding to the multiple file identifiers respectively.
  • files of different data types correspond to fog node routers of different device levels.
  • the cloud server may determine to store files of different data types in different devices after determining the device levels corresponding to the multiple fog node routers and the data types of the files corresponding to the multiple file identifiers respectively.
  • a mapping relationship table is generated according to the storage relationship between the files corresponding to the multiple file identifiers and the multiple fog node routers.
  • the data types include cold data types, hot data types, and candidate cold data types
  • the equipment level includes four levels of excellent, good, medium, and poor.
  • the cloud server can determine to store the files whose data type is cold data type in the fog node router whose device level is poor, and store the files whose data type is candidate cold data type in the fog node router whose device level is medium and good.
  • store the files whose data type is the hot data type in the fog node router with the best equipment level and then generate the mapping between the identifier corresponding to each file and each fog node router according to the storage relationship between each file and each fog node router. Relational tables.
  • the equipment level of fog node router B1 is excellent, the equipment level of fog node router B2 is good, the equipment level of fog node router B3 is medium, and the equipment level of fog node router B4 is poor.
  • the data types of the two files with the file IDs X1 and X2 respectively are the hot data type, the data type of the file with the file ID X3 is the candidate cold data type, and the data type of the file with the file ID X4 is the cold data type.
  • the cloud server can determine to store the two files with the file IDs X1 and X2 in the fog node router B1, the file with the file ID X3 in the fog node router B3, and the file ID X4 in the fog node router B3.
  • a mapping relationship table between the identifier corresponding to each file and each fog node router is generated, wherein, in the mapping relationship table, the file identifiers X1 and X2 correspond to the fog node router B1, and the file identifier X3 corresponds to the fog node router B3, and the file identifier X4 corresponds to the fog node router B4.
  • the network bandwidth of the fog node router with the highest equipment level can be fully utilized, and the transmission rate of the hot data type file can be improved, so that the most Hot resources are provided to a large number of clients at the same time to meet the needs of a large number of clients accessing the hottest resources at the same time.
  • the cloud server may determine the mapping relationship table between multiple file identifiers and multiple fog node routers at a preset frequency, and the multiple file identifiers currently determined by the cloud server and multiple fog nodes In the mapping relationship table of the router, there is a corresponding relationship between one or more file identifiers and the fog node router.
  • the mapping relationship table determined last time is different from the corresponding relationship between the file identifier and the fog node router, the corresponding relationship between the file identifier and the fog node router is different.
  • the file identifier of the file can be sent to the original fog node router corresponding to the file identifier in the last determined mapping relationship table and the current fog node router corresponding to the file identifier in the currently determined mapping relationship table, Therefore, the original fog node router can send the file corresponding to the file identifier to the current fog node router, so as to realize the conversion of the storage location of the file corresponding to the file identifier.
  • the cloud server can communicate with multiple fog node routers through long connections, and multiple fog node routers can communicate through P2P (Point to point, point-to-point) mode, so as to realize the realization of each fog node router.
  • the file corresponding to each file identifier can be transmitted between the fog node routers according to the mapping relationship table between the multiple file identifiers and the multiple fog node routers determined by the cloud server.
  • the cloud server receives a file transfer request sent by the client, wherein the file transfer request is a file access request, the file access request carries a target file identifier and an identifier of the client, and the cloud server stores multiple The mapping relationship table between the file ID and multiple fog node routers, the cloud server queries the mapping relationship table according to the target text ID, and determines the fog node router corresponding to the target file ID in the mapping relationship table as the target fog node router.
  • the node router sends a connection request, wherein the connection request carries the identifier of the client, so that the target fog node router establishes a file transfer connection with the client according to the identifier of the client, and performs file transfer through the file transfer connection. Therefore, when the client needs to access the file, the client can access the file through the file transfer connection with the target fog node router, so that the file download service from the external network can be provided for the client without data transfer. , and when the file is downloaded, the network bandwidth of the fog node router is fully utilized, the speed of the file download is increased, and the type and size of the downloaded file are not limited, which improves the user experience.
  • the above embodiment takes the file transfer request as a file access request as an example to describe the file transfer method, and the following takes the file transfer request as a file upload request as an example to describe the file transfer method provided by the embodiments of the present application.
  • FIG. 7 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • the file transmission method provided by this embodiment of the present application may include the following steps 701-704.
  • Step 701 The cloud server receives a file transfer request sent by the client, wherein the file transfer request is a file upload request, and the file upload request carries the identifier of the client.
  • Step 702 the cloud server determines the communication quality level between the client and the multiple fog node routers according to the identifier of the client.
  • Step 703 the cloud server selects a target fog node router from the multiple fog node routers according to the communication quality level between the client and the multiple fog node routers.
  • the client when it needs to store files, it can send a file upload request to the cloud server, and the file upload request carries the client's identifier, so that the cloud server can determine the client's identity with the multiple cloud servers according to the client's identifier.
  • the communication quality level between the node routers, and then according to the communication quality level between the client and the multiple fog node routers, the target fog node router is selected from the multiple fog node routers.
  • the cloud server can determine information such as the type of the client, network operator, location, etc., according to the identification of the client, and can determine the location of each fog node router and the corresponding network operator and other information, Further, for each fog node router, the network between the client and the fog node router can be determined according to information such as the type of the client, network operator, location, etc., as well as the location of the fog node router and the corresponding network operator. The quality is high and low, and then according to the communication quality between the client and multiple fog node routers, the communication quality between the client and each fog node router is classified, and the fog node router with the highest communication quality level is determined as the target. fog node router.
  • the cloud server can determine that the communication quality between the client and the fog node router B1 is better than the communication quality between the client and the fog node router B2 according to the location of the client, the network operation, and the locations and network operators of the fog node routers B1 and B2. Communication quality, so that the fog node router B1 is determined as the target fog node router.
  • Step 704 the cloud server sends a connection request to the target fog node router, wherein the connection request carries the identifier of the client, so that the target fog node router establishes a file transfer connection with the client according to the identifier of the client, and transfers files through the file transfer connection.
  • the connection request sent by the cloud server to the target fog node router may only include the identifier of the client, so that the target fog node router can establish a connection with the client according to the identifier of the client.
  • the client sends the target file and the identifier corresponding to the target file to the target fog node router through the file transfer connection.
  • the target fog node router in addition to the identifier of the client, it may also carry the identifier of the target file, so that the target fog node router establishes a file with the client according to the identifier of the client carried in the connection request.
  • the client can directly send the target file corresponding to the target file identifier to the target fog node router.
  • the file transfer request is a file upload request
  • the file upload request carries the identifier of the client
  • the cloud server determines the client according to the identifier of the client.
  • the communication quality level with multiple fog node routers and then according to the communication quality level between the client and multiple fog node routers
  • the target fog node router is selected from multiple fog node routers, and then sent to the target fog node router.
  • a connection request wherein the connection request carries the identifier of the client, so that the target fog node router establishes a file transfer connection with the client according to the identifier of the client, and performs file transfer through the file transfer connection.
  • the client when the client needs to upload a file, the client can upload the file through the file transfer connection with the target fog node router, so that the file storage service on the external network can be provided for the client without data transfer.
  • the network bandwidth of the fog node router when uploading files, the network bandwidth of the fog node router is fully utilized, the rate of file uploading is increased, the type and size of uploaded files are not limited, and the user experience is improved.
  • the following takes the client side as an example to describe the file transmission method provided by the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • the file transmission method provided by the embodiment of the present application is configured to be executed in the client. It can be understood that the file transfer method provided by the present application can be applied to a scenario in which a storage and download service on an external network is provided to multiple clients, and the client in this embodiment of the present application may be any client among the multiple clients. end.
  • the client can be a personal computer (Personal Computer, PC for short), a mobile device, etc.
  • the mobile device can be, for example, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, a vehicle-mounted device, etc. Any device that needs to perform file transfer.
  • the file transmission method may include the following steps 801-802.
  • Step 801 the client sends a file transfer request to the cloud server, so that the cloud server determines the target fog node router according to the file transfer request, and sends a connection request to the target fog node router, wherein the file transfer request and the connection request carry the identifier of the client.
  • the identifier of the client is used to uniquely identify the client, which can be arbitrarily set as required.
  • the cloud server can determine the target fog node router from multiple fog node routers according to the file transfer request, and the cloud server can send a connection request to the target fog node router, wherein the connection request carries the client's identifier, so that the target fog
  • the node router can establish a file transfer connection with the client according to the identification of the client in the connection request.
  • the manner in which the cloud server determines the target fog node router according to the file transmission request may refer to the above-mentioned embodiment, which will not be repeated here.
  • Step 802 after the client establishes a file transfer connection with the target fog node router according to the identifier of the client, the file transfer is performed through the file transfer connection.
  • the client can perform file transfer with the target fog node router through the file transfer connection.
  • the client and the target fog node router can transfer files through the file transfer connection between the two, so that the file transfer service of the external network can be provided for the client without data transfer.
  • the file transfer connection between clients is used for file transfer, there is no need to artificially limit the rate, size or type of file transfer due to cost reasons, and the network bandwidth of the fog node router can be fully utilized, thereby increasing the rate of file transfer and avoiding the need for data transfer.
  • the file type and size limitations improve the user experience.
  • the client sends a file transfer request to the cloud server, so that the cloud server determines the target fog node router according to the file transfer request, and sends a connection request to the target fog node router, wherein the file transfer request and
  • the connection request carries the identifier of the client.
  • the file transfer is performed through the file transfer connection, thereby realizing the connection between the client and the target fog node router. It can provide external network file transfer service for the client without data transfer, and make full use of the network bandwidth of the fog node router during file transfer, which improves the file transfer rate. , and does not limit the type and size of transferred files, improving the user experience.
  • FIG. 9 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • the file transmission method provided by the embodiment of the present application includes the following steps 901-904.
  • Step 901 the client determines whether the environment in which it is located is an external network environment, if so, executes step 902, otherwise, executes step 904.
  • Step 802 the client sends a file transfer request to the cloud server, so that the cloud server determines the target fog node router according to the file transfer request, and sends a connection request to the target fog node router, wherein the file transfer request and the connection request carry the identifier of the client.
  • Step 903 after the client establishes a file transfer connection with the target fog node router according to the identifier of the client, the file transfer is performed through the file transfer connection.
  • the cloud server can determine the target fog node router from multiple fog node routers according to the file transfer request, and the cloud server can send a connection request to the target fog node router, wherein the connection request carries the client's identifier, so that the target The fog node router can establish a file transfer connection with the client according to the identity of the client in the connection request.
  • the file transfer request may be a file access request or a file upload request.
  • a client when a client needs to access or download a file, it may send a file access request to the cloud server, and the file access request carries the client's identifier and the target file identifier.
  • the cloud server can pre-store the mapping relationship table of multiple file identifiers and multiple fog node routers, so that when the cloud server receives a file access request sent by the client, it can query the mapping relationship according to the target text identifier carried in the file access request table, and determine the fog node router corresponding to the target file identifier in the mapping relationship table as the target fog node router.
  • the cloud server After the cloud server determines the target fog node router, it can send a connection request carrying the client's identity to the target fog node router, so that after receiving the connection request, the target fog node router can communicate with the client according to the client's identity carried in the connection request.
  • the client establishes a file transfer connection, and then the target fog node router can perform file transfer with the client through the file transfer connection.
  • the connection request sent by the cloud server to the target fog node router can carry the target file identifier in addition to the client identifier, so that the target fog node can also carry the target file identifier.
  • the router After the router establishes a file transfer connection with the client according to the client's identifier, it can directly determine the target file according to the target file identifier, and send the target file to the client through the file transfer connection.
  • the client can connect through the file transfer, Directly receive the target file corresponding to the target file ID sent by the target fog node router, without the need for the client to send the target file ID to the target fog node router again after the file transfer connection is established, thus saving the time between the client and the target fog node router.
  • the number of interactions is increased, and the file transfer efficiency is improved.
  • the client when it needs to store files, it can send a file upload request to the cloud server, and the file upload request carries the client's identifier, so that the cloud server can determine the client's identity with the multiple cloud servers according to the client's identifier.
  • the communication quality level between the node routers, and then according to the communication quality level between the client and the multiple fog node routers, the target fog node router is selected from the multiple fog node routers.
  • the connection request sent by the cloud server to the target fog node router may only include the identifier of the client, so that the target fog node router can establish a connection with the client according to the identifier of the client.
  • the client sends the target file identifier and the target file method corresponding to the target file identifier to the target fog node router through the file transfer connection.
  • the target fog node router in addition to the identifier of the client, it may also carry the identifier of the target file, so that the target fog node router establishes a file with the client according to the identifier of the client carried in the connection request.
  • the client can directly send the target file corresponding to the target file identifier to the target fog node router.
  • Step 904 the client and the local router perform file transfer through the file transfer connection between the client and the local router.
  • the client when the environment where the client is located is an intranet environment, the client can perform file transfer with the local router through a file transfer connection between the client and the local router. Specifically, the client can download the file from the local router or transfer the file to the local router.
  • a file transfer request may be sent to the cloud server, so that the cloud server determines the target fog node router according to the file transfer request, and sends the request to the target fog node router.
  • a connection request wherein the file transfer request and the connection request carry the identifier of the client.
  • the client After the client establishes a file transfer connection with the target fog node router according to the client identifier, the client can perform file transfer with the target fog node router through the file transfer connection.
  • the environment where the client is located is an intranet environment
  • the client and the local router perform file transfer through a file transfer connection between the client and the local router.
  • the client can use the corresponding file transfer connection for file transfer according to the network environment where it is located. Since the client environment is an external network environment, the client and the target fog node router are connected through the file transfer between the two. For file transfer, the file transfer service on the external network can be provided for the client without data transfer, and the network bandwidth of the fog node router is fully utilized during file transfer, which improves the file transfer rate and does not limit the transfer. The type and size of the files improves the user experience.
  • the file transmission method provided by the embodiment of the present application is described below by taking the router side of the fog node as an example.
  • FIG. 10 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • the file transmission method provided by the embodiment of the present application is configured to be executed in the fog node router. It can be understood that the fog node router in the embodiment of the present application is specifically the target fog node router that provides the external network file storage and download service to the client in the foregoing embodiment.
  • the file transfer method may include the following steps 1001-1003.
  • Step 1001 the fog node router receives a connection request sent by the cloud server, wherein the connection request is sent by the cloud server to the fog node router after receiving the file transfer request sent by the client to the cloud server, and the file transfer request and the connection request carry the client end identification.
  • Step 1002 the fog node router establishes a file transfer connection with the client according to the identifier of the client.
  • the client may be a personal computer (Personal Computer, PC for short), a mobile device, etc.
  • the mobile device may be, for example, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, a vehicle-mounted device, or any other device that needs to perform file transfer.
  • the cloud server can determine the target fog node router from the multiple fog node routers according to the file transfer request, and the cloud server can send a connection request to the target fog node router, wherein the connection request carries the identifier of the client.
  • the target fog node router can establish a file transfer connection with the client according to the client's identity.
  • the manner in which the cloud server determines the target fog node router according to the file transmission request may refer to the above-mentioned embodiment, which will not be repeated here.
  • Step 1003 the fog node router and the client perform file transfer through a file transfer connection.
  • the target fog node can perform file transfer with the client through the file transfer connection.
  • the client and the target fog node router can transfer files through the file transfer connection between the two, so that the file transfer service of the external network can be provided for the client without data transfer.
  • the file transfer connection between clients is used for file transfer, there is no need to artificially limit the rate, size or type of file transfer due to cost reasons, and the network bandwidth of the fog node router can be fully utilized, thereby increasing the rate of file transfer and avoiding the need for data transfer.
  • the file type and size limitations improve the user experience.
  • the fog node router after receiving the connection request sent by the cloud server, the fog node router establishes a file transmission connection with the client according to the identifier of the client, and then the fog node router and the client perform file transmission through the file transmission connection, As a result, the client and the target fog node router are realized through the file transfer connection between the two to perform file transfer, so that the file transfer service of the external network can be provided for the client without data transfer.
  • the fog node router which makes full use of the network bandwidth of the fog node router, improves the rate of file transfer, and does not limit the type and size of the transferred files, improving the user experience.
  • FIG. 11 is a schematic flowchart of a file transmission method provided by an embodiment of the present application.
  • the file transmission method provided by the embodiment of the present application includes the following steps 1101-1104.
  • Step 1101 the fog node router receives a connection request sent by the cloud server, wherein the connection request is sent by the cloud server to the fog node router after receiving the file transfer request sent by the client to the cloud server, and the file transfer request is a file access request,
  • the file access request and the connection request carry the client's identifier and the target file identifier, and the fog node router stores files corresponding to multiple file identifiers.
  • the fog node router is a router with an external network address among other routers except the local router corresponding to the client.
  • Step 1102 the fog node router establishes a file transfer connection with the client according to the client's identifier.
  • the cloud server can determine the target fog node router from multiple fog node routers according to the file transfer request, and the cloud server can send a connection request to the target fog node router, wherein the connection request carries the client's identifier, so that the target fog node
  • the node router can establish a file transfer connection with the client according to the identification of the client in the connection request.
  • Step 1103 the fog node router searches for the target file corresponding to the target file identifier according to the target file identifier.
  • Step 1104 the fog node router sends the target file to the client through the file transmission connection.
  • the file transfer request and the connection request may carry the target file identifier in addition to the client's identifier.
  • the target fog node router can query the target fog node according to the target file identifier.
  • the multiple file identifiers stored in the router correspond to the files respectively, so as to find the target file corresponding to the target file identifier, and then the target file corresponding to the target file identifier can be sent to the client through the file transmission connection.
  • the file transfer request when the file transfer request is a file upload request, the file upload request and the connection request may carry the client's identifier and the target file identifier, so that after the target fog node router establishes a file transfer connection with the client, the client The file identifier and the target file corresponding to the file identifier can be sent to the target fog node router through the file transfer connection.
  • the target fog node router can receive the target file corresponding to the target file identifier sent by the client through the file transfer connection.
  • one or more fog node routers among the multiple fog node routers may also perform data synchronization with the local router corresponding to the client, wherein the synchronized data may be the local router corresponding to the client The hottest file in the router, so that when the file transfer connection between the client and the corresponding local router is disconnected, the client can obtain the hottest file from the fog node router for the user holding the client. That is, in the embodiment of the present application, the method may further include: data synchronization between the fog node router and the local router corresponding to the client.
  • the local router corresponding to the client can synchronize the hottest file stored in the local router to one or more fog node routers.
  • the local router can synchronize data with the fog node router in a P2P manner.
  • the client can download the hottest file from the local router or upload the target file to the local router.
  • the client can send a file transfer request to the cloud server (not shown in FIG. 12 ), so that the cloud server can determine the target fog node router according to the file transfer request, and send the request to the cloud server.
  • the target fog node router sends a connection request, and then the target fog node router can establish a file transfer connection with the client according to the connection request. After the client establishes a file transfer connection with the target fog node router, the client can download the hottest file for the client user from the target fog node router through the file transfer connection or upload the target file to the target fog node router.
  • the fog node router after receiving the connection request sent by the cloud server, the fog node router establishes a file transmission connection with the client according to the identifier of the client, and then the fog node router searches for the corresponding target file identifier according to the target file identifier.
  • the target file is sent to the client through the file transfer connection, thereby realizing the file transfer between the client and the target fog node router through the file transfer connection between the two, so that no data transfer is required.
  • FIG. 13 is a schematic structural diagram of a cloud server provided by an embodiment of the present application.
  • the cloud server 1300 may include: a receiving module 1310 and a first determining module 1320 .
  • the receiving module 1310 is configured to receive a file transfer request sent by the client, wherein the file transfer request carries the identifier of the client;
  • the first determining module 1320 is configured to determine the target fog node router according to the file transfer request, and send a connection request to the target fog node router, wherein the connection request carries the identifier of the client, so that the target fog node router communicates with the client according to the identifier of the client.
  • a file transfer connection is established, and file transfer is performed through the file transfer connection.
  • the file transfer request is a file access request
  • the file access request carries a target file identifier
  • the cloud server stores the mapping of multiple file identifiers and multiple fog node routers. Relational tables
  • the first determining module 1320 is specifically used for:
  • mapping relation table is queried according to the target text identifier, and the fog node router corresponding to the target file identifier in the mapping relation table is determined as the target fog node router.
  • the cloud server 1300 may further include:
  • the second determining module 1330 is configured to determine the device levels corresponding to the multiple fog node routers respectively;
  • a third determining module 1340 configured to determine the data types of the files corresponding to the multiple file identifiers respectively;
  • the fourth determination module 1350 is configured to determine the mapping relationship table between the multiple file identifiers and the multiple fog node routers according to the device levels corresponding to the multiple fog node routers and the data types of the files corresponding to the multiple file identifiers, wherein, Files of different data types correspond to fog node routers of different device levels.
  • the fourth determination module 1350 is specifically used for:
  • the device levels corresponding to the multiple fog node routers and the data types of the files corresponding to the multiple file identifiers it is determined that files of different data types are stored in the fog node routers of different device levels;
  • a mapping relationship table is generated according to the storage relationship between the files corresponding to the multiple file identifiers and the multiple fog node routers.
  • the second determining module 1330 is specifically configured to:
  • the equipment levels corresponding to the multiple fog node routers are determined.
  • the third determining module 1340 includes:
  • the determining unit is configured to identify the file corresponding to each file, and determine the data type of the file according to the current time, the creation time of the file, the modification time of the file, and the access volume of the file on the day.
  • the data types include cold data types, hot data types, and candidate cold data types; wherein, the determining unit is specifically used for:
  • the data type of the file is determined to be the cold data type
  • the file transfer request is a file upload request
  • the first determining module 1220 is specifically used for:
  • the identification of the client determine the communication quality level between the client and multiple fog node routers
  • the target fog node router is selected from multiple fog node routers.
  • the cloud server in the embodiment of the present application after receiving the file transfer request that carries the identifier of the client sent by the client, can determine the target fog node router according to the file transfer request, and send a connection request to the target fog node router, where the connection request carries the client ID of the client, so that the target fog node router establishes a file transfer connection with the client according to the client's ID, and performs file transfer through the file transfer connection.
  • the client and the target fog node router are realized through the file transfer connection between the two to perform file transfer, so that the file transfer service of the external network can be provided for the client without data transfer.
  • which makes full use of the network bandwidth of the fog node router improves the rate of file transfer, and does not limit the type and size of the transferred files, improving the user experience.
  • FIG. 15 is a schematic structural diagram of a client provided by an embodiment of the present application.
  • the client 1500 may include: a sending module 1510 and a first transmission module 1520 .
  • the sending module 1510 is configured to send a file transfer request to the cloud server, so that the cloud server determines the target fog node router according to the file transfer request, and sends a connection request to the target fog node router, wherein the file transfer request and the connection request carry the client terminal identification;
  • the first transmission module 1520 is configured to perform file transmission through the file transmission connection after the client establishes a file transmission connection with the target fog node router according to the identifier of the client.
  • the file transfer request is a file access request
  • the file access request and the connection request carry a target file identifier
  • the first transmission module 1520 is specifically used for:
  • the target file corresponding to the target file identifier sent by the target fog node router is received.
  • the file transfer request is a file upload request, and the file upload request and the connection request carry a target file identifier;
  • the first transmission module 1520 is specifically used for:
  • the target file corresponding to the target file identifier is sent to the target fog node router.
  • the client may further include:
  • the second transmission module is used for file transmission with the local router through the file transmission connection between the client and the local router when the environment where the client is located is an intranet environment.
  • the client in this embodiment of the present application may send a file transfer request to the cloud server, so that the cloud server determines the target fog node router according to the file transfer request, and sends a connection request to the target fog node router, wherein the file transfer request and the connection request carry
  • the identifier of the client after the client establishes a file transfer connection with the target fog node router according to the client identifier, the file transfer is performed through the file transfer connection, thereby realizing the file transfer between the client and the target fog node router through the two.
  • FIG. 16 is a schematic structural diagram of a fog node router provided by an embodiment of the present application.
  • the fog node router 1600 may include: a receiving module 1610 , a establishing module 1620 and a transmitting module 1630 .
  • the receiving module 1610 is configured to receive the connection request sent by the cloud server, wherein the connection request is the file transmission request and the connection request sent by the cloud server to the fog node router after receiving the file transmission request sent by the client to the cloud server. Carry the client's identity;
  • establishing module 1620 for establishing a file transfer connection with the client according to the identification of the client;
  • the transmission module 1630 is configured to perform file transmission with the client through a file transmission connection.
  • the fog node router is a router with an external network address among other routers other than the local router corresponding to the client.
  • the file transfer request is a file access request
  • the file access request and the connection request carry a target file identifier
  • the fog node router stores files corresponding to multiple file identifiers respectively.
  • the transmission module 1630 is specifically used for:
  • the target file identifier find the target file corresponding to the target file identifier
  • the file transfer request is a file upload request, and the file upload request and the connection request carry a target file identifier;
  • the transmission module 1630 is specifically used for:
  • the target file corresponding to the target file identifier sent by the client is received.
  • the fog node router may further include:
  • the synchronization module is used to synchronize data with the local router corresponding to the client.
  • the fog node router in the embodiment of the present application after receiving the connection request sent by the cloud server, establishes a file transmission connection with the client according to the identifier of the client, and then the fog node router and the client perform file transmission through the file transmission connection, thereby realizing The client and the target fog node router perform file transfer through the file transfer connection between the two, so that the file transfer service of the external network can be provided for the client without data transfer, and the file transfer can be fully utilized.
  • the network bandwidth of the fog node router increases the rate of file transfer, and does not limit the type and size of the transferred files, improving the user experience.
  • the present application also proposes a file transmission system, including a client, a cloud server, and a plurality of fog node routers.
  • the cloud server is used to receive the file transfer request sent by the client, and determine the target fog node router among the multiple fog node routers according to the file transfer request, and send a connection request to the target fog node router, wherein the file transfer request and The connection request carries the identity of the client;
  • the target fog node router is used to establish a file transfer connection with the client according to the identification of the client after receiving the connection request, and perform file transfer with the client through the file transfer connection;
  • the client is used to send a file transfer request to the cloud server, and to perform file transfer with the target fog node router through a file transfer connection.
  • the description of the cloud server, the client and the fog node router in the above embodiment is also applicable to the cloud server, the client and the target fog in the multiple fog node routers in the file transfer system of the embodiment of the present application Node routers, which are not repeated here.
  • the file transmission system provided by the embodiment of the present application realizes the file transmission between the client and the target fog node router through the file transmission connection between the two, so that the file transmission of the external network can be provided for the client without data transfer.
  • the network bandwidth of the fog node router is fully utilized, the rate of file transfer is increased, and the type and size of the transferred files are not limited, which improves the user experience.
  • the present application further proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores information that can be used by the at least one processor Executed instructions, the instructions are executed by the at least one processor, so that the at least one processor can execute the file transfer method proposed in any of the foregoing embodiments of the present application.
  • the present application further provides a non-transitory computer-readable storage medium storing computer instructions, the computer instructions being used to cause the computer to execute the file transfer method proposed in any of the foregoing embodiments of the present application.
  • the present application further proposes a computer program product, including a computer program, when the computer program is executed by a processor, the file transmission method as proposed in any of the foregoing embodiments of the present application is implemented.
  • FIG. 17 shows a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present application.
  • the electronic device 1700 shown in FIG. 17 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present application.
  • the electronic device may be a cloud server, a client or a fog node router.
  • electronic device 1700 takes the form of a general-purpose computing device.
  • Components of electronic device 1700 may include, but are not limited to, one or more processors or processing units 16 , system memory 28 , and bus 18 connecting various system components including system memory 28 and processing unit 16 .
  • Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of a variety of bus structures.
  • these architectures include, but are not limited to, Industry Standard Architecture (hereinafter referred to as: ISA) bus, Micro Channel Architecture (hereinafter referred to as: MAC) bus, enhanced ISA bus, video electronics Standards Association (Video Electronics Standards Association; hereinafter referred to as: VESA) local bus and Peripheral Component Interconnection (Peripheral Component Interconnection; hereinafter referred to as: PCI) bus.
  • ISA Industry Standard Architecture
  • MAC Micro Channel Architecture
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnection
  • Electronic device 1700 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 1700, including volatile and nonvolatile media, removable and non-removable media.
  • the memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) 30 and/or cache memory 32 .
  • Electronic device 1700 may further include other removable/non-removable, volatile/non-volatile computer system storage media.
  • storage system 34 may be used to read and write to non-removable, non-volatile magnetic media (not shown in FIG. 17, commonly referred to as a "hard disk drive").
  • a magnetic disk drive for reading and writing to removable non-volatile magnetic disks eg "floppy disks" and removable non-volatile optical disks (eg, compact disk read only memory)
  • CD-ROM Disc Read Only Memory
  • DVD-ROM Digital Video Disc Read Only Memory
  • each drive may be connected to bus 18 through one or more data media interfaces.
  • Memory 28 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of various embodiments of the present application.
  • a program/utility 40 having a set (at least one) of program modules 42, which may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data , each or some combination of these examples may include an implementation of a network environment.
  • Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
  • the electronic device 1700 may also communicate with one or more external devices 14 (eg, keyboard, pointing device, display 24, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1700, and/or communicate with the electronic device 1700. Any device (eg, network card, modem, etc.) that enables the electronic device 1700 to communicate with one or more other computing devices. Such communication may take place through input/output (I/O) interface 22 .
  • I/O input/output
  • the electronic device 1700 can also communicate with one or more networks (such as a local area network (Local Area Network; hereinafter referred to as: LAN), a wide area network (Wide Area Network; hereinafter referred to as: WAN) and/or a public network, such as the Internet, through the network adapter 20 ) communication.
  • networks such as a local area network (Local Area Network; hereinafter referred to as: LAN), a wide area network (Wide Area Network; hereinafter referred to as: WAN) and/or a public network, such as the Internet
  • network adapter 20 communicates with other modules of electronic device 1700 via bus 18 .
  • bus 18 a local area network
  • other hardware and/or software modules may be used in conjunction with electronic device 1700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tapes drives and data backup storage systems, etc.
  • the processing unit 16 executes various functional applications and data processing by running the programs stored in the system memory 28 , for example, implements the methods mentioned in the foregoing embodiments.
  • first and second are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implying the number of indicated technical features. Thus, a feature delimited with “first”, “second” may expressly or implicitly include at least one of that feature.
  • plurality means at least two, such as two, three, etc., unless expressly and specifically defined otherwise.
  • a "computer-readable medium” can be any device that can contain, store, communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or apparatus.
  • computer readable media include the following: electrical connections with one or more wiring (electronic devices), portable computer disk cartridges (magnetic devices), random access memory (RAM), Read Only Memory (ROM), Erasable Editable Read Only Memory (EPROM or Flash Memory), Fiber Optic Devices, and Portable Compact Disc Read Only Memory (CDROM).
  • the computer readable medium may even be paper or other suitable medium on which the program may be printed, as the paper or other medium may be optically scanned, for example, followed by editing, interpretation, or other suitable medium as necessary process to obtain the program electronically and then store it in computer memory.
  • each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.
  • the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请提出一种文件传输方法、云端服务器、客户端以及雾节点路由器，涉及通信技术领域，方法包括：云端服务器接收客户端发送的文件传输请求；云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，文件传输请求和连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。

Description

文件传输方法、云端服务器、客户端以及雾节点路由器
相关申请的交叉引用
本申请基于申请号为202110382829.2、申请日为2021年04月09日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信技术领域，尤其涉及一种文件传输方法、云端服务器、客户端以及雾节点路由器。
背景技术
相关技术中，在手机等电子设备处在例如4G(The 4th Generation mobile communication technology，第四代移动通信技术)网络或非本地网络等外网环境中时，通常通过中转服务为电子设备提供外网的存储下载服务，比如，电子设备通过中转服务器从源数据服务器获取数据。而数据中转的成本很高，考虑到数据中转的成本问题，通过中转服务提供外网的存储下载服务时，通常会人为限制文件传输的速率、大小或类型，从而导致电子设备通过外网进行文件下载或存储时易出现文件传输速率低、文件大小或类型受限的问题。
发明内容
本申请旨在至少在一定程度上解决相关技术中的技术问题之一。
本申请提出一种文件传输方法、云端服务器、客户端、雾节点路由器、文件传输系统、电子设备以及存储介质，以解决相关技术中通过中转服务器为电子设备提供外网的存储下载服务时，易出现文件传输速率低、文件大小或类型受限的情况的技术问题。
本申请第一方面实施例提出了一种文件传输方法，包括：云端服务器接收客户端发送的文件传输请求，其中，所述文件传输请求携带所述客户端的标识；所述云端服务器根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述连接请求携带所述客户端的标识，以使所述目标雾节点路由器根据所述客户端的标识与所述客户端建立文件传输连接，并通过所述文件传输连接进行文件传输。
本申请第二方面实施例提出了另一种文件传输方法，包括：客户端向云端服务器发送文件传输请求，以使所述云端服务器根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述文件传输请求和所述连接请求携带所述客户端的标识；在所述客户端根据所述客户端的标识与所述目标雾节点路由器建立文件传输连接后，通过所述文件传输连接进行文件传输。
本申请第三方面实施例提出了另一种文件传输方法，包括：雾节点路由器接收云端服务器发送的连接请求，其中，所述连接请求是所述云端服务器在接收到客户端向所述云端服务器发送的文件传输请求后发送至所述雾节点路由器的，所述文件传输请求和所述连接请求携带所述客户端的标识；所述雾节点路由器根据所述客户端的标识，与所述客户端建立文件传输连接；所述雾节点路由器与所述客户端通过所述文件传输连接进行文件传输。
本申请第四方面实施例提出了一种云端服务器，包括：接收模块，用于接收客户端发送的文件传输请求，其中，所述文件传输请求携带所述客户端的标识；第一确定模块，用于根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述连接请求携带所述客户端的标识，以使所述目标雾节点路由器根据所述客户端的标识与所述客户端建立文件传输连接，并通过所述文件传输连接进行文件传输。
本申请第五方面实施例提出了一种客户端，包括：发送模块，用于向云端服务器发送文件传输请求，以使所述云端服务器根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述文件传输请求和所述连接请求携带所述客户端的标识；第一传输模块，用于在所述客户端根据所述客户端的标识与所述目标雾节点路由器建立文件传输连接后，通过所述文件传输连接进行文件传输。
本申请第六方面实施例提出了一种雾节点路由器，包括：接收模块，用于接收云端服务器发送的连接请求，其中，所述连接请求是所述云端服务器在接收到客户端向所述云端服务器发送的文件传输请求后发送至所述雾节点路由器的，所述文件传输请求和所述连接请求携带所述客户端的标识；建立模块，用于根据所述客户端的标识，与所述客户端建立文件传输连接；传输模块，用于与所述客户端通过所述文件传输连接进行文件传输。
本申请第七方面实施例提出了一种文件传输系统，包括客户端、云端服务器以及多个雾节点路由器；其中，所述云端服务器，用于接收所述客户端发送的文件传输请求，以及根据所述文件传输请求确定所述多个雾节点路由器中的目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述文件传输请求和所述连接请求携带所述客户端的标识；所述目标雾节点路由器，用于在接收到所述连接请求后，根据所述客户端的标识，与所述客户端建立文件传输连接，以及与所述客户端通过所述文件传输连接进行文件传输；所述客户端，用于向所述云端服务器发送所述文件传输请求，以及与所述目标雾节点路由器通过所述文件传输连接进行文件传输。
本申请第八方面实施例提出了一种电子设备，包括：至少一个处理器；以及与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如本申请第一方面实施例或者第二方面实施例或者第三方面实施例提出的文件传输方法。
本申请第九方面实施例提出了一种存储有计算机指令的非瞬时计算机可读存储介质，所述计算机指令用于使所述计算机执行如本申请第一方面实施例或者第二方面实施例或者第三方面实施例提出的文件传输方法。
本申请第十方面实施例提出了一种计算机程序产品，包括计算机程序，所述计算机程序在被处理器执行时实现如本申请第一方面实施例或者第二方面实施例或者第三方面实施例提出的文件传输方法。
本申请实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
本申请附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本申请的实践了解到。
附图说明
本申请上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1为本申请实施例提供的文件传输方法的应用场景的示意图；
图2为本申请实施例所提供的文件传输方法的流程示意图；
图3为本申请实施例所提供的文件传输方法的另一流程示意图；
图4为本申请实施例所提供的文件传输方法中确定文件的数据类型的流程示意图；
图5为本申请实施例所提供的文件传输方法中确定文件的数据类型的示例图；
图6为本申请实施例提供的云端服务器与雾节点路由器之间、多个雾节点路由器之间以及雾节点路由器与本地路由器之间的通信方式的示例图；
图7为本申请实施例提供的文件传输方法的流程示意图；
图8为本申请实施例所提供的文件传输方法的另一流程示意图；
图9为本申请实施例所提供的文件传输方法的另一流程示意图；
图10为本申请实施例所提供的文件传输方法的另一流程示意图；
图11为本申请实施例所提供的文件传输方法的另一流程示意图；
图12为本申请实施例所提供的文件传输方法的示例图；
图13为本申请实施例所提供的云端服务器的结构示意图；
图14为本申请实施例所提供的云端服务器的另一结构示意图；
图15为本申请实施例所提供的客户端的结构示意图；
图16为本申请实施例所提供的雾节点路由器的结构示意图；
图17示出了适于用来实现本申请实施方式的示例性电子设备的框图。
具体实施方式
下面详细描述本申请的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本申请，而不能理解为对本申请的限制。
可以理解的是，相关技术中，在手机等电子设备处在例如4G网络或非本地网络等外网环境中时，通常通过中转服务为电子设备提供外网的存储下载服务，比如，电子设备通过中转服务器从源数据服务器获取数据。而数据中转的成本很高，考虑到数据中转的成本问题，通过中转服务提供外网的存储下载服务时，通常会人为限制文件传输的速率、大小或类型，从而导致电子设备通过外网 进行文件下载或存储时易出现文件传输速率低、文件大小或类型受限的问题。
本申请主要针对相关技术中通过中转服务提供外网的存储下载服务时，易出现文件传输速率低、文件大小或类型受限的情况的技术问题，提出一种能够提高文件传输的速率，且不限制传输的文件的类型和大小的文件传输方法、云端服务器、客户端、雾节点路由器、文件传输系统、电子设备、存储介质以及计算机程序产品。
下面参考附图描述本申请实施例的文件传输方法、云端服务器、客户端、雾节点路由器、文件传输系统、电子设备、存储介质以及计算机程序产品。
首先结合图1，对本申请实施例提供的文件传输方法的应用场景进行介绍。其中，图1为本申请实施例提供的文件传输方法的应用场景的示意图。
如图1所示，用户所使用的手机、电脑等客户端，比如图1中的A1、A2和A3均对应一个与其连接的本地路由器，云端服务器C中可以预先存储每个路由器的内网地址和外网地址。本申请实施例中，针对每个客户端，可以将除该客户端对应的本地路由器之外的其它各具备外网地址的路由器作为各雾节点路由器。
以图1中客户端A1和A2为例，对于客户端A1，可以将除客户端A1对应的本地路由器B1之外的其它各具备外网地址的路由器作为各雾节点路由器，对于客户端A2，可以将除客户端A2对应的本地路由器B2之外的其它各具备外网地址的路由器作为各雾节点路由器。在客户端A1需要进行文件传输时，可以搜索与其对应的本地路由器B1，并尝试与本地路由器B1进行连接，若连接成功，即此时客户端A1的所在环境为内网环境，则通过本地路由器B1为客户端A1提供文件传输服务。在客户端A1与本地路由器B1连接失败时，比如客户端A1的网络环境为4G网络或者非本地网络时，客户端A1可以向云端服务器C发送文件传输请求，从而云端服务器C可以根据文件传输请求确定多个雾节点路由器中的目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中文件传输请求和连接请求中携带客户端A1的标识，目标雾节点路由器在接收到连接请求后，可以根据客户端A1的标识与客户端A1建立文件传输连接，并通过文件传输连接与客户端A1进行文件传输。
由此，客户端的所在环境为外网环境时，客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，由于通过雾节点路由器与客户端之间的文件传输连接进行文件传输时，充分利用了雾节点路由器的网络带宽，从而提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
下面分别以云端服务器侧、客户端侧和雾节点路由器侧为例，对本申请实施例提供的文件传输方法进行详细说明。
首先以云端服务器侧为例，对本申请实施例提供的文件传输方法进行说明。其中，本申请实施例提供的文件传输方法，被配置在云端服务器中执行。其中，云端服务器可以是中继服务器，也可以是其它类型的服务器。
图2为本申请实施例所提供的文件传输方法的流程示意图。
如图2所示，该文件传输方法可以包括以下步骤201-202。
步骤201，云端服务器接收客户端发送的文件传输请求，其中，文件传输请求携带客户端的标识。
其中，客户端，可以是个人电脑(Personal Computer，简称PC)、移动设备等，移动设备例如可以为手机、平板电脑、个人数字助理、穿戴式设备、车载设备等任意需要进行文件传输的设备。
客户端的标识，用来唯一标识客户端，其可以根据需要任意设置。
在示例性实施例中，当客户端的所在环境为外网环境时，比如客户端的网络环境为4G网络或者非本地网络时，可以向云端服务器发送文件传输请求，文件传输请求中携带客户端的标识，相应的，云端服务器可以接收客户端发送的文件传输请求。
步骤202，云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。
在示例性实施例中，云端服务器接收到文件传输请求后，可以根据文件传输请求从多个雾节点路由器中选择目标雾节点路由器，并向目标雾节点路由器发送连接请求，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，从而客户端可以通过文件传输连接与目标雾节点路由器进行文件传输。
由此，客户端与目标雾节点路由器可以通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，由于通过雾节点路由器与客户端之间的文件传输连接进行文件传输时，无需因成本原因人为限制文件传输的速率、大小或类型，能够充分利用雾节点路由器的网络带宽，从而提高了文件传输的速率，避免了对传输的文件的类型和大小的限 制，改善了用户体验。
本申请提供的文件传输方法，云端服务器接收客户端发送的携带客户端的标识的文件传输请求后，可以根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。由此，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
下面结合图3，对本申请实施例中的文件传输方法进行进一步说明。
图3为本申请实施例所提供的文件传输方法的流程示意图。如图3所示，该文件传输方法包括以下步骤301-303。
步骤301，云端服务器接收客户端发送的文件传输请求，其中，文件传输请求为文件访问请求，文件访问请求携带目标文件标识和客户端的标识，且云端服务器存储有多个文件标识和多个雾节点路由器的映射关系表。
在示例性实施例中，文件传输请求可以为文件访问请求或文件上传请求，本申请实施例以文件传输请求为文件访问请求为例进行说明。
其中，目标文件标识，用来唯一标识客户端请求访问的目标文件。
在示例性实施例中，客户端在需要访问或者下载文件时，可以向云端服务器发送文件访问请求。
步骤302，云端服务器根据目标文本标识查询映射关系表，将映射关系表中与目标文件标识对应的雾节点路由器确定为目标雾节点路由器。
在示例性实施例中，云端服务器可以预先存储多个路由器的内网地址和外网地址，并且，针对每个客户端，可以将除该客户端对应的本地路由器之外的其它各具备外网地址的路由器作为各雾节点路由器。
各雾节点路由器中分别存储有多个文件，云端服务器可以存储多个文件标识和多个雾节点路由器的映射关系表，从而在云端服务器接收到客户端发送的文件访问请求时，可以根据文件访问请求中携带的目标文本标识，查询映射关系表，从而将映射关系表中与目标文件标识对应的雾节点路由器，确定为目标雾节点路由器。
步骤303，云端服务器向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。
在示例性实施例中，云端服务器确定了目标雾节点路由器后，可以向目标雾节点路由器发送携带客户端的标识的连接请求，从而目标雾节点路由器在接收到连接请求后，可以根据连接请求中携带的客户端的标识，与客户端建立文件传输连接，进而目标雾节点路由器可以通过文件传输连接与客户端进行文件传输。
需要说明的是，文件传输请求为携带目标文件标识的文件访问请求时，云端服务器向目标雾节点路由器发送的连接请求中，除携带客户端的标识外，还可以携带目标文件标识，从而目标雾节点路由器在根据客户端的标识，与客户端建立文件传输连接后，可以直接根据目标文件标识确定目标文件，并将目标文件发送至客户端，无需客户端在文件传输连接建立后，再次将目标文件标识发送至目标雾节点路由器，从而可以节省客户端与目标雾节点路由器之间的交互次数，提高文件传输效率。
在示例性实施例中，由于云端服务器需要根据多个文件标识和多个雾节点路由器的映射关系表，确定目标雾节点路由器，相应的，云端服务器可以预先确定并存储映射关系表。即，步骤302之前，还可以包括以下步骤304-306。
步骤304，云端服务器确定多个雾节点路由器分别对应的设备等级。
在示例性实施例中，云端服务器可以确定多个雾节点路由器中的每个雾节点路由器对应的设备等级。其中，确定多个雾节点路由器分别对应的设备等级的方式可以为：云端服务器根据多个雾节点路由器的在线情况，确定多个雾节点路由器的设备质量；根据多个雾节点路由器的网络带宽，确定多个雾节点路由器的网络质量；根据设备质量和网络质量，确定多个雾节点路由器分别对应的设备等级。
在示例性实施例中，针对每个雾节点路由器，云端服务器可以以第一预设时间间隔探测该雾节点路由器是否在线，并根据雾节点路由器在第一预设时间范围内的在线情况，确定该雾节点路由器的设备质量，并且，云端服务器可以以第二预设时间间隔，探测该雾节点路由器的网络带宽，并根据雾节点路由器在第二预设时间范围内的网络带宽确定该雾节点路由器的网络质量，进而根据该雾 节点路由器的设备质量和网络质量，确定该雾节点路由器的设备等级。其中，第一预设时间间隔和第二预设时间间隔可以相同，也可以不同，且预设时间间隔的具体值，可以根据需要设置。第一预设时间范围和第二预设时间范围可以相同，也可以不同，且预设时间范围的具体值，可以根据需要设置。
举例来说，假设第一预设时间间隔和第二预设时间间隔均为3s(秒)，第一预设时间范围和第二预设时间范围为24小时。云端服务器可以为每个雾节点路由器预先设置一个设备质量度量值a以及一个网络质量度量值b，假设a的初始值为1000，b的初始值为0。
针对每个雾节点路由器，云端服务器可以以3s一次的频率探测雾节点路由器是否在线，若雾节点路由器在线，则将设备质量度量值加1，若雾节点路由器不在线，则将设备质量度量值减1000。并且，针对每个雾节点路由器，云端服务器可以以3秒一次的频率探测雾节点路由器的网络带宽，若网络带宽小于10Mbps(兆比特每秒)，则将网络质量度量值b减1，若网络带宽大于10Mbps且小于100Mbps，则将网络质量度量值加1，若网络带宽大于100Mbps且小于200Mbps，则将网络质量度量值加2，若网络带宽大于200Mbps，则将网络质量度量值加3。进而可以根据24小时后，设备质量度量值a和网络质量度量值b的数值，确定雾节点路由器的设备等级。比如，在设备质量度量值a的数值小于0，或者网络质量度量值小于0时，确定雾节点路由器的设备等级为“差”；在设备质量度量值a的数值大于0且小于10000，且网络质量度量值大于0且小于10000时，确定雾节点路由器的设备等级为“中”；在设备质量度量值a的数值大于10000且小于20000，且网络质量度量值大于0且小于10000时，确定雾节点路由器的设备等级为“良”；在设备质量度量值a的数值大于0且小于10000，且网络质量度量值大于10000且小于20000时，确定雾节点路由器的设备等级为“良”；在设备质量度量值a的数值大于20000，且网络质量度量值大于20000时，确定雾节点路由器的设备等级为“优”，等等。
步骤305，云端服务器确定多个文件标识分别对应的文件的数据类型。
在示例性实施例中，各雾节点路由器可以将其存储的各个文件的标识以及各个文件的修改时间、创建时间、当日访问量等数据传输至云端服务器，从而云端服务器可以根据各雾节点路由器发送的数据，确定各文件的数据类型。
具体的，云端服务器可以针对每个文件标识对应的文件，根据当前时间、文件的创建时间、文件的修改时间以及文件的当日访问量，确定文件的数据类型。其中，数据类型例如可以为冷数据类型、热数据类型、候选冷数据类型等。
需要说明的是，云端服务器确定各雾节点路由器中存储的文件的数据类型的频率，可以根据需要设置，比如每天确定一次，或者每两天确定一次。本申请实施例以每天确定一次各雾节点路由器中存储的文件的数据类型为例进行说明。
在示例性实施例中，云端服务器根据当前时间、文件的创建时间、文件的修改时间以及文件的当日访问量，确定文件的数据类型的过程可以包括：
云端服务器判断当前时间与文件对应的创建时间的第一差值，或者当前时间与文件对应的修改时间的第二差值，是否大于预设时间阈值；
在第一差值和第二差值均不大于预设时间阈值时，确定文件的数据类型为热数据类型；
在第一差值或第二差值大于预设时间阈值时，进一步判断文件的当日访问量是否大于等于第一预设数量阈值；
在文件的当日访问量小于第一预设数量阈值时，确定文件的数据类型为候选冷数据类型；
在预设时间段内确定文件的数据类型为候选冷数据类型的连续次数超过第一预设次数阈值时，确定文件的数据类型为冷数据类型；
在文件的当日访问量大于等于第一预设数量阈值，且文件的数据类型不为冷数据类型时，确定文件的数据类型为热数据类型；
针对当前数据类型为冷数据类型的文件，云端服务器判断文件的当日访问量是否大于等于第二预设数量阈值；
在文件的当日访问量大于等于第二预设数量阈值，且确定文件的当日访问量大于等于第二预设数量阈值的连续次数超过第二预设次数阈值时，确定文件的数据类型为热数据类型。
其中，预设时间阈值，可以根据需要设置。第一预设数量阈值和第二预设数量阈值可以为相同数值，也可以为不同数值，其具体数值可以根据需要设置，比如可以根据一天内所有文件的当日访问量的总和的平均值以及80/20法则确定。本申请实施例以第一预设数量阈值和第二预设数量阈值为不同数值为例进行说明。预设时间段，可以根据需要设置，比如可以设置为1个月，两个月，等等。
下面结合图4和图5，对本申请实施例中根据当前时间、文件的创建时间、文件的修改时间以 及文件的当日访问量，确定文件的数据类型的过程进行说明。其中，图4为本申请实施例所提供的文件传输方法中确定文件的数据类型的流程示意图。图5为本申请实施例所提供的文件传输方法中确定文件的数据类型的示例图。
需要说明的是，本申请实施例中，可以设置一个候选冷数据队列和一个冷数据队列，候选冷数据队列和冷数据队列中的每个节点分别对应一个文件，在冷数据队列中的文件的数据类型为冷数据类型，在候选冷数据队列中的文件的数据类型为候选冷数据类型。并且，对于每个文件标识，分别预先设置标志位flag1和flag2，以及时间计数count1和count2。其中，文件标识对应的flag1为true时，表示文件标识对应的文件在候选冷数据队列中，即该文件的数据类型为候选冷数据类型；文件标识对应的flag1为false时，表示文件标识对应的文件不在候选冷数据队列中，即该文件的数据类型不为候选冷数据类型。同理，文件标识对应的flag2为true时，表示文件标识对应的文件在冷数据队列中，即该文件的数据类型为冷数据类型；文件标识对应的flag2为false时，表示文件标识对应的文件不在冷数据队列中，即该文件的数据类型不为冷数据类型。count1表示文件在候选冷数据队列中的时间计数，count2表示文件在冷数据队列中的时间计数。比如，某文件标识对应的count1为2时，表示该文件标识对应的文件连续2天在候选冷数据队列中。
本申请实施例中，假设预设时间阈值为T0、第一预设数量阈值P1、第二预设数量阈值P2、第一预设次数阈值H1和第二预设次数阈值H2、当日访问量为count，T1表示文件的创建时间、T2表示文件的修改时间。
如图4所示，云端服务器可以先对T0、P1、P2、H1和H2等参数进行初始化(步骤401)。在各雾节点路由器将其存储的各个文件的标识以及各个文件的修改时间、创建时间、当日访问量等数据传输至云端服务器，相应的，云端服务器获取各雾节点路由器发送的数据后(步骤402)，云端服务器可以针对每个文件标识对应的文件，确定文件对应的数据类型。
具体的，针对每个文件标识对应的文件，云端服务器可以先判断当前时间T与文件对应的创建时间T1之间的第一差值T-T1是否大于预设时间阈值T0，或者当前时间T与文件对应的修改时间T2之间的第二差值T-T2是否大于预设时间阈值T0(步骤403)。若第一差值和第二差值均不大于预设时间阈值T0，则确定文件的数据类型为热数据类型(步骤404)。若第一差值或第二差值大于预设时间阈值T0，则进一步判断文件的当日访问量count是否大于等于第一预设数量阈值P1(步骤405)。若文件的当日访问量count小于第一预设数量阈值P1，则确定文件的数据类型为候选冷数据类型，将文件插入候选冷数据队列(步骤406)。进一步的，判断候选冷数据队列中是否已有该文件(步骤407)，在候选冷数据队列中已有该文件时，将count1加1，并且设置flag1为true(步骤408)，在候选冷数据队列中没有该文件时，将count1设置为1，并且设置flag1为true(步骤409)。针对候选冷数据队列中的文件，可以判断文件对应的count1是否大于等于第一预设次数阈值P1(步骤410)，在文件对应的count1大于等于第一预设次数阈值P1，即文件的数据类型为候选冷数据类型的连续次数超过第一预设次数阈值P1时，可以确定文件的数据类型为冷数据类型，将文件加入冷数据队列，此时设置count1为0，flag1为false，flag2为true(步骤411)。在文件的当日访问量count1大于等于第一预设数量阈值P1时，可以判断该文件是否在冷数据队列中(步骤417)，若不在，即文件的数据类型不为冷数据类型，则确定文件的数据类型为热数据类型。
对于冷数据队列中的当前数据类型为冷数据类型的文件，云端服务器可以判断文件的当日访问量count是否大于等于第二预设数量阈值P2(步骤412)。若文件的当日访问量count大于等于第二预设数量阈值P2，则将count2加1(步骤414)，并判断文件对应的count2是否大于等于第二预设次数阈值H2(步骤415)，若文件对应的count2大于等于第二预设次数阈值H2，即文件的当日访问量大于等于第二预设数量阈值P2的连续次数超过第二预设次数阈值H2，则确定文件的数据类型为热数据类型，将文件移除冷数据队列，此时count2为0，flag2为false。
需要说明的是，对于冷数据队列中的当前数据类型为冷数据类型的文件，在文件的当日访问量count大于等于第二预设数量阈值P2时，也可以先判断文件对应的count2是否大于等于第二预设次数阈值H2(步骤417)，再将count2加1(步骤420)，步骤417和步骤420的执行顺序可以根据需要设置。
通过上述过程可知，本申请实施例中，如图5所示，在当前时间T与文件对应的创建时间T1之间的第一差值T-T1，以及当前时间T与文件对应的修改时间T2之间的第二差值均不大于预设时间阈值T0时，是根据文件当日访问量是否低于第一预设数量阈值P1，确定是将文件加入候选冷数据队列还是将候选冷数据队列中的文件移除。在文件当日访问量低于第一预设数量阈值P1时，将文件加入候选冷数据队列，此时文件的数据类型为候选冷数据类型，在候选冷数据队列中的文件的当日访问量高于第一预设数量阈值P1时，将该文件移除候选冷数据队列，此时文件的数据类型为热数据类型。
对于候选冷数据队列中的文件，是根据文件的当日访问量低于第一预设数量阈值P1的连续次数是否大于等于第一预设数量阈值P1，确定是否将文件加入冷数据队列。在文件的当日访问量低于第一预设数量阈值P1的连续次数大于等于第一预设次数阈值H1时，确定将文件加入冷数据队列；在文件的当日访问量低于第一预设数量阈值P1的连续次数小于第一预设次数阈值H1时，文件继续留在候选冷数据队列中。
对于冷数据队列中的文件，是根据文件的当日访问量高于第二预设数量阈值P2的连续次数是否大于等于第二预设次数阈值H2，确定是否将文件移除冷数据队列。在文件的当日访问量高于第二预设数量阈值P2的连续次数大于等于第二预设次数阈值H2时，确定将文件移除冷数据队列；在文件的当日访问量高于第二预设数量阈值P2的连续次数小于第二预设次数阈值H2时，文件继续留在冷数据队列中。
通过上述过程，即可确定各雾节点路由器中存储的各个文件的数据类型。
步骤306，云端服务器根据多个雾节点路由器分别对应的设备等级以及多个文件标识分别对应的文件的数据类型，确定多个文件标识和多个雾节点路由器的映射关系表。
其中，不同的数据类型的文件，与不同的设备等级的雾节点路由器对应。
在示例性实施例中，云端服务器可以在确定多个雾节点路由器分别对应的设备等级以及多个文件标识分别对应的文件的数据类型后，确定将不同的数据类型的文件，存储在不同的设备等级的雾节点路由器中，进而根据多个文件标识分别对应的文件与多个雾节点路由器的存储关系，生成映射关系表。
在示例性实施例中，假设数据类型包括冷数据类型、热数据类型和候选冷数据类型，设备等级包括优、良、中、差4个等级。则云端服务器可以确定将数据类型为冷数据类型的文件，存储在设备等级为差的雾节点路由器中，将数据类型为候选冷数据类型的文件，存储在设备等级为中和良的雾节点路由器中，将数据类型为热数据类型的文件，存储在设备等级为优的雾节点路由器中，进而根据各个文件与各雾节点路由器的存储关系，生成各个文件分别对应的标识与各雾节点路由器的映射关系表。
举例来说，假设雾节点路由器B1的设备等级为优，雾节点路由器B2的设备等级为良，雾节点路由器B3的设备等级为中，雾节点路由器B4的设备等级为差。文件标识分别为X1和X2的两个文件的数据类型为热数据类型，文件标识为X3的文件的数据类型为候选冷数据类型，文件标识为X4的文件的数据类型为冷数据类型。则云端服务器可以确定将文件标识分别为X1和X2的两个文件存储在雾节点路由器B1中，将文件标识分别为X3的文件存储在雾节点路由器B3中，将文件标识为X4的文件存储在雾节点路由器B4中。进而根据各个文件与各雾节点路由器的存储关系，生成各个文件分别对应的标识与各雾节点路由器的映射关系表，其中，映射关系表中，文件标识X1和X2对应雾节点路由器B1，文件标识X3对应雾节点路由器B3，文件标识X4对应雾节点路由器B4。
通过将数据类型为热数据类型的文件，存储在设备等级最高的雾节点路由器中，能够充分利用设备等级最高的雾节点路由器的网络带宽，提高热数据类型的文件的传输速率，从而能够将最热的资源同时提供给海量客户端，满足海量客户端同时访问最热的资源的需求。
需要说明的是，本申请实施例中，云端服务器可以以预设的频率确定多个文件标识和多个雾节点路由器的映射关系表，在云端服务器当前确定的多个文件标识与多个雾节点路由器的映射关系表中，存在某一个或多个文件标识与雾节点路由器的对应关系，与上次确定的映射关系表中，该文件标识与雾节点路由器的对应关系不同时，针对每个对应关系发生变化的文件，可以将该文件的文件标识，发送至上次确定的映射关系表中该文件标识对应的原始雾节点路由器以及当前确定的映射关系表中该文件标识对应的当前雾节点路由器，从而原始雾节点路由器可以将该文件标识对应的文件发送至当前雾节点路由器，实现该文件标识对应的文件的存储位置的转换。
参考图6，云端服务器可以与多个雾节点路由器之间通过长连接的方式进行通信，多个雾节点路由器之间可以通过P2P(Point to point，点对点)方式进行通信，从而实现各雾节点路由器可以根据云端服务器确定的多个文件标识与多个雾节点路由器的映射关系表，进行各文件标识对应的文件在各雾节点路由器之间的传输。
本申请实施例提供的文件传输方法，云端服务器接收客户端发送的文件传输请求，其中，文件传输请求为文件访问请求，文件访问请求携带目标文件标识和客户端的标识，且云端服务器存储有多个文件标识和多个雾节点路由器的映射关系表，云端服务器根据目标文本标识查询映射关系表，将映射关系表中与目标文件标识对应的雾节点路由器确定为目标雾节点路由器，云端服务器向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。由此，实现了在客户端需要访问文件时，客户端通过与目标雾节点路由器之间的文件传输连接，进行文件访问，从而不需 要数据中转，即可为客户端提供外网的文件下载服务，且进行文件下载时，充分利用了雾节点路由器的网络带宽，提高了文件下载的速率，且不限制下载的文件的类型和大小，改善了用户体验。
上述实施例以文件传输请求为文件访问请求为例，对文件传输方法进行了说明，下面以文件传输请求为文件上传请求为例，对本申请实施例提供的文件传输方法进行说明。
图7为本申请实施例提供的文件传输方法的流程示意图。
如图7所示，本申请实施例提供的文件传输方法，可以包括以下步骤701-704。
步骤701，云端服务器接收客户端发送的文件传输请求，其中，文件传输请求为文件上传请求，文件上传请求携带客户端的标识。
步骤702，云端服务器根据客户端的标识，确定客户端与多个雾节点路由器之间的通信质量等级。
步骤703，云端服务器根据客户端与多个雾节点路由器之间的通信质量等级，从多个雾节点路由器中选择目标雾节点路由器。
在示例性实施例中，客户端在需要进行文件存储时，可以向云端服务器发送文件上传请求，文件上传请求中携带客户端的标识，从而云端服务器可以根据客户端的标识，确定客户端与多个雾节点路由器之间的通信质量等级，进而根据客户端与多个雾节点路由器之间的通信质量等级，从多个雾节点路由器中选择目标雾节点路由器。
在示例性实施例中，云端服务器可以根据客户端的标识，确定客户端的类型、网络运营商、所在位置等信息，并且，可以确定每个雾节点路由器的所在位置以及对应的网络运营商等信息，进而针对每个雾节点路由器，可以根据客户端的类型、网络运营商、所在位置等信息、以及雾节点路由器的所在位置和对应的网络运营商等信息，确定客户端与雾节点路由器之间的网络质量高低，进而根据客户端与多个雾节点路由器之间的通信质量高低，为客户端与每个雾节点路由器之间的通信质量划分等级，并将通信质量等级最高的雾节点路由器确定为目标雾节点路由器。
举例来说，假设客户端为手机，客户端的所在位置为M1地区，网络运营商为运营商N，雾节点路由器B1的所在位置为M1地区，网络运营商为运营商N1，雾节点路由器B2的所在位置为M2地区，且M2地区与M1地区距离很远，雾节点路由器B2的网络运营商为运营商N2。则云端服务器可以根据客户端的所在位置、网络运营上，以及雾节点路由器B1和B2的所在位置和网络运营商，确定客户端与雾节点路由器B1的通信质量优于客户端与雾节点路由器B2的通信质量，从而将雾节点路由器B1确定为目标雾节点路由器。
步骤704，云端服务器向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。
在示例性实施例中，文件传输请求为文件上传请求时，云端服务器向目标雾节点路由器发送的连接请求中，可以仅包括客户端的标识，从而目标雾节点路由器可以根据客户端的标识与客户端建立文件传输连接，在文件传输连接建立后，再由客户端通过文件传输连接向目标雾节点路由器发送目标文件及目标文件对应的标识。
或者，云端服务器向目标雾节点路由器发送的连接请求中，除包括客户端的标识外，还可以携带目标文件标识，从而目标雾节点路由器在根据连接请求中携带的客户端的标识，与客户端建立文件传输连接后，客户端可以直接向目标雾节点路由器发送目标文件标识对应的目标文件。
本申请实施例提供的文件传输方法，云端服务器接收客户端发送的文件传输请求后，其中，文件传输请求为文件上传请求，文件上传请求携带客户端的标识,云端服务器根据客户端的标识，确定客户端与多个雾节点路由器之间的通信质量等级,再根据客户端与多个雾节点路由器之间的通信质量等级，从多个雾节点路由器中选择目标雾节点路由器，进而向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。由此，实现了在客户端需要上传文件时，客户端通过与目标雾节点路由器之间的文件传输连接，进行文件上传，从而不需要数据中转，即可为客户端提供外网的文件存储服务，且进行文件上传时，充分利用了雾节点路由器的网络带宽，提高了文件上传的速率，且不限制上传的文件的类型和大小，改善了用户体验。
下面以客户端侧为例，对本申请实施例提供的文件传输方法进行说明。
图8为本申请实施例所提供的文件传输方法的流程示意图。
其中，本申请实施例提供的文件传输方法，被配置在客户端中执行。其中，可以理解的是，本申请提供的文件传输方法可以应用于向多个客户端提供外网的存储下载服务的场景，本申请实施例中客户端可以为多个客户端中的任一客户端。
其中，客户端可以是个人电脑(Personal Computer，简称PC)、移动设备等，移动设备例如可 以为手机、平板电脑、个人数字助理、穿戴式设备、车载设备等任意需要进行文件传输的设备。
如图8所示，该文件传输方法可以包括以下步骤801-802。
步骤801，客户端向云端服务器发送文件传输请求，以使云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识。
其中，客户端的标识，用来唯一标识客户端，其可以根据需要任意设置。
在示例性实施例中，当客户端的所在环境为外网环境时，比如客户端的网络环境为4G网络或者非本地网络时，可以向云端服务器发送文件传输请求，文件传输请求中携带客户端的标识，从而使云端服务器可以根据文件传输请求从多个雾节点路由器中确定目标雾节点路由器，以及使云端服务器可以向目标雾节点路由器发送连接请求，其中，连接请求中携带客户端的标识，从而使目标雾节点路由器可以根据连接请求中的客户端的标识与客户端建立文件传输连接。
在示例性实施例中，云端服务器根据文件传输请求确定目标雾节点路由器的方式，可以参考上述实施例，此次不再赘述。
步骤802，在客户端根据客户端的标识与目标雾节点路由器建立文件传输连接后，通过文件传输连接进行文件传输。
在示例性实施例中，目标雾节点路由器根据客户端的标识与客户端建立文件传输连接后，客户端即可通过文件传输连接与目标雾节点路由器进行文件传输。
由此，客户端与目标雾节点路由器可以通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，由于通过雾节点路由器与客户端之间的文件传输连接进行文件传输时，无需因成本原因人为限制文件传输的速率、大小或类型，能够充分利用雾节点路由器的网络带宽，从而提高了文件传输的速率，避免了对传输的文件的类型和大小的限制，改善了用户体验。
本申请实施例提供的文件传输方法，客户端向云端服务器发送文件传输请求，以使云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识，在客户端根据客户端的标识与目标雾节点路由器建立文件传输连接后，通过文件传输连接进行文件传输，由此，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
下面结合图9，对本申请实施例提供的客户端侧执行的文件传输方法进行进一步说明。
图9为本申请实施例所提供的文件传输方法的流程示意图。
如图9所示，本申请实施例所提供的文件传输方法，包括以下步骤901-904。
步骤901，客户端确定所在环境是否为外网环境，若是，则执行步骤902，否则，执行步骤904。
步骤802，客户端向云端服务器发送文件传输请求，以使云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识。
步骤903，在客户端根据客户端的标识与目标雾节点路由器建立文件传输连接后，通过文件传输连接进行文件传输。
在示例性实施例中，当客户端的所在环境为外网环境时，比如客户端的网络环境为4G网络或者非本地网络时，可以向云端服务器发送文件传输请求，文件传输请求中携带客户端的标识，从而使云端服务器可以根据文件传输请求，从多个雾节点路由器中确定目标雾节点路由器，以及使云端服务器可以向目标雾节点路由器发送连接请求，其中，连接请求中携带客户端的标识，从而使目标雾节点路由器可以根据连接请求中的客户端的标识与客户端建立文件传输连接。
在示例性实施例中，文件传输请求可以为文件访问请求或文件上传请求。
在示例性实施例中，客户端在需要访问或者下载文件时，可以向云端服务器发送文件访问请求，文件访问请求中携带客户端的标识以及目标文件标识。云端服务器可以预先存储多个文件标识和多个雾节点路由器的映射关系表，从而在云端服务器接收到客户端发送的文件访问请求时，可以根据文件访问请求中携带的目标文本标识，查询映射关系表，并将映射关系表中与目标文件标识对应的雾节点路由器，确定为目标雾节点路由器。云端服务器确定了目标雾节点路由器后，可以向目标雾节点路由器发送携带客户端的标识的连接请求，从而目标雾节点路由器在接收到连接请求后，可以根据连接请求中携带的客户端的标识，与客户端建立文件传输连接，进而目标雾节点路由器可以通过文件传输连接与客户端进行文件传输。
需要说明的是，文件传输请求为携带目标文件标识的文件访问请求时，云端服务器向目标雾节 点路由器发送的连接请求中，除携带客户端的标识外，还可以携带目标文件标识，从而目标雾节点路由器在根据客户端的标识，与客户端建立文件传输连接后，可以直接根据目标文件标识确定目标文件，并通过文件传输连接将目标文件发送至客户端，相应的，客户端可以通过文件传输连接，直接接收目标雾节点路由器发送的目标文件标识对应的目标文件，无需客户端在文件传输连接建立后，再次将目标文件标识发送至目标雾节点路由器，从而可以节省客户端与目标雾节点路由器之间的交互次数，提高文件传输效率。
在示例性实施例中，客户端在需要进行文件存储时，可以向云端服务器发送文件上传请求，文件上传请求中携带客户端的标识，从而云端服务器可以根据客户端的标识，确定客户端与多个雾节点路由器之间的通信质量等级，进而根据客户端与多个雾节点路由器之间的通信质量等级，从多个雾节点路由器中选择目标雾节点路由器。
在示例性实施例中，文件传输请求为文件上传请求时，云端服务器向目标雾节点路由器发送的连接请求中，可以仅包括客户端的标识，从而目标雾节点路由器可以根据客户端的标识与客户端建立文件传输连接，在文件传输连接建立后，再由客户端通过文件传输连接，将目标文件标识及目标文件标识对应的目标文件方式至目标雾节点路由器。
或者，云端服务器向目标雾节点路由器发送的连接请求中，除包括客户端的标识外，还可以携带目标文件标识，从而目标雾节点路由器在根据连接请求中携带的客户端的标识，与客户端建立文件传输连接后，客户端可以直接向目标雾节点路由器发送目标文件标识对应的目标文件。
步骤904，客户端与本地路由器通过客户端与本地路由器之间的文件传输连接进行文件传输。
在示例性实施例中，客户端的所在环境为内网环境时，客户端可以与本地路由器通过客户端与本地路由器之间的文件传输连接进行文件传输。具体的，客户端可以从本地路由器下载文件或者将文件传输至本地路由器。
本申请实施例提供的文件传输方法，客户端的所在环境为外网环境时，可以向云端服务器发送文件传输请求，以使云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识，在客户端根据客户端的标识与目标雾节点路由器建立文件传输连接后，客户端可以通过文件传输连接与目标雾节点路由器进行文件传输，在客户端的所在环境为内网环境时，客户端与本地路由器通过客户端与本地路由器之间的文件传输连接进行文件传输。由此，实现了客户端根据所在网络环境，利用对应的文件传输连接进行文件传输，由于客户端所在环境为外网环境时，客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
下面以雾节点路由器侧为例，对本申请实施例提供的文件传输方法进行说明。
图10为本申请实施例所提供的文件传输方法的流程示意图。
其中，本申请实施例提供的文件传输方法，被配置在雾节点路由器中执行。其中，可以理解的是，本申请实施例中雾节点路由器具体为前述实施例中向客户端提供外网的文件存储下载服务的目标雾节点路由器。
如图10所示，该文件传输方法可以包括以下步骤1001-1003。
步骤1001，雾节点路由器接收云端服务器发送的连接请求，其中，连接请求是云端服务器在接收到客户端向云端服务器发送的文件传输请求后发送至雾节点路由器的，文件传输请求和连接请求携带客户端的标识。
步骤1002，雾节点路由器根据客户端的标识，与客户端建立文件传输连接。
其中，客户端可以是个人电脑(Personal Computer，简称PC)、移动设备等，移动设备例如可以为手机、平板电脑、个人数字助理、穿戴式设备、车载设备等任意需要进行文件传输的设备。
在示例性实施例中，当客户端的所在环境为外网环境时，比如客户端的网络环境为4G网络或者非本地网络时，可以向云端服务器发送文件传输请求，文件传输请求中携带客户端的标识，从而使云端服务器可以根据文件传输请求从多个雾节点路由器中确定目标雾节点路由器，以及使云端服务器可以向目标雾节点路由器发送连接请求，其中，连接请求中携带客户端的标识。目标雾节点路由器在接收到云端服务器发送的连接请求后，即可根据客户端的标识，与客户端建立文件传输连接。
在示例性实施例中，云端服务器根据文件传输请求确定目标雾节点路由器的方式，可以参考上述实施例，此次不再赘述。
步骤1003，雾节点路由器与客户端通过文件传输连接进行文件传输。
在示例性实施例中，目标雾节点路由器根据客户端的标识与客户端建立文件传输连接后，目标雾节点即可通过文件传输连接与客户端进行文件传输。
由此，客户端与目标雾节点路由器可以通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，由于通过雾节点路由器与客户端之间的文件传输连接进行文件传输时，无需因成本原因人为限制文件传输的速率、大小或类型，能够充分利用雾节点路由器的网络带宽，从而提高了文件传输的速率，避免了对传输的文件的类型和大小的限制，改善了用户体验。
本申请实施例提供的文件传输方法，雾节点路由器接收云端服务器发送的连接请求后，根据客户端的标识，与客户端建立文件传输连接，进而雾节点路由器与客户端通过文件传输连接进行文件传输，由此，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
下面结合图11，对本申请实施例提供的雾节点路由器侧执行的文件传输方法进一步说明。
图11为本申请实施例所提供的文件传输方法的流程示意图。
如图11所示，本申请实施例所提供的文件传输方法包括以下步骤1101-1104。
步骤1101，雾节点路由器接收云端服务器发送的连接请求，其中，连接请求是云端服务器在接收到客户端向云端服务器发送的文件传输请求后发送至雾节点路由器的，文件传输请求为文件访问请求，文件访问请求和连接请求携带客户端的标识和目标文件标识，且雾节点路由器存储有多个文件标识分别对应的文件。
在示例性实施例中，雾节点路由器，为除客户端对应的本地路由器之外的其它路由器中、具备外网地址的路由器。
步骤1102，雾节点路由器根据客户端的标识，与客户端建立文件传输连接。
在示例性实施例中，当客户端的所在环境为外网环境时，比如客户端的网络环境为4G网络或者非本地网络时，可以向云端服务器发送文件传输请求，文件传输请求中携带客户端的标识，从而使云端服务器可以根据文件传输请求，从多个雾节点路由器中确定目标雾节点路由器，以及使云端服务器可以向目标雾节点路由器发送连接请求，其中，连接请求中携带客户端的标识，从而目标雾节点路由器可以根据连接请求中的客户端的标识与客户端建立文件传输连接。
步骤1103，雾节点路由器根据目标文件标识，查找目标文件标识对应的目标文件。
步骤1104，雾节点路由器通过文件传输连接，将目标文件发送至客户端。
在示例性实施例中，文件传输请求和连接请求中除了携带客户端的标识，还可以携带目标文件标识，目标雾节点路由器在与客户端建立文件传输连接后，可以根据目标文件标识查询目标雾节点路由器中存储的多个文件标识分别对应的文件，以查找目标文件标识对应的目标文件，进而可以将目标文件标识对应的目标文件，通过文件传输连接，发送至客户端。
在示例性实施例中，文件传输请求为文件上传请求时，文件上传请求和连接请求中可以携带客户端的标识以及目标文件标识，从而目标雾节点路由器在与客户端建立文件传输连接后，客户端可以通过文件传输连接，向目标雾节点路由器发送文件标识及文件标识对应的目标文件，相应的，目标雾节点路由器可以通过文件传输连接，接收客户端发送的目标文件标识对应的目标文件。
在示例性实施例中，多个雾节点路由器中的某一个或多个雾节点路由器，还可以与客户端对应的本地路由器之间进行数据同步，其中，同步的数据可以为客户端对应的本地路由器中的最热的文件，从而在客户端与对应的本地路由器之间的文件传输连接断开时，客户端可以从雾节点路由器中获取对于持有客户端的用户来说最热的文件。即本申请实施例中，还可以包括：雾节点路由器与客户端对应的本地路由器进行数据同步。
参考图12，客户端对应的本地路由器可以将本地路由器中存储的最热的文件同步到某一个或多个雾节点路由器中。其中，如图6所示，本地路由器可以与雾节点路由器之间通过P2P方式进行数据同步。在客户端与本地路由器处于连接状态时，客户端可以从本地路由器中下载最热的文件或者将目标文件上传至本地路由器。在客户端与本地路由器的文件传输连接断开时，客户端可以向云端服务器发送文件传输请求，(图12中未示出)，从而云端服务器可以根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，进而目标雾节点路由器可以根据连接请求与客户端建立文件传输连接。在客户端与目标雾节点路由器建立文件传输连接后，客户端即可通过文件传输连接从目标雾节点路由器中下载对客户端用户来说最热的文件或者将目标文件上传至目标雾节点路由器。
本申请实施例提供的文件传输方法，雾节点路由器接收云端服务器发送的连接请求后，根据客户端的标识，与客户端建立文件传输连接，进而雾节点路由器根据目标文件标识，查找目标文件标识对应的目标文件，通过文件传输连接，将目标文件发送至客户端，由此，实现了客户端与目标雾 节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
图13为本申请实施例所提供的云端服务器的结构示意图。
如图13所示，该云端服务器1300可以包括：接收模块1310和第一确定模块1320。
其中，接收模块1310，用于接收客户端发送的文件传输请求，其中，文件传输请求携带客户端的标识；
第一确定模块1320，用于根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。
进一步地，在本申请实施例的一种可能的实现方式中，文件传输请求为文件访问请求，文件访问请求携带目标文件标识，且云端服务器存储有多个文件标识和多个雾节点路由器的映射关系表；
其中，第一确定模块1320，具体用于：
根据目标文本标识查询映射关系表，将映射关系表中与目标文件标识对应的雾节点路由器确定为目标雾节点路由器。
进一步地，在本申请实施例的一种可能的实现方式中，如图14所示，云端服务器1300，还可以包括：
第二确定模块1330，用于确定多个雾节点路由器分别对应的设备等级；
第三确定模块1340，用于确定多个文件标识分别对应的文件的数据类型；
第四确定模块1350，用于根据多个雾节点路由器分别对应的设备等级以及多个文件标识分别对应的文件的数据类型，确定多个文件标识和多个雾节点路由器的映射关系表，其中，不同的数据类型的文件，与不同的设备等级的雾节点路由器对应。
进一步地，在本申请实施例的一种可能的实现方式中，第四确定模块1350，具体用于：
根据多个雾节点路由器分别对应的设备等级以及多个文件标识分别对应的文件的数据类型，确定将不同的数据类型的文件存储在不同的设备等级的雾节点路由器中；
根据多个文件标识分别对应的文件与多个雾节点路由器的存储关系，生成映射关系表。
进一步地，在本申请实施例的一种可能的实现方式中，第二确定模块1330，具体用于：
根据多个雾节点路由器的在线情况，确定多个雾节点路由器的设备质量；
根据多个雾节点路由器的网络带宽，确定多个雾节点路由器的网络质量；
根据设备质量和网络质量，确定多个雾节点路由器分别对应的设备等级。
进一步地，在本申请实施例的一种可能的实现方式中，第三确定模块1340，包括：
确定单元，用于针对每个文件标识对应的文件，根据当前时间、文件的创建时间、文件的修改时间以及文件的当日访问量，确定文件的数据类型。
进一步地，在本申请实施例的一种可能的实现方式中，数据类型包括冷数据类型、热数据类型和候选冷数据类型；其中，确定单元，具体用于：
判断当前时间与文件对应的创建时间的第一差值，或者当前时间与文件对应的修改时间的第二差值，是否大于预设时间阈值；
在第一差值和第二差值均不大于预设时间阈值时，确定文件的数据类型为热数据类型；
在第一差值或第二差值大于预设时间阈值时，进一步判断文件的当日访问量是否大于等于第一预设数量阈值；
在文件的当日访问量小于第一预设数量阈值时，确定文件的数据类型为候选冷数据类型；
在预设时间段内确定文件的数据类型为候选冷数据类型的连续次数超过第一预设次数阈值时，确定文件的数据类型为冷数据类型；
在文件的当日访问量大于等于第一预设数量阈值，且文件的数据类型不为冷数据类型时，确定文件的数据类型为热数据类型；
针对当前数据类型为冷数据类型的文件，判断文件的当日访问量是否大于等于第二预设数量阈值；
在文件的当日访问量大于等于第二预设数量阈值，且确定文件的当日访问量大于等于第二预设数量阈值的连续次数超过第二预设次数阈值时，确定文件的数据类型为热数据类型。
进一步地，在本申请实施例的一种可能的实现方式中，文件传输请求为文件上传请求；
其中，第一确定模块1220，具体用于：
根据客户端的标识，确定客户端与多个雾节点路由器之间的通信质量等级；
根据客户端与多个雾节点路由器之间的通信质量等级，从多个雾节点路由器中选择目标雾节点 路由器。
需要说明的是，前述云端服务器侧执行的文件传输方法实施例中的解释说明也适用于该实施例的云端服务器，此处不再赘述。
本申请实施例的云端服务器，接收客户端发送的携带客户端的标识的文件传输请求后，可以根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，连接请求携带客户端的标识，以使目标雾节点路由器根据客户端的标识与客户端建立文件传输连接，并通过文件传输连接进行文件传输。由此，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
为了实现上述实施例，本申请实施例还提供一种客户端。图15为本申请实施例所提供的客户端的结构示意图。
如图15所示，该客户端1500可以包括：发送模块1510和第一传输模块1520。
其中，发送模块1510，用于向云端服务器发送文件传输请求，以使云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识；
第一传输模块1520，用于在客户端根据客户端的标识与目标雾节点路由器建立文件传输连接后，通过文件传输连接进行文件传输。
进一步地，在本申请实施例的一种可能的实现方式中，文件传输请求为文件访问请求，文件访问请求和连接请求携带目标文件标识；
相应的，第一传输模块1520，具体用于：
通过文件传输连接，接收目标雾节点路由器发送的目标文件标识对应的目标文件。
进一步地，在本申请实施例的一种可能的实现方式中，文件传输请求为文件上传请求，文件上传请求和连接请求携带目标文件标识；
相应的，第一传输模块1520，具体用于：
通过文件传输连接，将目标文件标识对应的目标文件发送至目标雾节点路由器。
进一步地，在本申请实施例的一种可能的实现方式中，客户端还可以包括：
第二传输模块，用于在客户端的所在环境为内网环境时，与本地路由器通过客户端与本地路由器之间的文件传输连接进行文件传输。
需要说明的是，前述客户端侧执行的文件传输方法实施例中的解释说明也适用于该实施例的客户端，此处不再赘述。
本申请实施例的客户端，可以向云端服务器发送文件传输请求，以使云端服务器根据文件传输请求确定目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识，在客户端根据客户端的标识与目标雾节点路由器建立文件传输连接后，通过文件传输连接进行文件传输，由此，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
为了实现上述实施例，本申请实施例还提供一种雾节点路由器。图16为本申请实施例所提供的雾节点路由器的结构示意图。
如图16所示，该雾节点路由器1600可以包括：接收模块1610、建立模块1620和传输模块1630。
其中，接收模块1610，用于接收云端服务器发送的连接请求，其中，连接请求是云端服务器在接收到客户端向云端服务器发送的文件传输请求后发送至雾节点路由器的，文件传输请求和连接请求携带客户端的标识；
建立模块1620，用于根据客户端的标识，与客户端建立文件传输连接；
传输模块1630，用于与客户端通过文件传输连接进行文件传输。
进一步地，在本申请实施例的一种可能的实现方式中，雾节点路由器，为除客户端对应的本地路由器之外的其它路由器中、具备外网地址的路由器。
进一步地，在本申请实施例的一种可能的实现方式中，文件传输请求为文件访问请求，文件访问请求和连接请求携带目标文件标识，且雾节点路由器存储有多个文件标识分别对应的文件；
相应的，传输模块1630，具体用于：
根据目标文件标识，查找目标文件标识对应的目标文件；
通过文件传输连接，将目标文件发送至客户端。
进一步地，在本申请实施例的一种可能的实现方式中，文件传输请求为文件上传请求，文件上传请求和连接请求携带目标文件标识；
相应的，传输模块1630，具体用于：
通过文件传输连接，接收客户端发送的目标文件标识对应的目标文件。
进一步地，在本申请实施例的一种可能的实现方式中，雾节点路由器还可以包括：
同步模块，用于与客户端对应的本地路由器进行数据同步。
需要说明的是，前述雾节点路由器侧执行的文件传输方法实施例中的解释说明也适用于该实施例的雾节点路由器，此处不再赘述。
本申请实施例的雾节点路由器，接收云端服务器发送的连接请求后，根据客户端的标识，与客户端建立文件传输连接，进而雾节点路由器与客户端通过文件传输连接进行文件传输，由此，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
为了实现上述实施例，本申请还提出一种文件传输系统，包括客户端、云端服务器以及多个雾节点路由器。
其中，云端服务器，用于接收客户端发送的文件传输请求，以及根据文件传输请求确定多个雾节点路由器中的目标雾节点路由器，并向目标雾节点路由器发送连接请求，其中，文件传输请求和连接请求携带客户端的标识；
目标雾节点路由器，用于在接收到连接请求后，根据客户端的标识，与客户端建立文件传输连接，以及与客户端通过文件传输连接进行文件传输；
客户端，用于向云端服务器发送文件传输请求，以及与目标雾节点路由器通过文件传输连接进行文件传输。
需要说明的是，上述实施例中对云端服务器、客户端以及雾节点路由器的说明，也适用于本申请实施例的文件传输系统中的云端服务器、客户端和多个雾节点路由器中的目标雾节点路由器，此处不再赘述。
本申请实施例提供的文件传输系统，实现了客户端与目标雾节点路由器通过两者之间的文件传输连接，进行文件传输，从而不需要数据中转，即可为客户端提供外网的文件传输服务，且进行文件传输时，充分利用了雾节点路由器的网络带宽，提高了文件传输的速率，且不限制传输的文件的类型和大小，改善了用户体验。
为了实现上述实施例，本申请还提出一种电子设备，包括：至少一个处理器；以及与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如本申请前述任一实施例提出的文件传输方法。
为了实现上述实施例，本申请还提出一种存储有计算机指令的非瞬时计算机可读存储介质，所述计算机指令用于使所述计算机执行如本申请前述任一实施例提出的文件传输方法。
为了实现上述实施例，本申请还提出一种计算机程序产品，包括计算机程序，所述计算机程序在被处理器执行时实现如本申请前述任一实施例提出的文件传输方法。
图17示出了适于用来实现本申请实施方式的示例性电子设备的框图。图17显示的电子设备1700仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。其中，电子设备可以是云端服务器、客户端或者雾节点路由器。
如图17所示，电子设备1700以通用计算设备的形式表现。电子设备1700的组件可以包括但不限于：一个或者多个处理器或者处理单元16，系统存储器28，连接不同系统组件(包括系统存储器28和处理单元16)的总线18。
总线18表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器，外围总线，图形加速端口，处理器或者使用多种总线结构中的任意总线结构的局域总线。举例来说，这些体系结构包括但不限于工业标准体系结构(Industry Standard Architecture；以下简称：ISA)总线，微通道体系结构(Micro Channel Architecture；以下简称：MAC)总线，增强型ISA总线、视频电子标准协会(Video Electronics Standards Association；以下简称：VESA)局域总线以及外围组件互连(Peripheral Component Interconnection；以下简称：PCI)总线。
电子设备1700典型地包括多种计算机系统可读介质。这些介质可以是任何能够被电子设备1700访问的可用介质，包括易失性和非易失性介质，可移动的和不可移动的介质。
存储器28可以包括易失性存储器形式的计算机系统可读介质，例如随机存取存储器(Random Access Memory；以下简称：RAM)30和/或高速缓存存储器32。电子设备1700可以进一步包括其 它可移动/不可移动的、易失性/非易失性计算机系统存储介质。仅作为举例，存储系统34可以用于读写不可移动的、非易失性磁介质(图17未显示，通常称为“硬盘驱动器”)。尽管图17中未示出，可以提供用于对可移动非易失性磁盘(例如“软盘”)读写的磁盘驱动器，以及对可移动非易失性光盘(例如：光盘只读存储器(Compact Disc Read Only Memory；以下简称：CD-ROM)、数字多功能只读光盘(Digital Video Disc Read Only Memory；以下简称：DVD-ROM)或者其它光介质)读写的光盘驱动器。在这些情况下，每个驱动器可以通过一个或者多个数据介质接口与总线18相连。存储器28可以包括至少一个程序产品，该程序产品具有一组(例如至少一个)程序模块，这些程序模块被配置以执行本申请各实施例的功能。
具有一组(至少一个)程序模块42的程序/实用工具40，可以存储在例如存储器28中，这样的程序模块42包括但不限于操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。程序模块42通常执行本申请所描述的实施例中的功能和/或方法。
电子设备1700也可以与一个或多个外部设备14(例如键盘、指向设备、显示器24等)通信，还可与一个或者多个使得用户能与该电子设备1700交互的设备通信，和/或与使得该电子设备1700能与一个或多个其它计算设备进行通信的任何设备(例如网卡，调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口22进行。并且，电子设备1700还可以通过网络适配器20与一个或者多个网络(例如局域网(Local Area Network；以下简称：LAN)，广域网(Wide Area Network；以下简称：WAN)和/或公共网络，例如因特网)通信。如图所示，网络适配器20通过总线18与电子设备1700的其它模块通信。应当明白，尽管图17中未示出，可以结合电子设备1700使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
处理单元16通过运行存储在系统存储器28中的程序，从而执行各种功能应用以及数据处理，例如实现前述实施例中提及的方法。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本申请的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不必须针对的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任一个或多个实施例或示例中以合适的方式结合。此外，在不相互矛盾的情况下，本领域的技术人员可以将本说明书中描述的不同实施例或示例以及不同实施例或示例的特征进行结合和组合。
此外，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。在本申请的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。
流程图中或在此以其他方式描述的任何过程或方法描述可以被理解为，表示包括一个或更多个用于实现定制逻辑功能或过程的步骤的可执行指令的代码的模块、片段或部分，并且本申请的实施方式的范围包括另外的实现，其中可以不按所示出或讨论的顺序，包括根据所涉及的功能按基本同时的方式或按相反的顺序，来执行功能，这应被本申请的实施例所属技术领域的技术人员所理解。
在流程图中表示或在此以其他方式描述的逻辑和/或步骤，例如，可以被认为是用于实现逻辑功能的可执行指令的定序列表，可以具体实现在任何计算机可读介质中，以供指令执行系统、装置或设备(如基于计算机的系统、包括处理器的系统或其他可以从指令执行系统、装置或设备取指令并执行指令的系统)使用，或结合这些指令执行系统、装置或设备而使用。就本说明书而言，"计算机可读介质"可以是任何可以包含、存储、通信、传播或传输程序以供指令执行系统、装置或设备或结合这些指令执行系统、装置或设备而使用的装置。计算机可读介质的更具体的示例(非穷尽性列表)包括以下：具有一个或多个布线的电连接部(电子装置)，便携式计算机盘盒(磁装置)，随机存取存储器(RAM)，只读存储器(ROM)，可擦除可编辑只读存储器(EPROM或闪速存储器)，光纤装置，以及便携式光盘只读存储器(CDROM)。另外，计算机可读介质甚至可以是可在其上打印所述程序的纸或其他合适的介质，因为可以例如通过对纸或其他介质进行光学扫描，接着进行编辑、解译或必要时以其他合适方式进行处理来以电子方式获得所述程序，然后将其存储在计算机存储器中。
应当理解，本申请的各部分可以用硬件、软件、固件或它们的组合来实现。在上述实施方式中，多个步骤或方法可以用存储在存储器中且由合适的指令执行系统执行的软件或固件来实现。如，如果用硬件来实现和在另一实施方式中一样，可用本领域公知的下列技术中的任一项或他们的组合来实现：具有用于对数据信号实现逻辑功能的逻辑门电路的离散逻辑电路，具有合适的组合逻辑门电 路的专用集成电路，可编程门阵列(PGA)，现场可编程门阵列(FPGA)等。
本技术领域的普通技术人员可以理解实现上述实施例方法携带的全部或部分步骤是可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，该程序在执行时，包括方法实施例的步骤之一或其组合。
此外，在本申请各个实施例中的各功能单元可以集成在一个处理模块中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。
上述提到的存储介质可以是只读存储器，磁盘或光盘等。尽管上面已经示出和描述了本申请的实施例，可以理解的是，上述实施例是示例性的，不能理解为对本申请的限制，本领域的普通技术人员在本申请的范围内可以对上述实施例进行变化、修改、替换和变型。

Claims (37)

  1. 一种文件传输方法，包括：
    云端服务器接收客户端发送的文件传输请求，其中，所述文件传输请求携带所述客户端的标识；
    所述云端服务器根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述连接请求携带所述客户端的标识，以使所述目标雾节点路由器根据所述客户端的标识与所述客户端建立文件传输连接，并通过所述文件传输连接进行文件传输。
  2. 根据权利要求1所述的方法，其中，所述文件传输请求为文件访问请求，所述文件访问请求携带目标文件标识，且所述云端服务器存储有多个文件标识和多个雾节点路由器的映射关系表；
    其中，所述云端服务器根据所述文件传输请求确定目标雾节点路由器，包括：
    所述云端服务器根据所述目标文本标识查询所述映射关系表，将所述映射关系表中与所述目标文件标识对应的雾节点路由器确定为所述目标雾节点路由器。
  3. 根据权利要求2所述的方法，其中，在所述云端服务器根据所述文件传输请求确定目标雾节点路由器之前，还包括：
    所述云端服务器确定所述多个雾节点路由器分别对应的设备等级；
    所述云端服务器确定所述多个文件标识分别对应的文件的数据类型；
    所述云端服务器根据所述多个雾节点路由器分别对应的设备等级以及所述多个文件标识分别对应的文件的数据类型，确定所述多个文件标识和多个雾节点路由器的映射关系表，其中，不同的所述数据类型的文件，与不同的所述设备等级的所述雾节点路由器对应。
  4. 根据权利要求3所述的方法，其中，所述确定所述多个文件标识和多个雾节点路由器的映射关系表，包括：
    所述云端服务器根据所述多个雾节点路由器分别对应的设备等级以及所述多个文件标识分别对应的文件的数据类型，确定将不同的所述数据类型的文件存储在不同的所述设备等级的所述雾节点路由器中；
    所述云端服务器根据所述多个文件标识分别对应的文件与所述多个雾节点路由器的存储关系，生成所述映射关系表。
  5. 根据权利要求3所述的方法，其中，所述云端服务器确定所述多个雾节点路由器分别对应的设备等级，包括：
    所述云端服务器根据所述多个雾节点路由器的在线情况，确定所述多个雾节点路由器的设备质量；
    根据所述多个雾节点路由器的网络带宽，确定所述多个雾节点路由器的网络质量；
    根据所述设备质量和所述网络质量，确定所述多个雾节点路由器分别对应的所述设备等级。
  6. 根据权利要求3所述的方法，其中，所述云端服务器确定所述多个文件标识分别对应的文件的数据类型，包括：
    针对每个所述文件标识对应的文件，所述云端服务器根据当前时间、所述文件的创建时间、所述文件的修改时间以及所述文件的当日访问量，确定所述文件的数据类型。
  7. 根据权利要求6所述的方法，其中，所述数据类型包括冷数据类型、热数据类型和候选冷数据类型；其中，所述云端服务器根据当前时间、所述文件的创建时间、所述文件的修改时间以及所述文件的当日访问量，确定所述文件的数据类型，包括：
    所述云端服务器判断所述当前时间与所述文件对应的创建时间的第一差值，或者所述当前时间与所述文件对应的修改时间的第二差值，是否大于预设时间阈值；
    在所述第一差值和所述第二差值均不大于所述预设时间阈值时，确定所述文件的数据类型为所述热数据类型；
    在所述第一差值或所述第二差值大于所述预设时间阈值时，进一步判断所述文件的当日访问量是否大于等于第一预设数量阈值；
    在所述文件的当日访问量小于所述第一预设数量阈值时，确定所述文件的数据类型为所述候选冷数据类型；
    在预设时间段内确定所述文件的数据类型为所述候选冷数据类型的连续次数超过第一预设次数阈值时，确定所述文件的数据类型为所述冷数据类型；
    在所述文件的当日访问量大于等于所述第一预设数量阈值，且所述文件的数据类型不为所述冷数据类型时，确定所述文件的数据类型为所述热数据类型；
    针对当前数据类型为所述冷数据类型的文件，所述云端服务器判断所述文件的当日访问量是否大于等于第二预设数量阈值；
    在所述文件的当日访问量大于等于所述第二预设数量阈值，且确定所述文件的当日访问量大于 等于所述第二预设数量阈值的连续次数超过第二预设次数阈值时，确定所述文件的数据类型为所述热数据类型。
  8. 根据权利要求1所述的方法，其中，所述文件传输请求为文件上传请求；
    其中，所述云端服务器根据所述文件传输请求确定目标雾节点路由器，包括：
    所述云端服务器根据所述客户端的标识，确定所述客户端与多个雾节点路由器之间的通信质量等级；
    根据所述客户端与所述多个雾节点路由器之间的所述通信质量等级，从所述多个雾节点路由器中选择所述目标雾节点路由器。
  9. 一种文件传输方法，包括：
    客户端向云端服务器发送文件传输请求，以使所述云端服务器根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述文件传输请求和所述连接请求携带所述客户端的标识；
    在所述客户端根据所述客户端的标识与所述目标雾节点路由器建立文件传输连接后，通过所述文件传输连接进行文件传输。
  10. 根据权利要求9所述的方法，其中，所述文件传输请求为文件访问请求，所述文件访问请求和所述连接请求携带目标文件标识；
    其中，所述通过所述文件传输连接进行文件传输，包括：
    所述客户端通过所述文件传输连接，接收所述目标雾节点路由器发送的所述目标文件标识对应的目标文件。
  11. 根据权利要求9所述的方法，其中，所述文件传输请求为文件上传请求，所述文件上传请求和所述连接请求携带目标文件标识；
    其中，所述通过所述文件传输连接进行文件传输，包括：
    所述客户端通过所述文件传输连接，将所述目标文件标识对应的目标文件发送至所述目标雾节点路由器。
  12. 根据权利要求9所述的方法，还包括：
    所述客户端的所在环境为内网环境时，所述客户端与本地路由器通过所述客户端与所述本地路由器之间的文件传输连接进行文件传输。
  13. 一种文件传输方法，包括：
    雾节点路由器接收云端服务器发送的连接请求，其中，所述连接请求是所述云端服务器在接收到客户端向所述云端服务器发送的文件传输请求后发送至所述雾节点路由器的，所述文件传输请求和所述连接请求携带所述客户端的标识；
    所述雾节点路由器根据所述客户端的标识，与所述客户端建立文件传输连接；
    所述雾节点路由器与所述客户端通过所述文件传输连接进行文件传输。
  14. 根据权利要求13所述的方法，其中，所述雾节点路由器，为除所述客户端对应的本地路由器之外的其它路由器中、具备外网地址的路由器。
  15. 根据权利要求13所述的方法，其中，所述文件传输请求为文件访问请求，所述文件访问请求和所述连接请求携带目标文件标识，且所述雾节点路由器存储有多个文件标识分别对应的文件；
    其中，所述雾节点路由器与所述客户端通过所述文件传输连接进行文件传输，包括：
    所述雾节点路由器根据所述目标文件标识，查找所述目标文件标识对应的目标文件；
    所述雾节点路由器通过所述文件传输连接，将所述目标文件发送至所述客户端。
  16. 根据权利要求13所述的方法，其中，所述文件传输请求为文件上传请求，所述文件上传请求和所述连接请求携带目标文件标识；
    其中，所述雾节点路由器与所述客户端通过所述文件传输连接进行文件传输，包括：
    所述雾节点路由器通过所述文件传输连接，接收所述客户端发送的所述目标文件标识对应的目标文件。
  17. 根据权利要求13所述的方法，还包括：
    所述雾节点路由器与所述客户端对应的本地路由器进行数据同步。
  18. 一种云端服务器，包括：
    接收模块，用于接收客户端发送的文件传输请求，其中，所述文件传输请求携带所述客户端的标识；
    第一确定模块，用于根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述连接请求携带所述客户端的标识，以使所述目标雾节点路由器根据所述客户端的标识与所述客户端建立文件传输连接，并通过所述文件传输连接进行文件传输。
  19. 根据权利要求18所述的云端服务器，其中，所述文件传输请求为文件访问请求，所述文件访问请求携带目标文件标识，且所述云端服务器存储有多个文件标识和多个雾节点路由器的映射关系表；
    其中，所述第一确定模块，具体用于：
    根据所述目标文本标识查询所述映射关系表，将所述映射关系表中与所述目标文件标识对应的雾节点路由器确定为所述目标雾节点路由器。
  20. 根据权利要求19所述的云端服务器，还包括：
    第二确定模块，用于确定所述多个雾节点路由器分别对应的设备等级；
    第三确定模块，用于确定所述多个文件标识分别对应的文件的数据类型；
    第四确定模块，用于根据所述多个雾节点路由器分别对应的设备等级以及所述多个文件标识分别对应的文件的数据类型，确定所述多个文件标识和多个雾节点路由器的映射关系表，其中，不同的所述数据类型的文件，与不同的所述设备等级的所述雾节点路由器对应。
  21. 根据权利要求20所述的云端服务器，其中，所述第四确定模块，具体用于：
    根据所述多个雾节点路由器分别对应的设备等级以及所述多个文件标识分别对应的文件的数据类型，确定将不同的所述数据类型的文件存储在不同的所述设备等级的所述雾节点路由器中；
    根据所述多个文件标识分别对应的文件与所述多个雾节点路由器的存储关系，生成所述映射关系表。
  22. 根据权利要求20所述的云端服务器，其中，所述第二确定模块，具体用于：
    根据所述多个雾节点路由器的在线情况，确定所述多个雾节点路由器的设备质量；
    根据所述多个雾节点路由器的网络带宽，确定所述多个雾节点路由器的网络质量；
    根据所述设备质量和所述网络质量，确定所述多个雾节点路由器分别对应的所述设备等级。
  23. 根据权利要求20所述的云端服务器，其中，所述第三确定模块，包括：
    确定单元，用于针对每个所述文件标识对应的文件，根据当前时间、所述文件的创建时间、所述文件的修改时间以及所述文件的当日访问量，确定所述文件的数据类型。
  24. 根据权利要求23所述的云端服务器，其中，所述数据类型包括冷数据类型、热数据类型和候选冷数据类型；其中，所述确定单元，具体用于：
    判断所述当前时间与所述文件对应的创建时间的第一差值，或者所述当前时间与所述文件对应的修改时间的第二差值，是否大于预设时间阈值；
    在所述第一差值和所述第二差值均不大于所述预设时间阈值时，确定所述文件的数据类型为所述热数据类型；
    在所述第一差值或所述第二差值大于所述预设时间阈值时，进一步判断所述文件的当日访问量是否大于等于第一预设数量阈值；
    在所述文件的当日访问量小于所述第一预设数量阈值时，确定所述文件的数据类型为所述候选冷数据类型；
    在预设时间段内确定所述文件的数据类型为所述候选冷数据类型的连续次数超过第一预设次数阈值时，确定所述文件的数据类型为所述冷数据类型；
    在所述文件的当日访问量大于等于所述第一预设数量阈值，且所述文件的数据类型不为所述冷数据类型时，确定所述文件的数据类型为所述热数据类型；
    针对当前数据类型为所述冷数据类型的文件，判断所述文件的当日访问量是否大于等于第二预设数量阈值；
    在所述文件的当日访问量大于等于所述第二预设数量阈值，且确定所述文件的当日访问量大于等于所述第二预设数量阈值的连续次数超过第二预设次数阈值时，确定所述文件的数据类型为所述热数据类型。
  25. 根据权利要求18所述的云端服务器，其中，所述文件传输请求为文件上传请求；
    其中，所述第一确定模块，具体用于：
    根据所述客户端的标识，确定所述客户端与多个雾节点路由器之间的通信质量等级；
    根据所述客户端与所述多个雾节点路由器之间的所述通信质量等级，从所述多个雾节点路由器中选择所述目标雾节点路由器。
  26. 一种客户端，包括：
    发送模块，用于向云端服务器发送文件传输请求，以使所述云端服务器根据所述文件传输请求确定目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述文件传输请求和所述连接请求携带所述客户端的标识；
    第一传输模块，用于在所述客户端根据所述客户端的标识与所述目标雾节点路由器建立文件传 输连接后，通过所述文件传输连接进行文件传输。
  27. 根据权利要求26所述的客户端，其中，所述文件传输请求为文件访问请求，所述文件访问请求和所述连接请求携带目标文件标识；
    其中，所述第一传输模块，具体用于：
    通过所述文件传输连接，接收所述目标雾节点路由器发送的所述目标文件标识对应的目标文件。
  28. 根据权利要求26所述的客户端，其中，所述文件传输请求为文件上传请求，所述文件上传请求和所述连接请求携带目标文件标识；
    其中，所述第一传输模块，具体用于：
    通过所述文件传输连接，将所述目标文件标识对应的目标文件发送至所述目标雾节点路由器。
  29. 根据权利要求26所述的客户端，还包括：
    第二传输模块，用于在所述客户端的所在环境为内网环境时，与本地路由器通过所述客户端与所述本地路由器之间的文件传输连接进行文件传输。
  30. 一种雾节点路由器，包括：
    接收模块，用于接收云端服务器发送的连接请求，其中，所述连接请求是所述云端服务器在接收到客户端向所述云端服务器发送的文件传输请求后发送至所述雾节点路由器的，所述文件传输请求和所述连接请求携带所述客户端的标识；
    建立模块，用于根据所述客户端的标识，与所述客户端建立文件传输连接；
    传输模块，用于与所述客户端通过所述文件传输连接进行文件传输。
  31. 根据权利要求30所述的雾节点路由器，其中，所述雾节点路由器，为除所述客户端对应的本地路由器之外的其它路由器中、具备外网地址的路由器。
  32. 根据权利要求30所述的雾节点路由器，其中，所述文件传输请求为文件访问请求，所述文件访问请求携带目标文件标识，且所述雾节点路由器存储有多个文件标识分别对应的文件；
    其中，所述传输模块，具体用于：
    根据所述目标文件标识，查找所述目标文件标识对应的目标文件；
    通过所述文件传输连接，将所述目标文件发送至所述客户端。
  33. 根据权利要求30所述的雾节点路由器，其中，所述文件传输请求为文件上传请求，所述文件上传请求和所述连接请求携带目标文件标识；
    其中，所述传输模块，具体用于：
    通过所述文件传输连接，接收所述客户端发送的所述目标文件标识对应的目标文件。
  34. 根据权利要求30所述的雾节点路由器，还包括：
    同步模块，用于与所述客户端对应的本地路由器进行数据同步。
  35. 一种文件传输系统，其中，包括客户端、云端服务器以及多个雾节点路由器；
    其中，所述云端服务器，用于接收所述客户端发送的文件传输请求，以及根据所述文件传输请求确定所述多个雾节点路由器中的目标雾节点路由器，并向所述目标雾节点路由器发送连接请求，其中，所述文件传输请求和所述连接请求携带所述客户端的标识；
    所述目标雾节点路由器，用于在接收到所述连接请求后，根据所述客户端的标识，与所述客户端建立文件传输连接，以及与所述客户端通过所述文件传输连接进行文件传输；
    所述客户端，用于向所述云端服务器发送所述文件传输请求，以及与所述目标雾节点路由器通过所述文件传输连接进行文件传输。
  36. 一种电子设备，包括：
    至少一个处理器；以及
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行权利要求1至8中任一项所述的方法，或者权利要求9至12中任一项所述的方法，或者权利要求13至17中任一项所述的方法。
  37. 一种存储有计算机指令的非瞬时计算机可读存储介质，其中，所述计算机指令用于使所述计算机执行权利要求1至8中任一项所述的方法，或者权利要求9至12中任一项所述的方法，或者权利要求13至17中任一项所述的方法。
PCT/CN2022/085914 2021-04-09 2022-04-08 文件传输方法、云端服务器、客户端以及雾节点路由器 WO2022214085A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110382829.2A CN113163003B (zh) 2021-04-09 2021-04-09 文件传输方法、云端服务器、客户端以及雾节点路由器
CN202110382829.2 2021-04-09

Publications (1)

Publication Number Publication Date
WO2022214085A1 true WO2022214085A1 (zh) 2022-10-13

Family

ID=76889670

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/085914 WO2022214085A1 (zh) 2021-04-09 2022-04-08 文件传输方法、云端服务器、客户端以及雾节点路由器

Country Status (2)

Country Link
CN (1) CN113163003B (zh)
WO (1) WO2022214085A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115834697A (zh) * 2022-11-16 2023-03-21 北京奇艺世纪科技有限公司 一种文件存储方法、系统、装置及电子设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113163003B (zh) * 2021-04-09 2023-05-30 北京汇钧科技有限公司 文件传输方法、云端服务器、客户端以及雾节点路由器

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104994171A (zh) * 2015-07-15 2015-10-21 上海斐讯数据通信技术有限公司 一种分布式存储方法与系统
US20170019459A1 (en) * 2014-06-30 2017-01-19 Tencent Technology (Shenzhen) Company Limited File transmission method, file transmission apparatus, and file transmission system
CN111629075A (zh) * 2020-08-03 2020-09-04 腾讯科技（深圳）有限公司 一种数据下载方法和相关装置
CN112073542A (zh) * 2020-11-12 2020-12-11 腾讯科技（深圳）有限公司 雾节点调度方法、装置、计算机设备和存储介质
CN113163003A (zh) * 2021-04-09 2021-07-23 北京汇钧科技有限公司 文件传输方法、云端服务器、客户端以及雾节点路由器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8347286B2 (en) * 2007-07-16 2013-01-01 International Business Machines Corporation Method, system and program product for managing download requests received to download files from a server
US9444905B2 (en) * 2014-03-20 2016-09-13 International Business Machines Corporation Allocating network bandwidth to prefetch requests to prefetch data from a remote storage to cache in a local storage
CN109033360B (zh) * 2018-07-26 2020-11-17 腾讯科技（深圳）有限公司 一种数据查询方法、装置、服务器及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170019459A1 (en) * 2014-06-30 2017-01-19 Tencent Technology (Shenzhen) Company Limited File transmission method, file transmission apparatus, and file transmission system
CN104994171A (zh) * 2015-07-15 2015-10-21 上海斐讯数据通信技术有限公司 一种分布式存储方法与系统
CN111629075A (zh) * 2020-08-03 2020-09-04 腾讯科技（深圳）有限公司 一种数据下载方法和相关装置
CN112073542A (zh) * 2020-11-12 2020-12-11 腾讯科技（深圳）有限公司 雾节点调度方法、装置、计算机设备和存储介质
CN113163003A (zh) * 2021-04-09 2021-07-23 北京汇钧科技有限公司 文件传输方法、云端服务器、客户端以及雾节点路由器

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115834697A (zh) * 2022-11-16 2023-03-21 北京奇艺世纪科技有限公司 一种文件存储方法、系统、装置及电子设备

Also Published As

Publication number Publication date
CN113163003B (zh) 2023-05-30
CN113163003A (zh) 2021-07-23

Similar Documents

Publication Publication Date Title
US10701147B1 (en) Systems and methods for synchronizing data between communication devices in a networked environment
WO2022214085A1 (zh) 文件传输方法、云端服务器、客户端以及雾节点路由器
US9329783B2 (en) Data processing system and data processing method
US20190213219A1 (en) Regulating data storage based on copy quantity
EP1684173A1 (en) Bus abstraction system and method for unifying device discovery and message transport in multiple bus implementations and networks
US8396009B2 (en) Method and apparatus for an adapter in a network device to discover its adapter name in a network system
TWI289983B (en) Plug and play networking architecture with enhanced scalability and reliability
US20090052461A1 (en) Method and Apparatus for Fibre Channel Over Ethernet Data Packet Translation Via Look up Table Conversion Bridge in a Network System
US8310953B2 (en) Method and apparatus for enabling an adapter in a network device to discover the name of another adapter of another network device in a network system
KR20050009685A (ko) 다수의 ｎｉｃ ｒｄｍａ가 가능한 장치의 상태 이동
JP2009516279A (ja) コンピュータ・システムのクラスタにおいてルーティング情報を調整するための方法およびシステム（サーバがクラスタに加入した時刻に基づいたルーティング・データの送信）
WO2017107463A1 (zh) 一种分发cdn地址的方法及装置
KR20040010609A (ko) 네트워크 파일 공유 방법 및 시스템
US8005918B2 (en) Data storage devices having IP capable partitions
US8199648B2 (en) Flow control in a variable latency system
US8065401B2 (en) Systems and methods for frame ordering in wide port SAS connections
US8510461B2 (en) Network selection for streaming media among multiple devices
US20090172433A1 (en) Powering on devices via intermediate computing device
CN109788075B (zh) 专网网络系统、数据的获取方法及边缘服务器
US11811643B2 (en) System and method for managing computing resources
US20240069754A1 (en) Computing system and associated method
CN107566319B (zh) 虚拟机器即时转移方法
JP2000293454A (ja) データ通信装置、データ通信方法、および記録媒体

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22784151

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 13/02/2024)