File transfer methods and remote video-on-demand systems for personal servers

By combining file transfer methods from personal servers and cloud servers, the problems of unsmooth playback and high bandwidth costs in remote on-demand playback on NAS devices are solved, achieving a more efficient data request and playback experience.

CN116684658BActive Publication Date: 2026-11-10XUNLEI NETWORKING TECHNOLOGIES LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202310732118.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-06-19
Publication Date
2026-11-10
Estimated Expiration
2043-06-19

AI Technical Summary

Technical Problem

Traditional NAS devices' remote video-on-demand solutions suffer from issues like choppy playback and buffering, and the high bandwidth costs of relay servers negatively impact the real-time performance and stability of playback.

Method used

The file transfer method combines personal servers and cloud servers. The relay server first checks the cloud server cache. If the cache is found, it returns the playback link. If the cache is not found, it requests data from the personal server. When the memory exceeds the threshold, the data is uploaded to the cloud server cache. The personal server uploads hot data to the cloud server to improve the hit rate.

Benefits of technology

By reducing data request time, the real-time performance and stability of playback are improved, bandwidth costs are reduced, and the user playback experience is enhanced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116684658B_ABST
    Figure CN116684658B_ABST
Patent Text Reader

Abstract

This application discloses a file transfer method for a personal server, relating to the field of streaming media on-demand technology. The method includes receiving a file request from a client and querying the cache; if the file request matches the cache of a cloud server, a playback link from the cloud server is returned to the client, allowing the client to play the data corresponding to the file request cached in the cloud server according to the playback link; if the file request does not match the cache of the cloud server, the data corresponding to the file request is requested from the personal server and returned to the client. This method can improve the real-time performance and stability of playback. This application also discloses another file transfer method for a personal server and a remote on-demand system, both of which have the above-mentioned technical effects.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of streaming media on-demand technology, and in particular to a file transfer method for personal servers and a remote on-demand system. Background Technology

[0002] In the era of broadband networks, NAS (Network Attached Storage) devices are widely used, providing audio and video streaming services in many situations. Traditional remote streaming solutions for NAS devices involve a relay server on a wide area network downloading raw video data from the NAS device, and then the relay server returning the raw video data to the player for playback. However, playing raw video data is limited by the uplink bandwidth of the NAS device and the decoding capabilities of the player, resulting in issues such as choppy playback and frequent buffering. Furthermore, because the relay server needs to receive the raw video data returned by the NAS device in real time before pushing it to the player, when a large amount of data needs to be relayed, it leads to excessively high bandwidth costs and long data request times, affecting the real-time performance and stability of playback.

[0003] Therefore, how to improve the real-time performance and stability of playback has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] The purpose of this application is to provide a file transfer method for a personal server that improves the real-time performance and stability of playback. Another purpose of this application is to provide another file transfer method for a personal server and a remote on-demand system, both of which achieve the aforementioned technical effects.

[0005] To address the aforementioned technical problems, this application provides a file transfer method for a personal server, applied to a relay server, comprising:

[0006] Receive file requests from clients and query the cache;

[0007] If the file request hits the cloud server's cache, the cloud server's playback link is returned to the client, so that the client can play the data corresponding to the file request cached in the cloud server according to the playback link;

[0008] If the file request does not hit the cloud server's cache, the data corresponding to the file request is requested from the personal server and returned to the client.

[0009] Optional, also includes:

[0010] When the amount of data in the memory of the relay server exceeds a preset threshold, the excess data is uploaded to the cloud server so that when the excess data needs to be loaded, it can be downloaded from the cloud server to the memory of the relay server.

[0011] Optionally, the data cached by the cloud server is the hot data uploaded by the personal server.

[0012] Optionally, when the popularity of the hot data cached by the cloud server drops to a preset value, the cloud server deletes the hot data whose popularity has dropped to the preset value.

[0013] To address the aforementioned technical problems, this application also provides a file transfer method for a personal server, applied to a cloud server, comprising:

[0014] Receive and cache data uploaded from personal servers;

[0015] When a client accesses the cloud server based on the playback link of the cloud server, the data corresponding to the file request of the client is returned to the client; the playback link is returned to the client by the relay server when the file request hits the cache of the cloud server; when the file request does not hit the cache of the cloud server, the relay server requests the data corresponding to the file request from the personal server and returns the data corresponding to the file request to the client.

[0016] Optionally, receiving and caching the data uploaded by the personal server includes:

[0017] Receive and cache the hot data uploaded by the personal server.

[0018] Optional, also includes:

[0019] Analyze the popularity of the cached hot data and delete the hot data whose popularity drops to a preset value.

[0020] Optional, also includes:

[0021] The system receives and caches excess data uploaded when the amount of data in the relay server's memory exceeds a preset threshold.

[0022] To address the aforementioned technical problems, this application also provides a video-on-demand system, comprising:

[0023] Relay servers, cloud servers, and personal servers;

[0024] The personal server is used to upload data to the cloud server and return data to the relay server when it receives a request from the relay server.

[0025] The cloud server is used to receive and cache the data uploaded by the personal server;

[0026] The relay server is used to receive file requests from clients and query the cache; if the file request matches the cache of the cloud server, it returns a playback link of the cloud server to the client so that the client can play the data corresponding to the file request cached by the cloud server according to the playback link; if the file request does not match the cache of the cloud server, it requests the data corresponding to the file request from the personal server and returns the data corresponding to the file request to the client.

[0027] Optionally, the personal server is specifically used to: upload hot data to the cloud server.

[0028] Optionally, the cloud server is also used for:

[0029] Analyze the popularity of the cached hot data and delete the hot data whose popularity drops to a preset value.

[0030] Optionally, the relay server is also used for:

[0031] When the amount of data in the memory of the relay server exceeds a preset threshold, the excess data is uploaded to the cloud server so that when the excess data needs to be loaded, it can be downloaded from the cloud server to the memory of the relay server.

[0032] The file transfer method for a personal server applied to a relay server provided in this application includes: receiving a file request from a client and querying the cache; if the file request hits the cache of a cloud server, returning a playback link of the cloud server to the client so that the client can play the data corresponding to the file request cached in the cloud server according to the playback link; if the file request does not hit the cache of the cloud server, requesting the data corresponding to the file request from the personal server and returning the data corresponding to the file request to the client.

[0033] As can be seen, the file transfer method for personal servers applied to relay servers provided in this application combines private cloud (i.e., personal server) and public cloud (i.e., cloud server). The cloud server caches some data in advance. When the client requests data, for requests that hit the cloud server, the data can be quickly obtained from the cloud server without waiting for the personal server to upload the data to the relay server. This can effectively shorten the data request time and improve the real-time performance and stability of playback.

[0034] The file transfer method for personal servers applied to cloud servers and the remote on-demand system provided in this application both have the aforementioned technical effects. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the prior art and embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 A schematic flowchart illustrating a file transfer method for a personal server provided in an embodiment of this application;

[0037] Figure 2 A schematic diagram illustrating another file transfer method for a personal server provided in an embodiment of this application;

[0038] Figure 3 This is a schematic diagram of a remote on-demand system provided in an embodiment of this application. Detailed Implementation

[0039] The core of this application is to provide a file transfer method for a personal server that improves the real-time performance and stability of playback. Another core aspect of this application is to provide another file transfer method for a personal server and a remote on-demand system, both of which achieve the aforementioned technical effects.

[0040] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0041] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a file transfer method for a personal server provided in an embodiment of this application. (Refer to...) Figure 1 As shown, this method is applied to a relay server and includes:

[0042] S101: Receive file requests from clients and query the cache;

[0043] S102: If the file request hits the cloud server's cache, then the cloud server's playback link is returned to the client so that the client can play the data corresponding to the file request cached in the cloud server according to the playback link;

[0044] When a client requests playback data, it uploads a file request to the relay server. The file request can carry a GCID. A GCID is a globally unique identifier for a file, used to indicate its uniqueness. The GCID of the original file can be generated by a personal server.

[0045] The relay server receives file requests from clients and checks its cache based on the GCID carried in the request. If the client's file request matches the cloud server's cache (i.e., the cloud server has the requested data cached), the relay server directly returns a playback link from the cloud server to the client. The client then plays the requested data using this playback link.

[0046] Data cached on the cloud server is uploaded to the cloud server by the personal server. The personal server can upload data to the cloud server when it is idle; alternatively, it can upload data to the cloud server when a client's file request misses the cloud server's cache. Specifically, during the resource indexing phase, the personal server periodically monitors for changes to disk files. When the personal server detects a change, it adds the file to the upload queue, waiting to upload it to the cloud server when the personal server is idle. If a file is not cached on the cloud server but a playback request for that file is received beforehand, the personal server uploads that file to the cloud server.

[0047] S103: If the file request does not hit the cache of the cloud server, then request the data corresponding to the file request from the personal server and return the data corresponding to the file request to the client.

[0048] If the client's file request does not hit the cloud server, meaning the cloud server does not cache the data requested by the client, the relay server requests the data requested by the client from the personal server and returns the data returned by the personal server to the client for playback.

[0049] The process by which a relay server requests data from a personal server and then returns the data from the personal server to the client can be described as follows:

[0050] When a client's file request misses the cloud server's cache, the relay server holds the file request and simultaneously starts multiple threads to notify the individual server to upload the original file requested by the client. The relay server slices the original file and uploads the switching data to the relay server.

[0051] The relay server can use the MQTT (Message Queuing Telemetry Transport) protocol to notify the personal server to upload the original file requested by the client.

[0052] Additionally, personal servers can upload slice data of the original file to a relay server via the WS protocol. WS stands for Web Socket, a full-duplex network communication protocol built on a single TCP (Transmission Control Protocol) connection.

[0053] The relay server receives the sliced ​​data uploaded by the individual server and stores it in allocated memory. Simultaneously, the relay server sends a notification to the HTTP sending thread, informing it of the data update. The HTTP sending thread then retrieves the sliced ​​data from memory and replies to the client via HTTP Chunk. HTTP Chunk, or Chunked Transfer Encoding, is a data transmission mechanism in the Hypertext Transfer Protocol (HTTP) that allows data sent from the application server to the client application via HTTP to be divided into multiple parts, better supporting dynamic content formats.

[0054] Based on the above embodiments, as a specific implementation method, it further includes:

[0055] When the amount of data in the memory of the relay server exceeds a preset threshold, the excess data is uploaded to the cloud server so that when the excess data needs to be loaded, it can be downloaded from the cloud server to the memory of the relay server.

[0056] The client's network environment is complex, and transmission reliability cannot be guaranteed. Furthermore, when the client has sufficient buffered data, it will pause data download. This can cause the segmented data in the relay server's memory to be delayed in pushing to the client. When the relay server cannot push the segmented data in memory to the client in a timely manner, if the amount of data in the relay server's memory exceeds a preset threshold, the relay server can index the excess segmented data (the portion exceeding the preset threshold) according to the segmented data ID and upload it to the cloud server for caching. When the client needs to play these cached segmented data on the cloud server, the relay server directly downloads the previously uploaded excess segmented data from the cloud server into memory and pushes it to the client.

[0057] The relay server uploads excess data to the cloud server. Leveraging the cloud server's data caching capabilities, personal servers can continuously upload data to the relay server, which then caches it on the cloud server. When the client needs to play excess data, it can quickly retrieve it from the cloud server, significantly accelerating playback and improving the user experience.

[0058] In order to increase the probability of hitting the cloud server cache, reduce data request time, and improve playback real-time performance, in some embodiments, the data cached by the cloud server is hot data uploaded by the personal server.

[0059] Specifically, a personal server can analyze the access frequency of the original files and select the most frequently accessed data, i.e., "hot data," to upload to the cloud server. Since the cloud server caches hot data, the probability of a client's file request hitting the cloud server's cache is greatly increased, thereby reducing data request time and improving real-time playback performance.

[0060] To save on cloud server storage costs, in some embodiments, when the popularity of cached hot data on the cloud server drops to a preset value, the cloud server deletes the hot data whose popularity has dropped to the preset value. After deleting the hot data whose popularity has dropped to the preset value, the cloud server updates the data index.

[0061] For example, if the popularity of some hot data cached by the cloud server drops to 0, the cloud server will delete this hot data and update the data index after deleting it.

[0062] In summary, the file transfer method for personal servers applied to relay servers provided in this application combines private cloud (i.e., personal server) and public cloud (i.e., cloud server). The cloud server caches some data in advance. When a client requests data, for requests that hit the cloud server, the data can be quickly obtained from the cloud server without waiting for the personal server to upload the data to the relay server. This can effectively shorten the data request time and improve the real-time performance and stability of playback.

[0063] Please refer to Figure 2 , Figure 2 This is a schematic flowchart illustrating another file transfer method for a personal server provided in an embodiment of this application. (Refer to...) Figure 2 As shown, this method is applied to a cloud server and includes:

[0064] S201: Receive and cache data uploaded by the personal server;

[0065] S202: When a client accesses the cloud server based on the playback link of the cloud server, the data corresponding to the file request of the client is returned to the client; the playback link is returned to the client by the relay server when the file request hits the cache of the cloud server; when the file request does not hit the cache of the cloud server, the relay server requests the data corresponding to the file request from the personal server and returns the data corresponding to the file request to the client.

[0066] Personal servers can upload data to the cloud server when idle; alternatively, they can upload data to the cloud server when a client's file request misses the cloud server's cache. The cloud server receives and caches the data uploaded by the personal server. When a client requests playback data, it uploads a file request to a relay server. The relay server receives the client's file request and checks its cache based on the request. If the client's file request hits the cloud server's cache, the relay server directly returns the cloud server's playback link to the client. The client accesses the cloud server using the playback link and plays the data corresponding to the file request. If the client's file request misses the cloud server's cache, the relay server requests the requested data from the personal server and returns the data from the personal server to the client for playback.

[0067] In order to increase the probability of hitting the cloud server cache, reduce data request time, and improve playback real-time performance, in some embodiments, receiving and caching the data uploaded by the personal server includes receiving and caching the hot data uploaded by the personal server.

[0068] Specifically, a personal server can analyze the access frequency of the original files and select the most frequently accessed data, i.e., "hot data," to upload to the cloud server. Since the cloud server caches hot data, the probability of a client's file request hitting the cloud server's cache is greatly increased, thereby reducing data request time and improving real-time playback performance.

[0069] In addition, to save on cloud server storage costs, some embodiments also include:

[0070] The system analyzes the popularity of the cached hot data and deletes any hot data whose popularity drops below a preset value. After deleting the hot data whose popularity drops below the preset value, the cloud server updates the data index.

[0071] For example, if the popularity of some hot data cached by the cloud server drops to 0, the cloud server will delete this hot data and update the data index after deleting it.

[0072] Furthermore, in some embodiments, it also includes:

[0073] The system receives and caches excess data uploaded when the amount of data in the relay server's memory exceeds a preset threshold.

[0074] Specifically, if the amount of data in the relay server's memory exceeds a preset threshold, the relay server can index the excess slice data (the portion exceeding the preset threshold) according to the slice data ID and upload the slice data to the cloud server for caching. When the client needs to play these cached slice data on the cloud server, the relay server directly downloads the previously uploaded excess slice data from the cloud server into its memory and pushes it to the client.

[0075] The relay server uploads excess data to the cloud server. Leveraging the cloud server's data caching capabilities, personal servers can continuously upload data to the relay server, which then caches it on the cloud server. When the client needs to play excess data, it can quickly retrieve it from the cloud server, significantly accelerating playback and improving the user experience.

[0076] The file transfer method for personal servers applied to cloud servers provided in this application combines private cloud (i.e., personal server) and public cloud (i.e., cloud server). The cloud server caches some data in advance. When the client requests data, for requests that hit the cloud server, the data can be quickly obtained from the cloud server without waiting for the personal server to upload the data to the relay server. This can effectively shorten the data request time and improve the real-time performance and stability of playback.

[0077] Please refer to Figure 3 , Figure 3 This is a schematic diagram of a remote video-on-demand system provided in an embodiment of this application, with reference to... Figure 3 As shown, the system includes:

[0078] Relay servers, cloud servers, and personal servers;

[0079] The personal server is used to upload data to the cloud server and return data to the relay server when it receives a request from the relay server.

[0080] The cloud server is used to receive and cache the data uploaded by the personal server;

[0081] The relay server is used to receive file requests from clients and query the cache; if the file request matches the cache of the cloud server, it returns a playback link of the cloud server to the client so that the client can play the data corresponding to the file request cached by the cloud server according to the playback link; if the file request does not match the cache of the cloud server, it requests the data corresponding to the file request from the personal server and returns the data corresponding to the file request to the client.

[0082] When a client requests playback data, it uploads a file request to the relay server. The relay server receives the client's file request and checks its cache based on it. If the client's file request matches the cloud server's cache, the relay server directly returns a playback link from the cloud server to the client. The client then uses this playback link to access the requested data on the cloud server.

[0083] If the client's file request misses the cloud server, the relay server requests the data requested by the client from the personal server and then returns the data from the personal server to the client for playback.

[0084] Personal servers can upload data to the cloud server when they are idle; or, they can upload data to the cloud server when a client's file request fails to hit the cloud server's cache.

[0085] In addition, the process of the relay server requesting the data requested by the client from the personal server and returning the data returned by the personal server to the client can be as follows:

[0086] When a client's file request misses the cloud server's cache, the relay server holds the file request and simultaneously starts multiple threads to notify the individual server to upload the original file requested by the client. The relay server slices the original file and uploads the switching data to the relay server.

[0087] The relay server receives the slice data uploaded by the individual server and stores it in allocated memory. Simultaneously, the relay server sends a notification to the HTTP sending thread, informing it of the data update. The HTTP sending thread then retrieves the slice data from memory and replies to the client via an HTTP Chunk.

[0088] In order to increase the probability of hitting the cloud server cache, reduce data request time, and improve playback real-time performance, in some embodiments, the personal server is specifically used to: upload hot data to the cloud server.

[0089] Personal servers can analyze the access frequency of original files and select the most frequently accessed data, i.e., "hot data," to upload to the cloud server. Since the cloud server caches hot data, the probability of client file requests hitting the cloud server's cache is greatly increased, thereby reducing data request time and improving real-time playback performance.

[0090] To save on cloud server storage costs, in some embodiments, the cloud server is also used for:

[0091] Analyze the popularity of the cached hot data and delete the hot data whose popularity drops to a preset value.

[0092] When the popularity of the hot data cached by the cloud server drops to a preset value, the cloud server deletes the hot data whose popularity has dropped to the preset value, and updates the data index after deleting the hot data whose popularity has dropped to the preset value.

[0093] To speed up playback and improve the user experience, in some embodiments, the relay server is also used for:

[0094] When the amount of data in the memory of the relay server exceeds a preset threshold, the excess data is uploaded to the cloud server so that when the excess data needs to be loaded, it can be downloaded from the cloud server to the memory of the relay server.

[0095] When the relay server is unable to push the segment data in memory to the client in a timely manner, if the amount of data in the relay server's memory exceeds a preset threshold, the relay server can index the excess segment data (the portion exceeding the preset threshold) according to the segment data ID and upload the segment data to the cloud server for caching. When the client needs to play these cached segment data on the cloud server, the relay server directly downloads the previously uploaded excess segment data from the cloud server into memory and pushes it to the client.

[0096] The relay server uploads excess data to the cloud server. Leveraging the cloud server's data caching capabilities, personal servers can continuously upload data to the relay server, which then caches it on the cloud server. When the client needs to play excess data, it can quickly retrieve it from the cloud server, significantly accelerating playback and improving the user experience.

[0097] The remote video-on-demand system provided in this application combines a private cloud (i.e., a personal server) with a public cloud (i.e., a cloud server). The cloud server caches some data in advance. When a client requests data, the data can be quickly obtained from the cloud server for requests that hit the cloud server, without having to wait for the personal server to upload the data to the relay server. This can effectively shorten the data request time and improve the real-time performance and stability of playback.

[0098] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the remote video-on-demand system disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0099] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0100] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0101] The file transfer method and remote on-demand system for personal servers provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A file transfer method for a personal server, characterized in that, Applications to relay servers include: Receive file requests from clients and query the cache; If the file request hits the cloud server's cache, a playback link from the cloud server is returned to the client, so that the client can play the data corresponding to the file request cached in the cloud server according to the playback link; the data cached in the cloud server is uploaded to the cloud server from the personal server; If the file request does not hit the cache of the cloud server, the data corresponding to the file request is requested from the personal server and returned to the client. The relay server requests the data requested by the client from the personal server and returns the data returned by the personal server to the client. This process includes: the relay server holding the client's file request, starting multiple threads, and notifying the personal server to upload the original file requested by the client; the relay server receiving the slice data obtained from slicing the original file uploaded by the personal server and storing it in memory; and the relay server retrieving the slice data from memory and replying the slice data to the client.

2. The file transfer method for a personal server according to claim 1, characterized in that, Also includes: When the amount of data in the memory of the relay server exceeds a preset threshold, the excess data is uploaded to the cloud server so that when the excess data needs to be loaded, it can be downloaded from the cloud server to the memory of the relay server.

3. The file transfer method for a personal server according to claim 1, characterized in that, The data cached on the cloud server is the hot data uploaded by the personal server.

4. The file transfer method for a personal server according to claim 3, characterized in that, When the popularity of the hot data cached by the cloud server drops to a preset value, the cloud server deletes the hot data whose popularity has dropped to the preset value.

5. A file transfer method for a personal server, characterized in that, Applied to cloud servers, including: Receive and cache data uploaded from personal servers; When a client accesses the cloud server based on the playback link of the cloud server, the data corresponding to the file request of the client is returned to the client; the playback link is returned to the client by the relay server when the file request hits the cache of the cloud server; when the file request does not hit the cache of the cloud server, the relay server requests the data corresponding to the file request from the personal server and returns the data corresponding to the file request to the client. The relay server requests the data requested by the client from the personal server and returns the data returned by the personal server to the client. This process includes: the relay server holding the client's file request, starting multiple threads, and notifying the personal server to upload the original file requested by the client; the relay server receiving the slice data obtained from slicing the original file uploaded by the personal server and storing it in memory; and the relay server retrieving the slice data from memory and replying the slice data to the client.

6. The file transfer method for a personal server according to claim 5, characterized in that, The data received and cached from the personal server includes: Receive and cache the hot data uploaded by the personal server.

7. The file transfer method for a personal server according to claim 6, characterized in that, Also includes: Analyze the popularity of the cached hot data and delete the hot data whose popularity drops to a preset value.

8. The file transfer method for a personal server according to claim 5, characterized in that, Also includes: The cached relay server receives excess data uploaded when the amount of data in the relay server's memory exceeds a preset threshold.

9. A remote on-demand system, characterized in that, include: Relay servers, cloud servers, and personal servers; The personal server is used to upload data to the cloud server and to return data to the relay server when it receives a request from the relay server. The cloud server is used to receive and cache the data uploaded by the personal server; The relay server is used to receive file requests from clients and query the cache; If the file request hits the cloud server's cache, the cloud server's playback link is returned to the client so that the client can play the data corresponding to the file request cached by the cloud server according to the playback link; if the file request does not hit the cloud server's cache, the data corresponding to the file request is requested from the personal server and the data corresponding to the file request is returned to the client. The relay server requests the data requested by the client from the personal server and returns the data returned by the personal server to the client. This includes the relay server keeping track of the client's file request, starting multiple threads, and notifying the personal server to upload the original file requested by the client. The relay server receives the slice data obtained from slicing the original file uploaded by the personal server and stores it in memory; the relay server retrieves the slice data from memory and replies with the slice data to the client.

10. The remote on-demand system according to claim 9, characterized in that, The personal server is specifically used to upload hot data to the cloud server.

11. The remote on-demand system according to claim 10, characterized in that, The cloud server is also used for: Analyze the popularity of the cached hot data and delete the hot data whose popularity drops to a preset value.

12. The remote on-demand system according to claim 9, characterized in that, The relay server is also used for: When the amount of data in the memory of the relay server exceeds a preset threshold, the excess data is uploaded to the cloud server so that when the excess data needs to be loaded, it can be downloaded from the cloud server to the memory of the relay server.

Citation Information

Patent Citations

  • Online VOD (video on demand) acceleration system and online VOD playing method

    CN103024593A

  • Online video playing method and device

    CN103945259A

  • Method for acquiring video

    CN113038033A