CN111355798A - Data distribution method and system - Google Patents

Data distribution method and system Download PDF

Info

Publication number
CN111355798A
CN111355798A CN202010124510.5A CN202010124510A CN111355798A CN 111355798 A CN111355798 A CN 111355798A CN 202010124510 A CN202010124510 A CN 202010124510A CN 111355798 A CN111355798 A CN 111355798A
Authority
CN
China
Prior art keywords
resource
pcdn
user
request
server
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202010124510.5A
Other languages
Chinese (zh)
Inventor
张克东
李俊龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dianji Network Technology Shanghai Co ltd
Original Assignee
Dianji Network Technology Shanghai Co ltd
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 Dianji Network Technology Shanghai Co ltd filed Critical Dianji Network Technology Shanghai Co ltd
Priority to CN202010124510.5A priority Critical patent/CN111355798A/en
Publication of CN111355798A publication Critical patent/CN111355798A/en
Pending legal-status Critical Current

Links

Images

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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application discloses a data distribution method and a system, wherein the PCDN system is formed by the existing household internet equipment, and the content distribution with low cost and high quality is carried out on the client media data through the P2P technology, thereby solving the problems of high cost, poor expansibility and defects in the adaptability and fault tolerance to burst flow when large-scale service is provided in the prior art. The data distribution method disclosed by the application comprises the following steps: a user sends a resource request to a scheduling server; the scheduling server sends resource request feedback information to the user according to the resource request; and if the request feedback information is a request success, the user downloads the resource from the PCDN. The application also discloses a data distribution system.

Description

Data distribution method and system
Technical Field
The present application relates to the field of network technologies, and in particular, to a data distribution method and system.
Background
With the development of the technology, the definition and the fluency of the video service are continuously improved, and with the arrival of 5G, the demand of the user on high-quality video is more and more vigorous, the high-definition video becomes the mainstream at present, the resolution and the definition are improved, and although the watching experience of the user is improved, the flow use is also sharply increased.
A video distribution mode popular in the industry at present is shown in fig. 1, resources such as video/audio/pictures are deployed on a Content Distribution Network (CDN), and when a user needs to download the resources, the user directly initiates a resource request to the CDN to realize downloading, live broadcasting, and on-demand. Users can also request resources from other users, and the resource sharing is realized through the Peer-to-Peer (P2P) technology. However, the existing method needs to provide large-scale service, which has high cost and poor expansibility, and still has certain defects in the aspects of adaptability to burst traffic, fault tolerance and the like in peak periods. Although the P2P technology can save bandwidth to some extent, due to the instability of the client, the availability and performance of the service are difficult to guarantee, and the data distribution efficiency is affected. For example, the user terminals such as mobile phones and tablets have limited storage capacity, cannot be controlled to be turned on and turned off, and often change geographic positions, which results in low data sharing efficiency.
Disclosure of Invention
The embodiment of the application provides a data distribution method and a data distribution device, which are used for distributing low-cost and high-quality content to client media data through a P2P technology by forming a PCDN (personal digital network) system by using existing household internet access equipment, and solving the problems of high cost, poor expansibility and defects in adaptability and fault tolerance to burst flow when large-scale service is provided in the prior art.
In a first aspect, an embodiment of the present invention provides a data distribution method, including:
a user sends a resource request to a scheduling server;
the scheduling server sends resource request feedback information to the user according to the resource request;
if the request feedback information is a request success, the user downloads the resource from a Peer-to-Peer data distribution Network (PCDN);
the PCDN is a home internet device and comprises an optical modem, a home router or an Over The Top device (OTT device) which runs at The edge of The internet; the feedback information includes address information of the PCDN owning the resource.
Further, in the above-mentioned case,
the PCDN, prior to providing data sharing to the user, further comprises:
the dispatching server sends a resource downloading indication message to the PCDN;
the PCDN sends a resource request message to a Content Delivery Network (CDN) according to the download indication message;
the CDN sends a resource request success message to the PCDN;
and the PCDN downloads the resources from the CDN and sends a download completion message to the scheduling server after the download is completed.
Further, in order to maintain the link between the PCDN and the scheduling server, after the PCDN is started, the PCDN needs to log in to the scheduling server and maintain the heartbeat message, which specifically includes:
after the PCDN is started, a login request is sent to the scheduling server;
the dispatching server records the PCDN relevant information according to the login request and sends a login success message to the PCDN;
after receiving the login success message, the PCDN starts a heartbeat timer;
when the heartbeat timer is overtime, sending a heartbeat message to the scheduling server;
the heartbeat timer is used for sending a heartbeat message to the scheduling server by the PCDN every T time and maintaining the link with the scheduling server.
Preferably, if the scheduling server does not receive the heartbeat message of the PCDN of the scheduling server within N consecutive times T, the scheduling server determines that the PCDN is linked down, where N is an integer greater than or equal to 2.
Further, when the user fails to request resources from the scheduling server, the data is obtained in one of the following three ways:
the first method is as follows: the user acquires the resource from the CDN;
the second method comprises the following steps: the user sends a resource request to a resource list server; the resource list server sends a request success message to the user; the user downloads the resources from other users according to the request success message; wherein the request success message includes address information indicating a user who owns the resource;
the third method comprises the following steps: and if the user fails to request the resources from the resource list server, the user directly acquires the resources from the CDN.
Furthermore, the scheduling server counts M resources with the largest number of requests within time T2, and sends a resource downloading indication message to the PCDN to indicate the PCDN to download the M resources, wherein T2 is preset, and M is an integer greater than or equal to 1.
Preferably, when the storage space of the PCDN is full, replacing data by the following method, and if the storage space of the PCDN is full, instructing the PCDN to download a hot resource mR to replace a cold resource mL; wherein the number of requests of the hot resource mR in time T2 is greater than the number of requests of a cold resource mL in time T2, the cold resource mL having been stored in the PCDN and the hot resource mR not having been stored.
In a second aspect, an embodiment of the present invention further provides a data distribution system, including: a Content Delivery Network (CDN) for deploying resources to be delivered;
a PCDN (Peer to Peer Content Delivery Network, PCDN) node for downloading and caching specified media data from the CDN;
the dispatching server is used for receiving a resource request of a user and returning to a PCDN node with resources;
a Peer-to-Peer (P2P) penetration server, configured to assist P2P penetration between the PCDN node and a user node to implement Network Address Translation (NAT);
a user node;
data information is transmitted between the CDN and the user node and between the CDN and the PCDN node;
data information is transmitted between the PCDN and the user node;
the PCDN is transmitted with the dispatching server and the P2P penetration server by control information;
control information is transmitted between the user node and the scheduling server and the P2P penetration server;
the PCDN is a home internet device and comprises an optical modem running at The edge of The internet, a home router or an Over The Top device (OTT device).
The data distribution system disclosed by the application and the data distribution method disclosed by the application belong to the same invention concept, solve the same technical problems and realize the same technical effects.
In the embodiment of the invention, the PCDN system is formed by the existing household internet equipment, and the content distribution with low cost and high quality is carried out on the client media data by the P2P technology, thereby solving the problems of high cost, poor expansibility and defects in the adaptability and fault tolerance to burst flow when large-scale service is provided in the prior art.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a prior art data distribution architecture;
FIG. 2 is a schematic diagram of a data distribution structure provided in an embodiment of the present application;
fig. 3 is a schematic diagram illustrating an interaction flow between the PCDN and the scheduling server after the PCDN is powered on according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a process of downloading data from a CDN by a PCDN according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a process for a user to obtain data from a PCDN according to an embodiment of the present application;
fig. 6 is a schematic flowchart illustrating a failure of a user to acquire data from a PCDN according to an embodiment of the present application;
fig. 7 is a schematic flowchart of a process in which a user acquires data from another user according to an embodiment of the present application;
fig. 8 is a schematic flowchart illustrating a failure of a user to acquire data from another user according to an embodiment of the present application;
fig. 9 is a schematic diagram of another data distribution structure provided in the embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Some of the words that appear in the text are explained below:
1. the term "and/or" in the embodiments of the present invention describes an association relationship of associated objects, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
2. In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application provides a data distribution method and a data distribution system, which are used for solving the problems of high cost, poor expansibility and low sharing efficiency of providing large-scale services in the existing scheme.
The method and the system are based on the same application concept, and because the principles of solving the problems of the method and the system are similar, the implementation of the system and the method can be mutually referred, and repeated parts are not repeated.
It should be noted that the display sequence of the embodiment of the present application only represents the sequence of the embodiment, and does not represent the merits of the technical solutions provided by the embodiments.
As shown in fig. 1, which is a schematic structural diagram of a data distribution system in the prior art, resources such as video/audio/pictures are deployed on a Content Delivery Network (CDN) 101, and a user node 102 directly requests data from the CDN or requests data from other users. Although the existing CDN technology can accelerate media data transmission to a certain extent and realize downloading, live broadcasting and on-demand, the core of the existing CDN technology is still a structure based on a centralized server and is tightly connected with a regional control, so that the cost of providing large-scale services is high, the extensibility is poor, and in addition, certain defects still exist in the aspects of adaptability, fault tolerance and the like to burst traffic at peak periods. The user node 101 may also request data from other user nodes 103 to reduce the pressure of the CDN in sudden traffic, but because the user node is unstable, for example, a mobile phone, a tablet, and other user terminals have limited storage capacity, the on-off time cannot be controlled, and the geographic location changes frequently, availability and performance are difficult to guarantee, and thus the data sharing efficiency is low.
With the improvement of storage and calculation capabilities of internet terminal home devices (routers, television boxes, smart televisions and the like) and the popularization of household bandwidth of hundreds of megabytes and gigabytes, the home edge internet devices are high in performance and large in quantity, and the problems in the prior art can be well solved by utilizing the home edge internet devices for data distribution. These terminal devices are also advantageous in terms of cost because they do not have the cost of land and operators, etc. The invention utilizes P2P technology, and forms the existing home Network equipment into a point-to-Point Content Distribution Network (PCDN) system, and distributes the Content of the client media data with low cost and high quality, thereby solving the problems of high cost, poor expansibility and defects in the adaptability and fault tolerance of burst flow when providing large-scale service in the prior art.
Referring to fig. 2, a schematic structural diagram of a data distribution system provided for the embodiment of the present application includes a content distribution network 201, a user node 202, a PCDN node 203, a scheduling server 204, and a P2P penetration server 205.
The Content Delivery Network 201 is a Content Delivery Network, abbreviated as CDN, and is used to deploy resources to be shared by video/audio/pictures. The CDN may be a virtual network built on top of an existing network;
the PCDN node 203 is composed of optical modems, home routers or OTTs and other devices which operate at the edge of the Internet. Optionally, the device runs a dedicated software, and is deployed and issued by a network operator. The PCDN node is scheduled by the scheduling server 204, downloads and caches specified media data from a CDN source by using a limited storage space, and provides the specified media data for the user node through a P2P technology according to the request of a user;
the scheduling server 204 is responsible for receiving the resource request of the user node and returning PCDN node information with resources;
the P2P penetration server is used for assisting P2P penetration between the PCDN node and the user node to realize Network Address Translation (NAT).
On the basis of the above system description, a data distribution method provided by the embodiment of the present application is given below.
Example one
As shown in fig. 5, a data distribution method provided by the present application includes:
s501, a user sends a resource request to a scheduling server;
and when the user node has a resource downloading requirement, sending a resource request message to the scheduling server. In order to enable the scheduling server to correctly return the PCDN node information having the resource to be downloaded, the request message may include unique identification information of the requested resource. As a preferred embodiment, the resource may be represented in file segments, i.e. which piece of data of which file is requested. To be globally unique, as a preferred embodiment, a file segment is represented by a hash value of a Uniform Resource Locator (URL). The file segment is a basic unit scheduled by the PCDN, refers to a continuous fragment of a certain resource file, and is represented by a starting interval and an ending interval of the segment, for example, [0,4] represents a fragment of a certain file from the 0 th slice to the 4 th slice with the length of 5 slices.
Preferably, the resource request message may further include a user IP address, so as to schedule the server to return the resource information.
Further, as a preferred example, the request message may further include indication information indicating the urgency of the resource.
S502, the scheduling server sends resource request feedback information to the user according to the resource request;
after receiving the resource request message of the user node, the scheduling server analyzes the requested resource identifier from the request message, searches the resource in all PCDNs, and feeds back the information of the PCDN node to the user node when searching the corresponding resource.
Preferably, the scheduling server may take geographical location information into account when searching for resources. And if the distance between the geographical position of the PCDN and the geographical position of the user node is within a preset range, the address information of the PCDN is included in the feedback information.
Preferably, when there are a plurality of PCDNs (i.e., 2 or more) that satisfy the above-described geographical location condition, the scheduling server may feed back the PCDN address information with the shortest distance to the user node. As another preferred example, the scheduling server may also feed back all the address information of the first S PCDNs closest to the user node, and the user node may decide which PCDN to acquire data from.
The distance is within a predetermined range, and the predetermined range is set in advance. As a preferred example, the PCDN system is deployed in provinces, and the predetermined range does not exceed the boundary of system deployment.
Preferably, when searching for the PCDN node, the scheduling server may also consider the stability of the uplink bandwidth, and may also consider ISP connectivity, and preferably select a PCDN node with stable uplink bandwidth, short distance, and good ISP connectivity to send data to the user node.
Further, when the scheduling server searches the PCDN meeting the condition, the request is indicated to be successful in the feedback information, otherwise, the request is indicated to be failed.
S503, if the request feedback information is a request success, the user sends a request message for assisting P2P transparent transmission to a Peer-to-Peer (P2P) penetrating server;
the request message is used for requesting the P2P penetration server to assist the P2P penetration between the PCDN node and the user to implement Network Address Translation (NAT).
S504, the user node downloads the resource from a Peer-to-Peer Content Delivery Network (PCDN).
After receiving the feedback message of successful request fed back by the scheduling server, the user node analyzes the information related to the PCDN from the feedback message, and then can download the required resources from the PCDN node.
Preferably, the request and the reception of the resource by the user node can be realized by an sdk (software development kit) of the PCDN, and the user node is implanted into software by a terminal software manufacturer to realize the acquisition of data from the PCDN system.
Preferably, the external service of the PCDN system is provided in the form of an SDK, the SDK provides the service by using a loopback address, the client requests the SDK for media data, and the SDK obtains the data from the CDN, the PCDN, and other client SDKs.
Further, The PCDN is composed of home internet devices, including optical modems running at The edge of The internet, home routers, or Over The Top devices (OTT devices). The devices have fixed geographic positions, stable online time and good performance. With the popularization of household bandwidth of hundreds of megabytes and gigabytes, the bandwidth capacity of household internet equipment is improved, and the requirement of serving as a PCDN node is met. On the other hand, the number of the household internet devices is huge, and the requirement of burst flow can be met.
In this embodiment, the PCDN node is formed by using the P2P technology and home edge internet access terminal devices, so that the cost is low and the performance is stable, thereby realizing low-cost and high-quality content distribution.
Example two
As shown in fig. 3, in order to make the PCDN node operate stably, the present embodiment further provides a data distribution method, where before the user downloads data from the PCDN node, the interaction between the PCDN and the scheduling server includes:
s301, starting up the PCDN;
s302, the PCDN sends a login request to a scheduling server;
the login request may include information related to the capability of the PCDN node, and preferably, the login request may include the storage space size of the PCDN node, network bandwidth, IP address, geographical location, device type, and PCDN node ID.
S303, the dispatching server sends a login success message to the PCDN node.
And after recording the relevant information of the PCDN, the scheduling server sends a login success message to the PCDN to confirm the completion of the login.
Preferably, the dispatching server can also check the capability of the PCDN, and if the capability of the PCDN does not meet the requirement, the login is refused. As a preferred example, the capability check may include one or a combination of the following: whether the storage capacity meets the requirements, whether the geographic location exceeds a predetermined range, whether the network bandwidth meets the requirements, and the like.
And S304, the PCDN node starts a heartbeat timer.
S305, when the heartbeat timer is over time, the PCDN node sends heartbeat messages to the dispatching server.
In order to maintain the link between the PCDN node and the scheduling server and avoid the PCDN from being disconnected but the scheduling system still performs scheduling on line, the PCDN node needs to start a heartbeat timer, the duration of the timer is T, namely, the heartbeat message is sent to the scheduling server at intervals of T. The heartbeat timer is started circularly, namely, the heartbeat timer continues to count again after the heartbeat timer expires. Preferably, the length of the time interval T is preset as needed. As a preferred example, the time interval T may be 10 seconds or 5 seconds, but may also be of other time lengths.
Preferably, if the scheduling server does not receive the heartbeat message of the PCDN node within N consecutive times T, the scheduling server determines that the PCDN link is interrupted, where N is an integer greater than or equal to 2. For the interrupted PCDN node, the scheduling server does not schedule any more and waits for logging again.
Through the steps, the PCDN node is started up and logs in the scheduling server, and the scheduling server takes the PCDN as an available resource for further scheduling. As shown in fig. 4, before providing data sharing to users, the PCDN needs to download and store data segments to be shared from the CDN, and the flow is as follows:
s401, the dispatching server sends a resource downloading indication message to the PCDN;
the unique identifier of the resource is included in the download indication message. As a preferred embodiment, the resource may be represented in file segments, i.e. which piece of data of which file is requested. To be globally unique, as a preferred embodiment, a file segment is represented by a hash value of a Uniform Resource Locator (URL). The file segment is a basic unit scheduled by the PCDN, refers to a continuous fragment of a certain resource file, and is represented by a starting interval and an ending interval of the segment, for example, [0,4] represents a fragment of a certain file from the 0 th slice to the 4 th slice with the length of 5 slices.
It should be noted that the scheduling server records the resource information requested by the user each time, and calculates the heat of the resource according to the statistical result. That is, for each requested resource, the number of requests in time T2 is counted, and the more the number of requests is, the more popular the resource is. Preferably, the scheduling server counts the first M resources requested for the most number of times within time T2, and instructs the PCDN to download the M resources by sending a resource download instruction message to the PCDN. That is, the scheduling server may sort the number of resource requests in time T2 by size, indicating the first M resources for which the PCDN has been downloaded most frequently. Where T2 is a predetermined value and M is an integer of 1 or more.
As a preferred embodiment, if the storage space of the PCDN is full, the PCDN may send a notification message to the scheduling server, and after receiving the message, the scheduling server indicates the PCDN to replace the resource in the download indication message. Specifically, the PCDN is instructed to download the hot resource mRReplacement of cold door resource mL(ii) a Wherein the hot door informationSource mRThe number of requests in time T2 is greater than the cold resource mLThe number of requests within time T2, the PCDN having stored therein the cold resource mLAnd the hot resource m is not storedR
As another preferred embodiment, the download instruction may include CDN-related information about resources to be downloaded, so that the PCDN downloads the corresponding resources to the target CDN.
S402, the PCDN sends a resource request message to a Content Delivery Network (CDN) according to the download indication message;
after receiving the downloading indication, the PCDN analyzes the resource identifier to be downloaded and the target CDN from the indication information and sends a resource request to the target CDN. The request message includes a resource identifier.
S403, the CDN sends a resource request success message to the PCDN;
after receiving the request of the PCDN, the CDN feeds back a request success message to the PCDN if the CDN has the requested resources, otherwise feeds back a request failure message.
S404, the PCDN starts data transmission with the CDN;
s405, after the downloading is completed, the PCDN sends a downloading completion message to the scheduling server.
After receiving the message of finishing the downloading of the PCDN, the scheduling server can start scheduling the related resources according to the requirements of the users.
In the embodiment, the PCDN is logged in and the resources are downloaded and prestored through the interaction between the scheduling server and the PCDN, so that the resources are quickly shared to the user through the PCDN, the pressure of the CDN is reduced, and the resource sharing efficiency is improved.
EXAMPLE III
The embodiment provides a data distribution method, and when a user fails to request resources from a scheduling server or times out, the user can download data in one of the following ways. It should be noted that, after the user sends the resource request, the timer T3 is started to wait for the response of the scheduling server, and when the timer T3 finishes timing and does not receive the response of the scheduling server, the timeout is determined.
The first method is as follows: as shown in fig. 6, the process flow is as follows:
s601, a user sends a resource request to a scheduling server;
the content of the request is the same as S501, and the description of this embodiment is omitted.
S602, the scheduling server sends a request failure message to the user;
the scheduling server searches resources in the PCDN according to the request of the user, and the searching method is detailed in S502, which is not described in detail in this embodiment.
And when the scheduling server does not search the schedulable PCDN for the requested resource or does not search the PCDN meeting the scheduling condition, feeding back a request failure message to the user.
S603, the user sends a resource request to the CDN;
when the response of the user waiting for the scheduling server is overtime or the scheduling server fails to feed back the request, the user directly initiates a resource request to the CDN. Preferably, the content included in the request message is the same as S501, and is not described in detail in this embodiment.
S604, the user starts data transmission with the CDN.
The second method comprises the following steps: as shown in fig. 7, the process flow is as follows:
s701, a user sends a resource request to a scheduling server;
the content of the request is the same as S501, and the description of this embodiment is omitted.
S702, the scheduling server sends a request failure message to the user;
the process of the scheduling server is the same as S602, which is not described in detail in this embodiment.
S703, the user sends a resource request to the resource list server;
it should be noted that the resource list server is configured to store all user node information that owns a certain resource, and the user node obtains other user information that owns the resource by requesting, and implements resource sharing between the client and the client by using the P2P technology.
Preferably, the content of the resource request message is consistent with S501, and this embodiment is not described again.
And when the response of the user waiting for the scheduling server is overtime or the feedback request of the scheduling server fails, sending a resource request to the resource list server.
S704, the resource list server sends a request success message to the user.
And the resource list server searches the requested resources in the recorded resources according to the requested content, and feeds back the user information of the owned resources to the requesting user when the user with the requested resources is searched.
Preferably, the resource list server may consider the geographical location information when searching. And if the distance between the geographical position of the user owning the requested resource and the geographical position of the node of the user requesting the resource is within a preset range, the address information of the user owning the resource is included in the request success message.
Preferably, when there are a plurality of users (i.e. 2 or more) having the requested resource satisfying the geographical location condition, the resource list server may feed back the address information of the user node having the shortest distance to the user node requesting the resource. As another preferred example, the resource list server may also feed back all address information of the top S user nodes having the requested resource to the resource requesting user node, and the resource requesting user node may decide which user node to obtain data from.
Preferably, when searching for a user node having a requested resource, the resource list server may also consider the stability of the uplink bandwidth, and may also consider ISP connectivity, and preferably select a user node having a stable uplink bandwidth, a short distance, and good ISP connectivity to send data to the user node requesting the resource.
Further, when the resource list server searches for a user node having the requested resource that satisfies the condition, success of the request is indicated in the feedback information, otherwise failure is indicated.
S705, the user starts data transmission with the user N having the requested resource through the P2P technology.
In this embodiment, when a user fails to request a resource from the scheduling server, data is downloaded from other users having the resource, thereby realizing data sharing among the users.
The third method comprises the following steps: as shown in fig. 8, the process flow is as follows:
s801, a user sends a resource request to a scheduling server;
the content of the request is the same as S501, and the description of this embodiment is omitted.
S802, the scheduling server sends a request failure message to the user;
the process of the scheduling server is the same as S602, which is not described in detail in this embodiment.
S803, the user sends a resource request to the resource list server;
this step is the same as S703, and is not described again in this embodiment.
S804, the resource list server sends a request failure message to the user;
and when the resource list server does not search the requested resource or does not have the user node meeting the condition, sending a request failure message to the user requesting the resource.
S805, the user sends a resource request message to the CDN;
and when the response of the user waiting for the resource list server is overtime or the resource list server fails to feed back the request, directly sending the resource request to the CDN.
Preferably, the content included in the request message is the same as S501, and is not described in detail in this embodiment.
S806, the user starts data transmission with the CDN;
in this embodiment, when the user fails to request resources from the scheduling server and the resource list server, the user requests data from the CDN, thereby implementing downloading of the requested resources.
Example four
This embodiment should provide a data distribution system, as shown in fig. 2, the system includes: content distribution network 201, user node 202, PCDN node 203, dispatch server 204 and P2P pass through server 205.
The Content Delivery Network 201, namely, a Content Delivery Network (CDN), is used to deploy resources to be shared, such as video, audio, and pictures. The CDN may be a virtual network built on top of an existing network;
the PCDN node 203, i.e., Peer to Peer Content Delivery Network, is abbreviated as PCDN, and is composed of optical modems, home routers, OTT, or other devices operating on the edge of the internet. Optionally, the device runs a special software, and is deployed and issued by a network operator;
the scheduling server 204 is responsible for receiving the resource request of the user node and returning PCDN node information with resources;
the P2P penetration server 205 is used for assisting P2P (Peer to Peer) penetration between the PCDN node and the user node to realize Network Address Translation (NAT);
the PCDN node 203 is scheduled by the scheduling server 204, downloads and caches specified media data from a CDN source by using a limited storage space, and provides the specified media data to a user node through a P2P technology according to the request of a user;
data information is transmitted among the CDN201, the user node 202 and the PCDN node 203;
data information is transmitted between the PCDN node 203 and the user node 202;
the PCDN node 203 transmits control information with the scheduling server 204 and the P2P penetration server 205;
the user node 202 has control information transmission with the dispatch server 204 and the P2P pass through server 205;
the PCDN node 203 is a home internet access device, and includes an optical modem, a home router, or an Over The Top device (OTT device) operating at The edge of The internet.
As a preferred embodiment, the user node 202 is further configured to send a resource request to the scheduling server 204;
the scheduling server 204 is further configured to send resource request feedback information to the user node 202 according to a resource request of the user node 202; wherein the feedback information comprises address information of a PCDN owning the resource;
if the request for feedback information is successful, the user node 202 is further configured to download the resource from the PCDN.
As a preferred embodiment, after the PCDN node 203 is powered on, it is configured to send a login request to the scheduling server 204; the dispatching server 204 records the relevant information of the PCDN node 203 according to the login request and sends a login success message to the PCDN node 203. Preferably, the scheduling server 204 may also perform capability check on the PCDN node 203, and refuse to log in if the capability of the PCDN node 203 does not meet the requirement. As a preferred example, the capability check may include one or a combination of the following: whether the storage capacity meets the requirements, whether the geographic location exceeds a predetermined range, whether the network bandwidth meets the requirements, and the like.
The PCDN node 203 is further configured to start a heartbeat timer after receiving a login success message; when the heartbeat timer is overtime, sending a heartbeat message to the scheduling server; the heartbeat timer is used for sending a heartbeat message to the scheduling server by the PCDN every T time and maintaining the link with the scheduling server. If the scheduling server 204 does not receive the heartbeat message of the PCDN node within N consecutive times T, the scheduling server 204 determines that the PCDN node 203 link is broken. For the interrupted PCDN node, the scheduling server does not schedule any more and waits for logging again. N is an integer of 2 or more.
As a preferred embodiment, before the user node 202 downloads resources from the PCDN node 203, the scheduling server 204 is further configured to send a resource download indication message to the PCDN node 203; the PCDN node 203 sends a resource request message to the CDN201 according to the download instruction message; the CDN201 sends a resource request success message to the PCDN node 203; the PCDN node 203 downloads the resource from the CDN201, and after the downloading is completed, sends a download completion message to the scheduling server 204.
It should be noted that, the embodiment of the system and the embodiment of the method are based on the same inventive concept, the same technical problems are solved, the same technical effects are achieved, the system can achieve all the methods described in the above all the embodiments of the method, and repeated details are not repeated.
EXAMPLE five
On the basis of the fourth embodiment, this embodiment further provides a data distribution system, as shown in fig. 9, the system includes a content distribution network CDN901, a user node 902, a PCDN node 903, a scheduling server 904, a P2P penetration server 905, a management system server 906, and a resource list server 907.
The CDN901, i.e., Content Delivery Network, is used to deploy resources to be shared by video/audio/pictures. The CDN may be a virtual network built on top of an existing network;
the PCDN node 903, i.e., Peer to Peer Content Delivery Network, is called PCDN for short, and is composed of devices such as optical modems, home routers, or OTTs, which run on the edge of the internet. Optionally, the device runs a special software, and is deployed and issued by a network operator;
the scheduling server 904 is responsible for receiving the resource request of the user node and returning the PCDN node information with the resource;
the P2P penetration server 905 is used for assisting P2P (Peer to Peer) penetration between the PCDN node and the user node to realize Network Address Translation (NAT);
the management system server 906 is used for realizing management functions such as node management, equipment authorization, flow statistics, log summarization, hot resource analysis and the like, facilitating management of a system administrator and content providers to know flow use conditions, ensuring content safety of a PCDN system and improving system operation efficiency;
the resource list server 907 is configured to store all user node information that owns a certain resource, and the user obtains other user information that owns the resource by requesting, and implements resource sharing between the client and the client by using the P2P technology.
Data information is transmitted between the CDN901 and the user node 902 and the PCDN node 903;
data information is transmitted between the PCDN node 903 and the user node 902;
control information is transmitted between the PCDN node 903 and the dispatch server 904 and the P2P pass-through server 905;
control information is transmitted between the user node 902 and the dispatch server 904 and the P2P pass through server 905;
control information is transmitted between the PCDN node 903 and the management system server 906;
there is control information transmission between the user node 902 and the resource list server 907;
the PCDN node 903 is a home internet access device, and includes an optical modem, a home router, or an Over The Top device (OTT device) operating at The edge of The internet.
It should be noted that the data distribution system provided in this embodiment can implement the same functions in the fourth embodiment, solve the same technical problems, and implement the same technical effects, and the details of the same parts are not repeated.
The system provided in this embodiment is further configured to, when the user node 902 fails to request the resource from the scheduling server 904, obtain data in one of the following three ways.
The first method is as follows:
the user node 902 sends a resource request to the scheduling server 904;
the content of the request is the same as S501, and the description of this embodiment is omitted.
The scheduling server 904 sends a request failure message to the user node 902;
the scheduling server 904 searches for resources in the PCDN according to the request of the user, and the searching method is detailed in S502, which is not described in detail in this embodiment.
When the scheduling server 904 does not search for the requested resource in the schedulable PCDNs or does not have a PCDN satisfying the scheduling condition, a request failure message is fed back to the user node 902.
The user node 902 sends a resource request to the CDN 901;
when the user node 902 waits for the response of the scheduling server 904 to time out, or the scheduling server 904 fails to feed back the request, the user node 902 directly initiates a resource request to the CDN 901. Preferably, the content included in the request message is the same as S501, and is not described in detail in this embodiment.
The user node 902 starts data transmission with the CDN 901.
The second method comprises the following steps:
the user node 902 sends a resource request to the scheduling server 904;
the content of the request is the same as S501, and the description of this embodiment is omitted.
The scheduling server 904 sends a request failure message to the user node 902;
the process of the scheduling server 904 is the same as S602, and is not described in detail in this embodiment.
The user node 902 sends a resource request to the resource list server 907;
preferably, the content of the resource request message is consistent with S501, and this embodiment is not described again.
When the user node 902 waits for the response of the scheduling server 904 to time out or the scheduling server 904 fails to feed back the request, it transmits a resource request to the resource list server 907.
The resource list server 907 transmits a request success message to the user;
the resource list server 907 searches the requested resources among the recorded resources according to the requested content, and when a user having the requested resources is searched, feeds back user information having the resources to the requesting user.
Preferably, the resource list server 907 may consider geographical location information when searching. And if the distance between the geographical position of the user owning the requested resource and the geographical position of the node of the user requesting the resource is within a preset range, the address information of the user owning the resource is included in the request success message.
Preferably, when there are a plurality of (i.e. 2 or more) users having the requested resource satisfying the above geographical location condition, the resource list server 907 may feed back the address information of the user node having the shortest distance to the user node having the requested resource. As another preferred example, the resource list server 907 may also feed back all address information of the top S user nodes having the requested resource to the resource requesting user node, and the resource requesting user node may decide which user node to obtain data from.
Preferably, when searching for a user node having a requested resource, the resource list server 907 may also consider the stability of the uplink bandwidth, and may also consider ISP connectivity, and preferably select a user node having a stable uplink bandwidth, a short distance, and good ISP connectivity to send data to the user node requesting the resource.
Further, when the resource list server 907 searches for a user node having the requested resource that satisfies the condition, success of the request is indicated in the feedback information, otherwise failure is indicated.
The user node 902 initiates data transfer with the user N having the requested resource via P2P technology.
The third method comprises the following steps:
the user node 902 sends a resource request to the scheduling server 904;
the content of the request is the same as S501, and the description of this embodiment is omitted.
The scheduling server 904 sends a request failure message to the user node 902;
the process of the scheduling server 904 is the same as S602, and is not described in detail in this embodiment.
The user node 902 sends a resource request to the resource list server 907;
this step is the same as S703, and is not described again in this embodiment.
The resource list server 907 transmits a request failure message to the user node 902;
when the resource list server 907 does not search for the requested resource or there are no user nodes that satisfy the conditions, a request failure message is sent to the user requesting the resource.
The user node 902 sends a resource request message to the CDN 901;
when the user node 902 waits for the response of the resource list server 907 to time out or the resource list server 907 fails to feed back the request, it directly sends the resource request to the CDN 901.
Preferably, the content included in the request message is the same as S501, and is not described in detail in this embodiment.
The user node 902 starts data transmission with the CDN 901;
in this embodiment, when the user fails to request resources from the scheduling server 904 and the resource list server 907, the user requests data from the CDN901, so as to implement downloading of the requested resources.
It should be noted that, the embodiment of the system and the embodiment of the method are based on the same inventive concept, the same technical problems are solved, the same technical effects are achieved, the system can achieve all the methods described in the above all the embodiments of the method, and repeated details are not repeated.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (10)

1. A method for data distribution, the method comprising:
a user sends a resource request to a scheduling server;
the scheduling server sends resource request feedback information to the user according to the resource request;
if the request feedback information is a request success, the user downloads the resource from a Peer-to-Peer data distribution Network Peer-to-PeerContent Delivery Network, PCDN;
the PCDN is a home Internet access device, The feedback information comprises address information of The PCDN with The resources, and The home Internet access device comprises an optical modem, a home router or Over The Top device which runs at The edge of The Internet.
2. The method of claim 1, wherein prior to the user downloading the resource from the PCDN, further comprising:
the dispatching server sends a resource downloading indication message to the PCDN;
the PCDN sends a resource request message to a Content Delivery Network (CDN) according to the download indication message;
the CDN sends a resource request success message to the PCDN;
and the PCDN downloads the resources from the CDN and sends a download completion message to the scheduling server after the download is completed.
3. The method of claim 2, wherein before the scheduling server sends the resource download indication message to the PCDN, further comprising:
after the PCDN is started, a login request is sent to the scheduling server;
the dispatching server records the PCDN relevant information according to the login request and sends a login success message to the PCDN;
after receiving the login success message, the PCDN starts a heartbeat timer;
when the heartbeat timer is overtime, sending a heartbeat message to the scheduling server;
the heartbeat timer is used for sending a heartbeat message to the scheduling server by the PCDN every T time and maintaining the link with the scheduling server.
4. The method of claim 1, wherein if the request feedback message is a request failure or a timeout, the user acquires the resource by one of:
the first method is as follows:
the user sends a resource request to a Content Delivery Network (CDN);
the user acquires the resource from the CDN;
the second method comprises the following steps:
the user sends a resource request to a resource list server;
the resource list server sends a request success message to the user;
the user downloads the resources from other users according to the request success message;
wherein the request success message includes address information indicating a user who owns the resource;
the third method comprises the following steps:
the user sends a resource request to a resource list server;
the resource list server sends a request failure message to the user;
the user sends a resource request to a Content Delivery Network (CDN);
and the user acquires the resources from the CDN.
5. The method of claim 2, wherein the sending, by the scheduling server, the resource download indication message to the PCDN specifically comprises:
the scheduling server counts M resources with the largest request times in time T2, and instructs the PCDN to download the M resources by sending a resource downloading indication message to the PCDN;
where T2 is a predetermined value, and M is an integer of 1 or more.
6. The method of claim 2, wherein the sending, by the scheduling server, the resource download indication message to the PCDN specifically comprises:
if the storage space of the PCDN is full, indicating the PCDN to download hot resources mRReplacement of cold door resource mL
Wherein the hot resource mRThe number of requests in time T2 is greater than the cold resource mLThe number of requests within time T2, the PCDN having stored therein the cold resource mLAnd the hot resource m is not storedR
7. A data distribution system, comprising:
the Content Delivery Network (CDN) is used for deploying resources to be delivered;
the PCDN Peer to Peer Content Delivery Network node is used for downloading and caching specified media data from the CDN;
the dispatching server is used for receiving a resource request of a user and returning to a PCDN node with resources;
a Peer-to-Peer (P2P) penetration server for assisting the PCDN node and the user node in realizing Network Address Translation (NAT) and the P2P penetration of NAT;
a user node;
data information is transmitted between the CDN and the user node and between the CDN and the PCDN node;
data information is transmitted between the PCDN and the user node;
the PCDN is transmitted with the dispatching server and the P2P penetration server by control information;
control information is transmitted between the user node and the scheduling server and the P2P penetration server;
the PCDN is a home Internet access device;
the home internet equipment comprises an optical modem, a home router or Over The Top equipment which runs at The edge of The internet.
8. The system of claim 7, comprising:
the user node sends a resource request to the scheduling server;
the scheduling server sends resource request feedback information to the user node according to the resource request;
if the request feedback information is a request success, the user node downloads the resource from the PCDN;
wherein the feedback information includes address information of a PCDN owning the resource.
9. The system of claim 8, wherein before the scheduling server sends the resource download indication message to the PCDN, further comprising:
after the PCDN is started, a login request is sent to the scheduling server;
the dispatching server records the PCDN relevant information according to the login request and sends a login success message to the PCDN;
after receiving the login success message, the PCDN starts a heartbeat timer;
when the heartbeat timer is overtime, sending a heartbeat message to the scheduling server;
the heartbeat timer is used for sending a heartbeat message to the scheduling server by the PCDN every T time and maintaining the link with the scheduling server.
10. The system of claim 7, wherein if the request feedback message is a request failure or a timeout, the user acquires the resource by one of:
the first method is as follows:
the user sends a resource request to a Content Delivery Network (CDN);
the user acquires the resource from the CDN;
the second method comprises the following steps:
the user sends a resource request to a resource list server;
the resource list server sends a request success message to the user;
the user downloads the resources from other users according to the request success message;
wherein the request success message includes address information indicating a user who owns the resource;
the third method comprises the following steps:
the user sends a resource request to a resource list server;
the resource list server sends a request failure message to the user;
the user sends a resource request to a Content Delivery Network (CDN);
and the user acquires the resources from the CDN.
CN202010124510.5A 2020-02-27 2020-02-27 Data distribution method and system Pending CN111355798A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010124510.5A CN111355798A (en) 2020-02-27 2020-02-27 Data distribution method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010124510.5A CN111355798A (en) 2020-02-27 2020-02-27 Data distribution method and system

