WO2021134861A1 - 一种管理资源状态信息的方法和资源下载系统 - Google Patents
一种管理资源状态信息的方法和资源下载系统 Download PDFInfo
- Publication number
- WO2021134861A1 WO2021134861A1 PCT/CN2020/074960 CN2020074960W WO2021134861A1 WO 2021134861 A1 WO2021134861 A1 WO 2021134861A1 CN 2020074960 W CN2020074960 W CN 2020074960W WO 2021134861 A1 WO2021134861 A1 WO 2021134861A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- target
- file
- node
- resource file
- Prior art date
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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
Definitions
- This application relates to the field of network communication technology, and in particular to a method for managing resource status information and a resource download system.
- P2P (peer-to-peer) technology is a communication technology based on peer-to-peer network for data transmission. It establishes a direct client-to-client communication mechanism.
- each P2P node It acts as both a client and a server for other P2P nodes.
- the data block of the transmission resource file based on the peer-to-peer network has been introduced on the basis of the CDN system.
- the CDN server can pre-deploy a large number of high-performance devices in the peer-to-peer network as super P2P nodes (hereinafter referred to as super nodes), or select some clients with better network quality, CPU, memory performance, etc.
- super node the super node can download and store all the data blocks of the resource file from the CDN server.
- the terminal can request a node list from the Tracker server while downloading the data block from the CDN server, and the Tracker server can feed back the node information of the super node that has stored the corresponding resource file to the terminal. Therefore, the terminal can establish a connection with the super node and obtain the data block of the resource file stored by the super node.
- a super node When a super node provides external resource download services, it will report the resource status information of all resource files stored locally to the Tracker server, and the Tracker server will maintain the resource status information reported by each super node.
- the Tracker server When a super node provides external resource download services, it will report the resource status information of all resource files stored locally to the Tracker server, and the Tracker server will maintain the resource status information reported by each super node.
- a large number of resource files are often stored on a single super node. Therefore, the amount of resource status information that the Tracker server needs to maintain and manage is huge, causing the Tracker server to be overloaded and the quality of service will be greatly affected.
- embodiments of the present application provide a method for managing resource status information and a resource download system.
- the technical solution is as follows:
- a method for managing resource status information including:
- a method for managing resource status information includes:
- a resource download system in a third aspect, includes a super node and a tracker server, wherein the super node is used to execute the method described in the first aspect, and the tracker server is used to execute The method described in the second aspect.
- a network device in a fourth aspect, includes a processor and a memory.
- the memory stores at least one instruction, at least one program, code set, or instruction set. A piece of program, the code set or the instruction set is loaded and executed by the processor to implement the method according to the first aspect or the second aspect.
- a computer-readable storage medium stores at least one instruction, at least one program, code set, or instruction set, the at least one instruction, the at least one program, and the code
- the set or instruction set is loaded and executed by the processor to implement the method according to the first aspect or the second aspect.
- the Tracker server determines the number of new resource files that can be added on the target super node, and selects at least one of the multiple resource files to be recommended according to the number of additions and the node list corresponding to the multiple resource files to be recommended
- the target resource file sends the file identifier of the target resource file to the target super node so that the target super super node configures the download service of each target resource file, receives the service configuration information of each target resource file reported by the target super node, and updates each target resource file.
- the Tracker server is only responsible for pushing resource files to the super nodes, and the specific file management work is sinked to each super node in a distributed deployment.
- the Tracker server does not need to recalculate the service configuration of all resource files when recovering from failure. Status, which can not only reduce the load pressure of the Tracker server, but also improve the stability of the entire resource download system.
- FIG. 1 is a schematic diagram of a network architecture of a peer-to-peer network provided by an embodiment of the present application
- Figure 2 is a flowchart of a method for managing resource status information provided by an embodiment of the present application
- FIG. 3 is a schematic diagram of a flow of downloading resource files provided by an embodiment of the present application.
- Fig. 4 is a schematic structural diagram of a network device provided by an embodiment of the present application.
- the embodiment of the present application provides a method for managing resource status information.
- the method can be applied to a peer-to-peer network and is mainly implemented by a tracker server and a super node in the peer-to-peer network.
- the specific architecture of the peer-to-peer network can be shown in Figure 1.
- the peer-to-peer network can include a large number of nodes, and each node can act as a data downloader (that is, a client), using P2P technology to download resource files from other nodes. It can also be used as a data provider (that is, a server), using P2P technology to provide stored resource files to other nodes.
- the nodes in the peer-to-peer network can include super nodes and ordinary P2P nodes (hereinafter referred to as ordinary nodes).
- the Tracker server can be used to collect and manage the resource status information of the resource files on each node in the peer-to-peer network, and then can respond to the received node query request based on the resource status information.
- the function of the aforementioned Tracker server can also be implemented in the form of a Tracker service cluster.
- the Tracker service cluster can be composed of multiple Tracker servers deployed in a distributed manner, and different Tracker servers can be used to serve P2P nodes in different regions.
- the super node can be mainly used to alleviate the resource download pressure of the CDN server, that is, the CDN server can deploy some resource files on the super node, so that when the user terminal wants to obtain these resource files, it can use P2P technology from Download from the super node without downloading from the CDN server.
- Step 201 The Tracker server determines the number of new resource files that can be added on the target super node.
- the super node when the super node provides resource file download services externally, it can continuously update the resource download service provided by it based on the attribute information of the resource file, user requirements and the distribution plan of the technical staff for the resource file, that is, regularly delete It stores old resource files on it, and constantly downloads new resource files from the CDN server.
- the super node can also download new resource files from other super nodes or ordinary nodes in the peer-to-peer network based on the P2P technology, which is not limited in this embodiment.
- the Tracker server can be used to manage the download processing of the new resource file of the super node.
- the super node when it needs to add a new resource file, it can recommend multiple resource files to the super node for the super node to add new resource files. Select the resource file to be added from the target resource files.
- the Tracker server can first determine the number of new resource files that can be added on the target super node before recommending new resource files to the target super node.
- Step 1 The target super node periodically determines the number of new resource files that can be added according to the real-time bandwidth load status
- Step 2 The target super node sends a resource download request carrying the number of resources that can be added to the Tracker server;
- Step 3 The Tracker server receives the resource download request sent by the target super node, and obtains the number of new resource files that can be added in the resource download request.
- the target super node can actively request the Tracker server to recommend new resource files based on its own service status. Specifically, the target super node can periodically check the current network connection number to determine whether it has reached the preset connection upper limit. If the preset connection upper limit is not reached, the target super node can determine the current number of idle connections. At the same time, each super node can pre-store the download performance occupancy standard of the resource file, and the download performance occupancy standard can reflect the equipment performance that the super node needs to occupy when downloading the resource file from the CDN server (or other P2P node), such as Downloading a certain resource file requires 3 network connections, 2G of memory space and 10% of the CPU processing speed.
- the number of network connections of the super node at the same time is relatively small, and the number of network connections is often regarded as the main bottleneck in the resource download process. Therefore, when the super node actively requests new resource files, it needs to give priority to idleness. Is the number of connections sufficient? It can be understood that technical personnel can set different download performance occupancy standards for resource files with different attribute information based on attribute information such as the size, category, and owner of the resource file. And because storage space is a gradual accumulation of equipment performance indicators that will not automatically decrease, after providing resource file download services for a long time, super nodes may also face insufficient remaining storage space when new resource files need to be added. The problem.
- the super node can determine the number of new resource files that can be added according to the current number of idle connections and remaining storage space, referring to the download performance occupancy standard of the pre-stored resource files.
- the number of new resource files that can be added can also be determined by referring to the performance of multiple devices based on the above principles.
- the target super node can send a resource download request to the Tracker server, so that the Tracker server can directly obtain the number of new resource files on the target super node that can be added from the resource download request.
- Step 1 The target super node regularly reports the local real-time bandwidth load status and remaining storage space to the Tracker server;
- Step 2 The Tracker server determines the number of new resource files that can be added on the target super node according to the real-time bandwidth load status and remaining storage space periodically uploaded by the target super node.
- the target super node can periodically report the local real-time bandwidth load status and remaining storage space to the Tracker server while providing resource file download services externally.
- the Tracker server can record the real-time bandwidth load status and remaining storage space reported by the target super node.
- it can use the real-time bandwidth load status and remaining storage space to select the super node when it feeds back the node list to the ordinary node to realize the super node.
- the number of new resource files that can be added on the target super node can be determined according to the real-time bandwidth load status and remaining storage space.
- the download performance occupancy standard of the resource file can also be pre-stored on the Tracker server, and the number of new resource files that can be added can be determined according to the download performance occupancy standard.
- the super node can also periodically upload other equipment performance information to the Tracker server for the Tracker server to actively determine the number of new resource files that can be added.
- the Tracker server selects at least one target resource file from the plurality of resource files to be recommended according to the number of addable and the node list corresponding to the plurality of resource files to be recommended.
- the Tracker server determines the number of new resource files that can be added on the target super node, it can first obtain the node list corresponding to multiple resource files to be recommended in the resource pool to be recommended, and the current node list can be recorded The node IDs of all super nodes that have provided the corresponding resource files. Then, the Tracker server can refer to the number of nodes that can be added and the node list corresponding to the multiple resource files to be recommended, and select at least one target resource file from the multiple resource files to be recommended. Among all the new resource files recommended by the Tracker server, some resource files may have been stored on the target super node. Therefore, in order to make full use of the bandwidth resources, storage space and other equipment performance of the target super node, the number of target resource files selected can be compared with The number of the above can be added is equal, or slightly larger than the number of can be added.
- the above process of selecting the target resource file may specifically be to traverse the node lists corresponding to multiple resource files to be recommended in order of the popularity value of the resource files; when the node of the resource file to be recommended When the target super node is not included in the list, the resource file to be recommended is selected as the target resource file until the number of target resource files is not less than the number that can be added, and the difference between the two is greater than the preset threshold.
- the Tracker server can sequentially select multiple resource files to be recommended from the resource pool to be recommended according to the order of the popularity value of the resource files, and obtain a list of nodes corresponding to the resource files to be recommended.
- the popularity value of the resource file can be reflected by the number of accesses of the resource file within a preset time.
- the Tracker server searches for the target super node in the node list of the resource file to be recommended.
- the Tracker server can select the corresponding resource file to be recommended as the target resource file; and if the target super node is included in the node list, it means that the target super node has provided the corresponding resource file
- the download service does not need to recommend the resource file to the target super node again, so the resource file can be skipped and the node list of the next resource file to be recommended is obtained.
- the Tracker server can continuously select resource files to be recommended as target resource files one by one until the number of target resource files is not less than the number that can be added, and the difference between the two is greater than the preset threshold.
- the specific number of target resource files can be referred to the description in step 202, and the detailed value can be manually determined.
- the Tracker server can simultaneously refer to the number of resource file requests and the number of service nodes to determine the resource file that needs to be recommended.
- the corresponding processing can be as follows: According to the number of requests and service nodes corresponding to each resource file within a preset time period Calculate the recommendation coefficient corresponding to each resource file; determine the resource file with the recommendation coefficient greater than the preset threshold as the resource file to be recommended.
- the Tracker server can record the number of requests corresponding to each resource file, and at the same time refer to the number of service nodes of each resource file to calculate the recommendation coefficient corresponding to each resource file. Assuming that the number of requests is N and the number of service nodes is M, the calculation method of the recommendation coefficient C can be as follows:
- T 1 and T 2 are preset number thresholds.
- the coefficients in the above formula are only used as an exemplary description, and this embodiment does not limit this.
- the Tracker server may compare the calculated recommendation coefficient with the preset threshold, thereby determining the resource file with the recommendation coefficient greater than the preset threshold as the resource file to be recommended.
- both the number of requests for the resource files and the number of super nodes that have been configured for the resource files are considered, so that the recommendation coefficient can more accurately reflect the actual recommendation requirements of each resource file; and It can be seen from the calculation formula of the recommendation coefficient that when the number of requests for resource files reaches a certain value, by adjusting the calculation method of the recommendation coefficient, a popular resource file can be effectively prevented from being frequently recommended to the super node, thereby avoiding resource files
- the repeated configuration can effectively improve the resource utilization of the super node.
- Step 203 The Tracker server sends the file identifier of the target resource file to the target super node.
- Step 204 The target super node receives the file identifier of at least one target resource file sent by the Tracker server.
- Step 205 The target super node configures the download service of each target resource file according to the file identifier and the local resource storage status.
- the target super node after the target super node receives the file identifier of at least one target resource file sent by the Tracker server, it can process the file identifiers one by one in combination with the local resource storage state to complete the configuration processing of the download service of each target resource file . Specifically, for the target file identifier, the target super node may first determine whether the target file identifier exists in the local current free resource list. If it exists, it means that the target super node has stored the resource file corresponding to the target file identifier, and can directly activate the download service of the resource file, and move the target file identifier out of the free resource list. If it does not exist, the target super node can download the resource file corresponding to the target file identifier, and after the download is completed, activate the download service of the resource file.
- the super node can decide whether to close the download service of the corresponding resource file according to the number of accesses, and the corresponding processing can be as follows: periodically count the number of accesses to the resource file outside the list of free resources stored locally in the current period; if When the number of accesses is less than the preset threshold, the file identifier of the resource file is added to the list of free resources, and the service stop notification of the resource file is sent to the Tracker server.
- the target super node may periodically count the number of accesses to the resource file (that is, the resource file outside the free resource list stored locally) in the current cycle that the download service is in an active state. If the number of accesses of a certain resource file is less than the preset threshold, the download service of the resource file can be turned off, that is, the file identifier of the resource file is added to the free resource list. At the same time, the service stop notification of the resource file can be sent to the Tracker server, so that the Tracker server deletes the node identifier of the target super node from the node list of the resource file after receiving the service stop notification.
- the download processing of the corresponding resource file can be as follows: If it is smaller than the file size of the resource file corresponding to the target file identifier, calculate the heat value corresponding to each file identifier in the free resource list; according to the order of heat value from low to high, delete the resource corresponding to the file identifier in the locally stored free resource list accordingly File; when the remaining storage space is not less than the file size of the resource file corresponding to the target file identifier, download the resource file corresponding to the target file identifier.
- the target super node can continuously detect the current remaining storage space when downloading the resource file corresponding to the target file identifier. If it is found that the remaining storage space is less than the file size of the resource file corresponding to the target file identifier, the local free resource list can be extracted, and the popularity value corresponding to each file identifier in the free resource list can be calculated. After that, the target super node can sequentially delete the resource files corresponding to the file identifiers in the free resource list from the local storage space in the order of the popularity value from low to high, and remove the file identifiers from the free resource list, so that priority can be given Delete the resource files with lower heat value.
- the target super node may stop the deletion process and download the resource file corresponding to the target file identifier.
- the target super node may also perform download processing of the resource file while deleting the resource file, so as to increase the download rate of the resource file.
- the super node when the resource file configured with the download service is updated, can stop the download service of the resource file, and the corresponding processing can be as follows: periodically check whether the locally stored resource file has an update requirement; if it exists, then Delete the locally stored resource files, and send a notification of the service stop of the resource files to the Tracker server.
- the target super node can periodically detect whether there is an update requirement for the locally stored resource file.
- the detection method here can use the file version query mechanism in the prior art, which is not described in detail in this embodiment.
- the target super node can stop the download service of the resource file, that is, delete the locally stored resource file, and send the service stop notification of the resource file to the Tracker server .
- the super node deletes the resource files with expired versions in time, one can save a lot of storage resources, and the two can ensure that the expired resource files are not downloaded by mistake, thereby improving the download service quality of the resource files.
- the super node if it detects that a certain resource file has a patch file that has a much smaller data volume than the resource file, it can actively download the patch file, and The resource file is not deleted, so as to prevent the resource file from being recommended by the Tracker server multiple times, and the super node repeatedly downloads the resource file.
- Step 206 The target super node feeds back the service configuration information of each target resource file to the Tracker server.
- the target super node can feed back the service configuration information of each target resource file to the Tracker server, where the service configuration information can at least include the download service of each target resource file Configuration status (success or failure).
- Step 207 The Tracker server receives the service configuration information of each target resource file reported by the target super node, and updates the node list corresponding to each target resource file.
- the Tracker server after the Tracker server receives the service configuration information reported by the target super node, it can update the node list corresponding to each target resource file according to the service configuration information. That is, if the target super node successfully configures the download service of the target resource file, the Tracker server adds the node identifier of the target super node to the node list of the target resource file, otherwise no processing is performed.
- this embodiment also discloses a process of downloading resource files based on the above steps 201 to 207, as shown in FIG. 3, which can be specifically as follows:
- Step 301 The Tracker server receives a resource file acquisition request sent by a common node.
- the resource download program can Perform the download task of the resource file. Based on the settings of the CDN server, some resources have been pre-deployed at the super node. Therefore, the resource download program can first determine the download mode of the resource file, that is, whether it is downloaded through a peer-to-peer network or through a CDN server. If it is downloaded via a peer-to-peer network, the resource download program can trigger the client to send a request for resource file acquisition to the Tracker server.
- the Tracker server selects an optional super node in the node list corresponding to the resource file according to the network address of the common node and the load status of each super node included in the node list.
- the Tracker server can read the node list corresponding to the resource file after receiving the resource file acquisition request sent by the common node, and then select the node closer to the common node according to the network address of the common node in the node list , Multiple optional super nodes with low load.
- Step 303 The Tracker server feeds back the node information of the optional super node to the ordinary node.
- the Tracker server determines the number of new resource files that can be added on the target super node, and selects at least one of the multiple resource files to be recommended according to the number of additions and the node list corresponding to the multiple resource files to be recommended
- the target resource file sends the file identifier of the target resource file to the target super node so that the target super super node configures the download service of each target resource file, receives the service configuration information of each target resource file reported by the target super node, and updates each target resource file.
- the Tracker server is only responsible for pushing resource files to the super nodes, and the specific file management work is sinked to each super node in a distributed deployment.
- the Tracker server does not need to recalculate the service configuration of all resource files when recovering from failure. Status, which can not only reduce the load pressure of the Tracker server, but also improve the stability of the entire resource download system.
- an embodiment of the present application also provides a resource download system.
- the resource download system includes a super node and a tracker server.
- the super node is used to execute the target super node in the above embodiment.
- the Tracker server is used to perform the processing implemented by the Tracker server in the foregoing embodiment.
- FIG. 4 is a schematic structural diagram of a network device provided by an embodiment of the present application.
- the network device 400 may have relatively large differences due to different configurations or performances, and may include one or more central processing units 422 (for example, one or more processors) and a memory 432, and one or more storage application programs 442 or
- the storage medium 430 of the data 444 (for example, one or a storage device with a large amount of storage).
- the memory 432 and the storage medium 430 may be short-term storage or persistent storage.
- the program stored in the storage medium 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the network device 400.
- the central processing unit 422 may be configured to communicate with the storage medium 430, and execute a series of instruction operations in the storage medium 430 on the network device 400.
- the network device 400 may also include one or more power supplies 429, one or more wired or wireless network interfaces 450, one or more input and output interfaces 458, one or more keyboards 456, and/or, one or more operating systems 441, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc.
- the network device 400 may include a memory and one or more programs.
- One or more programs are stored in the memory and configured to be executed by one or more processors. The above instructions for managing resource status information.
- the program can be stored in a computer-readable storage medium.
- the storage medium mentioned can be a read-only memory, a magnetic disk or an optical disk, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本申请公开了一种管理资源状态信息的方法和资源下载系统，属于网络通信技术领域。所述方法包括：目标超级节点接收Tracker服务器发送的至少一个目标资源文件的文件标识(204)；目标超级节点根据文件标识和本地的资源存储状态，配置每个目标资源文件的下载服务(205)；目标超级节点向所述Tracker服务器反馈每个目标资源文件的服务配置信息(206)。
Description
交叉引用
本申请引用于2020年01月03日递交的名称为“一种管理资源状态信息的方法和资源下载系统”的第202010006155.1号中国专利申请，其通过引用被全部并入本申请。
本申请涉及网络通信技术领域，特别涉及一种管理资源状态信息的方法和资源下载系统。
P2P(端对端，peer-to-peer)技术是一种基于对等网络进行数据传输的通讯技术，建立了一种客户端对客户端的直接通信机制，在对等网络中，每一P2P节点既作为客户端，又充当其它P2P节点的服务端。为了减轻CDN服务器的负载压力，同时节省CDN流量成本，目前已在CDN系统的基础上引入基于对等网络的传输资源文件的数据块。
CDN服务方可以预先在对等网络中分布式部署大量性能良好的设备作为超级P2P节点(以下简称为超级节点)，或者将一些网络质量、CPU、内存性能等各方面较好的客户端选取作为超级节点，超级节点可以从CDN服务器下载并存储资源文件全部的数据块。这样，当需要获取某一资源文件时，终端可以在从CDN服务器下载数据块的同时，向Tracker服务器请求节点列表，Tracker服务器可以向终端反馈已存储有相应资源文件的超级节点的节点信息。从而，终端可以与超级节点建立连接，并从超级节点处获取其存储的资源文件 的数据块。
在实现本申请的过程中，发明人发现现有技术至少存在以下问题：
超级节点在对外提供资源下载服务时，会将本地所存储的所有资源文件的资源状态信息都上报到Tracker服务器上，由Tracker服务器来维护各个超级节点上报的资源状态信息。然而，单台超级节点上往往会存储有大量的资源文件，故而Tracker服务器需要维护管理的资源状态信息的数量巨大，导致Tracker服务器的负载过大，服务质量将会大大受到影响。
发明内容
为了解决现有技术的问题，本申请实施例提供了一种管理资源状态信息的方法和资源下载系统。所述技术方案如下：
第一方面，提供了一种管理资源状态信息的方法，所述方法包括：
接收Tracker服务器发送的至少一个目标资源文件的文件标识；
根据所述文件标识和本地的资源存储状态，配置每个所述目标资源文件的下载服务；
向所述Tracker服务器反馈每个所述目标资源文件的服务配置信息。
第二方面，提供了一种管理资源状态信息的方法，所述方法包括：
确定目标超级节点上新资源文件的可添加个数；
根据所述可添加个数和多个待推荐资源文件对应的节点列表，在所述多个待推荐资源文件中选取至少一个目标资源文件；
向所述目标超级节点发送所述目标资源文件的文件标识，以使所述目标超级超节点配置每个所述目标资源文件的下载服务；
接收所述目标超级节点上报的每个所述目标资源文件的服务配置信息，更新每个所述目标资源文件对应的节点列表。
第三方面，提供了一种资源下载系统，所述资源下载系统包括超级节点和Tracker服务器，其中，所述超级节点用于执行如第一方面所述的方法，所 述Tracker服务器用于执行如第二方面所述的方法。
第四方面，提供了一种网络设备，所述网络设备包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如第一方面或第二方面所述的方法。
第五方面，提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如第一方面或第二方面所述的方法。
本申请实施例提供的技术方案带来的有益效果是：
本申请实施例中，Tracker服务器确定目标超级节点上新资源文件的可添加个数，根据可添加个数和多个待推荐资源文件对应的节点列表，在多个待推荐资源文件中选取至少一个目标资源文件，向目标超级节点发送目标资源文件的文件标识，以使目标超级超节点配置每个目标资源文件的下载服务，接收目标超级节点上报的每个目标资源文件的服务配置信息，更新每个目标资源文件对应的节点列表。这样，Tracker服务器仅负责向超级节点推送资源文件，而将具体的文件管理工作下沉到分布式部署的各个超级节点，同时Tracker服务器在进行故障恢复时也不需要重新计算所有资源文件的服务配置状态，从而既可以减轻Tracker服务器的负载压力，又可以提高整个资源下载系统的稳定性。
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种对等网络的网络架构示意图；
图2是本申请实施例提供的一种管理资源状态信息的方法流程图；
图3是本申请实施例提供的一种下载资源文件的流程示意图；
图4是本申请实施例提供的一种网络设备的结构示意图。
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作详细描述。
本申请实施例提供了一种管理资源状态信息的方法，该方法可以应用于对等网络，并主要由对等网络中的Tracker服务器和超级节点共同实现。对等网络的具体架构可以如图1所示，其中，对等网络可以包括大量节点，每个节点都可以作为数据下载方(即客户端)，利用P2P技术从其它节点处下载资源文件，同时也可以作为数据提供方(即服务端)，利用P2P技术将已存储的资源文件提供给其它节点，对等网络中的节点可以包括超级节点和普通P2P节点(以下简称为普通节点)。Tracker服务器可以用于收集并管理对等网络中各节点上资源文件的资源状态信息，进而可以基于这些资源状态信息，对接收到的节点查询请求进行响应。上述Tracker服务器的功能也可以以Tracker服务集群的形式来实现，Tracker服务集群可以由分布式部署的多台Tracker服务器构成，不同Tracker服务器可以用于服务不同区域内的P2P节点。本实施例中，超级节点可以主要用于缓解CDN服务器的资源下载压力，即CDN服务方可以将部分资源文件部署在超级节点上，使得用户终端想要获取这些资源文件时，能够通过P2P技术从超级节点上下载，而无需从CDN服务器下载。
下面将结合具体实施方式，对图2所示的处理流程进行详细的说明，内容可以如下：
步骤201，Tracker服务器确定目标超级节点上的新资源文件的可添加个数。
在实施中，超级节点在对外提供资源文件下载服务时，可以基于资源文件的属性信息、用户需求和技术人员对于资源文件的分布规划等因素，不断更 新其所提供的资源下载服务，即定期删除其上存储的旧资源文件，并不断从CDN服务器下载新资源文件。当然，超级节点同样可以基于P2P技术，从对等网络中的其它超级节点或普通节点处下载新资源文件，本实施例对此不进行限定。而在上述过程中，Tracker服务器可以用于管理超级节点的新资源文件的下载处理，其具体可以在超级节点需要添加新资源文件时，向超级节点推荐多个资源文件，以供超级节点在多个目标资源文件中选取其需要添加的资源文件。以目标超级节点为例，Tracker服务器在向目标超级节点推荐新资源文件前，可以先确定目标超级节点上新资源文件的可添加个数。
在一个实施例中，Tracker服务器向超级节点推荐资源文件的处理存在多种可选的触发方式，如下给出了两种可行的方式：
方式一：步骤一，目标超级节点周期性根据实时带宽负载状态，确定新资源文件的可添加个数；
步骤二，目标超级节点向Tracker服务器发送携带可添加个数的资源下载请求；
步骤三，Tracker服务器接收目标超级节点发送的资源下载请求，获取资源下载请求中携带的新资源文件的可添加个数。
在实施中，目标超级节点可以基于自身的服务状态，主动请求Tracker服务器推荐新资源文件。具体来说，目标超级节点可以周期性地查看当前的网络连接数，判断其是否到达预设连接上限。如果未达到预设连接上限，目标超级节点则可以确定出当前的空闲连接数。同时，各个超级节点中可以预先存储有资源文件的下载性能占用标准，该下载性能占用标准可以反映超级节点从CDN服务器(或其它P2P节点)处下载资源文件时，所需占用的设备性能，如下载某个资源文件需要占用3个网络连接、2G的内存空间和10％的CPU处理速度。而相比于其它设备性能，超级节点在同一时刻的网络连接数量比较少，网络连接数目常被认为是资源下载过程中的主要瓶颈，故而超级节点在主动请求新资源文件时，需要优先考虑空闲连接数是否足够。可以理解，技术人员可 以基于资源文件的大小、类别、归属者等属性信息，针对具备不同属性信息的资源文件设置不同下载性能占用标准。而由于存储空间属于逐渐累积，不会自动减小的一项设备性能指标，在长时间对外提供资源文件的下载服务后，超级节点也可能会面临在需要添加新资源文件时，剩余存储空间不足的问题。因此，超级节点可以根据当前的空闲连接数和剩余存储空间，参照预存的资源文件的下载性能占用标准，确定出新资源文件的可添加个数。当然，在确定可添加个数时，也可基于上述原理同时参考多种设备性能，来决定新资源文件的可添加个数。进而，目标超级节点可以向Tracker服务器发送资源下载请求，使得Tracker服务器可以直接从资源下载请求中，获取目标超级节点上的新资源文件的可添加个数。
方式二：步骤一，目标超级节点定期向Tracker服务器上报本地的实时带宽负载状态和剩余存储空间；
步骤二，Tracker服务器根据目标超级节点定期上传的实时带宽负载状态和剩余存储空间，确定目标超级节点上新资源文件的可添加个数。
在实施中，目标超级节点在对外提供资源文件的下载服务的同时，可以定期向Tracker服务器上报本地的实时带宽负载状态和剩余存储空间。相应的，Tracker服务器可以记录目标超级节点上报的实时带宽负载状态和剩余存储空间，一方面可以在向普通节点反馈节点列表时，利用实时带宽负载状态和剩余存储空间选取超级节点，以实现超级节点间的负载均衡；另一方面，可以根据实时带宽负载状态和剩余存储空间，确定目标超级节点上新资源文件的可添加个数。与方式一同理，Tracker服务器上也可以预存有资源文件的下载性能占用标准，并可以依照该下载性能占用标准确定上述新资源文件的可添加个数。同样的，根据下载性能占用标准所需的设备性能的不同，超级节点也可以定期向Tracker服务器上传其它设备性能信息，以供Tracker服务器主动来确定新资源文件的可添加个数。
步骤202，Tracker服务器根据可添加个数和多个待推荐资源文件对应的 节点列表，在多个待推荐资源文件中选取至少一个目标资源文件。
在实施中，Tracker服务器在确定了目标超级节点上新资源文件的可添加个数后，可以先获取待推荐资源池中多个待推荐资源文件对应的节点列表，该节点列表中可以记录有当前已提供相应资源文件的所有超级节点的节点标识。然后，Tracker服务器可以参考可添加个数和多个待推荐资源文件对应的节点列表，在多个待推荐资源文件中选取至少一个目标资源文件。其中，由于Tracker服务器推荐的所有新资源文件中，目标超级节点上可能已存储部分资源文件，故而为了充分利用目标超级节点的带宽资源、存储空间等设备性能，目标资源文件的选取个数可以与上述可添加个数相等，或者略大于可添加个数。
在一个实施例中，上述选取目标资源文件的过程具体可以是，按照资源文件的热度值从高至低的顺序，依次遍历多个待推荐资源文件对应的节点列表；当待推荐资源文件的节点列表中不包含目标超级节点时，将待推荐资源文件选取为目标资源文件，直至目标资源文件的个数不小于可添加个数，且二者差值大于预设阈值。
在实施中，Tracker服务器可以按照资源文件的热度值从高至低的顺序，从待推荐资源池中依次选取多个待推荐资源文件，并获取对个待推荐资源文件对应的节点列表。其中，资源文件的热度值可以由预设时间内资源文件的访问次数来体现。在此过程中，Tracker服务器在待推荐资源文件的节点列表中查找目标超级节点。若节点列表中不包含目标超级节点，Tracker服务器则可以将相应的待推荐资源文件选取为目标资源文件；而若节点列表中包含目标超级节点，则说明目标超级节点上已提供有相应资源文件的下载服务，无需再次将该资源文件推荐给目标超级节点，故而可以跳过该资源文件，获取下一待推荐资源文件的节点列表。基于上述过程，Tracker服务器可以持续地将待推荐资源文件逐个选取为目标资源文件，直至目标资源文件的个数不小于可添加个数，且二者差值大于预设阈值。此处，目标资源文件的具体个数，可以参考步骤202中的说明，详细数值可以由人工确定。
在一个实施例中，Tracker服务器可以同时参考资源文件的请求数目和服务节点数目，来确定需要推荐的资源文件，相应的处理可以如下：根据预设时长内各个资源文件对应的请求数目和服务节点数目，计算各个资源文件对应的推荐系数；将推荐系数大于预设阈值的资源文件确定为待推荐资源文件。
在实施中，Tracker服务器可以对各个资源文件对应的请求数目进行记录，并同时参考各个资源文件的服务节点数目，来计算各个资源文件对应的推荐系数。假设请求数目为N，服务节点数目为M，则推荐系数C的计算方式可以如下：
其中，T
1、T
2为预设的数目阈值。上述公式中的系数仅用作示例性的说明，本实施例并不对此进行限定。之后，Tracker服务器可以将计算得到的推荐系数与预设阈值进行比对，从而将推荐系数大于预设阈值的资源文件确定为待推荐资源文件。这样，在决定待推荐资源文件时，既考虑到了针对资源文件的请求数目，又结合了已配置资源文件的超级节点数量，可以使得推荐系数能更准确地反映各个资源文件的实际推荐需求；而从推荐系数的计算公式中可以看出，当资源文件的请求数目达到特定的数值后，通过调整推荐系数的计算方式，可以有效避免某一热门资源文件被频繁推荐给超级节点，从而避免资源文件的重复配置，可以有效提高超级节点的资源利用率。
步骤203，Tracker服务器向目标超级节点发送目标资源文件的文件标识。
步骤204，目标超级节点接收Tracker服务器发送的至少一个目标资源文件的文件标识。
步骤205，目标超级节点根据文件标识和本地的资源存储状态，配置每个目标资源文件的下载服务。
在实施中，目标超级节点接收到Tracker服务器发送的至少一个目标资 源文件的文件标识之后，可以结合本地的资源存储状态对文件标识逐个进行处理，以完成每个目标资源文件的下载服务的配置处理。具体的，对于目标文件标识，目标超级节点可以先判断本地当前的空闲资源列表中是否存在目标文件标识。如果存在，说明目标超级节点已存储有目标文件标识对应的资源文件，则可以直接激活该资源文件的下载服务，并将目标文件标识移出空闲资源列表。如果不存在，目标超级节点则可以下载目标文件标识对应的资源文件，并在下载完成后，激活该资源文件的下载服务。
在一个实施例中，超级节点可以根据访问次数，决定是否关闭相应资源文件的下载服务，相应的处理可以如下：周期性统计当前周期内本地存储的空闲资源列表外的资源文件的访问次数；若访问次数小于预设阈值，则将资源文件的文件标识添加入空闲资源列表，并向Tracker服务器发送资源文件的服务停止通知。
在实施中，目标超级节点可以周期性地统计当前周期内下载服务处于激活状态的资源文件(即本地存储的空闲资源列表外的资源文件)的访问次数。若某个资源文件的访问次数小于预设阈值，则可以关闭该资源文件的下载服务，即将资源文件的文件标识添加入空闲资源列表中。同时可以向Tracker服务器发送该资源文件的服务停止通知，以使Tracker服务器在接收到该服务停止通知后，从该资源文件的节点列表中删除目标超级节点的节点标识。
在一个实施例中，基于上述空闲资源列表的机制，若在下载资源文件时发现剩余存储空间不够，则可以根据空闲资源列表删除部分资源，相应的资源文件的下载处理可以如下：若剩余存储空间小于目标文件标识对应的资源文件的文件大小，则计算空闲资源列表中各文件标识对应的热度值；按照热度值从低至高的顺序，依此删除本地存储的空闲资源列表中文件标识对应的资源文件；当剩余存储空间不小于目标文件标识对应的资源文件的文件大小时，下载目标文件标识对应的资源文件。
在实施中，目标超级节点在下载目标文件标识对应的资源文件时，可以 持续检测当前的剩余存储空间。若发现剩余存储空间小于目标文件标识对应的资源文件的文件大小，则可以提取本地的空闲资源列表，并计算空闲资源列表中各文件标识对应的热度值。之后，目标超级节点可以按照热度值从低到高的顺序，从本地的存储空间中依次删除空闲资源列表中文件标识对应的资源文件，并将文件标识从空闲资源列表中移除，从而可以优先删除掉热度值较低的资源文件。进而，当检测到剩余存储空间不小于目标文件标识对应的资源文件的文件大小时，目标超级节点可以停止删除处理，下载目标文件标识对应的资源文件。当然，目标超级节点也可以在删除资源文件的同时，进行资源文件的下载处理，以提高资源文件的下载速率。
在一个实施例中，当配置了下载服务的资源文件出现更新，超级节点可以停止该资源文件的下载服务，相应的处理可以如下：定期检测本地存储的资源文件是否存在更新需求；如果存在，则删除本地存储的资源文件，并向Tracker服务器发送资源文件的服务停止通知。
在实施中，目标超级节点可以定期检测本地存储的资源文件是否存在更新需求，此处检测的方式可以采用现有技术中的文件版本查询机制，本实施例中不对此进行详细说明。当发现某个资源文件存在更新需求(即出现了新版本)，目标超级节点则可以停止该资源文件的下载服务，即删除本地存储的资源文件，并向Tracker服务器发送该资源文件的服务停止通知。这样，超级节点及时对版本过期的资源文件进行删除，一者可以节省大量的存储资源，二者可以保证过期的资源文件不被误下载，从而提高了资源文件的下载服务质量。在本实施例中，不同于上述更新-删除的机制，超级节点若检测到某个资源文件存在数据量相比该资源文件的数据量小很多的补丁文件，则可以主动下载该补丁文件，而非对资源文件进行删除，这样可以避免资源文件被Tracker服务器多次推荐，超级节点重复下载该资源文件。
步骤206，目标超级节点向Tracker服务器反馈每个目标资源文件的服务配置信息。
在实施中，在配置完成每个目标资源文件的下载服务之后，目标超级节点可以向Tracker服务器反馈每个目标资源文件的服务配置信息，其中，服务配置信息至少可以包含各个目标资源文件的下载服务配置情况(成功或失败)。
步骤207，Tracker服务器接收目标超级节点上报的每个目标资源文件的服务配置信息，更新每个目标资源文件对应的节点列表。
在实施中，Tracker服务器接收到目标超级节点上报的服务配置信息后，可以根据该服务配置信息，更新各个目标资源文件对应的节点列表。即若目标超级节点成功配置了目标资源文件的下载服务，Tracker服务器则在目标资源文件的节点列表中添加目标超级节点的节点标识，否则不进行处理。
在一个实施例中，本实施例还公开了一种基于上述步骤201至步骤207的下载资源文件的流程，如图3所示，具体可以如下：
步骤301，Tracker服务器接收普通节点发送的资源文件的获取请求。
在实施中，用户想要通过客户端(即普通节点)获取某一资源文件时，可以打开客户端上安装的资源下载程序，在资源下载程序中输入资源文件的标识信息，资源下载程序从而可以执行该资源文件的下载任务。而基于CDN服务方的设置，部分资源已预先部署在了超级节点处。故而资源下载程序可以先判断该资源文件的下载方式，即是通过对等网络下载还是通过CDN服务器下载。如果是通过对等网络下载，资源下载程序则可以触发客户端向Tracker服务器发送资源文件的获取请求。
步骤302，Tracker服务器在资源文件对应的节点列表中，根据普通节点的网络地址和节点列表包含的各个超级节点的负载状态选取可选超级节点。
在实施中，Tracker服务器在接收到普通节点发送资源文件的获取请求后，可以读取该资源文件对应的节点列表，然后在该节点列表中，根据普通节点的网络地址选取距离普通节点较近的、负载较低的多个可选超级节点。
步骤303，Tracker服务器将可选超级节点的节点信息反馈给普通节点。
本申请实施例中，Tracker服务器确定目标超级节点上新资源文件的可添 加个数，根据可添加个数和多个待推荐资源文件对应的节点列表，在多个待推荐资源文件中选取至少一个目标资源文件，向目标超级节点发送目标资源文件的文件标识，以使目标超级超节点配置每个目标资源文件的下载服务，接收目标超级节点上报的每个目标资源文件的服务配置信息，更新每个目标资源文件对应的节点列表。这样，Tracker服务器仅负责向超级节点推送资源文件，而将具体的文件管理工作下沉到分布式部署的各个超级节点，同时Tracker服务器在进行故障恢复时也不需要重新计算所有资源文件的服务配置状态，从而既可以减轻Tracker服务器的负载压力，又可以提高整个资源下载系统的稳定性。
基于相同的技术构思，本申请实施例还提供了一种资源下载系统，所述资源下载系统包括超级节点和Tracker服务器，其中，所述超级节点用于执行如上述实施例中目标超级节点所实现的处理，所述Tracker服务器用于执行如上述实施例中Tracker服务器所实现的处理。
图4是本申请实施例提供的网络设备的结构示意图。该网络设备400可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器422(例如，一个或一个以上处理器)和存储器432，一个或一个以上存储应用程序442或数据444的存储介质430(例如一个或一个以上海量存储设备)。其中，存储器432和存储介质430可以是短暂存储或持久存储。存储在存储介质430的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对网络设备400中的一系列指令操作。在本实施例中，中央处理器422可以设置为与存储介质430通信，在网络设备400上执行存储介质430中的一系列指令操作。
网络设备400还可以包括一个或一个以上电源429，一个或一个以上有线或无线网络接口450，一个或一个以上输入输出接口458，一个或一个以上键盘456，和/或，一个或一个以上操作系统441，例如Windows Server，Mac OS X，Unix，Linux，FreeBSD等等。
网络设备400可以包括有存储器，以及一个或者一个以上的程序，其中 一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行所述一个或者一个以上程序包含用于进行上述管理资源状态信息的指令。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本申请的部分实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
Claims (18)
- 一种管理资源状态信息的方法，包括：接收Tracker服务器发送的至少一个目标资源文件的文件标识；根据所述文件标识和本地的资源存储状态，配置每个所述目标资源文件的下载服务；向所述Tracker服务器反馈每个所述目标资源文件的服务配置信息。
- 根据权利要求1所述的方法，其中，所述方法还包括：周期性根据实时带宽负载状态，确定新资源文件的可添加个数；向所述Tracker服务器发送携带所述可添加个数的资源下载请求，以使所述Tracker服务器基于所述可添加个数反馈至少一个目标资源文件的文件标识。
- 根据权利要求2所述的方法，其中，所述周期性根据实时带宽负载状态，确定新资源文件的可添加个数，包括：周期性基于当前的网络连接数与预设连接上限，确定空闲连接数；根据所述空闲连接数和剩余存储空间，按照预存的资源文件的下载性能占用标准，确定新资源文件的可添加个数。
- 根据权利要求1所述的方法，其中，所述方法还包括：定期向所述Tracker服务器上报本地的实时带宽负载状态和剩余存储空间。
- 根据权利要求1所述的方法，其中，所述根据所述文件标识和本地的资源存储状态，配置每个所述目标资源文件的下载服务，包括：对于目标文件标识，判断本地当前的空闲资源列表中是否存在所述目标文件标识；如果存在，则将所述目标文件标识移出所述空闲资源列表，否则下载所述目标文件标识对应的资源文件。
- 根据权利要求5所述的方法，其中，所述方法还包括：周期性统计当前周期内本地存储的所述空闲资源列表外的资源文件的访问次数；若所述访问次数小于预设阈值，则将所述资源文件的文件标识添加入所述空闲资源列表，并向所述Tracker服务器发送所述资源文件的服务停止通知。
- 根据权利要求6所述的方法，其中，所述下载所述目标文件标识对应的资源文件，包括：若剩余存储空间小于所述目标文件标识对应的资源文件的文件大小，则计算所述空闲资源列表中各文件标识对应的热度值；按照所述热度值从低至高的顺序，依此删除本地存储的所述空闲资源列表中文件标识对应的资源文件；当剩余存储空间不小于所述目标文件标识对应的资源文件的文件大小时，下载所述目标文件标识对应的资源文件。
- 根据权利要求1所述的方法，其中，所述方法还包括：定期检测本地存储的资源文件是否存在更新需求；如果存在，则删除本地存储的所述资源文件，并向所述Tracker服务器发送所述资源文件的服务停止通知。
- 一种管理资源状态信息的方法，包括：确定目标超级节点上新资源文件的可添加个数；根据所述可添加个数和多个待推荐资源文件对应的节点列表，在所述多个待推荐资源文件中选取至少一个目标资源文件；向所述目标超级节点发送所述目标资源文件的文件标识，以使所述目标超级超节点配置每个所述目标资源文件的下载服务；接收所述目标超级节点上报的每个所述目标资源文件的服务配置信息，更新每个所述目标资源文件对应的节点列表。
- 根据权利要求9所述的方法，其中，所述确定目标超级节点上新资源文件的可添加个数，包括：接收所述目标超级节点发送的资源下载请求，获取所述资源下载请求中携带的新资源文件的可添加个数。
- 根据权利要求9所述的方法，其中，所述确定目标超级节点上新资源文件的可添加个数，包括：根据所述目标超级节点定期上传的实时带宽负载状态和剩余存储空间，确定目标超级节点上新资源文件的可添加个数。
- 根据权利要求9所述的方法，其中，所述根据所述可添加个数和多个待推荐资源文件对应的节点列表，在所述多个待推荐资源文件中选取至少一个目标资源文件，包括：按照资源文件的热度值从高至低的顺序，依次遍历多个待推荐资源文件对应的节点列表；当待推荐资源文件的节点列表中不包含目标超级节点时，将所述待推荐资源文件选取为目标资源文件，直至所述目标资源文件的个数不小于所述可添加个数，且二者差值大于预设阈值。
- 根据权利要求12所述的方法，其中，所述方法还包括：根据预设时长内各个资源文件对应的请求数目和服务节点数目，计算各个所述资源文件对应的推荐系数；将所述推荐系数大于预设阈值的资源文件确定为待推荐资源文件。
- 根据权利要求9所述的方法，其中，所述方法还包括：接收普通节点发送的资源文件的获取请求；在所述资源文件对应的节点列表中，根据所述普通节点的网络地址和节点列表包含的各个超级节点的负载状态选取可选超级节点；将所述可选超级节点的节点信息反馈给所述普通节点。
- 根据权利要求9所述的方法，其中，所述方法还包括：在接收到目标超级节点发送的目标资源文件的服务停止通知后，从所述目标资源文件的节点列表中删除所述目标超级节点的节点标识。
- 一种资源下载系统，所述资源下载系统包括超级节点和Tracker服务器，其中，所述超级节点用于执行如权利要求1至8任一项所述的方法，所述 Tracker服务器用于执行如权利要求9至15任一项所述的方法。
- 一种网络设备，包括：至少一个处理器；以及，与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至15任一所述的方法中的处理。
- 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至15中任一所述的方法中的处理。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP20719557.9A EP3873066A1 (en) | 2020-01-03 | 2020-02-12 | Method for managing resource state information, and resource downloading system |
| US16/862,373 US11102289B2 (en) | 2020-01-03 | 2020-04-29 | Method for managing resource state information and system for downloading resource |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010006155.1A CN111200657B (zh) | 2020-01-03 | 2020-01-03 | 一种管理资源状态信息的方法和资源下载系统 |
| CN202010006155.1 | 2020-01-03 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US16/862,373 Continuation US11102289B2 (en) | 2020-01-03 | 2020-04-29 | Method for managing resource state information and system for downloading resource |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2021134861A1 true WO2021134861A1 (zh) | 2021-07-08 |
Family
ID=70746811
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/074960 WO2021134861A1 (zh) | 2020-01-03 | 2020-02-12 | 一种管理资源状态信息的方法和资源下载系统 |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP3873066A1 (zh) |
| CN (1) | CN111200657B (zh) |
| WO (1) | WO2021134861A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115150263A (zh) * | 2022-06-17 | 2022-10-04 | 浙江中控技术股份有限公司 | 一种服务集群的部署方法 |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111641705A (zh) * | 2020-05-28 | 2020-09-08 | 浪潮电子信息产业股份有限公司 | 一种请求处理方法、装置、设备及可读存储介质 |
| CN112769957B (zh) * | 2021-02-05 | 2023-09-22 | 上海哔哩哔哩科技有限公司 | 点对点网络调度方法和系统 |
| CN113110938B (zh) * | 2021-05-08 | 2023-08-29 | 网易（杭州）网络有限公司 | 一种资源分配方法、装置、计算机设备及存储介质 |
| CN113453038B (zh) * | 2021-06-25 | 2022-03-29 | 桂林电子科技大学 | 一种cdn-p2p混合架构下效用最优协同缓存管理方法 |
| CN113709209B (zh) * | 2021-07-30 | 2023-04-18 | 济南浪潮数据技术有限公司 | 一种服务器软件下载方法、系统及计算机可读存储介质 |
| CN114785796A (zh) * | 2022-04-22 | 2022-07-22 | 中国农业银行股份有限公司 | 一种数据均衡方法和装置 |
| CN115174696B (zh) * | 2022-09-08 | 2023-01-20 | 北京达佳互联信息技术有限公司 | 节点调度方法、装置、电子设备及存储介质 |
| CN116405563B (zh) * | 2023-06-08 | 2023-08-18 | 湖南快乐阳光互动娱乐传媒有限公司 | 一种基于点对点内容分发网络的资源获取方法及系统 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101188625A (zh) * | 2007-12-26 | 2008-05-28 | 腾讯科技（深圳）有限公司 | 一种实现资讯内容订阅的方法及系统 |
| US20090177772A1 (en) * | 2006-09-14 | 2009-07-09 | Huawei Technologies Co., Ltd. | Method, system and device for establishing a peer to peer connection in a p2p network |
| CN102833293A (zh) * | 2011-06-17 | 2012-12-19 | 腾讯科技（深圳）有限公司 | P2sp网络中资源下载的方法及客户端 |
| CN104967651A (zh) * | 2015-03-02 | 2015-10-07 | 深圳市腾讯计算机系统有限公司 | 基于cdn架构的数据推送、存储、下载方法和装置 |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100539502C (zh) * | 2005-12-08 | 2009-09-09 | 华为技术有限公司 | 一种多点下载的方法 |
| CN101764831B (zh) * | 2008-12-24 | 2012-09-19 | 中国移动通信集团公司 | 一种流媒体数据共享方法、共享系统和流媒体节点 |
| CN101902346A (zh) * | 2009-05-31 | 2010-12-01 | 国际商业机器公司 | P2p内容缓存系统和方法 |
| KR101210613B1 (ko) * | 2010-11-30 | 2012-12-11 | 주식회사 케이티 | 모바일 ｐ２ｐ 서비스를 제공하는 시스템 및 그 방법 |
| CN103269351A (zh) * | 2012-12-07 | 2013-08-28 | 北京奇虎科技有限公司 | 一种文件下载方法和装置 |
| US10045160B2 (en) * | 2015-05-29 | 2018-08-07 | Spacehedge, Inc. | Dynamic flow and distribution optimization |
| CN109347968B (zh) * | 2018-11-07 | 2021-09-24 | 网宿科技股份有限公司 | 一种下载资源文件的数据块的方法、设备和系统 |
| CN110247983A (zh) * | 2019-06-27 | 2019-09-17 | 北京奇艺世纪科技有限公司 | 一种均衡负载方法及系统 |
-
2020
- 2020-01-03 CN CN202010006155.1A patent/CN111200657B/zh active Active
- 2020-02-12 EP EP20719557.9A patent/EP3873066A1/en not_active Withdrawn
- 2020-02-12 WO PCT/CN2020/074960 patent/WO2021134861A1/zh unknown
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090177772A1 (en) * | 2006-09-14 | 2009-07-09 | Huawei Technologies Co., Ltd. | Method, system and device for establishing a peer to peer connection in a p2p network |
| CN101188625A (zh) * | 2007-12-26 | 2008-05-28 | 腾讯科技（深圳）有限公司 | 一种实现资讯内容订阅的方法及系统 |
| CN102833293A (zh) * | 2011-06-17 | 2012-12-19 | 腾讯科技（深圳）有限公司 | P2sp网络中资源下载的方法及客户端 |
| CN104967651A (zh) * | 2015-03-02 | 2015-10-07 | 深圳市腾讯计算机系统有限公司 | 基于cdn架构的数据推送、存储、下载方法和装置 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115150263A (zh) * | 2022-06-17 | 2022-10-04 | 浙江中控技术股份有限公司 | 一种服务集群的部署方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111200657A (zh) | 2020-05-26 |
| CN111200657B (zh) | 2021-08-27 |
| EP3873066A4 (en) | 2021-09-01 |
| EP3873066A1 (en) | 2021-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2021134861A1 (zh) | 一种管理资源状态信息的方法和资源下载系统 | |
| WO2020253266A1 (zh) | 一种提供边缘服务的方法、装置和设备 | |
| US10484464B2 (en) | Connection control device, connection control system, and non-transitory computer readable medium | |
| CN106993054B (zh) | 文件分发方法、节点及系统 | |
| US10657108B2 (en) | Parallel I/O read processing for use in clustered file systems having cache storage | |
| US11102289B2 (en) | Method for managing resource state information and system for downloading resource | |
| US9992274B2 (en) | Parallel I/O write processing for use in clustered file systems having cache storage | |
| CN110474940B (zh) | 请求调度方法、装置、电子设备、及介质 | |
| WO2013075578A1 (zh) | 网络资源文件的离线下载系统和方法 | |
| WO2013178082A1 (zh) | 图片上传方法、系统、客户端及网络服务器、计算机存储介质 | |
| WO2008025297A1 (fr) | Procédé de téléchargement de fichiers selon la technique p2p (pair à pair) et système de téléchargement p2p | |
| US8667114B2 (en) | Program update management server and program update management method | |
| US9830091B2 (en) | Policy-based data tiering using a cloud architecture | |
| US9836358B2 (en) | Ephemeral remote data store for dual-queue systems | |
| CN106936623A (zh) | 分布式缓存系统及缓存集群的管理方法 | |
| US20120179778A1 (en) | Applying networking protocols to image file management | |
| CN111200622B (zh) | 一种资源传输方法及装置、存储介质 | |
| WO2022062807A1 (zh) | 设备控制方法、服务器及存储介质 | |
| JP2003122658A (ja) | データ配送方法 | |
| US8775456B2 (en) | System and method for scheduled and collaborative distribution of software and data to many thousands of clients over a network using dynamic virtual proxies | |
| US20190334968A1 (en) | Bit rate reduction processing method for data file, and server | |
| CN111770026B (zh) | 一种网络流量控制方法和装置 | |
| JP2002259197A (ja) | アクティブコンテンツキャッシュ制御システムと、アクティブコンテンツキャッシュ制御装置及び方法と、アクティブコンテンツキャッシュ制御処理用プログラム及びそのプログラムの記録媒体 | |
| CN108076116B (zh) | 一种基于云存储数据的智能读取方法及系统 | |
| CN112860505A (zh) | 一种分布式集群的调控方法及装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| ENP | Entry into the national phase |
Ref document number: 2020719557 Country of ref document: EP Effective date: 20200428 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |