WO2008131653A1 - Système et procédé pour la réalisation d'une mémoire d'abonnement à un réseau et serveur d'abonnement - Google Patents

Système et procédé pour la réalisation d'une mémoire d'abonnement à un réseau et serveur d'abonnement Download PDF

Info

Publication number
WO2008131653A1
WO2008131653A1 PCT/CN2008/070167 CN2008070167W WO2008131653A1 WO 2008131653 A1 WO2008131653 A1 WO 2008131653A1 CN 2008070167 W CN2008070167 W CN 2008070167W WO 2008131653 A1 WO2008131653 A1 WO 2008131653A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
server
user
data resource
shared user
Prior art date
Application number
PCT/CN2008/070167
Other languages
English (en)
French (fr)
Inventor
Peng Hu
Xiangxin Yu
Original Assignee
Tencent Technology (Shenzhen) Company Limited
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 Tencent Technology (Shenzhen) Company Limited filed Critical Tencent Technology (Shenzhen) Company Limited
Publication of WO2008131653A1 publication Critical patent/WO2008131653A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1061Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
    • H04L67/1063Discovery through centralising entities

Definitions

  • the present invention relates to the field of computer technology, and more particularly to a system and method for implementing network subscription storage and a subscription server. Background of the invention
  • P2P point-to-point
  • Peer-to-Peer Peer-to-Peer
  • P2P technology is different from the shared technology using client/server mode, but has the same features and can be used as a client. / A supplement to server technology.
  • users can share some resources owned by all P2P software installed in the network through P2P software in their own computers, including processing resources, storage resources, network connection resources, etc.
  • the network can be accessed directly by other computers on the network without going through intermediate entities.
  • the computer in the network can be either a resource provider, that is, a server, or a resource acquirer, that is, a client. Therefore, from the perspective of sharing, there is a peer-to-peer relationship between computers with P2P software installed in the network, and data can be directly transferred between computers, instead of the storage resources to be shared by the server transit. Can reduce the load on servers in the network.
  • a centralized/semi-distributed structure is generally adopted.
  • a management server or a super node is set as a centralized management node, which is responsible for managing shared resources in the network, such as management of shared files.
  • maintenance including management file index information, file network link location information, user online status information, and the like.
  • FIG. 1 a process of sharing a file resource is illustrated by using a management server in the prior art.
  • user A is a downloader of a file resource
  • user B is a provider of a file resource.
  • Step S101 User A sends a query request to the management server.
  • Step S102 The management server sends the information of User B to User A;
  • the management server After receiving the query request from user A, the management server queries the user's server to query the user B to have the file resources required by user A, and sends the information of user B to user A;
  • Step S103 Data transmission is performed between user A and user B.
  • user A After receiving the information of user B, user A establishes a P2P connection with user B, and user A receives the required file resource from user B.
  • Embodiments of the present invention provide a system and method for implementing network subscription storage and a subscription server to solve the problem that the user has a download request but cannot obtain a corresponding resource.
  • an embodiment of the present invention provides a system for implementing network subscription storage, including a management server, a subscription server, and a storage server.
  • the management server is configured to send shared user information obtained from the network to the subscription server;
  • the subscription server is configured to receive a subscription event from the downloading user, and send the obtained shared user information corresponding to the data resource to the storage server when the data resource corresponding to the subscription event is in a downloadable state;
  • the storage server is configured to establish a connection with the shared user by using the shared user information, and download the data resource.
  • An embodiment of the present invention further provides a method for implementing network subscription storage.
  • the storage server establishes a connection with the shared user by using the shared user information, and downloads and stores the data resource.
  • a subscription server the subscription server is connected to a storage server, and the storage server establishes a connection with the shared user by using the shared user information provided by the subscription server, and downloads Data resource
  • the reservation server includes a receiving unit, a determining unit, and a sending unit, where: the receiving unit is configured to receive a subscription event from the downloading user;
  • the determining unit is configured to notify the sending unit when determining that the data resource corresponding to the subscription event is in a downloadable state
  • the sending unit is configured to send the obtained shared user information corresponding to the data resource to the storage server.
  • the server obtains the data resource from the shared user through the subscription event and saves it. After obtaining all the data resources, the downloading user is notified, and the downloading user obtains the required data resource from the server.
  • the embodiment of the present invention solves the problem that when the shared user is in the network and the downloading user is not in the network, the downloading user cannot obtain the required data resource from the shared user, and the data resource transfer efficiency between the users in the network is greatly improved. It brings convenience for users to download data resources on the network.
  • the server obtains the data resource that is not obtained after the interruption for the download user, and after the download is completed, notifies the download user to obtain the data resource. It is convenient for the downloading users in the network to obtain data resources.
  • FIG. 2 is a structural diagram of Embodiment 1 of the system of the present invention.
  • Embodiment 2 of the present invention is a flow chart of Embodiment 2 of the present invention.
  • FIG. 5 is a flow chart of Embodiment 4 of the present invention.
  • Figure 6 is a flow chart of Embodiment 5 of the present invention
  • Fig. 7 is a structural diagram of a sixth embodiment of the present invention. Mode for carrying out the invention
  • the system includes a management server, a subscription server, and a storage server.
  • the management server is configured to send shared user information obtained from the network to the subscription server;
  • the subscription server is configured to receive a subscription event from the downloading user, and send the obtained shared user information corresponding to the data resource to the storage server when the data resource corresponding to the subscription event is in a downloadable state;
  • the storage server is configured to establish a connection with the shared user by using the shared user information, and download the data resource.
  • connection relationship between the storage server and the user is not directly shown.
  • the storage server can establish a connection with a shared user to share the data resource by using a plurality of connection methods.
  • the download user refers to the user who needs to download the data resource from the network.
  • the shared user refers to the user who has the data resource corresponding to the subscription event in the network, and the shared user information refers to the address link information of the shared user, such as the IP address. , port, etc.
  • Data resources are files of various types and the like.
  • user A may send a subscription message to the subscription server, and the subscription server parses the received subscription message, parses the subscription event in the subscription message, and includes multiple description attributes in the subscription event.
  • Description attributes include file name keywords, file type, subscription event validity period, file size limit, number of matching downloaded files The upper limit, the file content hash, and so on.
  • the subscription server can first query the storage server by using the description attribute in the subscription event, and query whether the storage server has a data resource corresponding to the parsed subscription event, if the storage server is previously Other users download and store such data resources, and the storage server establishes a connection with user A, and user A obtains the required data resources.
  • the management server When there is no data resource to be obtained by user A in the storage server, the management server sends the user information of user B and user C to user A and the subscription server. At this time, the user A can directly establish a connection with the user B and the user C through the user information to obtain the data resource. The user A can also send a command to the subscription server, and the reservation server notifies the storage server, and the storage server passes the user B and the user C. Establish a connection and get the data resources that User A needs. After the storage server obtains and stores all the data resources required by the user A, the user A is notified by mail, short message or other forms of instant communication message to download.
  • the subscription server triggers the storage server to perform the operation, and the storage server establishes a connection according to the user information of the user 8 and the user C, and obtains User A's required data resources. After the storage server obtains and stores all the data resources required by the user A, the user A is notified by a mail, short message or other form of timely communication message to download.
  • the downloading user may complete the operation of obtaining the data resource by the storage server in the network; when the shared user exists in the network, the downloading user may leave the network.
  • the operation of obtaining data resources is done by a server in the network.
  • the user can obtain the data resource directly from the user by using the user.
  • the user A receives the user information of the user B and the user C sent by the management server, and establishes a connection with the user B and the user C through the user information. Data resources.
  • the management server sends the progress information of the data resource obtained by user A to the subscription server in real time, and the subscription server stores the progress information in the subscription database. If the transmission process of the data resource between the user A and the user B and the user C is interrupted, for example, the user A leaves the network. At this point, the subscription server will discover this situation through no change in the progress information, and the subscription server will notify the storage server to continue to obtain the remaining data resources that User A has not obtained, and the storage server will pass the user information from the management server stored in the subscription server. And establishing a connection with the user B and the user C, and obtaining the remaining data resources not obtained by the user A according to the progress information in the subscription database. After the storage server obtains and stores all the data resources required by user A, A short message or other form of instant messaging message notifies User A to download.
  • the subscription server in the above system embodiment may be static storage or dynamic loading when running the subscription database.
  • the dynamically loaded access and retrieval speed is faster, but the reservation server needs more system memory.
  • the subscription server can be embedded in the management server device, otherwise the network device should be set up separately. It should be noted that if it is operated as a standalone device, in order not to affect the normal network operation of the management server, the subscription server and the management server are connected in the same network segment, that is, connected to the same network switch, taking a network intrusion. Detecting the parallel architecture of the system, the subscription server bypasses the user data on the management server on the network switch port.
  • the storage server in the foregoing system embodiment may allocate a storage space of different capacity according to the service level of each user and set a threshold, and the size of the file downloaded by the processing user subscription cannot exceed the capacity threshold.
  • the storage server can also index the files it stores for quick access.
  • the storage server can directly copy the file in the user storage space or directly establish an object reference to the file of the repeated demand, so as to timely send the required information to the user.
  • the storage server can be a single or clustered storage device or a distributed storage policy. In the case of distributed storage, the system supports the simultaneous assignment of multiple storage servers to download different pieces of files from file providers, enabling fast uploads and downloads using Multi-Source File Transfer Protocol (MFTP).
  • MFTP Multi-Source File Transfer Protocol
  • Step S301 The download user sends a reservation message
  • the download user sends the subscription event to the pre-sale in the form of a subscription message. Subscribe to the server and management server.
  • Step S302 The subscription server parses the subscription message.
  • the subscription server resolves the subscription event from the subscription message and saves it in the subscription database.
  • the subscription database the user record information of all download users and the download record information of the subscribed data resources of the download user are recorded.
  • the download record information may include whether the download has been completely downloaded to the storage server, and the downloaded progress is performed. Information, etc.
  • Step S303 The subscription server determines whether a corresponding data resource exists in the storage server.
  • the reservation server determines whether there are other download users before booking the same data resource, whether the data resource is completely downloaded by the storage server and has not been taken away, and if yes, step S304 is performed, and if not, the process ends;
  • Step S304 The subscription server notifies the storage server, and the storage server sends the data resource to the download user.
  • the storage server receives the notification from the subscription server, obtains the downloaded user information, and directly copies the corresponding data resources and sends them to the download user.
  • Step S305 The management server parses the subscription message.
  • the management server parses the subscription message and gets the subscription event.
  • Step S306 The management server determines whether there is shared user information.
  • the management server determines whether there is shared user information in the network that has a data resource corresponding to the subscription event. If yes, step S307 is performed, and if not, step S308 is performed.
  • Step S308 Notifying the downloading user
  • the management server notifies that there are no shared users on the network.
  • Step S307 The management server determines whether the download user needs to download; After the shared user information exists in the network, if the downloading user wants to establish a connection download through the shared user, step S309 is performed, and if the downloading user does not perform the connection, step S310 is performed.
  • Step S309 Download the user to connect
  • the download user obtains the shared user information through the management server, establishes a P2P connection with the shared user, and downloads the required data resources.
  • Step S310 The storage server performs downloading.
  • the download user may leave the network.
  • the management server notifies the subscription server, and attaches the shared user information in the notification.
  • the storage server is triggered. Use the shared user information to establish a P2P connection with the shared user, and obtain the data resources needed to download the user.
  • step S311 is performed after the step S304, the step S309, and the step S310.
  • Step S311 updating the subscription database
  • the subscription database is updated, the subscription events in the subscription database are deleted, and the relevant records are recorded.
  • the downloading user After the storage server obtains and stores all the data resources required by the downloading user, the downloading user is notified by a mail, short message or other form of timely communication message, and the downloading user obtains the data resource from the storage server after receiving the notification.
  • Step S304 and step S309 can be performed simultaneously, which speeds up the downloading speed of the downloading user and saves time for the downloading user to obtain all the data resources.
  • step S309 when downloading the user for downloading, if the downloading user leaves the network after not obtaining all the data resources, the downloading user only obtains a partial segment of the data resource, and in this case, the solution is solved by the second embodiment.
  • Step S401 The download user sends a reservation message
  • Step S402 The subscription server parses the subscription message.
  • Step S403 The subscription server sends the subscription event to the management server.
  • the subscription event is sent to the management server because the subscription server determines that the data resource required by the user is not downloaded in the storage server;
  • Step S404 The management server determines that the shared user information exists.
  • Step S405 The management server determines that the download user downloads by itself
  • Step S406 Download the user to connect, and obtain the data resource
  • the download user establishes a connection with the shared user and obtains a data resource
  • Step S407 The management server determines whether the download user goes offline.
  • the management server continuously determines whether the download user is still in the network, if yes, continues to determine; if not, proceeds to step S408; step S408: the management server notifies the subscription server;
  • the management server will notify the subscribing server that the downloading user is offline, that is, the downloading user has disconnected from the network, and notifies the corresponding shared user information and progress information of the subscribing server. Wait;
  • Step S409 The subscription server triggers the storage server download
  • the subscription server triggers the storage server reference progress information, establishes a connection with the shared user by using the shared user information, and obtains the remaining fragments of the data resource that are not obtained after the download user goes offline from the shared user. .
  • Step S410 Update the subscription database.
  • the download user After the storage server obtains and stores the remaining fragments of the data resource after the download user goes offline, the download user is notified by mail, short message or other forms of timely communication message, and the download user obtains the remaining fragments of the data resource from the storage server after receiving the notification. .
  • the above two embodiments are all sharing users in the network, downloading users leaving the network or downloading users after disconnecting the network during the download process, how the network downloads and saves data resources for the downloading users. Since both the shared user and the downloading user are reluctant in the network, there may be a case where the downloading user goes online to submit the subscription event, and the shared user is not in the network, as in steps S306 and S308 in the first embodiment, but after The shared user goes online. At this time, if the download user has left the network or is still in the network, the solution for such a situation is explained by the third embodiment, as shown in FIG. 5 .
  • Step S501 The management server determines whether a shared user joins in the network.
  • the management server continuously determines whether there is a shared user joining in the network. When it is determined that a shared user joins the network, the management server sends the shared user information to the subscription server;
  • Step S502 The subscription server retrieves the subscription database.
  • the subscription server After receiving the shared user information, the subscription server retrieves the subscription database according to the data resources owned by the shared user. Since the subscription server has previously stored the subscription event in the subscription database, and the subscription event and the data resource have a mutual correspondence, retrieves the corresponding subscription event in the subscription database through the data resource.
  • Step S503 determining whether there is a reservation event
  • step S504 retrieves whether a subscription event exists in the subscription database through a data resource. If yes, step S504 is performed, and if not, it ends.
  • Step S504 determining whether the download user is online
  • Step S505 The management server determines whether the download user establishes a connection; if yes, step S506 is performed, and if no, step S507 is performed.
  • Step S506 The download user establishes a connection
  • the download user can obtain the shared user information through the subscription server or the management server, and establish a P2P connection with the shared user to obtain the required data resources.
  • Step S507 The storage server performs downloading.
  • the management server notifies the subscription server, and the storage server is triggered by the subscription server, and the storage server establishes a connection with the shared user through the shared user information in the subscription server. Download all the data resources your users need.
  • Step S508 Update the subscription database
  • the subscription database is updated, the subscription events in the subscription database are deleted, and the relevant records are recorded.
  • the downloading user After the storage server obtains and stores all the data resources required by the downloading user, the downloading user is notified by a mail, short message or other form of timely communication message, and the downloading user obtains the data resource from the storage server after receiving the notification.
  • step S506 the downloading user selects to download by itself, that is, step S506 is performed.
  • step S506 the step in the second embodiment may be adopted in this case.
  • S407 to step S410 are solved; of course, there may be a case that after the connection between the download user and the shared user is established, since the shared user leaves the network, the download user only leaves part of the data resource and then leaves the network, and then the shared user joins again. Network, for this case, the solution is explained by the fourth embodiment. See Figure 6,
  • Step S601 The management server notifies the subscription server; Since the shared user leaves the network, the download user and the shared user disconnect, the management server will notify the subscription server that the shared user is offline, that is, the shared user has disconnected from the network, and notifies the reservation server of the progress information before disconnection;
  • Step S602 The subscription server records the received information.
  • the subscription server logs the received information to the subscription database and saves it with the corresponding subscription event;
  • Step S603 The management server determines whether there is a shared user joining in the network.
  • the management server continuously determines whether there is a shared user joining in the network.
  • the management server sends the shared user information to the subscription server.
  • the newly added shared user may be the same shared user before the last disconnection, or may be a different shared user, as long as the shared user has the data resources required to download the user.
  • Step S604 The subscription server retrieves the subscription database
  • the subscription server After receiving the shared user information, the subscription server retrieves the subscription database according to the data resources owned by the shared user. Since the subscription server has previously stored the subscription event in the subscription database, there is a correspondence between the subscription event and the data resource. Ability to retrieve the corresponding subscription event in the subscription database through the data resource.
  • Step S605 determining whether there is a reservation event
  • step S606 retrieves whether a subscription event exists in the subscription database through a data resource. If yes, indicating that the download user needs to obtain the corresponding data resource from the shared user, step S606 is performed, and if not, the process ends.
  • Step S606 determining whether the download user is online
  • step S607 is performed, and if it is not online, step S609 is performed.
  • Step S607 The management server determines whether the download user establishes a connection. If yes, step S608 is performed, and if no, step S609 is performed.
  • Step S608 The download user establishes a connection
  • the download user can obtain the shared user information through the subscription server or the management server, and establish a P2P connection with the shared user to obtain the remaining fragments of the data resource that were not obtained after the last disconnection.
  • Step S609 The storage server performs downloading.
  • the management server notifies the subscription server that the subscription server will look in the subscription database and find the progress information of the downloaded user recorded in the corresponding subscription event.
  • the subscription server triggers the storage server, and the storage server establishes a connection with the shared user by sharing the user information in the subscription server, and obtains the remaining segments of the data user that the last downloaded user did not obtain the data resource after disconnecting from the shared user according to the progress information.
  • Step S610 Updating the subscription database
  • the subscription database is updated, the subscription events in the subscription database are deleted, and the relevant records are recorded.
  • the download user After the storage server obtains and stores the remaining fragments of the data resource after the download user goes offline, the download user is notified by mail, short message or other forms of timely communication message, and the download user obtains the remaining fragments of the data resource from the storage server after receiving the notification. .
  • the number of times the subscription server receives the shared user message may be very frequent.
  • multiple subscription servers may be established to implement load balancing. Multiple subscription servers may be used. Cluster or distributed structure; The threshold of the number of shared user information can also be received according to the time period or the threshold for receiving the shared user information.
  • the subscription server has a critical role in implementing the network subscription storage function.
  • the composition of the reservation server it is carried out by the sixth embodiment of the present invention. Description, see Figure 7,
  • the reservation server 701 includes: a receiving unit 702, a determining unit 703, and a transmitting unit 704, where:
  • the receiving unit 702 is configured to receive a subscription event from a download user.
  • the determining unit 703 is configured to notify the sending unit 704 when it is known that the data resource corresponding to the subscription event is in a downloadable state;
  • the sending unit 704 is configured to send the obtained shared user information corresponding to the data resource.
  • connection established between the respective servers, download users, and shared users during data transmission may be a P2P connection, but is not limited to this connection.
  • Data can also be transmitted through other connection methods, such as direct connection or other connection, and the storage server can also be implemented through a network hard disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Description

一种实现网络预订存储的***和方法及预订服务器
技术领域
本发明涉及计算机技术领域, 特别是指一种实现网络预订存储的系 统和方法及预订服务器。 发明背景
随着计算机网络技术的发展, 网络中的资源共享变得更加快捷、 方 便。 目前采用的最多的资源共享方式是点到点 (P2P, Peer-to-Peer )技 术, P2P技术不同于采用客户 /服务器( Client/Server )模式的共享技术, 但有相同之处, 可作为客户 /服务器技术的一种补充。
在采用 P2P技术的互联网中, 用户可通过自己计算机中的 P2P软件 共享网络中所有安装 P2P软件的计算机所拥有的部分资源, 这些资源包 括处理资源、 存储资源、 网络连接资源等, 这些资源借助于网络, 能被 网络中其它计算机直接访问而无需经过中间实体。 在共享的过程中, 网 络中的计算机既可以是资源提供者, 即服务器( Server ), 又可以是资源 获取者, 即客户端 (Client )。 因此, 从共享的角度来看, 网络中安装有 P2P软件的计算机之间是一种对等的关系, 计算机之间可以直接进行数 据传输, 而不再需要通过服务器中转所要共享的存储资源, 从而能够降 低网络中服务器的负载。
由于网络中大量用户的计算机采用 P2P技术, 使用户之间的文件共 享非常容易, 并且在网络流量中占据着大部分带宽。 根据 Cache Logic 公司的统计, 在 2006年 1月, BT ( Bit torrent )、 电驴( eDonkey )等采 用 P2P技术的共享下载软件所产生的网络流量, 已经占据整个互联网 71 %的带宽。 借助 P2P技术的软件, 用户可以通过互联网轻松地获取分 布在全球各个计算机中的共享文件, 尤其是热门文件, 通过 P2P技术能 够在互联网中非常迅速地传播扩散。
网络中采用 P2P技术时,其网络逻辑结构主要分为集中式 /半分布式 结构和全分布式结构。 其中, 在采用 P2P技术互联网中, 普遍采用集中 式 /半分布式结构,这类结构的网络中设置有管理服务器或超级节点作为 集中管理节点, 负责管理网络中的共享资源, 例如共享文件的管理和维 护, 具体包括管理文件索引信息、 文件网络链接定位信息、 用户在线状 态信息等。 参见图 1 , 以现有技术中的管理服务器为例说明文件资源共 享的过程, 在图 1中, 用户 A是文件资源的下载者, 用户 B是文件资源 的提供者。
步骤 S101: 用户 A向管理服务器发送查询请求;
用户 A使用自己的计算机通过管理服务器查询所需要的文件资源; 步骤 S102: 管理服务器将用户 B的信息发送给用户 A;
管理服务器接收到用户 A的查询请求后,在自身的服务器上查询后, 查询到用户 B拥有用户 A所需的文件资源, 将用户 B的信息发送给用 户 A;
步骤 S103: 用户 A与用户 B之间进行数据传输。
用户 A收到用户 B的信息后, 与用户 B建立 P2P连接, 用户 A从 用户 B处接收所需要的文件资源。
在上述采用 P2P技术的网络中, 由于网络中的各个用户的计算机接 入、 离开网络具有艮强的动态特性。 因此, 当用户 Β的计算机离开网络, 或用户 Α的计算机由于自身原因退出网络,不能以足够的时间在网络中 获取用户 B全部的文件资源时, 都会造成用户 A只获得到用户 B的部 分文件资源,剩余的文件资源只能等到下次与用户 B同时接入到网络中 时获得。但是,用户 A与用户 B的计算机是否能同时接入到网络中是不 确定的, 从而可能导致当用户 B的计算机接入网络中, 而此前请求下载 的用户 A已经退出网络, 无法将文件资源共享给用户 A。
由此可见, 虽然网络的文件资源是丰富的, 但存在用户有下载请求 而无法获得相应资源的问题。 发明内容
本发明实施例提供一种实现网络预订存储的***和方法及预订服务 器, 以解决上述用户有下载请求, 但无法获得相应资源的问题。
为解决上述问题,本发明实施例提供一种实现网络预订存储的***, 包括管理服务器、 预订服务器、 存储服务器,
所述管理服务器, 用于将从网络中获得的共享用户信息发送至预订 服务器;
所述预订服务器, 用于接收来自下载用户的预订事件, 当所述预订 事件所对应的数据资源处于可下载状态时, 将获得的与所述数据资源相 对应的共享用户信息发送至存储服务器;
所述存储服务器,用于利用所述共享用户信息与共享用户建立连接, 下载所述数据资源。
本发明实施例还提供一种实现网络预订存储的方法,
接收来自下载用户的预订事件;
当判定所述预订事件相对应的数据资源处于可下载时, 获得与所述 数据资源相对应的共享用户信息;
存储服务器利用所述共享用户信息与共享用户建立连接, 下载并存 储所述数据资源。
一种预订服务器, 该预订服务器与存储服务器连接, 所述存储服务 器利用该预订服务器提供的共享用户信息与共享用户建立连接, 并下载 数据资源;
该预订服务器包括接收单元、 判断单元和发送单元, 其中: 所述接收单元, 用于接收来自下载用户的预订事件;
所述判断单元, 用于当判定所述预订事件所对应的数据资源处于可 下载状态时, 通知所述发送单元;
所述发送单元, 用于将获得的与所述数据资源相对应的共享用户信 息发送至所述存储服务器。
本发明的实施例在下载用户离开网络后, 服务器通过预订事件从共 享用户处获得数据资源并保存, 当获得全部的数据资源后, 通知下载用 户, 下载用户从服务器中获得所需的数据资源。 本发明的实施例解决了 共享用户在网络中而下载用户不在网络中时, 下载用户无法从共享用户 处获得所需的数据资源的问题, 较大地提高网络中各个用户之间的数据 资源传递效率, 为网络中用户下载数据资源带来了方便。 特别是对于下 载用户在获得数据资源的过程中, 如果与共享用户的连接出现中断, 则 服务器为下载用户获得在中断后未获得的数据资源, 并在下载完成后, 通知下载用户获得数据资源, 为网络中下载用户获得数据资源带来方 便。 附图简要说明
图 1是现有技术中文件资源共享的流程图;
图 2是本发明***实施例一的结构图;
图 3是本发明实施例二的流程图;
图 4是本发明实施例三的流程图
图 5是本发明实施例四的流程图;
图 6是本发明实施例五的流程图; 图 7是本发明实施例六的结构图。 实施本发明的方式
为详细说明本发明解决现有技术中所存在的问题, 下面结合附图详 细说明本发明的各个实施例。
参见图 2, 首先说明本发明***的实施例一。 在此实施例中, *** 包括管理服务器、 预订服务器和存储服务器,
所述管理服务器, 用于将从网络中获得的共享用户信息发送至预订 服务器;
所述预订服务器, 用于接收来自下载用户的预订事件, 当所述预订 事件所对应的数据资源处于可下载状态时, 将获得的与所述数据资源相 对应的共享用户信息发送至存储服务器;
所述存储服务器,用于利用所述共享用户信息与共享用户建立连接, 下载所述数据资源。
在图 2所示***结构中, 并没有直接示出存储服务器与用户之间的 连接关系。 本领域技术人员可以意识到, 存储服务器可以通过多种连接 方式, 利用共享用户信息与共享用户建立连接以下载所述数据资源。
其中, 下载用户是指需要从网络中下载数据资源的用户, 共享用户 是指网络中拥有与预订事件所对应数据资源的用户, 而共享用户信息是 指这些共享用户的地址链接信息, 如 IP地址、 端口等。 数据资源为各类 形式的文件等。
在该实施例中, 如果用户 A作为下载用户, 则用户 A可向预订服务 器发送预订消息, 预订服务器解析接收到预订消息, 解析出预订消息中 的预订事件, 预订事件中包括有多个描述属性。 描述属性包括文件名关 键词、 文件类型、 预订事件有效期、 文件大小限制、 匹配下载的文件数 目上限、 文件内容哈希值等。
解析出的预订事件后, 预订服务器可通过预订事件中的描述属性先 向存储服务器中查询, 查询存储服务器中是否已经存有与解析出的预订 事件相对应的数据资源, 如果存储服务器中之前为其它用户下载并存储 有这类数据资源,则存储服务器与用户 A建立连接,用户 A获得所需的 数据资源。
当然, 用户 A向预订服务器发送预订消息的同时, 还可同时向管理 服务器发送相同的预订消息。 管理服务器将解析预订消息, 并按照解析 出的预订事件查找网络中的共享用户, 如果网络中存在有共享用户, 且 共享用户为用户 B和用户 C, 则管理服务器将共享用户 B、 共享用户 C 的信息发送至用户 A, 用户 A与用户 B、 用户 C之间建立连接, 用户 A 获得数据资源。如果此时用户 A还与存储服务器建立连接,则用户 A可 同时从用户 B、 用户 C及存储服务器处获得数据资源, 以便能够用最少 的时间来获得所需的数据资源。
当存储服务器中没有用户 A所要获得的数据资源时, 管理服务器会 将用户 B和用户 C的用户信息发送给用户 A和预订服务器。 此时, 用 户 A既可通过用户信息直接与用户 B、用户 C建立连接,获得数据资源; 用户 A也可向预订服务器发送命令, 由预订服务器通知存储服务器, 由 存储服务器通过用户 B、 用户 C 建立连接, 获得用户 A所需要的数据 资源。存储服务器获得并存储用户 A所需要的全部数据资源后,以邮件、 短信或其它形式的即时通信消息通知用户 A进行下载。
由于用户 用户 C作为数据资源的提供者, 不可能保证实时在网 络中, 如果用户:8、 用户 C没有在网络中, 管理 务器则无法查询出用 户 B、 用户 C 的用户信息, 也就无法向预订服务器和用户 A提供共享 用户信息, 用户 A没有共享用户信息, 也会离开网络。 管理服务器会向 预订服务器发送没有共享用户信息的通知, 预订服务器接收到该通知 后,会将解析出的预订事件存储到预订数据库中。如果用户 B、用户 C加 入到网络中后, 管理服务器发现后会将用户 B、 用户 C的用户信息发送 至预订服务器, 预订服务器接收到用户 ^ 用户 C的用户信息后, 判断 所述预订数据库中是否有与用户信息相对应的预订事件, 由于预订数据 库中已经存有用户 A的预订事件,则预订服务器会触发存储服务器执行 操作, 存储服务器会按照用户 8、 用户 C的用户信息建立连接, 获得用 户 A所需要的数据资源。存储服务器获得并存储用户 A所需要的全部数 据资源后, 以邮件、 短信或其它形式的及时通信消息通知用户 A进行下 载。
在上述的实施例中, 当共享用户不存在网络中时, 下载用户可将获 得数据资源的操作由网络中的存储服务器来完成; 当共享用户存在于网 络中时, 下载用户既可离开网络, 由网络中的服务器完成获得数据资源 的操作。 还可以由下载用户直接通过共享用户来获得数据资源, 如前面 所描述的用户 A接收管理服务器发送的用户 B、用户 C的用户信息, 通 过用户信息与用户 B、 用户 C建立连接, 获得所需要的数据资源。
在用户 A通过用户 B、 用户 C获得数据资源的过程中, 管理服务器 会将用户 A获得数据资源的进度信息实时发送至预订服务器,预订服务 器会将进度信息存储到预订数据库中。 如果用户 A与用户 B、用户 C之 间的数据资源的传输过程出现中断, 例如用户 A离开网络。 此时, 预订 服务器会通过进度信息没有变化来发现这种情况, 而预订服务器会通知 存储服务器继续获得用户 A未获得的剩余数据资源,存储服务器会通过 预订服务器中存储的来自管理服务器的用户信息, 与用户 B、 用户 C建 立连接,并按照预订数据库中的进度信息获得用户 A未获得的剩余数据 资源。存储服务器获得并存储用户 A所需要的全部数据资源后,以邮件、 短信或其它形式的即时通信消息通知用户 A进行下载。
上述***实施例中的预订服务器, 在运行预订数据库时可以是静态 存储, 也可以动态加载, 相比而言, 动态加载的访问与检索速度较快, 但需要预订服务器具有较多的***内存。 对于已经实现完成的预订事 件, 可以将其静态存储, 从而减少内存占用。 相对而言, 如果预订规模 较小, 则预订服务器可以嵌入管理服务器设备, 否则应单独架设网络设 备。 需要注意的是, 如果作为独立设备运行, 为了不影响管理服务器的 正常网络操作, 将预订服务器和管理服务器连接在同一个网段内, 即连 接在同一个网路交换机中, 采取类似于网络入侵检测***的并联架构, 预订服务器在网络交换机端口上旁路侦听管理服务器上的用户数据。
上述***实施例中的存储服务器, 可根据每个用户的服务等级分配 不同容量的存储空间并设定阈值, 处理用户预订所下载的文件大小不能 超出此容量阈值。 存储服务器还可对其存储的文件做索引, 以便快速查 找。 当两个用户的预订事件相同, 即所预订的内容有重复, 则存储服务 器端可以直接在用户存储空间内复制文件或直接对重复需求的文件建 立对象引用, 以便及时向用户发送其所需要的数据资源。 存储服务器可 以是单个或集群存储设备, 也可以采取分布式存储的策略。 对于分布式 存储的情况, ***支持同时指派多个存储服务器从文件提供者下载文件 的不同片段, 从而能够利用多源文件传输协议(MFTP ) 实现快速上传 和下载。
上面所描述的***实施例详细说明***中各个服务器的关系及功 能, 下面详细描述实现预订存储流程的实施例。 首先描述实施例二, 参 见图 3,
步骤 S301: 下载用户发送预订消息;
为便于传输, 下载用户将预订事件以预订消息的形式同时发送至预 订服务器和管理服务器。
步骤 S302: 预订服务器解析所述预订消息;
预订服务器从预订消息中解析出预订事件并保存在预订数据库中。 在预订数据库中, 记录有所有下载用户的用户信息和该下载用户的所预 订的数据资源的下载记录信息, 比如, 所述下载记录信息可以包括是否 已经全部下载到存储服务器中、 已下载的进度信息等。
步骤 S303 : 预订服务器判断存储服务器中是否存在相应的数据资 源;
预订服务器判断之前是否存在其它下载用户也预订相同的数据资 源, 该数据资源是否被存储服务器全部下载且并未被取走, 如果是, 则 执行步骤 S304 , 如果否, 则结束;
步骤 S304: 预订服务器通知存储服务器, 存储服务器向下载用户发 送数据资源;
由于存储服务器中存储有其它下载用户预订的数据资源, 还未被取 走, 存储服务器接收到来自预订服务器的通知, 得到下载用户信息, 直 接将相应的数据资源复制后发送给下载用户。
步骤 S305: 管理服务器解析预订消息;
管理服务器解析预订消息, 获得预订事件。
步骤 S306: 管理服务器判断是否存在共享用户信息;
管理服务器判断是网络中是否存在拥有与所述预订事件相对应数据 资源的共享用户信息。 如果有, 则执行步骤 S307 , 如果没有, 则执行步 骤 S308。
步骤 S308: 通知下载用户;
管理服务器通知网络中不存在共享用户。
步骤 S307: 管理服务器判断下载用户是否需要下载; 当网络中存在有共享用户信息后, 如果下载用户要通过共享用户建 立连接下载, 则执行步骤 S309, 如果下载用户不进行连接, 则执行步骤 S310。
步骤 S309: 下载用户进行连接;
下载用户通过管理服务器获得共享用户信息, 与共享用户之间建立 P2P连接, 下载所需的数据资源。
步骤 S310: 存储服务器进行下载;
如果下载用户没有与共享用户建立连接, 则表明下载用户可能会离 开网络, 此时, 管理服务器会通知预订服务器, 并在通知中附着共享用 户信息, 预订服务器收到共享用户信息后, 触发存储服务器利用共享用 户信息与共享用户之间建立 P2P连接,并获得下载用户所需的数据资源。
在步骤 S304、 步骤 S309、 步骤 S310之后, 下载用户获得到所有的 数据资源后, 执行步骤 S311。
步骤 S311 : 更新预订数据库;
预订数据库进行更新, 将预订数据库中的预订事件删除, 并记录相 关曰志。
存储服务器获得并存储了下载用户所需要的全部数据资源后, 以邮 件、 短信或其它形式的及时通信消息通知下载用户, 下载用户接到通知 后从存储服务器中获得所述数据资源。
在实施例一中, 下载用户向预订服务器提交预订事件后, 便可以由 存储服务器直接下载, 存储服务器全部下载后, 再通知下载用户。 步骤 S304与步骤 S309可同时进行, 这样会加快下载用户的下载速度, 为下 载用户获得全部的数据资源节省时间。 在步骤 S309 中, 下载用户进行 下载时, 如果下载用户在没有获得全部数据资源后离开网络, 则下载用 户只获得数据资源的部分片段, 对于这种情况, 通过实施例二说明解决 的方案, 参见图 4,
步骤 S401 : 下载用户发送预订消息;
步骤 S402: 预订服务器解析所述预订消息;
步骤 S403: 预订服务器将预订事件发送至管理服务器;
由于预订服务器判断出存储服务器中没有下载用户所需的数据资 源, 将预订事件发送至管理服务器;
步骤 S404: 管理服务器判断出存在共享用户信息;
步骤 S405: 管理服务器判断出下载用户自行下载;
步骤 S406: 下载用户进行连接, 获得数据资源;
下载用户与共享用户建立连接, 获得数据资源;
步骤 S407: 管理服务器判断下载用户是否下线;
在下载用户获得数据资源的过程中, 管理服务器不断判断下载用户 是否还在网络中, 如果在, 则继续判断; 如果不在, 则执行步骤 S408; 步骤 S408: 管理服务器通知预订服务器;
由于下载用户可能会由于多种原因断开网络连接, 此时, 管理服务 器将会通知预订服务器该下载用户下线, 即下载用户已经断开网络, 并 通知预订服务器相应的共享用户信息、 进度信息等;
步骤 S409: 预订服务器触发存储服务器下载;
由于所有 P2P***都支持文件下载追踪并记录进度信息, 预订服务 器触发存储服务器参考进度信息, 利用共享用户信息与共享用户建立连 接, 从共享用户处获得下载用户下线后未获得数据资源的剩余片段。
步骤 S410: 更新预订数据库。
存储服务器获得并存储下载用户下线后未获得数据资源的剩余片段 后, 以邮件、 短信或其它形式的及时通信消息通知下载用户, 下载用户 接到通知后从存储服务器中获得数据资源的剩余片段。 上述两个实施例都是共享用户在网络中, 下载用户离开网络或下载 用户在下载过程中断开网络后, 网络是如何为下载用户下载并保存数据 资源的。 由于在网络中, 共享用户和下载用户都具有艮强的动态性, 还 可能会出现下载用户上线提交预订事件后, 共享用户不在网络中, 如实 施例一中的步骤 S306、 S308 , 但是, 之后共享用户上线, 此时, 如果下 载用户已经离开网络或还在网络中, 对于这类情况的解决方案, 通过实 施例三进行说明, 参见图 5 ,
步骤 S501 : 管理服务器判断网络中是否有共享用户加入;
管理服务器不停的判断网络中是否有共享用户加入, 当判断出有共 享用户加入到网络中后, 管理服务器将共享用户信息发送到预订服务 器;
步骤 S502: 预订服务器检索预订数据库;
预订服务器收到共享用户信息后, 根据该共享用户所拥有的数据资 源检索预订数据库, 由于预订服务器之前已经将预订事件存储到预订数 据库中, 而预订事件与数据资源之间存在相互对应关系, 能够通过数据 资源检索预订数据库中是否存在相应的预订事件。
步骤 S503: 判断是否存在预订事件;
通过数据资源检索预订数据库中是否存在预订事件。 如果存在, 则 执行步骤 S504 , 如果不存在, 则结束。
步骤 S504: 判断下载用户是否在线;
预订数据库中存在有相应的预订事件, 表明有下载用户需要从共享 用户处获得相应的数据资源, 此时, 先判断下载用户是否在网络中, 即 是否在线。 预订服务器将下载用户信息发送至管理服务器, 由管理服务 器判断下载用户是否在线, 如果在线, 则执行步骤 S505 , 如果不在线, 则执行步骤 S507。 步骤 S505: 管理服务器判断下载用户是否建立连接; 如果是, 则执行步骤 S506, 如果否, 则执行步骤 S507。
步骤 S506: 下载用户建立连接;
当下载用户需要自行下载时, 则下载用户可通过预订服务器或管理 服务器处获得共享用户信息, 并与共享用户建立 P2P连接, 获得所需的 数据资源。
步骤 S507: 存储服务器进行下载;
如果下载用户不在线或下载用户由于其它原因无法与共享用户建立 连接, 则管理服务器通知预订服务器, 由预订服务器触发存储服务器, 存储服务器通过预订服务器中的共享用户信息, 与共享用户建立连接, 获得下载用户所需的全部数据资源。
步骤 S508: 更新预订数据库;
在下载结束后, 预订数据库都会进行更新, 将预订数据库中的预订 事件删除, 并记录相关曰志。
存储服务器获得并存储了下载用户所需要的全部数据资源后, 以邮 件、 短信或其它形式的及时通信消息通知下载用户, 下载用户接到通知 后从存储服务器中获得所述数据资源。
在实施例三中, 下载用户选择自行下载, 即执行步骤 S506, 在下载 用户从共享用户处获得数据资源的过程中, 如果下载用户与网络断开连 接,这种情况可采取实施例二中步骤 S407至步骤 S410进行解决; 当然, 还可能存在的情况是下载用户与共享用户之间建立连接后, 由于共享用 户离开网络, 下载用户只获得部分数据资源后也离开网络, 之后, 共享 用户再次加入网络,对于这种情况,通过实施例四进行说明解决的方案。 参见图 6,
步骤 S601 : 管理服务器通知预订服务器; 由于共享用户离开网络, 下载用户和共享用户断开连接, 管理服务 器将会通知预订服务器该共享用户下线, 即共享用户已经断开网络, 并 通知预订服务器断开前的进度信息等;
步骤 S602: 预订服务器记录接收到的信息;
预订服务器会将所接收到信息记录到预订数据库中, 与相应的预订 事件保存在一起;
步骤 S603: 管理服务器判断网络中是否有共享用户加入; 管理服务器不停的判断网络中是否有共享用户加入, 当有共享用户 加入到网络中后, 管理服务器将共享用户信息发送到预订服务器。 新加 入的共享用户可以是上次断开前相同的共享用户, 也可以不同的共享 用户, 只要该共享用户有下载用户所需的数据资源即可。
步骤 S604: 预订服务器检索预订数据库;
预订服务器收到共享用户信息后, 会根据该共享用户所拥有的数据 资源检索预订数据库, 由于预订服务器之前已经将预订事件存储到预订 数据库中, 而预订事件与数据资源之间存在相互对应关系, 能够通过数 据资源检索预订数据库中是否存在相应的预订事件。
步骤 S605: 判断是否存在预订事件;
通过数据资源检索预订数据库中是否存在预订事件。 如果存在, 表 明有下载用户需要从共享用户处获得相应的数据资源, 则执行步骤 S606, 如果不存在, 则结束。
步骤 S606: 判断下载用户是否在线;
此时, 先判断下载用户是否在网络中, 即是否在线。 预订服务器将 下载用户信息发送至管理服务器, 由管理服务器判断下载用户是否在 线, 如果在线, 则执行步骤 S607, 如果不在线, 则执行步骤 S609。
步骤 S607: 管理服务器判断下载用户是否建立连接; 如果是, 则执行步骤 S608 , 如果否, 则执行步骤 S609。
步骤 S608: 下载用户建立连接;
当下载用户需要自行下载时, 则下载用户可通过预订服务器或管理 服务器处获得共享用户信息, 并与共享用户建立 P2P连接, 获得上次断 开后未获得数据资源的剩余片段。
步骤 S609: 存储服务器进行下载;
如果下载用户不在线或下载用户由于其它原因无法与共享用户建立 连接, 则管理服务器通知预订服务器, 预订服务器将在预订数据库中查 找, 找到相应的预订事件中所记录的下载用户的进度信息, 由预订服务 器触发存储服务器, 存储服务器通过预订服务器中的共享用户信息, 与 共享用户建立连接, 按照进度信息获得上次下载用户在与共享用户断开 后未获得数据资源的剩余片段。
步骤 S610: 更新预订数据库;
在下载结束后, 预订数据库都会进行更新, 将预订数据库中的预订 事件删除, 并记录相关曰志。
存储服务器获得并存储下载用户下线后未获得数据资源的剩余片段 后, 以邮件、 短信或其它形式的及时通信消息通知下载用户, 下载用户 接到通知后从存储服务器中获得数据资源的剩余片段。
由于***在工作过程中, 共享用户加入到网络中后, 预订服务器接 收到共享用户消息次数可能非常频繁, 为减少预订服务器的负担, 可建 立多个预订服务器实现负载均衡, 多个预订服务器可采用集群或分布式 结构; 还可以按照时间周期或接收到共享用户信息数量的阈值作为触发 预订服务器的工作条件。
在上述各个实施例中, 预订服务器在实现网络预订存储功能时, 具 有很关键的作用。 关于预订服务器的组成, 通过本发明的实施例六进行 说明, 参见图 7,
预订服务器 701 , 包括: 接收单元 702、 判断单元 703和发送单元 704, 其中:
所述接收单元 702, 用于接收来自下载用户的预订事件;
所述判断单元 703 , 用于当得知所述预订事件所对应的数据资源处 于可下载状态时, 通知所述发送单元 704;
所述发送单元 704, 用于将获得的与所述数据资源相对应的共享用 户信息发送出去。
在上面所描述的各个实施例中, 各个服务器、 下载用户、 共享用户 之间在进行数据传输时建立的连接可以是 P2P连接, 但不仅限于这种连 接方式。 还可通过其它的连接方式进行数据传输, 如直接连接或者通过 其它方式连接等, 存储服务器也可通过网络硬盘等方式实现。
对于本发明各个实施例中所阐述的***和方法, 凡在本发明的精神 和原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明 的保护范围之内。

Claims

权利要求书
1、 一种实现网络预订存储的***, 其特征在于, 包括管理服务器、 预订服务器、 存储服务器,
所述管理服务器, 用于将从网络中获得的共享用户信息发送至预订 服务器;
所述预订服务器, 用于接收来自下载用户的预订事件, 当所述预订 事件所对应的数据资源处于可下载状态时, 将获得的与所述数据资源相 对应的共享用户信息发送至存储服务器;
所述存储服务器,用于利用所述共享用户信息与共享用户建立连接, 下载所述数据资源。
2、 根据权利要求 1所述的实现网络预订存储的***, 其特征在于, 所述预订服务器包括: 接收单元、 判断单元和发送单元,
所述接收单元, 用于接收来自下载用户的预订事件;
所述判断单元, 用于当判定所述预订事件所对应的数据资源处于可 下载状态时, 通知所述发送单元;
所述发送单元, 用于将获得的与所述数据资源相对应的共享用户信 息发送至存储服务器。
3、 根据权利要求 1所述的实现网络预订存储的***, 其特征在于, 所述预订服务器, 用于接收来自下载用户的预订消息, 并将预订消 息中的预订事件发送至管理服务器;
所述管理服务器, 用于将网络中拥有与所述预订事件相应数据资源 的所述共享用户信息发送至预订服务器。
4、 根据权利要求 1所述的实现网络预订存储的***, 其特征在于, 所述预订服务器, 用于接收来自下载用户的预订消息, 并将预订消 息中的预订事件保存在预订数据库中, 收到来自管理服务器的所述共享 用户信息后, 利用所述共享用户信息判断所述共享用户拥有的所述数据 资源是否对应于所述预订数据库中的预订事件, 如果是, 将所述共享用 户信息发送至存储服务器;
所述存储服务器, 用于在将所述数据资源全部下载完成后, 通知所 述预订服务器删除所述预订事件。
5、 根据权利要求 1所述的实现网络预订存储的***, 其特征在于, 所述预订服务器, 进一步用于在接收到来自下载用户的预订消息后, 判 断预订消息中的预订事件所对应的数据资源是否在存储服务器中, 如果 在, 则将所述数据资源发送至下载用户。
6、 根据权利要求 1所述的实现网络预订存储的***, 其特征在于, 所述管理服务器, 进一步用于所述下载用户从所述共享用户下载所述数 据资源时中断后, 记录中断后所述下载用户的下载进度;
所述管理服务器, 用于在从网络中获得所述共享用户信息发送至预 订服务器的同时, 发送所述下载进度信息;
所述预订服务器, 进一步用于将获得的共享用户信息发送至存储服 务器的同时, 发送所述下载进度信息;
所述存储服务器, 用于在利用所述共享用户信息与共享用户建立连 接后, 利用所述进度信息下载所述数据资源中的剩余部分。
7、 一种实现网络预订存储的方法, 其特征在于, 该方法包括: 接收来自下载用户的预订事件;
当判定所述预订事件相对应的数据资源处于可下载状态时, 获得与 所述数据资源相对应的共享用户信息;
存储 务器利用所述共享用户信息与共享用户建立连接, 下载并存 储所述数据资源。
8、 根据权利要求 7所述的实现网络预订存储的方法, 其特征在于, 所述判定所述预订事件相对应的数据资源处于可下载状态包括:
判断网络中是否存在拥有所述数据资源相对应的共享用户, 如果存 在, 则处于可下载状态, 如果不存在, 则处于不可下载状态。
9、 根据权利要求 7所述的实现网络预订存储的方法, 其特征在于, 所述判定预订事件相对应的数据资源处于可下载状态包括:
利用共享用户的共享用户信息判断所述共享用户所拥有的数据资源 是否与所述接收到的预订事件相对应,如果相对应,则处于可下载状态, 如果不相对应, 则处于不可下载状态。
10、 根据权利要求 8或 9所述的实现网络预订存储的方法, 其特征 在于, 该方法进一步包括:
发送所述预订事件的下载用户从所述存储服务器下载所述数据资 源。
11、根据权利要求 7所述的实现网络预订存储的方法,其特征在于, 该方法进一步包括:
所述存储服务器下载并存储所述数据资源的过程中, 追踪并记录下 载进度信息。
12、根据权利要求 11所述的实现网络预订存储的方法,其特征在于, 所述存储服务器下载并存储所述数据资源的过程中,如果出现中断, 则当下一次判定所述预订事件相对应的数据资源处于可下载状态时, 再 次获得与所述数据资源相对应的共享用户信息;
存储服务器利用所述共享用户信息与共享用户建立连接, 并 利用所记录的下载进度信息, 对所述数据资源中未下载的部分进行 下载并存储, 直至将所述数据资源全部下载完成后, 将与所述数据资源 相对应的预订事件从预订服务器中删除。
13、 根据权利要求 8或 9所述的实现网络预订存储的方法, 其特征 在于, 在下载用户发起下载请求时, 该方法进一步包括:
判断存储服务器中是否保存有与该下载请求相对应的所述数据资 源, 如果是, 则直接从该存储服务器中下载对应的所述数据资源。
14、 一种预订服务器, 其特征在于, 该预订服务器与存储服务器连 接, 所述存储服务器利用该预订服务器提供的共享用户信息与共享用户 建立连接, 并下载数据资源;
该预订服务器包括接收单元、 判断单元和发送单元, 其中: 所述接收单元, 用于接收来自下载用户的预订事件;
所述判断单元, 用于当判定所述预订事件所对应的数据资源处于可 下载状态时, 通知所述发送单元;
所述发送单元, 用于将获得的与所述数据资源相对应的共享用户信 息发送至所述存储服务器。
PCT/CN2008/070167 2007-04-28 2008-01-23 Système et procédé pour la réalisation d'une mémoire d'abonnement à un réseau et serveur d'abonnement WO2008131653A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710097227.2 2007-04-28
CN 200710097227 CN100588172C (zh) 2007-04-28 2007-04-28 一种实现网络预订存储的***和方法

Publications (1)

Publication Number Publication Date
WO2008131653A1 true WO2008131653A1 (fr) 2008-11-06

Family

ID=38899162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070167 WO2008131653A1 (fr) 2007-04-28 2008-01-23 Système et procédé pour la réalisation d'une mémoire d'abonnement à un réseau et serveur d'abonnement

Country Status (2)

Country Link
CN (1) CN100588172C (zh)
WO (1) WO2008131653A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104753961A (zh) * 2015-04-22 2015-07-01 腾讯科技(北京)有限公司 一种多媒体数据的处理方法、客户端及服务器
CN115695434A (zh) * 2022-09-28 2023-02-03 聚好看科技股份有限公司 一种负载均衡方法、装置和电子设备

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100588172C (zh) * 2007-04-28 2010-02-03 腾讯科技(深圳)有限公司 一种实现网络预订存储的***和方法
CN101902346A (zh) 2009-05-31 2010-12-01 国际商业机器公司 P2p内容缓存***和方法
CN102118406B (zh) * 2009-12-31 2013-08-07 Tcl集团股份有限公司 一种终端设备离线下载方法及门户服务***
CN102148843A (zh) * 2010-02-05 2011-08-10 腾讯科技(深圳)有限公司 异步下载***及方法
US8898318B2 (en) * 2010-06-03 2014-11-25 Microsoft Corporation Distributed services authorization management
CN102209050B (zh) * 2011-05-24 2012-07-18 苏州阔地网络科技有限公司 一种用户信息共享的即时通讯***及方法
CN103269302A (zh) * 2012-12-07 2013-08-28 北京奇虎科技有限公司 用于即时通信的共享文件管理方法和***
CN103281234A (zh) * 2012-12-07 2013-09-04 北京奇虎科技有限公司 即时通信中的文件处理方法及***
CN103347041B (zh) * 2013-05-31 2016-04-13 中国联合网络通信集团有限公司 视频共享控制方法和装置
CN103546549B (zh) * 2013-10-12 2017-12-12 深圳Tcl新技术有限公司 终端离线数据共享的方法及***
CN108874445A (zh) * 2017-10-30 2018-11-23 上海寒武纪信息科技有限公司 神经网络处理器及使用处理器执行向量点积指令的方法
KR102147989B1 (ko) * 2017-11-30 2020-08-25 주식회사 카카오 예매 정보 및 티켓의 공유를 위한 방법 및 장치
CN109861955A (zh) * 2018-09-03 2019-06-07 西安新路网络科技有限公司 一种流量特征防私接方法
US11996105B2 (en) 2018-09-13 2024-05-28 Shanghai Cambricon Information Technology Co., Ltd. Information processing method and terminal device
CN117632660B (zh) * 2023-12-12 2024-05-28 北京衡石科技有限公司 应用检测方法、装置、电子设备和计算机可读介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1506877A (zh) * 2002-12-09 2004-06-23 宾得株式会社 下载***和下载设备
WO2006011758A1 (en) * 2004-07-29 2006-02-02 Widerthan Co., Ltd. Method for providing multimedia data via communication network and playing the multimedia data
CN1757033A (zh) * 2003-02-28 2006-04-05 皇家飞利浦电子股份有限公司 在网络中的用户站之间共享文件的方法
CN101072166A (zh) * 2007-04-28 2007-11-14 腾讯科技(深圳)有限公司 一种实现网络预订存储的***和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1506877A (zh) * 2002-12-09 2004-06-23 宾得株式会社 下载***和下载设备
CN1757033A (zh) * 2003-02-28 2006-04-05 皇家飞利浦电子股份有限公司 在网络中的用户站之间共享文件的方法
WO2006011758A1 (en) * 2004-07-29 2006-02-02 Widerthan Co., Ltd. Method for providing multimedia data via communication network and playing the multimedia data
CN101072166A (zh) * 2007-04-28 2007-11-14 腾讯科技(深圳)有限公司 一种实现网络预订存储的***和方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104753961A (zh) * 2015-04-22 2015-07-01 腾讯科技(北京)有限公司 一种多媒体数据的处理方法、客户端及服务器
CN115695434A (zh) * 2022-09-28 2023-02-03 聚好看科技股份有限公司 一种负载均衡方法、装置和电子设备