Publications (1)

Publication Number Publication Date
CN111355798A true CN111355798A (en) 2020-06-30

Family

ID=71194123

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010124510.5A Pending CN111355798A (en) 2020-02-27 2020-02-27 Data distribution method and system

Country Status (1)

Country Link
CN (1) CN111355798A (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112084449A (en) * 2020-09-07 2020-12-15 深圳市雷鸟网络传媒有限公司 Terminal operation method, operation server control method, terminal and medium
CN113507522A (en) * 2021-07-08 2021-10-15 上海七牛信息技术有限公司 Method and system for improving hit rate of PCDN (Primary Contourlet distribution) network requests
CN113590552A (en) * 2021-08-02 2021-11-02 北京金山云网络技术有限公司 File updating method and device, computer equipment and storage medium
CN113590539A (en) * 2021-08-02 2021-11-02 北京金山云网络技术有限公司 File pre-distribution method and device, computer equipment and storage medium
CN113612841A (en) * 2021-08-02 2021-11-05 北京金山云网络技术有限公司 Task scheduling method and device, computer equipment and storage medium
CN113630457A (en) * 2021-08-02 2021-11-09 北京金山云网络技术有限公司 Task scheduling method and device, computer equipment and storage medium
CN114222168A (en) * 2021-12-02 2022-03-22 上海哔哩哔哩科技有限公司 Resource scheduling method and system
WO2023109863A1 (en) * 2021-12-15 2023-06-22 华为云计算技术有限公司 Content delivery network system and content delivery method
CN116916048A (en) * 2023-09-07 2023-10-20 典基网络科技(上海)有限公司 Hybrid architecture, method, device and medium for streaming media transmission optimization
WO2024131383A1 (en) * 2022-12-22 2024-06-27 腾讯科技(深圳)有限公司 Data processing method and related apparatus

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101534204A (en) * 2008-03-10 2009-09-16 中国网通集团宽带业务应用国家工程实验室有限公司 Streaming media information distribution system and method thereof and user end
CN104283981A (en) * 2014-10-14 2015-01-14 无锡云捷科技有限公司 CDN transparent cache method based on hot spot mechanism
US20150100779A1 (en) * 2013-10-09 2015-04-09 Symantec Corporation Reducing latency for certificate validity messages using private content delivery networks
CN106537878A (en) * 2014-07-11 2017-03-22 微软技术许可有限责任公司 Private content distribution network
CN108259945A (en) * 2018-04-19 2018-07-06 腾讯音乐娱乐科技(深圳)有限公司 The method and apparatus that processing plays the playing request of multi-medium data
CN110417861A (en) * 2019-06-25 2019-11-05 腾讯科技(北京)有限公司 A kind of information-pushing method and relevant apparatus
CN110769023A (en) * 2019-08-21 2020-02-07 广东工业大学 Point-to-point content distribution network system based on intelligent home gateway

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101534204A (en) * 2008-03-10 2009-09-16 中国网通集团宽带业务应用国家工程实验室有限公司 Streaming media information distribution system and method thereof and user end
US20150100779A1 (en) * 2013-10-09 2015-04-09 Symantec Corporation Reducing latency for certificate validity messages using private content delivery networks
CN106537878A (en) * 2014-07-11 2017-03-22 微软技术许可有限责任公司 Private content distribution network
CN104283981A (en) * 2014-10-14 2015-01-14 无锡云捷科技有限公司 CDN transparent cache method based on hot spot mechanism
CN108259945A (en) * 2018-04-19 2018-07-06 腾讯音乐娱乐科技(深圳)有限公司 The method and apparatus that processing plays the playing request of multi-medium data
CN110417861A (en) * 2019-06-25 2019-11-05 腾讯科技(北京)有限公司 A kind of information-pushing method and relevant apparatus
CN110769023A (en) * 2019-08-21 2020-02-07 广东工业大学 Point-to-point content distribution network system based on intelligent home gateway

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
谢晓雯: "《基于P2P技术的PCDN网络设计》", 《中国优秀硕士学位论文全文数据库-信息科技辑》 *
阿里云开发者社区: "《使用阿里云PCDN降低内容分发成本》", 《HTTPS://DEVELOPER.ALIYUN.COM/ARTICLE/73659》 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112084449B (en) * 2020-09-07 2024-08-20 深圳市雷鸟网络传媒有限公司 Terminal operation method, operation server control method, terminal and medium
CN112084449A (en) * 2020-09-07 2020-12-15 深圳市雷鸟网络传媒有限公司 Terminal operation method, operation server control method, terminal and medium
CN113507522A (en) * 2021-07-08 2021-10-15 上海七牛信息技术有限公司 Method and system for improving hit rate of PCDN (Primary Contourlet distribution) network requests
CN113590552A (en) * 2021-08-02 2021-11-02 北京金山云网络技术有限公司 File updating method and device, computer equipment and storage medium
CN113590539A (en) * 2021-08-02 2021-11-02 北京金山云网络技术有限公司 File pre-distribution method and device, computer equipment and storage medium
CN113612841A (en) * 2021-08-02 2021-11-05 北京金山云网络技术有限公司 Task scheduling method and device, computer equipment and storage medium
CN113630457A (en) * 2021-08-02 2021-11-09 北京金山云网络技术有限公司 Task scheduling method and device, computer equipment and storage medium
CN114222168A (en) * 2021-12-02 2022-03-22 上海哔哩哔哩科技有限公司 Resource scheduling method and system
CN114222168B (en) * 2021-12-02 2024-03-12 上海哔哩哔哩科技有限公司 Resource scheduling method and system
WO2023109863A1 (en) * 2021-12-15 2023-06-22 华为云计算技术有限公司 Content delivery network system and content delivery method
WO2024131383A1 (en) * 2022-12-22 2024-06-27 腾讯科技(深圳)有限公司 Data processing method and related apparatus
CN116916048A (en) * 2023-09-07 2023-10-20 典基网络科技(上海)有限公司 Hybrid architecture, method, device and medium for streaming media transmission optimization
CN116916048B (en) * 2023-09-07 2023-11-17 典基网络科技(上海)有限公司 Hybrid architecture, method, device and medium for streaming media transmission optimization

Similar Documents

Publication Publication Date Title
CN111355798A (en) Data distribution method and system
EP3595268B1 (en) Streaming media resource distribution method, system, edge node and central dispatching system
CN108737405B (en) Method, CCL server and system for guiding direct broadcasting video stream
US10506062B2 (en) Network-optimized content delivery for high demand non-live contents
CN109347968B (en) Method, equipment and system for downloading data blocks of resource file
CN111327622B (en) Resource scheduling method and system
RU2647654C2 (en) System and method of delivering audio-visual content to client device
US20110246608A1 (en) System, method and device for delivering streaming media
US20090113253A1 (en) System and apparatus for delivering media and method for playing streaming media
CN105187847B (en) A kind of distributed network live telecast method, apparatus, video gateway and system
JP2004515173A (en) Integrated delivery architecture for multipoint video conferencing and interactive broadcast systems
JP2009165092A (en) Network transmission system and method of stream data
US10848586B2 (en) Content delivery network (CDN) for uploading, caching and delivering user content
CN102231762B (en) Peer-to-peer (p2p) server architecture capable of being unlimitedly and horizontally expanded
CN101179565A (en) Method of implementing essential service of electric playbill
WO2023061060A1 (en) Audio and video code stream scheduling method, system, medium and electronic apparatus
CN115002497B (en) Live broadcast source-returning scheduling method and system and source-returning server
WO2017182815A1 (en) Media data streaming method and apparatus
CN113014672B (en) Message pushing method and device, electronic equipment and storage medium
EP2890081B1 (en) Aggregated adaptive bit rate streaming
CN111147817B (en) Video processing method and device, electronic equipment and storage medium
JP3836843B2 (en) Method for receiving content distributed by multiple channels via information network by one terminal
CN105657570B (en) The resource transmission method and device of cache platform
CN105210347B (en) Monitoring server, resolution server, request equipment and node selecting method
KR20080042524A (en) Method and system for vod service based on p2p

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200630