Also Published As

Publication number Publication date
CN101072166A (zh) 2007-11-14
CN100588172C (zh) 2010-02-03

Similar Documents

Publication Publication Date Title
WO2008131653A1 (fr) Système et procédé pour la réalisation d'une mémoire d'abonnement à un réseau et serveur d'abonnement
US7782866B1 (en) Virtual peer in a peer-to-peer network
US8554827B2 (en) Virtual peer for a content sharing system
US8195742B2 (en) Distributed client services based on execution of service attributes and data attributes by multiple nodes in resource groups
CN100438408C (zh) 一种实现代理下载的方法、装置及***
JP4938074B2 (ja) リソースの位置情報の要求方法、当該方法のためのユーザノードおよびサーバ
US20190207891A1 (en) Selective distribution of messages in a scalable, real-time messaging system
US20140229582A1 (en) System And Method For Offline Downloading Network Resource Files
EP2227016B1 (en) A content buffering, querying method and point-to-point media transmitting system
US7970856B2 (en) System and method for managing and distributing assets over a network
JP4473942B2 (ja) コンテンツ配信装置、コンテンツ配信方法、及びコンテンツ配信プログラム
JP2004246632A (ja) データ分配サーバ、プログラム及びネットワークシステム
US9218353B2 (en) Method and system for name space propagation and file caching to remote nodes in a storage system
KR101485610B1 (ko) 네트워크 구조를 고려한 분산형 컨텐트 전달 시스템 및 그 방법
US8086629B2 (en) Content delivery apparatus, content delivery method, and content delivery program
JP2004192170A (ja) アクセス中継装置
JP2010522386A (ja) P2pコンテンツ共有のための方法、システム、及びノード
JP2012504282A (ja) 選択的データ転送ストレージ
WO2021082401A1 (zh) 一种数据的上传方法、***、装置及电子设备
US9544371B1 (en) Method to discover multiple paths to disk devices cluster wide
KR101041092B1 (ko) 웹 폴더를 이용한 효과적인 피투피 시스템
WO2013047207A1 (ja) キャッシュシステム、キャッシュ方法、及びキャッシュサーバ
CN101662494A (zh) 一种实现内容提供的方法、***和装置
WO2023040504A1 (zh) 数据处理***、数据处理方法及相关装置
Wang et al. Rio: a personal storage system in multi-device and cloud

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: 08706546

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 6641/CHENP/2009

Country of ref document: IN

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 OF 080310

122 Ep: pct application non-entry in european phase

Ref document number: 08706546

Country of ref document: EP

Kind code of ref document: A1